ORA-279 signalled during recovery of standby database

Hi All,
I am preparing standby database after taking hot backup and copying those datafiles to standby,
taken controlfile standby controlfile backup from primary
mounted the standby database using standby controlfile using
startup nomount pfile='/u01/stand.ora'
alter database mount standby database;
Now I have started applying archives on standby database after copying all archives from primary to standby box the archives generated during backup using..
recover standby database;
But I am getting the below warning on the recovery screen...
ORA-00279: change 51667629050 generated at 07/02/2009 00:59:43 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55118_652209172.arc
ORA-00280: change 51667629050 for thread 1 is in sequence #55118
ORA-00278: log file '/nodal-archive/archive/1_55117_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667703096 generated at 07/02/2009 01:06:04 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55119_652209172.arc
ORA-00280: change 51667703096 for thread 1 is in sequence #55119
ORA-00278: log file '/nodal-archive/archive/1_55118_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667767649 generated at 07/02/2009 01:12:28 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55120_652209172.arc
ORA-00280: change 51667767649 for thread 1 is in sequence #55120
ORA-00278: log file '/nodal-archive/archive/1_55119_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc
ORA-00280: change 51667831821 for thread 1 is in sequence #55121
ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer
needed for this recovery
and I am getting the below warning on the alert log..........
Sun Jul 5 18:37:36 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Sun Jul 5 18:37:36 2009
Media Recovery Log /nodal-archive/archive/1_55256_652209172.arc
Sun Jul 5 18:40:31 2009
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Sun Jul 5 18:40:31 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Sun Jul 5 18:40:31 2009
Media Recovery Log /nodal-archive/archive/1_55257_652209172.arc
Please suggest what to do now.............
Thanks in Advance,
Sukanta Paul.

Hi Sukanta,
I didn't really understand what the problem is...
Let me explain, hope it will be clear.
You created a standby control file, and backed up the database (it doesn't matter in which order). Now, you have a standby database that is ready to apply logs. It will be able to apply log forever, until we will stop it.
The messages you see say the following:
ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for thread 1 {color:blue} - this says that the recovery process is now at scn 51667831821 {color}
ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc {color:blue} - the information needed for the recover is in this file (this is only the default name, you can choose other name if the file is called differently) {color}
ORA-00280: change 51667831821 for thread 1 is in sequence #55121 {color:blue} - same here, the needed archive is sequence 55121 {color}
ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer needed for this recovery {color:blue} - this message is after Oracle has applied the log, and it means that this log is no longer needed {color}
Now it will wait for the next log. Again, this process is endless, this is how it is made to allow the standby database to be always synched with the primary.
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com]

Similar Messages

ORA-279 signalled during: ALTER DATABASE RECOVER automatic standby databas

Hi,
oracle server:8.1.7.0.0
os:solaris 5.9
we created standby server by taking coldbackup of primary server and we are using rsync to syschronize the archive log files between production and standby servers but every over we recover the standby server by executing
sql>recover automatic standby database:
but in alert log file i am getting the following error :
but when i googled for ora-279 error some people says it is default behaviour and can it be ignored and why it is asking next logfile.
Media Recovery Log /oratranslog/arch_1_1701118.arc
Wed Mar 26 21:35:34 2008
Media Recovery Log /oratranslog/arch_1_1701119.arc
Wed Mar 26 21:35:54 2008
Media Recovery Log /oratranslog/arch_1_1701120.arc
ORA-279 signalled during: ALTER DATABASE RECOVER automatic standby database...
Wed Mar 26 21:36:24 2008
ALTER DATABASE RECOVER CANCEL
Wed Mar 26 21:36:24 2008
Media Recovery Cancelled
Completed: ALTER DATABASE RECOVER CANCEL
Thanks and Regards
Prakash
juniour oracle dba

damorgan,
He is running 8.1.7.0. "DataGuard" scripts were initially available for 9i and then
backported (and available as a seperate download) for 8i. Many 8i implementations
did not and do not use DataGuard.
Even if it is "Jurassic" {which it certainly is NOT}, they obviously do have a good
reason for setting up a standby -- they DO have data of value. So, maybe they have
not upgraded to 9i or 10g. There could be a dozen reasons
1. Server HW/OS doesn't support 9i/10g, not budgetting for Server upgrade
2. Application using Forms 2.x or 4.5 and not tested on 9i / 10g (4.5 not certified
on 9i)
3. Low end client PCs working perfectly with Character-mode forms, not powerful
enought to run Jinitiator and Forms 6i / 9i
Just because someone hasn't upgraded to 10g doesn't mean that they are at fault
when you do NOT know the reason why they have not upgraded.
Surely, they do know that 8i is desupported. Don't you think that their management
has undertaken due diligence / cost-benefit analysis in considering whether they
should upgrade to 10g ?
Maybe they have another project implementing 10g in parallel and will be able
to shutdown this environment soon. Maybe they don't need to do so.
Do understand that people are intelligent enough to make their own decisions
considering their particular circumstances and don't go shooting off with your
assumption that anyone not running 10g is a dinosaur.

