I'm getting the error of 'System Table Inconsistency #17 - Recovering'
during the startup of D3 on an AIX box. It is right after the Locking
ABS ...Flush process started (pid xxxx). It is followed by the message
'Diagnostics.. successfully completed and 'Activating Processes'. Any
one have an idea what to look for. I have completed a restore and
haven't noted any other errors.

During system coldstart, at some point, the system verifies some tables of
addresses by comparing the contents of frame 1 with the a saved version in
frame 12. A little like windows does to check if a coldstart follows a
shutdown or not.

IIRC, #17 was checking abs base the difference between where ABS starts and
where the system THINKS it should start. You might consider changing your
COLDSTART proc to include the command SET-ABS DM,ABS, if it isn't there
already.

If it's not a big deal, I'd restore again. If it is, I'd ignore it until
the next time you can restore, as the system seems to eventually clear
itself and continue running.

Mark Brown

<pickd3 (AT) mchsi (DOT) com> wrote

This particular error is very well known to Raining Data Support. I
believe most D3 AIX sites are on current support agreements -
companies generally don't pay a lot of money for hardware and an OS
and then drop support for your DBMS. So if indeed you're on support I
recommend you call or email RD Support, just in case. It won't cost
you anything but some time. If there has been a rash of these errors
for your specific patch release, RD should know about each instance so
that they can find the root cause and get it fixed. The more people
rely on public support for issues at this level, the more we tend to
see issues at this level because the people responsible for fixing the
problems don't get the opportunity to hear about them. I hope that
makes sense.

Good luck.
T

"Mark Brown" wrote: