SQL3783N An error was encountered while opening the copy location file. Open file error code is errcode.

Explanation

During load recovery, an error was encountered while opening the copy location file. The operating system file open return code is returned.

User response

Look at the error code in the message for more information. Correct the error, if possible, and resubmit the command.

SQL3784W Invalid data was encountered while reading from the copy location file. Failure occurred at line line-no with error type errtype.

Explanation

During load recovery, invalid data was encountered while reading from the copy location file. The line number and error type are returned. The utility waits for a response to continue.

User response

Correct the data in the copy location file and return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.

SQL3785N Load recovery for table schema.tablename at time timestamp on node node-number failed due to error sqlcode with additional information additional-info.

Explanation

A severe error occurred during load recovery. The utility stops processing.

(Note : if you are using a partitioned database server, the node number indicates which node the error occurred on. Otherwise, it is not pertinent and should be ignored.)

User response

Examine the error code in the message for more information. Take corrective action and resubmit the command.

SQL3798W An invalid value was used for parameter parameter to invoke the roll-forward recovery API to continue load recovery.

Explanation

Load recovery is in progress and one of the parameters passed in is not valid for the current state of load recovery.

User response

Correct the value in error and return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.

SQL3799W Load recovery for table schema.tablename at time timestamp on node node-number is pending due to warning sqlcode with additional information additional-info.

Explanation

A warning condition is encountered during load recovery. The utility waits for a response to continue.

(Note : if you are using a partitioned database server, the node number indicates which node the error occurred on. Otherwise, it is not pertinent and should be ignored.)

User response

Examine the error code in the message for more information. Take corrective action and return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.

SQL3802N An invalid quiesce mode quiesce-mode was encountered.

Explanation

An invalid quiesce mode was passed to the quiesce API.

User response

Resubmit the command with the correct parameters.

SQL3804N The index is invalid.

Explanation

An invalid index was encountered during the processing of a utility command.

User response

Check in the Administration Guide to determine the appropriate way to revalidate the index and resubmit the command after the condition is corrected.

SQL3805N The state of the application or of one or more table spaces for the table specified prohibits the loadapi action or quiescemode action. Reason code = reason-code.

Explanation

The loadapi action (either quiescemode or callerac) passed to the load API is in conflict with either the state of the application or the state of one or more table spaces for the table.

The possible reason codes are as follows:

01

The state of one of the table spaces for the table specified prohibits the loadapi action or quiescemode.

02

The application is not at the start of its logical unit of work. This condition prohibits the load action specified.

03

The state of the application prohibits the load action specified.

04

One or more of the table spaces for the table is already quiesced by the maximum number of quiescers.

05

The system catalog table space cannot be quiesced.

06

A LOAD command with the COPY option is not allowed when a table space is in backup pending state.

07

Attempt to restart a load at an incorrect phase.

08

Attempt to restart a load into a table whose partitioning key depends on an identity column and where not all of the table partitions are restarting from the load phase. Such a load is not allowed as hashing of rows during the restarted load may be different from the hashing in the initial load due to the dependence on the identity column.

09

The QUIESCE TABLESPACES FOR TABLE command failed because the database is in WRITE SUSPEND state.

10

Attempt to restart a load against a random distribution table using the random by generation method.

User response

The user response corresponding to the reason code is as follows:

01

Resubmit the command with the correct loadapi action or quiescemode, or correct the state of the table spaces for the table.

02

Resubmit the command with the correct load action or complete the current logical unit of work by issuing either a COMMIT or ROLLBACK.

03

Resubmit the command with the correct load action.

04

Determine which table spaces for the table have reached the maximum number of quiescers. QUIESCE RESET these table spaces.

05

Resubmit the command with a table which is not in the system catalog table space.

06

Resubmit the command omitting the copy parameter

07

Determine at which phase the load should be restarted and resubmit the command with the correct phase.

08

Terminate the load operation using the TERMINATE action then resubmit the original load command.

09

