Hi,

I am in process of upgrading baan from IVc to IVc4.
I am getting error 512 (corrupt DD) on table ttiex188 while I was running installation CD.
When I look at the table via GTM, I can see the table just fine.
Not sure why the installation program is aborting with 512.

Any one experienced this problem? Any help is appreciated.

Environment:

OS: windows 2003
DB: SQL 2000

Thanks

Hello,

Possible Cause: This error could be due to the fact that the definition of the used table no longer matches the definition in the data dictionary.

Solution: The first thing you need to do is check the following log files in $BSE/log:
• log.bshell
• log.bdbreconfig6.x
• log."dbname" example: log.oracle8

In these logs you will find the mismatch.

Troubleshooting steps for a mismatched table definition. For example, table tccom010 from company 812 is corrupt with error 512.

To troubleshoot the problem:

1. Change directory to the used table definition:
• cd $BSE/dict/ddOPER_001/dtccom

2. Copy the used table definition to the .new extension:
• cp dtccom010 dtccom010.new

3. Copy a table definition from another package combination to the current package combination (overwriting the original table definition):
• cp $BSE/dict/dd31Sb/dtccom/dtccom010 $BSE/dict/ddOPER_001/dtccom
• Or you can create a table definition that matches the table.

4. Check to see if the table can be viewed again:
• ba6.1 ttaad4100
• Select the table tccom010812

5. If the error 512 doesn't occur, then go to step 6. If it still occurs, retry with another package combination and go to step 3.

6. Go to Unix and run this command:
• bdbreconfig6.1 -Ntccom010 -C812
• That should rebuild the table

7. Move the table definition with the .new extension and overwrite the one without extension:
• mv dtccom010.new dtccom010

8. Run refint6.2 -r -s -I<filename> -C000

Note: If copying files as user root, then check the permissions!

This procedure can be used for all tables mentioned in the log files with an error 512.

Good luck.