Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  DB2  [ 1000 result(s) ]
IBM DB2 
00D94001 and message DSNV086E. Standard DB2 diagnostic information is recorded in SYS1.LOGREC. An 04  -  IBM DB2
1. Run the print log map (DSNJU004) utility to print the content of both BSDSs. 2. Print SYS1.LOGREC. 3. Use the MVS DISPLAY DUMP command to get the failure reason code from dump titles. 4. Notify your system programmer. Obtain a copy of the SYS1.LOGREC and the SVC dump for the original error. Refer to the recovery scenarios in Part 4 (Volume 1) of DB2 Administration Guide before restarting. To restart DB2, you must do one of the following: v Add the missing archive log data sets back to the BSDS with the change log inventory (DSNJU003) utility and increase the MAXARCH parameter in the DSN6LOGP member of DSNZPARM to complete the rollback, or v Restart DB2 with a conditional restart specifying BACKOUT=NO to bypass the unit of recovery that is in-abort. At the time of the abend, registers 3 and 4 contain the 6-byte relative byte address (RBA) of the beginning of this unit of recovery. DB2 must read the log back to this point to complete the ROLLBACK of this unit of recovery.
Comments
 
00F3009C  -  IBM DB2
An RRS syncpoint exit was invoked for a DB2 agent by a task different than the task currently associated with the DB2 agent and the DB2 early code module installed on the system does not support this function. ; The RRS syncpoint request is abended. This will result in DB2 losing it’s connection with RRS. The DB2 subsystem must be stopped and then started again in order to establish a new connection with RRS.
Notify the system programmer. The version of the DB2 early code that was loaded from the LINKLIST library does not support RRS syncpoints initiated from a task that is not connected to the DB2 agent associated with the RRS unit of recovery for which syncpoint processing is being initiated. The DB2 early code must either be the DB2 V5 with APAR PQ16273 applied or the DB2 V6 early code. Make sure a compatible version of the DB2 early code will be loaded and then re-ipl the system. An entry recording this condition is written in SYS1.LOGREC.
Comments
 
00F70003  -  IBM DB2
The DB2 subsystem parameters specified that data sharing should be active. DB2 startup checking failed for either of two reasons: v The group and member names contained in the subsystem parameters are not equal to the group and member names contained in the DB2 ssnmMSTR JCL start procedure, or v The DB2 member is already active on another MVS system.; DB2 terminates.
Make sure the correct subsystem parameter load module name was specified for the DB2 that failed to start. Restart DB2 with the correct subsystem parameter name. Make sure the subsystem parameter name specified is the correct one for the DB2 subsystem and is not for a different member or group. You cannot share subsystem parameters among the members of a data sharing group. Make sure the group and member names specified in the subsystem parameters are equal to the group and member names contained in the DB2 ssnmMSTR JCL start procedure. If you suspect an error in DB2, refer to Part 2 of DB2 Diagnosis Guide and Reference for information on identifying and reporting the problem. This code is issued by the following CSECT: DSN7SINI
Comments
 
00D44031  -  IBM DB2
The DB2-DL/I batch support cannot continue because a connection could not be established to the DB2 subsystem named in the DDITV02 SYSIN data set. This error usually occurs for one of these reasons: v The DB2 subsystem name specified either in the DDITV02 SYSIN data set (default) or in the member defined by the IMSID-SSM combination is incorrect. v The DB2 system is not operational. This abend reason code is issued by the following CSECT: DSNMTV03 ; The DB2-DL/I batch support cannot continue and processing is terminated. User Response: Notify the system programmer.
It might be necessary to start the DB2 subsystem specified. Either correct the DDITV02 DD SYSIN or the member pointed to by the IMSID-SSM combination for the DB2 subsystem name if it is incorrect, and rerun the job. Otherwise, have the operator start the DB2 subsystem if it is stopped. Either check the DDITV02 DD SYSIN or the member pointed to by the IMSID-SSM combination for the proper DB2 subsystem name. Make sure the correct data set name is specified by the DDITV02 DD statement and the DCB RECFM is F or FB for the data set. The WAL control block in the dump contains information about the connection and the IMS attach trace table. Field WALSSID indicates the name of the DB2 subsystem being called. The last entry in the trace table has an ID of ID00 and the CALL STATUS contains the 2-byte return code and 4-byte reason code of the failure. The 4-byte reason code might provide additional diagnostic information to help determine the cause of the failure. If you suspect an error in DB2
Comments
 
