LOGSTDBY Analyzer process stopped

Question

hi,
i inserted a row in a table on primary db.
but it is not showing in standby db site.
error in standby alter.log
LOGSTDBY status: ORA-00001: unique constraint (user_name.PK_key) violated
LOGSTDBY id: XID 0x0003.02c.00000cc5, hSCN 0x0000.004da30d, lSCN 0x0000.004da30d, Thread 1, RBA 0x00be.00002771.1e4, txnCscn 0x0000.004da30f, PID 1280, ORACLE.EXE (P004)
LOGSTDBY Apply process P004 pid=58 OS id=1280 stopped
Tue Jan 03 16:48:38 2012
LOGSTDBY Apply process P004 pid=58 OS id=1280 stopped
Tue Jan 03 16:48:38 2012
LOGMINER: End mining logfile: 'Location\1_191_766840337.ARC'
Tue Jan 03 16:48:39 2012
LOGMINER: Begin mining logfile:Location\1_192_766840337.ARC
Tue Jan 03 16:48:39 2012
ORA-12801: error signaled in parallel query server P004
ORA-00001: unique constraint (USERNAME.PK_KEY) violated
Tue Jan 03 16:48:39 2012
LOGMINER: End mining logfile: Location\1_192_766840337.ARC
Tue Jan 03 16:48:39 2012
LOGMINER: Begin mining logfile: Location\1_193_766840337.ARC
LOGSTDBY Analyzer process P003 pid=57 OS id=5656 stopped
LOGSTDBY Apply process P007 pid=61 OS id=5124 stopped
LOGSTDBY Apply process P008 pid=62 OS id=3288 stopped
LOGSTDBY Apply process P006 pid=60 OS id=6128 stopped
LOGSTDBY Apply process P005 pid=59 OS id=5604 stopped
A single transaction is not saving there
Please help what can i do
Regards
Vaibhav

Answer 1

Hello;
There's an Oracle note on this :
Handling ORA-1403 ora-12801 on logical standby apply [ID 1178284.1]
With a large troubleshooting section.
Also worth a look :
Oracle Data Guard Readme for SQL Apply Release 10.1.0.4 [ID 304061.1]
This is key of course :
ORA-00001: unique constraint (USERNAME.PK_KEY) violated
When an insert is performed that violates a constraint the insert statement is placed into the redo stream with a record that states the insert should be rolled back. As the SQL Apply operations apply the sql from the redo stream the insert that violated the constraint is attempted and then rolled back.
To find the transaction that causes the sql apply failure :
SELECT
  EVENT,
  XIDUSN,
  XIDSLT,
   XIDSQN
FROM
  DBA_LOGSTDBY_EVENTS
WHERE
  EVENT_TIME = (SELECT MAX(EVENT_TIME) FROM DBA_LOGSTDBY_EVENTS);Sikp the transaction :
EXEC DBMS_LOGSTDBY.SKIP_TRANSACTION(<XIDUSN>,<XIDSLT>,<XIDSQN>)start the sql apply (Don't use if you are using broker, use broker)
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY;Best Regards
mseberg