Set Archivelog Mode

How can I turn on/off the Archivelog Mode for a database by using the OEM, (say, I launched the OEM at http://My_Machine:1158/oem, after I log on where I go next)?
Thanks to help.
Scott

Thanks for the response.
Now I am on the Recovery Settings page:
1) Under Media Recovery, I checked ARCHIVELOG Mode*
2) For the Log Archive Filename Format*, it carries the entry of: ARC%S_%R.%T, what should I replace %S, %R, abd %T with? --Could you give an example?
3)Under Number Archive Log Destination Quota (512B) Status Type, there are 10 lines for entries, so I filled with the following:
1 C:\Oracle\product\archivelog1_dir
2 C:\Oracle\product\archivelog2_dir
3 C:\Oracle\product\archivelog3_dir
9
10 USE_DB_RECOVERY_FILE_DEST n/a VALID Local
Quesion:
3.1) Is the (format of ) the above entry :"C:\Oracle\product\archivelogx_dir" --Correct? Note: archivelogx_dir is the sub-directory name, not the file name.
3.2) It looks like the Quota for each destination is (512B) (byte?). If so, generally, how many such (512 Byte) do I need? I mean on average. And why does it restrict to 512 Byte for each destination?
3.3) Assume I'll use up ALL the 10 (lines) of destinations above, if I understand it correctly, the total and maximum of the archivelog file is 10 x 512 Bytes -- Is this correct?
3.4) What should I do about Line #10 above, which carries the entries of:
USE_DB_RECOVERY_FILE_DEST under Archive Log Destination
n/a under Quota
VALID under Status
Local under Type
--I mean, should I replaced with a C:\Oracle\product\archivelogx_dir? or delete it? or else? What is this Line's default entry for?
4) If arvhice log file ARC%S_%R.%T is specified, will this same file be spread into multiple destination (directories)?
Thanks to help.
Scott

Similar Messages

Setting Archivelog mode

In order to use RMAN y need to alter my database into archivelog mode. I found some info abuot how to do that, however, I am not sure about the procedure.
These are the commands I have to write for make the modification:
shutdown immediate;
starup mount;
alter database archivelog;
alter database open;
But it looks very simple and I don´t think I'm in the correct way. There is a parameter that confuse me because the oracle page's examples don't show anythig about it:
USE_DB_RECOVERY_FILE_DEST
Can anybody helpme??

Hi,
You need to set the archive destination in the pfile/spfile before placing the database to archivelog mode.
In your database pfile/spfile:
db_recovery_file_dest_size=2G #space size can be specified according to your requirement
db_recovery_file_dest='<destination where you want to store the archives>'Once done, mount the database using the modified spfile/pfile and place the database in archive mode. Finally open the database.
If you do not want to use FRA (flash recovery area) and just want to place the database in archive mode, then in your pfile/spfile, add:
log_archive_dest='<location where you want to store the archives>'Once done, mount the database using the modified spfile/pfile and place the database in archive mode. Finally open the database.
If you feel that your questions have been answered, then please consider closing the threads by marking it as answered and providing appropriate points.

Set Archivelog Mode in OEM

How can I turn on/off the Archivelog Mode for a database by using the OEM, (say, I launched the OEM at http://My_Machine:1158/oem, after I log on where I go next)?
Thanks to help.
Scott

Thanks for the response.
Now I am on the Recovery Settings page:
1) Under Media Recovery, I checked ARCHIVELOG Mode*
2) For the Log Archive Filename Format*, it says: ARC%S_%R.%T, what should I replace with? --Could you give an example?
3)Under Number Archive Log Destination Quota (512B) Status Type, thre are 10 lines, i.e.: so I filled with
1 C:\Oracle\product\archivelog1
2 C:\Oracle\product\archivelog2
3 C:\Oracle\product\archivelog3
9
10 USE_DB_RECOVERY_FILE_DEST n/a VALID Local
Quesion:
3.1) Is the (format of ) the above entry :"C:\Oracle\product\archivelog1" --Correct?
3.2) It looks like the Quota for each destination is (512B) (byte?). If so, generally, how many such (512 Byte) do I need? I mean on average. And why does it restrict to 512 Byte for each destination?
3.3) If use up ALL the 10 (lines) of destinations above, if I understand it correctly, the total and maximum of the archivelog file is 10 x 512 Bytes -- Is this correct?
3.4) What should I do about Line #10 above, which carries:
USE_DB_RECOVERY_FILE_DEST under Archive Log Destination
n/a under Quota
[b]VALID under Status
Local under Type
Thanks to help.
Scott
Message was edited by:
scottjhn

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

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

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

Archivelog mode in oracle 9i

what are the process to keep archivelog mode in oracle 9i
senthil

