We did an upgrade of the porting set from 6.2a.03.01 to 7.1d.06. The Oracle database is also upgraded to 9 from 8. But still i see the driver info in the ipc_info as oracle8.how can i make sure that i'm using the correct driver??
When i try to to the bdbpost on any table... get the error " write error(512) which is the corrupt data dictionary ". i'm trying to convert the tables from level 1 to level2 by dropping the Hash columns, taking the bdbpre of the table and then the bdbpost. it fails in the bdbpost. can u help me on this?????

Regards

There is only one Oracle driver for Oracle versions 8,9 and 10
that's listed in Baan as the oracle8 driver.

Why would you drop the hash columns and then do a bdbpre / bdbpost?

If you're going to pre/post then just do ORA_LEVEL1=1 bdbpre6.1 ....
ORA_LEVEL1=0 bdbpost6.1 ... end of conversion...

I asked you before to post your db_resource and tabledef.. I can't help you on the 512 error until you do that.

Are you getting the error on all tables? or just some?

Dave

Hi,
I'm sending the snapshot of the db_resource and the tabledef6.2 for your reference. Kindly help me and let me know what settings should be done to enable the bdbdpost option. Actually the data has some ascii character (0) in place of Null values in Oracle level. But when the dta ais getting loaded using the bdbpost option the constraint fails and the error ("cannot insert null into not null column ...") is displayed and the bdbpost fails. This is the error (512).
How should i rectify this problem????

bmp1.jpg contains the snapshot of the tabledef and
bmp2.jpg contains the snapshot of the db_resource.

Expecting an early reply,
Query1

Ok, those look ok..

why not just use the "k" option on the bdbpost then?

Dave

Baan creates all collumns with the "not null" attribute. I think in your case you have an old existing table with a column, which Baan is not aware of (maybe was some other PKG) in the past.

Now Baan tries to insert and does not give a default value for the new/unknown column. This creates your error.

If you follow Daves advise, the table will be newly created and this should be ok!