fixing blocking issues

Author: MashaMSFT

docs/relational-databases/track-changes/known-issues-resolutions-with-cdc-for-oracle-attunity.md

@@ -15,7 +15,7 @@ ms.author: mathoma
 This topic lists the top issues and known resolutions when viewing a change data capture (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 SQL Server 2012. 
 
 ## Bug fixes
-Before spending too much time troubleshooting, it is important to use the latest builds of CDC for Oracle by Attunity to avoid known issues such as tehse:
+Before spending too much time troubleshooting, it is important to use the latest builds of CDC for Oracle by Attunity to avoid known issues such as these:
 
 ### SQL Server 2017
 
@@ -26,7 +26,7 @@ Before spending too much time troubleshooting, it is important to use the latest
 
 
 **Version 5.0.0.93** contains these fixes: 
-- Microsfot CDC for Oracle by Attunity Designer fails with "Incorrect syntax near the word 'KEY'" error when adding an Oracle table. 
+- Microsoft CDC for Oracle by Attunity Designer fails with "Incorrect syntax near the word 'KEY'" error when adding an Oracle table. 
 
 
 ### SQL Server 2016
@@ -55,21 +55,21 @@ Before spending too much time troubleshooting, it is important to use the latest
 - The metadata validation for Oracle table cdc.table_name failed. Column column_name index is out of range.  And this issue: Oracle CDC service shows aborted status when you use CDC for Oracle by Attunity
     - Fixed in _Cumulative Update 1 for SQL Server 2014 RTM_ as described in KB [2894025](https://support.microsoft.com/kb/2894025).
 - Some changes are missed and are not replicated to the SQL Server database. This issue occurs when a table contains more than one character large binary object (CLOB) and one of the CLOBs has a large value. 
-    - Fixed in _Cumulative Update 1 for SQL Server 2014 SP1_ and _Cumulative Update 8 for SQL Server 2014 RTM_ as described in KB [3029096](https://support.microsoft.com/en-us/kb/3029096). 
+    - Fixed in _Cumulative Update 1 for SQL Server 2014 SP1_ and _Cumulative Update 8 for SQL Server 2014 RTM_ as described in KB [3029096](https://support.microsoft.com/kb/3029096). 
 - Change Data Capture for Oracle by Attunity stops working when Oracle tables have column with Long data type.
-    - Fixed in _Cumulative Update 5 for SQL Server 2014 SP1_ and _Cumulative Update 12 for SQL 2014 RTM_ as described in KB [3145983](https://support.microsoft.com/en-us/kb/3145983).
+    - Fixed in _Cumulative Update 5 for SQL Server 2014 SP1_ and _Cumulative Update 12 for SQL 2014 RTM_ as described in KB [3145983](https://support.microsoft.com/kb/3145983).
 
 ### SQL Server 2012
 
 **Version 1.1.0.102** contains these fixes: 
 
 - 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
 - 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.
-- [2672759](https://support.microsoft.com/kb/2672759/EN-US): Error message when you use the Microsoft Change Data Capture Service for Oracle by Attunity: "ORA-00600: internal error code". Add the SOURCE level tracing and confirm if you get the same ORA-00600 error. Fixed by an Oracle patch download.
+- [2672759](https://support.microsoft.com/kb/2672759): Error message when you use the Microsoft Change Data Capture Service for Oracle by Attunity: "ORA-00600: internal error code". Add the SOURCE level tracing and confirm if you get the same ORA-00600 error. Fixed by an Oracle patch download.
 - Multiple Partitions
     - When you use more than 10 partitions on an Oracle table, the CDC instance cannot capture all the changes for the table. When the Oracle table is defined with more than 10 partitions, the changes are only captured from the last 10 partitions. Fixed in the _Service Pack 1 release for SQL Server 2012_. See [SP1 Feature Pack download page](https://www.microsoft.com/download/details.aspx?id=35580). 
 - Changes are lost
-    - The capturing of events can go into an infinite loop and stop capturing new data changes (related to Oracle bug 5623813). When on Oracle RAC environment is performing a stop or resume  of the the CDC instance, changes can be skipped/lost. This means the SQL Server change data capture will be missing important rows, and thus there is data loss in the data warehouse or subscribing system. Fixed in the _Service Pack 1 release for SQL Server 2012_. See [SP1 Feature Pack download page](https://www.microsoft.com/download/details.aspx?id=35580)
+    - The capturing of events can go into an infinite loop and stop capturing new data changes (related to Oracle bug 5623813). When on Oracle RAC environment is performing a stop or resume  of the CDC instance, changes can be skipped/lost. This means the SQL Server change data capture will be missing important rows, and thus there is data loss in the data warehouse or subscribing system. Fixed in the _Service Pack 1 release for SQL Server 2012_. See [SP1 Feature Pack download page](https://www.microsoft.com/download/details.aspx?id=35580)
 - Double widths on columns in SQL
     - When creating a CDC for Oracle instance, in the scripts to run against SQL Server, the length of a variable width data type column is doubled in SQL Server tables that are created in the script. For example, if you try to track changes on a VARCHAR2(10) column in an Oracle table, then the corresponding column in the SQL Server table is NVARCHAR(20) in the deployment script. Fix in either _Cumulative Update 2 for SQL Server 2012 SP1_ or _Cumulative update 5 for SQL Server 2012_ as described in KB [2769673](https://support.microsoft.com/kb/2769673). 
 - DDL Data is truncated
@@ -82,15 +82,15 @@ Before spending too much time troubleshooting, it is important to use the latest
 - The metadata validation for Oracle table cdc.table_name failed. Column column_name index is out of range. Fixed in _Cumulative Update 7 for SQL Server 2012 SP1_ as described in KB [2883524](https://support.microsoft.com/kb/2883524).
 - Oracle CDC service shows aborted status when you use CDC for Oracle by Attunity in SQL Server 2012. Fixed in _Cumulative Update 8 for SQL Server 2012 SP1_ as described in KB [2923839](https://support.microsoft.com/kb/2923839).  
 - Some changes are missed and 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. Fixed in _Cumulative Update 8 for SQL Server 2012 SP1_ as described in KB [2923839](https://support.microsoft.com/kb/2923839).   
-- Change Data Capture for Oracle by Attunity stops working when Oracle tables have column with Long data type. Fixed in _Cumulative Update 2 for SQL Server 2012 SP3_ and _Cumulative Update 11 for SQL 2012 SP2_  as described in KB [3145983]( https://support.microsoft.com/en-us/kb/3145983). 
+- Change Data Capture for Oracle by Attunity stops working when Oracle tables have column with Long data type. Fixed in _Cumulative Update 2 for SQL Server 2012 SP3_ and _Cumulative Update 11 for SQL 2012 SP2_  as described in KB [3145983](https://support.microsoft.com/kb/3145983). 
 
 ## Collect detailed logs 
 
 This section explains how to collect errors and events from the CDC instance. 
 
 ### Management console
 
-You can see errors in the **Status** messages filed within the Oracle Change Data Capture Designer management console when a CDC instance is highlighted int he left pane. 
+You can see errors in the **Status** messages filed within the Oracle Change Data Capture Designer management console when a CDC instance is highlighted in the left pane. 
 
 ### Query trace table
 
@@ -122,7 +122,7 @@ This is a common error displayed in the **Status** message field of the CDC Inst
 
 ![Oracle error](media/known-issues-resolutions-with-cdc-for-oracle-attunity/oracle-error.png)
 
-`
+```
 "ERROR","computername","ERROR","UNEXPECTED",
 "ORACDC508E:Oracle method OCIStmtExecute failed with error: ORA-00942: table or view does not exist ","source","",""
 
@@ -134,7 +134,7 @@ This is a common error displayed in the **Status** message field of the CDC Inst
 
 "ERROR","computername","ERROR","UNEXPECTED",
 "ORACDC414E:The Engine component failed with return code 1.","engine","",""
-`
+```
 
 This happens when the Oracle account connecting from the CDC instance to the Oracle server does not have permission to see system log views. 
 
@@ -150,7 +150,7 @@ You can set the user account by selecting the CDCInstance from the left pane and
 
 
 
-## See Also  
+## See also  
  [Track Data Changes (SQL Server)](../../relational-databases/track-changes/track-data-changes-sql-server.md)   
  [About Change Data Capture (SQL Server)](../../relational-databases/track-changes/about-change-data-capture-sql-server.md)   
  [Work with Change Data (SQL Server)](../../relational-databases/track-changes/work-with-change-data-sql-server.md)