My guess is you've got corruption in one of the indexes... With that
option selected, it uses an ORDER BY on the primary key column(s).
DBVALID that database at your next convenience.
Paul Horan[TeamSybase]
"Doug Stone" <nospamdougstoneatres-qdotcom> wrote
Quote:
One of our customers was reporting various problems with our application.
I decided to unload and reload their database.
dbunload using "primary key order" generated an assertion 100305 error.
However, when I un-selected "primary key order" the unload (and subsequent
reload) proceeded without error
What was the impact of de-selecting the "primary key order" default?
Thank you
Doug |