00D30021  -  IBM DB2
The processing of the CONNECT statement at a DB2 remote server has failed. This is because acceptable CONNECT information was not conveyed in the distributed relational database architecture (DRDA) ACCRDB command sent by the local DB2 to the remote server. This reason code is issued by the following CSECT: DSNLTACC ; The remote server database access agent (DBAA) sends a DRDA reply message (for example, VALNSPRM) to the local DB2 which indicates the specific nature of the problem. The above reason code is sent in the server diagnosis area of the reply message. The DBAA awaits further DRDA commands from the local DB2.
The SQLCA returned in response to the CONNECT statement indicates what DRDA reply message was sent by the remote server. The user should contact the local DB2 system administrator with this information. ; Operator will not detect this problem. ; If you suspect an error in DB2, refer to Part 2 of DB2 Diagnosis Guide and Reference for information on identifying and reporting the problem. ; This represents a DRDA configuration mismatch between the local DB2 and the remote server. The precise mismatch is determined from the reply message sent from the DB2 remote server to the local DB2. The reply message may be determined by examining the SQLCODE and the SQLCA tokens returned for the CONNECT statement. It could indicate any one of the following problems (but is not limited to these): v The EXCSAT command was not successfully processed prior to receipt of the ACCRDB command. v The TYPDEFNAM parameter (specifies local DB2 data types) in the ACCRDB command is not supported. v The TYPDEFOVR
Comments
 
00C20203  -  IBM DB2
DB2 cannot connect to a group buffer pool. The group buffer pool is not usable by this release of DB2. This DB2 subsystem is a member of a data sharing group containing DB2 members of different release levels. A later release level of DB2 specified an option for this group buffer pool that is not supported by the previous DB2 releases. The presence of this option makes the group buffer pool inaccessible to the previous DB2 releases. ; DB2 takes the following actions: v Unless already issued, message DSNB301E is sent to the console with this reason code to indicate that a connect failure occurred. v SQLCODE -904 (resource not available) is returned to the user with this reason code. The resource type and resource name are also returned.
Contact the system programmer. ; Do one of the following: v Issue the -ALTER GROUPBUFFERPOOL command from a DB2 that is at the later release level to remove the new option so that previous release levels of DB2 can access the group buffer pool. v Migrate the previous release levels to the current release.; This reason code is issued by the following CSECT: DSNB1GC0
Comments
 
00D30020  -  IBM DB2
The processing of the CONNECT statement at a remote server has failed. This is because acceptable CONNECT information was not conveyed in the distributed relational database architecture (DRDA) EXCSAT command sent by the local DB2 to the remote server. This reason code is issued by the following CSECT: DSNLTEXC ; The remote server database access agent (DBAA) sends a DRDA reply message (for example, MGRLVLRM) to the local DB2 which indicates the specific nature of the problem. The above reason code is sent in the server diagnosis area of the reply message. The DBAA awaits further DRDA commands from the local DB2.
The SQLCA returned in response to the CONNECT statement indicates what DRDA reply message was sent by the remote server. The user should contact the local DB2 system administrator with this information. ; Operator will not detect this problem. ; If you suspect an error in DB2, refer to Part 2 of DB2 Diagnosis Guide and Reference for information on identifying and reporting the problem. ; This represents a DRDA configuration mismatch between the local DB2 and the remote server. The precise mismatch is determined from the reply message sent from the remote server to the local DB2. The reply message may be determined by examining the SQLCODE and the SQLCA tokens returned for the CONNECT statement. The remote server and local DB2 system administrators Chapter 40. X’D3......’ codes 919 should consult together to determine if this is a system configuration error, or if an internal error exists at either the local DB2 or remote server. Collect the following diagnostic items listed in App
Comments
 
