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?

Similar Messages

Diagnosing an ASM space issue for a primary and a standby database instance with external redundancy.

I've received an alert from Enterprise manager saying "Disk Group DATA_SID requires rebalance because at least one disk
is low on space". My colleague who I would go to with this question is unavailable, so this is a learning opportunity
for me. So far google and Oracle documentation have provided lots of information, but nothing that answers my questions.
I've run the following query on both the primary and standby databases ASM instances:
select name, disk_number, sector_size,os_mb, total_mb, free_mb, redundancy from v$asm_disk;
On the primary I get 4810M Free space and 18431M Total Space
on the standby I get 1248M Free space and 18431M Total Space -- this is the one that complained via OEM
When I run the following query in the database instance:
select sum(bytes)/1024/1024 MB from dba_segments;
I get 3736.75M as a result.
My questions are:
1. Will OEM's suggestion to rebalance the disk actually help in this situation since the instance is set up with external redundancy?
2. If I've got 18G of space and only 3.7G of data, why is OEM complaining?
3. How can I reclaim what I presume is allocated but unused space in my problem disk group?
4. How can I determine what extra data the standby has that the primary doesn't since both have the same total space allocation, but different amounts of free space?

Thank you for the reply. That link is very good.
We are an 11.1 version of our database. Linus is OEL 5.6.
So, looking at the portion of the link that refers to 'Add Standby database and Instances to the OCR' - If we use SRVCTL to give the STANDBY the role of ‘physical_standby’ and the start option of ‘mount’, what effect will that have if the STANDBY becomes our PRIMARY?
Would these database settings need to be modified manually with SRVCTL each time?
We understand why the instance is not starting when the node is rebooted, we are looking for a best practice of how this is implemented.
Thank you.

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:

Creating standby database from ASM production database in standard edition

Hi,
I am using oracle 10g release 2 standard edition. I recently created a database instance and wanted to create a standby database instance. After sorting out how to achieve this without managed standby and data guard I finally got it working and the shipped archive logs are applied and working well on the standby database.
Now I am thinking of re-creating my production database and using ASM for storage managment. By doing this can a standby database still be created from a primary database using ASM? I want to be sure I can before I commit to using ASM for the production instance and manually creating a standby database from that instance.
Note: I am using standard edition not enterprise edition.

Hi
For Oracle SE standby, you can visit www.anbultechnologies.co.uk , they have a brilliant product name DRMC which is Automatic disaster recovery solution with automatic failover in case primary goes down due to any reason.
We are using this product for more than 2 years and it works like a dream using Oracle Standard Edition. We have depolyed more databases and Standby solution within the prices of 2 EE edition licenses.
You can give ma try as well.
website address is www.anbultechnologies.co.uk

Standby Database Creation in the same Box Oracle 9.2.0.1

Box - Sun Solaris 64 bit
Oracle Version - 9.2.0.1
I have a database called 'sales' in the above box. I want to create a standby database in the same box (in different mount point). This is what I did:
1. took cold backup of all datafiles
2. created standby controlfile
3. updated init file.
-when I tried to start the stabdby db, it is throwing error because the controlfile is confusing with the same db name as the primary ('sales').
My question is: Can I create a standby db in the same box?

