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]$                                                                                 

Similar Messages

  • 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 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 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

  • 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.

  • 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.

  • 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.

  • 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.

  • 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

  • RAC database in archivelog mode ?

    Hi all,
    may anyone provide me doc id in matalink to move a non archived RAC database in
    to archive log mode.
    THanx in advance.
    Deep

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

  • How to setup oracle database to archivelog mode and auto delete ?

    Oracle 11g R2
    - How to setup database to archive log mode and have oracle only save 24 hours of archive logs
    and delete the rest. So at any given time I will have only 24 hours of archive log and not more.
    So only 1 day of archive logs.
    - Let me know the database parameters I need to setup to accomplish this.
    - I don't want to use the RMAN
    - I am not setting up the database to archive log mode for recovery purpose. I am setting up archive log mode
    so we can use the log miner tool to dig up achives to see log activity for any performance & tuning.
    Edited by: johnpau2013 on May 9, 2012 6:09 PM

    johnpau2013 wrote:
    Thanks everyone for there responses.
    I need to rephrase and explain everyone as what I wanted to do exactly. This might help everyone understand and suggest me.
    We have oracle database 11g r2. Its a test database. Nothing is critical. We use EXPDP utility to backup the entire database every night. Which is enough for us to recover incase something happens. Even if we loose some data. That's fine.
    We are testing our web application on this oracle test database for performance & tuning.
    One thing we have noticed is that the redo logs are switching very frequently. 50MB each log file and there are 5 logs. each log switches every 40 seconds. So we wanted to see what is getting written in this redo logs. We wanted to use the LOG MINER tool in OEM to read the logs. It needed our database to be setup in archive log mode. So the log miner can read the archive logs and show us the sql's within the archive logs.
    Now when we setup the archive log mode on our database. By default the archive logs destination was set to flash recovery area ( may be oracle default archive log location is flash recovery area folder).
    We have setup the db_recovery_file_dest_size to 100GB. Now within 2 days we have filled up the flash recovery area folder. Database was frozen. Then we realized that its because oracle couldn't write archive logs. Because it reached the 100GB. Then we physically deleted files in the flash recovery area folder. Thinking it would help us start the frozen oracle database. But it didn't . The we realized that we are doing something wrong. As Oracle does not know that at OS level we deleted the files. Then temporarily we changed the db_recovery_file_dest_size to 130GB and were able to start the oracle database. Later we turned OFF the archive log mode.
    Being a rookie DBA we would have not read something properly.
    Finally:
    We wanted to know how to always keep only 1 day of archive logs (only for our performance tuning ) and not more than that. All we need this 1 day of archive logs is to use the log miner to read them. Backup is NOT our priority here. Only be able to read the archive logs from LOG MINER is PRIORITY.
    Correct me if I am wrong.Okay, so its making much more sense now, thanks for explaining your requirement.
    Database won't honor anything that you would do over the o/s without telling it. Your deletion of the archive log from the o/s location is NOT updated in the control file of the database and that's why, even when you had deleted the entire 100GB , from the db perspective, the space was still marked as used. This is the same which would happen even if you would increase the space from 100gb to whatever size as well. To delete the space, you would need to update the database's control file and that you can do from RMAN using its two commands , crosscheck backup following with deleted expired backup . The first command would find that which database backup files are NOT on the o/s which are shown in the control file and would mark all of them as expired. The second command would simply delete those expired files. This would update the control file and you would have your 100gb or whatever space, given back to you.
    To keep the archive logs of just one day, set up that Retention Policy for RMAN to either number of copies using the Redundancy option(default and set to 1) or Recovery Window. I believe for you Redundancy would be a suitable choice but you can have a read and play around with it. Setting it up would mark the files as Obsoleted and finally, you can write a small RMAN script to delete those obsoleted files.
    Now, what I don't understand is that why you want to keep on generating the archive logs just for the log miner? If you would have generated them once and figure out the reason for extensive redo generation(did you try increasing the redo log file size, 50mb seems to be smallish) , I don't think that there is any reason to keep on generating the archive logs still .
    And last part, for your question asked about that whether we can use RMAN to put the db in the archive log and is it a backup tool, yes and yes.
    HTH
    Aman....

  • Cannot bring liveCache database into "warm" mode

    Hello,
    We recently added disk capacity to our liveCache server and when we were adding data volumes one of the devices that was assigned to a log volume was also assigned to a new data volume.
    When we stopped the database and re-started it, we started getting the following errors:
    2006-02-21 10:25:05   364 ERR 11000 page0io_ Illegal file format
    2006-02-21 10:25:05   364 ERR 11000 page0io_ blocksize wanted: 8192, blocksize found: 0
    2006-02-21 10:25:05   148 ERR 11000 vattach  dev0_vattach returned FALSE
    2006-02-21 10:25:05   148 ERR    13 IOMan    Attach error on Log volume 1: Could not open volume
    2006-02-21 10:37:59   148 ERR    27 IOMan    DevNo from Log volume in configuration and info page are different: 2 vs 31
    2006-02-21 10:54:50   148 ERR    27 IOMan    DevNo from Log volume in configuration and info page are different: 2 vs 31
    2006-02-21 11:08:54   148 ERR    27 IOMan    DevNo from Log volume in configuration and info page are different: 2 vs 31
    2006-02-21 11:08:54   148 ERR 51080 SYSERROR -9209 Message not available
    2006-02-21 11:20:44   148 ERR    27 IOMan    DevNo from Log volume in configuration and info page are different: 2 vs 31
    2006-02-21 11:20:44   148 ERR 51080 SYSERROR -9209 Message not available
    2006-02-21 11:22:36   148 ERR    27 IOMan    DevNo from Log volume in configuration and info page are different: 2 vs 31
    2006-02-21 11:22:36   148 ERR 51080 SYSERROR -9209 Message not available
    It appears that we've either corrupted or destroyed one of our log volumes so the database will not start. Our recovery method of choice would be to re-initailize our database and restore from a good backup, but recently found out our backups are no good.
    We've also tried to clear the logs using the 'util_execute clear log' command, but that is not working either:
    dbmcli on LCT>util_execute clear log
    ERR
    -24988,ERR_SQL: sql error
    -902,Message not available
    Does anyone have any ideas on how we might be able to fix the issue and save our database?
    Thanks.
    Matthew

    HI,
    Im facing up the same problem, by restoring a Livecache from 2 differents servers.
    10-04-15 09:49:41   603     11597 IO       Open '/DISK/backup_log/bck_data' su
    ccessfull, fd: 59
    2010-04-15 09:49:41   603 ERR 11000 page0io_ Illegal file format
    2010-04-15 09:49:41   603 ERR 11000 page0io_ blocksize wanted: 65536, blocksize
    found: 131072
    2010-04-15 09:49:41   603 ERR 11000 d0_aopen max_block_cnt changed to 16
    Did you manage to solve the pb?
    Thanks
    John

  • Setting Archivelog mode

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

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

  • 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

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

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

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