00E80051  -  IBM DB2
An error was detected in the command that was used to start the DB2 subsystem. There are two conditions that can cause this error. If the -START DB2 command is in error, this abend results. Secondly, if the DB2 subsystem is not running (had never been started, or had been stopped), any DB2 command that is entered is interpreted as being a -START DB2 command. In this second case, the subsystem starts just long enough to discover that the command actually is not a -START DB2 command and then issues the abend. This abend reason code is issued by the following CSECT: DSNYSTRT ; The DB2 subsystem is terminated.
Reenter the command if it was entered in error; otherwise advise the system programmer. If you suspect an error in DB2, refer to Part 2 of DB2 Diagnosis Guide and Reference for information on identifying and reporting the problem. The recovery routine for the CSECT issuing this reason code records information in the variable recording area (VRA). This error does not cause a SYS1.LOGREC record to be written or an SVC dump to be requested. A diagnostic tool (for example, MVS SLIP) is required to get subcomponent diagnostic information. Register 9 contains the address of a 12-byte field that contains the following diagnostic information: bytes 1 through 4, the address of the buffer that contains the command used to start DB2; bytes 5 through 8, the general command processor return code; bytes 9 through 12, the IPC command processor return code, or 'FFFFFFFF' if bytes 5 through 8 contain a positive value. Collect the following diagnostic items listed in Appendix C, “Problem determination
Comments
 
00D3103C  -  IBM DB2
An attempt to allocate an LU6.2 conversation failed because the specified partner LU cannot support the LU6.2 SECURITY=SAME capability (that is, the LU6.2 Already-Verified security function). This abend reason code is issued by the following CSECT: DSNLVAAC ; The attempt to allocate an LU6.2 conversation fails, and the error is reported to the DB2 application that requested access to the distributed resource.
Notify your DB2 system programmer. ; DB2 will attempt to use SECURITY=SAME when connecting to remote database systems whose USERSECURITY column in the SYSIBM.LUNAMES table contains a value other than 'C'. In order to support the LU6.2 SECURITY=SAME function, the target DBMS must declare support for the SECURITY=SAME function. If the target DBMS is DB2, support for the SECURITY=SAME function is declared by specifying the following: 1. The DB2 VTAM APPL definition must specify SECACPT=ALREADYV at the remote DB2 subsystem. 2. The value in the USERSECURITY column of the SYSIBM.LUNAMES table at the remote DB2 subsystem must specify a value other than 'C' in the row associated with the requesting DB2 subsystem.; Collect the following diagnostic items: v The VTAM APPL definition for the remote DB2 system. v The contents of the SYSIBM.LUNAMES table.
Comments
 
00D93002  -  IBM DB2
The DB2 subsystem is terminated because an unrecoverable error was detected during must-complete processing for phase 2 of a commit-UR request for an agent that is a participant in a global transaction. This is a DB2 subsystem termination reason code. For further information, see Chapter 60, “IRLM abend codes,” on page 1341. ; Standard DB2 diagnostic information is recorded in SYS1.LOGREC, and an SVC dump is requested for the original error before DB2 subsystem termination is initiated.
Print SYS1.LOGREC, and restart DB2. Notify the system programmer. This is probably either an error in DB2 or in the commit of the global transaction. Refer to Part 2 of DB2 Diagnosis Guide and Reference for information on identifying and reporting the problem. DB2 records on the SYS1.LOGREC data set and requests an SVC dump. The error indicates that there may be a problem with DB2 or with the commit coordinator of the global transaction. Collect the following diagnostic items listed in Appendix C, “Problem determination,” on page 1353: 1, 2, 5. Chapter 44. X’D9......’ codes 1087
Comments
 
 

 
 
  Prev   1  2  3  4  5  6  7  8  9  10  Next