Hello,
For keeping the standby database on same HOST....it does seems to be great...i must be on separate box....may be on different network...i believe you would be using it for some failiover purpose...Isn't it.
For Unix it is quite easy..you may implement like this...The Issue which you are referring may be because of wrong Oracle Home or SID....(i'm not very much sure..) You may try following steps:
1. Create a separate Unix A/c and set ORACLE_HOME and ORACLE_SID relevant to your StandBy Database. I believe the Home would be same whereas SID would be your standby databse.
2. Take a Cold Backup of All your database files from Production.
3. Copy these files on separate mount points for standby Db. Put them all to relevant directory and be sure to set the Group of all these files as "SYSDBA" This is Must.
4. And then modify your INIT.ORA file i.e. InitSID.ora file accordingly and put the file in ORACLE_HOME
5. Login to Newly created Unix A/c. Check whether ORACLE_SID is set ot not to your standby database instance.
6. Login to sys as sysdba and start up the database. It will by default would try to check & do for your relevant Oracle SID for this profile...
HTH
Regards,
Kamesh Rastogi

Standby database 10.2

HI , I have problem with my standby database, all parameters are good work but in my alert log file have following error;
ORA-16401: archivelog rejected by RFS, pls help me what the problem???
On Primary: spfileORCL.ora
*.control_files='/u01/oracle/oradata/orcl/control01.ctl','/u01/oracle/oradata/orcl/control02.ctl','/u01/oracle/oradata/orcl/control03.ctl'
*.db_recovery_file_dest='/u01/oracle/flash_recovery_area'
*.db_unique_name='BAKI'
*.remote_login_passwordfile='EXCLUSIVE'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(BAKI,LONDON)'
*.LOG_ARCHIVE_DEST_1='LOCATION=/u02 VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=BAKI'
*.LOG_ARCHIVE_DEST_2='SERVICE=LONDON LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=LONDON'
*.LOG_ARCHIVE_DEST_STATE_1=enable
*.LOG_ARCHIVE_DEST_STATE_2=enable
*.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
*.FAL_SERVER=LONDON
*.FAL_CLIENT=BAKI
*.STANDBY_FILE_MANAGEMENT=AUTO
*.SERVICE_NAMES=BAKI
ON my standby database spfileORCL.ora
*.control_files='/u01/oracle/oradata/orcl/stanctl.ctl'
*.db_recovery_file_dest='/u01/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.remote_login_passwordfile='EXCLUSIVE'
*.db_unique_name='LONDON'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(BAKI,LONDON)'
*.LOG_ARCHIVE_DEST_1='LOCATION=/u02 VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=BAKI'
*.LOG_ARCHIVE_DEST_2='SERVICE=BAKI LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=BAKI'
*.LOG_ARCHIVE_DEST_STATE_1=enable
*.LOG_ARCHIVE_DEST_STATE_2=enable
*.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
*.FAL_SERVER=BAKI
*.FAL_CLIENT=LONDON
*.STANDBY_FILE_MANAGEMENT=AUTO
*.SERVICE_NAMES=LONDON
all connections work well:
SQL> conn sys/sys@BAKI as sysdba
Connected.
SQL>
SQL> conn sys/sys@LONDON as sysdba
Connected.
SQL>
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
OS: SUSE 10

Primary :
alert_log:
Errors in file /u01/oracle/admin/orcl/bdump/orcl_arc0_8465.trc:
ORA-16401: archivelog rejected by RFS
orcl_arc0_8465.trc:
Error 16401 creating standby archive log file at host 'LONDON'
ORA-16401: archivelog rejected by RFS
kcrrwkx: work to do 0x2 (end)
Error 16401 creating standby archive log file at host 'LONDON'
ORA-16401: archivelog rejected by RFS
kcrrwkx: nothing to do (end)
kcrrwkx: nothing to do (end)
kcrrwkx: nothing to do (end)
*** 2009-09-08 12:32:06.342
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0xa)
tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0xa)
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x2)
tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x2)
kcrrwkx: work to do 0x2 (end)
Error 16401 creating standby archive log file at host 'LONDON'
ORA-16401: archivelog rejected by RFS
kcrrwkx: work to do 0x2 (end)
Error 16401 creating standby archive log file at host 'LONDON'
ORA-16401: archivelog rejected by RFS
kcrrwkx: nothing to do (end)
kcrrwkx: nothing to do (end)
kcrrwkx: nothing to do (end)
Standby:
alert_log
Tue Sep 8 12:19:28 2009
Errors in file /u01/oracle/admin/orcl/udump/orcl_rfs_5463.trc:
ORA-16401: archivelog rejected by RFS
RFS[4]: Archivelog thread 1 sequence 7 cannot be reused
Tue Sep 8 12:19:28 2009
Errors in file /u01/oracle/admin/orcl/udump/orcl_rfs_5463.trc:
ORA-16401: archivelog rejected by RFS
Tue Sep 8 12:19:31 2009
ARC1: Archiving not possible: No primary destinations
ARC1: Failed to archive thread 1 sequence 6 (4)
orcl_rfs_5463.trc:
ORA-16401: archivelog rejected by RFS
*** 2009-09-08 12:20:28.159
KCRRFLAS
KCRRSNPS
*** 2009-09-08 12:20:28.162 60679 kcrr.c
RFS[4]: Archivelog thread 1 sequence 6 cannot be reused
This problem can occur as the result of multiple primary and/or
standby database(s) trying to archive to this standby database.
This is not allowed, since successfully completed archivelogs
would be overwritten.
ORA-16401: archivelog rejected by RFS
*** 2009-09-08 12:20:28.165 60679 kcrr.c
RFS[4]: Archivelog thread 1 sequence 7 cannot be reused
This problem can occur as the result of multiple primary and/or
standby database(s) trying to archive to this standby database.
This is not allowed, since successfully completed archivelogs
would be overwritten.
ORA-16401: archivelog rejected by RFS

