This article lists the top Troubleshooting errors and issues when viewing a CDC Instance in the Oracle CDC Designer Configuration tool. This tool is part of the Change Data Capture for Oracle by Attunity that is included starting with Microsoft SQL Server 2012. << Back to Microsoft SQL Server 2012 Change Data Capture for Oracle by Attunity Topics
Microsoft CDC for Oracle by Attunity Designer fails with "Incorrect syntax near the keyword 'KEY'" error when adding an Oracle Table.
Properties added in the Advanced options of the Attunity CDC instance are removed when a table is added or removed from CDC. Attunity CDC stops working after applying SQL fix that adds __$command_id column
Change Data Capture for Oracle by Attunity stops working when Oracle tables have column with Long data type
CDC for Oracle instance hangs when you start it, and does not capture changes. Oracle server memory may increase until it runs out of memory or crash.
Some changes are missed and they are not replicated to the SQL Server databases. This issue occurs when a table contains more than one character large binary object (CLOB) and one of the CLOBs has a large value.
You can see the error in the Status messages field on the Oracle Change Data Capture Designer management console, when a CDC instance is highlighed in the left pane.
You can query the trace table in the CDC database in SQL Server to see if anything has been logged. { "2/18/2012 12:16:34 AM","ERROR","computername","ERROR","UNEXPECTED","ORACDC508E:Oracle method OCIStmtExecute failed with error: ORA-00942: table or view does not exist ","source","","" "2/18/2012 12:16:34 AM","ERROR","computername","RUNNING","IDLE","ORACDC518E:Failed to verify archive log mode.","source","","" "2/18/2012 12:16:34 AM","ERROR","computername","ERROR","UNEXPECTED","ORACDC517E:Oracle Call Intreface (OCI) method failed: ORA-00942: table or view does not exist .","source","","" "2/18/2012 12:16:34 AM","ERROR","computername","ERROR","UNEXPECTED","ORACDC414E:The Engine component failed with return code 1.","engine","","" "2/18/2012 12:16:34 AM","INFO","computername","ERROR","STOP","ORACDC312I:The Oracle CDC instance for service OracleCDCService1 and database HR Instance finished abnormally.","service","","" }
You can raise the amount of tracing collected by the instance and repeat the scenario to gather more detailed logging. Add a new property in the Advanced Settings grid on the Advanced tab, set the name of the property to "trace," and then set the value to "SOURCE" without quotes. Click OK to save the change. Now reproduce the error. For example, you may start the CDC Instance and wait until an error has occurred. Click Collect Diagnostics hyperlink on the Status tab in the Oracle Change Data Capture Designer management console. Specify the full path and output file name, then click Create. "2/18/2012 12:16:34 AM","ERROR","computername","ERROR","UNEXPECTED","ORACDC508E:Oracle method OCIStmtExecute failed with error: ORA-00942: table or view does not exist","source","",""
"2/18/2012 12:16:34 AM","ERROR","computername","RUNNING","IDLE","ORACDC518E:Failed to verify archive log mode.","source","","" "2/18/2012 12:16:34 AM","ERROR","computername","ERROR","UNEXPECTED","ORACDC517E:Oracle Call Intreface (OCI) method failed: ORA-00942: table or view does not exist.","source","","" "2/18/2012 12:16:34 AM","ERROR","computername","ERROR","UNEXPECTED","ORACDC414E:The Engine component failed with return code 1.","engine","","" "2/18/2012 12:16:34 AM","INFO","computername","ERROR","STOP","ORACDC312I:The Oracle CDC instance for service OracleCDCService1 and database HR Instance finished abnormally.","service","",""
When using the CDC Instance there are various runtime errors and scenarios you may experience. This is a very common error as seen in the Status message field of the CDC Instance. The instance retries numerous times (Status icon will change to green momentarily) but then it will fail with the Red Exclamation and the UNEXPECTED status at the end of each try. "2/18/2012 12:16:34 AM","ERROR","computername","ERROR","UNEXPECTED","ORACDC508E:Oracle method OCIStmtExecute failed with error: ORA-00942: table or view does not exist ","source","","" "2/18/2012 12:16:34 AM","ERROR","computername","RUNNING","IDLE","ORACDC518E:Failed to verify archive log mode.","source","","" "2/18/2012 12:16:34 AM","ERROR","computername","ERROR","UNEXPECTED","ORACDC517E:Oracle Call Intreface (OCI) method failed: ORA-00942: table or view does not exist .","source","","" "2/18/2012 12:16:34 AM","ERROR","computername","ERROR","UNEXPECTED","ORACDC414E:The Engine component failed with return code 1.","engine","","" When the Oracle account specified for connecting from the CDC Instance to the Oracle server does not have permissions to see the various system log miner views, it cannot see that the view exists, and will raise the error.
To resolve the error, you can either change the account used for connecting to Oracle from the CDC instance to an account with the necessary permissions, or you can grant the currently configured user the appropriate permissions within the Oracle database system. The user must be able to query this system view, in order to avoid the error message. The list of all the necessarily permissions is detailed in the help file included in the installation program files folder [C:\Program Files\Change Data Capture for Oracle by Attunity\Attunity.SqlServer.XdbCdcDesigner.chm] See the page entitled "Connect to an Oracle Source Database" within that chm file for the complete list. You can set the user account by selecting the CDCInstance from the left pane and clicking the Properties button in the Actions rightmost pane within the CDC Designer window. You can change the Oracle log mining authentication account from the properties dialogue page.
<< Back to Microsoft SQL Server 2012 Change Data Capture for Oracle by Attunity Topics