DBMS Table Error

[TrunkMan]

I have a system with 1 DBMS table error and tried doing a DBMS check full and DBMS save and still not cleared he error. Im trying to avoid doing a restore to clear the fault as I believe that its a bit extreme. Ive been reading the software and error logs and have come up with this :

The bad record is in the forwarding info table in record number 844. If I do the DBTAB command, I get the following info :

sws_fwding_info [ 844 ] =
0A 0B 0C 0D 0E 0F 00 01 02 03 04 05 06 07 08
09
02C81C4A: D3 00 00 BD 00 00 00 00 00 00 00 00 00 00 00 00
02C81C5A: 00 00 00 00

I do know how to read the hex values and convert them to decimal, but I need to know how to take the above info and relate it to the record I need to delete. Can anybody shed any light on this or how to use the DBTAB command effectively in clearing database errors. This is my first try at trying to clear a database error without doing a data restore and any help would be much appreciated.

 

[M1tel]

You can only resolve by a Data Restore

 

[TrunkMan]

Any resoning behind this ?

 

[UncleRalph]

Your HEX translates like this:
11578966645329100816
30000000000000000000000000000

Doesn't mean anything to me but perhaps you can pull an extension number out of it.

Ralph

 

[TrunkMan]

The d3 and the b3 are the interesting bits, because if i type in dbtab <87> and <any spare record>. those bits are off. d3=211 and bd=189. Those exact bits are also generated in my software logs. I need to turn those bits off(delete in esm somehow) and that should clear the corruption

 

[kwbMitel]

Thanks for the updates.

Like watching a slow motion train wreck in the making.

I'm interested to know if the conductor survives.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[nytalkin]

Do a backup and restore.

NO GOOD DEED GOES UNPUNISHED!

 

[MitelSB]

I had the same problem, if you perform a backup and afterwards a restore, the 3300 will try to correct the error by deleting the wrong content.

There is also a command that you can enter to see what the 3300 is deleting while you perform the restore. You should check your helpfile to find out the command, because I forgot.