Tweet
The reason for the ORA-24082 error is that a message has been enqueued onto the AQ$_PROP_NOTIFY_<N> queue to notify the job_queue_process associated with the propagation schedule to stop propagating messages and the
job_queue_process has failed to acknowledge that message within a reasonable amount of time. Read more…
The state of a capture process describes what the capture process is doing currently. You can view the state of a capture process by querying the STATE column in the V$STREAMS_CAPTURE dynamic performance view. The following capture process states are possible
| CAPTURE PROCESS | |
| streams$_capture_process | Lists all defined capture processes |
| dba_capture | Basic status, error info |
| v$streams_capture | Detailed status info |
| dba_capture_parameters | Configuration information |
| PROPAGATE PROCESS | |
| streams$_propagation_process: | Lists all defined propagate processes |
| dba_propagation | Basic status, error info |
| v$propagation_sender | Detailed status info |
| v$propagation_receiver | Detailed status info |
| APPLY PROCESS | |
| streams$_apply_process | Lists all defined apply processes |
| dba_apply | Basic status, error info |
| v$streams_apply_reader | Status of the apply reader |
| v$streams_apply_server | Status of apply server(s) |
| v$streams_apply_coordinator | Overall status, latency info |
| dba_apply_parameters | Configuration information |
| Miscellaneous Tables | |
| v$buffered_queues | View that displays the current and cumulative number of messages enqueued and spilled, for each buffered queue. |
| sys.streams$_apply_spill_msgs_part | Table that the apply process uses, to “spill” messages from large transactions to disk. |
| system.logmnr_restart_ckpt$ | Table that holds capture process “checkpoint” information. |
My Capture, Propagate and apply processes were working fine until the server fial over. After a restart even though capture processes are enabled, they are stalled at status “INITIALIZING”. The Propagate and Apply were working fine.
While working with streams 10g RAC, setup went well but source database propagation process won’t work with target database “strmrepl1″ and returned TNS “12514″ error.
There are diferent ways to collect performance related data
Details below are for configuring a schema level replication using API DBMS_STREAMS_ADM.MAINTAIN_SCHEMAS.
Capture process is an optional Streams client that is an Oracle background process that scans a database redo log to capture DML and DDL changes made to database objects. Read more…
This post lists sample queries to monitor Streams queues and propagations.
1) Monitoring ANYDATA Queues and Messaging
2) Monitoring Buffered Queues
3) Monitoring Streams Propagations and Propagation Jobs
Following shell script will be handy when you are working with Streams Replication. There are 2 versions, one for 10g:monitor_streams_applyprocess_10g and another for 11g: monitor_streams_applyprocess_11g Read more…
SQL scripts below can display detailed information about error transactions in the error queue in a database.
These scripts are designed to display information about LCRs, but you can extend them to display information about any non-LCR messages used.
The streams contain following processes:
