- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- Creating DR Databse system
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Creating DR Databse system
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 06-21-2011 10:20 AM
Dear Friends,
We have created DR server of our ECC production server.
We are running ECC 6.0, HP-UX and oracle 10g.
Now we want to create DR for the same using offline backup of our primary database.
Please help me ?
Regrdsa
Ganesh Datt Tiwari
- SAP Managed Tags:
- Oracle Database,
- SAP ERP
Accepted Solutions (0)
Answers (4)
Answers (4)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Dear Friends,
Very very thanks for lot of helps given in this thread. I have solved the problem, there was restore error there were some missing files and permission problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Tiwari,
Check the link, below;
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239.pdf
Best regards,
Orkun Gedik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Orkun,
Thanks for providing the document.
I have created the standby database. Now I am trying to applying the redologs then it is giving the error messag as below.
SQL> SQL> SQL> ORA-00279: change 163046 generated at 06/05/2007 14:46:13 needed
for thread 1
ORA-00289: suggestion : /oracle/PDR/oraarch/PDRarch1_10_624465037.dbf
ORA-00280: change 163046 for thread 1 is in sequence #10
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'/oracle/PDR/oraarch/PDRarch1_10_624465037.dbf'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
ORA-00308: cannot open archived log
'/oracle/PDR/oraarch/PDRarch1_10_624465037.dbf'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01245: offline file 1 will be lost if RESETLOGS is done
ORA-01110: data file 1: '/oracle/PDR/sapdata1/system_1/system.data1'
Please help me
Regards
Ganesh Datt Tiwari
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Ganesh,
ORA-00308: cannot open archived log
'/oracle/PDR/oraarch/PDRarch1_10_624465037.dbf'
1. check whether file PDRarch1_10_624465037.dbf is present in '/oracle/PDR/oraarch' directory.
2. Check permission for file, it should be ora<SID>:dba 755
Once above 2 points are done then start the recovery.
Regards,
Rajesh
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Ganesh,
I think you have done with DR set up.
Check the last log applied in DR and also check the last log that was generated before you have taken offline backup of your source system.
If both are in sync. then u have done with DR set up... Now to proceed further leave the DR Database in Standby mode and copy the source archive logs to target and sync DR with source.
Regards,
Vivek S
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Rajesh,
Thanks for your valuable reply.
The missing log PDRarch1_10_624465037.dbf dated in year 2007 but i have taken offline backup of our primary server on 20/06/2011 and restored it to our Dr server and also taken redo log.
But when i start recover then why it is asking for that old log ?
Please help me
Regards
Ganesh Datt Tiwari
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
Thanks for your valuable reply.
I have done as per comands given by you but there is erro as below.
SQL> alter database backup controlfile to trace;
Database altered.
SQL> startup nomount;
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup nomount;
ORACLE instance started.
Total System Global Area 2.0300E+10 bytes
Fixed Size 2080176 bytes
Variable Size 3103785552 bytes
Database Buffers 1.7180E+10 bytes
Redo Buffers 14696448 bytes
SQL> @control.trc ;
SP2-0310: unable to open file "control.trc"
SQL> SQL>
SQL> @control.trc ;
SP2-0310: unable to open file "control.trc"
SQL> SQL>
regards
Ganesh Datt Tiwari
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Rajesh,
Thanks for your valuable reply.
I have tried to fin dthe file control.trc but in my system there is a file "pdr_ora_22200.trc".
Please find the content of this file.
Unix process pid: 22200, image: oracle@jkeccdb (TNS V1-V3)
SERVICE NAME:(SYS$USERS) 2008-10-01 02:03:27.767
SESSION ID:(739.24722) 2008-10-01 02:03:27.767
2008-10-01 02:03:27.767
-- The following are current System-scope REDO Log Archival related
-- parameters and can be included in the database initialization file.
--
-- LOG_ARCHIVE_DEST=''
-- LOG_ARCHIVE_DUPLEX_DEST=''
--
-- LOG_ARCHIVE_FORMAT=%t_%s_%r.dbf
--
-- DB_UNIQUE_NAME="PDR"
--
-- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG'
-- LOG_ARCHIVE_MAX_PROCESSES=2
-- STANDBY_FILE_MANAGEMENT=MANUAL
-- STANDBY_ARCHIVE_DEST=?/dbs/arch
-- FAL_CLIENT=''
-- FAL_SERVER=''
--
-- LOG_ARCHIVE_DEST_1='LOCATION=/oracle/PDR/oraarch/PDRarch'
-- LOG_ARCHIVE_DEST_1='MANDATORY NOREOPEN NODELAY'
-- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM EXPEDITE NOVERIFY SYNC'
-- LOG_ARCHIVE_DEST_1='NOREGISTER NOALTERNATE NODEPENDENCY'
-- LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME'
-- LOG_ARCHIVE_DEST_1='VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)'
-- LOG_ARCHIVE_DEST_STATE_1=ENABLE
--
-- Below are two sets of SQL statements, each of which creates a new
-- control file and uses it to open the database. The first set opens
-- the database with the NORESETLOGS option and should be used only if
-- the current versions of all online logs are available. The second
-- set opens the database with the RESETLOGS option and should be used
-- if online logs are unavailable.
-- The appropriate set of statements can be copied from the trace into
-- a script file, edited as necessary, and executed when there is a
-- need to re-create the control file.
--
-- Set #1. NORESETLOGS case
--
-- The following commands will create a new control file and use it
-- to open the database.
-- Data used by Recovery Manager will be lost.
-- Additional logs may be required for media recovery of offline
-- Use this only if the current versions of all online logs are
-- available.
-- After mounting the created controlfile, the following SQL
-- statement will place the database in the appropriate
-- protection mode:
-- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "PDR" NORESETLOGS ARCHIVELOG
MAXLOGFILES 255
MAXLOGMEMBERS 3
MAXDATAFILES 254
MAXINSTANCES 50
MAXLOGHISTORY 23360
LOGFILE
GROUP 21 (
'/oracle/PDR/origlogA/log_g21m1.dbf',
'/oracle/PDR/mirrlogA/log_g21m2.dbf'
) SIZE 250M,
GROUP 22 (
'/oracle/PDR/origlogA/log_g22m1.dbf',
'/oracle/PDR/mirrlogA/log_g22m2.dbf'
) SIZE 250M,
GROUP 23 (
'/oracle/PDR/origlogB/log_g23m1.dbf',
'/oracle/PDR/mirrlogB/log_g23m2.dbf'
) SIZE 250M,
GROUP 24 (
'/oracle/PDR/origlogB/log_g24m1.dbf',
'/oracle/PDR/mirrlogB/log_g24m2.dbf'
) SIZE 250M
-- STANDBY LOGFILE
DATAFILE
'/oracle/PDR/sapdata1/system_1/system.data1',
'/oracle/PDR/sapdata3/undo_1/undo.data1',
'/oracle/PDR/sapdata1/sysaux_1/sysaux.data1',
'/oracle/PDR/sapdata1/pdr_1/pdr.data1',
'/oracle/PDR/sapdata1/pdr_2/pdr.data2',
'/oracle/PDR/sapdata1/pdr_3/pdr.data3',
'/oracle/PDR/sapdata1/pdr_4/pdr.data4',
'/oracle/PDR/sapdata1/pdr_5/pdr.data5',
'/oracle/PDR/sapdata2/pdr_6/pdr.data6',
'/oracle/PDR/sapdata2/pdr_7/pdr.data7',
'/oracle/PDR/sapdata2/pdr_8/pdr.data8',
'/oracle/PDR/sapdata2/pdr_9/pdr.data9',
'/oracle/PDR/sapdata2/pdr_10/pdr.data10',
'/oracle/PDR/sapdata3/pdr_11/pdr.data11',
'/oracle/PDR/sapdata3/pdr_12/pdr.data12',
'/oracle/PDR/sapdata3/pdr_13/pdr.data13',
'/oracle/PDR/sapdata3/pdr_14/pdr.data14',
'/oracle/PDR/sapdata3/pdr_15/pdr.data15',
'/oracle/PDR/sapdata4/pdr_16/pdr.data16',
'/oracle/PDR/sapdata4/pdr_17/pdr.data17',
'/oracle/PDR/sapdata4/pdr_18/pdr.data18',
'/oracle/PDR/sapdata4/pdr_19/pdr.data19',
'/oracle/PDR/sapdata4/pdr_20/pdr.data20',
'/oracle/PDR/sapdata1/pdr700_1/pdr700.data1',
'/oracle/PDR/sapdata1/pdr700_2/pdr700.data2',
'/oracle/PDR/sapdata1/pdr700_3/pdr700.data3',
'/oracle/PDR/sapdata1/pdr700_4/pdr700.data4',
'/oracle/PDR/sapdata2/pdr700_5/pdr700.data5',
'/oracle/PDR/sapdata2/pdr700_6/pdr700.data6',
'/oracle/PDR/sapdata2/pdr700_7/pdr700.data7',
'/oracle/PDR/sapdata2/pdr700_8/pdr700.data8',
'/oracle/PDR/sapdata3/pdr700_9/pdr700.data9',
'/oracle/PDR/sapdata3/pdr700_10/pdr700.data10',
'/oracle/PDR/sapdata3/pdr700_11/pdr700.data11',
'/oracle/PDR/sapdata3/pdr700_12/pdr700.data12',
'/oracle/PDR/sapdata4/pdr700_13/pdr700.data13',
'/oracle/PDR/sapdata4/pdr700_14/pdr700.data14',
'/oracle/PDR/sapdata4/pdr700_15/pdr700.data15',
'/oracle/PDR/sapdata4/pdr700_16/pdr700.data16',
'/oracle/PDR/sapdata1/pdrusr_1/pdrusr.data1',
'/oracle/PDR/sapdata4/pdr_21/pdr.data21',
'/oracle/PDR/sapdata4/pdr_22/pdr.data22',
'/oracle/PDR/sapdata4/pdr_23/pdr.data23',
'/oracle/PDR/sapdata4/pdr_24/pdr.data24',
'/oracle/PDR/sapdata4/pdr_25/pdr.data25',
'/oracle/PDR/sapdata4/pdr_26/pdr.data26',
'/oracle/PDR/sapdata1/pdr_27/pdr.data27',
'/oracle/PDR/sapdata4/pdr_28/pdr.data28',
'/oracle/PDR/sapdata3/pdr_29/pdr.data29',
'/oracle/PDR/sapdata2/pdr_30/pdr.data30',
'/oracle/PDR/sapdata5/pdr_31/pdr.data31',
'/oracle/PDR/sapdata5/pdr_32/pdr.data32',
'/oracle/PDR/sapdata5/pdr_33/pdr.data33',
'/oracle/PDR/sapdata5/pdr_34/pdr.data34',
'/oracle/PDR/sapdata5/pdr_35/pdr.data35',
'/oracle/PDR/sapdata6/pdr_36/pdr.data36',
'/oracle/PDR/sapdata6/pdr_37/pdr.data37',
'/oracle/PDR/sapdata6/pdr_38/pdr.data38',
'/oracle/PDR/sapdata6/pdr_39/pdr.data39',
'/oracle/PDR/sapdata6/pdr_40/pdr.data40',
'/oracle/PDR/sapdata5/pdr700_17/pdr700.data17',
'/oracle/PDR/sapdata5/pdr700_18/pdr700.data18',
'/oracle/PDR/sapdata6/pdr700_19/pdr700.data19',
'/oracle/PDR/sapdata6/pdr700_20/pdr700.data20',
'/oracle/PDR/sapdata6/pdr700_21/pdr700.data21',
'/oracle/PDR/sapdata5/pdr700_22/pdr700.data22',
'/oracle/PDR/sapdata6/pdr_41/pdr.data41',
'/oracle/PDR/sapdata6/pdr_42/pdr.data42',
'/oracle/PDR/sapdata6/pdr_43/pdr.data43',
'/oracle/PDR/sapdata5/pdr_44/pdr.data44',
'/oracle/PDR/sapdata5/pdr_45/pdr.data45'
CHARACTER SET UTF8
;
-- Commands to re-create incarnation table
-- Below log names MUST be changed to existing filenames on
-- disk. Any one log file from each branch can be used to
-- re-create incarnation records.
';
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE
-- All logs need archiving and a log switch is needed.
ALTER SYSTEM ARCHIVE LOG ALL;
-- Database can now be opened normally.
ALTER DATABASE OPEN;
-- Commands to add tempfiles to temporary tablespaces.
-- Online tempfiles have complete space information.
-- Other tempfiles may require adjustment.
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/PDR/sapdata2/temp_1/temp.data1'
SIZE 3380M REUSE AUTOEXTEND ON NEXT 20971520 MAXSIZE 10000M;
-- End of tempfile additions.
--
-- Set #2. RESETLOGS case
--
-- The following commands will create a new control file and use it
-- to open the database.
-- Data used by Recovery Manager will be lost.
-- The contents of online logs will be lost and all backups will
-- be invalidated. Use this only if online logs are damaged.
-- After mounting the created controlfile, the following SQL
-- statement will place the database in the appropriate
-- protection mode:
-- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "PDR" RESETLOGS ARCHIVELOG
MAXLOGFILES 255
MAXLOGMEMBERS 3
MAXDATAFILES 254
MAXINSTANCES 50
MAXLOGHISTORY 23360
LOGFILE
GROUP 21 (
'/oracle/PDR/origlogA/log_g21m1.dbf',
'/oracle/PDR/mirrlogA/log_g21m2.dbf'
) SIZE 250M,
GROUP 22 (
'/oracle/PDR/origlogA/log_g22m1.dbf',
'/oracle/PDR/mirrlogA/log_g22m2.dbf'
) SIZE 250M,
GROUP 23 (
'/oracle/PDR/origlogB/log_g23m1.dbf',
'/oracle/PDR/mirrlogB/log_g23m2.dbf'
) SIZE 250M,
GROUP 24 (
'/oracle/PDR/origlogB/log_g24m1.dbf',
'/oracle/PDR/mirrlogB/log_g24m2.dbf'
) SIZE 250M
-- STANDBY LOGFILE
DATAFILE
'/oracle/PDR/sapdata1/system_1/system.data1',
'/oracle/PDR/sapdata3/undo_1/undo.data1',
'/oracle/PDR/sapdata1/sysaux_1/sysaux.data1',
'/oracle/PDR/sapdata1/pdr_1/pdr.data1',
'/oracle/PDR/sapdata1/pdr_2/pdr.data2',
'/oracle/PDR/sapdata1/pdr_3/pdr.data3',
'/oracle/PDR/sapdata1/pdr_4/pdr.data4',
'/oracle/PDR/sapdata1/pdr_5/pdr.data5',
'/oracle/PDR/sapdata2/pdr_6/pdr.data6',
'/oracle/PDR/sapdata2/pdr_7/pdr.data7',
'/oracle/PDR/sapdata2/pdr_8/pdr.data8',
'/oracle/PDR/sapdata2/pdr_9/pdr.data9',
'/oracle/PDR/sapdata2/pdr_10/pdr.data10',
'/oracle/PDR/sapdata3/pdr_11/pdr.data11',
'/oracle/PDR/sapdata3/pdr_12/pdr.data12',
'/oracle/PDR/sapdata3/pdr_13/pdr.data13',
'/oracle/PDR/sapdata3/pdr_14/pdr.data14',
'/oracle/PDR/sapdata3/pdr_15/pdr.data15',
'/oracle/PDR/sapdata4/pdr_16/pdr.data16',
'/oracle/PDR/sapdata4/pdr_17/pdr.data17',
'/oracle/PDR/sapdata4/pdr_18/pdr.data18',
'/oracle/PDR/sapdata4/pdr_19/pdr.data19',
'/oracle/PDR/sapdata4/pdr_20/pdr.data20',
'/oracle/PDR/sapdata1/pdr700_1/pdr700.data1',
'/oracle/PDR/sapdata1/pdr700_2/pdr700.data2',
'/oracle/PDR/sapdata1/pdr700_3/pdr700.data3',
'/oracle/PDR/sapdata1/pdr700_4/pdr700.data4',
'/oracle/PDR/sapdata2/pdr700_5/pdr700.data5',
'/oracle/PDR/sapdata2/pdr700_6/pdr700.data6',
'/oracle/PDR/sapdata2/pdr700_7/pdr700.data7',
'/oracle/PDR/sapdata2/pdr700_8/pdr700.data8',
'/oracle/PDR/sapdata3/pdr700_9/pdr700.data9',
'/oracle/PDR/sapdata3/pdr700_10/pdr700.data10',
'/oracle/PDR/sapdata3/pdr700_11/pdr700.data11',
'/oracle/PDR/sapdata3/pdr700_12/pdr700.data12',
'/oracle/PDR/sapdata4/pdr700_13/pdr700.data13',
'/oracle/PDR/sapdata4/pdr700_14/pdr700.data14',
'/oracle/PDR/sapdata4/pdr700_15/pdr700.data15',
'/oracle/PDR/sapdata4/pdr700_16/pdr700.data16',
'/oracle/PDR/sapdata1/pdrusr_1/pdrusr.data1',
'/oracle/PDR/sapdata4/pdr_21/pdr.data21',
'/oracle/PDR/sapdata4/pdr_22/pdr.data22',
'/oracle/PDR/sapdata4/pdr_23/pdr.data23',
'/oracle/PDR/sapdata4/pdr_24/pdr.data24',
'/oracle/PDR/sapdata4/pdr_25/pdr.data25',
'/oracle/PDR/sapdata4/pdr_26/pdr.data26',
'/oracle/PDR/sapdata1/pdr_27/pdr.data27',
'/oracle/PDR/sapdata4/pdr_28/pdr.data28',
'/oracle/PDR/sapdata3/pdr_29/pdr.data29',
'/oracle/PDR/sapdata2/pdr_30/pdr.data30',
'/oracle/PDR/sapdata5/pdr_31/pdr.data31',
'/oracle/PDR/sapdata5/pdr_32/pdr.data32',
'/oracle/PDR/sapdata5/pdr_33/pdr.data33',
'/oracle/PDR/sapdata5/pdr_34/pdr.data34',
'/oracle/PDR/sapdata5/pdr_35/pdr.data35',
'/oracle/PDR/sapdata6/pdr_36/pdr.data36',
'/oracle/PDR/sapdata6/pdr_37/pdr.data37',
'/oracle/PDR/sapdata6/pdr_38/pdr.data38',
'/oracle/PDR/sapdata6/pdr_39/pdr.data39',
'/oracle/PDR/sapdata6/pdr_40/pdr.data40',
'/oracle/PDR/sapdata5/pdr700_17/pdr700.data17',
'/oracle/PDR/sapdata5/pdr700_18/pdr700.data18',
'/oracle/PDR/sapdata6/pdr700_19/pdr700.data19',
'/oracle/PDR/sapdata6/pdr700_20/pdr700.data20',
'/oracle/PDR/sapdata6/pdr700_21/pdr700.data21',
'/oracle/PDR/sapdata5/pdr700_22/pdr700.data22',
'/oracle/PDR/sapdata6/pdr_41/pdr.data41',
'/oracle/PDR/sapdata6/pdr_42/pdr.data42',
'/oracle/PDR/sapdata6/pdr_43/pdr.data43',
'/oracle/PDR/sapdata5/pdr_44/pdr.data44',
'/oracle/PDR/sapdata5/pdr_45/pdr.data45'
CHARACTER SET UTF8
;
-- Commands to re-create incarnation table
-- Below log names MUST be changed to existing filenames on
-- disk. Any one log file from each branch can be used to
-- re-create incarnation records.
-- ALTER DATABASE REGISTER LOGFILE '/oracle/PDR/oraarch/PDRarch1_1_624465037.dbf
';
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE USING BACKUP CONTROLFILE
-- Database can now be opened zeroing the online logs.
ALTER DATABASE OPEN RESETLOGS;
-- Commands to add tempfiles to temporary tablespaces.
-- Online tempfiles have complete space information.
-- Other tempfiles may require adjustment.
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/PDR/sapdata2/temp_1/temp.data1'
SIZE 3380M REUSE AUTOEXTEND ON NEXT 20971520 MAXSIZE 10000M;
-- End of tempfile additions.
--
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
You need to modify the trace control file. Follow the bellow way if you have UNIX based system.
Edit the <TRACEFILE> and make the following changes:
vi <rmd_control.trc >
Locate u201CSTARTUP NOMOUNTu201D
:/START and press n until the location is found
Place the cursor on the line with u201CSTARTUP NOMOUNTu201D (very Important)
:1,.d
:/;
Place the cursor on the line below the semicolon.
:.,$d
Change u201CREUSEu201D to u201CSETu201D
Change u201CNORESETLOGSu201D to u201CRESETLOGSu201D
Change u201CARCHIVELOGu201D to u201CNOARCHIVELOGu201D
Change the <source system id> to <target sid>in the entire file as:
eg
:1,$s/S11/T11/g
Save and exit. :wq!
Rename the database by executing the following:
Make sure that your Oracle environment variable "ORACLE_SID" is set to Target SID
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi ,
Thanks for your reply.
I have done changes in the trc file but when I am checking the parameter ORACLE_HOME from SQL prompt then it is showing blank but when i m checking from # prompt then it is showing PDR.
Error is same as below when i start recovery after changes in trc file.
SQL> recover standby database;
ORA-00279: change 163046 generated at 06/05/2007 14:46:13 needed for thread 1
ORA-00289: suggestion : /oracle/PDR/oraarch/PDRarch1_10_624465037.dbf
ORA-00280: change 163046 for thread 1 is in sequence #10
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log
'/oracle/PDR/oraarch/PDRarch1_10_624465037.dbf'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
ORA-00308: cannot open archived log
'/oracle/PDR/oraarch/PDRarch1_10_624465037.dbf'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01245: offline file 1 will be lost if RESETLOGS is done
ORA-01110: data file 1: '/oracle/PDR/sapdata1/system_1/system.data1'
Regards
Ganesh Datt Tiwari
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Ganesh,
As per your first response, i understand that you are trying to apply logs and the log which is asking for recovery is belogning to 2007 year which is absolultely wrong.
Ideally for a DR database instance which is already came in to mount state, you do not need to take trace of existing database and create controlfile.
As this is DR instance and you will be applying production redo-logs on DR database, database structure should be in sync with production.
I suspect you DB restore, where in some of datafiles either not restored or their restore is not proper, due to which they are asking for recovery with very old redolog.
You need to verify DB consistency before moving ahead with redolog application:
check PIT of your restored database first:
select to_char(CHECKPOINT_TIME,'yyyy-mm-dd:hh24:mi:ss') from v$datafile where file#=1;
Check header sequence number: should be same for all datafiles
select count(*), fhrba_seq from x$kcvfh group by fhrba_seq;
all checkpoints time should be belonging to same date:
select distinct CHECKPOINT_TIME from v$datafile;
select distinct time from v$recover_file;
Compare the output with a consostent database, you should get some dates of 2007 year as your datafile recovery is asking very log old file to be applied.
If you get any inconsistency, I would suggest that you do restore again and open the database with production controlfile trace after checking restored file's consistency.
Cheers !!!
Ashish
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
Restore offline backup of your production system on DR server and start recovery by shipping archive logs on the DR server continuously so that production and DR will be in sync.
Thanks
Sunny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- SAP Datasphere + SAP S/4HANA: Your Guide to Seamless Data Integration in Technology Blogs by SAP
- What’s New in SAP Datasphere Version 2024.9 — Apr 23, 2024 in Technology Blogs by Members
- Hybrid Architectures: A Modern Approach for SAP Data Integration in Technology Blogs by SAP
- What’s New in SAP Analytics Cloud Release 2024.09 in Technology Blogs by SAP
- Vectorize your data for Infuse AI in to Business using Hana Vector and Generative AI in Technology Blogs by Members
| User | Count |
|---|---|
| 84 | |
| 10 | |
| 10 | |
| 8 | |
| 7 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.