DSNL410I WARM START CONNECTION BY PARTNER location REJECTED. PARTNER CHANGED AT LEAST 1 OF - OUR LOG NAME oldourname(newourname), THEIR LOG NAME oldtheirname(newtheirname), PA_SUPPORT oldpa(newpa), FLAG_BYTE_SENT oldfb(newfb), CCLUNAME_SENT oldccls(newccls), AND INDOUBT THREADS REQUIRE RESOLUTION. SEE IFCID=205 TRACE RECORD WITH IFCID SEQUENCE NUMBER=seq-no.
Explanation
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 threads 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.
- location
- The 'location' with which the connection failed: either the relational database name (location-name) or the logical unit name (<luname>) of the partner.
- oldourname
- The log name for this Db2 subsystem. This value is null if the partner did not initiate the log name exchange.
- newourname
- The log name for this Db2 subsystem, as remembered by our partner and sent to us in the attempted warm start connection. This value is null if the partner did not initiate the log name exchange.
- oldtheirname
- The log name used by the partner during the last connection, as remembered by Db2.
- newtheirname
- The log name used by the partner in the attempted warm start connection.
- oldpa
- The sync point protocol used during the last connection, as remembered by the Db2 (PA - Presumed Abort, PN - Presumed Nothing).
- newpa
- The sync point protocol used during the last connection, as remembered by the partner (PA - Presumed Abort, PN - Presumed Nothing).
- oldfb
- The use of the PS header byte 2 during the last connection, as remembered by Db2 (F - used as flag byte, N - not used as flag byte).
- newfb
- The use of the PS header byte 2 during the last connection, as remembered by the partner (F - used as flag byte, N - not used as flag byte).
- oldccls
- Whether the luname of the conversation correlator was exchanged as part of the sync point protocol during the last connection, as remembered by Db2. (E - was exchanged, N - was not exchanged).
- newccls
- Whether the luname of the conversation correlator was exchanged as part of the sync point protocol during the last connection, as remembered by the partner (E - was exchanged, N - was not exchanged).
- seq-no
- The IFCID sequence number associated with the trace record. The sequence number is printed in hexadecimal format. If the sequence number is zero, then IFCID 0205 was not active or it was active with a destination of the resident trace table only. IFCID 0205 is a member of statistics class 4, which has a default destination of SMF.
System action
The connection with the partner is rejected. Alert A002 is generated. Db2 retains indoubt knowledge.
System programmer response
Call the database administrator.
Database Administrator Action: Contact the database administrator at the partner 'location' 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:
- Have the partner 'location' perform a cold start connection with this Db2 subsystem.
- Use the RESET INDOUBT command with the FORCE option in conjunction with the LOCATION parameter to cause the next connection with the partner to be a cold start connection.