Standby database info in OEM's SYSMAN schema

Hi all,
I'd appreciate your help with the following question -
Where can I find the pairing between primary and standby databases in the OEM repository views (or backend tables)?
Any advice would be greatly appreciated.
Thanks in advance.

To identify the metric value of archive metrics (arch % full, etc)
SELECT target_name, metric_name, metric_column, value
FROM mgmt$metric_current
where target_type = 'oracle_database'
and metric_name like 'arch%'
If you're actually looking for the location of arch_dest, the init params are collected and stored here.
select * from mgmt$db_init_params
where name like 'log_archive%';

Similar Messages

Standby database info in OEM's repository views

Hi all,
I'd appreciate your help with the following question -
Where can I find the pairing between primary and standby databases in the OEM repository views?
Any advice would be greatly appreciated.
Thanks in advance.

Not sure about the views, but the High Availability Console has a ton of information.
Might depend some on which version of Grid Control you are using.
Best Regards
mseberg

Problem discovering 9.2.0 physical standby database in 10GR1 OEM

We have a Dataguard test setup in our company which was done using 9.2.0 OEM consisting of two 9.2.0 databases(one primary and another physical standby).
I could get the 10GR1 agent discover the primary database properly, but couldnot discover the physical standby database? The 10GR1 agent on the remote host is running fine, but just not discovers the database that is in physical standby mode and running fine.
Any suggestions???

Have you tried manually adding the standby?
Note that in grid, in the monitoring configuation screen, use the sys as sysdba account, dbsnmp doesn't have enough privileges.
Bazza

Creating Standby database in OEM 10g

