Why no Data Guard tools shown on EM Console?

I have successfully created a 10g(10.1.0) physical standby database a broker on OEL5.0 Linux system. Then I configured the fast_start failover and observer on the Data Guard system. But no any Data Guard tools(GUI tools) shown on EM Console. How can I use the EM Console tool to manage the Data Guard?

There is no way you can manage Dataguard from the EM Console, first of all EM is created on a per database basis. Conceptually it is impossible. What would happen if your primary database is down? So the EM repository, then how could you possibly manage the environment to perform the switch or the switch back operations?.
As you can see from EM DB Control, there it doesn't exist any Dataguard link. You must configure it by means of EM Grid Control.
~ Madrid
http://hrivera99.blogspot.com

Similar Messages

Data guard broker/manager

Good day,
My Oracle 9i do not have Data Guard Manager option in OEM console, seems it is not installed with Data Guard Broker.
Kindly guide how can I install it.
Regards
Anshuman

Thanx,
I will try to use commandline. but still any clue how can i install the graphical interface in oracle 9i or it is not availabe at all?
Regards
Message was edited by:
AnshTyagi

Why Data Pump tool cannot get in?

Why Data Pump tool cannot get in?
[oracle@hostp ~]$ impdp
Import: Release 10.2.0.1.0 - Production on Thursday, 18 September, 2008 22:30:05
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Username: system
Password:
UDI-00008: operation generated ORACLE error 1033
ORA-01033: ORACLE initialization or shutdown in progress
[oracle@hostp bdump]$ impdp sys/oracle directory='/u01/app/oracle/oradata/db10g/example01.dbf' dumpfile='dumpfile.dmp' transport_datafiles='disk1/transportdest/example01.dbf';
Import: Release 10.2.0.1.0 - Production on Thursday, 18 September, 2008 22:41:36
Copyright (c) 2003, 2005, Oracle. All rights reserved.
UDI-00008: operation generated ORACLE error 1033
ORA-01033: ORACLE initialization or shutdown in progress
Username: system
Password:
UDI-00008: operation generated ORACLE error 1033
ORA-01033: ORACLE initialization or shutdown in progress

The Oracle have finished the mounting progress. Because data file 5 is lost, it cannot be opened. Can I use impdp tool while it in the mounted condition?
SQL> startup
ORACLE instance started.
Total System Global Area 608174080 bytes
Fixed Size 1220820 bytes
Variable Size 213913388 bytes
Database Buffers 385875968 bytes
Redo Buffers 7163904 bytes
Database mounted.
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: '/u01/app/oracle/oradata/db10g/example01.dbf'
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
[oracle@hostp ~]$ impdp
Import: Release 10.2.0.1.0 - Production on Friday, 19 September, 2008 9:01:22
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Username: system
Password:
UDI-00008: operation generated ORACLE error 1033
ORA-01033: ORACLE initialization or shutdown in progress

Should e-book Data Guard Concepts and Administration be useless for us?

I think The Data Guard Broker is an easy and efficient way to manage a Data Guard configuration. The Data Guard Broker provides us with two efficient tools: EM Console and DGMGRL. We can do everything we want for Data Guard system.
Why we spend so much time to read Oracle e-book Data Guard Concepts and Administration? I think it is useless. Only Broker is enough?

Frank,
The thing is GUI tool itself is also program that need some one to manage. The developer of such tools cannot take care unlimited possibilities in the real world.
Just check how many threads in this forum about why emca, dbca and EM console not working.
Being a DBA, we should understand the underlying technology that driven the system. It's like driving a car. A regular customer could say I don't care about mechanics of a car. As long as it's running, that's enough. But we are not regular customer, we suppose to be the auto repair mechanician in Oracle world. We could enjoy driving a car, but at same time we should know why and how it's working.

Data Guard ora-00314 and ora-00312

Good afternoon. Please, I have configured a data guard on the same server and am sure the files are well configured as
*.db_file_name_convert='C:\Oracle\product\10.2.0\oradata\test2','C:\Oracle\product\10.2.0\oradata\test1'
log_file_name_convert='C:\Oracle\product\10.2.0\oradata\test2','C:\Oracle\product\10.2.0\oradata\test1'
Thanks

