Submitting forms on the support site are temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for the inconvenience.
If you received error "Notice: can't parse log record at #", and capture is not moving, consider the following:
Common cause for error "Notice: can't parse log record at #" usually is because the REDO LOGS was set with LOG_PARALLELISM > 1. If the LOG_PARALLELISM parameter is set to a value greater than 1, SharePlex will not be able to parse the redo logs correctly and thus the Capture process start to skips records and error with "Notice: can't parse log record at #".
To verify if you're in compliant, check Oracle init.ora for LOG-PARALLESM > 1.
Sign In Required
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
Your Request will be reviewed by our technical reviewer team and, if approved, will be added as a Topic in our Knowledgebase.
Welcome to Quest Support
You can find online support help for Quest *product* on an affiliate support site. Click continue to be directed to the correct support content and assistance for *product*.
The Quest Software Portal no longer supports IE8, 9, & 10 and it is recommended to upgrade your browser to the latest version of Internet Explorer or Chrome.