Resume I/O write operations for the database, and resubmit the QUIESCE TABLESPACES FOR TABLE command.

10

Terminate the load operation using the TERMINATE action then resubmit the original load command.

SQL3806N Not all table constraints are off for the table to be loaded.

Explanation

One or more constraints for the table to be loaded are still on when the load API is invoked.

User response

Resubmit the command after all table constraints are turned off.

SQL3807N Instance or database name quiesce is pending.

Explanation

Another user has submitted the quiesce command and it has not yet completed.

User response

Wait for the quiesce to complete.

SQL3808N Instance or database name unquiesce is pending.

Explanation

Another user has submitted the unquiesce command and it has not yet completed.

User response

Wait for the unquiesce to complete.

SQL3901N A non-severe system error occurred. Reason code reason-code.

Explanation

Processing ended because of a non-severe system error.

User response

If trace was active, invoke the Independent Trace Facility at the operating system command prompt. Then contact your technical service representative with the following information:
  • Problem description
  • SQLCODE and embedded reason code
  • SQLCA contents if possible
  • Trace file if possible.

SQL3902C A system error occurred. Further processing is not possible. Reason code = reason-code.

Explanation

A system error occurred.

User response

If trace was active, invoke the Independent Trace Facility at the operating system command prompt. Then contact your technical service representative with the following information:
  • Problem description
  • SQLCODE and embedded reason code
  • SQLCA contents if possible
  • Trace file if possible.

SQL3910I Synchronization session completed successfully.

Explanation

User response

SQL3911I Test synchronization session completed successfully.

Explanation

User response

SQL3912I STOP completed successfully.

Explanation

User response

SQL3913I STOP issued, but no synchronization session is currently active.

Explanation

User response

SQL3914I A user interrupt was issued. The synchronization session stopped successfully.

Explanation

User response

SQL3915I A user interrupt was issued before the results were uploaded to the satellite control server. The results will be uploaded during the next synchronization session.

Explanation

User response

SQL3916I A STOP request was received. Synchronization session stopped successfully.

Explanation

User response

SQL3917I A STOP request was received before the results were uploaded to the satellite control server. The results will be uploaded during the next synchronization session.

Explanation

User response

SQL3918I Synchronization progress information was obtained successfully.

Explanation

User response

SQL3919I A STOP request was received before the satellite could contact the satellite control server. Synchronization stopped successfully.

Explanation

User response

SQL3920I The application version on this satellite does not match one that is available for the group of this satellite. Synchronization cannot occur.

Explanation

The application version reported by the satellite does not exist at the satellite control server.

User response

Contact the help desk or your system administrator.

SQL3921I This satellite is disabled at the satellite control server. Synchronization cannot occur.

Explanation

When disabled, the satellite cannot synchronize.

User response

Contact the help desk or your system administrator.

SQL3930W There are no synchronization scripts to execute.

Explanation

No synchronization scripts were downloaded to the satellite for execution.

User response

Contact the help desk or your system administrator to ensure that synchronization scripts are available on the satellite control database for this satellite.

SQL3931W The test synchronization session completed successfully. The satellite ID, however, could not be found in the satellite control database.

Explanation

Either the satellite ID is not defined correctly on the satellite or this satellite has not been defined in the satellite control database.

User response

If you use the DB2SATELLITEID registry variable, ensure that it is set to the unique ID for the satellite. If you are using the operating system logon ID as the satellite ID, ensure you log on using it.

SQL3932W The test synchronization session completed successfully. The satellite application version, however, is not set locally, or does not exist for this satellite's group at the satellite control server.

Explanation

The application version on the satellite is different from any that are available for this satellite's group.

User response

Ensure that the application version on the satellite is set to the correct value.

SQL3933W The test synchronization session completed successfully. The release level of the satellite, however, is not supported by the release level of the satellite control server.

Explanation

The release level of the satellite must be within the range of one level above to two levels below that of the satellite control server.

User response

Contact the help desk or your system administrator.

