Force logging in archivelog mode

Hi !!!
What happen if I have "force_logging" parameter set to true when the database is in archivelog mode ?
Thanks.

rarain wrote:
Hi Juamd,
You should only use this option when it is really required because this option will forcibly generate redo for all Nologging operations that means you might find more archives and you need to setup more space for archive.
Normally we use this option when we need to replicate data changes from one database to another database like in standby configuration, Golden Gate replication etc. I would suggest you to monitor Redo amount generated after enabling this option and accordingly estimate archive space and backup space for archive.
Thanks...Ah, don't agree with that at all. You can compromise your recovery if you happen to want to restore to a point-in-time when there was a NOLOGGING operation going on. Fine, if it's an index, but if it happens to be on a table...
(Yes, been there, done that - with a non-Production database, thankfully)
This is one of the 'must haves', IMO, for Production - set it at the database-level and it overrides any tablespace or object setting.
Archivelogs are generated for a reason. If you have a particular operation that really does massively benefit from NOLOGGING and is something you are sure that you simply re-run/re-create yourself, fine. If not, by default, you really should FORCE LOGGING.

Similar Messages

No archivelog mode and logging option

hi i am having a database 9i on windows 2000 adv server. my database is in no archivelog mode. i am creating a table with logging option as follows
create table x(no number(1))
logging;
table created
please let me know where the information will be logged? whether into trace files because database is in no archivelog mode.

Logging information is always recorded in your redolog files, irrespective whether your database is in ARCHIVELOG mode or NOARCHIVELOG mode.
By default a table is created in LOGGING mode, you don't have to explicitly specify it.
Here is an example:
SQL> archive log list
Database log mode              No Archive Mode
Automatic archival             Disabled
Archive destination            /u10/app/oracle/product/oracle10g/dbs/arch
Oldest online log sequence     11
Current log sequence           13
SQL> create table t(a number);
Table created.
SQL> select logging from user_tables where table_name = 'T';
LOG
YES

Why we need oracle database reboot to put database in archivelog mode?

I know how to enable archivelog mode, but what is the reason that to enable archive log we need database restart. which process forces to do that.

SantoshGanjure wrote:
Thanks a lot EdStevens for ur prompt response...I need something that satisfies my managers query.
If the question has originated with the PHB, then my flippant answer is even more relevant ...
PHB's are incapable of understanding the technical details, so I prefer to give them the 'executive summary':
"Because that's the way Oracle is written. We can argue over the technical merits of such a requirement 'till the cows come home. But at the end of the day, we have to shut down the database because the 'alter database archivelog' command will only succeed when the database is in mount (not open) mode. Now, let's work out how we can achieve our objective of putting the database in archivelog mode with minimal and appropriately scheduled down time."
As for the actual down time, it's about as minimal as you can get. How long does it take your database to complete a shutdown once the command is given? How long does it take you to type "startup mount"? How long does it take you to type "alter database archivelog"? to type "alter database open;"? For the database to complete the 'open' process? You could even script it so as to eliminate the keyboard typing time.

Problem running oracle 9i database in archivelog mode - database freezes

Greetings,
I recently needed to change a (test) database to archivelog mode to make online back-ups of this database. This posed no real problem although I seem to be unable to set the database to automatic archiving eventhough I edited the init.ora file (translation of the "archive log list" output between square brackets):
SQL> archive log list
Databaselogmodus Archiveermodus [Databaselogmode: Archivemode]
Automatisch archiveren Gedeactiveerd [Automatic archiving: Deactivated]
Archiveerbestemming O:\oracle\ora92\RDBMS [Archivedestionation: O:\oracle\ora92\RDBMS]
Oudste on-line logreeks 12306
Volgende logreeks voor archivering 12306
Huidige logreeks 12308
I added this to my init.ora file:
# Archvie Log Destinations
log_archive_start=TRUE
log_archive_dest_1=%ORACLE_HOME%\database\archive
log_archive_format="%%ORACLE_SID%%t_%s.arc"
However, this is not the real problem (maybe it has something to do with it, which is why I mention it aswell), the real problem is that my database freezes when the archive log file is "full". When the archive file reaches ~102.400Kb it just freezes up and I need to restart the database.
The following error is written to the alert_sid.log file:
Thu Apr 17 09:19:55 2008
Thread 1 cannot allocate new log, sequence 12309
All online logs needed archiving
Current log# 2 seq# 12308 mem# 0: O:\ORACLE\ORADATA\O\REDO02.LOG
The problem seems to be that the oracle service can't start a new logfile when the previous one is full. Does anybody know how I could fix this?
Thanks in advance,
Bram