alter system set log_archive_dest='path....' scope=spfile;From TFM:For Enterprise Edition users, this parameter has been deprecated in favor
of the LOG_ARCHIVE_DEST_n parameters. If Oracle Enterprise Edition is not installed or
it is installed, but you have not specified any LOG_ARCHIVE_DEST_n parameters, this
parameter is valid.Yoann.

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.

Archivelog Mode / init.ora file

Hi,
Maybe someone can help me out. I am presently trying to set up a dev server that has 3 or 4 databases on it. The first database is installed by the Oracle installation kit. The 2nd one that I am now trying to configure is giving me the following error: Ora-01126: database must be mounted EXCLUSIVE and not open for this operation. I am also setting it up for archiving.
When I do a SELECT * from V$database; the answer comes back that it is in noarchivelog mode. I even edited the init.ora file in both the pfile folder and the ora81/database folder and yet the answer is still the same. I even rebooted it with the same results. I understand that the database is in exclusive mode by default. Does this have anything to do with Parrelizm (spelling). I tried altering the database to archivelog mode but with no results.
Any ideas? Im at a loss.
Thanks for your time.
Al

Hi Al,
try to startup the db with startup mount or startup read only and try
the alter command again.
Normally it should work then!
Tobias

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.

Switched Database to ARCHIVELOG Mode, Then it Hung

Hi everyone,
This db is 9.2 on Windows.
**After switching my database to Archivelog mode and reopening, it hung forever.**
(I had to use Shutdown abort to bring it down - these steps worked to get it back online:
shutdown abort; --startup mount;
alter system archive log all;
alter database noarchivelog;
alter database open;)
The Alert.log shows "Cannot allocate new log" immediately after I switched to Archivelog mode. So it hung at that point. Had I known why it hung, maybe running 'Alter system archive log all' would have fixed everything. But I've never had to run that when I've switched other databases to Archivelog mode.
Does this indicate another problem with this database? I'm leery of it now and feel lucky that I was able to get it up again.
Thanks, John
entries from Alert.log when I switched to Archivelog mode:
ALTER DATABASE MOUNT
Wed Aug 06 11:44:19 2008
Successful mount of redo thread 1, with mount id 1689013583
Wed Aug 06 11:44:19 2008
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Wed Aug 06 11:44:45 2008
alter database archivelog
Wed Aug 06 11:44:45 2008
Starting control autobackup
Control autobackup written to DISK device
handle 'F:\ORACLE\ORA92\DATABASE\C-1602026732-20080806-00'
Completed: alter database archivelog
Wed Aug 06 11:45:17 2008
alter database open
Wed Aug 06 11:45:17 2008
Thread 1 opened at log sequence 9014
Current log# 1 seq# 9014 mem# 0: F:\ORACLE\ORADATA\PBSMEM\REDO01.LOG
Successful open of redo thread 1
Wed Aug 06 11:45:17 2008
SMON: enabling cache recovery
Wed Aug 06 11:45:17 2008
Undo Segment 1 Onlined
Undo Segment 2 Onlined
Undo Segment 3 Onlined
Undo Segment 4 Onlined
Undo Segment 5 Onlined
Undo Segment 6 Onlined
Undo Segment 7 Onlined
Undo Segment 8 Onlined
Undo Segment 9 Onlined
Undo Segment 10 Onlined
Successfully onlined Undo Tablespace 1.
Wed Aug 06 11:45:17 2008
SMON: enabling tx recovery
Wed Aug 06 11:45:17 2008
Database Characterset is WE8MSWIN1252
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: alter database open
Wed Aug 06 11:59:58 2008
Thread 1 advanced to log sequence 9015
Current log# 2 seq# 9015 mem# 0: F:\ORACLE\ORADATA\PBSMEM\REDO02.LOG
Wed Aug 06 12:01:03 2008
Thread 1 advanced to log sequence 9016
Current log# 3 seq# 9016 mem# 0: F:\ORACLE\ORADATA\PBSMEM\REDO03.LOG
Wed Aug 06 12:09:16 2008
Thread 1 cannot allocate new log, sequence 9017
All online logs needed archiving
Current log# 3 seq# 9016 mem# 0: F:\ORACLE\ORADATA\PBSMEM\REDO03.LOG
**** PrefBid App locked up at this point – hung – users cannot do anything -- Note the gap in log entry time – no further entries until my Shutdown request

Hi,
We can enable automatic archiving after instance startup.
In order to enable automatic archiving without shutting down the current instance, use the SQL command ALTER SYSTEM with the ARCHIVE LOG START parameter.
ALTER SYSTEM ARCHIVE LOG START;
When using this option, the instance does not have to be shut down to enable automatic archiving.
However, if an instance is shutdown and restarted after automatic archiving is enabled using this option, the instance is reinitialized using the settings of the parameter file ("LOG_ARCHIVE_START"), which may or may not enable automatic archiving.
NOTE: On 9i, you can use an SPFILE instead of the standard pfile. The LOG_ARCHIVE_START parmaeter is deprecated with 10g.
alter system set log_archive_start=true scope=spfile;
Did you read the Metalink Note I gave you? These information was there...
Thanks,
Marcello M.