MANAGED RECOVERY AT STANDBY DATABASE REQURING OLD ARCHIVELOGS ORA-00308

Oracle 9.2.0.4
HP-UX 11.11i
The database in Archivelog mode, single standby database in managed recovery
mode.
keeping standby in sync with manual applying the ARCHIVELOG from primary to
standby database.
primary database was 3 REDO log members of 100 MB with 1 member each.
what i did, 1 drop and re-create the INACTIVE REDO group for all three, and
make them
5 REDO logs of 200 MB with 1 member each,
then in order to keep fresh copy of primary database onto standby database, i
send the cold backup after 15 days (last week) with standby controlfile.
now, with that standby controlfile and the database, i can mount the database
but while to open the database, receives messages as , it requiring the
ARCHIVELOGS generated log time ago.
changes the REDO groups from 3 to 5 and size 100 to 200 MB at INACTIVE state
### Workarounds Used ###
SQL> alter database mount standby database;
Database altered.
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/user01/oracle9i/oradata/iobasprd/system01.dbf'
SQL> alter database recover automatic standby database;
alter database recover automatic standby database
ERROR at line 1:
ORA-00279: change 1655989696 generated at 08/12/2005 12:46:25 needed for thread
1
ORA-00289: suggestion :
/user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf
ORA-00280: change 1655989696 for thread 1 is in sequence #16849
ORA-00278: log file
'/user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf' no longer needed
for this recovery
ORA-00308: cannot open archived log
'/user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf'
ORA-27037: unable to obtain file status
HP-UX Error: 2: No such file or directory
Additional information: 3
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /user02/oracle9i/oradata/iobasprd/archive
Oldest online log sequence 53052
Next log sequence to archive 53056
Current log sequence
53056
-----------------------AlertIOBASPRD.log----------------------------
alter database mount standby database
Mon Oct 24 12:05:05 2005
Successful mount of redo thread 1, with mount id 3283884781.
Mon Oct 24 12:05:05 2005
Standby Database mounted.
Completed: alter database mount standby database
Mon Oct 24 12:05:12 2005
alter database open read only
ORA-16004 signalled during: alter database open read only...
Mon Oct 24 12:05:23 2005
alter database recover automatic standby database
Mon Oct 24 12:05:23 2005
Media Recovery Start
Starting datafile 1 recovery in thread 1 sequence 52617
Datafile 1: '/user01/oracle9i/oradata/iobasprd/system01.dbf'
Starting datafile 2 recovery in thread 1 sequence 52617
Datafile 2: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_005.dbf'
Starting datafile 3 recovery in thread 1 sequence 52617
Datafile 3: '/user01/oracle9i/oradata/iobasprd/drsys01.dbf'
Starting datafile 4 recovery in thread 1 sequence 52617
Datafile 132: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_002.dbf'
Starting datafile 133 recovery in thread 1 sequence 52617
Datafile 133: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_003.dbf'
Starting datafile 134 recovery in thread 1 sequence 52617
Datafile 134: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_004.dbf'
Media Recovery Log
Media Recovery Log /user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf
Errors with log /user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf.
ORA-279 signalled during: alter database recover automatic standby database...
Mon Oct 24 12:06:01 2005
Restarting dead background process QMN0
QMN0 started with pid=9
The snap of alertIOBASPRD.log can understand me that it requiring the
ARCHIVELOG 52617 only
and its lying in LOG_ARCHIVE_DET location also as
$ pwd
/user02/oracle9i/oradata/iobasprd/archive
$ ls archive_5261*.dbf
archive_52610.dbf archive_52613.dbf archive_52616.dbf archive_52619.dbf
archive_52611.dbf archive_52614.dbf archive_52617.dbf
archive_52612.dbf archive_52615.dbf archive_52618.dbf
$
now, even the files are lying , why ORACLE requing the old archive logs ?????

You haven't given any usefuly information on your problem.
show parameter log_archive_dest
show parameter fal
show parameter dg
What errors are in your alert logs ?
What command are you using to recover ?
Check the contents of v$archived_log
# run on primary to detect failures :-
select destination, status, fail_date, valid_now
from v$archive_dest
where status != 'VALID' or VALID_NOW != 'YES';
# run on standby to get exact position of rollforward :-
select thread#, to_char(snapshot_time,'dd-mon-yyyy:hh24:mi'),
to_char(applied_time,'dd-mon-yyyy:hh24:mi'),
to_char(newest_time,'dd-mon-yyyy:hh24:mi') from V$STANDBY_APPLY_SNAPSHOT;
Are you using dataguard broker ?

