Configuring Websphere Plugin with NAGIOS Monitoring System
1. Download WAS plugin for Nagios from here.
1. Download WAS plugin for Nagios from here.
How Grid Repository Stores Data?
The agents upload data at MGMT_METRIC_RAW table which is retained for 7 days.
Raw data are aggregated by Grid Control based on a predefined policy into 1-hour records, stored in MGMT_METRIC_1HOUR.
After 31 days or a month, 1-hour records in MGMT_METRIC_1HOUR are subject for further aggregation that rolls into 1-day records.
These 1-day records are stored in MGMT_METRIC_1Day for 365 days or 1 year before purged by Grid Control.
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.
Cloning is the process of copying an existing Oracle installation to a different location and then updating the copied installation to work in the new environment.
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
I have a 2 node RAC -DG setup between 2 remote data centres. After building DataGuard between them I am now coming across stange latency stats. Read more…
Details below are for configuring a schema level replication using API DBMS_STREAMS_ADM.MAINTAIN_SCHEMAS.
Use SQL Query below at Grid sysman database to locate growth of tablespaces over time. The returned results data could be used under EXCEL to generate graphs. Read more…
I have often used following procedure to create list of roles & corresponding users mapped into it. This was then used to email business owners as well as for user accesss auditing. Read more…
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.
ls -lt | grep "^-" | awk '{ if($8 ~ /:/) $8=2011 Date_count=$6" "$7", "$8 freq[Date_count]++} END {for (date in freq) printf "%s\t%d\n", date, freq[date] }' | sort
The streams contain following processes:
select NAME
, DBID
from RC_DATABASE;
Management Services and Repository:
Lets you monitor system performance and access diagnostic information for the Oracle Management Services and Management Repository.
If you are receiving tonnes of alerts from grid as below, here is a simple solution.
Configuration details below are for a 2 Node RAC as Primary (PROD1,PROD2) & 2 node RAC(STDBY1,STDBY2) as Physical Standby.
1) Remove the Data Guard Broker Configuration
Using the Commandline DGMGRL
SQL> show parameter dg_broker;
NAME TYPE VALUE
———————————— ———– ——————————
dg_broker_config_file1 string /mnt/data/oradata/PROD/dr1PROD.dat
dg_broker_config_file2 string /mnt/data/oradata/PROD/dr2PROD.dat
dg_broker_start boolean TRUE
I generally don’t cut and paste metalink notes. But in case you are using DG , for diagnosis you will have to use 2 metalink scripts, [ID 241438.1] & [ID 241374.1] Read more…
I generally don’t cut and paste metalink notes. But in case you are using DG , for diagnosis you will have to use 2 metalink scripts, [ID 241438.1] & [ID 241374.1] Read more…
If you can’t see directory structure properly, use this file Read more…