Re: Schema Change Error
From: Robert Klemme (bob.news_at_gmx.net)
Date: 11/19/04
- Next message: Joe Weinstein: "Re: Schema Change Error"
- Previous message: rahulkav: "Schema Change Error"
- In reply to: rahulkav: "Schema Change Error"
- Next in thread: Joe Weinstein: "Re: Schema Change Error"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 19 Nov 2004 15:32:01 +0100
"rahulkav" <rahulkav@discussions.microsoft.com> schrieb im Newsbeitrag
news:F331C7F1-E196-445B-AE0B-2D33FEDC4AC3@microsoft.com...
> Hi,
>
> We are getting following Exception in our Java application:
>
> ====================================================
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
> JDBC][SQLServer]Could not complete cursor operation because the table
schema
> changed after the cursor was declared.
> at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown
Source)
> at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
> at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
> Source)
> at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
> Source)
> at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
> Source)
> at com.microsoft.jdbc.sqlserver.tds.TDSRequest.getRow(Unknown Source)
> at com.microsoft.jdbc.sqlserver.tds.TDSCursorRequest.getRow(Unknown
Source)
> at
>
com.microsoft.jdbc.sqlserver.SQLServerImplResultSetServerSideCursor.positi
onCursor(Unknown Source)
> at com.microsoft.jdbc.base.BaseResultSet.next(Unknown Source)
>
> ---------------------------------------------------------------------
>
> We have a Java application which is running for 24 hours and we have
> implemented our own connection pooling. We are connected to SQL Server
2000
> with Serverice pack 3 installed.
>
> We get the above error when there is a schema change i.e. Creating a new
> table, Dropping an existing table. This schema change is done by a
stored
> procedure which is run in parallel with our Java application.
> We have restared our application but sometimes it doesn't make any
> difference. The tables created and droped are in tempDB.
>
> This error doesn't occur regularly and all environments. It seems to be
an
> intermittent error i.e. some bug in SQL Server.
I'd rather suspect it's an error in your application logic: you change
something concurrently that your cursor relies on. You need some kind of
mutual exclusion mechanism. Also, make sure you have closed all
statements and result sets when you return a connection to the pool.
Regards
robert
- Next message: Joe Weinstein: "Re: Schema Change Error"
- Previous message: rahulkav: "Schema Change Error"
- In reply to: rahulkav: "Schema Change Error"
- Next in thread: Joe Weinstein: "Re: Schema Change Error"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|