ORA-1092 signalled during: alter database open...

When trying to startup the db runnint into following error:
SMON: enabling cache recovery
Sat May 16 10:35:12 2009
Successfully onlined Undo Tablespace 1.
Sat May 16 10:35:12 2009
SMON: enabling tx recovery
Sat May 16 10:35:12 2009
Database Characterset is UTF8
Sat May 16 10:35:13 2009
Errors in file d:\oracle\visdb\9.2.0\admin\vis_apps\udump\vis_ora_2200.trc:
ORA-00600: internal error code, arguments: [4193], [2391], [2395], [], [], [], [], []
Doing block recovery for fno: 10 blk: 159
Sat May 16 10:35:17 2009
Recovery of Online Redo Log: Thread 1 Group 2 Seq 3 Reading mem 0
Mem# 0 errs 0: D:\ORACLE\VISDATA\LOG2.DBF
Doing block recovery for fno: 10 blk: 153
Sat May 16 10:35:18 2009
Recovery of Online Redo Log: Thread 1 Group 2 Seq 3 Reading mem 0
Mem# 0 errs 0: D:\ORACLE\VISDATA\LOG2.DBF
Sat May 16 10:35:18 2009
Errors in file d:\oracle\visdb\9.2.0\admin\vis_apps\udump\vis_ora_2200.trc:
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [4193], [2391], [2395], [], [], [], [], []
Error 607 happened during db open, shutting down database
USER: terminating instance due to error 607
Sat May 16 10:35:19 2009
Errors in file d:\oracle\visdb\9.2.0\admin\vis_apps\bdump\vis_pmon_2288.trc:
ORA-00607: Internal error occurred while making a change to a data block
Instance terminated by USER, pid = 2200
ORA-1092 signalled during: alter database open...
Pl. advice to recover from this suitation. New to recovery/bkup.
Thanks,
Sashi.

00607, 00000, "Internal error occurred while making a change to a data block"
// *Cause: An internal error or memory exception occurred while Oracle was
// applying redo to a data block.
// *Action: call Oracle Support

ORA-301 Signalled during: ALTER DATABASE ...

Hi,
I tried to add 4 standby redologs to our standby setup, and first file went well.
theothers already got error ORA-301:
ALTER DATABASE ADD STANDBY LOGFILE GROUP 8 '/export/home/oracle/logs/redo8.log' SIZE 2G
Fri May 31 15:31:22 2013
Completed: ALTER DATABASE ADD STANDBY LOGFILE GROUP 8 '/export/home/oracle/logs/redo8.log' SIZE 2G
ALTER DATABASE ADD STANDBY LOGFILE GROUP 9 '/export/home/oracle/logs/redo9.log' SIZE 2G
ORA-301 signalled during: ALTER DATABASE ADD STANDBY LOGFILE GROUP 9 '/export/home/oracle/logs/redo9.log' SIZE 2G...
ALTER DATABASE ADD STANDBY LOGFILE GROUP 10 '/export/home/oracle/logs/redo10.log' SIZE 2G
ORA-301 signalled during: ALTER DATABASE ADD STANDBY LOGFILE GROUP 10 '/export/home/oracle/logs/redo10.log' SIZE 2G...
ALTER DATABASE ADD STANDBY LOGFILE GROUP 11 '/export/home/oracle/logs/redo11.log' SIZE 2G
ORA-301 signalled during: ALTER DATABASE ADD STANDBY LOGFILE GROUP 11 '/export/home/oracle/logs/redo11.log' SIZE 2G...
Fri May 31 16:33:39 2013
I tried to track any info in the web and metalink, but it's the first time I encounter an ORA error with no documentation... :(
Some facts:
The oracle is 11.2.0 on Linux
There is no space issue on disk
Thanks for any help/ideas...

thanks for the reply.
first one I stated in the original post. there is tons of storage :)
for the others 2 -
user has priviledge... he created the first file succesfully...
those files do not exist on the disk already.
Thanks

ORA-1624 signalled during: ALTER DATABASE CLEAR....

Hi,
I get this error in my alert file what it means?
ORA-1624 signalled during: ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 1...
Thanks
Edited by: vittel on Sep 3, 2008 1:28 PM
Edited by: vittel on Sep 3, 2008 1:29 PM

Hi,
First thanks for your quick response.
The only thing that we have running in the database is a scheduled program how run every 3 min to switch the current log and he applied the archive log to the standby database!!!
It can be a session how is trying to do this "Alter database clear unarchived logfile...." ?
Thanks

ORA-1109 signalled during: alter database close

