Expert Advice

KRC_inbay_too_long  
Situation Description
Suggested Actions
Situation Description

A packet has been in the shipping bay longer than expected.

 

Suggested Actions

A synchronization packet can remain in an incoming bay too long if a packet on which this packet depends has been delayed or lost in transit. This packet cannot be applied to the replica until another sibling sends the missing oplogs. Determine if the packet is a replica creation packet or a synchronization packet. Replica creation packets must be deleted manually after the replica has been created using the "mkreplica -import" command. Synchronization packets are deleted automatically after they have been imported to all local replicas by a "syncreplica -import" command in a receipt-handler script or scheduled job. Open the Epochs workspace and check the epoch tables to determine whether the packet's dependencies have been met. Open the Logs workspace and look for errors in MultiSite logs. For more information, see Technote 1132053 (Packet depends on changes not yet received)

 

Copyright IBM Corp. 2005, 2012 All Rights Reserved US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contact IBM