Home » RDBMS Server » Enterprise Manager » Monitoring standby database using grid control (Grid control 10.2.0.3 linux)
Monitoring standby database using grid control [message #304015] Mon, 03 March 2008 13:53 Go to next message
meggens
Messages: 57
Registered: February 2007
Location: Netherlands
Member
Hi,

I'm monitoring and all my databases using grid control.
Recently I added a dataguard configuration but the standby database shows me a lot of error simple because it's in MOUNT state. Does anybody know how I should configure grid control or the standby database so the errors disappear?

Regards,
Martin
Re: Monitoring standby database using grid control [message #304170 is a reply to message #304015] Tue, 04 March 2008 07:12 Go to previous messageGo to next message
borg
Messages: 5
Registered: February 2008
Location: Indonesia
Junior Member

1. What type of standby database ? (physical standby/logical standby)
2. Can you show me alert_log/drc_log of standby database ?


Re: Monitoring standby database using grid control [message #304245 is a reply to message #304015] Tue, 04 March 2008 11:31 Go to previous messageGo to next message
meggens
Messages: 57
Registered: February 2007
Location: Netherlands
Member
Hi,

Thanks for your reply.
It's a physical standby. There's nothing wrong with the dataguard configuration, eveything works fine (the dataguard part) except that grid control give me a lot of target errors because the database is not open so the metrics can't be queried.

Grid control 'sees' the database as a physical standby database.
Are you monitoring a dataguard confguration with grid control?

Regards,
Martin
Re: Monitoring standby database using grid control [message #304322 is a reply to message #304245] Tue, 04 March 2008 20:30 Go to previous messageGo to next message
borg
Messages: 5
Registered: February 2008
Location: Indonesia
Junior Member

Dear meggens,

Yes, we also monitor dataguard using gridcontrol.

Try using sysdba(sys) or sysoper account in preffered credential for monitoring metric / reconfigure database using sysdba account.

Mounted / standby database can't be monitored by normal user.
Re: Monitoring standby database using grid control [message #304352 is a reply to message #304015] Wed, 05 March 2008 00:08 Go to previous messageGo to next message
meggens
Messages: 57
Registered: February 2007
Location: Netherlands
Member
hi,

ok, that makes sense, I'll try this. Is this documented somewhere?

Regards,
Martin
Re: Monitoring standby database using grid control [message #304416 is a reply to message #304322] Wed, 05 March 2008 01:53 Go to previous messageGo to next message
meggens
Messages: 57
Registered: February 2007
Location: Netherlands
Member
Hi,

I just checked, and I'm already monitoring as sys/sysdba.

Herewith some of the Metric Errors I see in the All Metric Errors overview.

Target Type Metric Collection Timestamp Error Type Message
STBY01.asd2lnx198 Database Instance User-Defined SQL Metrics: Age of datafile backup 03-Mar-2008 16:43:33 CET Collection Failure ORA-01033: ORACLE initial...
STBY01.asd2lnx198 Database Instance Metrics with Adaptive Thresholds 03-Mar-2008 16:43:33 CET Collection Failure ORA-01219: database not o...
STBY01.asd2lnx198 Database Instance User-Defined SQL Metrics: Age of redolog backup 03-Mar-2008 16:43:33 CET Collection Failure ORA-01033: ORACLE initial...
STBY01.asd2lnx198 Database Instance Tablespaces With Problem Segments 03-Mar-2008 16:12:50 CET Collection Failure em_error=prepare(select a...
STBY01.asd2lnx198 Database Instance mgmt_db_datafiles 03-Mar-2008 16:03:30 CET Collection Failure DBD::Oracle::db prepare f...
STBY01.asd2lnx198 Database Instance mgmt_db_tablespaces 03-Mar-2008 16:03:30 CET Collection Failure ORA-01219: database not o...
STBY01.asd2lnx198 Database Instance mgmt_db_dbNInstanceInfo 03-Mar-2008 16:03:30 CET Collection Failure ORA-01219: database not o...
STBY01.asd2lnx198 Database Instance mgmt_db_rollback_segs 03-Mar-2008 16:03:30 CET Collection Failure ORA-01219: database not o...
STBY01.asd2lnx198 Database Instance mgmt_db_options 03-Mar-2008 16:03:30 CET Collection Failure ORA-01219: database not o...
STBY01.asd2lnx198 Database Instance Tablespaces Full (dictionary managed) 03-Mar-2008 15:40:38 CET Collection Failure em_error=prepare(select t...
STBY01.asd2lnx198 Database Instance Tablespaces Full 03-Mar-2008 15:40:38 CET Collection Failure ORA-01219: database not o...
STBY01.asd2lnx198 Database Instance db_recUserSettings 03-Mar-2008 13:50:27 CET Collection Failure ORA-01219: database not o...
STBY01.asd2lnx198 Database Instance db_recSegmentSettings_sysseg 03-Mar-2008 13:50:27 CET Collection Failure Missing Properties : [SQL...
STBY01.asd2lnx198 Database Instance db_recTablespaceSettings 03-Mar-2008 13:50:27 CET Collection Failure ORA-01219: database not o...
STBY01.asd2lnx198 Database Instance db_recSegmentSettings 03-Mar-2008 13:50:27 CET Collection Failure ORA-01219: database not o...
STBY01.asd2lnx198 Database Instance Latest HDM Findings 03-Mar-2008 13:37:01 CET Collection Failure ORA-06550: line 18, colum...
STBY01.asd2lnx198 Database Instance latest_hdm_metric_helper 03-Mar-2008 13:37:01 CET Collection Failure ORA-06550: line 13, colum...
STBY01.asd2lnx198 Database Instance Segment Advisor Recommendations 03-Mar-2008 12:09:15 CET Collection Failure em_error=prepare(SELECT ...
STBY01.asd2lnx198 Database Instance mgmt_ha_backup


Regards,
Martin
Re: Monitoring standby database using grid control [message #304493 is a reply to message #304322] Wed, 05 March 2008 07:13 Go to previous messageGo to next message
meggens
Messages: 57
Registered: February 2007
Location: Netherlands
Member
Oracle support guided me to, I´m currently investigating this

Metric Collection Errors with ORA-1219 for Physical Standby Databases in Grid Control
Note:403223.1
Re: Monitoring standby database using grid control [message #563356 is a reply to message #304015] Mon, 13 August 2012 03:15 Go to previous message
David Lozano Lucas
Messages: 2
Registered: September 2009
Location: Madrid
Junior Member

I have finally found a way to monitor standby databases avoiding metric collection errors.

I created a template only for Standby with the following settings:

Metric Thresholds
Metric Comparison Operator Warning Threshold Critical Threshold Corrective Actions Collection Schedule Details
Average File Read Time (centi-seconds) > None Disabled
Average File Write Time (centi-seconds) > None Disabled
Instance Status = None Disabled
Mounted = None Disabled
Rate at which messages are getting spilled(per Sec) > None Disabled
Segments Approaching Maximum Extents Count > None Disabled
Segments Not Able to Extend Count > None Disabled
State Matches
DOWN|UNKNOWN.* Critical Only Every 5 Minutes
Status

Down None Every 5 Minutes
Streams Apply - (%) Messages in Waiting State > None Disabled
Streams Apply - (%) Spilled Messages > None Disabled
Streams Capture - (%) Spilled Messages > None Disabled
Streams - Latency (seconds) > None Disabled
Streams Process Errors > None Disabled
Streams Process Status = None Disabled
Streams Prop - (%) Messages in Waiting State > None Disabled
Streams - Throughput (messages/sec) < None Disabled
Unavailable = None Disabled
Unmounted = None Disabled

Policies (all disabled)


Policy Severity Category Collection Schedule Description Disabled Details
Default Permanent Tablespace Set to a System Tablespace Warning Storage Every 24 Hours Checks if the DEFAULT_PERMANENT_TABLESPACE database property is set to a system tablespace

Default Temporary Tablespace Set to a System Tablespace Warning Storage Every 24 Hours Checks if the DEFAULT_TEMP_TABLESPACE database property is set to a system tablespace

Dictionary Managed Tablespaces Informational Storage Every 24 Hours Checks for dictionary managed tablespaces

Non-System Data Segments in System Tablespaces Informational Storage Every 24 Hours Checks for data segments owned by non-system users located in tablespaces SYSTEM and SYSAUX

Non-System Users with System Tablespace as Default Tablespace Informational Storage Every 24 Hours Checks for non-system users using SYSTEM or SYSAUX as the default tablespace

Segment with Extent Growth Policy Violation Informational Storage Every 24 Hours Checks for segments in dictionary managed or migrated locally managed tablespaces having irregular extent sizes and/or non-zero Percent Increase settings

Tablespace Not Using Automatic Segment-Space Management Informational Storage Every 24 Hours Checks for locally managed tablespaces that are using MANUAL segment space management

Tablespaces Containing Rollback and Data Segments Informational Storage Every 24 Hours Checks for tablespaces containing both rollback and data segments

Users with Permanent Tablespace as Temporary Tablespace Informational Storage Every 24 Hours Checks for users using a permanent tablespace as the temporary tablespace



After creating the template, set it as default template and delete and re-add the databases for all the metrics are applied correctly.
Previous Topic: EM SQL & Reference Collection Problem
Next Topic: Oracle EM on a remote server
Goto Forum:
  


Current Time: Sat Dec 20 15:56:20 CST 2014

Total time taken to generate the page: 0.07804 seconds