Hi
i have found the following error in alert log after i shut down my database for cold backup
alter database close
ORA-1109 signalled during: alter database close...
Please advice is there any threat because of this error and whats the reason for the occurence of this error.
Version of DB: 10.2.0.4.0
I have DR configured for this db also..
Regards,
Arun Kumar

Thats not the command i am using..
I just use shutdown immediate.. when i use that command i get the sequnce of steps logged in alert log..
there i find the error.. see below..(a part of alert log content)
Shutting down instance: further logons disabled
Sun Aug 9 19:12:39 2009
Stopping background process CJQ0
Sun Aug 9 19:12:39 2009
Stopping background process MMNL
Sun Aug 9 19:12:40 2009
Stopping background process MMON
Sun Aug 9 19:12:41 2009
Shutting down instance (immediate)
License high water mark = 5
Sun Aug 9 19:12:41 2009
Stopping Job queue slave processes, flags = 7
Sun Aug 9 19:12:41 2009
Job queue slave processes stopped
Sun Aug 9 19:12:41 2009
alter database close
ORA-1109 signalled during: alter database close...*
Sun Aug 9 19:12:41 2009
alter database dismount
Completed: alter database dismount
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes

ORA-604 signalled during: create tablespace

Hello,
While creating the my_idx_tablespace tablespace. I am getting ORA-604 error.
=====================================================================
Wed Mar 10 18:16:32 2010
create tablespace my_idx_tablespace
datafile 'E:\Oracle\Database\my_idx.dbf' size 1024m reuse
blocksize 8192
extent management local
segment space management auto
online
Wed Mar 10 18:18:13 2010
ORA-604 signalled during: create tablespace my_idx_tablespace
datafile 'E:\Oracle\Database\my_idx.dbf' size 1024m reuse
blocksize 8192
extent management local
segment space management auto
online...
Wed Mar 10 18:21:31 2010
drop tablespace log1_tablespace including contents and datafiles
ORA-959 signalled during: drop tablespace log1_tablespace including contents and datafile
=====================================================================
Any suggestion ?
OS: Windows 2003 32 bit machine.
Oracle: Oracle 10g enterprise edition 10.2.0.3
Thanks
With Regards
Hemant.

Hi,
Thanks for your response.
I will upload the log ASAP.
Can you please let me know some pointer for this error.
Thanks
With Regards
Hemant.

ORA-01666: controlfile is for a standby database - My DB Doesn't OPEN

dear Gurus,
I've created a Standby, and Configured the Dataguard no issues.
I've start a swtchover into Site 2
After half an Hour without responding I cancle the operation.
Now I'm facing this Situation, My Standby Site still Ok but my Prod Database shows ORA-01666: controlfile is for a standby database
What shall i do?
When I check the Config in the Dataguard Broker everything seems ok for SITE 2
DGMGRL> show site verbose 'CFMP_SITE2';
Site
Name: 'CFMP_SITE2'
Hostname: 'srvsdmwebp02'
Instance name: 'CFMP'
Service Name: 'CFMP_SITE2'
Standby Type: 'physical'
Number Built-in Processes: '2'
Number Generic Processes: '0'
Enabled: 'yes'
Required: 'yes'
Default state: 'STANDBY'
Intended state: 'STANDBY'
PFILE: ''
Number of resources: 1
Resources:
Name: CFMP_SITE2 (default) (verbose name='CFMP_SITE2')
Current status for "CFMP_SITE2":
SUCCESS
DGMGRL>
But in Site 1 it's different
DGMGRL>
DGMGRL> show site verbose 'CFMP_SITE1';
Site
Name: 'CFMP_SITE1'
Hostname: 'srvsdmwebp01'
Instance name: 'CFMP'
Service Name: 'CFMP_RW.world'
Standby Type: 'physical'
Number Built-in Processes: '2'
Number Generic Processes: '0'
Enabled: 'yes'
Required: 'yes'
Default state: 'PRIMARY'
Intended state: 'PRIMARY'
PFILE: ''
Number of resources: 1
Resources:
Name: CFMP_SITE1 (default) (verbose name='CFMP_SITE1')
Current status for "CFMP_SITE1":
Warning: ORA-16609: one or more resources have failed
How shall I proceed ?
Thxs