Hello Maran, thanks for your quick response.
I added the output of archivelog list in the original post, but it's in dutch so here's the (loose) translation of the output:
SQL> archive log list
Databaselog mode Archive mode
Automatic archiving Deactivated
Archive destionation O:\oracle\ora92\RDBMS
Oldest on-line logsequence 12307
Next logsequence for archiving 12307
Current logsequence 12309
Maybe something that can help with the troubleshooting:
The archivelog file is written to O:\oracle\ora92\RDBMS but only AFTER the reboot, I've checked SYSTEM rights to the folder and it has full control.
Babu, thanks aswell for your quick response.
The location exists and space is available but the database doesn't seem to load (that part of) the ora.init file because the output of archive log list still refers to %ORACLE_HOME%\rdbms instead of %ORACLE_HOME%\database\archive.
I've now executed alter system archive log all; and am executing the import where the database usually freezes to see if it still happens. So far I already had this written to the alert_sid.log file after executing the command:
Completed: alter database open
Thu Apr 17 10:00:11 2008
ARCH: Evaluating archive log 1 thread 1 sequence 12307
ARCH: Beginning to archive log 1 thread 1 sequence 12307
Creating archive destination LOG_ARCHIVE_DEST_1: 'O:\ORACLE\ORA92\RDBMS\ARC12307.001'
ARCH: Completed archiving log 1 thread 1 sequence 12307
ARCH: Evaluating archive log 2 thread 1 sequence 12308
ARCH: Beginning to archive log 2 thread 1 sequence 12308
Creating archive destination LOG_ARCHIVE_DEST_1: 'O:\ORACLE\ORA92\RDBMS\ARC12308.001'
ARCH: Completed archiving log 2 thread 1 sequence 12308
And new log files were written to the directory (O:\oracle\ora92\RDBMS) and this time I didn't have to reboot for it to happen. Both were 100mb files without the database actually doing all that much though.
Message was edited by:
user616266

Restore database in archivelog mode

Hello everyone.
I've been looking on google, how to restore my database on archivelog mode, but i did not succeed.
I made my backup using this mode, and now i need to know what is the command need to use to restore this.
Somebody can write the command here please ?
Thanks for help.
Regards,
Dan
ps: Using Oracle 10g XE on Win XP.

user8973191 wrote:
Oh, ok Vijayaraghavan K.
Thx for u help.
And about the users ?
i need to create the "same" user in another machine ?
For example:
In this machine i using the "system" user, where i have my tables.
Another machine, when i restore, my tables will go to the "system" user too? or i can choice? or i need to create one?A true backup is a copy of the data files at the file/block level. The restore is therefore a restore of the data files/blocks. Applying the redo (archive logs) is also done at the block level. None of that knows or cares (or needs to know or care) about logical objects (such as users, tablespaces, tables, rows, etc) within the database. so if you do a proper restore, you are restoring files to a consistent state and thus everything that was defined within those files will be there when restored.

Database in Archivelog mode

Hi
All,
I have oracle 9.2.0.6 at my workplace.right now my database running in ARCHIVELOG MODE. I want to set it to NOARCHIVELOG MODE.
can I do on the fly? in other way, Do I need to shutdown and restart database?
Any help will be appreciated.
Thanks,
Vishal