DB = Oracle 10.2.0.4
OS = Solaris 10 Sparc
I am trying to create a physical standby database using the add standby database option within OEM 10g. This is something we have done numerous times before on 10g and 11g db's without a single issue, but for some reason, this time after selecting my RMAN backup location and staging area location , I am getting the following error when I click Next:
RMAN Backup Location - The specified RMAN backup is invalid. Could not identify controlfile from the backup
It is the latest backup (using RMAN catalog) from the previous evening and includes datafiles and control file.
Here is the output for List backup:
BS Key Size Device Type Elapsed Time Completion Time
1741586 7.70G DISK 00:03:26 06-DEC-12
BP Key: 1741590 Status: AVAILABLE Compressed: NO Tag: TAG20121206T220033
Piece Name: /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4811_1.bus
List of Archived Logs in backup set 1741586
Thrd Seq Low SCN Low Time Next SCN Next Time
1 20013 7974703107 04-DEC-12 7974865046 04-DEC-12
1 20014 7974865046 04-DEC-12 7975209322 05-DEC-12
1 20015 7975209322 05-DEC-12 7975792781 05-DEC-12
1 20016 7975792781 05-DEC-12 7975841363 05-DEC-12
1 20017 7975841363 05-DEC-12 7976016507 05-DEC-12
1 20018 7976016507 05-DEC-12 7976577946 06-DEC-12
1 20019 7976577946 06-DEC-12 7976685352 06-DEC-12
1 20020 7976685352 06-DEC-12 7976816259 06-DEC-12
1 20021 7976816259 06-DEC-12 7976884597 06-DEC-12
1 20022 7976884597 06-DEC-12 7977236969 06-DEC-12
1 20023 7977236969 06-DEC-12 7978009499 06-DEC-12
1 20024 7978009499 06-DEC-12 7978784609 06-DEC-12
1 20025 7978784609 06-DEC-12 7979558556 06-DEC-12
1 20026 7979558556 06-DEC-12 7980614921 06-DEC-12
1 20027 7980614921 06-DEC-12 7981238045 06-DEC-12
1 20028 7981238045 06-DEC-12 7981890156 06-DEC-12
1 20029 7981890156 06-DEC-12 7982119933 06-DEC-12
1 20030 7982119933 06-DEC-12 7982775834 06-DEC-12
1 20031 7982775834 06-DEC-12 7983388279 06-DEC-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
1741587 Full 214.09G DISK 01:15:15 06-DEC-12
List of Datafiles in backup set 1741587
File LV Type Ckp SCN Ckp Time Name
1 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/system01.dbf
2 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/undotbs01.dbf
3 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/sysaux01.dbf
4 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_indexes01.dbf
5 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_indexes02.dbf
6 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_indexes03.dbf
7 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_tables01.dbf
8 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_tables02.dbf
9 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_tables03.dbf
10 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables01.dbf
11 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables02.dbf
12 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables03.dbf
13 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables04.dbf
14 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_tables01.dbf
15 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_tables02.dbf
16 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_tables03.dbf
17 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_indexes01.dbf
18 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_indexes01.dbf
19 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/tools01.dbf
20 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_indexes02.dbf
Backup Set Copy #1 of backup set 1741587
Device Type Elapsed Time Completion Time Compressed Tag
DISK 01:15:15 06-DEC-12 NO TAG20121206T220415
List of Backup Pieces for backup set 1741587 Copy #1
BP Key Pc# Status Piece Name
1741591 1 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_1.bus
1741592 2 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_2.bus
1741593 3 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_3.bus
1741594 4 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_4.bus
1741595 5 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_5.bus
1741596 6 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_6.bus
1741597 7 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_7.bus
1741598 8 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_8.bus
1741599 9 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_9.bus
1741600 10 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_10.bus
1741601 11 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_11.bus
1741602 12 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_12.bus
1741603 13 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_13.bus
1741604 14 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_14.bus
1741605 15 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_15.bus
1741606 16 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_16.bus
1741607 17 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_17.bus
1741608 18 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_18.bus
1741609 19 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_19.bus
1741610 20 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_20.bus
1741611 21 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_21.bus
1741612 22 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_22.bus
BS Key Size Device Type Elapsed Time Completion Time
1741658 104.19M DISK 00:00:04 06-DEC-12
BP Key: 1741679 Status: AVAILABLE Compressed: NO Tag: TAG20121206T231939
Piece Name: /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4813_1.bus
List of Archived Logs in backup set 1741658
Thrd Seq Low SCN Low Time Next SCN Next Time
1 20032 7983388279 06-DEC-12 7983637536 06-DEC-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
1741702 Full 7.33M DISK 00:00:02 06-DEC-12
BP Key: 1741704 Status: AVAILABLE Compressed: NO Tag: TAG20121206T231950
Piece Name: /carebackup/oradata/CARELIVE/carelive/backup/ctlc-3640364239-20121206-00
Control File Included: Ckp SCN: 7983638867 Ckp time: 06-DEC-12
SPFILE Included: Modification time: 06-DEC-12
The only difference between creating a standby for this db and others we have created is that the file system the backups are stored on is on a non-global zone shared via nfs mount.
I know that when I try and share that filesystem with other servers I get the message:
share_nfs: Cannot share filesystems in non-global zones
If the /backup filesystem is not shared with any other servers would OEM be able to read from that NGZ? The filesystem is available to connect to using ssh from other locations, but not sure how OEM handles this part of the process.
Any advice would be great.
Regards,
JP

Thanks for the reply. I thought that is what I would need to do. However this link is very useful and could resolve the issue. I have yet to raise it with the system admin guys here yet but will do and will report back on outcome.
http://faizsulaiman.com/mount-nfs-solaris-non-global-zone/

Creating a new schema in a Logical Standby Database

