CDC for Oracle Continually goes to Aborted State - SQL Server 2012

Question

I am setting up a test environment for CDC with an Oracle system.  I have everything set up to the point where logs are being read and data appears to be getting added to the CDC tables in SQL Server.  However, at different times during the day,
the status of the service goes to Aborted and the service is completely stopped.  The first time I start the service, it will run for about 1 hour, before it aborts.  After that, it only takes 2 or 3 minutes, sometimes less, before this happens again.
Below are the last entries in the log when the instance aborted.  Whenever the instance aborts, the last message is always "Reading Complementary records for large log miner SQL_REDO/SQL_UNDO".  I'm guessing there's a permission or setting
in Oracle that I'm missing, but I don't know what it is.
Version information:
Oracle: 10.2.0.5.0
CDC Service: SQL Server 2012 SP 1
SQL Server Database Engine: 11.0.3128
record","source","","0xDD070A00170012001C0004000043073800000000000000000626001100F8DD3A00000000061474B6B30100000100012B190000CC8E01340000000000"
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Reading next record","source","",""
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Enqueue transaction record","source","","0xDD070A00170012001C0004004085163800000000000000000626002F00E2DD3A00000000061474B6B40100000100012B190000CCA201C40000000000"
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Reading next record","source","",""
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Enqueue transaction record","source","","0xDD070A00170012001C000400C009353800000000000000000026002F00E2DD3A00000000061474B6B50100000100012B190000CCA500A00000000000"
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Reading next record","source","",""
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Enqueue transaction record","source","","0xDD070A00170012001C000400408E533800000000000000000026001100F8DD3A00000000061474B6B70100000100012B190000CCAF00440000000000"
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Reading next record","source","",""
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Enqueue transaction record","source","","0xDD070A00170012001C00040080D0623800000000000000000626002D00DBDD3A00000000061474B8780100000100012B19000108B500280000000000"
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Reading next record","source","",""
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Enqueue transaction record","source","","0xDD070A00170012001C0004000055813800000000000000000626001500E0DD3A00000000061474B8790100000100012B19000108C7003C0000000000"
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Reading next record","source","",""
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Enqueue transaction record","source","","0xDD070A00170012001C00040080D99F3800000000000000000026001500E0DD3A00000000061474B87A0100000100012B19000108C901140000000000"
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Reading next record","source","",""
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Enqueue transaction record","source","","0xDD070A00170012001C000400C01BAF3800000000000000000026002D00DBDD3A00000000061474B87C0100000100012B19000108D301540000000000"
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Reading next record","source","",""
"10/23/2013 6:28:04 PM","TRACE","ETL-BI12-01-T","RUNNING","IDLE","ORACDC000T:Reading Complementary records for large log miner SQL_REDO/SQL_UNDO","source","",""

Answer 1

Here are the permissions we have set up on the Oracle side: (Please forgive the poor formatting.  The editor wants to remove all of the spaces and add extra carriage returns.)
GRANT
EXECUTE
ON 
"SYS"."DBMS_LOGMNR"
TO
"LOGREADER";
GRANT
EXECUTE
ON 
"SYS"."DBMS_LOGMNR_D"
TO
"LOGREADER";
grant
select
any
transaction
to
logreader;
GRANT
"CONNECT"
TO
"LOGREADER";
GRANT
select
ON
sys.v_$database
to
"LOGREADER";
GRANT
select
ON
sys.v_$logmnr_contents
to
"LOGREADER";
GRANT
select ON
sys.v_$logmnr_dictionary
to
"LOGREADER";
GRANT
selectONsys.v_$logmnr_logfileto"LOGREADER";
GRANT
selectONsys.v_$logmnr_logsto"LOGREADER";
GRANT
selectONsys.v_$logmnr_parametersto"LOGREADER";
GRANT
selectONsys.v_$logmnr_sessionto"LOGREADER";
GRANT
selectONsys.v_$logmnr_transactionto"LOGREADER";
GRANT
selectONsys.v_$logto"LOGREADER";
GRANT
selectONsys.v_$logfileto"LOGREADER";
GRANT
selectONsys.v_$archived_logto"LOGREADER";
GRANT
select
ON
sys.dba_registry
to
"LOGREADER";
GRANT
select
ON
sys.v_$instance
to
"LOGREADER";
GRANT
select
ON
sys.v_$thread
to
"LOGREADER";
GRANT
select
ON
sys.v_$parameter
to
"LOGREADER";
For each table we want to capture changes on, select rights have been granted to this user, as well.