The Primary database was OK before I start the Standby database. I've tried many times but failed to open the Primary database after I successfuly created and opened the Standby database. Did the Standby database crash the redo log of Primary? Why?
Error shown when I want to open the Primary database:
ORA-00314: log 2 of thread 1, expected sequence# 11 doesn't match 0
ORA-00312: online log 2 thread 1: '/u01/oradata/DB01/redo_log02.dbf'Part of my initDB01.ora
DB_NAME=DB01
DB_UNIQUE_NAME=DB01
LOG_ARCHIVE_CONFIG='DG_CONFIG=(DB01,DB02)'
LOG_ARCHIVE_DEST_1=
'LOCATION=/u01/oradata/DB01/arc/ MANDATORY
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=DB01'
LOG_ARCHIVE_DEST_2=
'SERVICE=DB02
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=DB02'
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
LOG_ARCHIVE_MAX_PROCESSES=30
FAL_SERVER=DB02
FAL_CLIENT=DB01
DB_FILE_NAME_CONVERT='/u01/oradata/DB02/','/u01/oradata/DB01/'
LOG_FILE_NAME_CONVERT='/u01/oradata/DB02/arc/','/u01/oradata/DB01/arc/'
STANDBY_FILE_MANAGEMENT=AUTO
Part of my initDB02.ora
CONTROL_FILES='/opt/oracle/oradata/DB02/control_primary.ctl'
DB_NAME=DB01
DB_UNIQUE_NAME=DB02
LOG_ARCHIVE_CONFIG='DG_CONFIG=(DB01,DB02)'
LOG_ARCHIVE_DEST_1=
'LOCATION=/u01/oradata/DB02/arc/ MANDATORY
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=DB02'
LOG_ARCHIVE_DEST_2=
'SERVICE=DB01
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=DB01'
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
STANDBY_FILE_MANAGEMENT=AUTO
FAL_SERVER=DB01
FAL_CLIENT=DB02
DB_FILE_NAME_CONVERT='/u01/oradata/DB01/','/u01/oradata/DB02/'
LOG_FILE_NAME_CONVERT='/u01/oradata/DB01/arc/','/u01/oradata/DB02/arc/'

Clarification on Data Guard(Physical Standyb db)

