What if "ALTER DATABASE OPEN" WORKS WHEN DB IS INCONSISTENT???

Hello Everyone,
I heard from couple of friends that in the case of recovery , oracle database opens despite the fact that some of the data files are inconsistent.
Is this really true? If it is, then i think its a bug with specific Oracle patch or release.
Is there anyone who has experienced a similar situation in the past? Please share.
Thanks.
sapguy

Appreciate your response. I ran into a situation where we are not sure of what time choose to choose recovery (point in time) and ended up recovering file by file and its been 100 files .. .none of those files helped with "Media recovery complete" message . This is database refresh from production backup.
Then when i am trying to issue ALTER DATABASE OPEN RESETLOGS  one of main guy says do not issue OPEN command as it may corrupt the database.
I came across one of friend who ran into similar situation and he was able open the database , but LATER database started issuing ora 600 due to corrupted files or whatever which never happened.   Forgive me .. if my text is confusing.
Thanks.

Similar Messages

  • 'alter database open resetlogs' didn't reset one of the datafiles

    I've spent the last three and a half weeks recovering an oracle database (11g 64-bit linux) because of a corrupt block in an online redo log (which I thought was being written to multiple locations). I restored the files, moving some of them around in the process; recovered to the latest possible point; moved files back to their proper location; ran 'alter database open resetlogs'; and one of the datafiles (from a bigfile tablespace) didn't get reset. I checked afterward, and it was marked offline. I do not remember placing the file offline, and cannot find such a statement in my last 300 sqlplus commands, which includes commands well before I renamed this file and the commands surrounding the rename.
    Restoring/recovering the database again will take too long, and is a remarkably poor option. Even if the database had opened correctly, the affected tablespace would not have been touched in the two or three minutes the database was open. Is there any way to force oracle to reset the logs again or otherwise fix this one file to mark it with the same date? Only allowing the resetlogs option after an incomplete recovery seems a poor restriction, especially, if files can slip through like this. I'm suspecting there is someway to just fix the checkpoint values for the tablespace, but I don't know where to begin. This particular file is <5% of the database, so if I have to do some sort of backup/restore with just it, that is probably doable.

    0: 11.1.0.6.0 on SUSE Linux Enterprise Server 10 SP2
    1: rman
    backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_datafiles_%p' (database);
    backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_archivelogs_%p' archivelog all delete input;
    backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_control_%p' current controlfile spfile;
    2:
    restore database; --not sure what datafiles were restored with this
    restore datafile X; --several files were restored individually
    recover database until scn 1137554504; -- I verified that all datafiles were on the same checkpoint after this finished. Not having placed any files offline, I didn't bother checking that.
    3:
    SQL> alter database open resetlogs;
    Database altered.
    Elapsed: 00:04:20.34
    SQL> quit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    4: Nothing in the tablespace has been touched since I ran 'alter database open resetlogs;'. It also appears that oracle placed the file offline (without me telling it to do so) and left it that way through the resetlogs, leaving the tablespace unusable during the time it was opened. The only things that would be out of date are the 'RESETLOGS_CHANGE#', the 'CHECKPOINT_CHANGE#', and associated values. It's still at the last scn before the resetlogs, and the system has been in archivelog mode the entire time. This is all information that Oracle could be tracking, and from a program logic standpoint there is no reason why Oracle cannot tie together the changes before the resetlogs, the resetlogs command and the changes after the resetlogs into a new, continuous string of changes. I assume there is some such feature in a high-caliber program because I'm actually a programmer (who would have included such advanced tracking features), and I've become a DBA out of necessity. I admit to not knowing all of the oracle DBA commands, hence me posting here before doing the work of submitting a request to metalink.
    5: I consider it a poor restriction because it doesn't always reset the logs on all files, and as far as my knowledge goes it has rendered my 3.5 week recovery process WORTHLESS. I suppose it could cause numerous errors, especially if the database wasn't cleanly shut down, but having the ability to do something equivalent to datafiles that oracle skipped the process on seems quite useful in my situation. I guess the more fundamental problem to complain about is that it would apply such changes to only some of the files, while leaving others unusable, instead of just giving me an error that some files weren't going to be reset, but I think I'm done venting my Oracle frustrations for now.
    Am I stuck with a tablespace that I cannot bring online with the database open, or is there some sort of 'alter database datafile' command (or anything else) that I know nothing of that will fix the straggling file?
    Edited by: jbo5112 on Oct 5, 2009 3:33 PM -- obfuscated some file names to secure identity.

  • Alter database open resetlogs

    Hi,
    when I try to duplicate my database by RMAN I have :
    RMAN-06053: unable to perform media recovery because of missing log
    RMAN-06025: no backup of log thread 1 seq 1452 scn 252730 found to restore
    I connect to duplicate database in sqlplus , it is not open.
    Than I do :
    alter database open resetlogs;
    And the database would be open.
    Is it bad ? Will we lose the data ? If yes what solution do you propose ?
    Effectively I do not know how to use this informations :
    log thread 1 seq 1452 scn 252730 found to restore
    Please help me to use this informations if helplfull.
    Many thanks.

    From Oracle Error documentation:
    RMAN-06025: no backup of log thread number seq number lowscn string found to restore
    Cause: An archive log restore restore could not proceed because no backup of the indicated archived log was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user"s restore operands.
    Action: None - this is an informational message. See message 6026 for further details.
    RMAN-06026: some targets not found - aborting restore
    Cause: Some of the files specified for restore could not be found. Message 6023, 6024, or 6025 is also issued to indicate which files could not be found. Some common reasons why a file can not be restored are that there is no backup or copy of the file that is known to recovery manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or some datafile copies have been made but not cataloged.
    Action: The Recovery Manager LIST command can be used to display the backups and copies that Recovery Manager knows about. Select the files to be restored from that list.
    It seems you do not have some of the files required for recover operation. Could you post how this database is backed up using RMAN?

  • Cannot alter database open

    I go the error message when I open databse.
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01190: controlfile or data file 1 is from before the last RESETLOGS
    ORA-01110: data file 1: '/u01/oracle/uatdata/system01.dbf'
    Then I issue the following command:
    SQL> recover datafile 1;
    ORA-00283: recovery session canceled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    what went wrong?
    FAN

    Here are the following information:
    RMAN> list backup of controlfile
    2> ;
    using target database controlfile instead of recovery catalog
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    402 Full 6M DISK 00:00:00 08-OCT-08
    BP Key: 402 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081008-00
    Controlfile Included: Ckp SCN: 2023488262 Ckp time: 08-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    412 Full 6M DISK 00:00:01 09-OCT-08
    BP Key: 412 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081009-00
    Controlfile Included: Ckp SCN: 2024136961 Ckp time: 09-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    422 Full 6M DISK 00:00:00 11-OCT-08
    BP Key: 422 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081011-00
    Controlfile Included: Ckp SCN: 2025471910 Ckp time: 11-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    425 Full 6M DISK 00:00:01 11-OCT-08
    BP Key: 425 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081011-01
    Controlfile Included: Ckp SCN: 2025471911 Ckp time: 11-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    435 Full 6M DISK 00:00:00 12-OCT-08
    BP Key: 435 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081012-00
    Controlfile Included: Ckp SCN: 2026183392 Ckp time: 12-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    436 Full 6M DISK 00:00:00 12-OCT-08
    BP Key: 436 Status: AVAILABLE Tag: TAG20081012T111913
    Piece Name: /u02/db/backup/RMAN/backup_UAT_667912753_460_1_ecjsv2hh_1_1.bck
    Controlfile Included: Ckp SCN: 2026183392 Ckp time: 12-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    438 Full 6M DISK 00:00:00 12-OCT-08
    BP Key: 438 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081012-01
    Controlfile Included: Ckp SCN: 2026183393 Ckp time: 12-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    448 Full 6M DISK 00:00:00 12-OCT-08
    BP Key: 448 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081012-02
    Controlfile Included: Ckp SCN: 2026451642 Ckp time: 12-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    449 Full 6M DISK 00:00:00 12-OCT-08
    BP Key: 449 Status: AVAILABLE Tag: TAG20081012T202618
    Piece Name: /u02/db/backup/RMAN/backup_UAT_667945578_473_1_epjt02ja_1_1.bck
    Controlfile Included: Ckp SCN: 2026451642 Ckp time: 12-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    451 Full 6M DISK 00:00:01 12-OCT-08
    BP Key: 451 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081012-03
    Controlfile Included: Ckp SCN: 2026451643 Ckp time: 12-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    461 Full 6M DISK 00:00:04 13-OCT-08
    BP Key: 461 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081013-00
    Controlfile Included: Ckp SCN: 2026889745 Ckp time: 13-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    464 Full 6M DISK 00:00:00 13-OCT-08
    BP Key: 464 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081013-01
    Controlfile Included: Ckp SCN: 2026889749 Ckp time: 13-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    474 Full 6M DISK 00:00:00 14-OCT-08
    BP Key: 474 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081014-00
    Controlfile Included: Ckp SCN: 2027589079 Ckp time: 14-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    477 Full 6M DISK 00:00:01 14-OCT-08
    BP Key: 477 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081014-01
    Controlfile Included: Ckp SCN: 2027589080 Ckp time: 14-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    487 Full 6M DISK 00:00:01 15-OCT-08
    BP Key: 487 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081015-00
    Controlfile Included: Ckp SCN: 2028248959 Ckp time: 15-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    488 Full 6M DISK 00:00:00 15-OCT-08
    BP Key: 488 Status: AVAILABLE Tag: TAG20081015T111406
    Piece Name: /u02/db/backup/RMAN/backup_UAT_668171647_512_1_g0jt6vbv_1_1.bck
    Controlfile Included: Ckp SCN: 2028248959 Ckp time: 15-OCT-08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    490 Full 6M DISK 00:00:00 15-OCT-08
    BP Key: 490 Status: AVAILABLE Tag:
    Piece Name: /u02/oracle/uat/uatdb/9.2.0/dbs/c-1357907388-20081015-01
    Controlfile Included: Ckp SCN: 2028248960 Ckp time: 15-OCT-08
    FAN

  • Alter database open resetlog?

    Hi all,
    I am trying the Database cloning(new database name) in my development environment(Oracle 11g r1 Windows 2003 Server). While Creating a new controlfile we need pass command like this "CREATE CONTROLFILE REUSE SET DATABASE "ORCL2" RESETLOGS FORCE LOGGING NOARCHIVELOG"
    1.i just wants to know why we need to use resetlogs, when i pass this command what is internally happening in the oracle?
    2.when the new database name is updated in all datafile during controlfile creation or while opening the database?
    3.Alter database open resetlogs what is internally happening in the oracle when i pass this command?
    Please advice me
    Thanks & Regards,
    Shan

    this will help
    http://web.njit.edu/info/limpid/DOC/backup.102/b14191/osrecov009.htm

  • Startup command starts database but alter database open read only gives error

    Hi,
    I'm having some strange behavior. I've 10.2.0.3 database on windows 2003.
    The startup command starts database without any issues.
    But if I try following it gives error.
    startup mount (successful no errors)
    alter database open read only; gives error that file Mnnnnnn is missing.
    Why this is happening and how to fix it?
    Thanks.

    You really need to show us exactly what Oracle is telling you, using copy and paste, so we can have some clue.  You can hide details like instance and host names if they show up.
    I'm wondering if you had some messed up offline datafile in a tablespace, where Oracle handles it with startup, but gets upset when you try to open read-only.  It's some bizarro sequence of events like: add a datafile to a tablespace, decide that was a mistake, alter it offline, then remove it from the OS without telling Oracle any more about it.  I've come back from vacation to find scenarios like this, it winds up being a time-bomb trying to recreate a standby later.  Or something like that, I could be unremembering some details.

  • ORA1589 signalled during alter database open...

    Hello
    Im running database Oracle9i Enterprise Edition Release 9.0.1.1.1 on windows XP
    Im getting this error when i open. the database is in no archive mode. Please see the following extract from the alert log extract
    PMON started with pid=2
    DBW0 started with pid=3
    LGWR started with pid=4
    CKPT started with pid=5
    SMON started with pid=6
    RECO started with pid=7
    Sat Feb 05 10:08:06 2011
    starting up 1 shared server(s) ...
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    Sat Feb 05 10:08:29 2011
    alter database mount exclusive
    Sat Feb 05 10:08:53 2011
    Successful mount of redo thread 1, with mount id 2728236189.
    Sat Feb 05 10:08:53 2011
    Database mounted in Exclusive Mode.
    Completed: alter database mount exclusive
    Sat Feb 05 10:08:54 2011
    alter database open
    Sat Feb 05 10:09:08 2011
    ORA-1589 signalled during: alter database open...
    Thanks for your kind help
    Edited by: user1115482 on Feb 5, 2011 1:03 AM

    Go through your alert.log for the last few messages relating to Log Sequence#1572. It may well still be an Online Redo Log.
    However, you started this thread without explaining what actions had been performed before the startup attempt that returned ORA-1589. That wasn't very professional of you.
    A doctor doesn't go ask other doctors for assistance with "my patient's heart is failing, what do I do" without saying "I had attempted open heart surgery and, during the course of surgery, found that his heart beat was irregular, however, I had already cut open his chest ... now what do I do ?"
    We do not know if
    a. You had restored a control file
    b. You had attempted a RESTORE and/or RECOVER database
    c. There had been an instance failure / server crash / corruption / error relating to a control file
    d. Some error had occurred before the STARTUP attempt that you posted
    e. Any other messages were posted to the alert.log
    Hemant K Chitale
    Edited by: Hemant K Chitale on Feb 5, 2011 10:31 PM

  • Oracle hands for 12 min during "alter database open"

    Dear all,
    After a disk failure/replacement in a SAN disk array that we are using for storage, we had to restore our Oracle database. After the restore the database does not start properly: It takes around 12 min to move from the state "Mount" to the state "Open". It finally opens but even after this, when I start SAP, only 5 workprocesses connect and logging into SAP is not possible, the gui just hangs
    There are no errors in the alert_RSP.log. I attach an extract here to show the time difference between the mount state and the open state
    Thu Apr 19 11:16:07 2007
    Starting ORACLE instance (normal)
    Thu Apr 19 11:16:29 2007
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    SCN scheme 3
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 9.2.0.7.0.
    System parameters with non-default values:
      processes                = 240
      sessions                 = 288
      timed_statistics         = TRUE
      event                    = 38068 trace name context forever, level 100
      shared_pool_size         = 620756992
      sga_max_size             = 1159695232
      shared_pool_reserved_size= 20401094
      java_pool_size           = 167772160
      enqueue_resources        = 8000
      filesystemio_options     = SETALL
      control_files            = /oracle/RSP/sapdata1/cntrl/cntrlRSP.dbf, /oracle/RSP/origlogA/cntrl/cntrlRSP.dbf, /oracle/RSP/sa
    parch/cntrl/cntrlRSP.dbf
      db_block_checksum        = FALSE
      db_block_size            = 8192
      compatible               = 9.2.0
      log_archive_start        = TRUE
      log_archive_dest         = /oracle/RSP/saparch/RSParch
      log_buffer               = 1048576
      log_checkpoint_interval  = 0
      log_checkpoint_timeout   = 0
      db_files                 = 254
      db_file_multiblock_read_count= 8
      log_checkpoints_to_alert = TRUE
      control_file_record_keep_time= 30
      dml_locks                = 5000
      replication_dependency_tracking= FALSE
      transaction_auditing     = FALSE
      undo_management          = AUTO
    undo_tablespace          = PSAPUNDO
      undo_suppress_errors     = TRUE
      undo_retention           = 43200
      remote_os_authent        = TRUE
      db_domain                = WORLD
      session_cached_cursors   = 800
      hash_join_enabled        = FALSE
      background_dump_dest     = /oracle/RSP/saptrace/background
      user_dump_dest           = /oracle/RSP/saptrace/usertrace
      max_dump_file_size       = 20000
      core_dump_dest           = /oracle/RSP/saptrace/background
      optimizer_features_enable= 9.2.0
      sort_area_size           = 2097152
      sort_area_retained_size  = 0
      db_name                  = RSP
      open_cursors             = 800
      optimizer_mode           = choose
      sortelimination_cost_ratio= 10
      btree_bitmap_plans     = FALSE
      pushjoin_predicate     = FALSE
      optimizerjoin_sel_sanity_check= TRUE
      optimizer_index_cost_adj = 10
      optimpeek_user_binds   = FALSE
      optimizeror_expansion  = DEPTH
    PMON started with pid=2
    DBW0 started with pid=3
    DBW1 started with pid=4
    DBW2 started with pid=5
    DBW3 started with pid=6
    LGWR started with pid=7
    CKPT started with pid=8
    SMON started with pid=9
    RECO started with pid=10
    Thu Apr 19 11:16:31 2007
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=11
    ARC0: Archival started
    ARC1 started with pid=12
    ARC1: Archival started
    Thu Apr 19 11:16:31 2007
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Thu Apr 19 11:16:31 2007
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no FAL' ARCHARC0: Thread not mounted
    Thu Apr 19 11:16:31 2007
    ARC1: Becoming the heartbeat ARCH
    ARC1: Becoming the heartbeat ARCHARC1: Thread not mounted
    Thu Apr 19 11:16:31 2007
    ALTER DATABASE   MOUNT
    Thu Apr 19 11:16:36 2007
    Successful mount of redo thread 1, with mount id 1209727119
    Thu Apr 19 11:16:36 2007
    Database mounted in Exclusive Mode.
    Completed: ALTER DATABASE   MOUNT
    Thu Apr 19 11:16:36 2007
    ALTER DATABASE OPEN
    Thu Apr 19 11:16:37 2007
    LGWR: Primary database is in CLUSTER CONSISTENT mode
    Thread 1 opened at log sequence 6727
      Current log# 12 seq# 6727 mem# 0: /oracle/RSP/origlogB/log_g12m1.dbf
      Current log# 12 seq# 6727 mem# 1: /oracle/RSP/mirrlogB/log_g12m2.dbf
    Successful open of redo thread 1
    Thu Apr 19 11:16:37 2007
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Thu Apr 19 11:16:38 2007
    SMON: enabling cache recovery
    Thu Apr 19 11:16:49 2007
    Successfully onlined Undo Tablespace 27.
    Thu Apr 19 11:16:49 2007
    SMON: enabling tx recovery
    Thu Apr 19 11:16:50 2007
    Database Characterset is WE8DEC
    Thu Apr 19 11:29:09 2007
    Completed: ALTER DATABASE OPEN
    Please note the time difference between 11:16:50 and 11:29:09, when the database is mounted and we are just waiting for it to open
    I run dbverify, all ok
    I reviewed note 521264 and my issue is described in case 2c. However, after reviewing all 127 datafiles and online redologs, I do not have any files with an "S" in their permissions
    We run Solaris 10, Oracle 9.2.0.7 and WAS 6.40 SP16
    Any help will be very much appreciated
    Many thanks
    Andreas

    Hello,
    Here are the details:
    R3trans -d returns 0000 instantly. I am not including trans.log here as the connection to the database works . I have no space issues neither, have around 70GB left under /oracle
    The startup log is as follows
    Trace of system startup/check of SAP System RSP on Fri Apr 20 08:38:10 BST 2007
    Called command: /usr/sap/RSP/SYS/exe/run/startsap
    Starting SAP Instance DVEBMGS00
    SAP-R/3-Startup Program Rel 640 V1.8 (2003/04/24)
    Starting at 2007/04/20 08:38:10
    Startup Profile: "/usr/sap/RSP/SYS/profile/START_DVEBMGS00_rspda002"
    Execute Pre-Startup Commands
    (6285) Local: /usr/sap/RSP/SYS/exe/run/sapmscsa -n pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
    /usr/sap/RSP/SYS/exe/run/sapmscsa: SCSA is attached and useable.
    /usr/sap/RSP/SYS/exe/run/sapmscsa: finished.
    (6285) Local: rm -f ms.sapRSP_DVEBMGS00
    (6285) Local: ln -s -f /usr/sap/RSP/SYS/exe/run/msg_server ms.sapRSP_DVEBMGS00
    (6285) Local: rm -f dw.sapRSP_DVEBMGS00
    (6285) Local: ln -s -f /usr/sap/RSP/SYS/exe/run/disp+work dw.sapRSP_DVEBMGS00
    (6285) Local: rm -f co.sapRSP_DVEBMGS00
    (6285) Local: ln -s -f /usr/sap/RSP/SYS/exe/run/rslgcoll co.sapRSP_DVEBMGS00
    (6285) Local: rm -f se.sapRSP_DVEBMGS00
    (6285) Local: ln -s -f /usr/sap/RSP/SYS/exe/run/rslgsend se.sapRSP_DVEBMGS00
    Starting Programs
    (6304) Starting: local ms.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
    (6305) Starting: local dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
    (6306) Starting: local co.sapRSP_DVEBMGS00 -F pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
    (6307) Starting: local se.sapRSP_DVEBMGS00 -F pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
    (6285) Waiting for Child Processes to terminate.
    Instance on host rspda002 started
    ps -ef | grep dw is shown below: It only starts 5 -6 dialog processes. All the other processes are not started (normally I have around 40 )
    rspda002:rspadm 33% ps -ef | grep dw
      rspadm  6317  6305   0 08:38:17 ?           0:00 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6310  6305   0 08:38:16 ?           0:01 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6311  6305   0 08:38:16 ?           0:00 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6624  5523   0 08:43:35 pts/1       0:00 grep dw
      rspadm  6305  6285   0 08:38:11 ?           0:04 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6312  6305   0 08:38:17 ?           0:01 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6313  6305   0 08:38:17 ?           0:00 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
    That is ps -ef | grep sap
    rspda002:rspadm 32% ps -ef | grep sap
      rspadm  6317  6305   0 08:38:17 ?           0:00 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6310  6305   0 08:38:16 ?           0:01 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
        root 12375   650   0 11:15:58 ?           3:56 /usr/sap/RSP/SYS/exe/run/saposcol
      rspadm  6311  6305   0 08:38:16 ?           0:00 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6309  6305   0 08:38:16 ?           0:01 icman -attach pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6306  6285   0 08:38:11 ?           0:00 co.sapRSP_DVEBMGS00 -F pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6307  6285   0 08:38:11 ?           0:00 se.sapRSP_DVEBMGS00 -F pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6304  6285   0 08:38:11 ?           0:00 ms.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6308  6305   0 08:38:16 ?           0:02 gwrd -dp pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6622  5523   0 08:43:29 pts/1       0:00 grep sap
      rspadm  6305  6285   0 08:38:11 ?           0:04 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm 20243   650   0 15:11:34 ?          13:11 sapccm4x -DCCMS pf==/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6285   650   0 08:38:11 ?           0:00 /usr/sap/RSP/SYS/exe/run/sapstart pf=/usr/sap/RSP/SYS/profile/START_DVEBMGS00_r
      rspadm  6312  6305   0 08:38:17 ?           0:01 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
      rspadm  6313  6305   0 08:38:17 ?           0:00 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
    Many thanks
    Andreas

  • Orale 9i alter database open ( noarchivelog )

    Hi all,
    Not sure what was trhe issue as after I tried to put my database in noarchivelog mode it game me a ORA- device busy and logged me out of the session ?!!
    Steps:
    Shutdown first
    then
    - startup mount
    - alter database noarchivelog
    - alter database open
    ORA-xxx device busy , acquire with NOWAIT option .....
    Any ideas what i missed ?
    Thx

    Afaik, there is really no need to adjust the log_archive_start and/or log_archive_dest parameters when changing the archivelog mode. The sequence mentioned by the OP (shutdown; startup mount; alter database noarchivelog; alter database open;) is sufficient.

  • ORA-1092 signalled during: alter database open...

    When trying to startup the db runnint into following error:
    SMON: enabling cache recovery
    Sat May 16 10:35:12 2009
    Successfully onlined Undo Tablespace 1.
    Sat May 16 10:35:12 2009
    SMON: enabling tx recovery
    Sat May 16 10:35:12 2009
    Database Characterset is UTF8
    Sat May 16 10:35:13 2009
    Errors in file d:\oracle\visdb\9.2.0\admin\vis_apps\udump\vis_ora_2200.trc:
    ORA-00600: internal error code, arguments: [4193], [2391], [2395], [], [], [], [], []
    Doing block recovery for fno: 10 blk: 159
    Sat May 16 10:35:17 2009
    Recovery of Online Redo Log: Thread 1 Group 2 Seq 3 Reading mem 0
    Mem# 0 errs 0: D:\ORACLE\VISDATA\LOG2.DBF
    Doing block recovery for fno: 10 blk: 153
    Sat May 16 10:35:18 2009
    Recovery of Online Redo Log: Thread 1 Group 2 Seq 3 Reading mem 0
    Mem# 0 errs 0: D:\ORACLE\VISDATA\LOG2.DBF
    Sat May 16 10:35:18 2009
    Errors in file d:\oracle\visdb\9.2.0\admin\vis_apps\udump\vis_ora_2200.trc:
    ORA-00607: Internal error occurred while making a change to a data block
    ORA-00600: internal error code, arguments: [4193], [2391], [2395], [], [], [], [], []
    Error 607 happened during db open, shutting down database
    USER: terminating instance due to error 607
    Sat May 16 10:35:19 2009
    Errors in file d:\oracle\visdb\9.2.0\admin\vis_apps\bdump\vis_pmon_2288.trc:
    ORA-00607: Internal error occurred while making a change to a data block
    Instance terminated by USER, pid = 2200
    ORA-1092 signalled during: alter database open...
    Pl. advice to recover from this suitation. New to recovery/bkup.
    Thanks,
    Sashi.

    00607, 00000, "Internal error occurred while making a change to a data block"
    // *Cause:  An internal error or memory exception occurred while Oracle was
    // applying redo to a data block.
    // *Action: call Oracle Support                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Alter database open

    Hi,
    I try to start a database with the commands
    startup mount
    alter database noarchivelog
    everything is ok up to now
    When I give the command
    alter database open
    I obtain
    ERROR at line 1
    ORA-01092 Oracle instance terminated Disconnection forced.
    Why?
    Thank you,
    Mihaela

    I post the last 120 lines of alert_log:
    Mon Jul 24 12:57:31 2006
    alter database noarchivelog
    Mon Jul 24 12:57:31 2006
    Completed: alter database noarchivelog
    Mon Jul 24 12:57:44 2006
    alter database open
    Mon Jul 24 12:57:47 2006
    Thread 1 opened at log sequence 1281
    Current log# 3 seq# 1281 mem# 0: /web/oradata/simmer/redo03_A.log
    Current log# 3 seq# 1281 mem# 1: /web/oradata/simmer/redo03_B.log
    Successful open of redo thread 1
    Mon Jul 24 12:57:47 2006
    SMON: enabling cache recovery
    Mon Jul 24 12:57:50 2006
    Successfully onlined Undo Tablespace 1.
    Mon Jul 24 12:57:50 2006
    SMON: enabling tx recovery
    Mon Jul 24 12:57:50 2006
    Errors in file /web/bin/oracle/9206/admin/simmer/udump/simmer_ora_1636.trc:
    ORA-12701: CREATE DATABASE character set is not known
    Mon Jul 24 12:57:50 2006
    Error 12701 happened during db open, shutting down database
    USER: terminating instance due to error 12701
    Instance terminated by USER, pid = 1636
    ORA-1092 signalled during: alter database open
    Tue Jul 25 09:52:36 2006
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    SCN scheme 3
    Using log_archive_dest parameter default value
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 9.2.0.6.0.
    System parameters with non-default values:
    processes = 300
    timed_statistics = TRUE
    shared_pool_size = 117440512
    large_pool_size = 16777216
    java_pool_size = 117440512
    control_files = /web/oradata/simmer/control01.ctl, /web/arhive/ctl/control02.ctl, /web/bin/oracle/9206/ctl/control03.ctl
    db_block_size = 8192
    db_cache_size = 33554432
    compatible = 9.2.0.0.0
    db_file_multiblock_read_count= 16
    fast_start_mttr_target = 300
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    undo_retention = 10800
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    instance_name = SIMMER
    job_queue_processes = 10
    hash_join_enabled = TRUE
    background_dump_dest = /web/bin/oracle/9206/admin/simmer/bdump
    user_dump_dest = /web/bin/oracle/9206/admin/simmer/udump
    core_dump_dest = /web/bin/oracle/9206/admin/simmer/cdump
    sort_area_size = 1048576
    db_name = SIMMER
    open_cursors = 300
    optimizer_mode = rule
    star_transformation_enabled= FALSE
    query_rewrite_enabled = FALSE
    pga_aggregate_target = 25165824
    aq_tm_processes = 1
    PMON started with pid=2
    DBW0 started with pid=3
    LGWR started with pid=4
    CKPT started with pid=5
    SMON started with pid=6
    RECO started with pid=7
    CJQ0 started with pid=8
    QMN0 started with pid=9
    Tue Jul 25 09:52:44 2006
    ALTER DATABASE MOUNT
    Tue Jul 25 09:52:49 2006
    Successful mount of redo thread 1, with mount id 535276268
    Tue Jul 25 09:52:49 2006
    Database mounted in Exclusive Mode.
    Completed: ALTER DATABASE MOUNT
    Tue Jul 25 09:52:50 2006
    ALTER DATABASE OPEN
    Tue Jul 25 09:52:51 2006
    Beginning crash recovery of 1 threads
    Tue Jul 25 09:52:52 2006
    Started redo scan
    Tue Jul 25 09:52:53 2006
    Completed redo scan
    21 redo blocks read, 5 data blocks need recovery
    Tue Jul 25 09:52:53 2006
    Started recovery at
    Thread 1: logseq 1281, block 1240, scn 0.28883578
    Tue Jul 25 09:52:53 2006
    Recovery of Online Redo Log: Thread 1 Group 3 Seq 1281 Reading mem 0
    Mem# 0 errs 0: /web/oradata/simmer/redo03_A.log
    Mem# 1 errs 0: /web/oradata/simmer/redo03_B.log
    Tue Jul 25 09:52:53 2006
    Completed redo application
    Tue Jul 25 09:52:53 2006
    Ended recovery at
    Thread 1: logseq 1281, block 1261, scn 0.28903619
    5 data blocks read, 5 data blocks written, 21 redo blocks read
    Crash recovery completed successfully
    Tue Jul 25 09:52:54 2006
    Thread 1 advanced to log sequence 1282
    Thread 1 opened at log sequence 1282
    Current log# 1 seq# 1282 mem# 0: /web/oradata/simmer/redo01_A.log
    Current log# 1 seq# 1282 mem# 1: /web/oradata/simmer/redo01_B.log
    Successful open of redo thread 1
    Tue Jul 25 09:52:56 2006
    SMON: enabling cache recovery
    Tue Jul 25 09:52:59 2006
    Successfully onlined Undo Tablespace 1.
    Tue Jul 25 09:52:59 2006
    SMON: enabling tx recovery
    Tue Jul 25 09:52:59 2006
    Database Characterset is US7ASCII
    replication_dependency_tracking turned off (no async multimaster replication found)
    Completed: ALTER DATABASE OPEN
    openes.hq.fdeb.ro>
    Thank you,
    Mihaela

  • Alter Database Open Mystery

    We have a script that issued the Startup command this morning. In the .trc logs we are able to see that the Startup command got as far as the Alter Database Mount command. So we know this command completed successfully. But the next command we expect to see is the Alter Database Open command. This was mysteriously absent from the .trc file.
    We lack a full time DBA on our project so we are wondering if there is a logical explanation for this failure? Are there any places we can look to see why the Alter Database Open command was never issued and didn't appear in the .trc log?
    Any suggestions or probably causes would be greatly appreciated.

    DB version 9.2.0.6.0 on Solaris 8
    Just noticed that our /UNDO file system is a 99% and that our UNDO tablespace is using 'auto extend' option. Could this be a potential cause?
    /dev/vx/dsk/rootdg/undo
    11796416 10490922 125853 99% /undo
    The alert log just stopped and didn't show anything regarding the Alter Database Open command. Then it jumps to this morning when one of our guys started the database manually. You can see this where May 3rd entries stop:
    ALTER DATABASE MOUNT
    Thu May 3 23:18:24 2007
    Successful mount of redo thread 1, with mount id 1534972155
    Thu May 3 23:18:24 2007
    Database mounted in Exclusive Mode.
    Completed: ALTER DATABASE MOUNT
    Fri May 4 07:10:07 2007
    Starting ORACLE instance (normal)
    Fri May 4 07:12:57 2007
    Shutting down instance: further logons disabled
    Shutting down instance (immediate)
    License high water mark = 3
    Fri May 4 07:12:57 2007
    ALTER DATABASE CLOSE NORMAL
    ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
    Fri May 4 07:12:57 2007
    ALTER DATABASE DISMOUNT
    Completed: ALTER DATABASE DISMOUNT
    ARCH: Archiving is disabled
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    ARCH: Archiving is disabled
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Fri May 4 07:13:07 2007
    Starting ORACLE instance (normal)
    Disable cache advisory with old cache parameters
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    SCN scheme 3
    Using log_archive_dest parameter default value
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 9.2.0.6.0.
    System parameters with non-default values:
    processes = 200
    timed_statistics = TRUE
    shared_pool_size = 150994944
    java_pool_size = 50331648
    nls_date_format = DD-MON-RR
    control_files = /oracle_data/oradata1/FC/control01.ctl, /oracle_dat
    a/oradata2/FC/control02.ctl, /oracle_data/oradata3/FC/control03.ctl
    db_block_buffers = 22000
    db_block_size = 2048
    db_writer_processes = 2
    dbhandles_cached = 0
    compatible = 9.0.0.0.0
    log_buffer = 524288
    log_checkpoint_interval = 10000
    db_files = 38
    db_file_multiblock_read_count= 32
    dml_locks = 1500
    undo_management = AUTO
    undo_tablespace = undotbs_01
    max_enabled_roles = 100
    remote_login_passwordfile= EXCLUSIVE
    db_domain = .WORLD
    service_names = FC
    utl_file_dir = /apps/oracle9i/admin/FC/script
    job_queue_processes = 1
    systemtrig_enabled = TRUE
    background_dump_dest = /apps/oracle9i/admin/FC/bdump
    user_dump_dest = /apps/oracle9i/admin/FC/udump
    max_dump_file_size = 10240
    core_dump_dest = /apps/oracle9i/admin/FC/cdump
    audit_trail = DB
    sort_area_size = 1500000
    db_name = FC
    open_cursors = 200
    optimizer_mode = choose
    PMON started with pid=2
    DBW0 started with pid=3
    DBW1 started with pid=4
    LGWR started with pid=5
    CKPT started with pid=6
    SMON started with pid=7
    RECO started with pid=8
    CJQ0 started with pid=9
    Fri May 4 07:13:09 2007
    ALTER DATABASE MOUNT
    Fri May 4 07:13:14 2007
    Successful mount of redo thread 1, with mount id 1534971461
    Fri May 4 07:13:14 2007
    Database mounted in Exclusive Mode.
    Completed: ALTER DATABASE MOUNT
    Fri May 4 07:13:14 2007
    ALTER DATABASE OPEN
    Fri May 4 07:13:15 2007
    Thread 1 opened at log sequence 272984
    Current log# 4 seq# 272984 mem# 0: /rollback_logs/FC/redo04.log
    Successful open of redo thread 1
    Fri May 4 07:13:15 2007
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Fri May 4 07:13:15 2007
    SMON: enabling cache recovery
    Fri May 4 07:13:17 2007
    Successfully onlined Undo Tablespace 17.
    Fri May 4 07:13:17 2007
    SMON: enabling tx recovery
    Fri May 4 07:13:17 2007
    Database Characterset is US7ASCII
    replication_dependency_tracking turned off (no async multimaster replication fou
    nd)
    Completed: ALTER DATABASE OPEN
    Fri May 4 07:15:05 2007
    Thread 1 advanced to log sequence 272985
    Current log# 5 seq# 272985 mem# 0: /rollback_logs/FC/redoFC05.log
    Fri May 4 07:15:28 2007
    Thread 1 advanced to log sequence 272986
    Current log# 6 seq# 272986 mem# 0: /rollback_logs/FC/redoFC06.log
    Fri May 4 07:15:53 2007
    Thread 1 advanced to log sequence 272987
    Current log# 7 seq# 272987 mem# 0: /rollback_logs/FC/redoFC07.log
    Fri May 4 07:16:18 2007
    Thread 1 advanced to log sequence 272988
    Current log# 8 seq# 272988 mem# 0: /rollback_logs/FC/redoFC08.log
    Fri May 4 07:20:20 2007
    Thread 1 advanced to log sequence 272989
    Current log# 9 seq# 272989 mem# 0: /rollback_logs/FC/redoFC09.log
    Fri May 4 07:20:45 2007
    Thread 1 advanced to log sequence 272990
    Current log# 10 seq# 272990 mem# 0: /rollback_logs/FC/redoFC10.log
    Fri May 4 07:21:09 2007
    Thread 1 advanced to log sequence 272991
    Current log# 11 seq# 272991 mem# 0: /rollback_logs/FC/redoFC11.log
    Fri May 4 07:25:21 2007
    Thread 1 advanced to log sequence 272992
    Current log# 2 seq# 272992 mem# 0: /rollback_logs/FC/redo02.log
    Fri May 4 07:25:45 2007
    more

  • Alter database open resetlogs upgrade ;         throwing error

    Recently i have cloned a database from 11.2.0.2 to 11.2.0.3 on a new server.... I got the error as fowwos,
    contents of Memory Script:
    Alter clone database open resetlogs;
    executing Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    RMAN-10041: Could not re-create polling channel context following failure.
    RMAN-10024: error setting up for rpc polling
    RMAN-10005: error opening cursor
    RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
    RMAN-03002: failure of Duplicate Db command at 07/12/2012 16:19:24
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-00704: bootstrap process failure
    ORA-39700: database must be opened with UPGRADE option
    Process ID: 29247
    Session ID: 200 Serial number: 5
    So i have tried
    SQL> alter database open resetlogs upgrade;
    alter database open resetlogs upgrade
    ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    SQL> alter database open upgrade;
    alter database open upgrade
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '+DATA_CMX/cmx/datafile/system.270.788451975'
    Any help ?

    Hi,
    Duplicate is not supported using different version of database, so I recommend you don't use duplicate.
    Because RMAN "duplicate" attempts to automatically rename (rename required recover) and open the database you may not use RMAN duplicate for this case, only RMAN restore.
    Perform this work using normal restore database.
    See this example.
    On prod database with db_name/db_unique_name dbupg:
    Recovery Manager: Release 11.2.0.2.0 - Production on Fri Jul 13 15:15:59 2012
    RMAN> backup database plus archivelog delete input;
    Starting backup at 13-JUL-12
    current log archived
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=52 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=17 RECID=1 STAMP=788540852
    input archived log thread=1 sequence=18 RECID=2 STAMP=788541371
    channel ORA_DISK_1: starting piece 1 at 13-JUL-12
    channel ORA_DISK_1: finished piece 1 at 13-JUL-12
    piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_annnn_TAG20120713T151612_800shf7w_.bkp tag=TAG20120713T151612 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_17_800rz40y_.arc RECID=1 STAMP=788540852
    archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_18_800shcsd_.arc RECID=2 STAMP=788541371
    Finished backup at 13-JUL-12
    Starting backup at 13-JUL-12
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=+DS8000_DG/dbupg/datafile/system.271.788537119
    input datafile file number=00002 name=+DS8000_DG/dbupg/datafile/sysaux.272.788537167
    input datafile file number=00003 name=+DS8000_DG/dbupg/datafile/undotbs1.273.788537199
    input datafile file number=00004 name=+DS8000_DG/dbupg/datafile/users.275.788537229
    channel ORA_DISK_1: starting piece 1 at 13-JUL-12
    channel ORA_DISK_1: finished piece 1 at 13-JUL-12
    piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp tag=TAG20120713T151614 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:35
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 13-JUL-12
    channel ORA_DISK_1: finished piece 1 at 13-JUL-12
    piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncsnf_TAG20120713T151614_800sjm29_.bkp tag=TAG20120713T151614 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 13-JUL-12
    Starting backup at 13-JUL-12
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=19 RECID=3 STAMP=788541412
    channel ORA_DISK_1: starting piece 1 at 13-JUL-12
    channel ORA_DISK_1: finished piece 1 at 13-JUL-12
    piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_annnn_TAG20120713T151652_800sjnf7_.bkp tag=TAG20120713T151652 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_19_800sjn5q_.arc RECID=3 STAMP=788541412
    Finished backup at 13-JUL-12
    RMAN> backup current controlfile;
    Starting backup at 13-JUL-12
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    channel ORA_DISK_1: starting piece 1 at 13-JUL-12
    channel ORA_DISK_1: finished piece 1 at 13-JUL-12
    piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncnnf_TAG20120713T153435_800tkwl2_.bkp tag=TAG20120713T153435 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 13-JUL-12I used same server to do this work... I really dont recommend that, if yes you must be aware about location of restore... you should use new server:
    Create a spfile:
    *.control_files='+DS8000_DG/dbclone/controlfile/Current.277.788541913'
    *.db_name='dbupg'
    *.db_unique_name='dbclone'
    *.audit_file_dest='/u01/app/oracle/admin/dbclone/adump'
    *.audit_trail='db'
    *.compatible='11.2.0.0.0'
    *.db_block_size=8192
    *.db_create_file_dest='+MMC'
    *.db_domain=''
    *.db_recovery_file_dest_size=107374182400
    *.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area01'
    *.diagnostic_dest='/u01/app/oracle'
    *.log_file_name_convert='+DS8000_DG','+MMC'
    *.memory_target=1031798784
    *.open_cursors=300Make backup available on new server:
    and:
    SQL*Plus: Release 11.2.0.3.0 Production on Fri Jul 13 15:33:24 2012
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
    Connected to an idle instance.
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area 1027182592 bytes
    Fixed Size                  2227936 bytes
    Variable Size             599785760 bytes
    Database Buffers          419430400 bytes
    Redo Buffers                5738496 bytes
    SQL> show parameter db_n
    NAME                                 TYPE        VALUE
    db_name                              string      dbupg
    SQL> show parameter db_un
    NAME                                 TYPE        VALUE
    db_unique_name                       string      dbclone
    RMAN> restore controlfile from '/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncnnf_TAG20120713T153435_800tkwl2_.bkp';
    Starting restore at 13-JUL-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=290 device type=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
    output file name=+DS8000_DG/dbclone/controlfile/current.277.788541913
    Finished restore at 13-JUL-12
    RMAN> startup mount
    database is already started
    database mounted
    released channel: ORA_DISK_1
    RMAN> run {
    2> SET NEWNAME FOR DATABASE TO '+MMC';
    3> restore database  ;
    4> }
    executing command: SET NEWNAME
    Starting restore at 13-JUL-12
    Starting implicit crosscheck backup at 13-JUL-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=290 device type=DISK
    Crosschecked 4 objects
    Finished implicit crosscheck backup at 13-JUL-12
    Starting implicit crosscheck copy at 13-JUL-12
    using channel ORA_DISK_1
    Crosschecked 2 objects
    Finished implicit crosscheck copy at 13-JUL-12
    searching for all files in the recovery area
    cataloging files...
    no files cataloged
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to +MMC
    channel ORA_DISK_1: restoring datafile 00002 to +MMC
    channel ORA_DISK_1: restoring datafile 00003 to +MMC
    channel ORA_DISK_1: restoring datafile 00004 to +MMC
    channel ORA_DISK_1: reading from backup piece /u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp
    channel ORA_DISK_1: piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp tag=TAG20120713T151614
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:46
    Finished restore at 13-JUL-12
    RMAN> recover database;
    Starting recover at 13-JUL-12
    using channel ORA_DISK_1
    starting media recovery
    media recovery complete, elapsed time: 00:00:01
    Finished recover at 13-JUL-12So, just startup with upgrade option.
    SQL*Plus: Release 11.2.0.3.0 Production on Fri Jul 13 15:39:31 2012
    SQL>  alter database open resetlogs upgrade; Now you can upgrade your database.
    After upgrade database you can change the database name using NID:
    $ nid
    DBNEWID: Release 11.2.0.3.0 - Production on Fri Jul 13 15:50:23 2012
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    Keyword     Description                    (Default)
    TARGET      Username/Password              (NONE)
    DBNAME      New database name              (NONE)
    LOGFILE     Output Log                     (NONE)
    REVERT      Revert failed change           NO
    SETNAME     Set a new database name only   NO
    APPEND      Append to output log           NO
    HELP        Displays these messages        NOHTH,
    Levi Pereira
    Edited by: Levi Pereira on Jul 13, 2012 4:04 PM

  • ORA-16196 on Alter Database open.

    Hi
    Why when we close a database with ALTER DATABASE CLOSE
    it's impossible to open immediately after with ALTER DATABASE OPEN?
    How to do this without dismount the database ?
    Regards
    Den

    Seems illogical but thats the way it has been defined by Oracle.
    The instance can mount/dismount a database any number of times but it can open or close the database only once.
    The only reason I can think of is this is the way it is required in RAC. Any instance can open a database but it can do it only once. May be in order to preserve the integrity of the database structures.

  • How to alter database open using srvctl command

    Hi all,
    I mounted my instances by using:
    [oracle@rac1 ~]$ srvctl start database -d RAC -o mount
    How can i open the instances by using srvctl from mounted status?
    Thank you!
    Dân.

    Hi,
    srvctl start database <dbname> -open will not issue an "alter database open", hence it will not work on a mounted instance, as you have seen. So this is expected.
    In case crs did only start the database in mount mode, you either have to use sqlplus or shutdown the db beforehand:
    srvctl stop database -d <dbname> -o immediate
    srvctl start database -d <dbname> -o openFor the future change the behavior, how crs will start the database with srvctl modify database.
    Regards
    Sebastian

Maybe you are looking for