Hi All,
I am experimenting with logical standby databases for the purpose of reporting, and have not been able to create a new schema in the logical standby database - one of the key features of logical standbys.
I have setup primary and logical standby databases, and they seem to be running just fine - changes are moved from the primary to the standby and queries on the standby seem to run ok.
However, If I try to create a new schema on the logical standby, that does not exist on the primary, I get "ORA-01031: insufficient privileges" errors when I try to create new objects.
Show below are the steps I have taken to create the new schema on the logical standby. Any help would be greatly appreciated.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_new
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user new
2 identified by new
3 default tablespace ts_new
4 temporary tablespace temp
5 quota unlimited on ts_new
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to new
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to new
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to new
SYS@UATDR> select * from dba_sys_privs where grantee='NEW'
2 /
GRANTEE PRIVILEGE ADM
NEW CREATE ANY TABLE NO
NEW CREATE TABLE NO
NEW UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect new/new
Connected.
NEW@UATDR>
NEW@UATDR> -- prove ability to create tables
NEW@UATDR> create table new
2 (col1 number not null)
3 tablespace ts_new
4 /
create table new
ERROR at line 1:
ORA-01031: insufficient privileges
NEW@UATDR>
NEW@UATDR>

HI Daniel,
I appreciate your quick response.
My choice of name may not have been ideal, however changing new to another name - like gav - does not solve the problem.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_gav
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user gav
2 identified by gav
3 default tablespace ts_gav
4 temporary tablespace temp
5 quota unlimited on ts_gav
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to gav
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to gav
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to gav
SYS@UATDR> select * from dba_sys_privs where grantee='GAV'
2 /
GRANTEE PRIVILEGE ADM
GAV CREATE TABLE NO
GAV CREATE ANY TABLE NO
GAV UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect gav/gav
Connected.
GAV@UATDR>
GAV@UATDR> -- prove ability to create tables
GAV@UATDR> create table gav
2 (col1 number not null)
3 tablespace ts_gav
4 /
create table gav
ERROR at line 1:
ORA-01031: insufficient privileges
GAV@UATDR>

OEM and Standby Database

I have not tried but I believe OEM does not automate creation of standby database be it physical or logical. Does it ?

I m on 10.2.0.4 , Solaris os. I saw lot of forum questions on standby databse creation where folks have run into some errors while creating the standby db. No body mentioned that they are getting into errors while creating standby db through OEM or any other kind of automation from Oracle. It seems that all of them were trying to create the standby db manually by ollowing the procedure that Oracle recommends.
Also, is data guard free ? Can I have a standby database without dataguard ? From the procedure, it looks like all you have to do is
creata a log archive destination of type service on the primary so that log can be shipped on the other side. Where does data guard comes in picture?
I am sorry if I sound dumb here but I am new to standby database and stuff like that.

Physical standby database, dblinks derived frn schemas help

I observed that many of the procedure,function,trigger of the database using dblinks which are derived from two schemas within the same database (i.e. eg: DBlink "CIS_TO_HIS" created in CISPROD schema connecting HISPROD schema of the same database). Now Oracle doesn't recommend this type of coding as a suitable.
But I am more concerned about implementing the same code over data guard in Physical standby database as it will be in read only mode and will have different TNS names entry. Therefore since database link uses TNS entry and physical standby would be using a separate TNS entry from primary, this might be a risk of transaction using those dblinks will fail. Hence can you please let me know the risk areas in physical standby of using dblink within same database?

The best solution for you is to stop using DB links between different DB schemas in the same DB.
If you do not use RAC, one workaround would be to use the loopback IP (127.0.0.1) to define your TNS connection over.
<Your DB>=
(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)
(HOST = 127.0.0.1)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = <Your DB>)))That way, if you hit the production server, the TNS will lead you to the production DB, and if you hit the standby server, you’ll go to the standby DB.
You would need to create another TNS entry for the production DB on the standby server and use it for standby replication.
Since this change might affect production operation and failover abilities, you need to thoroughly test it.
Iordan Iotzov
http://iiotzov.wordpress.com/

Creating a Physical Standby Database using OEM GC

