DBT file errors (OpenInsight Specific)
At 28 JUN 1999 11:51:53AM Peter Bowyer wrote:
We seem to be getting quite a number of errors which are showing themselves as corrupting the application DBT file. The earliest warning is that we are unable to save changes to a dictionary.
We are using OI3.4, Novell 3.12 with NLM 1.5.
I have read the thread on 64k problems, but the DBT file is only some 20k
Any ideas anyone?
At 28 JUN 1999 12:15PM Stephen Revelation wrote:
Peter,
This may be worth a shot. If your application's .dbt is indeed corrupt, try the following. Rename your application's .dbt file to application.old. Create a new file called application.dbt and then copy your sysprog.dbt and paste it back in as application.dbt. Then, start up your application and go into Database Manager. From here, add all of the tables that are missing that existed in your previous application's .dbt. Hoperfully, this will fix any problems you are experiencing.
Good Luck,
Stephen Revelation
At 28 JUN 1999 04:43PM Dave Pociu wrote:
A while ago, I had my DBT table getting corrupted weekly…
I turned out I had an MFS subroutine I brought over from AREV that was performing an OPEN statement at the very beginning. Since OI executes each MFS when it initializes ( with an init code passed in) but before the file system is there, it was screwing everything up…
After fixing that, I haven't had any DBT problems whatsoever ( past 2-3 years) running both local, on Novell or NT.
Dave Pociu
P.S. My DBT file is pretty hefty too at 50K…