Hi All,

Long back, We have customised "Purchase Register" print session, for that, we have added two indices in tfgld410.

Recently, we have upgraded SP's and localisation, results, two indices are removed, and our "Purchase Register" is stopped.

I can add, that two indices again, but my worry is - the table size is too big now and 7 companies, earlier it was small, it may take long time, which we cannot afford down time.

Is there any alternate of "Reconfigure Table" so that we can avoid down time?

Regards,

-Suhas

Yes, there is a way. I've never done it by myself, but our database freaks using the way:

Very First: BE SURE YOUR BACKUP (database and Baan complete) IS OK!!!

1) Add the indices in Oracle (with Oracle tools) and reconfigure the table
2) Add the indices in Baan
3) Convert the baan table to Runtime DD without reconfigure!!
4) Move the DD.new file(s) by yourself to the DD.old file(s) and keep backups of the files.
5) Remove the reconfiguration Indicators in the ttaadxxx tables (500, 501, 502 or 503. Actually I don't know, but this are the tables I ever check before reconfigure)

Normaly it works fine.

Hope, I didn't forget a step

If you try it, it is at your own risk.

Regards
csecgn

Suhas,

Looks like your SQL Server... If you're level 2, then you can probably use the same method as csecgn does in oracle.. But if you're level 1
then you need to generate the hash columns, which means that the
only option is a reconfig.

Dave

Wouldn't a reconfig had to have been done at the time of the upgrade in order to lose the 2 indices? Are they really gone?

If reorging a single table takes too long, I would say you have more than that to worry about. But to stick to the issue at hand, there is another method of speeding up the process.

Dump all your data from the table using SQLPlus. Delete the table with everything in it. Create it again after making your changes to the DD and (again using SQLPlus) reload your data.

This is essentially the same process that a Baan reconfig does, but it will safe you roughly half the time.

Oops, I saw "Win2k" and thought SQL2k.. so I think the "alter table method" is the best. That's what Baan now does for Baan 5, and there's no reason (for a simple index) that you can't do it that way.

Dave

Thanks for the prompt replies.

csecgn,
Right now, I am working on your reply on our dev server by forcefully dropping and creating indexes. And Yes, I know all that reconfig info. tables.

naabi0,
I am sure, they are gone?

Francesco,
Your thinking is right, single table should not take that much time, but it is tfgld410 with 7 companies with billions of records. And Definitely our database is healthy.
Our database is multiplex archived, reloading data generates lot of arc files, I am thinking to avoid it. I am just curious, will reference allow to delete that table? Yes, I am agree, database import will take half of time compare to BaaN.

Dave,
Altering table/index, is not that much easy,it has to specify tablespaces.

Regards,

-Suhas

Ok, how about this then:

(assuming you have tfgld410 setup in your ora_storage (ora_storage_param) file modify the table def in Baan.
convert to runtime w/o reconfigure table option.
move the .new in place

create a script
notepad gc1.txt
#1 tfgld410 TCRI <index number> -p 0

gcommand gc1.txt <company number>

Dave