-
Title
Capture stopped due to ORA-01403 after Oracle upgrade -
Description
Capture is stopped due to error after Oracle upgrade (9i to 10g in this case) and the event log shows that it is stopped due to ORA-01403 as the following screen shots show:
sp_ctrl (wustd4107:2150)> show
Process Source Target State PID
---------- ------------------------ ------------ -------------------- ------
Capture o.w229u Stopped - due to error
Read o.w229u Running 27013
sp_ctrl (wustd4107:2150)> show log reverse
04/18/07 16:50 Process exited sp_ocap (for o.w229u) [pid = 27485] - exit(1)
04/18/07 16:50 Error: Unexpected Oracle error: ORA-01403: no data found. in sp_ocap.c:1758 [sp_ocap(osp)/27485]
04/18/07 16:50 Notice: ORA-01403: no data found. [sp_ocap(osp)/27485]
04/18/07 16:50 Notice: Oracle env - w229u:/opt/oracle/product/10.2.0.3 [sp_ocap(pdb)/27485]
04/18/07 16:50 Notice: FioSetEnsure: set redolog_ensure to 1 [sp_ocap/27485]
04/18/07 16:50 Notice: Capture log parser queue size is 100000 [sp_ocap/27485]
04/18/07 16:50 Process launched: sp_ocap (for o.w229u) [pid = 27485]
04/18/07 16:50 Logging user command: oracle start capture
04/18/07 16:43 Process exited sp_ocap (for o.w229u) [pid = 26987] - exit(1)
04/18/07 16:43 Error: Unexpected Oracle error: ORA-01403: no data found. in sp_ocap.c:1758 [sp_ocap(osp)/26987]
04/18/07 16:43 Notice: ORA-01403: no data found. [sp_ocap(osp)/26987]
04/18/07 16:43 Notice: Oracle env - w229u:/opt/oracle/product/10.2.0.3 [sp_ocap(pdb)/26987]
04/18/07 16:43 Process launched: sp_ordr (for o.w229u) [pid = 27013]
04/18/07 16:43 Notice: FioSetEnsure: set redolog_ensure to 1 [sp_ocap/26987]
04/18/07 16:43 Notice: Capture log parser queue size is 100000 [sp_ocap/26987]
event_log (15/32) -
Cause
Incorrect Shareplex binaries may have been used. -
Resolution
Check to see if the correct (upgraded) Shareplex binaries are used. As a part of Oracle upgrade you must have installed the corresponding binaries for upgraded Oracle. If for some reason you are still using the old Shareplex binaries to start sp_cop, it will result in the above error.
To determine which sp_cop was used to start Shareplex, you can issue the command at OS prompt:
$ which sp_cop (where $ denotes OS prompt)
If feasible, shutdown Shareplex, run ora_cleansp and then restart Shareplex using the correct path. If ora_cleansp is not an option, you can make sure that correct binaries are used to start Shareplex and hopefully there should not be any further ORA-01403 reported by Capture. If these steps do not resolve the issue, call Support to see if there is any other workaround.