Dear Gurus,
Thxs for all your replys,
You really help Me, anyhow, now i could Start at Least one database, the Secondary SITE is Up and running
But when I check the Dataguard Broker I get
DGMGRL> show resource verbose 'CFMP_SITE2';
Resource
Name: CFMP_SITE2
Manager Type: internal
Standby Type: PHYSICAL
Online States:
ONLINE
PHYSICAL-APPLY-READY
PHYSICAL-APPLY-ON
READ-ONLY
LOGICAL-APPLY-READY
LOGICAL-APPLY-ON
READ-WRITE
READ-WRITE-XPTON
Properties:
INTENDED_STATE = 'PHYSICAL-APPLY-ON'
ENABLED = 'yes'
IGNORE_STATUS = 'no'
LogXptMode = 'ASYNC'
Dependency = ''
Alternate = ''
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
ReopenSecs = '300'
AsyncBlocks = '16384'
LogShipping = 'ON'
ApplyNext = '0'
ApplyNoDelay = 'NO'
ApplyParallel = '1'
StandbyArchiveDest = '/u03/archive/CFMP'
LogArchiveTrace = '0'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '1800'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = ' , '
LogFileNameConvert = ' , '
LogArchiveFormat = 'CFMP_%s.arc'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
SbyLogQueue = '(monitor)'
Properties for 'PRIMARY' state:
DEFAULT_STATE = 'READ-WRITE-XPTON'
EXPLICIT_DISABLE = 'no'
REQUIRED = 'yes'
Properties for 'STANDBY' state:
DEFAULT_STATE = 'PHYSICAL-APPLY-ON'
EXPLICIT_DISABLE = 'no'
REQUIRED = 'yes'
Current status for "CFMP_SITE2":
Error: ORA-16762: Invalid database state
I don't get ???? Can we really seriouslly trust this DATAGUARD stuff ????

ORA-16831: operation disallowed on this standby database type

Om my primary database, i am getting this error when i give ADD database command. How i can resolve. The difference between primary & secondary is that primary is 64bit OS and secondary is 32bit OS. Both have 12gr2 and linux.
DGMGRL> ADD DATABASE tbdb AS CONNECT IDENTIFIER IS tbdb MAINTAINED AS PHYSICAL;
Error: ORA-16831: operation disallowed on this standby database type

It's supported till 10g. But data guard broker is not supported if you use different binaries. See support note 414043.1
Also http://emrebaransel.blogspot.com/2010/12/dataguard-on-different-operating.html

ORA-604 signalled during: ALTER TABLESPACE...

Oracle 10.2.0.4 EE, Server 2003...
Today I wanted to add new datafile…
First I restart the instance and then used EM to add datafile… After 5 minutes process failed and in AlertSID.ora I get this message:
===========================================================
Mon Feb 08 10:23:04 2010
ALTER TABLESPACE "R1" ADD DATAFILE 'D:\Datafile\R03.DBF' SIZE 15000M AUTOEXTEND ON NEXT 512M MAXSIZE 32767M
Mon Feb 08 10:28:08 2010
ORA-604 signalled during: ALTER TABLESPACE "R1" ADD DATAFILE 'D:\Datafile\R03.DBF' SIZE 15000M AUTOEXTEND ON NEXT 512M MA…
===========================================================
Then I create datafile with command prompt and everything was fine, new datafile was added.
Any Ideas why does this happen?
Thanks!

Error message was only:
Mon Feb 08 10:28:08 2010
ORA-604 signalled during: ALTER TABLESPACE "R1" ADD DATAFILE 'D:\Datafile\R03.DBF' SIZE 15000M AUTOEXTEND ON NEXT 512M MAXSIZE 32767M
As I said, I used EM and after 5 minutes EM connection failed. Then I re-connect and EM don’t show me any errors, everything was fine but new datafile was not added. Only I get error message in AlertSID.ora…

ORA-1113 signalled during: alter database open...

Hello,
Today when I was unable to logon to my Oracle 9i database on Windows machine, I referred to the Alter.log file.
This file showed me the above error.
And when I try to logon to database with normal user, I get the error as "Database initialization or shutdown is in progress"
When I tried to log on using the DBA privileges, I can see that my Database is MOUNTED.
What should I do next? Do I bring the database down forcefully using the "Shutdown abort" command? and then at the startup when some datafile is shown as required to recovery then, recover the datafile using following command:
RECOVER AUTOMATIC DATAFILE 'file_Path';
Please guide
Thanks in advance
Himanshu

ORA-01113 file string needs media recovery
Cause: An attempt was made to open a datafile that is in need of media recovery.
Action: First apply media recovery to the datafile identified in the message, then retry the operation.
media recovery for datafile is required
log as sys user.
shutdown the database
startup mount
recover datafile <filename>
alter database open

ORA-1543 signalled during: create tablespace TSP222_TBL

Can someone please tell me what this error means... What things should I check? Oracle 10g

http://www.oracle.com/pls/db102/print_hit_summary?search_string=ORA-01543

10g standard edition, create a manual standby without ORA-279 and ORA-308.

