Sybase Error 8203,623,933,658
Mr. Andrew Leung
I cannot find any description in the Sybase Trouble shooting guide.
It also has an error 605 before the error 623 but after 8203.
I am using Sybase SQL Server with option :
SQL Server/10.0.1/P2/RS6000/AIX3.2/1/OPT/Tue Apr 5 03:23:49 PDT 1994
Would anyone can explain those errors to me?
Is the later error is leaded by the previous one?
How can I fix those errors?
(I cannot affort one-day data lost to load the last backup!)
How can I avoid those errors occur again?
Many thanks in advance!
+-------------------------------------------+
| Andrew Leung from HONG KONG /\__/\ |
| email : leu...@ha.org.hk \ xx / |
| Tel : (852) 515 1603 __oOO_\__/_OOo__ |
| Fax : (852) 515 0420 My life as a dog |
+-------------------------------------------+
Teresa A Larson
|> Recently, I found errors 8203, 623, 933, 658 in the errorlog file but
|> I cannot find any description in the Sybase Trouble shooting guide.
|> It also has an error 605 before the error 623 but after 8203.
|>
|> I am using Sybase SQL Server with option :
|> SQL Server/10.0.1/P2/RS6000/AIX3.2/1/OPT/Tue Apr 5 03:23:49 PDT 1994
|>
|> Would anyone can explain those errors to me?
|> Is the later error is leaded by the previous one?
|> How can I fix those errors?
|> (I cannot affort one-day data lost to load the last backup!)
|> How can I avoid those errors occur again?
A SELECT * FROM master..sysmessages shows the following (which
should have appeared in your error log):
933 22
Logical page %ld of the log encountered while retrieving highest
timestamp in database '%.*s' is not the last page of the log and we
are not currently recovering that database.
623 21
Attempt to retrieve row from page via RID failed because logical
page %ld is not a data page. %S_RID. %S_PAGE.
658 22
Last log page in database '%.*s' incorrectly identified as page %ld.
Run DBCC checktable on syslogs.
8203 26
Expected to find the descriptor in %s state.
In the System 10 Documentation, Chapter 11 of the System Administration
Guide explains the severity levels of the messages. Unfortunately,
Sybase documentation is famous/infamous for not fully documenting all
the errors. Msg 933 and 658 are severity 22, 623 is severity 21
and 8203 is Severity 26. Accordingly to the book levels 19 and above
are fatal problems.
21 indicates a SQL Server fatal error in database
processes. The book suggests that it is unlikely that the database
itself has been damaged, but you should reboot the server and run the
dbcc diagnostics.
22 is a fatal server error that indicates that table integrity is
suspect. You should reboot the server and run dbcc to determine if
other objects in the database are also damaged.
Have you noticed read/write errors from the disks in operating system
logs that might indicate a media problem? You need to determine the
source of the your problem if you can. If the disks are the problem,
you might be creating unreliable backups. dbcc fix can help you
correct allocation errors.
Good Luck,
Teresa Larson
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
| Teresa A. Larson - Hughes STX Corporation |
| NASA/GSFC Code 933.0 voice: (301) 286-7867 |
| Greenbelt, Maryland 20771 fax: (301) 286-1777 |
| Teresa...@gsfc.nasa.gov |
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
Standard disclaimer ...