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.

Similar Messages

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

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

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.

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

Archive log mode in oracle 10g on windows environment

Hi All,
I have a production database (Oracle 10g 10.2.0.1.0) on windows 2003 server. yesterday i put the database into archivelog mode. when i query for spfile location it is shown in ORACLE_HOME\dbs location.
but when i created pfile using the spfile it is created at ORACLE_HOME\database location. and there is another spfile also. i set the log_archive_dest at a location other than flash_recovery_area in pfile, but it is showing the DB_RECOVER_AREA.
today i seen archives are creating in both locations.
can a database have two spfiles. and working on them ?
can i remove a spfile in /dbs location.
pls. give me suggestion to rectify this
thanks and regards.

Salman Qureshi wrote:
Hi,
On windows platform, spfile and initfiles are by default created under ORACLE_HOME\database directory and this is also the default location, so, your spfile or initfile in this directory are actually in use.
i set the log_archive_dest at a location other than flash_recovery_area in pfile, but it is showing the DB_RECOVER_AREA. You need to unset the "db_recovery_file_dest" parameter first.
alter system set db_recovery_file_dest='';Now set your log_archive_dest as follows
alter system set log_archive_dest_1="location=your_location";Don't user older "log_archive_dest" parameter
SalmanYour assertion that "You need to unset the "db_recovery_file_dest" parameter first." is patently false.
DB_RECOVERY_FILE_DEST is used for more than just archivelogs. Setting LOG_ARCHIVE_DEST_n to a location other than USE_DB_RECOVERY_FILE_DEST even while DB_RECOVERY_FILE_DEST is set is perfectly acceptable. In fact it is required if you want to continue to use the FRA for things other than archivelogs. Things, like - oh, say - backups!
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2011.02.15 07:42:18 =~=~=~=~=~=~=~=~=~=~=~=
login as: oracle
oracle@vmlnx01's password:
Last login: Tue Feb 15 07:01:51 2011 from 192.168.160.1
[oracle@vmlnx01 ~]$ sqlplus / as sysdbaFirst, note the date and time of logon, to compare to archivelog timestamps later ...
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Feb 15 07:42:27 2011
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing optionsNext, note the values for the log_archive_dest_n parameters. Actually, the value for #10 is the default if no log_arch_dest_n parms are set, but I like to set it explicitly to avoid ambiguity.
SQL> show parameter log_archive_dest_
NAME     TYPE VALUE
log_archive_dest_1     string
log_archive_dest_10     string LOCATION=USE_DB_RECOVERY_FILE_
DEST
log_archive_dest_2     string
log_archive_dest_3     string
log_archive_dest_4     string
log_archive_dest_5     string
log_archive_dest_6     string
log_archive_dest_7     string
log_archive_dest_8     string
log_archive_dest_9     string
NAME     TYPE VALUE
log_archive_dest_state_1     string enable
log_archive_dest_state_10     string enable
log_archive_dest_state_2     string enable
log_archive_dest_state_3     string enable
log_archive_dest_state_4     string enable
log_archive_dest_state_5     string enable
log_archive_dest_state_6     string enable
log_archive_dest_state_7     string enable
log_archive_dest_state_8     string enable
log_archive_dest_state_9     string enableAnd note the setting for db_recovery_file_dest ...
SQL> show parameter db_recovery_file_dest
NAME     TYPE VALUE
db_recovery_file_dest     string /orafra
db_recovery_file_dest_size     big integer 4GNow lets check what's in the recovery dest. Notice there is no directory timestamped today (15 Feb), so no archivelogs have been generated for today.
SQL> !ls -l /orafra/VLNXORA1/archivelog
total 28
drwxr-x--- 2 oracle oinstall 4096 Feb 11 17:53 2011_02_08
drwxr-x--- 2 oracle oinstall 4096 Feb 11 17:53 2011_02_09
drwxr-x--- 2 oracle oinstall 4096 Feb 11 17:53 2011_02_10
drwxr-x--- 2 oracle oinstall 4096 Feb 11 17:53 2011_02_11
drwxr-x--- 2 oracle oinstall 4096 Feb 12 06:00 2011_02_12
drwxr-x--- 2 oracle oinstall 4096 Feb 13 11:00 2011_02_13
drwxr-x--- 2 oracle oinstall 4096 Feb 14 22:00 2011_02_14So lets force a log switch and check the results
SQL> alter system switch logfile;
System altered.
SQL> !ls -l /orafra/VLNXORA1/archivelog
total 32
drwxr-x--- 2 oracle oinstall 4096 Feb 11 17:53 2011_02_08
drwxr-x--- 2 oracle oinstall 4096 Feb 11 17:53 2011_02_09
drwxr-x--- 2 oracle oinstall 4096 Feb 11 17:53 2011_02_10
drwxr-x--- 2 oracle oinstall 4096 Feb 11 17:53 2011_02_11
drwxr-x--- 2 oracle oinstall 4096 Feb 12 06:00 2011_02_12
drwxr-x--- 2 oracle oinstall 4096 Feb 13 11:00 2011_02_13
drwxr-x--- 2 oracle oinstall 4096 Feb 14 22:00 2011_02_14
drwxr-x--- 2 oracle oinstall 4096 Feb 15 07:43 2011_02_15
SQL> !ls -l /orafra/VLNXORA1/archivelog/2011_02_15
total 1892
-rw-r----- 1 oracle oinstall 1931776 Feb 15 07:43 o1_mf_1_82_6oo0qomc_.arcSo we see that, as expected, the archivelog was written to the FRA. Note the log sequence # of 82
Also, let's check my "alternate" location, as yet undefinded to the db ..
SQL> !ls -l /oraarch/vlnxora1
total 0No files there.
Now we will change the archivelog destination. Note that I am NOT touching the FRA definition
SQL> alter system set log_archive_dest_1='location=/oraarch/vlnxora1' scope=both;
System altered.
SQL> alter system set log_archive_dest_10 = '' SCOPE=both;
System altered.
SQL> show parameter log_archive_dest_
NAME     TYPE VALUE
log_archive_dest_1     string location=/oraarch/vlnxora1
log_archive_dest_10     string
log_archive_dest_2     string
log_archive_dest_3     string
log_archive_dest_4     string
log_archive_dest_5     string
log_archive_dest_6     string
log_archive_dest_7     string
log_archive_dest_8     string
log_archive_dest_9     string
log_archive_dest_state_1     string enable
NAME     TYPE VALUE
log_archive_dest_state_10     string enable
log_archive_dest_state_2     string enable
log_archive_dest_state_3     string enable
log_archive_dest_state_4     string enable
log_archive_dest_state_5     string enable
log_archive_dest_state_6     string enable
log_archive_dest_state_7     string enable
log_archive_dest_state_8     string enable
log_archive_dest_state_9     string enable
SQL> show parameter db_recovery_file_dest
NAME     TYPE VALUE
db_recovery_file_dest     string /orafra
db_recovery_file_dest_size     big integer 4GSo, above we see that I do not have an archivelog destination set to the FRA, but the FRA is still set. I did not unset it, as you asserted was necessary. I still want my backups to go there.
Next we'll do another log switch and check the results.
SQL> alter system switch logfile;
System altered.First, we'll check the (now unused) FRA destination. Notice that there is still just the one archivelog, sequence 82.
SQL> !ls -l /orafra/VLNXORA1/archivelog/2011_02_15
total 1892
-rw-r----- 1 oracle oinstall 1931776 Feb 15 07:43 o1_mf_1_82_6oo0qomc_.arcNow check the new, non-fra destination. Notice that it now has an archivelog, sequence 83
SQL> !ls -l /oraarch/vlnxora1
total 96
-rw-r----- 1 oracle oinstall 92160 Feb 15 07:45 1_83_732127364.dbf
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@vmlnx01 ~]$ exit
logout