Maybe you are looking for

  • How to write a SQL query in SAP B1 2007 B with input parameters?

    How to write a SQL query in SAP B1 2007 B with input parameters, on execution of which will ask for some input value from the user and the values will be selected from a list such as item list?

  • Changing data in events in Table Maintenance generator

    Hi, My requirement is to default two fields while changing a row.. I tried using event 01, 02 and 03... I used the below code.. ZYREN-userid = sy-uname. zyren-lupdate = 0. Please help me in solving this.. Thanks

  • Update should not happen in the name of WF-BATCH

    Hi All, I have a requirement to change the WF-BATCH to the other user id. The task completion or update should not happen in the name of WF-BATCH, instead it should happen with the name of the other user id. Please can anybody suggest on this.. Thank

  • Possible error in SDK docs for xmlDomInstance

    API Reference/modules/LrXml.html#xmlDomInstance:transform discusses normalizing the result you get back, and provides a snippet of string manipulation to do so: "... apply a substitution pattern such as this: string.gsub( result, "[\r\n      ]+", " "

  • CS4 & OpenGL on OSX 10.5.5

    I have read the Tech note:GPU and OpenGL Features and Limitations in Photoshop CS4, but do not see the issues I encountered on my set-up. I have had to switch off OpenGL because I was regularly getting the following issues: Using marquee tool in norm