Cause: DB2 was the DRDA2 AS for the transaction identified by "<luwid>". Resolution with the DB2 database shows heuristic damage occurred. The database identified by "<dbalias>" manually resolved the indoubt transaction. The DB2 database at "<luname>" rolled back the transaction. This is inconsistent with the commit decision of the DRDA2 coordinator at "<luname>".
The XID associated with the unit of work is printed following this message.
Indoubt resolution with the participant completes.
Action: Call the database administrator.
Database Administrator Action: Inform the database administrators at both the COORDINATOR "<luname>" and at the DATABASE "<dbalias>" that heuristic damage occurred for the transaction with "<luwid>". DB2 was a DRDA2 AS for the transaction. The DRDA2 AR at COORDINATOR "<luname>" made the decision to COMMIT the database updates made by "<luwid>". The "<dbalias>" PARTICIPANT made a heuristic decision to ROLL BACK the updates made by "<luwid>".
Cause: DB2 was the DRDA2 AS for the transaction identified by "<luwid>". Resolution with the DB2 DATABASE shows heuristic damage occurred. The database identified by "<dbalias>" manually resolved the indoubt transaction. The "<dbalias>" committed the transaction. This is inconsistent with the roll back decision of the DRDA2 COORDINATOR at "<luname>".
The XID associated with the unit of work is printed following this message.
Indoubt resolution with the participant completes.
Action: Call the database administrator.
Database Administrator Action: Inform the database administrators at both the COORDINATOR "<luname>" and at the DATABASE "<dbalias>" that heuristic damage occurred for the transaction with "<luwid>". DB2 was a DRDA2 AS for the transaction. The DRDA2 AR at COORDINATOR "<luname>" made the decision to roll back the database updates made by "<luwid>". At the PARTICIPANT "<dbalias>" a heuristic decision was made to COMMIT the updates made by "<luwid>".
Cause: DB2 has coordinator responsibility for the transaction identified by "<luwid>". Resolution with the participant shows heuristic damage occurred. The participant identified by "<luname>" and "<dbalias>" manually resolved the indoubt transaction. The action taken was to commit the transaction. This is inconsistent with the roll back decision of the coordinator.
The XID associated with the unit of work is printed following this message.
Indoubt resolution with the participant completes.
Action: Call the database administrator.
Database Administrator Action: Inform the local database administrator and the database administrator at "<luname>" that heuristic damage occurred for the transaction with "<luwid>". DB2 was the coordinator for the transaction and made the decision to roll back the database updates made by "<luwid>". At "<luname>" a heuristic decision was made to COMMIT the updates made by "<luwid>".
Cause: DB2 has coordinator responsibility for the transaction identified by "<luwid>". Resolution with the participant shows heuristic damage occurred. The participant identified by "<luname>" and "<dbalias>" manually resolved the indoubt transaction. The action taken was to roll back the UOW. This is inconsistent with the commit decision of the coordinator.
The XID associated with the unit of work is printed following this message.
Indoubt resolution with the participant completes.
Action: Call the database administrator.
Database Administrator Action: Inform the local database administrator and the database administrator at "<luname>" that heuristic damage occurred for the transaction with "<luwid>". DB2 was the coordinator for the transaction and made the decision to COMMIT the database updates made by "<luwid>". At "<luname>" a heuristic decision was made to ROLL BACK the updates made by "<luwid>".
Cause: DB2 was the DRDA2 AS for the transaction identified by "<luwid>". The DB2 transaction associated at the database with LUNAME="<luname2>" is indoubt. A protocol error occurred during indoubt resolution with the coordinator identified by "<luname1>".
The XID associated with the unit of work is printed following this message.
The indoubt transaction remains indoubt. A Resync Protocol Violation trace record is written.
Action: Call the database administrator.
Database Administrator Action: DB2 does not attempt to automatically resolve the indoubt transaction. The transaction must be manually resolved. The commit or abort decision made at the coordinator must be determined so that the same decision can be made at this participant DB2.
Contact the database administrator at the coordinator with "<luname>" and "<dbalias>", to determine whether the transaction committed or aborted.
Use the LIST INDOUBT TRANSACTIONS command at this (the participant) dbalias to resolve the indoubt transaction.
Cause: During execution of the two phase commit protocol with the coordinator at "<luname2>", a communication failure occured. Phase 1 of the protocol completed and the transaction at the database with "<luname1>" is indoubt.
The transaction is placed in the indoubt state and appears in the LIST DRDA INDOUBTS TRANSACTIONS report. Periodic attempts are made to reestablish communication with the coordinator for automatic resolution.
The XID associated with the indoubt unit of work is printed following this message.
Periodic attempts will be made to automatically resolve the indoubt transaction.
Action: Determine the cause of the communication failure and have the problem corrected. DB2 periodically attempts to establish communication for automatic resolution. If automatic resolution does not occur in a reasonable amount of time, call the database administrator. Manual resolution of the indoubt transaction might be necessary to release locked resources.
Database Administrator Action: If manual resolution is necessary:
Cause: During execution of the two phase commit protocol with the participant at "<luname>", a communication failure occured. Phase 1 of the protocol completed and the transaction is prepared for either commit or abort. The decison to commit the transaction was made, but cannot be communicated to the participant at this time. The participant is indoubt.
DB2 becomes responsible for indoubt resolution with the participant. This responsibility appears in the LIST DRDA INDOUBTS TRANSACTION report. Periodic attempts are made to reestablish communication with the participant for automatic resolution.
The XID associated with the unit of work is printed following this message.
Periodic attempts will be made to automatically resolve the indoubt transaction at the participant.
Action: Determine the cause of the communication failure and have the problem corrected. DB2 periodically attempts to reestablish communication for automatic resolution. If automatic resolution does not occur in a reasonable amount of time, call the database administrator. Manual resolution of the transaction might be necessary at the participant to release locked resources.
Database Administrator Action: If manual resolution is necessary, inform the database administrator at the participant that the decision is commit.
Cause: The indoubt transaction at the database identified by "<dbname>" was automatically resolved by communication with the coordinator identified by "<luname>". The transaction was committed.
The XID associated with the unit of work is printed following this message.
Processing continues normally.
Cause: One or more indoubt transactions exist with "<luname>". DB2 attempted to automatically resolve the indoubt transaction but a communication error occured.
Action: Determine the cause of the communication failure and have the problem corrected. DB2 periodically attempts to reestablish communication for automatic resolution. If automatic resolution does not occur in a reasonable amount of time, call the database administrator. Manual resolution of the transaction might be necessary at the participant to release locked resources.
Database Administrator Action: If manual resolution is necessary, inform the database administrator at the participant that the decision is commit.
Cause: An indoubt transaction exists with the partner at "<luname>". DB2 is unable to resolve the indoubt transaction because the partner has lost all knowledge of indoubt transactions due to a previous cold start.
Action: There is probably inconsistent data at the coordinator and participant. Inform database administrator of the status of the transaction.
Database Administrator Action: Manual resolution is necessary. The heuristic decision (that is, to commit or roll back the transaction) should be coordinated with any other participants and/or the coordinator. The existence of other participants might not be easy to determine. The information might be available in the coordinators recovery log even though the coordinator performed a cold start.
The commit or abort decision provided using the LIST INDOUBT TRANSACTIONS command for the transaction are propagated to all downstream participants, if any.
Cause: An attempt to make a warm start connection with a partner was rejected because the partner specified a different set of sync point parameters than the ones that were in use when communications were lost. DB2 has knowledge of indoubt transactions that involve the partner as either the coordinator or a participant. This error might be a recoverable error if the partner can restart with the original sync point parameters. If this is not possible, then the partner must perform a cold start connection with DB2.
The connection with the partner is rejected. DB2 retains indoubt knowledge.
Action: Call the database administrator.
Database Administrator Action: Contact the database administrator at the partner "<luname>" and determine if it is possible for the partner to perform a warm start with same sync point parameters as ours ('oldourname', 'oldtheirname', 'oldpa', 'oldfb', 'oldccls'). If this is possible, the next attempt to connect will succeed.
If this cannot be done, then there are two other possible solutions:
Cause: DB2 was the DRDA2 AS and has participant responsibility for indoubt transactions. The coordinator informed DB2 that it performed a cold start operation and lost all knowledge of indoubt transactions. The indoubt transactions at this DB2 must be manually resolved with the LIST INDOUBT TRANSACTIONS command.
The connection with the partner is accepted. A trace record is written.
Action: Call the database administrator.
Database Administrator Action: DB2 is a participant with one or more indoubt transactions where the coordinator is "<luname>". The DBMS at "<luname>" performed a cold start. The DB2 participant assumes that the coordinator recovery log was lost or damaged and indoubt transaction resolution cannot be achieved. There is probably inconsistent data at the coordinator.
The heuristic decision (that is, to commit or abort the transaction should be coordinated with any other participants. The existence of other participants might not be easy to determine. The information might be available in the coordinators recovery log even though the coordinator performed a cold start.
The commit or abort decision provided using the LIST INDOUBT TRANSACTIONS command for the transaction are propagated to all downstream participants, if any.
Cause: DB2 is a participant in the transaction. A protocol error occurred during the SNA sync point exchange with the coordinator identified by "<luname>". The protocol error fits into one of the following categories:
The XID associated with the unit of work is printed following this message.
If the protocol error was detected before the commit decision, the transaction at the database with LU name="<luname2>" may be indoubt. DB2 does not automatically resolve such an indoubt transaction because of the protocol error.
If the protocol error was detected after the commit decision, the transaction either completed commit or abort processing.
A Syncpoint Protocol Violation trace is written.
Action: The database administrator might need to manually resolve the indoubt transaction.
Database Administrator Action: Determine if the transaction is indoubt. If it is indoubt, it must be manually resolved using the LIST INDOUBT TRANSACTIONS command. The commit or abort decision made at the coordinator must be determined so that the same decision can be made at DB2.
Contact the database administrator at the coordinator dbalias to determine whether the transaction with LUWID="<luwid>" committed or aborted.
If the coordinator system is another DB2, then the following steps can be taken at the DB2 coordinator to determine the commit or abort decision.
Cause: DB2 is the coordinator of the transaction. A protocol error occurred during the SNA sync point exchange with the participant identified by "<luname>" and "<dbalias>". The protocol error fits into one of the following categories:
The XID associated with the unit of work is printed following this message.
If application was told that the transaction committed.
There may be an indoubt transaction at the participant and if so, the indoubt transaction must be manually resolved. DB2 does not automatically resolve the indoubt transaction because of the protocol error.
A Syncpoint Protocol Violation trace record is written.
Action: Call the database administrator. The participant might need to manually resolve the indoubt transaction.
Cause: DB2 has coordinator responsibility for the transaction which was rolled back. A protocol error occurred during indoubt resolution with the participant identified by "<luname>" and "<dbalias>".
The transaction at the participant remains indoubt. DB2 will not attempt to automatically resolve the indoubt transaction because of the protocol violation.
The XID associated with the unit of work is printed following this message.
A Resync Protocol Violation trace record is written.
Action: Call the database administrator. The participant might need to manually resolve the indoubt transaction.
Database Administrator Action: If the transaction is indoubt at the participant, it must be manually (heuristically) resolved.
Cause: The indoubt transaction at the database identified by "<dbname>" was automatically resolved by communication with the coordinator identified by "<luname>". The transaction was rolled back.
The XID associated with the unit of work is printed following this message.
Processing continues normally.
Cause: DB2 attempted to make a cold-start connection with a partner dbalias. The partner rejected this attempted connection.
The connection was not made.
Action: Call the database administrator.
Database Administrator Action: DB2 is not able to connect the partner "<luname>" until the partner "<luname>" allows a cold-start connection with DB2. Contact the database administrator at the partner "<luname>".
Contact your IBM Support Center for further assistance.
Cause: DB2 is the coordinator of the transaction. A protocol error occurred during the SNA sync point exchange with the participant identified by "<luname>" and "<dbalias>". The protocol error fits into one of the following categories:
The XID associated with the unit of work is printed following this message.
If application was told that the transaction rolled back.
There may be an indoubt transaction at the participant and if so, the indoubt transaction must be manually resolved. DB2 does not automatically resolve the indoubt transaction because of the protocol error.
A Syncpoint Protocol Violation trace record is written.
Action: Call the database administrator. The participant might need to manually resolve the indoubt transaction.
Cause: DB2 has coordinator responsibility for indoubt transactions at a participant and just connected with the participant, which lost all knowledge of indoubt transactions because of a previous cold start. There might be damage at the participant.
The connection with the partner is accepted.
Action: Call the database administrator.
Database Administrator Action: DB2 is the coordinator with indoubt transaction resolution responsibility for one or more indoubt units of work at "<luname>". The DBMS at "<luname>" performed a cold start. DB2 assumes that the participant recovery log was lost or damaged and indoubt transaction resolution cannot be achieved. There is probably inconsistent data at the participant. Minimally, the participant might not completely reflect the final outcome of the transactions that were indoubt at the time the failure occurred.
Cause: DB2 detected a protocol violation in the SNA Exchange Log Names (XLN) exchange with the partner at the specified "<luname>".
The attempt to connect with the remote site fails. An XLN Protocol Violation trace record is written.
Action: Contact the system programmer for the remote site. The invalid XLN message is recorded in the trace record. The system logic error that causes the invalid XLN message must be corrected at the remote site.
Cause: An attempt to make a warm start connection with a partner was rejected because the partner specified our log name as name2. Our log name is name1, which is the luname of the local DB2. This error might be a recoverable error if the partner can restart with our log name as name1. If this is not possible, then the partner must perform a cold start connection with DB2.
The connection with the partner is rejected.
Action: Call the database administrator.
Database Administrator Action: Contact the database administrator at the partner "<luname>" and determine if it is possible for the partner to perform a warm start with our log name specified as the luname of this DB2. If this is possible, the next attempt to connect will succeed. Or have the partner "<luname>" perform a cold start connection with DB2.
Cause: The indoubt unit of work was automatically resolved by communication with the participant. The participant has been notified of the commit decision.
The XID associated with the unit of work is printed following this message.
Processing continues normally.
Cause: The indoubt unit of work was automatically resolved by communication with the participant. The participant has been notified of the roll back decision.
The XID associated with the unit of work is printed following this message.
Processing continues normally.
Cause: During execution of the two phase commit protocol with the participant at "<luname>", a communication failure occured. Phase 1 of the protocol completed and the transaction is prepared for either commit or abort. The decison to roll back the transaction was made, but cannot be communicated to the participant at this time. The participant is indoubt.
DB2 becomes responsible for indoubt resolution with the participant. This responsibility appears in the LIST DRDA INDOUBTS TRANSACTION report. Periodic attempts are made to reestablish communication with the participant for automatic resolution.
The XID associated with the unit of work is printed following this message.
Periodic attempts will be made to automatically resolve the indoubt transaction at the participant.
Action: Determine the cause of the communication failure and have the problem corrected. DB2 periodically attempts to reestablish communication for automatic resolution. If automatic resolution does not occur in a reasonable amount of time, call the database administrator. Manual resolution of the transaction might be necessary at the participant to release locked resources.
Database Administrator Action: If manual resolution is necessary, inform the database administrator at the participant that the decision is roll back.
Cause: DB2 has coordinator responsibility for the transaction which was committed. A protocol error occurred during indoubt resolution with the participant identified by "<luname>" and "<dbalias>".
The transaction at the participant remains indoubt. DB2 will not attempt to automatically resolve the indoubt transaction because of the protocol violation.
The XID associated with the unit of work is printed following this message.
A Resync Protocol Violation trace record is written.
Action: Call the database administrator. The participant might need to manually resolve the indoubt transaction.
Database Administrator Action: If the transaction is indoubt at the participant, it must be manually (heuristically) resolved.
Cause: The local communications release level is older than the minimum release level or the communication manager is incorrectly configured to support APPC SYNCLEVEL(SYNC) conversations.
The attempt to create a protected conversation fails.
Action: Install and configure the correct communications level required to support SYNCLEVEL(SYNC) conversations.
Cause: The DB2 Syncpoint Manager recovery log is inconsistent and cannot be used to perform recovery during DB2 start up processing.
Action: Indoubt transactions may exist at DRDA2 application servers. These indoubt transactions must be recovered manually.
Call the database administrator.
Database Administrator Action: To start the Syncpoint Manager, erase the spmlog directory and start DB2. This will cause DB2 to create new syncpoint log files and to establish cold start connections with all DRDA2 application servers.
Cause: The DB2 Syncpoint Manager log is inconsistent and cannot be used. An unrecoverable error has been detected while attempting to write to the SPM log during DB2 processing.
Action: The DB2 Syncpoint Manager will not allow any new synclevel(twophase) connections. Issue the LIST DRDA INDOUBT TRANSACTIONS command to determine the status of any indoubt transactions.
Call the database administrator.
Database Administrator Action: To start the Syncpoint Manager, erase the spmlog directory and start DB2. This will cause DB2 to create new syncpoint log files and to establish cold start connections with all DRDA2 application servers.
Cause: The syncpoint support could not be enabled by DB2. The most likely causes of this are:
Action: Determine the reason based on the provided possibilites. Correct and retry.
Cause: The DB2 Syncpoint Manager requires a CPIC Side Information Profile of the name provided in order to initialise. This profile cannot be found or contains incorrect information.
Action: Please correct the profile, verify the SNA profile, stop and restart both DB2 and SNA. Please see the DB2 Connect Quick Beginnings for information on how to configure for SPM support.
Cause: In order for the DB2 Syncpoint Manager to initialise itself the instance in which DB2 is started needs certain authorities in order to interact with the SNA support. AIX SNA requires that the Trusted Group Names be updated to include any userids which will be issuing these commands.
Action: Update trusted group name as described, stop and restart AIX SNA. Logoff of the AIX Term, log back on and retart DB2.
Cause: The DB2 Syncpoint Manager requires a Transaction Program Profile of the name provided in order to initialise. This profile cannot be found or contains incorrect information.
Action: Please correct the profile, verify the SNA profile, stop and restart both DB2 and SNA. Please see the DB2 Connect Quick Beginnings for information on how to configure for SPM support.
Cause: When the DB2 Syncpoint Manager initialises itself it registers Transaction Programs for which it will listen. In order for the SPM to listen for the named TP, it isnecessary that no other Transaction Program Profile have this TP defined else there will be a conflict between the DB2 SPM and AIX SNA. If such a conflict exists then AIX SNA will listen and the SPM will not.
Action: If you require the DB2 SPM to listen for the named TP then you must ensure that no other TP Profile references this transaction program. The SPM has started succesfully regardless of this error.
Cause: The DB2 SPM tried to register this TP but could not.
Action: Remove the TP Profile from AIX SNA. Stop and restart both DB2 and AIX SNA.
Cause: An LU can be registered with AIX SNA as supporting syncpoint by at most one application. In this case, the requested SPM LU is already registered. The most likely cause is that the Encina Peer to Peer Gateway is using this LU as an SPM or another DB2 instance is using this as an SPM.
Action: Change the spm_name in the database manager configuration such that a unique LU is used. Stop and restart DB2.
Cause: This error occurs when the customer is trying the start the SPM using CS/NT V5.01 and is using a Local LU 6.2 definition where the SNA API client use flag has been set.
Action: Either choose a different local LU 6.2 (without the SNA API client use configured) or disable the SNA API client use flag for the Local LU 6.2 definition.
Cause: In order to have proper communications with the host system, any CPIC Side information profile defined for communication must specifiy the same LU as defined for the configured DB2 SPM.
Action: Update SNA CPIC Side information profile "<profile1>" with the proper LU, verify the SNA profile, stop and restart both SNA and DB2, and try the connection again.