Error 539, SQL Server 11.0.3.2

I have a problem on an SQL Server 11.0.3.2 system running on OpenVMS.

The server was shutdown and restarted following a temp_db full event. All
seemed to be well, but some12 hours later, various functions of a client
application that use this database started to fail. The following type of
error is listed in the SQL Server error log :

00:2005/09/16 08:33:19.72 server Error: 539, Severity: 20, State: 1
00:2005/09/16 08:33:19.76 server Access methods error code 0 encountered
but run does not know how to handle it: spid = 19, dbid = 5, objectid =
669297494, curcmd = 195 (INSERT), plasterror = 0, pstat = 0x10100, p2stat =
0x41001000, pattention = 0, xact id = (2692349, 15).

Unfortunately, Sybase no longer support their products on OpenVMS so I
cannot take the suggested action of logging it with their support group.

Can anybody explain to me in more detail what this error means, whether it
is related or not to the problem with temp_db and, more importantly, what I
can do to resolve it.

Thanks and regards,

Steve Shadbolt

Dropping and re-creating a partitioned table seems to have resolved this
problem. Does this give anybody any clues as to what might have gone wrong
?

Steve.

"Steve Shadbolt" <steve.shadbolt.RemoveThis@hp.com> wrote in message
news:bDzXe.12852$Tj1.2505@news.cpqcorp.net...
>I have a problem on an SQL Server 11.0.3.2 system running on OpenVMS.
>
> The server was shutdown and restarted following a temp_db full event. All
> seemed to be well, but some12 hours later, various functions of a client
> application that use this database started to fail. The following type of
> error is listed in the SQL Server error log :
>
> 00:2005/09/16 08:33:19.72 server Error: 539, Severity: 20, State: 1
> 00:2005/09/16 08:33:19.76 server Access methods error code 0 encountered
> but run does not know how to handle it: spid = 19, dbid = 5, objectid =
> 669297494, curcmd = 195 (INSERT), plasterror = 0, pstat = 0x10100, p2stat
> = 0x41001000, pattention = 0, xact id = (2692349, 15).
>
> Unfortunately, Sybase no longer support their products on OpenVMS so I
> cannot take the suggested action of logging it with their support group.
>
> Can anybody explain to me in more detail what this error means, whether it
> is related or not to the problem with temp_db and, more importantly, what
> I can do to resolve it.
>
> Thanks and regards,
>
> Steve Shadbolt
>