This Paper is about the creation of a physical Stanby Database using OEM GC.
You will see that there is really nothing to it and using the Data Guard Broker, performing a switchover is as easy as 1,2,3,.
BTW, this works in both OEM GC 10.2.0.5 and 11.1
http://oemgc.wordpress.com/2010/07/19/creating-a-physical-standby-database-using-oem-gc/

Thanks Rob for sharing this.
Regards
Rajesh

How to import schema into logical standby database

i had created a new schema(A)in different database and exported the schema into a dmp file using export utility
from the exported dmp file i want to import that schema(A) into logical standby database using import utility
iam importing as system user .
i am getting the following error
IMP-00003: ORACLE error 1031 encountered
ORA-01031: insufficient privileges
can some one help what was going wrong.
thank you in advance.
kalyan

Hi kalyan,
May u plz let us know which import command you are using? kinldy check that your system user has import/export privileges?
Thanks
Hassan Khan

Monitoring Physical standby database through OEM

HI ,
We are monitoring Physical standby database through OEM and we monitor from console using SYS user
As per our company policy we change our sys password every month so after change it we need to change SYS password from console also
so is any way we can change SYS password on console using command line utility? if yes then please give us the command
Thanks

we monitor from console using SYS userYou have to monitor it using a SYSDBA user not necessarily SYS. So you can create a user e.g. SYS_MONITOR which has different policy than SYS. Although it is best to change that password on regular bases too, maybe every 3 months.
so is any way we can change SYS password on console using command line utility?I don't get your question. Are you asking if it is possible to change the monitoring username/password using some command line utility? If so, I haven't heard of such tool. But there could be a package like MGMT_TARGET which you can manipulate the credentials if you know how to use it.

Creating physical standby databases with DG Broker & OEM

Hi guys,
I manage 8i, 9i & 10g databases through OEM 10.2.0.2.
Today, I would like to create physical standby db for the most important applications. Because I'm a lazy guy, I'd like to do it the easiest way, with GUI and wizzards provided by OEM.
1. Do you know any tutorial on the Internet that would help to do it easily ? My only source up to now is the official DB broker documentation (http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/toc.htm), which is 300 pages long like every Oracle doc. I'd appreciate any tutorial that could lead me straight to the essential. I've heard that is not so tricky to create a physical standby db
2. Is the procedure really different to create (and then manage) a physical standby database on Oracle 8i, 9i and 10g ? Is it possible to do it through DB Broker and OEM for every version ?
thank you for your help
Antoine

Antionio,
Oracle Documentation is the best source of configuring any Oracle component.
But, If you do not want to read the entire doc, and want to configure Dataguard Broker (without OEM), then here is the Link.
http://www.oracledba.org/10g/dr/10gR2_dataguard_RAC_to_RAC.html#Configure_Dataguard_Broker:

OEM for physical standby database

Hello All,
I am using Oracle 11.2.0.3. My enterprise manager is db console 11.2
I have Oracle Enterprise manager dbcnsole for my RAC primary database and I have created through sqlplus command line a physical standby database.
My questions
Can I use the RAC primary dbconsole to monitor my physical standby database? if yes what the steps?
Is it mandatory to use grid control in that case? if yes, what steps are needed to implement grid control ?
Regards,

Hi,
It is not possible to monitor/administer a Logical or Physical Standby database, i.e Data Guard, using Enterprise Manager Database Control. This is primarily due to the fact that Database Control is designed to monitor 1 database and a Data Guard environment, by definition, includes more than 1 database.
If you attempt to run emca against a standby Database, you will get an error like (i.e. ORA-01219: database not open).
Database Control, can, of course, be used to monitor the current Primary database (with no ability to administer or monitor Data Guard related functionality). In such a case, when failover occurs Database Control must be reconfigured to run on the new Primary database using the commands detailed in Note 278100.1 How To Drop, Create And Recreate DB Control In A 10g Database, section C. Recreate/ReConfig DB Control, Option 2. Recreate the DB Control Configuration Files and Repository.
Enterprise Manager Grid Control or Cloud Control provides the functionality for viewing, monitoring, and administering primary and standby databases in a Data Guard configuration.
Reference: Is it Possible to Configure Database Control for a Logical or Physical Standby Database? (Doc ID 315116.1)
Using EM cloud control 12c is best available option to monitor your standby databases
For install docs refer to
http://docs.oracle.com/cd/E24628_01/install.121/e22624/toc.htm
For Software download link
http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html
Regards,
Rahul

