Database open in exclusive mode

Hi,
DB in 9i on Linux, when I startup it is opened in EXCLUSIVE mode. What does it mean ? How can I change it to non exclusive ?
Many thanks.

Ok,
it was it.
devlpt SQL> shutdown immediate;
ORA-01507: base de donnees non montee
Instance ORACLE arrêtée.
I deleted /soft/oracle/V9.2.0.4/dbs/lkMYDB then
devlpt SQL> startup
Instance ORACLE lancée.
Total System Global Area 692655708 bytes
Fixed Size 452188 bytes
Variable Size 620756992 bytes
Database Buffers 67108864 bytes
Redo Buffers 4337664 bytes
Base de données montée.
now since 14 hours ago, it is in :
and in alertolog we have :
Restarting dead background process QMN0
Any help.

Similar Messages

  • ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

    Hello,
    Yesterday i did a clean install of XE on my Windows 7 64bit laptop. The installation went well. Today when i tried to connect to the database i got ORA-01033 initialization or shutdown in progress.
    So i started sqlplus as sysdba and executed
    SQL> shutdown abort
    ORACLE instance shut down.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 1071333376 bytes
    Fixed Size 1388352 bytes
    Variable Size 620757184 bytes
    Database Buffers 444596224 bytes
    Redo Buffers 4591616 bytes
    Database mounted.
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    The alert log is showing the following output
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =19
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up:
    Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production.
    Using parameter settings in server-side pfile C:\ORACLE\APP\ORACLE\PRODUCT\11.2.0\SERVER\DATABASE\INITXE.ORA
    System parameters with non-default values:
    sessions = 176
    spfile = "C:\ORACLE\APP\ORACLE\PRODUCT\11.2.0\SERVER\DBS\SPFILEXE.ORA"
    memory_target = 1G
    control_files = "C:\ORACLE\APP\ORACLE\ORADATA\XE\CONTROL.DBF"
    compatible = "11.2.0.0.0"
    db_recovery_file_dest = "C:\oracle\app\oracle\fast_recovery_area"
    db_recovery_file_dest_size= 10G
    undo_management = "AUTO"
    undo_tablespace = "UNDOTBS1"
    remote_login_passwordfile= "EXCLUSIVE"
    dispatchers = "(PROTOCOL=TCP) (SERVICE=XEXDB)"
    shared_servers = 4
    job_queue_processes = 4
    audit_file_dest = "C:\ORACLE\APP\ORACLE\ADMIN\XE\ADUMP"
    db_name = "XE"
    open_cursors = 300
    diagnostic_dest = "C:\ORACLE\APP\ORACLE"
    Wed Sep 07 09:26:50 2011
    PMON started with pid=2, OS id=4936
    Wed Sep 07 09:26:50 2011
    PSP0 started with pid=3, OS id=4756
    OER 7451 in Load Indicator : Error Code = OSD-04500: illegal option specified !
    Wed Sep 07 09:26:51 2011
    VKTM started with pid=4, OS id=5772 at elevated priority
    VKTM running at (10)millisec precision with DBRM quantum (100)ms
    Wed Sep 07 09:26:51 2011
    GEN0 started with pid=5, OS id=5424
    Wed Sep 07 09:26:51 2011
    DIAG started with pid=6, OS id=5928
    Wed Sep 07 09:26:51 2011
    DBRM started with pid=7, OS id=4000
    Wed Sep 07 09:26:51 2011
    DIA0 started with pid=8, OS id=3876
    Wed Sep 07 09:26:51 2011
    MMAN started with pid=9, OS id=6004
    Wed Sep 07 09:26:51 2011
    DBW0 started with pid=10, OS id=5252
    Wed Sep 07 09:26:51 2011
    LGWR started with pid=11, OS id=848
    Wed Sep 07 09:26:51 2011
    CKPT started with pid=12, OS id=2420
    Wed Sep 07 09:26:51 2011
    SMON started with pid=13, OS id=2424
    Wed Sep 07 09:26:51 2011
    RECO started with pid=14, OS id=2396
    Wed Sep 07 09:26:51 2011
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    Wed Sep 07 09:26:51 2011
    MMON started with pid=15, OS id=2388
    starting up 4 shared server(s) ...
    ORACLE_BASE from environment = C:\oracle\app\oracle
    Wed Sep 07 09:26:51 2011
    ALTER DATABASE MOUNT
    Wed Sep 07 09:26:51 2011
    MMNL started with pid=16, OS id=1288
    Successful mount of redo thread 1, with mount id 2642331547
    Database mounted in Exclusive Mode
    Lost write protection disabled
    Completed: ALTER DATABASE MOUNT
    Wed Sep 07 09:26:56 2011
    ALTER DATABASE OPEN
    Errors in file C:\ORACLE\APP\ORACLE\diag\rdbms\xe\xe\trace\xe_ora_2212.trc:
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    ORA-1589 signalled during: ALTER DATABASE OPEN...
    Wed Sep 07 09:41:54 2011
    db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Can anybody tell me what to do to solve this problem?
    Kind Regards,
    D.

    DennisV wrote:
    Starting ORACLE instance (normal)What do you have in the alert.log above that line?
    OER 7451 in Load Indicator : Error Code = OSD-04500: illegal option specified !This is one of the symptoms reported earlier when running on unsupported platform (x64) and maybe there's some connection with your issue.
    See {thread:id=2278170}.
    Errors in file C:\ORACLE\APP\ORACLE\diag\rdbms\xe\xe\trace\xe_ora_2212.trc:What errors does trace file reveal?

  • Database Started In Restricted Mode...

    Dear Exports,
    We are using Oracle 10gR2 on Windows server 2008. My database size is approximately 2tb. Now we are going to setup Dataguard for our primary. We started the database with the changer parameters for dataguard and create spfile from pfile. And started the database with Spfile. But after some time i noticed that the database started automatically in Restricted mode. As in our database Previously dataguard was configured, due to the some problem that setup is not working and the logs are not applied in Standby server. I thought may be for this reason database going to restricted mode automatically so i set the log_archive_dest_state_2='DEFFER' and Now I scanned the whore alert.log file and found the same situation of restricted is happening from Jan 2010. Please Suggest some solution how i can over come the problem.
    The alertlog when i started the database recently...
    ALTER DATABASE CLOSE NORMAL
    ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Fri Apr 12 19:12:39 2013
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =97
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.4.0.
    System parameters with non-default values:
    processes = 800
    sessions = 885
    sga_max_size = 10737418240
    __shared_pool_size = 1325400064
    __large_pool_size = 16777216
    __java_pool_size = 16777216
    __streams_pool_size = 0
    sga_target = 8589934592
    control_files = G:\ORADATA\CONTROL01.CTL, G:\ORADATA\CONTROL02.CTL, G:\ORADATA\CONTROL03.CTL
    db_block_size = 8192
    __db_cache_size = 7214202880
    compatible = 10.2.0.3.0
    log_archive_config = DG_CONFIG=(orcl,stdby)
    log_archive_dest_1 = LOCATION=I:\archive_log VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=orcl
    log_archive_dest_2 = SERVICE=stdby NOAFFIRM ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=stdby
    log_archive_dest_state_1 = enable
    log_archive_max_processes= 30
    log_archive_format = ARC%D_%s_%R.%T
    fal_client = orcl
    fal_server = stdby
    db_file_multiblock_read_count= 16
    db_recovery_file_dest = D:\oracle\product\10.2.0\flash_recovery_area
    db_recovery_file_dest_size= 2147483648
    standby_file_management = AUTO
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    undo_retention = 5400
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
    local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=192.168.12.86)(PORT=1521))
    job_queue_processes = 10
    audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
    background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
    user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
    core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
    db_name = orcl
    open_cursors = 500
    pga_aggregate_target = 10737418240
    PMON started with pid=2, OS id=14328
    PSP0 started with pid=3, OS id=15420
    MMAN started with pid=4, OS id=9092
    DBW0 started with pid=5, OS id=12360
    DBW1 started with pid=6, OS id=18112
    LGWR started with pid=7, OS id=18360
    CKPT started with pid=8, OS id=18448
    SMON started with pid=9, OS id=17160
    RECO started with pid=10, OS id=18512
    CJQ0 started with pid=11, OS id=19324
    MMON started with pid=12, OS id=14380
    Fri Apr 12 19:12:40 2013
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=13, OS id=2996
    Fri Apr 12 19:12:40 2013
    starting up 1 shared server(s) ...
    Fri Apr 12 19:12:41 2013
    ALTER DATABASE MOUNT
    Fri Apr 12 19:12:45 2013
    Setting recovery target incarnation to 2
    Fri Apr 12 19:12:45 2013
    Successful mount of redo thread 1, with mount id 1340307369
    Fri Apr 12 19:12:45 2013
    Allocated 15937344 bytes in shared pool for flashback generation buffer
    Starting background process RVWR
    RVWR started with pid=17, OS id=5524
    Fri Apr 12 19:12:45 2013
    Database mounted in Exclusive Mode
    Completed: ALTER DATABASE MOUNT
    Fri Apr 12 19:12:46 2013
    ALTER DATABASE OPEN
    Fri Apr 12 19:12:46 2013
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=18, OS id=11964
    ARC1 started with pid=19, OS id=13472
    ARC2 started with pid=20, OS id=17960
    ARC3 started with pid=21, OS id=18548
    ARC4 started with pid=22, OS id=15660
    ARC5 started with pid=23, OS id=15548
    ARC6 started with pid=24, OS id=14720
    ARC7 started with pid=25, OS id=15780
    ARC8 started with pid=26, OS id=17992
    ARC9 started with pid=27, OS id=17988
    ARCa started with pid=28, OS id=19436
    ARCb started with pid=29, OS id=16104
    ARCc started with pid=30, OS id=6656
    ARCd started with pid=31, OS id=6900
    ARCe started with pid=32, OS id=10568
    ARCf started with pid=33, OS id=16992
    ARCg started with pid=34, OS id=14372
    ARCh started with pid=35, OS id=18084
    ARCi started with pid=36, OS id=5788
    ARCj started with pid=37, OS id=4940
    ARCk started with pid=38, OS id=18816
    ARCl started with pid=39, OS id=14588
    ARCm started with pid=40, OS id=16820
    ARCn started with pid=41, OS id=8068
    ARCo started with pid=42, OS id=18736
    ARCp started with pid=43, OS id=8316
    ARCq started with pid=44, OS id=5952
    ARCr started with pid=45, OS id=16304
    ARCs started with pid=46, OS id=14884
    Fri Apr 12 19:12:46 2013
    ARC0: Archival started
    ARCt started with pid=47, OS id=19408
    Fri Apr 12 19:12:46 2013
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    Thread 1 opened at log sequence 117446
    Current log# 10 seq# 117446 mem# 0: G:\ORADATA\REDO10A.LOG
    Current log# 10 seq# 117446 mem# 1: H:\ORADATA\REDO10B.LOG
    Fri Apr 12 19:12:46 2013
    ARC0: Becoming the 'no FAL' ARCH
    Fri Apr 12 19:12:46 2013
    ARC0: Becoming the 'no SRL' ARCH
    Fri Apr 12 19:12:46 2013
    ARC8: Becoming the heartbeat ARCH
    Fri Apr 12 19:12:47 2013
    Successful open of redo thread 1
    Fri Apr 12 19:12:47 2013
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Fri Apr 12 19:12:47 2013
    SMON: enabling cache recovery
    Fri Apr 12 19:12:48 2013
    Successfully onlined Undo Tablespace 1.
    Fri Apr 12 19:12:48 2013
    SMON: enabling tx recovery
    Fri Apr 12 19:12:48 2013
    Database Characterset is WE8MSWIN1252
    Opening with internal Resource Manager plan
    where NUMA PG = 1, CPUs = 16
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=48, OS id=10048
    Fri Apr 12 19:12:51 2013
    Completed: ALTER DATABASE OPEN
    Fri Apr 12 19:12:51 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_mmon_14380.trc:
    ORA-19815: WARNING: db_recovery_file_dest_size of 2147483648 bytes is 99.56% used, and has 9486336 remaining bytes available.
    Fri Apr 12 19:12:51 2013
    You have following choices to free up space from flash recovery area:
    1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
    then consider changing RMAN ARCHIVELOG DELETION POLICY.
    2. Back up files to tertiary device such as tape using RMAN
    BACKUP RECOVERY AREA command.
    3. Add disk space and increase db_recovery_file_dest_size parameter to
    reflect the new space.
    4. Delete unnecessary files using RMAN DELETE command. If an operating
    system command was used to delete files, then use RMAN CROSSCHECK and
    DELETE EXPIRED commands.
    Dump file d:\oracle\product\10.2.0\admin\orcl\bdump\alert_orcl.log
    Fri Apr 12 19:13:26 2013
    ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Windows NT Version V6.0 Service Pack 1
    CPU : 16 - type 8664, 16 Physical Cores
    Process Affinity : 0x0000000000000000
    Memory (Avail/Total): Ph:55999M/65533M, Ph+PgF:183151M/193356M
    Fri Apr 12 19:13:26 2013
    Starting ORACLE instance (restrict)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =97
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.4.0.
    System parameters with non-default values:
    processes = 800
    sessions = 885
    sga_max_size = 10737418240
    __shared_pool_size = 1325400064
    __large_pool_size = 16777216
    __java_pool_size = 16777216
    __streams_pool_size = 0
    sga_target = 8589934592
    control_files = G:\ORADATA\CONTROL01.CTL, G:\ORADATA\CONTROL02.CTL, G:\ORADATA\CONTROL03.CTL
    db_block_size = 8192
    __db_cache_size = 7214202880
    compatible = 10.2.0.3.0
    log_archive_config = DG_CONFIG=(orcl,stdby)
    log_archive_dest_1 = LOCATION=I:\archive_log VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=orcl
    log_archive_dest_2 = SERVICE=stdby NOAFFIRM ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=stdby
    log_archive_dest_state_1 = enable
    log_archive_max_processes= 30
    log_archive_format = ARC%D_%s_%R.%T
    fal_client = orcl
    fal_server = stdby
    db_file_multiblock_read_count= 16
    db_recovery_file_dest = D:\oracle\product\10.2.0\flash_recovery_area
    db_recovery_file_dest_size= 2147483648
    standby_file_management = AUTO
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    undo_retention = 5400
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
    local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=192.168.12.86)(PORT=1521))
    job_queue_processes = 10
    audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
    background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
    user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
    core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
    db_name = orcl
    open_cursors = 500
    pga_aggregate_target = 10737418240
    PMON started with pid=2, OS id=18668
    PSP0 started with pid=3, OS id=17668
    MMAN started with pid=4, OS id=16896
    DBW0 started with pid=5, OS id=18204
    DBW1 started with pid=6, OS id=16976
    LGWR started with pid=7, OS id=14552
    CKPT started with pid=8, OS id=4480
    SMON started with pid=9, OS id=10236
    RECO started with pid=10, OS id=11832
    CJQ0 started with pid=11, OS id=18844
    MMON started with pid=12, OS id=15320
    Fri Apr 12 19:13:27 2013
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=13, OS id=14944
    Fri Apr 12 19:13:27 2013
    starting up 1 shared server(s) ...
    Fri Apr 12 19:13:27 2013
    alter database orcl mount exclusive
    Fri Apr 12 19:13:31 2013
    Setting recovery target incarnation to 2
    Fri Apr 12 19:13:31 2013
    Successful mount of redo thread 1, with mount id 1340305111
    Fri Apr 12 19:13:31 2013
    Allocated 15937344 bytes in shared pool for flashback generation buffer
    Starting background process RVWR
    RVWR started with pid=17, OS id=12880
    Fri Apr 12 19:13:31 2013
    Database mounted in Exclusive Mode
    Completed: alter database orcl mount exclusive
    Fri Apr 12 19:13:31 2013
    alter database open
    Fri Apr 12 19:13:31 2013
    Beginning crash recovery of 1 threads
    parallel recovery started with 15 processes
    Fri Apr 12 19:13:31 2013
    Started redo scan
    Fri Apr 12 19:13:31 2013
    Completed redo scan
    735 redo blocks read, 211 data blocks need recovery
    Fri Apr 12 19:13:31 2013
    Started redo application at
    Thread 1: logseq 117446, block 97761
    Fri Apr 12 19:13:31 2013
    Recovery of Online Redo Log: Thread 1 Group 10 Seq 117446 Reading mem 0
    Mem# 0: G:\ORADATA\REDO10A.LOG
    Mem# 1: H:\ORADATA\REDO10B.LOG
    Fri Apr 12 19:13:31 2013
    Completed redo application
    Fri Apr 12 19:13:32 2013
    Completed crash recovery at
    Thread 1: logseq 117446, block 98496, scn 7310601900
    211 data blocks read, 211 data blocks written, 735 redo blocks read
    Fri Apr 12 19:13:33 2013
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=33, OS id=18508
    ARC1 started with pid=34, OS id=14692
    ARC2 started with pid=35, OS id=17728
    ARC3 started with pid=36, OS id=12476
    ARC4 started with pid=37, OS id=19228
    ARC5 started with pid=38, OS id=11552
    ARC6 started with pid=39, OS id=7576
    ARC7 started with pid=40, OS id=6244
    ARC8 started with pid=41, OS id=18468
    ARC9 started with pid=42, OS id=18492
    ARCa started with pid=43, OS id=10352
    ARCb started with pid=44, OS id=15516
    ARCc started with pid=45, OS id=18216
    ARCd started with pid=46, OS id=5660
    ARCe started with pid=47, OS id=18756
    ARCf started with pid=48, OS id=17828
    ARCg started with pid=49, OS id=8696
    ARCh started with pid=50, OS id=17736
    ARCi started with pid=51, OS id=16736
    ARCj started with pid=52, OS id=13208
    ARCk started with pid=53, OS id=12012
    ARCl started with pid=54, OS id=19180
    ARCm started with pid=55, OS id=16632
    ARCn started with pid=56, OS id=17588
    ARCo started with pid=57, OS id=11948
    ARCp started with pid=58, OS id=18416
    ARCq started with pid=59, OS id=17888
    ARCr started with pid=60, OS id=2144
    ARCs started with pid=61, OS id=14392
    Fri Apr 12 19:13:33 2013
    ARC0: Archival started
    ARCt started with pid=62, OS id=19264
    Fri Apr 12 19:13:33 2013
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    Fri Apr 12 19:13:33 2013
    Thread 1 advanced to log sequence 117447 (thread open)
    Thread 1 opened at log sequence 117447
    Current log# 8 seq# 117447 mem# 0: G:\ORADATA\REDO08A.LOG
    Current log# 8 seq# 117447 mem# 1: H:\ORADATA\REDO08B.LOG
    Successful open of redo thread 1
    Fri Apr 12 19:13:33 2013
    ARC3: Becoming the 'no FAL' ARCH
    Fri Apr 12 19:13:33 2013
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Fri Apr 12 19:13:33 2013
    ARC3: Becoming the 'no SRL' ARCH
    Fri Apr 12 19:13:33 2013
    ARCr: Becoming the heartbeat ARCH
    Fri Apr 12 19:13:33 2013
    SMON: enabling cache recovery
    Fri Apr 12 19:13:33 2013
    Successfully onlined Undo Tablespace 1.
    Fri Apr 12 19:13:33 2013
    SMON: enabling tx recovery
    Fri Apr 12 19:13:33 2013
    Database Characterset is WE8MSWIN1252
    Opening with internal Resource Manager plan
    where NUMA PG = 1, CPUs = 16
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=63, OS id=14896
    Fri Apr 12 19:13:34 2013
    Completed: alter database open
    Fri Apr 12 19:13:34 2013
    ALTER SYSTEM disable restricted session;
    Fri Apr 12 19:13:35 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_mmon_15320.trc:
    ORA-19815: WARNING: db_recovery_file_dest_size of 2147483648 bytes is 99.56% used, and has 9486336 remaining bytes available.
    Fri Apr 12 19:13:35 2013
    You have following choices to free up space from flash recovery area:
    1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
    then consider changing RMAN ARCHIVELOG DELETION POLICY.
    2. Back up files to tertiary device such as tape using RMAN
    BACKUP RECOVERY AREA command.
    3. Add disk space and increase db_recovery_file_dest_size parameter to
    reflect the new space.
    4. Delete unnecessary files using RMAN DELETE command. If an operating
    system command was used to delete files, then use RMAN CROSSCHECK and
    DELETE EXPIRED commands.
    Fri Apr 12 19:13:36 2013
    Error 12514 received logging on to the standby
    Fri Apr 12 19:13:36 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc0_18508.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    FAL[server, ARC0]: Error 12514 creating remote archivelog file 'stdby'
    FAL[server, ARC0]: FAL archive failed, see trace file.
    Fri Apr 12 19:13:36 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc0_18508.trc:
    ORA-16055: FAL request rejected
    ARCH: FAL archive failed. Archiver continuing
    Fri Apr 12 19:19:33 2013
    Error 12514 received logging on to the standby
    Fri Apr 12 19:19:33 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcr_2144.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
    Fri Apr 12 19:22:52 2013
    PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
    Fri Apr 12 20:09:34 2013
    Error 12514 received logging on to the standby
    Fri Apr 12 20:09:34 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcr_2144.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
    Fri Apr 12 20:13:50 2013
    Sat Apr 13 01:54:52 2013
    Error 12514 received logging on to the standby
    Sat Apr 13 01:54:52 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcr_2144.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
    Sat Apr 13 12:35:12 2013
    Error 12514 received logging on to the standby
    Sat Apr 13 12:35:12 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcr_2144.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
    Sat Apr 13 12:37:01 2013
    ALTER SYSTEM SET log_archive_dest_state_2='DEFER' SCOPE=MEMORY;
    Sat Apr 13 12:38:23 2013
    Unable to allocate flashback log of 1946 blocks from
    current recovery area of size 2147483648 bytes.
    Current Flashback database retention is less than target
    because of insufficient space in the flash recovery area.
    Flashback will continue to use available space, but the
    size of the flash recovery area must be increased to meet
    the Flashback database retention target
    Use ALTER SYSTEM SET db_recovery_file_dest_size command
    to add space. DO NOT manually remove flashback log files
    to create space.
    Sat Apr 13 12:38:41 2013
    ALTER SYSTEM SET db_recovery_file_dest_size='5G' SCOPE=MEMORY;
    Sat Apr 13 12:38:41 2013
    db_recovery_file_dest_size of 5120 MB is 39.82% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Sat Apr 13 15:42:21 2013
    ORA-01555 caused by SQL statement below (SQL ID: 2zb70pwz9p06q, Query Duration=1365847941 sec, SCN: 0x0001.b3c0f735):
    Sat Apr 13 15:42:21 2013
    SELECT * FROM RELATIONAL("ORISSA_TRANSACTION"."SELLER_BIOMETRICS_TBL")
    Sat Apr 13 15:48:37 2013
    Thread 1 advanced to log sequence 117452 (LGWR switch)
    Current log# 10 seq# 117452 mem# 0: G:\ORADATA\REDO10A.LOG
    Current log# 10 seq# 117452 mem# 1: H:\ORADATA\REDO10B.LOG
    Sat Apr 13 20:31:00 2013
    The value (30) of MAXTRANS parameter ignored.
    kupprdp: master process DM00 started with pid=31, OS id=16196
    to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_30', 'ORISSA_TRANSACTION', 'KUPC$C_1_20130413203100', 'KUPC$S_1_20130413203100', 0);
    kupprdp: worker process DW01 started with worker id=1, pid=66, OS id=16200
    to execute - SYS.KUPW$WORKER.MAIN('SYS_EXPORT_SCHEMA_30', 'ORISSA_TRANSACTION');
    Sun Apr 14 00:00:11 2013
    Thread 1 advanced to log sequence 117453 (LGWR switch)
    Current log# 8 seq# 117453 mem# 0: G:\ORADATA\REDO08A.LOG
    Current log# 8 seq# 117453 mem# 1: H:\ORADATA\REDO08B.LOG
    Sun Apr 14 00:00:52 2013
    Thread 1 advanced to log sequence 117454 (LGWR switch)
    Current log# 9 seq# 117454 mem# 0: G:\ORADATA\REDO09A.LOG
    Current log# 9 seq# 117454 mem# 1: H:\ORADATA\REDO09B.LOG

    like you show in the alert.log:
    PROBLEM
    Unable to allocate flashback log of 1946 blocks from
    current recovery area of size 2147483648 bytes.
    Current Flashback database retention is less than target
    because of insufficient space in the flash recovery area.
    Flashback will continue to use available space, but the
    size of the flash recovery area must be increased to meet
    the Flashback database retention target
    Use ALTER SYSTEM SET db_recovery_file_dest_size command
    to add space. DO NOT manually remove flashback log files
    to create space.
    SOLUTION
    Fri Apr 12 19:12:51 2013
    You have following choices to free up space from flash recovery area:
    1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
    then consider changing RMAN ARCHIVELOG DELETION POLICY.
    2. Back up files to tertiary device such as tape using RMAN
    BACKUP RECOVERY AREA command.
    3. Add disk space and increase db_recovery_file_dest_size parameter to
    reflect the new space.
    4. Delete unnecessary files using RMAN DELETE command. If an operating
    system command was used to delete files, then use RMAN CROSSCHECK and
    DELETE EXPIRED commands.
    ************************************************************************choose one and try again. Post if you have more issues.

  • Database Recovery in NOARCHIVELOG Mode

    Hi All,
    I was trying to 'startup' my database & encountered the following error in the alert.log
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01122: database file 469 failed verification check
    ORA-01110: data file 469: '/ora/ctcm_uat02/CMOLP1/undo/CMOLP1_undots_30.dbf'
    ORA-01209: data file is from before the last RESETLOGS
    I then looked up on the internet and since the error was related to the UNDO TABLESPACE, i did the following:
    sql>startup mount
    sql>alter database datafile '/ora/ctcm_uat02/CMOLP1/undo/CMOLP1_undots_30.dbf' offline drop;
    sql>alter database open
    Thereafter the database kept on erroring on all the datafiles belonging to the undo tablespaces and i dropped all the datafiles belonging to the undo tablespace using the above command. (alter database datafile ....offline drop).
    Next, i tried to open the database and got the following error from the alert log:
    Tue May 12 18:15:24 2009
    alter database open
    Tue May 12 18:15:33 2009
    Beginning crash recovery of 1 threads
    Tue May 12 18:15:33 2009
    Started redo scan
    Tue May 12 18:15:33 2009
    Completed redo scan
    21 redo blocks read, 3 data blocks need recovery
    Tue May 12 18:15:33 2009
    Started recovery at
    Thread 1: logseq 252, block 2, scn 1917.14626262
    Tue May 12 18:15:33 2009
    Recovery of Online Redo Log: Thread 1 Group 3 Seq 252 Reading mem 0
    Mem# 0 errs 0: /ora/ctcm_dev/CMOLP1/redo/CMOLP1_redo03a.dbf
    Tue May 12 18:15:33 2009
    Completed redo application
    Tue May 12 18:15:33 2009
    Ended recovery at
    Thread 1: logseq 252, block 23, scn 1917.14646284
    3 data blocks read, 3 data blocks written, 21 redo blocks read
    Crash recovery completed successfully
    Tue May 12 18:15:35 2009
    Thread 1 advanced to log sequence 253
    Thread 1 opened at log sequence 253
    Current log# 4 seq# 253 mem# 0: /ora/ctcm_dev/CMOLP1/redo/CMOLP1_redo04a.dbf
    Successful open of redo thread 1
    Tue May 12 18:15:38 2009
    LOG_CHECKPOINT_INTERVAL was set when MTTR advisory was switched on.
    Tue May 12 18:15:38 2009
    SMON: enabling cache recovery
    Tue May 12 18:15:38 2009
    Successfully onlined Undo Tablespace 1.
    Tue May 12 18:15:39 2009
    SMON: enabling tx recovery
    Tue May 12 18:15:39 2009
    Database Characterset is US7ASCII
    Tue May 12 18:15:39 2009
    SMON: about to recover undo segment 1
    Can someone please help me on this issue? Thanks and Regards

    Hi ERROR,
    I think i figured out the hidden parameter that you were referring to.
    (1) I set the allowresetlogs_corruption=TRUE and commented undo_management. Then opened the database using--> alter database open resetlogs;
    But still was not able to start the database. The alert log entries are as below:
    ALTER DATABASE   MOUNT
    Thu May 14 18:11:56 2009
    Successful mount of redo thread 1, with mount id 4113112614
    Thu May 14 18:11:56 2009
    Database mounted in Exclusive Mode.
    Completed: ALTER DATABASE   MOUNT
    Shutting down instance: further logons disabled
    Shutting down instance (immediate)
    License high water mark = 2
    Thu May 14 18:12:05 2009
    ALTER DATABASE CLOSE NORMAL
    ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
    Thu May 14 18:12:05 2009
    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
    Would be great if you can help me further on this.
    Regards,
    Fuzzy

  • 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

  • Exclusive Mode

    Hi friends
    What does "Database cannot be open in Exclusive mode" means?

    What does "Database cannot be open in Exclusive mode" means? That's not the correct error message. Is it? What is your Oracle Release?
    Well, I guess you are getting ORA-01102 while starting the database. You still has background processes running or not shutdown properly
    If you have already shutdown the database, look for the processes and kill them manually. If you hav enot shutdown the database, shutdown the database cleanly.

  • 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

  • Error message in Command line (cannot mount database in EXCLUSIVE mode)

    Hello Experts
    I'm new in Oracle and trying to connect to my database though SQL command line. After I login as SYS I user I get the message that 'connected to idle instance'. Then I use “STARTUP” to connect to database. Now from my understanding it should mount the database and open it as well. But it does'nt happens.Instead I get the message 'cannot mount database in EXCLUSIVE mode' . I'm not sure why it can't mound the database and what should I do to make it working. Please can somebody show me how to make it working again. Here are the details about my problem
    Enter user-name: SYS as SYSDBA
    Enter password:
    Connected to an idle instance.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 595591168 bytes
    Fixed Size 1220748 bytes
    Variable Size 301993844 bytes
    Database Buffers 285212672 bytes
    Redo Buffers 7163904 bytes
    ORA-01102: cannot mount database in EXCLUSIVE mode
    Thanks a lot in advance.

    Thank you so much for both of you. I've checked everything. All looks fine to me and then i tried to connect though SQL and it worked. Now what I've notice that this time I didn't start Enterprise Manager only I started the listner and then start sql it worked. Does this means that I can't use both SQL and EM at a time together?

  • PMON and ORA-01102: cannot mount database in EXCLUSIVE mode error

    hello all
    I have been asked to look into a problem server with the following details
    OS: sunOS 5.8
    Oracle: 10.2.0.1
    sys user password is not available !
    backgrround processes for the instance(sid=test) are running
    only schema credentials available and with that user is able to connect.
    verified all oraenv parameters(ORACLE_SID is same as the running instance(test)).
    only one instance is configured in this server(verified all tnsnames.ora, data files etc).oratab is empty
    the issues are,
    when I tried to connect to the server using "oracle" user using conn / as sysdba
    1. Tried to shutdown using , shutdown immediate
    ORA-01507:database not mounted
    ORACLE instance shut down
    still able to see the background processes and user is able to connect
    2. Tried startup command,
    In the nomount state I can see more than one PMON process with the same sid
    when tried to mount/open
    ran into the error,
    ORA-01102: cannot mount database in EXCLUSIVE mode
    Eventhough the background processes for the "test" instance are running I am not able to shutdown the instance using "oracle" user
    please help
    newbie

    hi
    i renamed lk* file but the issue still remains,
    with the oracle user
    1./ as sysdba
    2. shutdown immediate
    this leads to
    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    SVR4 Error: 2: No such file or directory
    still not able to identify the running oracle instance.
    there is only one oracle home and the oraenv details are set with the correct values
    verified the alert log(ora home details are matching with the env details), details of the oracle processes which are active are in the alert log along with the startup failures(mount errors) at the tail end
    oracle sysdba is not able to identify the already running instance?
    please help
    newbie

  • ORA-011-2 cannot mount database in Exclusive mode

    This is brand new both Oracle 10g and SUSE 9.3 install. The installation went fine, no errors. At the end I tried to verify the installation:
    sqlplus /nolog
    SQL>connect / as sysdba
    Connected to an idle instance
    SQL>startup
    ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file '/opt/oracle/product/10g/dbs/initmydb.ora'
    SQL>
    So, I figured the missing initmydb file must be in different directory so I looked for it, started new shell session and entered this:
    ln -s @ORACLE_BASE/admin/orcl/pfile/initmydb.ora
    $ORACLE_HOME/dbs/initmydb.ora
    Now I get the following error:
    SQL>startup
    ORA-011-2 cannot mount database in Exclusive mode
    This is third time that I am triyng to install both SUSE and Oracle from scratch and I always run in the same problem, so you can only imagine how I feel.

    Now after reading many documents I am even more confused. The thing is, now I can connect to EM and manage database, create tables, etc, which means the database is up, right? However, I am unable to verify the database existance in sqlplus.
    First after I connect as sysdba in sqlplus, the console says "Connected to an idle instance". When I enter show sga sqlplus, the sqlplus displays 0. Startup comand will display error in the above post.
    So, the bottom line is, according to the EM the database is up and running (I can use isqlplus too) but not according to sqlplus on the server itself. What'sgoing on here? I've been reading every single paper on Oracle's and Novell SUSE web sites and couldn't find anything about it.

  • Database Mount and open only exclusive after cluster upgrade to 11R2 Window

    Hi,
    i just finish my 2 nodes upgrade of my cluster from 11.1.7 to 11.2.0.1 under windows. In the upgrade, everything work fine.
    Now, when i connect to my database i can see only one of the 2 nodes have the database open. When i check the log i can see the first node open the database in exclusive mode, so, the second one can not opened because a instance already working with it.
    How can i change the mount of the database in share mode so the cluster can open the database for the 2 nodes?
    I would like to connect in local mode to close and open mount it in share mode but,
    i'm not able to connect anymore in sqlplus in local mode, Why?
    What have been change, the listener is not the same, now i have 3 listeners, one for each node and on global?
    I'm shure i'm missing something, but i do not find the info the the documents.
    Any help will be welcome

    I finaly found the problem.
    After the upgrade the oracle_home was not set correctly

  • Cannot open the database, stuck in mount mode

    Someone please shed some lights on this problem.
    I ran into some media failure, and ended up restoring the database from the offline whole backup.
    The database is in the nonarchivelog mode (I know, it is not good), so there is no archive log files and
    restore database is the only solution.
    . startup mount
    . restore database <== ran ok
    . ALTER DATABASE CLEAR LOGFILE GROUP 1 <== ran ok
    . ALTER DATABASE CLEAR LOGFILE GROUP 2 <== alter failed
    ORA-01624: log 2 needed for crash recovery of instance orcl (thread 1)
    Alter failed with group 2 and 3 because one was CURRENT,
    and one was ACTIVE.
    SQL> select group#, sequence#, members, status from v$log;
    GROUP# SEQUENCE# MEMBERS STATUS
    1 0 2 UNUSED
    3 189 2 CURRENT
    2 188 2 ACTIVE
    I also tried 'alter database open resetlogs', and got:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    I don't think I can recover the datafile since there is no archive log file here.
    Besides, if the restore database ran fine, why did I get SYSTEM01.DBF datafile needs media recovery message?
    Right now, the database is in mount mode, and I cannot open it. How do I solve the problem with
    ALTER DATABASE CLEAR LOGFILE GROUP for group 2 and 3?
    Any suggestion? Thank you for the input.
    The database is 11G running on Window.

    I would think the cold backup ran successfully. Here is the backup record:
    RMAN> run {
    2> shutdown immediate;
    3> startup mount;
    4> allocate channel c1 type disk;
    5> backup as backupset database;
    6> alter database open;
    7> }
    8>
    using target database control file instead of recovery catalog
    database closed
    database dismounted
    Oracle instance shut down
    connected to target database (not started)
    Oracle instance started
    database mounted
    Total System Global Area 535662592 bytes
    Fixed Size 1348508 bytes
    Variable Size 331353188 bytes
    Database Buffers 197132288 bytes
    Redo Buffers 5828608 bytes
    allocated channel: c1
    channel c1: SID=156 device type=DISK
    Starting backup at 29-NOV-09
    channel c1: starting full datafile backup set
    channel c1: specifying datafile(s) in backup set
    input datafile file number=00002 name=C:\APP\DAVECW\ORADATA\ORCL\SYSAUX01.DBF
    input datafile file number=00001 name=C:\APP\DAVECW\ORADATA\ORCL\SYSTEM01.DBF
    input datafile file number=00003 name=C:\APP\DAVECW\ORADATA\ORCL\UNDOTBS01.DBF
    input datafile file number=00005 name=C:\APP\DAVECW\ORADATA\ORCL\EXAMPLE01.DBF
    input datafile file number=00006 name=C:\APP\DAVECW\ORADATA\ORCL\INVENTORY01.DBF
    input datafile file number=00004 name=C:\APP\DAVECW\ORADATA\ORCL\USERS01.DBF
    channel c1: starting piece 1 at 29-NOV-09
    channel c1: finished piece 1 at 29-NOV-09
    piece handle=C:\APP\DAVECW\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_11_29\O1_MF_NNNDF_TAG20091129T230
    632_5K6VQY0W_.BKP tag=TAG20091129T230632 comment=NONE
    channel c1: backup set complete, elapsed time: 00:01:55
    channel c1: starting full datafile backup set
    channel c1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel c1: starting piece 1 at 29-NOV-09
    channel c1: finished piece 1 at 29-NOV-09
    piece handle=C:\APP\DAVECW\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_11_29\O1_MF_NCSNF_TAG20091129T230
    632_5K6VVNJR_.BKP tag=TAG20091129T230632 comment=NONE
    channel c1: backup set complete, elapsed time: 00:00:03
    Finished backup at 29-NOV-09
    database opened
    released channel: c1
    Recovery Manager complete.

  • Error during open standby database in read only mode

    hi,
    alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-10458: standby database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/u02/app/oracle/oradata/standby/system01.dbf'
    Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS:could not resolve the connect identifier specified
    what is the reason of this.
    Thanks in advance.

    thanks for your reply.
    [oracle@standby admin]$ cat listener.ora
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.124)(PORT = 1521))
    LISTENER_STANDBY =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.124)(PORT = 1521))
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME =/opt/app/oracle/product/11.2.0/db_1)
    (PROGRAM = extproc)
    tnsfile
    [oracle@standby admin]$ cat tnsnames.ora
    standby =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST =10.105.1.124)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = standby)
    ora11g =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST =10.105.1.120)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = ora11g)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.120)(PORT = 1521))
    EXTPROC_CONNECTION_DATA =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (CONNECT_DATA =
    (SID = PLSExtProc)
    (PRESENTATION = RO)
    pfile
    [oracle@standby standby]$ cat initstandby.ora
    ora11g.__db_cache_size=130023424
    ora11g.__java_pool_size=4194304
    ora11g.__large_pool_size=4194304
    ora11g.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
    ora11g.__pga_aggregate_target=146800640
    ora11g.__sga_target=276824064
    ora11g.__shared_io_pool_size=0
    ora11g.__shared_pool_size=121634816
    ora11g.__streams_pool_size=8388608
    *.audit_file_dest='/u01/app/oracle/admin/ora11g/adump'
    *.audit_trail='db'
    *.compatible='11.2.0.1.0'
    #*.control_files='/u02/app/ora11g/oradata/ora11g/control01.ctl','/u01/app/oracle/flash_recovery_area/ora11g/control02.ctl'
    *.db_block_size=8192
    *.db_domain=''
    *.db_name='ora11g'
    *.db_recovery_file_dest='/opt/app/oracle/flash_recovery_area'
    *.db_recovery_file_dest_size=4039114752
    *.diagnostic_dest='/opt/app/oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=ora11g)'
    *.memory_target=2016M
    *.open_cursors=300
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.undo_tablespace='UNDOTBS1'
    *.audit_file_dest='/opt/app/oracle/admin/standby/adump'
    *.audit_trail=none
    #*.background_dump_dest='/opt/app/oracle/admin/standby/bdump'
    #*.compatible='10.2.0.2.0'
    #*.control_files='/opt/app/oracle/oradata/standby/control01.ctl'
    #,'/opt/app/oracle/oradata/standby/control02.ctl','/opt/app/oracle/or
    *.control_files='/u02/app/oracle/oradata/standby/control_sb01.ctl'
    #,'/u02/app/oracle/oradata/standby/control_02.ctl','/u02/app/oracle/oradata/standby/control_03.ctl'
    *.core_dump_dest='/u01/app/oracle/diag/rdbms/standby/standby/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    #*.db_name='standby'
    #*.dispatchers='(PROTOCOL=TCP) (SERVICE=standby)'
    *.job_queue_processes=10
    *.log_archive_dest_1='location=/opt/app/oracle/arch'
    *.log_archive_config='dg_config=(standby,ora11g)'
    *.log_archive_dest_1='LOCATION=/opt/app/oracle/oradata/standby/archivelog'
    *.log_archive_dest_2='service=orcl valid_for=(online_logfiles,primary_role) db_unique_name=ora11g'
    *.log_archive_format='%t_%s_%r.dbf'
    *.standby_file_management=auto
    *.db_unique_name =standby
    *.fal_server='ora11g'
    *.fal_client='standby'
    *.service_names='standby'
    *.open_cursors=300
    *.pga_aggregate_target=525336576
    *.processes=1500
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=1576009728
    *.undo_management='AUTO'
    *.undo_tablespace='undotbs02'
    #*.user_dump_dest='/opt/app/oracle/diag/rdbms/standby/standby/trace'
    *.standby_file_management ='manual'
    *.instance_name =standby
    #*.standby_archive_dest=/opt/app/oracle/oradata/standby/archivelog
    *.db_file_name_convert=(/u02/app/ora11g/oradata/ora11g,/u02/app/oracle/oradata/standby)
    *.log_file_name_convert='/u02/app/ora11g/oradata/ora11g','/u02/app/oracle/oradata/standby'
    #*.remote_listener=LISTENER_ora11g

Maybe you are looking for