I have an on premise oracle 11g database that i have to migrate to an EC2 instance hosting Oracle 11g in AWS. I have three options to achieve this 1. Use Oracle Data guard to replicate the on premise database to cloud database 2. Using RMAN to backup the existing database and restore it on Cloud 3. Using expdp and impdp commands to export and import the database My database size is approximately 2 TB. I have following doubts Q1: What is the best way among the three options? Q2: Using data guard means that the AWS and the on premise database should be connected the entire time until the data is replicated on cloud, what if there is a network disconnect in between the process? Do i have to restart the replication process or will it continue from where it stopped? Edit: We have a 2 day downtime window in which the data has to be migrated and restored on cloud. The on premise database is hosted on Solaris Operating System and Operating System on the AWS cloud will be RedHat Linux since Solaris in not available in AWS. Will Oracle Data guard or RMAN support the change in the Operating system on the servers?

I have duplicated the primary database to standby database and then I added the primary database in data broker configuration. But when I'm trying to add standby database I'm getting following error: DGMGRL> add database 'orcl_standby' as connect identifier is orcl_standby maintained as physical; Error: ORA-16606: unable to find property "" Error: ORA-16554: translation not valid Failed. Is this a problem with log_archive_dest_state_2? I have enable it. Or is there any problem in DR2ORCL.DAT files? Any help will be appreciated.

I'm trying to setup data guard broker in my production instance. I have duplicated the primary database to standby database successfully. I've added primary database to data broker configuration and when I'm trying to add standby database following error is getting DGMGRL> ADD DATABASE 'orcl_standby' AS CONNECT IDENTIFIER IS orcl_standby maintained as physical; ERROR: ORA - 12154 : TNS: could not resolve the connect identifier specified Tnsping from primary db to standby db and vice-versa is successful. I'm able to connect primary db from standby db using sqlplus sys/password@orcl as sysdba but when trying to connect to standby db from primary db, error is getting like > ORA - 12154 : TNS: could not resolve the connect identifier specified. Tried out all possible solutions. Below is my tnsnames.ora file ORCL = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.25.42)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orcl) (SID = orcl) (UR = A) ) ) ORACLR_CONNECTION_DATA = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521)) ) (CONNECT_DATA = (SID = CLRExtProc) (PRESENTATION = RO) ) ) ORCL_STANDBY= (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.25.44)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orcl_standby) (SID = orcl_standby) (UR = A) ) ) Any help will be appreciated

To convert from non-CDB to cdb it's necessary to install a new instance as CDB and so, to use dbms_pdb.describe in the non-CDB database to generate a xml of the non-CDB to add as a PDB in new CDB instance. The new CDB instance in dataguard side is installed with a normal controlfile (as primary database). This mean I always need to recreate dataguard? has someone made a conversion of non-CDB to CDB in a dataguard environment?

I am new to Oracle and needing help just getting a quick script to check Oracle Dataguard. Do any of you have a simple script that could be used to just give me a quick status on dataguard? Just a quick check, if dataguard is in sync or not. I was given the below query, and it appears the script just simply tells the log gap count between the primary and stand by. Does that seem reasonable or is there a better approach? In this case, if the log gap is more than say, 3, then dataguard needs to be investigated?

