-
This means that your standby db is still not in sync with the primary.
In what point of time your archive logs have been appied to your standby?
If the proble with regards to datafile is still exist I don't think you have applied successfully the archive logs after the timestamp where in datafile was created.
Take a look in the alert log of your standby database, and try to find if there is a ORA-600 errors.
Observe also how log switching happens in your Primary database, if there is a fast switching, your standby db most probably didn't able to keep up with the primary db resulting this type of error.
---------------
-
rey.., it doesn't shows any error on standby like ora-600.
-
How about this error in Primary database?
---------
ORA-16099: internal error ORA-00600 occurred at standby database
.....
ORA-16055: FAL request rejected
----------------------------------------
If nothing, and your primary db doesn't have log switching problem then,
You might as well re-create your standby db.
---------------
-
Did you set offline for the tablespace-datafile from the prim server before you copy?
---------------
-
have you try recreating the standby controlfile from prim server and use it in standby db?
---------------
-
I have made up mind to re-create standby.I have planned to create control file after copying hot backup to standby.But little bit scared.If i create control file after copying to standby (it takes 3hrs to copy complete Bkup).,will it show any error when i mount my standby because of time difference.
-
I have re-created standby copied all .dbf file,created control file,and move latest archive log files mounted standby and applied.
SQL> startup nomount;
ORACLE instance started.
Total System Global Area 873535324 bytes
Fixed Size 452444 bytes
Variable Size 452984832 bytes
Database Buffers 419430400 bytes
Redo Buffers 667648 bytes
SQL> alter database mount standby database;
Database altered.
SQL> alter database recover managed standby database disconnect from session;
Database altered.
SQL> recover managed standby database cancel;
Media recovery complete.
then i tried to open..
SQL> alter database open read only;
alter database open read only
*
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/mnt/.../system01.dbf'
SQL> alter database recover datafile '/mnt/..../system01.dbf';
alter database recover datafile '/mnt/.../system01.dbf'
*
ERROR at line 1:
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
What to do i don't know,
pls help.. How to recover using backup control file.
Last edited by ams-jamali; 03-12-2007 at 11:37 PM.
Reason: to increase details
-
Hello, Do you have all the necessary logs on the standby servers? Can you try manual recovery using:
ALTER DATABASE RECOVER AUTOMATIC STANDBY DATABASE;.
then
Can you please put the standby in automatic recovery mode and switch logs on primary? Then compare the sequence# in both, monitor alertlog for logs being applied or any errors.
Milind
-----------------------------
www.milinds.com
My Private World on the Web !
-
i have used
alter database backup controlfile to trace
and opened that trace file(before using this command i deleted all .trc file in that dir)it shows two times and other unwanted information.
Unusual trace file i have ever seen.
udump>cat isp_ora_27492.trc
/mnt/db/oracle/admin/ISP/udump/isp_ora_27492.trc
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.4.0 - Production
ORACLE_HOME = /mnt/db/oracle/product/9.2.0
System name: Linux
Node name: susedb2
Release: 2.6.8-24.25-bigsmp
Version: #1 SMP Thu Aug 24 09:57:32 UTC 2006
Machine: i686
Instance name: ISP
Redo thread mounted by this instance: 1
Oracle process number: 9
Unix process pid: 27492, image: oracle@susedb2 (TNS V1-V3)
*** SESSION ID:(11.311) 2007-03-12 22:55:08.604
*** 2007-03-12 22:55:08.604
# 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=%d_%t_%s.arc
# REMOTE_ARCHIVE_ENABLE=TRUE
# LOG_ARCHIVE_START=TRUE
# LOG_ARCHIVE_MAX_PROCESSES=2
# STANDBY_FILE_MANAGEMENT=AUTO
# STANDBY_ARCHIVE_DEST=/mnt/backup/arch/ISP
# FAL_CLIENT=ISP.STANDBY1
# FAL_SERVER=ISP.ISH.COM
#
# LOG_ARCHIVE_DEST_1='LOCATION=/mnt/backup/arch/ISP'
# LOG_ARCHIVE_DEST_1='OPTIONAL REOPEN=300 NODELAY'
# LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM SYNC'
# LOG_ARCHIVE_DEST_1='REGISTER NOALTERNATE NODEPENDENCY'
# LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED'
# 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 the recovery manager will be lost. Additional logs may
# be required for media recovery of offline data files. Use this
# only if the current version of all online logs are available.
# WARNING! The current control file needs to be checked against
# the datafiles to insure it contains the correct files. The
# commands printed here may be missing log and/or data files.
# Another report should be made after the database has been
# successfully opened.
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ISP" NORESETLOGS FORCE LOGGING ARCHIVELOG
-- SET STANDBY TO MAXIMIZE PERFORMANCE
MAXLOGFILES 50
MAXLOGMEMBERS 5
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 678
LOGFILE
GROUP 1 '/mnt/db/oracle/oradata/ISP/redo01.log' SIZE 100M,
GROUP 2 '/mnt/db/oracle/oradata/ISP/redo02.log' SIZE 100M,
GROUP 3 '/mnt/db/oracle/oradata/ISP/redo03.log' SIZE 100M
-- STANDBY LOGFILE
DATAFILE
'/mnt/db/oracle/oradata/ISP/system01.dbf',
'/mnt/db/oracle/oradata/ISP/ishindx16.dbf',
'/mnt/db/oracle/oradata/ISP/drsys01.dbf',
'/mnt/db/oracle/oradata/ISP/example01.dbf',
'/mnt/db/oracle/oradata/ISP/indx01.dbf',
'/mnt/db/oracle/oradata/ISP/odm01.dbf',
'/mnt/db/oracle/oradata/ISP/tools01.dbf',
'/mnt/db/oracle/oradata/ISP/users01.dbf',
'/mnt/db/oracle/oradata/ISP/xdb01.dbf',
'/mnt/db/oracle/oradata/ISP/isdata01.dbf',
'/mnt/db/oracle/oradata/ISP/isindx01.dbf',
'/mnt/db/oracle/oradata/ISP/isdata02.dbf',
'/mnt/db/oracle/oradata/ISP/isdata03.dbf',
'/mnt/db/oracle/oradata/ISP/isdata04.dbf',
'/mnt/db/oracle/oradata/ISP/isdata05.dbf',
'/mnt/db/oracle/oradata/ISP/isdata06.dbf',
'/mnt/db/oracle/oradata/ISP/isdata07.dbf',
'/mnt/db/oracle/oradata/ISP/isdata08.dbf',
'/mnt/db/oracle/oradata/ISP/isdata09.dbf',
'/mnt/db/oracle/oradata/ISP/isdata10.dbf',
'/mnt/db/oracle/oradata/ISP/isindx02.dbf',
'/mnt/db/oracle/oradata/ISP/isindx03.dbf',
'/mnt/db/oracle/oradata/ISP/isindx04.dbf',
'/mnt/db/oracle/oradata/ISP/isindx05.dbf',
'/mnt/db/oracle/oradata/ISP/isindx06.dbf',
'/mnt/db/oracle/oradata/ISP/isindx07.dbf',
'/mnt/db/oracle/oradata/ISP/isindx08.dbf',
'/mnt/db/oracle/oradata/ISP/isindx09.dbf',
'/mnt/db/oracle/oradata/ISP/isindx10.dbf',
'/mnt/db/oracle/oradata/ISP/isindx11.dbf',
'/mnt/db/oracle/oradata/ISP/isindx12.dbf',
'/mnt/db/oracle/oradata/ISP/isindx13.dbf',
'/mnt/db/oracle/oradata/ISP/isindx14.dbf',
'/mnt/db/oracle/oradata/ISP/.dbf',
'/mnt/db/oracle/oradata/ISP/isindx17.dbf',
'/mnt/db/oracle/oradata/ISP/undotbs.dbf',
'/mnt/db/oracle/oradata/ISP/isindx015.dbf',
'/mnt/db/oracle/oradata/ISP/perfstat.dbf',
'/mnt/db/oracle/oradata/ISP/isdata11.dbf'
CHARACTER SET WE8ISO8859P1
;
# 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;
# No tempfile entries found to add.
#
# Set #2. RESETLOGS case
#
# The following commands will create a new control file and use it
# to open the database.
# The contents of online logs will be lost and all backups will
# be invalidated. Use this only if online logs are damaged.
# WARNING! The current control file needs to be checked against
# the datafiles to insure it contains the correct files. The
# commands printed here may be missing log and/or data files.
# Another report should be made after the database has been
# successfully opened.
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ISPRO20" RESETLOGS FORCE LOGGING ARCHIVELOG
-- SET STANDBY TO MAXIMIZE PERFORMANCE
MAXLOGFILES 50
MAXLOGMEMBERS 5
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 678
LOGFILE
GROUP 1 '/mnt/db/oracle/oradata/ISP/redo01.log' SIZE 100M,
GROUP 2 '/mnt/db/oracle/oradata/ISP/redo02.log' SIZE 100M,
GROUP 3 '/mnt/db/oracle/oradata/ISP/redo03.log' SIZE 100M
-- STANDBY LOGFILE
DATAFILE
'/mnt/db/oracle/oradata/ISP/system01.dbf',
'/mnt/db/oracle/oradata/ISP/ishindx16.dbf',
'/mnt/db/oracle/oradata/ISP/drsys01.dbf',
'/mnt/db/oracle/oradata/ISP/example01.dbf',
'/mnt/db/oracle/oradata/ISP/indx01.dbf',
'/mnt/db/oracle/oradata/ISP/odm01.dbf',
'/mnt/db/oracle/oradata/ISP/tools01.dbf',
'/mnt/db/oracle/oradata/ISP/users01.dbf',
'/mnt/db/oracle/oradata/ISP/xdb01.dbf',
'/mnt/db/oracle/oradata/ISP/isdata01.dbf',
'/mnt/db/oracle/oradata/ISP/isindx01.dbf',
'/mnt/db/oracle/oradata/ISP/isdata02.dbf',
'/mnt/db/oracle/oradata/ISP/isdata03.dbf',
'/mnt/db/oracle/oradata/ISP/isdata04.dbf',
'/mnt/db/oracle/oradata/ISP/isdata05.dbf',
'/mnt/db/oracle/oradata/ISP/isdata06.dbf',
'/mnt/db/oracle/oradata/ISP/isdata07.dbf',
'/mnt/db/oracle/oradata/ISP/isdata08.dbf',
'/mnt/db/oracle/oradata/ISP/isdata09.dbf',
'/mnt/db/oracle/oradata/ISP/isdata10.dbf',
'/mnt/db/oracle/oradata/ISP/isindx02.dbf',
'/mnt/db/oracle/oradata/ISP/isindx03.dbf',
'/mnt/db/oracle/oradata/ISP/isindx04.dbf',
'/mnt/db/oracle/oradata/ISP/isindx05.dbf',
'/mnt/db/oracle/oradata/ISP/isindx06.dbf',
'/mnt/db/oracle/oradata/ISP/isindx07.dbf',
'/mnt/db/oracle/oradata/ISP/isindx08.dbf',
'/mnt/db/oracle/oradata/ISP/isindx09.dbf',
'/mnt/db/oracle/oradata/ISP/isindx10.dbf',
'/mnt/db/oracle/oradata/ISP/isindx11.dbf',
'/mnt/db/oracle/oradata/ISP/isindx12.dbf',
'/mnt/db/oracle/oradata/ISP/isindx13.dbf',
'/mnt/db/oracle/oradata/ISP/isindx14.dbf',
'/mnt/db/oracle/oradata/ISP/.dbf',
'/mnt/db/oracle/oradata/ISP/isindx17.dbf',
'/mnt/db/oracle/oradata/ISP/undotbs.dbf',
'/mnt/db/oracle/oradata/ISP/isindx015.dbf',
'/mnt/db/oracle/oradata/ISP/perfstat.dbf',
'/mnt/db/oracle/oradata/ISP/isdata11.dbf'
CHARACTER SET WE8ISO8859P1
;
RECOVER DATABASE USING BACKUP CONTROLFILE
I have changed some paths and file name,(for security purpose)
pls help..
Last edited by ams-jamali; 03-13-2007 at 01:13 AM.
Reason: to increase information
-
can you post your pfile from spfile of your primary server? and post it here.
CREATE PFILE='/disk1/oracle/ADMIN/PFILE/BACKUP/initPRIMSVR.ora' FROM SPFILE;
---------------
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|