Hi guys,
I have been trying to setup up Data Guard with a physical standby database for the past few weeks and I think I have managed to setup it up and also perform a switchover. I have been reading a lot of websites and even Oracle Docs for this.
However I need clarification on the setup and whether or not it is working as expected.
My environment is Windows 32bit (Windows 2003)
Oracle 10.2.0.2 (Client/Server)
2 Physical machines
Here is what I have done.
Machine 1
1. Create a primary database using standard DBCA, hence the Oracle service(oradgp) and password file are also created along with the listener service.
2. Modify the pfile to include the following:-
oradgp.__db_cache_size=436207616
oradgp.__java_pool_size=4194304
oradgp.__large_pool_size=4194304
oradgp.__shared_pool_size=159383552
oradgp.__streams_pool_size=0
*.audit_file_dest='M:\oracle\product\10.2.0\admin\oradgp\adump'
*.background_dump_dest='M:\oracle\product\10.2.0\admin\oradgp\bdump'
*.compatible='10.2.0.3.0'
*.control_files='M:\oracle\product\10.2.0\oradata\oradgp\control01.ctl','M:\oracle\product\10.2.0\oradata\oradgp\control02.ctl','M:\oracle\product\10.2.0\oradata\oradgp\control03.ctl'
*.core_dump_dest='M:\oracle\product\10.2.0\admin\oradgp\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='oradgp'
*.db_recovery_file_dest='M:\oracle\product\10.2.0\flash_recovery_area'
*.db_recovery_file_dest_size=21474836480
*.fal_client='oradgp'
*.fal_server='oradgs'
*.job_queue_processes=10
*.log_archive_dest_1='LOCATION=E:\ArchLogs VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=oradgp'
*.log_archive_dest_2='SERVICE=oradgs LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=oradgs'
*.log_archive_format='ARC%S_%R.%T'
*.log_archive_max_processes=30
*.nls_territory='IRELAND'
*.open_cursors=300
*.pga_aggregate_target=203423744
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=612368384
*.standby_file_management='auto'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='M:\oracle\product\10.2.0\admin\oradgp\udump'
*.service_names=oradgp
The locations on the harddisk are all available and archived redo are created (e:\archlogs)
3. I then add the necessary (4) standby logs on primary.
4. To replicate the db on the machine 2(standby db), I did an RMAN backup as:-
RMAN> run
{allocate channel d1 type disk format='M:\DGBackup\stby_%U.bak';
backup database plus archivelog delete input;
5. I then copied over the standby~.bak files created from machine1 to machine2 to the same directory (M:\DBBackup) since I maintained the directory structure exactly the same between the 2 machines.
6. Then created a standby controlfile. (At this time the db was in open/write mode).
7. I then copied this standby ctl file to machine2 under the same directory structure (M:\oracle\product\10.2.0\oradata\oradgp) and replicated the same ctl file into 3 different files such as: CONTROL01.CTL, CONTROL02.CTL & CONTROL03.CTL
Machine2
8. I created an Oracle service called the same as primary (oradgp).
9. Created a listener also.
9. Set the Oracle Home & SID to the same name as primary (oradgp) <<<-- I am not sure about the sid one.
10. I then copied over the pfile from the primary to standby and created an spfile with this one.
It looks like this:-
oradgp.__db_cache_size=436207616
oradgp.__java_pool_size=4194304
oradgp.__large_pool_size=4194304
oradgp.__shared_pool_size=159383552
oradgp.__streams_pool_size=0
*.audit_file_dest='M:\oracle\product\10.2.0\admin\oradgp\adump'
*.background_dump_dest='M:\oracle\product\10.2.0\admin\oradgp\bdump'
*.compatible='10.2.0.3.0'
*.control_files='M:\oracle\product\10.2.0\oradata\oradgp\control01.ctl','M:\oracle\product\10.2.0\oradata\oradgp\control02.ctl','M:\oracle\product\10.2.0\oradata\oradgp\control03.ctl'
*.core_dump_dest='M:\oracle\product\10.2.0\admin\oradgp\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='oradgp'
*.db_recovery_file_dest='M:\oracle\product\10.2.0\flash_recovery_area'
*.db_recovery_file_dest_size=21474836480
*.fal_client='oradgs'
*.fal_server='oradgp'
*.job_queue_processes=10
*.log_archive_dest_1='LOCATION=E:\ArchLogs VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=oradgs'
*.log_archive_dest_2='SERVICE=oradgp LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=oradgp'
*.log_archive_format='ARC%S_%R.%T'
*.log_archive_max_processes=30
*.nls_territory='IRELAND'
*.open_cursors=300
*.pga_aggregate_target=203423744
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=612368384
*.standby_file_management='auto'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='M:\oracle\product\10.2.0\admin\oradgp\udump'
*.service_names=oradgs
log_file_name_convert='junk','junk'
11. User RMAN to restore the db as:-
RMAN> startup mount;
RMAN> restore database;
Then RMAN created the datafiles.
12. I then added the same number (4) of standby redo logs to machine2.
13. Also added a tempfile though the temp tablespace was created per the restore via RMAN, I think the actual file (temp01.dbf) didn't get created, so I manually created the tempfile.
14. Ensuring the listener and Oracle service were running and that the database on machine2 was in MOUNT mode, I then started the redo apply using:-
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
It seems to have started the redo apply as I've checked the alert log and noticed that the sequence# was all "YES" for applied.
****However I noticed that in the alert log the standby was complaining about the online REDO log not being present****
So copied over the REDO logs from the primary machine and placed them in the same directory structure of the standby.
########Q1. I understand that the standby database does not need online REDO Logs but why is it reporting in the alert log then??########
I wanted to enable realtime apply so, I cancelled the recover by :-
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
and issued:-
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
This too was successful and I noticed that the recovery mode is set to MANAGED REAL TIME APPLY.
Checked this via the primary database also and it too reported that the DEST_2 is in MANAGED REAL TIME APPLY.
Also performed a log swith on primary and it got transported to the standby and was applied (YES).
Also ensured that there are no gaps via some queries where no rows were returned.
15. I now wanted to perform a switchover, hence issued:-
Primary_SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
All the archivers stopped as expected.
16. Now on machine2:
Stdby_SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
17. On machine1:
Primary_Now_Standby_SQL>SHUTDOWN IMMEDIATE;
Primary_Now_Standby_SQL>STARTUP MOUNT;
Primary_Now_Standby_SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
17. On machine2:
Stdby_Now_Primary_SQL>ALTER DATABASE OPEN;
Checked by switching the logfile on the new primary and ensured that the standby received this logfile and was applied (YES).
However, here are my questions for clarifications:-
Q1. There is a question about ONLINE REDO LOGS within "#" characters.
Q2. Do you see me doing anything wrong in regards to naming the directory structures? Should I have renamed the dbname directory in the Oracle Home to oradgs rather than oradgp?
Q3. When I enabled real time apply does that mean, that I am not in 'MANAGED' mode anymore? Is there an un-managed mode also?
Q4. After the switchover, I have noticed that the MRP0 process is "APPLYING LOG" status to a sequence# which is not even the latest sequence# as per v$archived_log. By this I mean:-
SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS,FROM V$MANAGED_STANDBY;
MRP0 APPLYING_LOG 1 47 452 1024000
but :
SQL> select max(sequence#) from v$archived_log;
46
Why is that? Also I have noticed that one of the sequence#s is NOT applied but the later ones are:-
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
42 NO
43 YES
44 YES
45 YES
46 YES
What could be the possible reasons why sequence# 42 didn't get applied but the others did?
After reading several documents I am confused at this stage because I have read that you can setup standby databases using 'standby' logs but is there another method without using standby logs?
Q5. The log switch isn't happening automatically on the primary database where I could see the whole process happening on it own, such as generation of a new logfile, that being transported to the standby and then being applied on the standby.
Could this be due to inactivity on the primary database as I am not doing anything on it?
Sorry if I have missed out something guys but I tried to put in as much detail as I remember...
Thank you very much in advance.
Regards,
Bharath
Edited by: Bharath3 on Jan 22, 2010 2:13 AM

Parameters:
Missing on the Primary:
DB_UNIQUE_NAME=oradgp
LOG_ARCHIVE_CONFIG=DG_CONFIG=(oradgp, oradgs)
Missing on the Standby:
DB_UNIQUE_NAME=oradgs
LOG_ARCHIVE_CONFIG=DG_CONFIG=(oradgp, oradgs)
You said: Also added a tempfile though the temp tablespace was created per the restore via RMAN, I think the actual file (temp01.dbf) didn't get created, so I manually created the tempfile.
RMAN should have also added the temp file. Note that as of 11g RMAN duplicate for standby will also add the standby redo log files at the standby if they already existed on the Primary when you took the backup.
You said: ****However I noticed that in the alert log the standby was complaining about the online REDO log not being present****
That is just the weird error that the RDBMS returns when the database tries to find the online redo log files. You see that at the start of the MRP because it tries to open them and if it gets the error it will manually create them based on their file definition in the controlfile combined with LOG_FILE_NAME_CONVERT if they are in a different place from the Primary.
Your questions (Q1 answered above):
You said: Q2. Do you see me doing anything wrong in regards to naming the directory structures? Should I have renamed the dbname directory in the Oracle Home to oradgs rather than oradgp?
Up to you. Not a requirement.
You said: Q3. When I enabled real time apply does that mean, that I am not in 'MANAGED' mode anymore? Is there an un-managed mode also?
You are always in MANAGED mode when you use the RECOVER MANAGED STANDBY DATABASE command. If you use manual recovery "RECOVER STANDBY DATABASE" (NOT RECOMMENDED EVER ON A STANDBY DATABASE) then you are effectively in 'non-managed' mode although we do not call it that.
You said: Q4. After the switchover, I have noticed that the MRP0 process is "APPLYING LOG" status to a sequence# which is not even the latest sequence# as per v$archived_log. By this I mean:-
Log 46 (in your example) is the last FULL and ARCHIVED log hence that is the latest one to show up in V$ARCHIVED_LOG as that is a list of fully archived log files. Sequence 47 is the one that is current in the Primary online redo log and also current in the standby's standby redo log and as you are using real time apply that is the one it is applying.
You said: What could be the possible reasons why sequence# 42 didn't get applied but the others did?
42 was probably a gap. Select the FAL columns as well and it will proably say 'YES' for FAL. We do not update the Primary's controlfile everytime we resolve a gap. Try the same command on the standby and you will see that 42 was indeed applied. Redo can never be applied out of order so the max(sequence#) from v$archived_log where applied = 'YES' will tell you that every sequence before that number has to have been applied.
You said: After reading several documents I am confused at this stage because I have read that you can setup standby databases using 'standby' logs but is there another method without using standby logs?
Yes, If you do not have standby redo log files on the standby then we write directly to an archive log. Which means potential large data loss at failover and no real time apply. That was the old 9i method for ARCH. Don't do that. Always have standby redo logs (SRL)
You said: Q5. The log switch isn't happening automatically on the primary database where I could see the whole process happening on it own, such as generation of a new logfile, that being transported to the standby and then being applied on the standby.
Could this be due to inactivity on the primary database as I am not doing anything on it?
Log switches on the Primary happen when the current log gets full, a log switch has not happened for the number of seconds you specified in the ARCHIVE_LAG_TARGET parameter or you say ALTER SYSTEM SWITCH LOGFILE (or the other methods for switching log files. The heartbeat redo will eventually fill up an online log file but it is about 13 bytes so you do the math on how long that would take :^)
You are shipping redo with ASYNC so we send the redo as it is commited, there is no wait for the log switch. And we are in real time apply so there is no wait for the log switch to apply that redo. In theroy you could create an online log file large enough to hold an entire day's worth of redo and never switch for the whole day and the standby would still be caught up with the primary.

Data Guard configuration for RAC database disappeared from Grid control

Primary Database Environment - Three node cluster
RAC Database 10.2.0.1.0
Linux Red Hat 4.0 2.6.9-22 64bit
ASM 10.2.0.1.0
Management Agent 10.2.0.2.0
Standby Database Environment - one Node database
Oracle Enterprise Edition 10.2.0.1.0 Single standby
Linux Red Hat 4.0 2.6.9-22 64bit
ASM 10.2.0.1.0
Management Agent 10.2.0.2.0
Grid Control 10.2.0.1.0 - Node separate from standby and cluster environments
Oracle 10.1.0.1.0
Grid Control 10.2.0.1.0
Red Hat 4.0 2.6.9-22 32bit
After adding a logical standby database through Grid Control for a RAC database, I noticed sometime later the Data Guard configuration disappeared from Grid Control. Not sure why but it is gone. I did notice that something went wrong with the standby creation but i did not get much feedback from Grid Control. The last thing I did was to view the configuration, see output below.
Initializing
Connected to instance qdcls0427:ELCDV3
Starting alert log monitor...
Updating Data Guard link on database homepage...
Data Protection Settings:
Protection mode : Maximum Performance
Log Transport Mode settings:
ELCDV.qdx.com: ARCH
ELXDV: ARCH
Checking standby redo log files.....OK
Checking Data Guard status
ELCDV.qdx.com : ORA-16809: multiple warnings detected for the database
ELXDV : Creation status unknown
Checking Inconsistent Properties
Checking agent status
ELCDV.qdx.com
qdcls0387.qdx.com ... OK
qdcls0388.qdx.com ... OK
qdcls0427.qdx.com ... OK
ELXDV ... WARNING: No credentials available for target ELXDV
Attempting agent ping ... OK
Switching log file 672.Done
WARNING: Skipping check for applied log on ELXDV : disabled
Processing completed.
Here are the steps followed to add the standby database in Grid Control
Maintenance tab
Setup and Manage Data Guard
Logged in as sys
Add standby database
Create a new logical standby database
Perform a live backup of the primary database
Specify backup directory for staging area
Specify standby database name and Oracle home location
Specify file location staging area on standby node
At the end am presented with a review of the selected options and then the standby database is created
Has any body come across a similar issue?
Thanks,

Any resolution on this?
I just created a Logical Standby database and I'm getting the same warning (WARNING: No credentials available for target ...) when I do a 'Verify Configuration' from the Data Guard page.
Everything else seems to be working fine. Logs are being applied, etc.
I can't figure out what credentials its looking for.

Best Practice for monitoring database targets configured for Data Guard

We are in the process of migrating our DB targets to 12c Cloud Control.
In our current 10g environment the Primary Targets are monitored and administered by OEM GC A, and the Standby Targets are monitored by OEM GC B. Originally, I believe this was because of proximity and network speed, and over time it evolved to a Primary/Standby separation. One of the greatest challenges in this configuration is keeping OEM jobs in sync on both sides (in case of switchover/failover).
For our new OEM CC environment we are setting up CC A and CC B. However, I would like to determine if it would be smarter to monitor all DB targets (Primary and Standby) from the same CC console. In other words, monitor and administer DB Primary and Standby from the same OEM CC Console. I am trying to determine the best practice. I am not sure if administering a swichover from Cloud Control from Primary to Standby requires that both targets are monitored in the same environment or not.
I am interested in feedback. I am also interested in finding good reference materials (I have been looking at Oracle documentation and other documents online). Thanks for your input and thoughts. I am deliberately trying to keep this as concise as possible.

OMS is a tool it is not need to monitor your primary and standby what is what I meant by the comment.
The reason you need the same OMS to monitor both the primary and the standby is in the Data Guard administration screen it will show both targets. You also will have the option of doing switch-overs and fail-overs as well as convert the primary or standby. One of the options is also to move all the jobs that are scheduled with primary over to the standby during a switch-over or fail-over.
There is no document that states that you need to have all targets on one OMS but that is the best method for the reason of having OMS. OMS is a tool to have all targets in a central repository. If you start have different OMS server and OMS repository you will need to log into separate OMS to administrator the targets.

Urgent : ORA-01426: numeric overflow on oracle 11g Active Data Guard

Hi
I have configured Active Data Guard on oracle 11g, for reporting purpose we will select mutliple querry on target side(10 users). we are getting 'numeric overflow erro'r on alert log file When we issuing multiple query on target side. PLeae let me know is this error will cause performance degrad. if it will degrade performance mean please tell me how to resolve this problem. Why the numeric overflow is comming . and it is not comming in the primary database, it is comming in standby database only. please any one help it is very urgent
is there any parameter To overcome this problme
Please please it is very important to me and very urgent .
Thanks
nafees
Edited by: Nafees on Jan 1, 2009 3:44 AM
Edited by: Nafees on Jan 1, 2009 3:54 AM

There is no one drowning.
Your house is not on fire.
The volcano has not exploded.
Please apologize for abusing this forum by claiming your issue is more urgent than other people's requests.
Then, and only then, should anyone help you. I know I certainly won't until I read your sincere apology and promise not to be abusive in the future.

Where to download EH&S Data Editor tool

Hi,
I know EH&S Data Editor tool is not more available to download from TechniData ftp site. Do you know where can I download EH&S Data Editor tool in SAP Service Marketplace or TechniData site?
Thanks,
KC

Mark,
Somebody of my team would like to use this tool within the scope of a PLM project (for initial data load).
Of course I will contact my SAP service account manager but it should be useful to explain to the community (do not need all thedetails) why this product is not sold anymore (after Technidata acquisition).
Does it mean that there is a similar, equivalent solution within the SAP product portfolio (Business Objects) area for example ?
Thanks beforehand.

Data Guard

I have configured physical standby data guard on two different physical machines on oracle 10g. Log shipping is working fine. All the arch log generated on primary server is shipped to standby server successfully . On standby server, applied column shows 'YES' when queried from v$archived_log for all the logs. There are no errors in alert log on both the primary and standby servers.
Then,
When I check switchover_status on standby server i, why does it shows 'NOT ALLOWED' ?

SWITCHOVER_STATUS Column Indicates whether switchover is allowed and it can following information,
_NOT ALLOWED - Either this is a standby database and the primary database has not been switched first_ or this is a primary database and there are no standby databases.
SESSIONS ACTIVE - Indicates that there are active SQL sessions attached to the primary or standby database that need to be disconnected before the switchover operation is permitted. Query the V$SESSION view to identify the specific processes that need to be terminated.
SWITCHOVER PENDING - This is a standby database and the primary database switchover request has been received but not processed.
SWITCHOVER LATENT - The switchover was in pending mode, but did not complete and went back to the primary database.
TO PRIMARY - This is a standby database and is allowed to switch over to a primary database.
TO STANDBY - This is a primary database and is allowed to switch over to a standby database.
RECOVERY NEEDED - This is a standby database that has not received the switchover request.
Thanks

Some queries on Data Guard design

Hi, I have some basic questions around Data Guard design
Q1. Looking at the Oracle instructions for creating a logical standby, it firstly advocates creating a physical standby and then converting it to a logical standby. However I thought a logical standby could have a completely different physical structure from the primary. How can this be the case if a logical standby first starts its life as a physical standby ( where structure needs to be identical ) ?
Q2. Is it normal practice to backup your standby database as well – if so why ?
Q3. Can RMAN backup a Standby Database whilst it is in the mounted state ( rather than open ) ?
Q4. What's the point of Cascaded Redo Apply rather than simply getting the Primary to ship to each Standby ?
I guess you could be trying to reduce node to node latency if some of the standby were quite distant from the primary
Q5. Is it possible to convert a Logical Standby back to a Physical one ?
Q6. What the maximium number of standbys you can have - Oracle suggests 30 but I thought I remember reading somewhere in relation to 11gR2 that this limit has now been increased ?
thanks,
Jim

Hi,
Q5 . Is it possible to convert a Logical Standby back to a Physical one ? --- Yes it is possible .
-- Primary
select switchover_status from v$database;
SWITCHOVER_STATUS
SESSIONS ACTIVE
2) switch operation
-- Primary - starat database switch
alter database commit to switchover to physical standby with session shutdown;
-- see alertlog.
Switchover: Complete - Database shutdown required
Completed: alter database commit to switchover to physical standby with session shutdown
-- database role ve switchover_status
select NAME,OPEN_MODE,DATABASE_ROLE,SWITCHOVER_STATUS,PROTECTION_MODE,PROTECTION_LEVEL from v$database;
NAME      OPEN_MODE            DATABASE_ROLE    SWITCHOVER_STATUS    PROTECTION_MODE      PROTECTION_LEVEL
TESTCRD   READ WRITE           PHYSICAL STANDBY RECOVERY NEEDED      MAXIMUM AVAILABILITY UNPROTECTED
-- Primary
shutdown abort
-- standby - switch to primary
alter database commit to switchover to primary with session shutdown;
-- alert log
Completed: alter database commit to switchover to primary with session shutdown
alter database open
3) Old Primary open
sqlplus / as sysdba
startup nomount
alter database mount standby database
-- database role ve switchover_status
select NAME,OPEN_MODE,DATABASE_ROLE,SWITCHOVER_STATUS,PROTECTION_MODE,PROTECTION_LEVEL from v$database;
NAME      OPEN_MODE            DATABASE_ROLE    SWITCHOVER_STATUS    PROTECTION_MODE      PROTECTION_LEVEL
TESTCRD   READ WRITE           PHYSICAL STANDBY RECOVERY NEEDED      MAXIMUM AVAILABILITY UNPROTECTED
recover managed standby database using current logfile disconnect from session;
4) Old standby
SQL> select NAME,OPEN_MODE,DATABASE_ROLE,SWITCHOVER_STATUS,PROTECTION_MODE,PROTECTION_LEVEL from v$database;
NAME      OPEN_MODE            DATABASE_ROLE    SWITCHOVER_STATUS    PROTECTION_MODE      PROTECTION_LEVEL
AZKKDB    READ WRITE           PRIMARY          TO STANDBY           MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE
Q2 . . Is it normal practice to backup your standby database as well – if so why ?
Hence you only have to backup one of the both (you can decide to only backup the standby though, if you want to remove load on the primary). But if you are confident with the backup of the primary, there is no need for backing up the standby. (Since you can recreate the standby with the backup from primary).
Please see link : http://blog.dbvisit.com/rman-backups-on-your-standby-database-yes-it-is-easy/
Thank you

