Hi,
i always have a fatal error code 601 ( reference table locked ) when i run a processing on BAAN. I can have this error on all tables of my company.

All locked application are removed.

Help me please

Error 601 can be due to bugs within the session and the Baan knowledgebase contains several solutions that have been created as a result of error 601.

I would check for any available patches for the process you are running.

Regards
Neal Matthews
Intier Automotive

Get also more information from Baan Support about

1. dbsinit:021

For pessimistic or optimistic approach.

2. ora_timeout:{9999,999,999,999,999}

(these are our settings)

i have take the parameters of this files.

So the problem is resolved .

Thanks a lot for help

A lot of fans, like me, did not understand exactely what wou have done. We understood the problems that you had. Please have a description of the way you solved the problem, because this may be useful for many others who may have had the same problem. Or... maybe they will have the problem in the future and they will search through these postings for help.

So, what were the old settings in db_resource? What did you change? Is it OK now?

Regards,

i have installed baanIV c4 and oracle8 on the new server.

And i have seen that in the db_resource file, the variable

dbinit was not present.

So, i simply append in the file
dbinit:021

the presence of this variable inthe file is mandatory.

Things are not exactely so simple. You may read the document "Oracle Database driver internals" and get more information.

dbsinit is not mandatory. What I suggested is a very loose policy. The settings in db_resource are not really independent, you need to corellate them. For example:

dbsinit
lock_retry
ora_timeout

It depends from site to site how you set all these variables. For example, we use

lock_retry:0

But this is not a general rule for everybody.
I remember that there was a porting set which said that we should set dbsinit to 01. (I think it was 6.1c.05.02, not sure). Anyway, now we have PS 6.1c.06.02.

I am glad that it works fine now.