Archive log mode in oracle 10g

Hi,
I would like to know the archive log mode in oracle 10g and I use this code in SQLPlus
select log_mode from v$database
But it displayed: "2" not : NOARCHIVELOG or ARCHIVELOG
It displayed a number, not a String.
How could I know this?
Thanks

Hi Paul
Because I am a newbie in DBA Oracle so I got many difficulties.
You are very kind to help me.
So I have some more questions:
1. when I executed this code, it always reported error:
$ tmp=`${ORACLE_HOME}/bin/sqlplus -s / as sysdba << EOF
set heading off feedback off;
exit
EOF`
tmp='ERROR:
ORA-01031: insufficient privileges
SP2-0306: Invalid option.
Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
where <logon> ::= <username>[<password>][@<connect_identifier>] | /
SP2-0306: Invalid option.
Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
where <logon> ::= <username>[<password>][@<connect_identifier>] | /
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus'
so when I updated like this:
tmp=`${ORACLE_HOME}/bin/sqlplus -s sys/syspass@db02 as sysdba <<EOF
               set heading off feedback off;
               exit
               EOF`
It run correctly.
2. With Paul's guide:
Do not execute Oracle commands from root, execute them as oracle user. This works to me :
$ tmp=`${ORACLE_HOME}/bin/sqlplus -s / as sysdba << EOF
set heading off feedback off
alter database backup controlfile to '${CONTROLFILE_DIR}/<file name>';
alter database backup controlfile to trace;
exit
EOF`
Of course CONTROLFILE_DIR must be set to a directory with write permission for oracle user.
For ex: I have an Unix account: unix/unix
and a Sys Oracle account: oracle/oracle
I login with Unix acount (unix/unix) and call script file that contains above code.
tmp=`${ORACLE_HOME}/bin/sqlplus -s oracle/oracle@db02 as sysdba <<EOF
               set heading off feedback off
               alter database backup controlfile to '${CONTROLFILE_DIR}/backup_control.ctl';
               alter database backup controlfile to trace;
               exit
               EOF`