Standby database - RMAN level 0 - Recovery catalog - OEM.

We have configured rman level 0 backup from standby database on OEM. Job is running fine, but rman is not getting connected to recovery catalog. RMAN is connecting to target control file instead of recovery catalog. I understand we need to have DG broker configured for primary and standby for RMAN to connect recovery catalog if you run from OEM. We have configured the DG broker also. DG broker configuration is woriing fine. but Still Standby is not connecting the rman recovery catalog database.
Can anyone tell me what i should check.

Catalog database is same for primary and standby. It is not working for both the version. What are all the basic check i need to do to debug the issue.
THIS IS LOG FROM OEM it is not connecting to target. instead of it is connecting to target control file.
Recovery Manager: Release 11.2.0.3.0 - Production on Thu Sep 6 22:40:28 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: CAAPRD1 (DBID=524360237, not open)
using target database control file instead of recovery catalog
RMAN>
echo set on
RMAN> run {
2> allocate channel oem_backup_disk1 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
3> allocate channel oem_backup_disk2 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
4> allocate channel oem_backup_disk3 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
5> allocate channel oem_backup_disk4 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
6> allocate channel oem_backup_disk5 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
7> allocate channel oem_backup_disk6 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
8> allocate channel oem_backup_disk7 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
9> allocate channel oem_backup_disk8 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAATB1/level0/%U';
10> backup FILESPERSET 1 as BACKUPSET tag 'DAILY_LEVL0_DATA' database;
11> backup FILESPERSET 1 as BACKUPSET tag 'DAILY_LEVL0_ARCH' archivelog all not backed up;
12> release channel oem_backup_disk1;
13> release channel oem_backup_disk2;
14> release channel oem_backup_disk3;
15> release channel oem_backup_disk4;
16> release channel oem_backup_disk5;
17> release channel oem_backup_disk6;
18> release channel oem_backup_disk7;
19> release channel oem_backup_disk8;
20> }

Can I monitor an 8i Standby Database with OEM 10gR3?

I have added the target for an 8i instance and its physical standby. The primary looks fine but the standby shows down and reports the following message:
ORA-01033: ORACLE initialization or shutdown in progress
I also notice that OEM doesn't display the type as "Database Instance:
Primary or Physical Standby" like the 9i and 10g ones we have. I have searched this forum, Metalink and the Doc library for the answer with no luck. Do you know if this is a support configuration and if so what I need to do to get it working?
Thanks.

Think grid supports 8.1.7.4 and above, check metalink for exact support details.
Have you configed the agent properly? For standby databases you need to set up the connect with sys as sysdba rather than dbsnmp.
Go to setup ---> agents
Click on the relevant agent
Select the standby database and click on configure
Edit the connection type to sysdba FIRST
then you can change the user to sys
Good luck

Standby database instance parameters in OEM repository

Hello all,
I am just wondering if someone using mgmt$db_init_params view to get information
about init parameters for standby databases in OEM (11.1.0.1)
I had problems for one of standby databases and after creation of SR was told that
dbconfig metric is not gathering that information for standby databases
Using Management Repository Views
However I have ~40 standby databases in OEM and 25 of them got entries in the view - how they got there?
And if there are any other ways to get init params for standby databases which do not
have that information in the view
Thank you,
Andrey

How are you monitoring the standby targets with sys account or dbsnmp?

Standby database info in OEM's SYSMAN schema

Similar Messages

Maybe you are looking for