Hi,
I have a 10 g database 10g r2 on linux rhel 5.2. I've create a standby database from an rman backup on another server (same name, same path....).
every 10 minutes , i switch log on primary database and rsync them to the stanby path on stanby server.
every 10 minutes, i apply the new received archive to the standby database with this script :
sqlplus /nolog
connect / as sysdba
recover database until cancel using backup controlfile;
AUTO
recover database until cancel using backup controlfile;
CANCEL
exit
this script gives some ORA errors like this :
2010/03/31 Wed 11:30:03 Media Recovery Log /v4/db/oradata/LFEX/archives/1_61705_640182036.dbf
2010/03/31 Wed 11:30:03 ORA-308 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
2010/03/31 Wed 11:30:04 ORA-279 signalled during: ALTER DATABASE RECOVER database until cancel using backup controlfile ...
2010/03/31 Wed 11:40:01 ORA-279 signalled during: ALTER DATABASE RECOVER database until cancel using backup controlfile ...
I understand this error, the script is searching the next archive, which doesn't exist at this time, that's OK.
To avoid to have this error, i believe that i can do something like that:
sqlplus /nolog
connect / as sysdba
recover database until time 'sysdate-1/(24*4)' using backup controlfile;
AUTO
exit
i'm searching to replay the archive and stop 15 minutes before sysdate, Is it possible?
when i try this, i have this message :
SQL> recover database until time 'sysdate-1/(24*4)' using backup controlfile;
ORA-01841: L'année (complète) doit être comprise entre -4713 et +9999 et être
différente de 0.
I'm trying to change nls_date_format, nls_lang without any success.
thx.
Antoine.