Hi,
Issue the following commands to put a database into NOARCHVELOG mode:
1) Take Back up of Present SPfile by creating pfile
create pfile from present spfile.
2) Shutdown the database by SUTDOWN IMMEDIATE.
3) Take Cold backup of the database.
4) Change the parameter in the pfile.
log_archive_start = FALSE
#log_archive_dest_1 = 'LOCATION='Your location'
log_archive_dest_state_1 = DISABLE
#log_archive_format = %d_%t_%s.arc
5) And make a spfile from the modified pfile in default location .
6) Start the database with spfile.
SQL> CONNECT sys AS SYSDBA
SQL> STARTUP MOUNT ;
SQL> ALTER DATABASE ARCHIVELOG;
SQL> ARCHIVE LOG START;
SQL> ALTER DATABASE OPEN;
NOTE 1: Remember to take a baseline database backup right after disabling archivelog mode. Without it one would not be able to recover.
Regards
Jafar

Problem in Converting Database into Archivelog mode (Oracle 10G)

Hi Team,
I come across a strange problem in the ORACLE 10G Server.
I am converting database mode from NoArchivelog to Archivelog mode through RMAN in 10G.
Now When I execute these following commands through RMAN prompt it works properly as shown below?
C:\>rman
Recovery Manager: Release 10.2.0.1.0 - Production on Thu Nov 30 18:01:08 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN> connect target /
connected to target database: RAVI (DBID=4025722893, not open)
RMAN> shutdown immediate;
using target database control file instead of recovery catalog
database dismounted
Oracle instance shut down
RMAN> STARTUP MOUNT;
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area 167772160 bytes
Fixed Size 1247876 bytes
Variable Size 79693180 bytes
Database Buffers 79691776 bytes
Redo Buffers 7139328 bytes
RMAN> SQL 'ALTER DATABASE ARCHIVELOG';
sql statement: ALTER DATABASE ARCHIVELOG
RMAN> ALTER DATABASE OPEN;
database opened
RMAN>
But this same script when i writes in the backup.ora file & pass to Rman prompt it fails,
File backup.ora contains...
run
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
SQL 'ALTER DATABASE ARCHIVELOG';
ALTER DATABASE OPEN;
passed to RMAN as follows...
C:\OracleCode\BACKUP>"C:\oracle\product\10.2.0\db_1\bin\RMAN.EXE" target /"connect target SYSTEM/sreedhar@RAVI" log="C:\ORACLE~2\LOGS\backup_log.log" append cmdfile="C:\ORACLE~2\BACKUP\backup.ora"
RMAN> 2> 3> 4> 5> 6> 7> 8>
then it fails giving the following errors...
using target database control file instead of recovery catalog
database closed
database dismounted
Oracle instance shut down
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of startup command at 11/30/2006 18:05:59
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Recovery Manager complete.
The same thing is working in the Oracle 9i but not in the Oracle 10G.
Can Anybody plz help me in this?
Regards,
S.Tiwari
.

export ORACLE_SID=<SID>
rman target /cmdfile="C:\ORACLE~2\BACKUP\backup.ora"
it will connect to the default SID, there's no such thing as a default SID, what do you mean?
But what if there are more that one SID available & I
want to connect to SID other than the default SID.just specify the desired SID prior starting rman.
more over the same string is working with 9i but not
with 10G.maybe due to a bug?
to summarize, you have two options it you would like to start up the instance:
either you specify the SID prior starting rman and use os authentication
or
you register the instance statically and use oracle authentication.
regards,
-ap

Database crashes when placed in Archivelog mode

My production database continues to crash when I place it in Archivelog mode. This happen especially during the period most of the heavy jobs is running. On the other hand, I created a clone of this very same database on another server in Archivelog mode and it is running great. It’s also honest to say the jobs that run on the production are not running in the clone.
Any advice will be appreciated.
Edited by: Albert Zaza on Apr 27, 2010 8:24 AM

