Go Back > Forum > Baan Quick Support: Functional & Technical > Tools Administration & Installation

Maintenance Warning will be unavailable on Saturday 26th of January from 12hrs until Sunday 27 of January at 18hrs (GMT+1) due to infrastructure upgrades.

User login

Frontpage Sponsor


Google search

How big is your Baan-DB (just Data AND Indexes)
0 - 200 GB
200 - 500 GB
500 - 800 GB
800 - 1200 GB
1200 - 1500 GB
1500 - 2000 GB
> 2000 GB
Total votes: 42

Baanboard at LinkedIn

Reference Content

Thread Tools Display Modes
Old 29th June 2007, 20:50
kbabu1's Avatar
kbabu1 kbabu1 is offline
Join Date: Sep 2003
Location: India, Mumbai
Posts: 46
kbabu1 is on a distinguished road
Baan: Baan 4 and 5, Infor ERP LN - DB: Oracle, SQL Server - OS: Windos 2000, Unix
Corrupted data dictionary (error 512)
Baan: Other/Unknown
DB: Other/Unknown
OS: Other/Unknown
C/S: None/Unknown


I get the following error when I am starting some of the Baan sessions.

1 : process 6 - Error : SQLState QP999: Corrupted data dictionary (error 512) ( in object ottstpstandard)
2 : process 6 - Fatal error : Error 512 (Corrupted data dictionary) on select
3 : process 6 - Fatal error : Can not continue in tdext8566m000 in DLL: ottstpstandard ([retry.point]

I did convert runtime DD and also tried with create RuntimeDD for all the tables... but no use.

any suggestions to avoid this error?

Reply With Quote
Old 29th June 2007, 21:17
rduncan10's Avatar
rduncan10 rduncan10 is offline
Senior Member
Join Date: Feb 2007
Location: Cambridge, ON Canada
Posts: 117
rduncan10 is on a distinguished road
Baan: IVc4 - DB: Oracle 10g - OS: SUSE Linux
Did you select "Reconfigure table" when you created the runtime DD?

Did you look in the logs ($BSE/log)? We got this error a lot when upgrading Baan recently and the logs often had more specific messages for this error (log.ba6.1, log.bshell, and the database logs). They might point you to the table that is causing the error.
Reply With Quote
Old 29th June 2007, 22:18
kbabu1's Avatar
kbabu1 kbabu1 is offline
Join Date: Sep 2003
Location: India, Mumbai
Posts: 46
kbabu1 is on a distinguished road
Baan: Baan 4 and 5, Infor ERP LN - DB: Oracle, SQL Server - OS: Windos 2000, Unix
Yes, I did.
Reply With Quote
Sponsored Links
Old 30th June 2007, 13:53
yashwant yashwant is offline
Join Date: Jul 2004
Location: Bangalore,India
Posts: 72
yashwant is on a distinguished road
Baan: iv - DB: oracle - OS: win98
check ttadv500-504 tables .delete all the will work.
Reply With Quote
Old 1st July 2007, 11:34
csecgn's Avatar
csecgn csecgn is offline
Join Date: Aug 2004
Location: Cologne/Germany
Posts: 300
csecgn is on a distinguished road
Baan: IVc4 SP14 (Tools SP 21) ; LN 6.1 (Testing) - DB: Oracle - OS: Solaris
Could you identify the corrupted table?

If you want to know how much time the repair wil need, you can check the baan DD against the table structure in the database. If there is no difference, you only have a problem with references. In this case there will be no reconfigure happen. If yes you can modify the table structure in the database so it is identical to the baan structure -> no reconfigue will happen. Or you don't change it and let baan do the job.

The next steps to solve such problems are equal in both cases:

1. first check the tables ttadv500 to ttadv504 in company 000, They should be empty. If not, yo have had some old incorrect reconfigures. You have to clear this first.

2. set the corrupted table to expired. Press save. Remove the expired. Save again.

Now you should see your and all referenced tables in ttadv502 (and your table is not expired).

Convert to runtime all tables/packages/modules incl. reconfigure.

Log out and log in again.


Reply With Quote
Old 2nd July 2007, 14:34
toolswizard toolswizard is offline
Senior Member
Join Date: Aug 2001
Location: USA
Posts: 292
toolswizard is on a distinguished road
Baan: 4c4, 50b, 50c, ERP ln - DB: Informix, Oracle, Sql - OS: Unix, NT, AIX
I have run across this several times in the last 6 months at various customers. To speed up the Convert to Runtime Process, certain checks have been removed. If you have not created ALL the tables for you package combination, and a patch gets loaded with table changes, the reconfigure program will try to reconfigure them, and usually will abort because the table does not exist. An attempt to create the table, will create it with the new table definition, but reconfigure still expects to see the old table. You need to view the table within the administrative tools to see the physical structure, and then make the datadictionary in Baan match. If a field has been added, then you can delete the field in the database also. Which ever is easier. It will be created during reconfigure again.

This is only one possibility, that started with FP2. As a rule, I tell my customers to make sure all tables are created even if they are not used, and to run create tables before any Convert to Runtime where you will be reconfiguring tables, or before applying any patches. None of them have had a problem since.
Reply With Quote
Old 16th January 2017, 17:30
JackDRip2006 JackDRip2006 is offline
Junior Member
Join Date: Oct 2006
Posts: 6
JackDRip2006 is on a distinguished road
Baan: SSA Ln 6.1 - DB: Oracle 11g 64bit - OS: AIX 6.1
Hi toolswizard What particular sessions should i be running? And in what sequence? Thanks in advance.
Reply With Quote

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
ERPJewels Hitesh Shah Third Party Products 10 6th November 2006 06:38
Difference between application data dictionary and runtime data dictionary? jack786 Tools Development 3 21st August 2004 03:04
Error 512 (corrupted data dictionary) springgirl Tools Administration & Installation 2 1st March 2004 13:45

All times are GMT +2. The time now is 11:12.

©2001-2018 - -