Unix report as following: Linux error: 13: Permission denied.
CONTROLFILE_DIR directory is read,write,execute for account unix/unix.
Of course CONTROLFILE_DIR must be set to a directory with write permission for oracle user. You mean I have to create a Unix user is the same to Oracle user so that Oracle user can have permission to write.
Please guilde more detail.
Thanks for your attention.
Message was edited by:
user481034

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

Put database in archivelog mode

I know how to do it.
using oracle 9.2.0.8 on AIX 5.3
My question is that can I mention a different location
my database installed in /opt/oracle/product/9.2
datafiles/control files and redolof files
in /var/data/oracle/product/9.2/orcl
I want archive to be in
/var/data/oracle/product/9.2
How can I do this
please suggest

Is this standard or enterprise edition?
On the enterprise edition you can use the log_archive_dest_N (n=1..10) instance parameter file to configure up to ten different locations. As an example, you would configure: log_archive_dest_1="location=/var/data/oracle/product/9.2 mandatory" You have to configure log_archive_format as well (unless you want the default format mask); log_archive_format=arch%S.arc and the log_archive_start parameter to true.
Shutdown normal or immediate your database. Once it is shutdown start it up to the mount state:
startup mount
and issue the alter command:
ALTER DATABASE ARCHIVELOG
open your database and you will be working on archivelog mode.
If you are on a standard edition, just proceed as previously indicated, the difference is that log_archive_dest_N parameter is not available, and you can define up to two different file locations, parameters are:
LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST
and to indicate mandatory or optional, you'll have to use the LOG_ARCHIVE_MIN_SUCCEED_DEST instance parameter.
~ Madrid

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?

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

Alter database into Archivelog mode.

HI Team,
I am using ORACLE 9i.
I want to convert database into archivelog mode from noarchivelog mode.
Using the following SQL Commands I can able to convert my database into the Archivelog.
SQL> connect sys as sysdba
Enter password: *****************
Connected.
SQL> alter database archivelog;
alter database archivelog
ERROR at line 1:
ORA-01126: database must be mounted EXCLUSIVE and not open for this operation
SQL> startup mount;
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 252779340 bytes
Fixed Size 453452 bytes
Variable Size 125829120 bytes
Database Buffers 125829120 bytes
Redo Buffers 667648 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
My problem is that I had to shutdown the database before converting it in to the archivelog mode...
Is there any way that without shuting down the database i can switch to archivelog mode.
Please comments...
Shatrughan

if we shutdown immediate one's database..do
it's listener terminated too???The database registration with the listener yes, the listener itself no. That is, if you execute a command like "lsnrctl stat" you won't see the database anymore, but the listener is still active. Example :
[ora102 ~ db102]$ lsnrctl stat
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 05-MAY-2007 18:57:51
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date                05-MAY-2007 18:27:34
Uptime                    0 days 0 hr. 30 min. 16 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /home/ora102/OraHome1/network/admin/listener.ora
Listener Log File         /home/ora102/OraHome1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "db102" has 1 instance(s).
Instance "db102", status READY, has 2 handler(s) for this service...
The command completed successfully
[ora102 ~ db102]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Sat May 5 18:58:03 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SYS@db102 SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SYS@db102 SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
[ora102 ~ db102]$ lsnrctl stat
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 05-MAY-2007 18:58:33
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date                05-MAY-2007 18:27:34
Uptime                    0 days 0 hr. 30 min. 58 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /home/ora102/OraHome1/network/admin/listener.ora
Listener Log File         /home/ora102/OraHome1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[ora102 ~ db102]$

Archivelog mode in oracle 9i

Similar Messages

Maybe you are looking for