logo  
Google
 

DB2 SQL-Error: -110

SQLState: 42961

Short Description: C THE LOCATION NAME DOES NOT MATCH THE CURRENT SERVER

A 3-part SQL procedure name was provided for one of the following SQL statements: ASSOCIATE LOCATORS CALL DESCRIBE PROCEDURE The first part of the SQL procedure name, which specifies the location where the stored procedure resides, did not match the value of the SQL CURRENT SERVER special register. System action: The statement cannot be executed. Programmer response: Take one of these actions to resolve the mismatch: v Change the location qualifier to match the CURRENT SERVER special register. v Issue an SQL CONNECT to the location where the stored procedure resides before issuing the SQL statement. Ensure that the SQL CALL statement is issued before the ASSOCIATE LOCATORS or DESCRIBE PROCEDURE. v Bind the package containing the 3-part SQL procedure name with the BIND option DBPROTOCOL(DRDA). With this option, DB2 implicitly uses the DRDA protocol for remote access to the stored procedure. v Correct the statements so that the exact syntax used to specify the procedure name on the CALL statement be the same as that on the ASSOCIATE LOCATOR and/or DESCRIBE PROCEDURE. If an unqualified name is used to CALL the procedure, the 1-part name must also be used on the other statements. If the CALL statement is made with a 3-part name, and the current server is the same as the location in the 3-part name, the ASSOCIATE LOCATOR or DESCRIBE procedure can omit the location.

 <-  BACK TO INDEX