Reconcile fails due to following errors:
"Error: 15007 - Can't open poster queue que_NOEXIST: Queue does not exist. [sp_oreconcile(rcl)/6548]"
"Child process failed: internal error -- see event log"
This can be due to a number of reasons which are detailed in the Resolution section.
The following are the causes along with the resolution:
1. The Post queue has not yet been spawned so it does not exist.
For the reconcile to be able to operate without error, one may want to wait for the Post queue to spawn. It will happen after the user activity resumes on the source database and the changes to the database are gathered by Capture process and sent to target. Once such messages reach target, the Post queue in question will be spawned and the reconcile can then be issued.
2. A wrong queue name has been specified, or the case (upper or lower case) specified is not correct.
If an incorrect queue name is specified, then one can re-issue the reconcile command with the correct queue name. The command is sensitive to the case (upper or lower case) of the queue name. So one may check the config file and issue the command with the proper name and case of the Post queue. There are other commands of Shareplex that are not case sensitive, for example, "show post detail queue <queue name>" but this is not so with reconcile.
3. A server name has been specified in reconcile when there exists named Post queue(s).
The use of server name and named Post queue is mutually exclusive in reconcile, meaning that either one needs to specify a named Post queue to be reconciled (if using named Post queues) or specify a server name if no named Post queue exist. Specifying a server name in reconcile when using named Post queue will result in the above error and the command needs to be re-issued with proper options.
4. Wrong SID for source and/or target has been specified including the case.
The use of wrong source and/or target SID as well as the incorrect case of the SID can also result in the above error and the command needs to be re-issued after the necessary corrections as applicable.
5. Reconcile was already issued for the named Post queue in question and the second reconcile on the same queue failed.
This typically happens when there are many named Post queue involved and there is a chance that the user may lose track of the reconcile issued earlier. Another thing that increases the chances of errors is that once reconcile is issued from a session, the prompt does not return until the reconcile terminates. This requires opening up of another session for issuing the next reconcile on another queue. So there is a chance that the user may issue reconcile second time for the same named queue. The error does no harm as far as the earlier reconcile on the same queue is concerned and nothing needs to be done other than to wait for the previous reconcile to succeed or error out.
Please refer to Solution # SOL 15099 that delves on similar error incurred when Post is running while reconcile is run.