Would you use scripts to take database out of archivelog mode?

Background: we do not use RMAN for this production database and we do cold backups each night.
I've been asked to take one of our databases out of archivelog mode for a few days and then to put it back into archivelog mode.
Being somewhat neurotic about these things - I've only ever done it manually - so that I can make sure nothing goes wrong and to check that there was a last successful cold backup prior to the switch.
However, management have asked that it be done automatically by scripts after the backup.
Whilst I can create a script that will do this - the question I'd like to ask the forum is - have you and would you?

I do not agree with taking any Oracle database out of archivelog mode and I do not approve of management's decision and have told them why and all the risks they run.
This is not a test database - it IS a production database and other users do make changes daily.
What I did not reveal until now is that I have also been asked to take this database out of archivelog mode for 5 days and suspend all cold back-ups for the whole server (with 3 other instances on the server - also impacted) - and have warned them accordingly.
However, management have been swayed by someone who feels they know better - who claims to be a qualified Oracle DBA - I'm OCP but seems to have little sway since this person has convinced management that my 6 years experience and qualification is less than his application experience in GIS.
They want to run an upload which will take around 5 days to do - I'm somewhat miffed that an upload can take that length of time and question whether a GIS system should need such an upload for such a length of time.
Let's no go into the problem with tablespaces and space within the tablespaces - the upload will fail because they do not understand that if the tablespace fills up - the upload will fail - but despite asking - I've been told that there is no problem - there will be a problem - since I refuse to allow autoextend on this database - because of the potential to run out of disk space.
I've explained until I'm blue in the face - never mind that even if the upload is successful - the cold backup tape won't be able to backup the data because it'll be potentially over the limit.
I've even warned of my past experience x 3 - when a RAID controller failed - literally died in front of my eyes - I just happened to be standing next to one of the servers talking to someone - and the whole server was lost - but because we had the archivelogs - and the previous day's backup - we got it up and running after Dell replaced the RAID controller - within 1 hour.
That's the joy of Oracle - nothing is lost other than the last archivelog - depending on the time you set the switch.
I love this system - it's so recoverable - it such a joy to work with.
But then when I get told to suspend cold backups and then at the same time suspend archivelog mode - I go mad.
Don't get me started - I've gone down the usual path of why hire an OCP when you won't listen to what I say, etc.
Management are demanding I switch it automatically out of archivelog mode etc.
I can do it - but my question is still - have you guys?
And why did you do it?
All I can say is that I hope that the server has a RAID contoller failure and finally they listen to me - the chances of that are minimal - so management are saying - do it or else.
Oh and by the way - the GIS team have asked for this to be bi-monthly - automated.
And have said that:
"You can not rollback or recover the loading process using the log files because it involves a far more complex operation that would most likely not be successful."
Nice phrase that to an OCP.
I welcome your comments - as I really am in a hole here.
Thanks.

No archivelog mode backups

I am curious if anyone knows of any software out there that can backup a database that is in no archivelog mode while it is running?
I don't want to do this....but I am curious to see if there is any that I have not heard of for a writeup I am doing.
Regards
Tim Boles

Hello,
I've never heard about it.
RMAN which is (on my point of view) the best tool to Backup Oracle database needs to set the database
in mount state for Cold Backup.
Else, about mirror or "business copy", they cannot manage dirty blocks in the buffer. They just manage
the files on the disk but, while a database is open the datafiles have no reason to be consistent.
We make clone with Business Copy (HP) for our Backup and we need to have the database in archivelog mode
and the Tablespaces in Backup mode.
Best regards,
Jean-Valentin

Comming out from archivelog mode

Hi,
I have a database which is in archive log mode. How can I come back to non archive log mode ?
Many thanks.

Setting log_archive_start = true in init.ora file enables automatic archiving of redo log files.
You will disable automatic archiving if you say.
SQL> ALTER SYSTEM ARCHIVE LOG STOP;
Now you have to archive the redo log manually. If the database is in archivelog mode and automatic archiving is disabled and if log switch happens then LGWR cannot overwrite the redo log file which is not yet archived. I experimented on my test machine and database operation hang up as follows.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL> alter system switch logfile;
System altered.
SQL> /
hanged here.
If you say the following then database will not be in archivelog mode. LGWR will overwrite the redolog files and will not wait for archiving as the database is in noarchivelog mode.
SQL> startup mount
SQL> alter database noarchivelog;
Now it depends upon your requirement. Do you want to stop the current archivelog mode temporarily or permanent ?
aijaz

Set Archivelog Mode

Similar Messages

Maybe you are looking for