My Oracle Support Banner

Capture Process Aborts Everytime Due to Error ORA-1323 (Doc ID 273608.1)

Last updated on MARCH 07, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 10.1.0.3 [Release 10.1]
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Symptoms

 Capture process aborts everytime due to error ORA-01323, which does not help to find out the cause of the stop.

In the Alert logfile you can see something similar to the following:

Streams CAPTURE C004 started with pid=26, OS id=27280
Thu May 20 05:27:08 2004
LOGMINER: Parameters summary for session# = 43
LOGMINER: ReqParallelism = 3, EagerThreshold = 1
LOGMINER: StopMiningThreshold = 1M, MemorySize = 10M
LOGMINER: MaxLogLookback = 10M
Thu May 20 05:27:11 2004
Streams CAPTURE C004 with pid=26, OS id=27280 stopped
Thu May 20 05:27:11 2004
Errors in file /<path_name>/<trace_name>.trc:
ORA-01323: Invalid state

In the referenced capture process trace file you can see something similar to the following

*** SERVICE NAME:(SYS$USERS) 2004-05-20 05:27:11.591
*** SESSION ID:(122.428) 2004-05-20 05:27:11.591
error 1323 in STREAMS process
ORA-01323: Invalid state
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-01323: Invalid state

Changes

 Some archive log files have been moved out from the archive log dest

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.