Steps for data guard RAC primary RAC standby

Hi,
I have some doubt in configuring data guard for rac DR to rac primary.
1) In RAC DR, physical standby will be in RAC before starting data guard for RAC Primary , right?.
2) While configuring RAC DR , should one node be down in standby?.
3) After creating the auxiliary database in standby, i mean restoring the rman backup from staging directory in DR,
Shall we have to register the services(database,instance,asm,etc..) to CRS(OCR)?. If yes ,Why?.
4) After DR configure over , Shall i shut/down one node?. Should all the nodes in DR be in up , while applying logs to
standby ?.
If anybody have made the setup and have the prepared document , requesting you to share with me.
Thank you very much,
Sunand

Hi Sunand,
Please follow the following My Oracle Support (MOS) Document ID:
MAA - Creating a RAC Physical Standby for a RAC Primary [ID 380449.1]
For further details, see the referred documents in previous post. Try practicing on VMWare because it will give you the flexibility for creating snapshots to save your work. Please see the answers for your question below:
Q1. In RAC DR, physical standby will be in RAC before starting data guard for RAC Primary , right?.
Answer: Yes, this is recommend but not mandatory. You can add a second node later on.
Q2. While configuring RAC DR , should one node be down in standby?
Answer: Yes, there are some database configuration commands that should be run in exclusive mode. You can start the remaining instance(s) after DB creation. Do not forget to set CLUSTER_DATABASE parameter to TRUE. Also, all instances except one should be close while performing switchover/failover.
Q3. After creating the auxiliary database in standby, i mean restoring the rman backup from staging directory in DR, Shall we have to register the services(database,instance,asm,etc..) to CRS(OCR)?. If yes ,Why?
Answer: Yes, this is recommended for RAC configuration to take advantage of high availability services.
Q4. After DR configure over , Shall i shut/down one node?. Should all the nodes in DR be in up , while applying logs to
standby ?
Answer: You can start up all the instances after DR creation. In this case if your one node goes down log apply services will continue to apply changes in DR.
Hope, this helps to clear your questions.
Regards,
Shahid

