Restoring No Archivelog Mode Database

This is only for testing purposes>>>
Is there any way to get a database up and running if the database is in no archivelog mode and their is a datafile missing?
Suppose your full backup is missing that 1 datafile also, but you have a full export of the database from the same time the backup was taken. Can you restore tablespace from an export file?

Thanks, I found this information about running in NO Archivelog mode and Losing a Datafile
"ALTER TABLESPACE ...OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE ...OFFLINE is only allowed if database is in ARCHIVEREDO LOG mode. You should use the 'alter database datafile 'xx' offline drop', which just takes the datafile offline in the controlfile. This allows you to open the database and the next step should be to drop the tablespace. This will remove information on the file from the data dictionary. Since you are running in NOARCHIVELOG, your only option is to drop and recreate the tablespace. If not much activity has occurred on the database since then, you can try recovering it using the online redo log files. If they haven't been written over, this may work. Whether the datafile is offlined (archivelog mode) or offline dropped (noarchivelog mode), the definition remains in the database until the associated tablespace is dropped."
This information was very helpful as it allowed the database to open.

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

Restoring a Rman Tablespace backup to noarchilog mode database

Hi All,
Is it possible to take a backup of a tablespace through rman from archivelog mode database and restore the same to noarchivelog mode database through rman ? Please suggest if it is not possible why it is not possible.
We have a testing database from which a tablespace has been dropped. Can it be restored from the Prod database ?
Please help. The database version is 9.2.0.8..

Fabricio_Jorge wrote:
I think it's possible to backup/restore a single tablespace:
BACKUP TABLESPACE nome_tablespace [FORMAT 'path/bkp_file'];
Being able to backup a single tablespace is NOT the same as grafting that TS into a different database.
First, you are not really backing up a 'tablespace'. You are backing up files. In this case, just the files that implement the named TS, but files, nevertheless. And files belong to a database. Header info in each file defines, among other things, the dbid of the database the file belongs to. And the current scn. That will be a severe mis-match if you tried to 'restore' it to some other db.

ARCHIVELOG MODE --- Please assist

dear experts,
I have this doubt in my mind and would like you guys to advise on.
Is it true that when a database is in ARCHIVELOG MODE, database recovery using archived logs & hotbackup is possible to the last commit?
probably using the command: recover database using backup controlfile until cancel; (to apply all the arhive logs to last hotbackup)
From my point of view, i feel that the database recovery using the ARCHIVED LOGS and hotbackup is possible only up to the last redo log switch. In order to recover the database to the last commit, I have to recover the database using both the ARCHIVED LOGS as well as the last ACTIVE REDO LOG.
It is because the most recent commited transactions on the current redo log might not be written to archive log (as the active log is not full and no alter system switch logfile performed) at the point of time when the db crashed.
Please advise.
thanks all!

Also, by using RMAN you can approach more to the last commit with RMAN parameters like SCN, etc.
It's quite easy!

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

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.

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

How to use OEM grid control to find any database not in archivelog mode?

Hello,
currently we have 130 databases, say, if I want to pick out any database currently NOT in archivelog mode, is there a quick way to find out ?
by using OEM grid control
or
some trick similar,
but really don't need to check each database manually.
thank you very much!

This query works in 12c - please run as SYSMAN.
It is based on undocumented assumptions though +( AND key_value = 'NOARCHIVELOG')+.
SELECT *
FROM SYSMAN.MGMT$GROUP_DERIVED_MEMBERSHIPS O ,
    SYSMAN.MGMT$TARGET T ,
    sysman.MGMT$AVAILABILITY_CURRENT st
WHERE
o.member_target_type     IN ('oracle_database', 'rac_database')
AND ( t.target_type           ='rac_database'
OR (t.target_type             ='oracle_database'
AND t.type_qualifier3        != 'RACINST'))
AND o. member_target_guid     = t.target_guid
AND t.target_guid             = st.target_guid
AND st.availability_status    = 'Target Up'
AND ( EXISTS
    (SELECT *
    FROM sysman.mgmt$metric_current i
    WHERE I.TARGET_GUID = O.MEMBER_TARGET_GUID
    AND metric_name     = 'archFull'
    AND Metric_Column   = 'archTotal'
    AND metric_label    = 'Archive Area'
    AND column_label    = 'Total Archive Area (KB)'
    AND key_value       = 'NOARCHIVELOG'
    ));Another way to achieve the goal is to push extended metrics (SELECT LOG_MODE FROM V$DATABASE) on each DB, and monitor the values they return to the repository. This is an example for a (slightly) different problem - http://iiotzov.wordpress.com/2012/08/08/how-to-use-the-new-oem-12c-metric-extensions-to-enforce-enterprise-wide-custom-policies .
OEM Repository has many other great uses as well - http://iiotzov.files.wordpress.com/2012/05/oem-repository-a-second-look.doc , http://iiotzov.files.wordpress.com/2011/08/iotzov_oem_repository.pdf
Iordan Iotzov
http://iiotzov.wordpress.com/

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.

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 during Database upgrade

I have database that needs to be upgraded (from 8.1.7 to 10.2.0.4) and this database runs in ARCHIVELOG MODE. My question should I turn archivelog mode off during upgrade? Do you see any benefits or issues with that?

Better option to put database in no archivelog mode. Take a backup and then put database in noarchivelog mode.
Log_archive_format will be different in 10g so while enable you may need to change this parameter.

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.

Restoring No Archivelog Mode Database

Similar Messages

Maybe you are looking for