Oracle DB RAC 3 Node DR Configuration Steps Summary : This document provides a comprehensive step-by-step guide to configure a 3-node Oracle RAC Data Guard disaster recovery (DR) environment. It covers prerequisites, configuration details, and validation procedures for setting up a physical standby database in a RAC environment. Key steps include enabling force logging and archivelog mode, creating and modifying parameter files and standby redo logs, and performing an RMAN backup and duplication for standby creation. · Detailed instructions for ASM directory setup, password file copying, and TNS configuration ensure proper connectivity and environment consistency. · The guide concludes with commands to start the standby database, create SPFILE, add instances to OCR, and start managed recovery, ensuring synchronization and replication validation between primary and standby databases. Assumed you have already Installed Grid Infrastructure and Oracle Database Binary/Software on STANDBY Se...
Posts
Dataguard Configuration steps
- Get link
- X
- Other Apps
Dataguard Configuration step by steps Primary Server Configurations: Primary Sever Name : TestDB <Step – 1 > Enable Archive log: <Step – 1 > Primary database is in No Archive Mode, Enable it: SQL> archive log list; Database log mode Archive Mode Automatic archival Enabled Archive destination USE_DB_RECOVERY_FILE_DEST Oldest online log sequence 10 Next log sequence to archive 12 Current log sequence 12 <Step – 2 > Enable force logging with the help of following SQL command: SQL> ALTER DATABASE FORCE LOGGING; Database altered. <Step – 3 > Verify initialization parameters db_name and db_unique_name on primary, In my case those are set to: testdb SQL> show parameter db_name NAME ...
RMAN DUPLICATE from Active Database
- Get link
- X
- Other Apps
Step 1: Add oratab entry in Target -------------------------- PRODDB:/app/oracle/product/12202:N Step 2: create password file in Target (should be same as Source) ------------------------------ orapwd file=orapwPRODDB password=test123 entries=20 Step 3: Create static listener for Target DB ------------------------------------- LISTENER_PRODDB = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.16.0.5)(PORT = 1524)) )) SID_LIST_LISTENER_PRODDB = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = PRODDB) (ORACLE_HOME = /app/oracle/product/12202) (SID_NAME = PRODDB) ) ) Step 4: Add TNS entry of source & target in both servers ------------------------------------------------- PRODDB_source = (DESCRIPTION = (ADDRESS = (PROT...
RMAN-08137: WARNING: archived log not deleted
- Get link
- X
- Other Apps
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process When we are taking archive log backup with delete then got an error. RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process archived log file name=/pac/lci9t1/arch/redo_1_16470_842608348.arc thread=1 sequence=16470 RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process archived log file name=/pac/lci9t1/arch/redo_1_16471_842608348.arc thread=1 sequence=16471 RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process SOLUATION: Cause: The archive logs seems that it is not yet applied in the standby database. Select sequence# , applied from v$archived_log; Action: Check the standby database and apply t...
ORA-19909: datafile 1 belongs to an orphan incarnation
- Get link
- X
- Other Apps
When i was tried to restored the backup i found below error message RMAN-03002: failure of recover command at 05/29/2019 15:35:47 ORA-00283: recovery session canceled due to errors RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed standby start ORA-00283: recovery session canceled due to errors ORA-19909: datafile 1 belongs to an orphan incarnation ORA-01110: data file 1: '/oradbf1/oradata/ctsdb/system01.dbf' Primary and standby have different incarnations: standby db: RMAN> list incarnation of database; List of Database Incarnations DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time ------- ------- -------- ---------------- --- ---------- ---------- 1 1 CTSDB 193365640 PARENT 1 31-JAN-17 2 ...
Recovery Manager (RMAN) Table Point In Time Recovery (PITR) in Oracle Database 12c Release 1 and 2 (12.1 and 12.2)
- Get link
- X
- Other Apps
New in Oracle 12c database Architecture, as well as the ability to restore one table from an RMAN backup. This blog post explains how to do a restore of one table in a database. Setup the test: 1.) Create a user – tables cannot be restored in the SYS schema 2.) Create a table for that user 3.) Take a backup – a backup of the table has to exist; it can’t just be in archive logs. 4.) Drop the table 5.) Restore the table 6.) Check that the table has been restored 1.) Create a user: CONN / AS SYSDBA CREATE USER test IDENTIFIED BY test QUOTA UNLIMITED ON users; GRANT CREATE SESSION, CREATE TABLE TO test; 2.) Create a table for that user: CONN test/test CREATE TABLE t1 (id NUMBER); INSERT INTO t1 VALUES (1); COMMIT; 3.) To Check the current SCN or TIMESTAMP : CONN / AS SYSDBA SELECT DBMS_FLASHBACK.get_system_change_number FROM dual; GET_SYSTEM...
Oracle 12C Database creation - manual method
- Get link
- X
- Other Apps
Oracle 12C Database Creation - Manual Method 1. Install the Oracle Software in the Primary Server 192.2.4.45. 1.1 Create Directories for the File Locations : =============================================== [oracle@orman01 prod]$ pwd /oracle/app/oracle/oradata [oracle@orman01 oradata]$ mkdir prod [oracle@orman01 prod]$ cd /oracle/app/oracle/oradata/prod/ [oracle@orman01 prod]$ mkdir -p flash_recovery_area archive_log adump [oracle@orman01 prod]$ ...