Monitor standby database via OEM using non-sysdba account

Hi,
Is it at all possible to monitor a standby database via grid control using non-sysdba account so that targets are seen as up (green arrows visible etc)
We audit sys operations and as the SYS user is the account that currently monitors the standby we are seeing our audit file dest fill too quickly. We need to keep auditing on though.
I would like to do this using dbsnmp, though are there any roles or specific privs that need to be granted to do this? so far i am unable to do this.
Would welcome any advice on this one.
Thanks,
firefly.

Thanks for reply robert.
we are using active for one standby but not using active for 2 other standby db's.
I just wondered what the SYSDBA priv used (what actual priv etc) to be able to monitor standby dbs effectively, whereas non-SYSDBA accounts are unable to.
Thanks,
firefly

Similar Messages

  • 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.

  • How can i do this, Check to see if you have any network monitoring software that might be using your iCloud account

    How can i do this, Check to see if you have any network monitoring software that might be using your iCloud account to automatically send messages, such as firewalls or internet security software configured to send an alert when a potential security issue

    you can try:
    *Wireshark: http://www.wireshark.org/download.html

  • 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

  • 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 Standby Database from ASM Databse none ASM

    I have ASM RAC database running on Solaris 10. I want to take a backup with RMAN and move the Backup to none ASM on other Stand alone server. I want to use this none ASM backup database to create Standby Database for Test purpose. Is it doable? If it is doable can you answer following questions?
    What command should I use with RMAN to take a full backup and move it to none ASM platform?
    Thank you

    Well, the answer is most likely yes, but first need to confirm
    - Do you want a physical or logical standby?
    - Will the standby run on the same platform , i.e. also Solaris 10?
    - What version of database ? It is much easier in 11g.

  • Monitoring oracle database from OEM 12c grid control

    Hi,
    I am using OEM 12c grid control to analysis various server's performance. The application database in oracle database v11g. Is there any problem if i add database on oem to monitor? To be more clear, If it creates any conflict between database's em and oem's em when i want to deploy em agent on database ? Is it necessary to remove database's EM before installing oem agent on it?

    Rakesh,
    Please refer to the following links:
    SOA and Middleware Management
    http://www.oracle.com/technology/products/oem/prod_focus/soa_mgmt.html
    New Oracle Enterprise Manager Management Pack for SOA and Middleware Management
    http://blogs.oracle.com/oem/2009/06/new_oracle_enterprise_manager_1.html
    ORACLE ENTERPRISE MANAGER 10g: ORACLE MANAGEMENT PACK PLUS FOR SOA
    http://www.oracle.com/technology/products/oem/pdf/ds_soa_mgmt_pack.pdf
    Regards,
    Hussein

  • Updating standby database from primary using rman

    I have created a standby database using rman on my oracle linux server, now i want to update the standby from my primary database, but i didn't remember the scn which i used for creating the standby. How can i find out the scn from where i should perform the incremental backup on the primary, so that i can update my standby database with the latest information.

    You simply need to find out which logs on the Primary have yet to be applied to your Standby. Have a look at this (or any Oracle Data Guard docs.): http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/manage_ps.htm#1024046
    As long as the logs are available on the Primary server, then they should be sent across to the Standby server. Use the views described in the above link to check for any gaps, etc.

  • Create physical standby database via grid control Errror

    Hi
    I wonder if anyone has seen the following problem
    I am creating a standby database using EM Grid Control wizard. It all configures fine and starts the job goes through all steps including copying datafiles etc. but when it hits the step CREATE STANDBY DATABASE it fails with no explanation. In the oms log all it says is an error about cant find the sid name
    EM Grid COntrol is 10.2.0.5 version
    Windows Primary is Windows 2003 server 10.2.0.4 db
    Trying to create on windows 2003 server with same oracle version
    Thanks
    D

    Did you search the same on Metalink ?
    please also cehck
    EM: Creation process for a physical standby DB failed with SQL Exception
    Regards
    Rajesh

  • Can't send email via smtp on non- iCloud account

    I can send email fine via the iCloud but when trying to send using a different account via smtp it does not work and places the email in the outbox. I hope I have explained this correctly and look forward to a response, thanks

    I have an orange email account set up in addition to the iCloud .me account. When I am  in the orange email account on the apple mail program and try to send an email, it will not let me.
    Thanks for your time so far
    Edenr1

  • User blogs using non-OD accounts

    I'm attempting to deploy user blogs but all my users are currently in an external LDAP. I've been able to get authentication working so that an LDAP account can login, create a blog, and act as the owner. But any other LDAP user can login and post to the blog. The other users aren't owners, or at least they can't change any of the blog settings.
    If I create an OD user and a new blog then only the OD user can post to it.
    So has any one else run into this breakdown in permissions?
    Thanks,
    Derek

    The username section can get populated from the users that do exist on the controller.
    The second issue doesnt make much sense, you may want to open a TAC SR to investigate this further

  • Use OEM to monitor oracle database size

    Hello All,
    We currently have several database which are currently monitored via OEM however i will appreciate if anyone can tell me how i can monitor the the size of my oracle databases via oem
    Thanks

    Hi,
    I'm not sure of OEM will monitor database size, but many 3rd party tools do.
    There are many ways to achieve Oracle table monitoring, and many create specialized extension metadata tables to monitor Oracle table growth. In Oracle 10g you can perform Oracle tables monitoring with the dba_hist_seg_stat tables, specifically the space_used_total column.
    On my databases, I create STATSPACK extension tables to track table and overall database growth:
    http://www.dba-oracle.com/te_table_monitoring.htm
    The full scripts are in my Oracle Press book, Oracle tuning with STATSPACK . . .
    http://www.amazon.com/Oracle9i-High-Performance-Tuning-STATSPACK-Burleson/dp/007222360X
    Hope this helps . . .
    Donald K. Burleson
    Oracle Press author
    Author of "Oracle Tuning: The Definitive Reference"
    http://www.rampant-books.com/book_2005_1_awr_proactive_tuning.htm

  • How to monitor 8i physical standby databases ?

    Hi guys,
    It seems easy to create and monitor standby databases for 9i and 10g instances through OEM 10, but what about 8i standby db ?
    Has everything to be done manually : creation, monitoring, maintenance ?
    It is at least possible to monitor redo transport and applying for example with an older version of OEM ?
    thanks for your help
    Antoine

    10g EM is the first version, which really monitors (almost) the whole landscape. Previous versions don't deal with Dataguard configurations. 10g EM still can monitor an 8i (must be at least 8.1.7.4) database, but on a very basic level. Remember 8i is desupported for a long time now. 9i is also desupported, but many sites still use it, that can't be ignored by Oracle.
    Werner

  • 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 - 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> }

Maybe you are looking for