ORA-01403: no data found on LOGICAL STANDBY database

Hi ,
Logical Standby issue :
Oracle 10.2.0.2 enterprise edition .
M Working on LOGICAL Standby since 1 yrs but still i havent got this ......................................
I m getting countinuously no data foud errror on logical standby database .
I found the table causing the proble(db_logstdby_events) and skipped that table and instanciated table using bwlow package:
exec dbms_logstdby.instantiate_table (.......................................
but when i start apply process on logical standby it again give no data found for new table :
Even i tried to instantiate the table using EXPORT/IMPORT during down time but the same facing same problem .
As much as i known abt the error that is :
table1
id
10
20
30
Now if sql apply process on logical standby tries to performe the update transaction(for example) as belows
update table1 set id=100 where id=50;
above query will not be completed cos it will never find the values 50 which is not in table .Thts why this error comming ..
Now my worry is ... no users dare to change/make such changes on Logical standby .So if there is no changes in tables then sqll apply should get all the values to be needded for an update ......
watingggg guyssss/......

Troubleshooting ORA-1403 errors with Flashback Transaction
In the event that the SQL Apply engine errors out with an ORA-1403, it may be possible to utilize flashback transaction on the standby database to reconstruct the missing data. This is reliant upon the undo_retention parameter specified on the standby database instance.
ORA-1403: No Data Found
Under normal circumstances the ORA-1403 error should not be seen in a Logical Standby environment. The error occurs when data in a SQL Apply managed table is modified directly on the standby database, and then the same data is modified on the primary database.
When the modified data is updated on the primary database and received by the SQL Apply engine, the SQL Apply engine verifies the original version of the data is present on the standby database before updating the record. When this verification fails, an ORA-1403: No Data Found error is thrown by Oracle Data Guard: SQL Apply.
The initial error
When the SQL Apply engine verification fails, the error thrown by the SQL Apply engine is reported in the alert log of the logical standby database as well as a record being inserted into the DBA_LOGSTDBY_EVENTS view. The information in the alert log is truncated, while the error is reported in it's entirety in the database view.
LOGSTDBY stmt: update "SCOTT"."MASTER"
set
"NAME" = 'john'
where
"PK" = 1 and
"NAME" = 'andrew' and
ROWID = 'AAAAAAAAEAAAAAPAAA'
LOGSTDBY status: ORA-01403: no data found
LOGSTDBY PID 1006, oracle@staco03 (P004)
LOGSTDBY XID 0x0006.00e.00000417, Thread 1, RBA 0x02dd.00002221.10
The Investigation
The first step is to analyze the historical data of the table that threw the error. This can be achieved using the VERSIONS clause of the SELECT statement.
SQL> select versions_xid
, versions_startscn
, versions_endscn
, versions_operation
, pk
, name
from scott.master
versions between scn minvalue and maxvalue
where pk = 1
order by nvl(versions_startscn,0);
VERSIONS_XID VERSIONS_STARTSCN VERSIONS_ENDSCN V PK NAME
03001900EE070000 3492279 3492290 I 1 andrew
02000D00E4070000 3492290 D 1 andrew
Depending upon the amount of undo retention that the database is configured to retain (undo_retention) and the activity on the table, the information returned might be extensive and the versions between syntax might need to be changed to restrict the amount of information returned.
From the information returned, it can be seen that the record was first inserted at scn 3492279 and then was deleted at scn 3492290 as part of transaction ID 02000D00E4070000. Using the transaction ID, the database should be queried to find the scope of the transaction. This is achieved by querying the flashback_transaction_query view.
SQL> select operation
, undo_sql
from flashback_transaction_query
where xid = hextoraw('02000D00E4070000');
OPERATION UNDO_SQL
DELETE insert into "SCOTT"."MASTER"("PK","NAME") values
('1','andrew');
BEGIN
Note that there is always one row returned representing the start of the transaction. In this transaction, only one row was deleted in the master table. The undo_sql column when executed will restore the original data into the table.
SQL> insert into "SCOTT"."MASTER"("PK","NAME") values ('1','andrew');
SQL> commit;
The SQL Apply engine may now be restarted and the transaction will be applied to the standby database.
SQL> alter database start logical standby apply;

Can't connect to OEM database on server where OEM is installed?

I am trying to setup a sql script job that will connect to the database in which the OEM repository is installed and I get the following. Any suggestions?
SQL*Plus: Release 10.1.0.5.0 - Production on Mon Aug 16 09:28:37 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> SQL> SQL> SQL> ERROR:
ORA-12154: TNS:could not resolve the connect identifier specified

looks like your tnsnames.ora configuration

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

Destination database instance is 'started' not 'mounted' in standby alert.l

11.2.0.2 Physcial standby db is taking long time to startup approximately about 20 to 30 minutes. In Alert.log i am seeing continous message "destination database instance is 'started' not 'mounted'" at time of startup. Its solaris 64bit platform. Any idea whats wrong?

user530956 wrote:
11.2.0.2 Physcial standby db is taking long time to startup approximately about 20 to 30 minutes. In Alert.log i am seeing continous message "destination database instance is 'started' not 'mounted'" at time of startup. Its solaris 64bit platform. Any idea whats wrong?what parameters you been set for LOG_ARCHIVE_DEST_2 in standby instance? Disable those parameters.
Next time paste your PFILE of standby.
>
user530956
     Newbie
Handle:      user530956
Status Level:      Newbie
Registered:      Sep 15, 2006
Total Posts:      113
Total Questions:      63 (63 unresolved)
>
WOW.... Not even one question was not resolved, Sad to see that no one is helpful in OTN, then work with Support.
CLOSE THE THREADS AS ANSWERED Keep the forum clean.
Read Announcement: Forums Etiquette / Reward Points
https://forums.oracle.com/forums/ann.jspa?annID=718

OEM Repository Database Restarts Daily

Greetings,
I am running OEM 12.1.0.3.0 on a VM running Linux x86_64. The repository is Oracle 11.2.0.3.0 running on a separate VM host also running Linux x86_64.
On a daily basis at 05:57:21 (give or take a few seconds) my OEM repository is restarted -
Shutting down instance (immediate)
Stopping background process SMCO
Shutting down instance: further logons disabled
<remaining shutdown steps displayed in the alert logs>
and it immediately restarts. I am unable to determine why. The host is not restarted. I have looked at dba_jobs in the repository and see nothing running which would do this. I have looked at OEM jobs and don't see anything scheduled there which would do this. I am at a loss to explain this and am wondering if anyone else has encountered this or has an explanation. Is this expected behavior or is my setup an anomaly?
Thank you.
Bill Wagman

Bill,
This would not be an expected behaviour. If your Repository DB re-starts, then there are chances that the OMS will also re-start if it cannot access the repository DB for a long duration. This will affect console usage.
Do you not see any other errors before this shutdown?
You could also check if there are any DB trace files created around the same time.
Recommend posting this in the Database forum for further investigation.
Regards,
Smitha.

Establish Database connection to connect to OEM Repository from Agents

I have a requirement to establish Database connection from Agent through Plug-in.
Ex:
My plug-in metadata will have a perl script which gets executed in each individual agents and it should connect to the OEM Repository database to execute a package.
Your Help is Appreciable.

You would have to take in all of the information needed to connect to the database as instance properties for your target type. So each time someone creates an instance of your target type, they'd have to enter the connection details for the repository database.
The specifics of what are needed should be in the extensibility guide where the SQL fetchlet is documented.

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

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 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%';

Standby database instance parameters in OEM repository

Similar Messages

Maybe you are looking for