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.

Similar Messages

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

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

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

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?

Rman backup with no archivelog mode

Hi Friend,
I did this backup many times before, to backup a test db which is not in archivelog mode.
My procedure are the following:
$ rman target /
rman> run {
shutdown immediate;
startup mount;
backup format '/u02/RMAN/%d_LVL0_%T_%u_s%s_p%p' database;
delete obsolete;
But strange I got now error:
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
Thanks a lot

Hi,
Paste the snap shot of what you actually doing and what error messages are coming. That will help to analyze the problem.
This basically happens when your shutdown is not normal or clean.
One way is to again startup the database and then issue shutdown Normal.
Regards,
Edited by: Navneet on Sep 30, 2008 3:21 AM

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

HI All,
During upgrading the database from 10g to 11g... I will put my database from noarchivelog mode to archivelog mode to save the disk space.
Does this task improves or speedsup the process of upgradation or any impact.
Suggestions please.
regards,
TEJAS

when DB is archivelog mode and you put DB in startup upgrade mode.. and execute catupgrd.sql script it starts updating dictionary objects and generates archivelogs ..
Hence i put the DB in noarchive log mode..
Any performance impact by putting the upgrade process in noarchivelog mode in terms of time duration the backup is performed.No performance impact, But recommended to put in Archivelog mode, even though if you have good backup.
Also apart from this thread, have a question, The catupgrd.sql script execution duration depends upon the data disctionary contents right not on the DB size ? i am having this question. plz answer.The upgrade script creates and alters certain data dictionary tables. It also upgrades or installs the following database components in the new Oracle Database 11g Release 2 (11.2) database:
Source:-
Answer is here in detail.. http://docs.oracle.com/cd/E11882_01/server.112/e10819/upgrade.htm#sthref184

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.

Archivelog mode Configuration

Hi
I am using Oracle10g , and OS is Windows XP. i had tried to enable it to archive mode by using the following
SQL> SELECT LOG_MODE FROM SYS.V$DATABASE;
LOG_MODE
NOARCHIVELOG
Then by adding the following lines in the Pfile
$ORACLE_HOME/admin/SID/pfile. I'll add the following lines to the end of the file:
# Archive Log Destinations -benr(10/15/04)
log_archive_dest_1='location=/u02/oradata/cuddle/archive'
log_archive_start=TRUE
startup the database in mount mode and put it in archivelog mode
SQL> startup mount
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
Database altered.
SQL> select log_mode from v$database;
LOG_MODE
ARCHIVELOG
when i log in to the db, i only can log in as sys user.when log in as sys user i got this error :
"ORA-00257: archiver error. Connect internal only,until freed."
What's the possible problem? And how to solve it?
Regards,
[email protected]

hi surya,
i think your are not using your pfile during startup, and the changes you have made to your pfile does not take effect.
the parameter log_archive_start=TRUE is no longer supported in 10g.you should get a notification of parameter deprecated during startup.
you issued the command : startup , so your pfile is not being used.
you should issue : archive log list to see your archive destination
if it is default, it should be db_recovery_file_dest
next issue show parameter db_recovery_file_dest
check the space availability of the directory by issuing df -h, df -k
you can manually removed your old archive log but after you need to perform crosscheck from rman.
best practise is to do it using rman during your scheduled backup.
br,
mrak

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

Unable to enable archivelog mode and flashback mode

Hi,
I have oracle10g installed on Linux machine.
Everytime i try to enable ARCHIVELOG mode and FLASHBACK through the DB EM console and during the restart of the database, the database just startup and gets mounted, but does not get open. and not able to get the database to archive log mode.
and when i startup the database through the sqlplus i get this following error:
ORA-32004: obsolete and/or deprecated parameter(s) specified
i am not able to enable successfully archive log mode and flashback mode.
in sqlplus i did the following and got the following:
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 13585
Current log sequence 13587
so i was thinking maybe it is the archive log start sequence that is creating error.
because long back i had the database in archive log mode and because the archive log files got filled up, i disabled the archive mode and had to delete the archive log files.
Can someone help me bring the database in archive log mode which i am not able to successfully execute.
Thanks in advance,
Philip.

Hi,
yes i looked in to the init.ora file and i got this
orcl.__db_cache_size=1308622848
orcl.__java_pool_size=167772160
orcl.__large_pool_size=16777216
orcl.__shared_pool_size=167772160
orcl.__streams_pool_size=16777216
*.audit_file_dest='/home/oracle/oracle/admin/orcl/adump'
*.background_dump_dest='/home/oracle/oracle/admin/orcl/bdump'
*.compatible='10.2.0.1.0'
*.control_files='/u01/oradata/orcl/control01.ctl','/u01/oradata/orcl/control02.ctl','/u01/oradata/orcl/control03.ctl'
*.core_dump_dest='/home/oracle/oracle/admin/orcl/cdump'
*.db_block_size=8192
*.db_domain='mslabs.noaa.gov'
*.db_file_multiblock_read_count=16
*.db_name='orcl'
*.db_recovery_file_dest='/u02/flash_recovery_area'
*.db_recovery_file_dest_size=64424509440
*.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
*.java_pool_size=159383552
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=562036736
*.processes=150
*.log_archive_start=FALSE
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=1687158784
*.shared_pool_size=157286400
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/home/oracle/oracle/admin/orcl/udump'
and there is a
*.log_archive_start=false
so do i have to delete it?
Thanks,
Philip.

Startup in Archivelog mode

Similar Messages

Maybe you are looking for