Hi Frank,
That's quite strange - it looks like it's a potential problem within the unload process then. We did have another report of a similar issue from a customer a while back, but it doesn't look like we were able to determine the absolute root cause as the issue was resolved once the software was re-installed.
Is there any other information you might be able to provide about this database about its origin and history? The "dbinfo" information might be useful, along with 'SELECT * FROM SYS.SYSHISTORY'. Does 'DBA' really have 'DBA' authority, or are there other permissions involved?
Can this database be provided to us for further analysis? If all of the table data is dropped, does the issue still reproduce?
Regards,
Jeff Albion
SAP Active Global Support