logo  
Google
 

DB2 SQL-Error: -571

SQLState: 25000

Short Description: THE STATEMENT WOULD RESULT IN A MULTIPLE SITE UPDATE

This SQLCODE is issued in the following situations: v When an application program operating in an IMS or CICS environment attempts to modify data at a remote location where multi-site update capabilities are not supported. v When an application program has explicit SQL statements within a commit scope that would result in updates at multiple sites where one of the sites at which data is being updated does not support multi-site update. This SQLCODE can be issued when an application program explicitly modifies data at a single location within a commit scope. This can occur in the following situations: v A package or plan associated with the application program was invalidated. v A package or plan was bound at one release of DB2 and fallback occurs to a prior release. In the situations described above, an implicit autobind is done on behalf of the user. An autobind results in the DB2 catalog being updated. The conditions that must exist for this SQLCODE to be issued when an autobind occurs are: v One site where data has been modified does not support multi-site update. v The autobind occurs at a separate and distinct site from where an application program explicitly modifies data. v At the time of the autobind, locks are being held to process an SQL statement within the application program.System action: The statement cannot be executed. Programmer response: v Ensure that all requests for modifications to the data are confined to a single location within any given commit scope for any application that references a location that does not support multi-site update. v For programs operating in an IMS or CICS environment where the remote database systems do not support multi-site update, all SQL statements must be read-only access. v If an autobind is causing this SQLCODE to be issued, REBIND the plan or package.

 <-  BACK TO INDEX