muhonve
24th March 2004, 14:59
When reconfiguring tables I keep getting these errors after installation of SP9-SP14 and porting set 6.1c.07.01.

tcmcs991010 * 25 Drop original table error 113
Undo .... 25 Adding indexes ...
Error 113 for create index 9999.

I'm the only user in the system, so the tables are not locked (113).

And the worst thing is, that runtime dd is updated !!!
So after the reconfiguration I cannot access the table at all. : (

Anyone had similar errors?


/ Vesa

en@frrom
24th March 2004, 16:31
Try to restart shared memory. If this won't help, I recommend to restart Baan completely.

Brendan Shine
24th March 2004, 23:06
If you are using Informix it is possible to get a table lock due to a SQL parse lock--have your DBA check if such a lock exists--if so, would need to bounce Informix.

dave_23
24th March 2004, 23:39
Vesa,

First, move your old DD back into place. Do an
explode6.X d<table>
ex.
explode6.1 dtccom000

that will tell you where the DD is.. In that directory will be a
dtccom000.old.

Do:
mv dtccom000 dtccom000.new
mv dtccom000.old dtccom000

You can get 113 errors becuase Baan is checking referential integrity on other tables. Try running bdbreconfig with -mn option.
(you can create a wrapper script to go around bdbreconfig to put these options on).

Then, log a case with Baan support.

Dave