>
Please post last 50 lines of the alert log (there should be a very readable error message).
Sun Jan 17 10:35:29 2010
Thread 1 advanced to log sequence 12834
Current log# 2 seq# 12834 mem# 0: J:\ORA_TPISG64A\TPISG64A\REDO02.LOG
Sun Jan 17 18:21:12 2010
Thread 1 advanced to log sequence 12835
Current log# 3 seq# 12835 mem# 0: J:\ORA_TPISG64A\TPISG64A\REDO03.LOG
Sun Jan 17 23:01:01 2010
Thread 1 advanced to log sequence 12836
Current log# 1 seq# 12836 mem# 0: J:\ORA_TPISG64A\TPISG64A\REDO01.LOG
Mon Jan 18 07:54:55 2010
Thread 1 advanced to log sequence 12837
Current log# 2 seq# 12837 mem# 0: J:\ORA_TPISG64A\TPISG64A\REDO02.LOG
Mon Jan 18 13:03:59 2010
KCF: write/open error block=0x22f online=1
file=2 J:\ORA_TPISG64A\TPISG64A\UNDOTBS01.DBF
error=27072 txt: 'OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.'
Mon Jan 18 13:03:59 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_dbw0_4136.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01114: IO error writing block to file 2 (block # 559)
ORA-01110: data file 2: 'J:\ORA_TPISG64A\TPISG64A\UNDOTBS01.DBF'
ORA-27072: File I/O error
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.
DBW0: terminating instance due to error 1242
Mon Jan 18 13:03:59 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_pmon_4588.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:00 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_lgwr_5068.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:00 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_j000_728.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:01 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_reco_4824.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:01 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_ckpt_4964.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:01 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_smon_4976.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:01 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_psp0_1584.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:02 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_mman_4364.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:13 2010
Instance terminated by DBW0, pid = 4136
Tue Jan 19 07:31:47 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 251658240
__large_pool_size = 16777216
__java_pool_size = 16777216
__streams_pool_size = 50331648
streams_pool_size = 50331648
nls_length_semantics = BYTE
resource_manager_plan =
sga_target = 5133828096
control_files = J:\ORA_TPISG64A\TPISG64A\CONTROL01.CTL, J:\ORA_TPISG64A\TPISG64A\CONTROL02.CTL, J:\ORA_TPISG64A\TPISG64A\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 4781506560
compatible = 10.2.0.2.0

Archivelog mode

I'd like to make sure of the following:
when the database works in noarchivelog mode it does not matter what's the value of log_archive_start parameter whether it is true or false .I mean if log_archive_start in this case is set to true it won't archive the full redolog files because the database is in noarchive mode,Am i right?
Thanks in advance.

The parameter archive_log_start controls whether or not the Archiver (arcN) process is started at database startup or not. If you are not in archivelog mode, then it is immaterial. If you are in archive log mode, then if archive_log_start is false, you will have to manually archive redo logs as the fill, otherwise the system will stop after it fills the last archive log.
Unless you are running a read only database, and know that it will never ever be modified (I have two such databases holding data from legacy systems), then you might as well set archive_log_start to TRUE. One day, you are going to want to put that test database into archivelog mode for some reason or another, and users screan really loudly when the system "hangs" because all the redo logs are filled.
Been there, done that, got the earplugs.
John

Can we put RAC database in Archivelog mode without shutting down

All,
Can we put RAC database in Archivelog mode without shutting down.
Currently our new production database (2 node RAC) is in no archive log mode, Need to enable archive log in the database...
I believe we need to set the cluster_database=false and then put the DB in archive log mode then we need to bounce the database to take effect...
Just curious to know in 11gR2 ...Can we put the RAC database in archive log mode without any downtime ...?

Even RAC or non-RAC, database should bounced and enable/disable archive log mode from mount status.

Advantage of FORCE LOGGING over NOLOGGING

Hi,
Can you please help me on the advantages of using force logging mode with a standby database and the effect of it in indexes etc. Also, it may help if you could also share ideas on difference between the two modes?
Thanks,
Jennah

<i>>> Can you help me what factors would be sacrificed</i>
This really depends on your system, in most cases you will not be able to see a difference. However i did a small test:
- drop index, restart db
- create index with logging (measure time/redo size)
- drop index, restart db
- create index with logging (measure time/redo size)
Result:
logging - Elapsed: 00:02:40.68 / Redo size: 800mb
nologging - Elapsed: 00:02:20.29 / Redo size: 1.5mb
Here the full test:
[code]SQL> select a.name, b.value from v$statname a, v$mystat b where a.statistic# = b.statistic# and a.name = 'redo size';
NAME                                                                  VALUE
redo size                                                             28304
SQL> CREATE UNIQUE INDEX "SAPR3"."CDCLS~0" ON "SAPR3"."CDCLS"
("MANDANT", "OBJECTCLAS", "OBJECTID", "CHANGENR", "PAGENO")
PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 65536 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "PSAPCLUI" LOGGING;
Index created.
Elapsed: 00:02:40.68
SQL> select a.name, b.value from v$statname a, v$mystat b where a.statistic# = b.statistic# and a.name = 'redo size';
NAME                                                                  VALUE
redo size                                                         834714816
SQL> select segment_name, bytes/1024/1024 "Size_MB" from dba_segments where segment_name = 'CDCLS~0'
SEGMENT_NAME            Size_MB
CDCLS~0                     800
drop index / db restart here
SQL> select a.name, b.value from v$statname a, v$mystat b where a.statistic# = b.statistic# and a.name = 'redo size';
NAME                                                                  VALUE
redo size                                                             28992
SQL> CREATE UNIQUE INDEX "SAPR3"."CDCLS~0" ON "SAPR3"."CDCLS"
("MANDANT", "OBJECTCLAS", "OBJECTID", "CHANGENR", "PAGENO")
PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 65536 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "PSAPCLUI" NOLOGGING;
Index created.
Elapsed: 00:02:20.29
SQL> select a.name, b.value from v$statname a, v$mystat b where a.statistic# = b.statistic# and a.name = 'redo size';
NAME                                                                  VALUE
redo size                                                           1520824
SQL> select segment_name, bytes/1024/1024 "Size_MB" from dba_segments where segment_name = 'CDCLS~0';
SEGMENT_NAME            Size_MB
CDCLS~0                     800[/code]

FORCE LOGGING

I want to create a physical standby database. The primary database is in archive log mode, and the 50% of the data belong to the staging area of datawarehouse. During ETL processes the database generates great amount of GBs of redologs. This tables contain temporary data that are only used for ETL process.
Can I set the database like FORCE LOGGING=N and set FORCE LOGGING=Y only for the tablespace that contain the tables of data (production, not intermediate) ???

If you are trying to run a physical standby, for any database larger and more important than a toy, across the internet you are doomed to failure.
Databases do not fail on predictable schedules.
A DR site means a DR site ... it does not mean someplace out there in the cloud. For all you know your redo is being shipped to the moon and
back. Buy room in a data center no more than 500km away from your current location.
DR is for serious people with serious issues. If you do not need it then don't build it. If you do need it build it correctly.

ARCHIVELOG mode needless for offline (cold) backups ?

When I read some tutorials or comments about backup with rman or expdb I saw often the recommendation to put database in ARCHIVELOG mode.
But this is from my point of view useless when I do such a backups in offline mode.
I want to backup the current state of the database - full stop.
Redo logs from ARCHIVELOG are not necessary. Only if I want to go further back from the current state back to the past they are of use.
Am I right?
Peter

Data pump does not require or use archivelog mode for importing, or exporting.
The archivelog mode is required, however, for RMAN backups, except for full database copy which it copies while the database is shutdown.
The Data Pump utility uses a parameter called FLASHBACK_SCN (and FLASHBACK_TIME) which reads the undo data, but not to be confused with archivelogs.
NOTE that if you set archivelog mode on, you may want to either turn off archivelog mode when importing, or set the tabelspaces to nologging (then back to logging when done). Otherwise, it may cause enough archive logs during import to fill up your file system.
Re: http://www.oracle.com/technology/products/manageability/database/pdf/ow06/Motorola_datapump.pdf
Hope this helps.
ji li

Startup in Archivelog mode

Hi.
I only will do a simply question:
If I have a database in archivelog mode, and ocurr a unexpected shutdown
is There some process that use these logs archived if it´s necesary automatically when I do a normal startup, or only will use the redo logs?
Thanks

Alex Tutor wrote:
Hi.
I only will do a simply question:
If I have a database in archivelog mode, and ocurr a unexpected shutdown
is There some process that use these logs archived if it´s necesary automatically when I do a normal startup, or only will use the redo logs?
ThanksNo ,in this case oracle(SMON) will use only online redo log and will perform instance recovery then database will open.Of course if there will not happen media failure.

Recover datafile in no archivelog mode

Hi, i have always done media recovery using RMAN and this works nicely.
However im doing some testing on a database that does not use RMAN and is not in archivelog mode and im confused.(11.2 - aix)
My testing is as follows;
With the database shutdown cleanly i have taken a copy of dbf file. I then open the database and delete the dbf file.
(to slightly digress how can i still view and update the table from this datafile when the dbf file is dropped?)
In scenario 1 i shutdown the database after dropping the file. I then put the dbf file back and try and startup the database.
I thought that as i have a complete consistent backup i would be able to open the database normally without recovery, but this produced an error saying the file needed media recovery so i recovered the datafile and put online and the the db opened normally.
In scenario 2 i again took a clean backup and removed the dbf file. I then opened my database and switched redo logs 3 times ( i have 3 redo logs). After the 3rd switch the database crashed (which makes sense).
I have tried opening it normally again butagain it says the file needs media recovery. i then tried to recover the file but now i the following error:
ORA-00279: change 6667823 generated at 12/17/2013 11:35:20 needed for thread 1
ORA-00289: suggestion :
/test/oracle/TSTA/TSTA/archivelog/2013_12_17/o1_mf_1_78_%u_.arc
ORA-00280: change 6667823 for thread 1 is in sequence #78
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Any help would be greatly appreciated

885842 wrote:
Hi, i have always done media recovery using RMAN and this works nicely.
However im doing some testing on a database that does not use RMAN and is not in archivelog mode and im confused.(11.2 - aix)
My testing is as follows;
With the database shutdown cleanly i have taken a copy of dbf file. I then open the database and delete the dbf file.
(to slightly digress how can i still view and update the table from this datafile when the dbf file is dropped?)
In all *nix systems, the file is still there and open by any processes that had it open when you issued the 'rm' command. It is not really deleted until all processes that have it open have terminated.
In scenario 1 i shutdown the database after dropping the file. I then put the dbf file back and try and startup the database.
I thought that as i have a complete consistent backup i would be able to open the database normally without recovery, but this produced an error saying the file needed media recovery so i recovered the datafile and put online and the the db opened normally.
The backup may have been consistent, but if you restored only that one file, it was several SCN's behind the other files that continued to be updated after you took the consistent backup. "Consistent" means not only consistent interally to the individual file, but consistent with all other data files, plus the control files, plus the redologs.
In scenario 2 i again took a clean backup and removed the dbf file. I then opened my database and switched redo logs 3 times ( i have 3 redo logs). After the 3rd switch the database crashed (which makes sense).
I have tried opening it normally again butagain it says the file needs media recovery. i then tried to recover the file but now i the following error:
ORA-00279: change 6667823 generated at 12/17/2013 11:35:20 needed for thread 1
ORA-00289: suggestion :
/test/oracle/TSTA/TSTA/archivelog/2013_12_17/o1_mf_1_78_%u_.arc
ORA-00280: change 6667823 for thread 1 is in sequence #78
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Any help would be greatly appreciated
You said you are not in archivelog mode. So where did this reference to an archivelog come from?

Force logging in archivelog mode

Similar Messages

Maybe you are looking for