SQL3934W The test synchronization session completed successfully. This satellite, however, is disabled at the satellite control server.

Explanation

The satellite has been placed in the disabled state at the satellite control server.

User response

Contact the help desk or your system administrator.

SQL3935W The test synchronization session completed successfully. This satellite, however, is in the failed state at the satellite control server.

Explanation

The satellite is in the failed state at the control server.

User response

Contact the help desk or your system administrator.

SQL3936W No progress information is available.

Explanation

The synchronization session has not reached a stage where the progress information has been logged, or there is no active synchronization session for this satellite.

User response

Ensure the synchronization session is active, or try querying for progress information later.

SQL3937W The application version for this satellite does not match one that is available for this satellite's group.

Explanation

A satellite can only synchronize with a particular application version for its group. The application version for this satellite is not available for the satellite's group at the control server.

User response

Ensure that the application version on the satellite is set to the correct value.

SQL3938W An interrupt was issued during script execution. The synchronization session was stopped, but the satellite may be in an inconsistent state.

Explanation

An interrupt was issued while the script execution phase of the synchronization process was being performed. The synchronization session was stopped but the satellite may be in an inconsistent state because a script may have been halted at an inappropriate place.

User response

Contact the help desk or your system administrator.

SQL3942I Synchronization session identifier was set successfully for the satellite.

Explanation

The session identifier was set successfully for the satellite.

User response

No action is required.

SQL3943N Synchronization session identifier exceeds the maximum length of length characters.

Explanation

The specified synchronization session identifier is longer than the allowed length of length characters.

User response

Ensure that the identifier is no more than nnn characters.

SQL3944I Synchronization session identifier was reset successfully for the satellite.

Explanation

The session identifier was reset successfully for the satellite.

User response

No action is required.

SQL3945I Synchronization session identifier for the satellite was retrieved successfully.

Explanation

The session identifier for this satellite was found and returned successfully.

User response

No action is required.

SQL3946N Synchronization session identifier operation failed.

Explanation

The synchronization session identifier operation has failed for an unknown reason.

User response

Ensure that the product is installed correctly. If the failure persists, contact DB2 service.

SQL3950N A synchronization session is active. At most one synchronization session can be active.

Explanation

Only one synchronization session can be active at a time.

User response

Wait until the current synchronization session completes successfully before initiating another session.

SQL3951N The satellite ID cannot be found locally.

Explanation

Either the operating system logon was bypassed or the DB2SATELLITEID registry variable was not set.

User response

If you are using the operating system logon ID as the satellite ID, log on to the operating system. If you use the DB2SATELLITEID registry variable, ensure that it is set to the unique ID for the satellite.

SQL3952N The satellite ID cannot be found at the satellite control server.

Explanation

Either the satellite ID is not defined correctly on this satellite or this satellite has not been defined at the satellite control server.

User response

If you use the DB2SATELLITEID registry variable, ensure that it is set to the unique ID for the satellite. If you are using the operating system logon ID as the satellite ID, ensure you log on using it. Otherwise, contact the help desk or your system administrator.

SQL3953N This satellite has been disabled at the satellite control server.

Explanation

The satellite ID has been disabled at the satellite control server.

User response

Contact the help desk or your system administrator.

SQL3954N This satellite is in the failed state at the satellite control server.

Explanation

The satellite is in the failed state because a previous synchronization session failed.

User response

Contact the help desk or your system administrator.

SQL3955N The satellite control database name or its alias could not be found.

Explanation

The satellite control database is not cataloged correctly.

User response

Contact the help desk or you system administrator.

SQL3956N The application version for this satellite is not defined locally.

Explanation

The application version is not defined locally on this satellite or is not defined correctly.

User response

Ensure that the application version is set to the correct value.

SQL3957N Cannot connect to the satellite control database because of a communication failure: SQLCODE=sqlcode, SQLSTATES=sqlstate, Tokens =token1, token2, token3.

Explanation

An error has been detected by the communication subsystem. Refer to sqlcode for more details.

