after changing porting set i'm not able to access table ttadv304,ttadv364 ,its giving error 512


when i'm changing the bin to old bin i'm able to access those tables

can anyone tell me why this is happening and how can i resolve this issue

thanks in advance

Mithun

Dear Mithun,

This is what error 512 is according to BaanERP programmer reference

512 EDDCORRUPT This indicates a corrupt data dictionary. You can use the bdbpre and bdbpost tools to repair it.

You may want to try to create data dictionary again for these tables

Rgds,
Paul

Take a backup first. Then you could try ttadv5213m000 (Create Runtime Data Dictionary for Tools) with reconfigure tables checked and/or create a sequential dump of the tables (ttaad4226m000) and then import them (ttaad4227m000).

The tables ttadv304, ttadv335, ttadv364 have a field " layo" which store binary data

check solution nr. 1955

best way to export with old port , import with new port.-set

Hi,

Paul,

You say in your reply:

"You can use the bdbpre and bdbpost tools to repair it."

If I use bdbpre/bdbpost in a situation like this, won't I get the same error 512 problem? either on export or import?

New driver, old constraints.

Add the line [ora_column_format:7] (without the brackets) to your db_resource file and all your problems will be solved.

Well, this one anyway.

You are right:
Has to do with this restriction of Oracle7: string values may only be xxx long. So the DBdriver created two records for one text field internally. Because the DBdriver is aware, you will not know within Baan.

Now Oracle8 does not have this restriction anymore, so the text field may be of xxx+ length. And the DBdriver assumes it is working with Oracle8. But since you did not migrate your data (not adding txt.part1+txt.part2 into txt.whole), you will need to tell you work with a non converted database using the above setting.

Mithun,

Take a look at this thread: -

http://www.baanboard.com/baanboard/showthread.php?s=&threadid=7299&highlight=512


Regards

PJ