Can anyone have the clue why I am getting the following error.

Loaded the table with sequential data using session "create table using sequential dump". Whem I tried to open the table using GTM, I am getting the error 16200. The database is Oracle version 8.1.

Regards
Chandra

According to my notes 16200 is a BISAM error.

Can you access the table through Oracle?

How is your tabledef6.x set up? Is it pointing to bisam or an Oracle instance? 16200 is normally a tbase error (bisam) and would normally use tbase6.1, say, to rectify it.

Thank you for your help..

Sorry, the database is Tbase for our developemnt box. Earlier I mentioned it as a Oracle. If the data definition file with .old extensin not present, then we will get 16200 error. I made another copy of table DD with .old extension and it solved my problem !!!

Hi,

We have just had the same problem. Trying to access tccom020 generated the 16200 error "Bad Registration Information"

We are using tbase.

It has been suggested that we use tbase6.1 to fix this. How exactly do we go about doing this? None of us has experience with this.

Thanks

You can see all options with command tbase6.1 R .

I think initial installations had a repair script (try `which repair`).

It is calling tbase6.1 in a for loop to check and repair all tables based upon isamdef6.1 for a certain company.

The option used to repair a table should be:
tbase6.1 B bcr
like in:
for i in t?????/t?????????.bdt
do
tbase6.1 B bcr $i
done

Dear all,

For all of you who still work with the Baan Tbase database engine (like me !), I wrote a small script to solve the 16200 error for a complete company. Basically, it is a somewhat extended version of the script part given by OmeLuuk.

In my situation, this script had to be used to re-register tables in the Tbase Registration File after a complete company had been restored from backup tape. In order to ensure that the correct UNIX-inode number of the physical table-file is registered, the tables must be re-registered in the described way in order to prevent the 16200 error from occurring.

Useage is quite simple: Simply change the paths, update the 'packages' file so that all Baan-packages are listed and run the 'reg_tables.sh' script as 'root' or 'tbase' user and this error will disappear. It may take a while to complete, especially for the larger tables, but it works !

Finally, in order to check whether all 16200 errors have been solved, run Baan tools-session ttaad4232m000.

With best regards,

Maarten
Q4U Consulting

********************************
bshell6.1> more reg_tables.sh
#!/bin/ksh
#
# Maarten Roset, Q4U Consulting
# November 2005
#
# This script re-registers all tables for a specific company in the
# Baan TBASE Registration File.
# This script is helpfull to solve 16200 errors reported when a
# company backup is restored from tape.
#
# Useage:
# 1. Log in as 'root' or 'tbase'
# 2. Fill packages file with list of Baan packages (tc, td etc.)
# each seperated by a Carriage Return/Line Feed.
# 3. Change path to packages file (see below)
# 4. Change path to company tables (see below)

for package in `cat /tmp/packages`
do
for i in `ls /baan/tables/304/t$package*/t?????????.bdt`
do
tbase6.1 B cr $i
done
done

*********************************

bshell6.1> cat packages
ba
bc
bd
bi
cc
cp
ct
da
do
nt
ps
tc
td
tf
tg
ti
tl
tm
tp
tr
ts
tt
tu
xe
xx