User response

Contact the help desk or your system administrator.

SQL3958N Error occurred during synchronization session: SQLCODE=sqlcode, SQLSTATES=sqlstate, Tokens =token1, token2, token3.

Explanation

An unknown error has been detected by the communication subsystem. Refer to sqlcode for more details.

User response

Contact the help desk or your system administrator.

SQL3959N Synchronization session cannot start because of a communication failure: SQLCODE=sqlcode, SQLSTATES=sqlstate, Tokens =token1, token2, token3.

Explanation

An error has been detected by the communication subsystem. Refer to sqlcode for more details.

User response

Contact the help desk or your system administrator.

SQL3960N Cannot upload results to the satellite control server because of a communication failure: SQLCODE=sqlcode, SQLSTATES=sqlstate, Tokens =token1, token2, token3.

Explanation

An error has been detected by the communication subsystem. Refer to sqlcode for more details.

User response

Contact the help desk or your system administrator.

SQL3961N Cannot authenticate with the satellite control server.

Explanation

An authentication error was detected while trying to connect to the satellite control database.

User response

Either the remote administrative user ID or the password required to connect to the satellite control database was not correct, or both. Either provide the correct user ID and password, or contact the help desk or your system administrator.

SQL3962N Synchronization could not be started because of a database error: SQLCODE=sqlcode, SQLSTATES=sqlstate, Tokens =token1, token2, token3.

Explanation

An error preventing synchronization occurred at the satellite control server.

User response

Attempt to synchronize again. If failure persists, contact the help desk or your system administrator.

SQL3963N Results cannot be uploaded because of a database error: SQLCODE=sqlcode, SQLSTATES=sqlstate, Tokens =token1, token2, token3.

Explanation

An error occurred while uploading results to the satellite control server.

User response

Contact the help desk or your system administrator.

SQL3964N Synchronization failed because the release level of the satellite is not supported by the satellite control server.

Explanation

The release level of the satellite must be within the range of one level above to two levels below that of the satellite control server.

User response

Contact the help desk or your system administrator.

SQL3965N Cannot download synchronization scripts because of a satellite control server failure: SQLCODE=sqlcode, SQLSTATES=sqlstate, Tokens =token1, token2, token3.

Explanation

The satellite cannot download the scripts that are required to synchronize the satellite. One possible reason for this failure is that the control server cannot instantiate parameterized scripts with the attributes of the satellite. Another reason is that the satellite control server was temporarily unable to complete the request because of resource constraints.

User response

Try the request again. If the failure persists, contact the help desk or your system administrator.

SQL3966N Synchronization session failed. Reason code reason-code.

Explanation

The synchronization session failed to complete for one of the following reasons:
  • (01) Missing authentication information.
  • (02) Some scripts required for synchronization are missing.
  • (03) System files are corrupted or missing.
  • (04) A system error prevented scripts from executing.

User response

Try the request again. If failure persists, contact the help desk or your system administrator.

SQL3967N Progress information cannot be retrieved.

Explanation

Progress on this satellite's synchronization session cannot be retrieved. Either the data is corrupt, or it does not exist.

User response

If a synchronization session is active and no progress information is available, contact the help desk or your system administrator.

SQL3968N Synchronization failed to complete successfully because of a script failure. The results, however, were successfully sent to the satellite control server.

Explanation

One of the synchronization scripts failed during execution. Either a return code was not in the defined success code set, or the script failed to execute.

User response

Contact the help desk or your system administrator.

SQL3969N Synchronization failed because an interrupt was received during script execution.

Explanation

Script execution fails when an interrupt is received. An abnormal termination of this type will cause the synchronization session to fail because the system may be in an inconsistent state.

User response

Contact the help desk or your system administrator.

SQL3970N Synchronization session failed: SQLCODE sqlcode, SQLSTATE sqlatate. The error was detected at the location location.

Explanation

Script execution failed because of an unknown error.

User response

Contact the help desk or your system administrator.