select LOG_ARCHIVED-LOG_APPLIED "LOG_GAP" from
(SELECT MAX(SEQUENCE#) LOG_ARCHIVED FROM V$ARCHIVED_LOG WHERE DEST_ID=1 AND ARCHIVED='YES'),
(SELECT MAX(SEQUENCE#) LOG_APPLIED FROM V$ARCHIVED_LOG WHERE DEST_ID=2 AND APPLIED='YES');

I need to write a trigger which prevents certain users from logging into the production database. We use Active Data Guard. If I hardcode the Linux hostname in the trigger to verify the host is production, then in case of "Role Change", the trigger may not work. Correct? --- This is a three-tier system. The end users communicate via an application server, which will use a generic name. Here is a solution I had been contemplating implementing: 1. Have a table which will check for combination of user + server + database hostname (name of machine where database is hosted). 2. Have a DB_ROLE_CHANGE trigger which will get activated if the production now runs from standby 3. The DB_ROLE_TRIGGER will modify the table so that the database hostname now reflects new production server hostname 4. The APPSERVER and APPUSER will match OK. But since the hostname is now production - it will disallow login.

I have oracle database 11.2.0.3 with RAC feature , with 2 node on oracle linux 6.4 : ol6-112-rac1 and ol6-112-rac2 I want to create active data guard with RAC feature from this database , these active dataguard with rac option has 2 node : ol6-rac1-guard,ol6-rac2-guard I want to use this document for creation active data guard from rac database to rac database : http://www.oracledba.org/11gR2/dr/11gR2_dataguard_RAC_to_RAC.html#Create_Physical_Standby I do the steps in this document , all of things is ok but in step " Start the Managed Recovery Process " after i want to switch log in primary , switch log is not occurred on standby database . After " tail of alert log " on standby database and executing " Switch log " on primary , this error is occurred : tail -f /ora01/app/oracle/diag/rdbms/racguard/racguard1/trace/alert_racguard1.log Wed Feb 17 04:37:57 2016 Media Recovery Waiting for thread 1 sequence 76 Error 12154 received logging on to the standby FAL[client, USER]: Error 12154 connecting to rac for fetching gap sequence This is my mistake , can any one help me ?

We have already setup Oracle replication using Dataguard from a primary active site to a near DR site. The near DR is a passive site. Is it possible to replicate from the Near DR (Passive) site to Far DR site using dataguard?

when use data guard, primary propagate redoLog and standby apply redo log. 1. the transaction inner redo log was applied on standby will has same SCN with primary ? 2. the apply action will cause the standby's SCN increased bigger also ? thanks:)

I have an Oracle Data Guard configuration with two servers: - oradb (physical) - oradbstb (standby) Both are running with Oracle 11g R2. A few days ago I had problems with the standby (the server was turned off and the primary files were not received ... which were subsequently deleted). I would like to know how to reconfigure the standby server from scratch. What would be the steps that I must carry out? On the primary database I make a full backup with rman every Saturday and the rest of the days I make a backup of archives also with rman. How should I go about restoring my standby database again? What steps should I follow?

We have deployed an Oracle RAC cluster which consists of three Oracle instances. As we are considering the HA issue, and as far as I know, the only way of Oracle HA is DataGuard. So is it possible that we deploy DataGuard in another data center as backup for the master RAC cluster and if master RAC cluster down, We can switch the DataGuard to master which enable read and write operations. Someone told me that it is a very complicated process. Is that true? how much time does this process cost? Is there any other solutions on Oracle HA or any other load balance solution to replace RAC cluster? Does Mysql have the same capability?

I changed the SYS password on the primary and copied orapwd into the standby as documented. This approach worked fine for multiple databases, but for one standby, ORA-28000 appeared after a few minutes. Once this happened, Data Guard transport stopped and latency started to build. How can I find and eliminate the cause?

I am running my Oracle primary database instance on pod oracle-0(SID=ORCLP) and standby database instance on oracle-1 Kubernetes pod. They are connected with a headless service. data guard broker, fast_start failover all are enabled and configured properly. I am running an data guard broker observer on another pod. When I'm giving shutdown abort command from primary pod, observer is successfully failover primary to standby pod oracle-1. But when I'm deleting primary pod(SID=ORCLP) for testing purpose if observer is handling failover properly, Observer is not failover primary to standby pod. Its giving me this error log continuously:

[W000 2025-01-08T05:53:05.356+00:00] Standby is in the SUSPEND state.
[W000 2025-01-08T05:53:06.355+00:00] Primary database cannot be reached.
[W000 2025-01-08T05:53:06.355+00:00] Fast-Start Failover suspended. Reset FSFO timer.
[W000 2025-01-08T05:53:06.355+00:00] Fast-Start Failover threshold has not exceeded. Retry for the next 30 seconds
[W000 2025-01-08T05:53:07.355+00:00] Try to connect to the primary.
[P005 2025-01-08T05:53:08.044+00:00] Failed to attach to ORCLP.
ORA-12545: Connect failed because target host or object does not exist

Unable to connect to database using ORCLP

Instead of failover after failover threshold, Its continuously trying connect with deleted primary pod(SID=ORCLP). Is there anyway to solve this?

Oracle Enterprise Manager 13.5 constantly reports Error ORA-16810: multiple errors or warnings detected for the member. ... Target type=Database Instance Target name=xxxx Categories=Availability Message=The Data Guard status of xxxxxx is Error ORA-16810: multiple errors or warnings detected for the member. ... Event Type=Metric Alert Event name=dataguard:dg_status Metric Group=Data Guard Status Metric=Data Guard Status Metric value=Error ORA-16810: multiple errors or warnings detected for the member Checking dgmgrl on the target machine, the apply lag seem to be solved already. How to solve this?

I have a recently made physical dataguard configuration and everything works correctly so far, but I've noticed that the datafiles that are created in the primary are created in the standby in a different route, the environment is as follows: Primary - db_name: oradb, db_unique_name: oradb. Oracle 11gR2. ASM storage. Diskgoups: SYS, SYS2 and DATA Standby - db_name: oradb, db_unique_name: oradb2. Oracle 11gR2. ASM storage. Diskgoups: SYS, SYS2 and DATA. When creating a tablespace in the primary, example: CREATE TABLESPACE TBS_DATA DATAFILE '+DATA' SIZE 50M AUTOEXTEND ON NEXT 1M MAXSIZE 100M ... the respective datafile is created in the diskgroup DATA ... +DATA/oradb/datafile/tbs_data... all good, the doubt that I have is that I realized that in the Standby database the datafile is created in the diskgroup SYS +SYS/oradb2/datafile/tbs_data... , what should I do to create the datafiles in the correct path, that is +DATA/oradb2/datafile/tbs_data...? Thank you very much in advance

I have an Oracle 19c environment, where the primary has a standby and the standby has its own standby (Cascading DR). Somehow the standby's DR's incarnation changed to a new one. In the logs, I get this:

rfs (PID:1286351): A new recovery destination branch has been registered
 rfs (PID:1286351): Standby in the future of new recovery destination branch(resetlogs_id) 1177883943
 rfs (PID:1286351): Incomplete Recovery SCN:0x000000003b52f9a6
 rfs (PID:1286351): Resetlogs SCN:0x0000000039031be8
 rfs (PID:1286351): SBPS:0x0000000039031be5
 rfs (PID:1286351): Flashback database to SCN:0x0000000039031be5 (956505061) to follow new branch
 rfs (PID:1286351): New Archival REDO Branch(resetlogs_id): 1177883943  Prior: 1115909325
 rfs (PID:1286351): Archival Activation ID: 0x9cc516c2 Current: 0x9c3156ad
 rfs (PID:1286351): Effect of primary database OPEN RESETLOGS
 rfs (PID:1286351): Managed Standby Recovery process is active

there has been no such activity on the primary database which has resulted in such behavior. Can someone explain this?

I'm looking for information & advice on the best way to migrate from a hardware Oracle 19c Data Guard server pair to an Oracle 19c Cloud Data Guard server pair. Our configurations currently are: HW_Primary, HW_Standby - Currently Production DB Cloud_Primary, Cloud_Standby - Contains a Training DB. Currently is in use for server configuration and remote site connectivity testing. My plan at the moment is to: - Break connection between HW_Primary & HW_Standby. - Break connection between Cloud_Primary & Cloud_Standby. -Take a full backup of HW_Primary (DataPump or Level 0 Rman - preferences). - Restore to Cloud_Primary . - Bring up Cloud Primary for in-house data verification. - Restore Cloud_Standby using Recover Standby database from service Cloud_Primary. - Next would be backing up Cloud_Primary. (Side question: Is there a way to back up the Cloud_Standby while Dataguard is running?) - And finally - Reverification of the data by remote sites. I'm hoping this makes sense and will work. Please let me know what you think and feel free to make suggestions for improvement to this plan.

If I have standby which is db role is PHYSICAL STANDBY and it is MOUNTED. So, when I open it read/write the standby will be destroyed. (I have DataGuard) So, basically do I need to mount it again and start the recover process to fix it or does this envolve more steps?

Replication is working fine on the other servers, however on DB_B there's some problem; It is unable to receive archives. **Can someone help me out? If I have missed any parameters, please do let me know.** **EDIT:** Primary is DB_A and DR is DB_B Configurations on the primary

NAME               TYPE   VALUE                                                                                 
------------------ ------ ------------------------------------------------------------------------------------- 
log_archive_dest_5 string service=DB_B ASYNC valid_for=(online_logfile,all_roles) db_unique_name=DB_B 


NAME       TYPE   VALUE                              
---------- ------ ---------------------------------- 
fal_client string DB_A                            
fal_server string DB_C, DB_D, DB_E, DB_B 

NAME               TYPE   VALUE                                               
------------------ ------ --------------------------------------------------- 
log_archive_config string DG_CONFIG=(DB_C,DB_D,DB_E,DB_B,DB_A)

TNSPing also successful On DR

NAME                                 TYPE        VALUE
------------------------------------ ----------- --------------------------------
fal_client                           string      DB_B
fal_server                           string      DB_C, DB_D, DB_E, DB_A
                                                 
												 
												 
NAME                                 TYPE        VALUE
------------------------------------ ----------- --------------------------------------------------
log_archive_config                   string      dg_config=(DB_C,DB_A,DB_E,DB_D,DB_B)

**Current Environment:** - 12cR1 RAC Production Database -> Let's say PROD - 12cR1 Single Instance Physical Standby (Active Data Guard) -> Let's say DR1 **Planned Environment:** - 12cR1 RAC Production Database -> PROD (From current environment) - 12cR1 Single Instance Physical Standby (Active Data Guard) -> DR1 (From current environment) - 12cR1 RAC Physical Standby -> Let's say DR2 (New environment) - 12cR1 Single Instance Physical Standby -> Let's say DR3 (Cascaded standby to DR2) (New environment) **Important Note: data guard broker will not be used. Process will be done manually.** **Scenario:** > We want to switchover to a new physical machine. > > Physical machine and OS (OEL 8.7) installations have been completed. > (New environment) > > Oracle 19c grid software and Oracle 12cR1 database software > installations have been completed. (New environment) > > The goal here is to both move to a new physical machine and move to a > newer operating system version. After the switchover to new > environment, 12cR1 to 19c upgrade will be planned. > > A few days before the migration, the data guard installation in the > new environment will be completed. (Named DR2) > > At the same time, the installation of DR3 data guard cascaded with DR2 > will be completed a few days before the migration. (DR3) > > Thus, at the time of migration, PROD will have 2 different data guards > (DR1 and DR2). At the same time, DR3 is cascaded with DR2. > > Our purpose in doing this is to complete the migration with minimum > downtime. After switchover from PROD to DR2, we will convert DR3 from > cascaded standby to physical standby (active data guard). **Questions:** I have 2 different questions. > 1-) Is the scenario possible? While there are 2 different data guards > (DR1 and DR2) belonging to PROD, how can I determine with commands > whether switchover will be performed specifically to DR2 (without > corrupting DR1)? Actually, DR1 does not matter during the migration, > or should I remove DR1 from the data guard configuration before the > switchover? (by deleting DR1 from parameters such as dg_config, > fal_server, fal_client, log_archive_dest etc.) > > 2-) Is there any action that needs to be taken in DR3 before > performing the switchover to DR2? Because it will work as cascaded > standby until the moment of switchover. Or should I remove the > cascaded standby configuration of DR3 before performing the switchover > from PROD to DR2 and configure it as physical standby for the new PROD > (old DR2) after the switchover? After the switchover, DR2 will become > the new PROD and DR3 will become the new DR2 (active data guard)?