i found a script to do an automatic recover script like this :
recover database until time '2010-04-01:16:49:05' using backup controlfile;
ORA-00279: changement 2456430208 généré à 04/01/2010 16:31:01 requis pour thread 1
ORA-00289: suggestion : /v4/db/oradata/LFEX/archives/1_61853_640182036.dbf
ORA-00280: le changement 2456430208 pour le thread 1 se trouve au no de séquence 61853
ORA-00279: changement 2456432030 généré à 04/01/2010 16:39:01 requis pour thread 1
ORA-00289: suggestion : /v4/db/oradata/LFEX/archives/1_61854_640182036.dbf
ORA-00280: le changement 2456432030 pour le thread 1 se trouve au no de séquence 61854
ORA-00278: le fichier journal
'/v4/db/oradata/LFEX/archives/1_61853_640182036.dbf' n'est plus nécessaire pour cette récupération
So i continue to have some error like ORA-278.... but no more ORA-308 error, it's better, because ORA-278 279 and 280 are only information messages, so i can ignore it in alert.log files.
Only ORA-308 in this case interresting me, to see if an archive is really missing.
thx.
PS : the script standby_recover generate the recover.sql script :
[dblegu@dbback SQL]$ cat $PGLEGU/SQL/standby_recover.sql
connect sys/password as sysdba
set trimspool on linesize 200 head off feedback off sqlprompt "--" verify off
spool &1/SQL/recover.sql
select 'connect sys/password as sysdba'||chr(10)||
'set autorecovery on'||chr(10)||
'recover database until time '''||
to_char(sysdate - 1/(24*4),'YYYY-MM-DD:HH24:MI:SS')||''' using backup controlfile;'||chr(10)||
'exit;' from dual;
spool off
exit
the resul in recover.sql is :
connect sys/password as sysdba
set autorecovery on
recover database until time '2010-04-01:16:49:05' using backup controlfile;
exit;
i found this on site : http://erkanorclog.blogspot.com/2007/08/batch-scripts-to-set-up-asyncronous.html.
Edited by: fleuron on 1 avr. 2010 09:04

Standby Database gives error ORA-03113:ORA-03114

Hi
I am using oracle 9iR2 on standby database when i recover it return errors like
SQL> recover standby database;
ORA-00279: change 8209765386 generated at 07/18/2008 12:10:41 needed for thread
1
ORA-00289: suggestion : J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86548.ARC
ORA-00280: change 8209765386 for thread 1 is in sequence #86548
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 8209782309 generated at 07/18/2008 12:22:05 needed for thread
1
ORA-00289: suggestion : J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86549.ARC
ORA-00280: change 8209782309 for thread 1 is in sequence #86549
ORA-00278: log file 'J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86548.ARC' no
longer needed for this recovery
ORA-03113: end-of-file on communication channel
ORA-03114: not connected to ORACLE
Alert log display
Starting datafile 1 recovery in thread 1 sequence 86551
Datafile 1: 'E:\ORANT\ORADATA\APR1\SYSTEM01.DBF'
Starting datafile 3 recovery in thread 1 sequence 86551
Datafile 3: 'E:\ORANT\ORADATA\APR1\CWMLITE01.DBF'
Starting datafile 4 recovery in thread 1 sequence 86551
Datafile 4: 'E:\ORANT\ORADATA\APR1\DRSYS01.DBF'
Starting datafile 5 recovery in thread 1 sequence 86551
Datafile 5: 'E:\ORANT\ORADATA\APR1\EXAMPLE01.DBF'
Starting datafile 6 recovery in thread 1 sequence 86551
Datafile 6: 'E:\ORANT\ORADATA\APR1\INDX01.DBF'
Starting datafile 7 recovery in thread 1 sequence 86551
Datafile 7: 'E:\ORANT\ORADATA\APR1\ODM01.DBF'
Starting datafile 8 recovery in thread 1 sequence 86551
Datafile 8: 'E:\ORANT\ORADATA\APR1\TOOLS01.DBF'
Starting datafile 9 recovery in thread 1 sequence 86551
Datafile 9: 'J:\ORACLE\ORADATA\APR1\USERS01.DBF'
Starting datafile 10 recovery in thread 1 sequence 86551
Datafile 10: 'E:\ORANT\ORADATA\APR1\XDB01.DBF'
Starting datafile 11 recovery in thread 1 sequence 86551
Datafile 11: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_E.DBF'
Starting datafile 12 recovery in thread 1 sequence 86549
Datafile 12: 'J:\ORACLE\ORADATA\APR1\APR_DATA4_C.DBF'
Starting datafile 13 recovery in thread 1 sequence 86550
Datafile 13: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_D.DBF'
Starting datafile 14 recovery in thread 1 sequence 86550
Datafile 14: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_A.DBF'
Starting datafile 15 recovery in thread 1 sequence 86548
Datafile 15: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_B.DBF'
Starting datafile 16 recovery in thread 1 sequence 86550
Datafile 16: 'J:\ORACLE\ORADATA\APR1\APR_DATA1_A.DBF'
Starting datafile 17 recovery in thread 1 sequence 86550
Datafile 17: 'J:\ORACLE\ORADATA\APR1\APR_DATA1_B.DBF'
Starting datafile 18 recovery in thread 1 sequence 86550
Datafile 18: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_A.DBF'
Starting datafile 19 recovery in thread 1 sequence 86549
Datafile 19: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_B.DBF'
Starting datafile 20 recovery in thread 1 sequence 86549
Datafile 20: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_C.DBF'
Starting datafile 25 recovery in thread 1 sequence 86550
Datafile 25: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_A.DBF'
Starting datafile 26 recovery in thread 1 sequence 86550
Datafile 26: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_B.DBF'
Starting datafile 27 recovery in thread 1 sequence 86550
Datafile 27: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_C.DBF'
Starting datafile 28 recovery in thread 1 sequence 86550
Datafile 28: 'J:\ORACLE\ORADATA\APR1\APR_MVIEWS_A.DBF'
Starting datafile 29 recovery in thread 1 sequence 86550
Datafile 29: 'J:\ORACLE\ORADATA\APR1\BLOB_A.DBF'
Starting datafile 30 recovery in thread 1 sequence 86549
Datafile 30: 'J:\ORACLE\ORADATA\APR1\HR_DATA1_A.DBF'
Starting datafile 31 recovery in thread 1 sequence 86548
Datafile 31: 'J:\ORACLE\ORADATA\APR1\HR_DATA2_A.DBF'
Starting datafile 32 recovery in thread 1 sequence 86550
Datafile 32: 'J:\ORACLE\ORADATA\APR1\HR_INDX1_A.DBF'
Starting datafile 33 recovery in thread 1 sequence 86550
Datafile 33: 'J:\ORACLE\ORADATA\APR1\HR_INDX2_A.DBF'
Starting datafile 34 recovery in thread 1 sequence 86548
Datafile 34: 'J:\ORACLE\ORADATA\APR1\INVENTORY_A.DBF'
Starting datafile 35 recovery in thread 1 sequence 86550
Datafile 35: 'J:\ORACLE\ORADATA\APR1\INVENTORY_INDX_A.DBF'
Starting datafile 36 recovery in thread 1 sequence 86550
Datafile 36: 'E:\ORANT\ORADATA\APR1\SAMPLE_DATA1_A.DBF'
Starting datafile 37 recovery in thread 1 sequence 86550
Datafile 37: 'J:\ORACLE\ORADATA\APR1\VMS_DATA1_A.DBF'
Starting datafile 38 recovery in thread 1 sequence 86550
Datafile 38: 'J:\ORACLE\ORADATA\APR1\APR_MMS_A.DBF'
Starting datafile 39 recovery in thread 1 sequence 86550
Datafile 39: 'J:\ORACLE\ORADATA\APR1\AUDIT_DATA_A.DBF'
Starting datafile 40 recovery in thread 1 sequence 86549
Datafile 40: 'J:\ORACLE\ORADATA\APR1\UNDOTBS.DBF'
Starting datafile 41 recovery in thread 1 sequence 86550
Datafile 41: 'J:\ORACLE\ORADATA\APR1\APR_DATA1_C.DBF'
Starting datafile 42 recovery in thread 1 sequence 86549
Datafile 42: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_E.DBF'
Starting datafile 43 recovery in thread 1 sequence 86548
Datafile 43: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_C.DBF'
Starting datafile 44 recovery in thread 1 sequence 86550
Datafile 44: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_E.DBF'
Starting datafile 46 recovery in thread 1 sequence 86550
Datafile 46: 'E:\ORANT\ORADATA\APR1\SYSTEM02.DBF'
Starting datafile 47 recovery in thread 1 sequence 86550
Datafile 47: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_A.DBF'
Starting datafile 48 recovery in thread 1 sequence 86549
Datafile 48: 'J:\ORACLE\ORADATA\APR1\APR_DATA4.DBF'
Starting datafile 49 recovery in thread 1 sequence 86550
Datafile 49: 'J:\ORACLE\ORADATA\APR1\APR_DATA4_A.DBF'
Starting datafile 50 recovery in thread 1 sequence 86548
Datafile 50: 'J:\ORACLE\ORADATA\APR1\APR_DATA4_B.DBF'
Starting datafile 51 recovery in thread 1 sequence 86550
Datafile 51: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_B.DBF'
Starting datafile 52 recovery in thread 1 sequence 86550
Datafile 52: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_A.DBF'
Starting datafile 53 recovery in thread 1 sequence 86550
Datafile 53: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_B.DBF'
Starting datafile 54 recovery in thread 1 sequence 86550
Datafile 54: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_C.DBF'
Starting datafile 55 recovery in thread 1 sequence 86550
Datafile 55: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_D.DBF'
Starting datafile 56 recovery in thread 1 sequence 86549
Datafile 56: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_C.DBF'
Starting datafile 57 recovery in thread 1 sequence 86550
Datafile 57: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_F.DBF'
Starting datafile 58 recovery in thread 1 sequence 86550
Datafile 58: 'J:\ORACLE\ORADATA\APR1\APR_DATA6_A.DBF'
Starting datafile 59 recovery in thread 1 sequence 86548
Datafile 59: 'J:\ORACLE\ORADATA\APR1\APR_DATA6_B.DBF'
Starting datafile 60 recovery in thread 1 sequence 86549
Datafile 60: 'J:\ORACLE\ORADATA\APR1\APR_DATA6_C.DBF'
Starting datafile 61 recovery in thread 1 sequence 86549
Datafile 61: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_D.DBF'
Starting datafile 62 recovery in thread 1 sequence 86550
Datafile 62: 'J:\ORACLE\ORADATA\APR1\APR_INDX5_A.DBF'
Starting datafile 63 recovery in thread 1 sequence 86550
Datafile 63: 'J:\ORACLE\ORADATA\APR1\APR_INDX5_B.DBF'
Starting datafile 64 recovery in thread 1 sequence 86550
Datafile 64: 'E:\ORANT\ORADATA\APR1\USERS01_A.DBF'
Starting datafile 65 recovery in thread 1 sequence 86550
Datafile 65: 'J:\ORACLE\ORADATA\APR1\GMT1_DATA.DBF'
Starting datafile 66 recovery in thread 1 sequence 86548
Datafile 66: 'J:\ORACLE\ORADATA\APR1\GMT1_INDX.DBF'
Starting datafile 67 recovery in thread 1 sequence 86550
Datafile 67: 'J:\ORACLE\ORADATA\APR1\APR_DATA7.DBF'
Starting datafile 68 recovery in thread 1 sequence 86550
Datafile 68: 'J:\ORACLE\ORADATA\APR1\APR_INDX7A.ORA'
Starting datafile 69 recovery in thread 1 sequence 86550
Datafile 69: 'J:\ORACLE\ORADATA\APR1\APR_INDX8_A.DBF'
Starting datafile 70 recovery in thread 1 sequence 86550
Datafile 70: 'J:\ORACLE\ORADATA\APR1\APR_INDX8_B.DBF'
Media Recovery Log
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
Wed Jul 23 11:26:24 2008
ALTER DATABASE RECOVER CONTINUE DEFAULT
Wed Jul 23 11:26:24 2008
Media Recovery Log J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86548.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Wed Jul 23 11:26:25 2008
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86549.ARC
Wed Jul 23 11:26:53 2008
Some recovered datafiles maybe left media fuzzy
Media recovery may continue but open resetlogs may fail
Wed Jul 23 11:26:53 2008
ARC0: terminating instance due to error 472
Instance terminated by ARC0, pid = 2100
Tell me the solution.
Thanks in advance

I think your database is not going in begin backup mode...
this is my standby database server Pratap is there any method to check backup mode .
Thanks

ORA-279 signalled during recovery of standby database

Similar Messages

Maybe you are looking for