Hello,

since we migrate from Baanbase to Oracle we have some troubles to create tables with ttaad4227m000 Create Tables from Seq. Dump,

we get the Error "Can not commit transaction (error 520)"

2009-05-06[16:55:29]:E:6brvhx: ******* S T A R T of Error message *******
2009-05-06[16:55:29]:E:6brvhx: Log message called from /BAAN/view/port.6.1c.07.15/vobs/tt/bdb_tools/bdb_bdbpost.c: #1022 keyword:
2009-05-06[16:55:29]:E:6brvhx: Pid 48248 Uid 445 Euid 445 Gid 125 Egid 125
2009-05-06[16:55:29]:E:6brvhx: user_type S language 2 user_name 6brvhx tty ote locale ISO88592/NULL
2009-05-06[16:55:29]:E:6brvhx: Errno 0 bdb_errno 520 (Error during buffered updates)
2009-05-06[16:55:29]:E:6brvhx: Log_mesg: tipcs023990: Error for commit 520
2009-05-06[16:55:29]:E:6brvhx: ******* E N D of Error message *******

this error appears mostly with big tables, but sometimes also with small one,

if we refresh a Test-Company we dump the Live-Comp., delete the Tables in the Testcomp. and start the import with ttaad4227m000 (with Ign.Ref.Integ.Constr.),
then the Cannot Com. Error appears for a few tables,
then we import the not importet Tables seperatly (with the Pattern to Match Table Names on Form2)

We could not find any cause of defect

regards
Robert

First try to check in logfiles, whether there are other log entries just above the one you've send. In some cases error 520 comes out as a result of previous errors, which are visible in logfile in preceeding lines. If it's not your case, try to switch off range checking ni ttaad4227m000. Check also date fields in your tables - in Baanbase a value of "-1" was accepted in a date field, and it caused me problems with migration to another DB - when ttaad4227 encounters a record with date = -1, it can raise error 205 and then 520 (two entries in logfile).
Of course, there can be Oracle related problems as well - like problems with redo logs, unability to extent tablespace etc. For all those you should have another entries in logfiles.

Follow these steps :

1. Login as bsp or super user and go to session ttaad41110m000
2. Uncheck "Audit trail" option , Save , goto special "Convert to runtime" , logout and login .
3. Load the data from seq dump.

revert back the setting when finish dumping data.

regards

Hi,

I think ,Importing Huge Table data from seq.dump must have filled the temp Tablespace.
then it will show size as 0 in "Oracle Enterprise manager".

just Drop the Temp tbs and Recreate it.

This must do the trick.

Regards,
Sushil Kumar Mudaliar