Anyone Here want a Data Guard Certification?

There is a Oracle RAC Certfied Expert Certification . . . Why not one for Data Guard?
It would be nice for those of us who have spent time with Data Guard
Post a comment and let's see if they will make one.

OCP is meaningless. You wouldn't go to a dentist who got their degree with a multiple choice test with so low a bar to passing. Or an attorney, or a surgeon. Why is OCP acceptable as a criterion for anything other than private schools to make money?
To be meaningful a certification must be hands-on and must include proving competence. If you can not build a 3 node RAC cluster, unaided, you should not get the piece of paper.

Data Guard Logical Standby DB Questions

Hi,
I am creating Oracle 9i Logical Standby database on AIX 5 on same server ( for
testing only ).
In Data Guard Manual ( PDF file page no : 86 ) it is said that
Step 4 Create a backup copy of the control file for the standby database. On the
primary database, create a backup copy of the control file for the standby database:
SQL> ALTER DATABASE BACKUP CONTROLFILE TO
2> '/disk1/oracle/oradata/payroll/standby/payroll3.ctl';
My Questions regarding this are
1. Does it missing "backup standby controlfile" word ? if not what is the use of
this control file ? Because as per this manual section 4.2.2 step no 1 and 2 I
have stopped the primary database and copied datafiles,logfiles and controlfiles
as specified which are having consistent stage.
2. On primary database I am mirroring 2 controlfiles at two diffrent locations.
On Standby Database I am going to keep same policy. Then on standby database do I have to copy this controlfile to two locations and rename datafiles or I have
to user controlfiles which I have backed up along with datafiles ?
3. Suppose my primary database is "infod" and standby database is "standby".
Then what should be value of log_file_format parameter of standby database ? On
primary db I have defined "infod LOG_ARCHIVE_FORMAT=infod_log%s_%t.arc. Do I have to keep same or change it ? If on standby db I change the value do I
require other parameters to be set ?
regards & thanks
pjp

Q/A1) Its correct you dont need the standby keyword. Not sure abut the reason why but we have created logical standby running in prod using the oracle doc.
Q/A2) Yo can specify any location and name for your controlfiles as it is instance specific and not depending on primary database.
Q/A3) You can set any format for your archlogs on standby side. It doesnt bother the primary db or DG configuration.
Regards,
http://askyogesh.com

Why no Data Guard tools shown on EM Console?

Similar Messages

Maybe you are looking for