Fatal Error 803 
Author Message
 Fatal Error 803

I have a single application inserting records into a table via RDO1.0b &
VB4.0a. The server is NT 4.0 SP2 & SQL 6.5 SP2. After about a dozen inserts
I am getting :

[Microsoft][ODBC SQL Server Driver][SQL Server]WARNING - Fatal Error 803
occurred at March 3, 1997 1:14PM. Please note the error and time, and
contact your System Administrator.

I have contacted myself and I don't know what the problem is<g>.

The database has room and the log is not full. I've run dbcc checkdb(),
newalloc(), checkcatalog() and they don't report errors. Rebooting the
server hasn't helped. Has anyone experienced this before or have any
suggestions?

Thanks,
John

PS - According to Administrator's Companion : Error 803 -
Unable to place buffer 0x%lx holding logical page %ld in sdes for object
'%.*s' - either there is no room in sdes or buffer already in requested
slot.



Fri, 20 Aug 1999 03:00:00 GMT
 Fatal Error 803

Neil,

 Thanks for the reply. Unfortunately I think it will be hard to reproduce.
I did several thousand inserts Friday with no problem, the problem only
cropped up Monday ( a few days before scheduled production use I might add)
and now I can no longer do inserts.

A smaller percentage of the time I do not get a 803 error but a message
stating my process is deadlocked and has been selected for termination. I
find this hard to believe since only 1 instance of a single application is
connected to the server and it is using 1 ODBC connection to boot.

Do you think I should switch back to SP1?

John

Quote:
> John,

>  Definitely a SQL bug.  Q153455 describes the only outstanding documented
803
> bug not fixed in 6.5 SP2, so yours is probably a new one.  Can you
re-create
> the problem with the same tables and an ISQL script?  This makes it much
easier
> to reproduce.  

>  At the end of the day you will need a reproduction script to pass to MS
to
> resolve this one.



Sat, 21 Aug 1999 03:00:00 GMT
 Fatal Error 803

Quote:
> Well I dropped back to 'SP0' i.e. SQL 6.5 with no SP's. Now I am getting
> Fatal Error 2610 - Could not find leaf row in non-clustered index. I am
> going to try dropping & recreating all indexes and then apply SP1.

John,

Good luck.  I recommend calling MS PSS for their advice on which level of
software to go with.  As both the errors are SQL bugs you won't be charged.


 Protech Computing Ltd (MS Solution Provider)
 Using Virtual Access 3.52 build 159c (32-bit) on NT 4.0 SP2



Sat, 21 Aug 1999 03:00:00 GMT
 Fatal Error 803

Neil,

Well I dropped back to 'SP0' i.e. SQL 6.5 with no SP's. Now I am getting
Fatal Error 2610 - Could not find leaf row in non-clustered index. I am
going to try dropping & recreating all indexes and then apply SP1.

John



Sat, 21 Aug 1999 03:00:00 GMT
 Fatal Error 803

Neil,

Neil

Quote:
> Good luck.  I recommend calling MS PSS for their advice on which level of
> software to go with.  As both the errors are SQL bugs you won't be
charged.

Well dropping the indexes didn't work and neither did applying SP1. I also
tried using SELECT INTO another table, dropping the old table and renaming
the new table. Still got the error. I decided at that point to just
reinstall everything, NT server and SQL. I'm now running NT40 SP1 & SQL
6.5SP1 and I restored old backup of the database. Hopefully this doesn't
crop up again.

John



Sun, 22 Aug 1999 03:00:00 GMT
 Fatal Error 803

Eugne,

Quote:
> probably is a bug in SP2 because is doen't happen in SP1.
> A work around for this problem can be the following:
> You probably defined a text column in you table and filled it with text.

Well here's some unsettling news, the table in question does not use text
columns! I have reinstalled server, with NT SP1 & SQL6.5 SP1 ands will
stick with that. I have restored an old backup of the data. Luckily this
didn't happen in production. Hopefully it doesn't happen again.

John



Sun, 22 Aug 1999 03:00:00 GMT
 
 [ 6 post ] 

 Relevant Pages 

1. Locking up or Error 803 in mass conversion of database

2. SQL Server Error 803

3. Severe Error 803

4. SQL error message -803

5. 803 error

6. Oninit Fatal error oninit: Fatal error in initialising ASF wi

7. VB5 / Oracle 803, Microsoft driver for Oracle 2.73

8. imp 803=>805

9. US-803-SR.ORACLE APPS FUNCTIONAL PM

10. Migrate databases from 803 NW to 805 NT

11. OCI 803 problems

12. JDBC - Help! 803 Host cannot be found


 
Powered by phpBB® Forum Software