Database is not avaible

Hello,
When start the dialog instance, the message "Database is not avaible via /usr/sap/<SID>/SYS/exe/ctrun/R3trans -d -w" is displayed.
Can you help us?

Hello,
when you are an SAP customer I would like to ask you to open an OSS message about this issue. You can use component BC-DB-SDB
Thank you very much,
Stefan Seemann

Similar Messages

  • Can't get icloud to restore after crash from ios 8.1 update, says server not avaible, any suggestions?

    Had ipad2 crash during ios 8.1 update, tried different things to make it work, ended up booting as new.  Tried on a couple different days to restore from clould and it says server  not avaible, would love to get the info back, any suggestions?

    Can someone tell me the implications of using the command RESET DATABASE on my system days after I did the open reset logs? I opened the database with the ALTER DATABASE OPEN RESETLOGS in SQL not RMAN and I see the below note.....
    Re: Can't get dataguard to recover after SAN crash.
    To reset the incarnation of the target database in the RMAN repository, which means to do either of the following actions:
    •Inform RMAN that the SQL statement ALTER DATABASE OPEN RESETLOGS has been executed and that a new incarnation of the target database has been created. Note that if you run the RMAN command ALTER DATABASE OPEN RESETLOGS (not the SQL statement with the same keywords), then RMAN resets the target database automatically so that you do not have to run RESET DATABASE. By resetting the database, RMAN considers the new incarnation as the current incarnation of the database.

  • Question: 10gR2 database can not see the 11gR2 ASM diskgroup?

    Hi there,
    env:
    uname -rm
    2.6.18-92.1.22.el5xen x86_64
    Single server(non-RAC)
    note: we don't want to upgrade 10gr2 database into 11gR2 yet. But we created the 11gR2 ASM, then a 11gr2 database on ASM, and plan to migrate datafile in 10gR2 database to 11gR2 ASM
    1. oracle 10gR2 installed first version: 10.2.0.3.0
    2. then install 11gR2 Grid Infrastructure, and created ASM (version 11gr2)
    $ sqlplus / as sysasm
    SQL*Plus: Release 11.2.0.1.0 Production on Tue Oct 19 10:30:56 2010
    Copyright (c) 1982, 2009, Oracle. All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Automatic Storage Management option
    SQL> col name form a15
    SQL> col COMPATIBILITY form a15
    SQL> col DATABASE_COMPATIBILITY form a15
    SQL> l
    1* select name , STATE, COMPATIBILITY, DATABASE_COMPATIBILITY from v$asm_diskgroup
    SQL> /
    NAME STATE COMPATIBILITY DATABASE_COMPAT
    ORCL_DATA1 MOUNTED 11.2.0.0.0 10.1.0.0.0
    ORA_DATA MOUNTED 10.1.0.0.0 10.1.0.0.0
    3. in 10gR2 database
    sqlplus /
    SQL*Plus: Release 10.2.0.3.0 - Production on Tue Oct 19 12:12:31 2010
    Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
    With the Partitioning and Data Mining options
    SQL> select * from v$asm_diskgroup;
    no rows selected
    4. pin the node into css
    # /u01/app/product/11.2.0/grid/bin/crsctl pin css -n mynodename
    CRS-4000: Command Pin failed, or completed with errors.
    Question: 10gR2 database can not see the 11gR2 ASM diskgroup?
    please help
    Thanks
    Scott

    What is the output of
    olsnodes -t -n
    Also, see unix error log and ohasd error log if you find anything in that

  • Database is not starting after RAC installation

    Hi All,
    I have installed 10g R2 2-node RAC on RHEL4 without any problem. But after the installation the database is not starting and i'm not able to connect. It is showing the below error..
    ERROR:
    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    Linux Error: 2: No such file or directory
    Can anybody help what might be the problem?
    Thanks,
    Praveen

    Hi,
    I'm giving the contents of alter log file from the first node...
    Mon Feb 19 16:45:59 2007
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Interface type 1 eth1 10.250.90.0 configured from OCR for use as a cluster interconnect
    Interface type 1 eth0 10.250.90.0 configured from OCR for use as a public interface
    Shared memory segment for instance monitoring created
    Picked latch-free SCN scheme 2
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =36
    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.2.0.
    System parameters with non-default values:
    processes = 300
    sessions = 335
    sga_max_size = 1073741824
    sga_target = 1073741824
    db_block_size = 8192
    compatible = 10.2.0.2.0
    log_archive_dest_1 = LOCATION=+BSA_DATA1/bsaprod/
    log_archive_format = %t_%s_%r.dbf
    db_file_multiblock_read_count= 16
    cluster_database_instances= 1
    db_create_file_dest = +ORCL_DATA1
    instance_number = 1
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    dispatchers = (PROTOCOL=TCP) (SERVICE=bsaprodXDB)
    remote_listener = LISTENERS_BSAPROD
    job_queue_processes = 10
    background_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/bdump
    user_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/udump
    core_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/cdump
    audit_file_dest = /u01/app/oracle/oracle/admin/bsaprod/adump
    db_name = bsaprod
    open_cursors = 300
    pga_aggregate_target = 262144000
    Cluster communication is configured to use the following interface(s) for this instance
    10.250.90.107
    Mon Feb 19 16:46:00 2007
    cluster interconnect IPC version:Oracle UDP/IP (generic)
    IPC Vendor 1 proto 2
    PMON started with pid=2, OS id=31282
    DIAG started with pid=3, OS id=31284
    PSP0 started with pid=4, OS id=31286
    LMON started with pid=5, OS id=31300
    LMD0 started with pid=6, OS id=31315
    MMAN started with pid=7, OS id=31317
    DBW0 started with pid=8, OS id=31319
    LGWR started with pid=9, OS id=31321
    CKPT started with pid=10, OS id=31323
    SMON started with pid=11, OS id=31325
    RECO started with pid=12, OS id=31327
    CJQ0 started with pid=13, OS id=31329
    MMON started with pid=14, OS id=31331
    Mon Feb 19 16:46:00 2007
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=15, OS id=31333
    Mon Feb 19 16:46:00 2007
    starting up 1 shared server(s) ...
    Mon Feb 19 16:46:00 2007
    lmon registered with NM - instance id 1 (internal mem no 0)
    Mon Feb 19 16:46:01 2007
    Reconfiguration started (old inc 0, new inc 2)
    List of nodes:
    0
    Global Resource Directory frozen
    * allocate domain 0, invalid = TRUE
    Communication channels reestablished
    Master broadcasted resource hash value bitmaps
    Non-local Process blocks cleaned out
    Resources and enqueues cleaned out
    Resources remastered 0
    Set master node info
    Submitted all remote-enqueue requests
    Dwn-cvts replayed, VALBLKs dubious
    All grantable enqueues granted
    Post SMON to start 1st pass IR
    Submitted all GCS remote-cache requests
    Post SMON to start 1st pass IR
    Reconfiguration complete
    Mon Feb 19 16:46:01 2007
    CREATE DATABASE "bsaprod"
    MAXINSTANCES 32
    MAXLOGHISTORY 1
    MAXLOGFILES 192
    MAXLOGMEMBERS 3
    MAXDATAFILES 1024
    DATAFILE SIZE 300M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
    EXTENT MANAGEMENT LOCAL
    SYSAUX DATAFILE SIZE 120M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
    SMALLFILE DEFAULT TEMPORARY TABLESPACE TEMP TEMPFILE SIZE 20M AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
    SMALLFILE UNDO TABLESPACE "UNDOTBS1" DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
    CHARACTER SET WE8ISO8859P1
    NATIONAL CHARACTER SET AL16UTF16
    LOGFILE GROUP 1 SIZE 51200K,
    GROUP 2 SIZE 51200K
    USER SYS IDENTIFIED BY *USER SYSTEM IDENTIFIED BY
    Mon Feb 19 16:46:01 2007
    Starting background process ASMB
    ASMB started with pid=19, OS id=31365
    Starting background process RBAL
    RBAL started with pid=20, OS id=31369
    Loaded ASM Library - Generic Linux, version 2.0.2 (KABI_V2) library for asmlib interface
    Mon Feb 19 16:46:05 2007
    SUCCESS: diskgroup ORCL_DATA1 was mounted
    SUCCESS: diskgroup ORCL_DATA1 was dismounted
    Mon Feb 19 16:46:06 2007
    SUCCESS: diskgroup ORCL_DATA1 was mounted
    Mon Feb 19 16:46:06 2007
    Database mounted in Exclusive Mode
    Mon Feb 19 16:46:09 2007
    Successful mount of redo thread 1, with mount id 3309011657
    Assigning activation ID 3309011657 (0xc53b82c9)
    Thread 1 opened at log sequence 1
    Current log# 1 seq# 1 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Successful open of redo thread 1
    Mon Feb 19 16:46:09 2007
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Mon Feb 19 16:46:09 2007
    SMON: enabling cache recovery
    Mon Feb 19 16:46:09 2007
    create tablespace SYSTEM datafile SIZE 300M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
    EXTENT MANAGEMENT LOCAL online
    Mon Feb 19 16:46:20 2007
    Completed: create tablespace SYSTEM datafile SIZE 300M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
    EXTENT MANAGEMENT LOCAL online
    Mon Feb 19 16:46:20 2007
    create rollback segment SYSTEM tablespace SYSTEM
    storage (initial 50K next 50K)
    Completed: create rollback segment SYSTEM tablespace SYSTEM
    storage (initial 50K next 50K)
    Mon Feb 19 16:46:24 2007
    CREATE SMALLFILE UNDO TABLESPACE UNDOTBS1 DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
    Mon Feb 19 16:46:31 2007
    Successfully onlined Undo Tablespace 1.
    Completed: CREATE SMALLFILE UNDO TABLESPACE UNDOTBS1 DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
    Mon Feb 19 16:46:31 2007
    create tablespace SYSAUX datafile SIZE 120M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
    EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO online
    Completed: create tablespace SYSAUX datafile SIZE 120M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
    EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO online
    Mon Feb 19 16:46:36 2007
    CREATE SMALLFILE TEMPORARY TABLESPACE TEMP TEMPFILE SIZE 20M AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
    Completed: CREATE SMALLFILE TEMPORARY TABLESPACE TEMP TEMPFILE SIZE 20M AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
    Mon Feb 19 16:46:36 2007
    ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP
    Completed: ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP
    Mon Feb 19 16:46:36 2007
    ALTER DATABASE DEFAULT TABLESPACE SYSTEM
    Completed: ALTER DATABASE DEFAULT TABLESPACE SYSTEM
    Mon Feb 19 16:46:38 2007
    SMON: enabling tx recovery
    Mon Feb 19 16:46:39 2007
    Threshold validation cannot be done before catproc is loaded.
    Threshold validation cannot be done before catproc is loaded.
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=22, OS id=32303
    Mon Feb 19 16:46:39 2007
    Completed: CREATE DATABASE "bsaprod"
    MAXINSTANCES 32
    MAXLOGHISTORY 1
    MAXLOGFILES 192
    MAXLOGMEMBERS 3
    MAXDATAFILES 1024
    DATAFILE SIZE 300M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
    EXTENT MANAGEMENT LOCAL
    SYSAUX DATAFILE SIZE 120M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
    SMALLFILE DEFAULT TEMPORARY TABLESPACE TEMP TEMPFILE SIZE 20M AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
    SMALLFILE UNDO TABLESPACE "UNDOTBS1" DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
    CHARACTER SET WE8ISO8859P1
    NATIONAL CHARACTER SET AL16UTF16
    LOGFILE GROUP 1 SIZE 51200K,
    GROUP 2 SIZE 51200K
    USER SYS IDENTIFIED BY *USER SYSTEM IDENTIFIED BY
    Mon Feb 19 16:46:39 2007
    CREATE SMALLFILE UNDO TABLESPACE "UNDOTBS2" DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
    Completed: CREATE SMALLFILE UNDO TABLESPACE "UNDOTBS2" DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
    Mon Feb 19 16:46:46 2007
    CREATE SMALLFILE TABLESPACE "USERS" LOGGING DATAFILE SIZE 5M AUTOEXTEND ON NEXT 1280K MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO
    Completed: CREATE SMALLFILE TABLESPACE "USERS" LOGGING DATAFILE SIZE 5M AUTOEXTEND ON NEXT 1280K MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO
    Mon Feb 19 16:46:46 2007
    ALTER DATABASE DEFAULT TABLESPACE "USERS"
    Completed: ALTER DATABASE DEFAULT TABLESPACE "USERS"
    Mon Feb 19 16:47:05 2007
    Thread 1 advanced to log sequence 2
    Current log# 2 seq# 2 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 16:47:34 2007
    Thread 1 cannot allocate new log, sequence 3
    Checkpoint not complete
    Current log# 2 seq# 2 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 3
    Current log# 1 seq# 3 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 16:48:10 2007
    Thread 1 cannot allocate new log, sequence 4
    Checkpoint not complete
    Current log# 1 seq# 3 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 4
    Current log# 2 seq# 4 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 16:49:05 2007
    Thread 1 cannot allocate new log, sequence 5
    Checkpoint not complete
    Current log# 2 seq# 4 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 5
    Current log# 1 seq# 5 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 16:50:19 2007
    Thread 1 cannot allocate new log, sequence 6
    Checkpoint not complete
    Current log# 1 seq# 5 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 6
    Current log# 2 seq# 6 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 16:51:00 2007
    Thread 1 cannot allocate new log, sequence 7
    Checkpoint not complete
    Current log# 2 seq# 6 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 7
    Current log# 1 seq# 7 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 16:51:54 2007
    Thread 1 cannot allocate new log, sequence 8
    Checkpoint not complete
    Current log# 1 seq# 7 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 8
    Current log# 2 seq# 8 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 16:55:32 2007
    Thread 1 cannot allocate new log, sequence 9
    Checkpoint not complete
    Current log# 2 seq# 8 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 9
    Current log# 1 seq# 9 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 16:56:35 2007
    Thread 1 cannot allocate new log, sequence 10
    Checkpoint not complete
    Current log# 1 seq# 9 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 10
    Current log# 2 seq# 10 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 16:56:52 2007
    Thread 1 cannot allocate new log, sequence 11
    Checkpoint not complete
    Current log# 2 seq# 10 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 11
    Current log# 1 seq# 11 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 16:57:04 2007
    Thread 1 cannot allocate new log, sequence 12
    Checkpoint not complete
    Current log# 1 seq# 11 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 12
    Current log# 2 seq# 12 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 16:57:14 2007
    Thread 1 cannot allocate new log, sequence 13
    Checkpoint not complete
    Current log# 2 seq# 12 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 13
    Current log# 1 seq# 13 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 16:57:31 2007
    Thread 1 cannot allocate new log, sequence 14
    Checkpoint not complete
    Current log# 1 seq# 13 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 14
    Current log# 2 seq# 14 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 16:58:13 2007
    Thread 1 cannot allocate new log, sequence 15
    Checkpoint not complete
    Current log# 2 seq# 14 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 15
    Current log# 1 seq# 15 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 16:59:42 2007
    Thread 1 cannot allocate new log, sequence 16
    Checkpoint not complete
    Current log# 1 seq# 15 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 16
    Current log# 2 seq# 16 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 17:00:33 2007
    Thread 1 cannot allocate new log, sequence 17
    Checkpoint not complete
    Current log# 2 seq# 16 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 17
    Current log# 1 seq# 17 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 17:01:49 2007
    Thread 1 cannot allocate new log, sequence 18
    Checkpoint not complete
    Current log# 1 seq# 17 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 18
    Current log# 2 seq# 18 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 17:02:23 2007
    Thread 1 cannot allocate new log, sequence 19
    Checkpoint not complete
    Current log# 2 seq# 18 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 19
    Current log# 1 seq# 19 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 17:04:06 2007
    Thread 1 cannot allocate new log, sequence 20
    Checkpoint not complete
    Current log# 1 seq# 19 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 20
    Current log# 2 seq# 20 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 17:05:22 2007
    Thread 1 cannot allocate new log, sequence 21
    Checkpoint not complete
    Current log# 2 seq# 20 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 21
    Current log# 1 seq# 21 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 17:06:22 2007
    Thread 1 cannot allocate new log, sequence 22
    Checkpoint not complete
    Current log# 1 seq# 21 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 22
    Current log# 2 seq# 22 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 17:08:42 2007
    Thread 1 cannot allocate new log, sequence 23
    Checkpoint not complete
    Current log# 2 seq# 22 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 23
    Current log# 1 seq# 23 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 17:09:43 2007
    Thread 1 cannot allocate new log, sequence 24
    Checkpoint not complete
    Current log# 1 seq# 23 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 24
    Current log# 2 seq# 24 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 17:10:42 2007
    Thread 1 cannot allocate new log, sequence 25
    Checkpoint not complete
    Current log# 2 seq# 24 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 25
    Current log# 1 seq# 25 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 17:11:31 2007
    Thread 1 cannot allocate new log, sequence 26
    Checkpoint not complete
    Current log# 1 seq# 25 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 26
    Current log# 2 seq# 26 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 17:12:01 2007
    Thread 1 cannot allocate new log, sequence 27
    Checkpoint not complete
    Current log# 2 seq# 26 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 27
    Current log# 1 seq# 27 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 17:13:12 2007
    Thread 1 cannot allocate new log, sequence 28
    Checkpoint not complete
    Current log# 1 seq# 27 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 28
    Current log# 2 seq# 28 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 17:14:05 2007
    Thread 1 cannot allocate new log, sequence 29
    Checkpoint not complete
    Current log# 2 seq# 28 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 29
    Current log# 1 seq# 29 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 17:14:57 2007
    Thread 1 cannot allocate new log, sequence 30
    Checkpoint not complete
    Current log# 1 seq# 29 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Thread 1 advanced to log sequence 30
    Current log# 2 seq# 30 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Mon Feb 19 17:16:29 2007
    Thread 1 cannot allocate new log, sequence 31
    Checkpoint not complete
    Current log# 2 seq# 30 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
    Thread 1 advanced to log sequence 31
    Current log# 1 seq# 31 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Mon Feb 19 17:17:54 2007
    Starting background process EMN0
    EMN0 started with pid=25, OS id=15651
    Mon Feb 19 17:17:54 2007
    Shutting down instance: further logons disabled
    Mon Feb 19 17:17:55 2007
    Stopping background process QMNC
    Mon Feb 19 17:17:55 2007
    Stopping background process CJQ0
    Mon Feb 19 17:17:57 2007
    Stopping background process MMNL
    Mon Feb 19 17:17:58 2007
    Stopping background process MMON
    Mon Feb 19 17:17:59 2007
    Shutting down instance (immediate)
    License high water mark = 1
    Mon Feb 19 17:17:59 2007
    Stopping Job queue slave processes
    Mon Feb 19 17:17:59 2007
    Job queue slave processes stopped
    All dispatchers and shared servers shutdown
    Mon Feb 19 17:18:01 2007
    ALTER DATABASE CLOSE NORMAL
    Mon Feb 19 17:18:01 2007
    SMON: disabling tx recovery
    SMON: disabling cache recovery
    Mon Feb 19 17:18:03 2007
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Thread 1 closed at log sequence 31
    Successful close of redo thread 1
    Mon Feb 19 17:18:04 2007
    Completed: ALTER DATABASE CLOSE NORMAL
    Mon Feb 19 17:18:04 2007
    ALTER DATABASE DISMOUNT
    Mon Feb 19 17:18:04 2007
    SUCCESS: diskgroup ORCL_DATA1 was dismounted
    Mon Feb 19 17:18:04 2007
    Completed: ALTER DATABASE DISMOUNT
    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
    Mon Feb 19 17:18:09 2007
    freeing rdom 0
    Mon Feb 19 17:18:12 2007
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Interface type 1 eth1 10.250.90.0 configured from OCR for use as a cluster interconnect
    Interface type 1 eth0 10.250.90.0 configured from OCR for use as a public interface
    Picked latch-free SCN scheme 2
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =36
    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.2.0.
    System parameters with non-default values:
    processes = 300
    sessions = 335
    sga_max_size = 1073741824
    sga_target = 1073741824
    control_files = +ORCL_DATA1/bsaprod/controlfile/current.256.614969167
    db_block_size = 8192
    compatible = 10.2.0.2.0
    log_archive_dest_1 = LOCATION=+BSA_DATA1/bsaprod/
    log_archive_format = %t_%s_%r.dbf
    db_file_multiblock_read_count= 16
    cluster_database_instances= 1
    db_create_file_dest = +ORCL_DATA1
    instance_number = 1
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    dispatchers = (PROTOCOL=TCP) (SERVICE=bsaprodXDB)
    remote_listener = LISTENERS_BSAPROD
    job_queue_processes = 10
    background_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/bdump
    user_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/udump
    core_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/cdump
    audit_file_dest = /u01/app/oracle/oracle/admin/bsaprod/adump
    db_name = bsaprod
    open_cursors = 300
    pga_aggregate_target = 262144000
    Cluster communication is configured to use the following interface(s) for this instance
    10.250.90.107
    Mon Feb 19 17:18:13 2007
    cluster interconnect IPC version:Oracle UDP/IP (generic)
    IPC Vendor 1 proto 2
    PMON started with pid=2, OS id=16124
    DIAG started with pid=3, OS id=16126
    PSP0 started with pid=4, OS id=16128
    LMON started with pid=5, OS id=16130
    LMD0 started with pid=6, OS id=16132
    MMAN started with pid=7, OS id=16134
    DBW0 started with pid=8, OS id=16136
    LGWR started with pid=9, OS id=16138
    CKPT started with pid=10, OS id=16140
    SMON started with pid=11, OS id=16142
    RECO started with pid=12, OS id=16144
    CJQ0 started with pid=13, OS id=16146
    MMON started with pid=14, OS id=16148
    Mon Feb 19 17:18:13 2007
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=15, OS id=16150
    Mon Feb 19 17:18:13 2007
    starting up 1 shared server(s) ...
    Mon Feb 19 17:18:13 2007
    lmon registered with NM - instance id 1 (internal mem no 0)
    Mon Feb 19 17:18:14 2007
    Reconfiguration started (old inc 0, new inc 2)
    List of nodes:
    0
    Global Resource Directory frozen
    * allocate domain 0, invalid = TRUE
    Communication channels reestablished
    Master broadcasted resource hash value bitmaps
    Non-local Process blocks cleaned out
    Resources and enqueues cleaned out
    Resources remastered 0
    Set master node info
    Submitted all remote-enqueue requests
    Dwn-cvts replayed, VALBLKs dubious
    All grantable enqueues granted
    Post SMON to start 1st pass IR
    Submitted all GCS remote-cache requests
    Post SMON to start 1st pass IR
    Reconfiguration complete
    Mon Feb 19 17:18:14 2007
    ALTER DATABASE MOUNT
    Mon Feb 19 17:18:14 2007
    Starting background process ASMB
    ASMB started with pid=19, OS id=16182
    Starting background process RBAL
    RBAL started with pid=20, OS id=16186
    Loaded ASM Library - Generic Linux, version 2.0.2 (KABI_V2) library for asmlib interface
    Mon Feb 19 17:18:18 2007
    SUCCESS: diskgroup ORCL_DATA1 was mounted
    Mon Feb 19 17:18:23 2007
    Setting recovery target incarnation to 1
    Mon Feb 19 17:18:23 2007
    Successful mount of redo thread 1, with mount id 3309012054
    Mon Feb 19 17:18:23 2007
    Database mounted in Exclusive Mode
    Completed: ALTER DATABASE MOUNT
    Mon Feb 19 17:18:23 2007
    alter database archivelog
    Completed: alter database archivelog
    Mon Feb 19 17:18:23 2007
    alter database open
    Mon Feb 19 17:18:23 2007
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=22, OS id=16393
    Mon Feb 19 17:18:23 2007
    ARC0: Archival started
    ARC1: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    ARC1 started with pid=23, OS id=16395
    Mon Feb 19 17:18:23 2007
    Thread 1 opened at log sequence 31
    Current log# 1 seq# 31 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Successful open of redo thread 1
    Mon Feb 19 17:18:23 2007
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Mon Feb 19 17:18:23 2007
    SMON: enabling cache recovery
    Mon Feb 19 17:18:23 2007
    ARC0: STARTING ARCH PROCESSES
    Mon Feb 19 17:18:23 2007
    ARC1: Becoming the 'no FAL' ARCH
    ARC1: Becoming the 'no SRL' ARCH
    Mon Feb 19 17:18:23 2007
    ARC2: Archival started
    ARC0: STARTING ARCH PROCESSES COMPLETE
    ARC0: Becoming the heartbeat ARCH
    ARC2 started with pid=24, OS id=16422
    Mon Feb 19 17:18:23 2007
    Successfully onlined Undo Tablespace 1.
    Mon Feb 19 17:18:23 2007
    SMON: enabling tx recovery
    Mon Feb 19 17:18:23 2007
    Database Characterset is WE8ISO8859P1
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=25, OS id=16449
    Mon Feb 19 17:18:25 2007
    Completed: alter database open
    Mon Feb 19 17:18:25 2007
    ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 3 SIZE 51200K,
    GROUP 4 SIZE 51200K
    Completed: ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 3 SIZE 51200K,
    GROUP 4 SIZE 51200K
    Mon Feb 19 17:18:28 2007
    ALTER DATABASE ENABLE PUBLIC THREAD 2
    Completed: ALTER DATABASE ENABLE PUBLIC THREAD 2
    SUCCESS: diskgroup BSA_DATA1 was mounted
    SUCCESS: diskgroup BSA_DATA1 was dismounted
    Mon Feb 19 17:18:29 2007
    Starting background process EMN0
    EMN0 started with pid=26, OS id=16564
    Mon Feb 19 17:18:29 2007
    Shutting down instance: further logons disabled
    Mon Feb 19 17:18:29 2007
    Stopping background process QMNC
    Mon Feb 19 17:18:29 2007
    Stopping background process CJQ0
    Mon Feb 19 17:18:30 2007
    Stopping background process MMNL
    Mon Feb 19 17:18:31 2007
    Stopping background process MMON
    Mon Feb 19 17:18:32 2007
    Shutting down instance (immediate)
    License high water mark = 3
    Mon Feb 19 17:18:32 2007
    Stopping Job queue slave processes
    Mon Feb 19 17:18:32 2007
    Job queue slave processes stopped
    All dispatchers and shared servers shutdown
    Mon Feb 19 17:18:34 2007
    ALTER DATABASE CLOSE NORMAL
    Mon Feb 19 17:18:34 2007
    SMON: disabling tx recovery
    SMON: disabling cache recovery
    Mon Feb 19 17:18:34 2007
    Shutting down archive processes
    Archiving is disabled
    Mon Feb 19 17:18:39 2007
    ARCH shutting down
    ARC2: Archival stopped
    Mon Feb 19 17:18:44 2007
    ARCH shutting down
    ARC1: Archival stopped
    Mon Feb 19 17:18:49 2007
    ARCH shutting down
    ARC0: Archival stopped
    Mon Feb 19 17:18:50 2007
    Thread 1 closed at log sequence 31
    Successful close of redo thread 1
    Mon Feb 19 17:18:51 2007
    Completed: ALTER DATABASE CLOSE NORMAL
    Mon Feb 19 17:18:51 2007
    ALTER DATABASE DISMOUNT
    Mon Feb 19 17:18:51 2007
    SUCCESS: diskgroup ORCL_DATA1 was dismounted
    Mon Feb 19 17:18:51 2007
    Completed: ALTER DATABASE DISMOUNT
    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
    Mon Feb 19 17:18:56 2007
    freeing rdom 0
    Mon Feb 19 17:18:59 2007
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Interface type 1 eth1 10.250.90.0 configured from OCR for use as a cluster interconnect
    Interface type 1 eth0 10.250.90.0 configured from OCR for use as a public interface
    Picked latch-free SCN scheme 2
    Autotune of undo retention is turned on.
    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.2.0.
    System parameters with non-default values:
    processes = 300
    sessions = 335
    sga_max_size = 1073741824
    spfile = +BSA_DATA1/bsaprod/spfilebsaprod.ora
    sga_target = 1073741824
    control_files = +ORCL_DATA1/bsaprod/controlfile/current.256.614969167
    db_block_size = 8192
    compatible = 10.2.0.2.0
    log_archive_dest_1 = LOCATION=+BSA_DATA1/bsaprod/
    log_archive_format = %t_%s_%r.dbf
    db_file_multiblock_read_count= 16
    cluster_database = TRUE
    cluster_database_instances= 2
    db_create_file_dest = +ORCL_DATA1
    thread = 1
    instance_number = 1
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    dispatchers = (PROTOCOL=TCP) (SERVICE=bsaprodXDB)
    remote_listener = LISTENERS_BSAPROD
    job_queue_processes = 10
    background_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/bdump
    user_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/udump
    core_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/cdump
    audit_file_dest = /u01/app/oracle/oracle/admin/bsaprod/adump
    db_name = bsaprod
    open_cursors = 300
    pga_aggregate_target = 262144000
    Cluster communication is configured to use the following interface(s) for this instance
    10.250.90.107
    Mon Feb 19 17:19:00 2007
    cluster interconnect IPC version:Oracle UDP/IP (generic)
    IPC Vendor 1 proto 2
    PMON started with pid=2, OS id=17373
    DIAG started with pid=3, OS id=17375
    PSP0 started with pid=4, OS id=17377
    LMON started with pid=5, OS id=17379
    LMD0 started with pid=6, OS id=17381
    LMS0 started with pid=7, OS id=17383
    LMS1 started with pid=8, OS id=17387
    MMAN started with pid=9, OS id=17391
    DBW0 started with pid=10, OS id=17393
    LGWR started with pid=11, OS id=17395
    CKPT started with pid=12, OS id=17397
    SMON started with pid=13, OS id=17399
    RECO started with pid=14, OS id=17412
    CJQ0 started with pid=15, OS id=17428
    MMON started with pid=16, OS id=17430
    Mon Feb 19 17:19:00 2007
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=17, OS id=17432
    Mon Feb 19 17:19:00 2007
    starting up 1 shared server(s) ...
    Mon Feb 19 17:19:01 2007
    lmon registered with NM - instance id 1 (internal mem no 0)
    Mon Feb 19 17:19:01 2007
    Reconfiguration started (old inc 0, new inc 2)
    List of nodes:
    0
    Global Resource Directory frozen
    * allocate domain 0, invalid = TRUE
    Communication channels reestablished
    Master broadcasted resource hash value bitmaps
    Non-local Process blocks cleaned out
    Mon Feb 19 17:19:01 2007
    LMS 1: 0 GCS shadows cancelled, 0 closed
    Mon Feb 19 17:19:01 2007
    LMS 0: 0 GCS shadows cancelled, 0 closed
    Set master node info
    Submitted all remote-enqueue requests
    Dwn-cvts replayed, VALBLKs dubious
    All grantable enqueues granted
    Post SMON to start 1st pass IR
    Mon Feb 19 17:19:01 2007
    LMS 1: 0 GCS shadows traversed, 0 replayed
    Mon Feb 19 17:19:01 2007
    LMS 0: 0 GCS shadows traversed, 0 replayed
    Mon Feb 19 17:19:01 2007
    Submitted all GCS remote-cache requests
    Post SMON to start 1st pass IR
    Fix write in gcs resources
    Reconfiguration complete
    LCK0 started with pid=20, OS id=17460
    Mon Feb 19 17:19:02 2007
    ALTER DATABASE MOUNT
    Mon Feb 19 17:19:02 2007
    This instance was first to mount
    Mon Feb 19 17:19:02 2007
    Starting background process ASMB
    ASMB started with pid=22, OS id=17466
    Starting background process RBAL
    RBAL started with pid=23, OS id=17470
    Loaded ASM Library - Generic Linux, version 2.0.2 (KABI_V2) library for asmlib interface
    Mon Feb 19 17:19:06 2007
    SUCCESS: diskgroup ORCL_DATA1 was mounted
    Mon Feb 19 17:19:09 2007
    SUCCESS: diskgroup BSA_DATA1 was mounted
    SUCCESS: diskgroup BSA_DATA1 was dismounted
    SUCCESS: diskgroup BSA_DATA1 was mounted
    SUCCESS: diskgroup BSA_DATA1 was dismounted
    Mon Feb 19 17:19:10 2007
    Setting recovery target incarnation to 1
    Mon Feb 19 17:19:10 2007
    Successful mount of redo thread 1, with mount id 3308997510
    Mon Feb 19 17:19:10 2007
    Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
    Completed: ALTER DATABASE MOUNT
    Mon Feb 19 17:19:11 2007
    ALTER DATABASE OPEN
    This instance was first to open
    Picked broadcast on commit scheme to generate SCNs
    Mon Feb 19 17:19:11 2007
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=26, OS id=17679
    Mon Feb 19 17:19:11 2007
    ARC0: Archival started
    ARC1: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    ARC1 started with pid=27, OS id=17706
    Mon Feb 19 17:19:11 2007
    Thread 1 opened at log sequence 31
    Current log# 1 seq# 31 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Successful open of redo thread 1
    Mon Feb 19 17:19:11 2007
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Mon Feb 19 17:19:11 2007
    ARC0: STARTING ARCH PROCESSES
    Mon Feb 19 17:19:11 2007
    ARC1: Becoming the 'no FAL' ARCH
    ARC1: Becoming the 'no SRL' ARCH
    Mon Feb 19 17:19:11 2007
    SMON: enabling cache recovery
    Mon Feb 19 17:19:11 2007
    ARC2: Archival started
    ARC0: STARTING ARCH PROCESSES COMPLETE
    ARC0: Becoming the heartbeat ARCH
    ARC2 started with pid=28, OS id=17708
    Mon Feb 19 17:19:11 2007
    Successfully onlined Undo Tablespace 1.
    Mon Feb 19 17:19:11 2007
    SMON: enabling tx recovery
    Mon Feb 19 17:19:11 2007
    Database Characterset is WE8ISO8859P1
    Mon Feb 19 17:19:11 2007
    Instance recovery: looking for dead threads
    Instance recovery: lock domain invalid but no dead threads
    Mon Feb 19 17:19:12 2007
    SUCCESS: diskgroup BSA_DATA1 was mounted
    SUCCESS: diskgroup BSA_DATA1 was dismounted
    SUCCESS: diskgroup BSA_DATA1 was mounted
    SUCCESS: diskgroup BSA_DATA1 was dismounted
    SUCCESS: diskgroup BSA_DATA1 was mounted
    SUCCESS: diskgroup BSA_DATA1 was dismounted
    SUCCESS: diskgroup BSA_DATA1 was mounted
    SUCCESS: diskgroup BSA_DATA1 was dismounted
    SUCCESS: diskgroup BSA_DATA1 was mounted
    SUCCESS: diskgroup BSA_DATA1 was dismounted
    Mon Feb 19 17:19:12 2007
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=29, OS id=17735
    Mon Feb 19 17:19:13 2007
    Completed: ALTER DATABASE OPEN
    Mon Feb 19 17:20:11 2007
    Shutting down archive processes
    Mon Feb 19 17:20:16 2007
    ARCH shutting down
    ARC2: Archival stopped
    Mon Feb 19 17:23:35 2007
    Starting background process EMN0
    EMN0 started with pid=74, OS id=28350
    Mon Feb 19 17:23:35 2007
    Shutting down instance: further logons disabled
    Mon Feb 19 17:23:36 2007
    Stopping background process QMNC
    Mon Feb 19 17:23:36 2007
    Stopping background process CJQ0
    Mon Feb 19 17:23:38 2007
    Stopping background process MMNL
    Mon Feb 19 17:23:39 2007
    Stopping background process MMON
    Mon Feb 19 17:23:40 2007
    Shutting down instance (immediate)
    License high water mark = 34
    Mon Feb 19 17:23:40 2007
    Stopping Job queue slave processes
    Mon Feb 19 17:23:40 2007
    Job queue slave processes stopped
    All dispatchers and shared servers shutdown
    Mon Feb 19 17:24:07 2007
    ALTER DATABASE CLOSE NORMAL
    Mon Feb 19 17:24:07 2007
    SMON: disabling tx recovery
    SMON: disabling cache recovery
    Mon Feb 19 17:24:08 2007
    Shutting down archive processes
    Archiving is disabled
    Mon Feb 19 17:24:18 2007
    ARC1: Becoming the 'no FAL' ARCH
    ARC1: Becoming the 'no SRL' ARCH
    ARC1: Archiving disabled
    ARCH shutting down
    Mon Feb 19 17:24:18 2007
    ARC1: Archival stopped
    Mon Feb 19 17:24:18 2007
    ARC0: Becoming the heartbeat ARCH
    Mon Feb 19 17:24:18 2007
    ARC0: Archiving disabled
    ARCH shutting down
    ARC0: Archival stopped
    Mon Feb 19 17:24:19 2007
    Thread 1 closed at log sequence 31
    Successful close of redo thread 1
    Mon Feb 19 17:24:19 2007
    Completed: ALTER DATABASE CLOSE NORMAL
    Mon Feb 19 17:24:19 2007
    ALTER DATABASE DISMOUNT
    Mon Feb 19 17:24:19 2007
    SUCCESS: diskgroup ORCL_DATA1 was dismounted
    Mon Feb 19 17:24:19 2007
    Completed: ALTER DATABASE DISMOUNT
    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
    Mon Feb 19 17:24:25 2007
    freeing rdom 0
    Mon Feb 19 17:24:35 2007
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Interface type 1 eth1 10.250.90.0 configured from OCR for use as a cluster interconnect
    Interface type 1 eth0 10.250.90.0 configured from OCR for use as a public interface
    Picked latch-free SCN scheme 2
    Autotune of undo retention is turned on.
    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.2.0.
    System parameters with non-default values:
    processes = 300
    sessions = 335
    sga_max_size = 1073741824
    __shared_pool_size = 255852544
    __large_pool_size = 4194304
    __java_pool_size = 4194304
    __streams_pool_size = 0
    spfile = +BSA_DATA1/bsaprod/spfilebsaprod.ora
    sga_target = 1073741824
    control_files = +ORCL_DATA1/bsaprod/controlfile/current.256.614969167
    db_block_size = 8192
    __db_cache_size = 801112064
    compatible = 10.2.0.2.0
    log_archive_dest_1 = LOCATION=+BSA_DATA1/bsaprod/
    log_archive_format = %t_%s_%r.dbf
    db_file_multiblock_read_count= 16
    cluster_database = TRUE
    cluster_database_instances= 2
    db_create_file_dest = +ORCL_DATA1
    thread = 1
    instance_number = 1
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    dispatchers = (PROTOCOL=TCP) (SERVICE=bsaprodXDB)
    remote_listener = LISTENERS_BSAPROD
    job_queue_processes = 10
    background_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/bdump
    user_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/udump
    core_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/cdump
    audit_file_dest = /u01/app/oracle/oracle/admin/bsaprod/adump
    db_name = bsaprod
    open_cursors = 300
    pga_aggregate_target = 262144000
    Cluster communication is configured to use the following interface(s) for this instance
    10.250.90.107
    Mon Feb 19 17:24:35 2007
    cluster interconnect IPC version:Oracle UDP/IP (generic)
    IPC Vendor 1 proto 2
    PMON started with pid=2, OS id=29950
    DIAG started with pid=3, OS id=29952
    PSP0 started with pid=4, OS id=29954
    LMON started with pid=5, OS id=29956
    LMD0 started with pid=6, OS id=29958
    LMS0 started with pid=7, OS id=29960
    LMS1 started with pid=8, OS id=29964
    MMAN started with pid=9, OS id=29968
    DBW0 started with pid=10, OS id=29970
    LGWR started with pid=11, OS id=29972
    CKPT started with pid=12, OS id=29974
    SMON started with pid=13, OS id=29976
    RECO started with pid=14, OS id=29978
    CJQ0 started with pid=15, OS id=29980
    MMON started with pid=16, OS id=29982
    Mon Feb 19 17:24:36 2007
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=17, OS id=29984
    Mon Feb 19 17:24:36 2007
    starting up 1 shared server(s) ...
    Mon Feb 19 17:24:36 2007
    lmon registered with NM - instance id 1 (internal mem no 0)
    Mon Feb 19 17:24:39 2007
    Reconfiguration started (old inc 0, new inc 4)
    List of nodes:
    0 1
    Global Resource Directory frozen
    * allocate domain 0, invalid = TRUE
    Communication channels reestablished
    * domain 0 not valid according to instance 1
    * domain 0 valid = 0 according to instance 1
    Mon Feb 19 17:24:39 2007
    Master broadcasted resource hash value bitmaps
    Non-local Process blocks cleaned out
    Mon Feb 19 17:24:39 2007
    LMS 1: 0 GCS shadows cancelled, 0 closed
    Mon Feb 19 17:24:39 2007
    LMS 0: 0 GCS shadows cancelled, 0 closed
    Set master node info
    Submitted all remote-enqueue requests
    Dwn-cvts replayed, VALBLKs dubious
    All grantable enqueues granted
    Mon Feb 19 17:24:39 2007
    LMS 0: 0 GCS shadows traversed, 0 replayed
    Mon Feb 19 17:24:39 2007
    LMS 1: 0 GCS shadows traversed, 0 replayed
    Mon Feb 19 17:24:39 2007
    Submitted all GCS remote-cache requests
    Post SMON to start 1st pass IR
    Fix write in gcs resources
    Reconfiguration complete
    LCK0 started with pid=20, OS id=30069
    Mon Feb 19 17:24:40 2007
    ALTER DATABASE MOUNT
    Mon Feb 19 17:24:41 2007
    Starting background process ASMB
    ASMB started with pid=22, OS id=30121
    Starting background process RBAL
    RBAL started with pid=23, OS id=30125
    Loaded ASM Library - Generic Linux, version 2.0.2 (KABI_V2) library for asmlib interface
    Mon Feb 19 17:24:45 2007
    SUCCESS: diskgroup ORCL_DATA1 was mounted
    Mon Feb 19 17:24:49 2007
    Setting recovery target incarnation to 1
    Mon Feb 19 17:24:49 2007
    Successful mount of redo thread 1, with mount id 3309017062
    Mon Feb 19 17:24:49 2007
    Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
    Mon Feb 19 17:24:51 2007
    SUCCESS: diskgroup BSA_DATA1 was mounted
    SUCCESS: diskgroup BSA_DATA1 was dismounted
    SUCCESS: diskgroup BSA_DATA1 was mounted
    SUCCESS: diskgroup BSA_DATA1 was dismounted
    SUCCESS: diskgroup BSA_DATA1 was mounted
    SUCCESS: diskgroup BSA_DATA1 was dismounted
    SUCCESS: diskgroup BSA_DATA1 was mounted
    SUCCESS: diskgroup BSA_DATA1 was dismounted
    SUCCESS: diskgroup BSA_DATA1 was mounted
    SUCCESS: diskgroup BSA_DATA1 was dismounted
    Mon Feb 19 17:24:52 2007
    Completed: ALTER DATABASE MOUNT
    Mon Feb 19 17:24:52 2007
    ALTER DATABASE OPEN
    Picked broadcast on commit scheme to generate SCNs
    Mon Feb 19 17:24:52 2007
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=25, OS id=30406
    Mon Feb 19 17:24:53 2007
    ARC0: Archival started
    ARC1: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    ARC1 started with pid=26, OS id=30422
    Mon Feb 19 17:24:53 2007
    Thread 1 opened at log sequence 31
    Current log# 1 seq# 31 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
    Successful open of redo thread 1
    Mon Feb 19 17:24:53 2007
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Mon Feb 19 17:24:53 2007
    ARC0: STARTING ARCH PROCESSES
    Mon Feb 19 17:24:53 2007
    ARC1: Becoming the 'no FAL' ARCH
    ARC1: Becoming the 'no SRL' ARCH
    Mon Feb 19 17:24:53 2007
    SMON: enabling cache recovery
    Mon Feb 19 17:24:53 2007
    ARC2: Archival started
    ARC0: STARTING ARCH PROCESSES COMPLETE
    ARC0: Becoming the heartbeat ARCH
    ARC2 started with pid=27, OS id=30436
    Mon Feb 19 17:25:07 2007
    Successfully onlined Undo Tablespace 1.
    Mon Feb 19 17:25:07 2007
    SMON: enabling tx recovery
    Mon Feb 19 17:25:07 2007
    Database Characterset is WE8ISO8859P1
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=29, OS id=30882
    Mon Feb 19 17:26:31 2007
    Completed: ALTER DATABASE OPEN
    Mon Feb 19 17:26:38 2007
    ALTER SYSTEM SET service_names='bsaprod','bsatest' SCOPE=MEMORY SID='bsaprod1';
    Mon Feb 19 17:26:53 2007
    Shutting down archive processes
    Mon Feb 19 17:26:58 2007
    ARCH shutting down
    ARC2: Archival stopped
    Mon Feb 19 17:32:16 2007
    Error: KGXGN aborts the instance (6)
    Mon Feb 19 17:32:16 2007
    Errors in file /u01/app/oracle/oracle/admin/bsaprod/bdump/bsaprod1_lmon_29956.trc:
    ORA-29702: error occurred in Cluster Group Service operation
    LMON: terminating instance due to error 29702
    Mon Feb 19 17:32:17 2007
    System state dump is made for local instance
    System State dumped to trace file /u01/app/oracle/oracle/admin/bsaprod/bdump/bsaprod1_diag_29952.trc
    Mon Feb 19 17:32:18 2007
    Trace dumping is performing id=[cdmp_20070219173217]
    Mon Feb 19 17:32:21 2007
    Instance terminated by LMON, pid = 29956
    and also the output of crs_stat -t in first node is....
    Name Type Target State Host
    ora....d1.inst application ONLINE OFFLINE
    ora....d2.inst application ONLINE OFFLINE
    ora....od1.srv application ONLINE OFFLINE
    ora....od2.srv application ONLINE OFFLINE
    ora....test.cs application ONLINE OFFLINE
    ora.bsaprod.db application ONLINE OFFLINE
    ora....SM1.asm application ONLINE UNKNOWN dsrvbd003
    ora....ER.lsnr application ONLINE UNKNOWN dsrvbd003
    ora....03.lsnr application ONLINE UNKNOWN dsrvbd003
    ora....003.gsd application ONLINE UNKNOWN dsrvbd003
    ora....003.ons application ONLINE UNKNOWN dsrvbd003
    ora....003.vip application ONLINE ONLINE dsrvbd003
    ora....SM2.asm application ONLINE OFFLINE
    ora....04.lsnr application ONLINE OFFLINE
    ora....004.gsd application ONLINE OFFLINE
    ora....004.ons application ONLINE OFFLINE
    ora....004.vip application ONLINE OFFLINE

  • Database is not created in SQL server for Persistant Chat

    Hi All,
    We were deploying the Persistant Chat Lync 2013 Role. We have created the topology and published it. Then the Lync 2013 deployment is done on the Persistant Chat servers, while upgrading the cumulative servers soon after the deployment we are getting the
    error as :
    Test-CsDatabase : Cannot open database "mgc" requested by the login. The login
    failed.
    Login failed for user 'domain\username'.
    At line:1 char:1
    + Test-CsDatabase -ConfiguredDatabases -SqlServerFqdn
    SQL Server ...
    Get-MirrorState also was not giving the proper result. Then when I checked in the SQL server, we found that both mgc and mgccomp databases itself not created.
    Could someone assist how we can install the database now?? I googled but confused a bit. Servers are already LYNC deployed, so which command and procedure we need to follow to install the DB on SQL servers and also in mirror server.
    Never giveup till you get what to want.

    Please share Test-CsDatabase -verbose 
    And Get-MirrorState
    in details
    PLEASE REMEMBER, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answered"

  • CRVS2010 beta - Date field from database does not display in report

    Hi there - can someone please help?!
    I am getting a problem where a date field from the database does not display in the report viewer (It displays on my dev machine, but not on the client machines...details given below)
    I upgraded to VS 2010
    I am using the CRVS2010 Beta
    My development machine is Windows 7 - and so is my fellow developer's
    We are using Microsoft SQL Server 2000
    We run the queries within VS and then we send the data table to VS using .SetDataSource
    We have a few reports which display the date on our dev machines (whether we run the EXE or from within Visual Studio)
    When we roll out to the client machines (running Windows XP SP3) then everything works, except that the date does not display (on quite a few reports)
    This is the only real issue I have had - a show stopper for me
    The rest works well - any input will be greatly appreciated
    Regards,
    Ridwan

    Hi Ridwan,
    After much testing I have it all working now using CRDB_adoplus.dll as a data source ( XML )
    Alter your Config file to look like this:
    <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0"/>
    </startup>
    Then using the code below, and CR requires the Schema to be able to read the date format.
    private void SetToXML_Click(object sender, EventArgs e)
    CrystalDecisions.CrystalReports.Engine.ReportDocument rpt = new CrystalDecisions.CrystalReports.Engine.ReportDocument();
    ISCDReportClientDocument rcd;
    rcd = rptClientDoc;
    string connString = "Provider=SQLOLEDB;Data Source=dwcb12003;Database=xtreme;User ID=sb;Password=password";
    string sqlString = "Select * From Orders";
    OleDbConnection oleConn = new OleDbConnection(connString);
    OleDbDataAdapter oleAdapter = new OleDbDataAdapter(sqlString, oleConn);
    //OleDbDataAdapter oleAdapter2 = new OleDbDataAdapter(sqlString2, oleConn);
    DataTable dt1 = new DataTable("Orders");
    oleAdapter.Fill(dt1);
    System.Data.DataSet ds = new System.Data.DataSet();
    // We need the schema to get the data formats
    ds.WriteXml("c:
    sc.xml", XmlWriteMode.WriteSchema);
    //Create a new Database Table to replace the reports current table.
    CrystalDecisions.ReportAppServer.DataDefModel.Table boTable = new CrystalDecisions.ReportAppServer.DataDefModel.Table();
    //boMainPropertyBag: These hold the attributes of the tables ConnectionInfo object
    PropertyBag boMainPropertyBag = new PropertyBag();
    //boInnerPropertyBag: These hold the attributes for the QE_LogonProperties
    //In the main property bag (boMainPropertyBag)
    PropertyBag boInnerPropertyBag = new PropertyBag();
    //Set the attributes for the boInnerPropertyBag
    boInnerPropertyBag.Add("File Path ", @"C:\sc.xml");
    boInnerPropertyBag.Add("Internal Connection ID", "{680eee31-a16e-4f48-8efa-8765193dccdd}");
    //Set the attributes for the boMainPropertyBag
    boMainPropertyBag.Add("Database DLL", "crdb_adoplus.dll");
    boMainPropertyBag.Add("QE_DatabaseName", "");
    boMainPropertyBag.Add("QE_DatabaseType", "");
    //Add the QE_LogonProperties we set in the boInnerPropertyBag Object
    boMainPropertyBag.Add("QE_LogonProperties", boInnerPropertyBag);
    boMainPropertyBag.Add("QE_ServerDescription", "NewDataSet");
    boMainPropertyBag.Add("QE_SQLDB", "False");
    boMainPropertyBag.Add("SSO Enabled", "False");
    //Create a new ConnectionInfo object
    CrystalDecisions.ReportAppServer.DataDefModel.ConnectionInfo boConnectionInfo =
    new CrystalDecisions.ReportAppServer.DataDefModel.ConnectionInfo();
    //Pass the database properties to a connection info object
    boConnectionInfo.Attributes = boMainPropertyBag;
    //Set the connection kind
    boConnectionInfo.Kind = CrConnectionInfoKindEnum.crConnectionInfoKindCRQE;
    //*EDIT* Set the User Name and Password if required.
    boConnectionInfo.UserName = "";
    boConnectionInfo.Password = "";
    //Pass the connection information to the table
    boTable.ConnectionInfo = boConnectionInfo;
    //Get the Database Tables Collection for your report
    CrystalDecisions.ReportAppServer.DataDefModel.Tables boTables;
    boTables = rptClientDoc.DatabaseController.Database.Tables;
    //For each table in the report:
    // - Set the Table Name properties.
    // - Set the table location in the report to use the new modified table
    boTable.Name = "Orders";
    boTable.QualifiedName = "Orders";
    boTable.Alias = "Orders";
    rptClientDoc.DatabaseController.SetTableLocation(boTables[0], boTable);
    //Verify the database after adding substituting the new table.
    //To ensure that the table updates properly when adding Command tables or Stored Procedures.
    rptClientDoc.VerifyDatabase();
    MessageBox.Show("Data Source Set", "RAS", MessageBoxButtons.OK, MessageBoxIcon.Information);
    Thanks again
    Don

  • Database does not exist in the specified path

    Just bought a USB 6009 DAQ and for some reason I now keep getting this error: "Database does not exist in the specified path" in VI Logger 2.0.1 it was working.  Can anyone help??

    Jared,
    It sounds like VI Logger somehow lost its association with its
    database. Please open MAX and check out the "Historical
    Data"->"Citadel 5 Universe" entry. Under "My Computer" in the
    right-hand pane, you should have a database called "VI Logger Data". It
    must be spelled, spaced, and capitalized the exact same way. If you do
    not have this database (which I suspect you do not), right click on "My
    Computer" and select "Create/Attach Database..." The default database
    path (if you want to have access to your old data) is C:\Documents and
    Settings\All Users\Application Data\National Instruments\VI Logger,
    with the database name as "VI Logger Data". If you want to create a new
    database, then specify a new path.
    If "VI Logger Data" does appear, a possible fix is to detach and
    reattach it. Right click on "VI Logger Data," select
    "Detach/Delete...," and chose the "Detach" option. Finally, reattach
    the database as described above.
    Hope this helps,
    Ryan Verret
    Product Marketing Engineer
    Signal Generators
    National Instruments

  • Shrink database is not active in SQL SERVER Enterpriser manager

    Dear guru
    Shrink database is not active in SQL SERVER Enterpriser manager what to do
    Rupesh
    SAP BASIS Consultant

    Hi,
    >Thank you very much for not supporting i have solved the problem by reading some other documents
    That's exactly what I wanted you to do : With a little personal work, you can actually learn to do your own work ! "Don't give fish to hungry people. Teach them how to go fishing !"
    Regards,
    Olivier

  • RCVCAT database is not compatible with this version of RMAN

    I am getting the below error while trying to configure rman catalog datababse.
    rman target prod_dba/Pass1234@proddb catalog cat_dba/Pass1234@catdb
    Recovery Manager: Release 9.2.0.1.0 - Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to target database: TESTDB (DBID=2409515669)
    connected to recovery catalog database
    recovery catalog is not installed
    RMAN>
    RMAN> register database;
    recovery catalog is not installed
    recovery catalog is not installed
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of register command at 07/20/2007 19:05:40
    RMAN-06429: RCVCAT database is not compatible with this version of RMAN
    RMAN>
    And Oracle version is same in proddb and catdb
    SQL> select * from v$version;
    BANNER
    Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    PL/SQL Release 9.2.0.1.0 - Production
    CORE 9.2.0.1.0 Production
    TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
    NLSRTL Version 9.2.0.1.0 - Production
    any inputs...
    Thanks.

    Hi,
    when upgrading catalog am getting the error like,
    error occurred in source file: krmk.pc, line: 6986
    text of failing SQL statement: ╠≥`☺
    ORACLE error from recovery catalog database: ORA-00942: table or view does not e
    xist
    error occurred in source file: krmk.pc, line: 6986
    text of failing SQL statement: ╠≥`☺
    ORACLE error from recovery catalog database: ORA-00942: table or view does not e
    xist
    error occurred in source file: krmk.pc, line: 6986
    text of failing SQL statement:µ`☺
    ORACLE error from recovery catalog database: ORA-00942: table or view does not e
    xist
    Whether i need to run catpath.sql etc on the db?

  • TARGET database is not compatible with this version of RMAN

    I am trying to register a database (version 8.0.4) on my catalog database which is version 8.1.7.
    I get the following error:
    RMAN-06185: Recovery Manager incompatible with TARGET database: RMAN 8.0.4 to 8.0.4 required
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-06429: TARGET database is not compatible with this version of RMAN
    Does this mean that my RMAN database has to be 8.0.4 ?
    What happens if my RMAN database is 8.0.4 and target is 8.1.7 ?
    Thanks for any help,
    Sameer

    check RMAN compatibility matrix
    Target/Auxiliary Database|| RMAN Executable|| Catalog Database ||Catalog Schema
    8.0.3 8.0.3 >=8.x 8.0.3
    8.0.4 8.0.4 >=8.x >= 8.0.4, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
    8.0.5 8.0.5 >=8.x >= 8.0.5, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
    8.0.6 8.0.6 >=8.x 8.0.6
    8.0.6 8.0.6 >=8.1.x >=8.1.x
    8.1.5 8.1.5 >=8.1.x >= 8.1.5
    8.1.6 8.0.6.1 >=8.x 8.0.6
    8.1.6 8.0.6.1 >=8.1.x >= 8.1.x
    8.1.6 8.1.x >=8.1.x >= RMAN executable
    8.1.7 8.0.6.1 >=8.x 8.0.6
    8.1.7 8.0.6.1 >=8.1.x >=8.1.x
    8.1.7 8.1.x >=8.1.x >= RMAN executable
    9.0.1 >=9.0.1 >=8.1.x >= RMAN executable
    In other words to backup 8.0.4 version u need a separate schema in catalog database and which will be only used for 8.0.4

  • TARGET database is not compatible with RMAN version

    Hi all,
    we have an issue related to RMAN version.
    A few weeks ago we update our 10.2.0.1 Oracle Database to 10.2.0.4 using 6810189 pacth set.
    Now when we try to execute RMAN this is the output:
    Recovery Manager : Release 11.1.0.6.0 - Production on Jue Nov 20 12:20:57 2008
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.4 needed
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-06429: TARGET database is not compatible with this version of RMAN
    (I translate the spanish message, maybe the words is not exactly the same in the english version)
    As is shown in the output the RMAN version installed by the pacthset is higher than database version, is there a way to downgrade RMAN or to solve this issue?
    Thanks in advance,
    Alex

    I'm pretty sure patchset 6810189 does not install RMAN executable 11g. I did several patchings to 10.2.0.4 and that never happened. Patching may sometimes leave components at a lower level than the patchset,but never the opposite is true. That would be definitely a bug. So you (or someone else) installed 11g software.
    Werner

  • RMAN-06429: TARGET database is not compatible with this version of RMAN

    he Hi,
    how can i solve this issue . how i will upgrade the Rman. My production database details are below
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    while i'm configuring rman i'm getting below error . please help me.
    C:\Documents and Settings\vj.dcruz>rman target / catalog rman01/rman01@upp
    Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 08:18:02 2011
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.0 required
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-06429: TARGET database is not compatible with this version of RMAN
    rgds,
    john

    Johnvd wrote:
    Hi Hemant,
    i'm doing same thing login 10.2.0.0 database and configure the rman but while connect target its saying that my Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 09:04:59 2011
    how its happening is there any where i have to change the path.
    Regards,
    johnJohn, you need to use the RMAN binary which is located in bin folder of Oracle Database (ie /u01/oracle/product/10.2/db1/bin). You shouldn't use "rman which comes with Oracle 11g client".
    If you are using windows, run the following commands in command prompt and then copy/paste the output:
    echo 5ORACLE_HOME%
    echo %PATH%
    If you are using unix, run the following commands in terminal and then copy/paste the output:
    echo $ORACLE_HOME
    echo $PATH
    Regards
    Gokhan

  • After upgrading ACS 3.3.1 to 4.2 on windows the local database is not working

    Hi,
    I have upgaded the ACS 3.3.1 for windows server to 4.2. Everything went fine but the local database is not working.
    The CD is an upgrade kit from 3.x to 4.2 on windows. I tried to install directly the 4.2 I was able to install but integration with AD/LDAp is not working. Anysay its an upgrade kit so I cant expect it shoud work when install drectly the 4.2 but by upgrading from 3.3 to 4.2 everything should work fine.
    I followed the upgradation path as recomended.
    Also we have a requirment that once it is upgraded to 4.2 we need to shift the whole thing from the physical server to a virtual machine on VMware ESX server 3.5.
    Can anybody pls guide me if anything else to do after the upgradation.
    Thanks & Regards
    Sachi

    Hi Javier,
    First of all I was facing a problem of restoring the old database of 3.3 to 4.2. Somehow I overcame that issue by following the below steps. Now local authentication is working fine but AD/other External database authentication is not working. As you told the setting for the unknown users are configured to fetch the credentials from the external database if it is not in the local database.
    Do we need to do anything in the AD itself?
    Regards
    Sachi
    Steps for ACS upgrade to 4.2 version
    Below are the requested steps mentioned for the up gradation from ACS 3.3.2 to ACS 4.2.
            1)     Take a configuration backup from existing ACS. ACS--->System
    configuration----> ACS Backup
    2)    now if you have  ACS 3.3.2 on server. take backup of the ACS
    3)   Insert the cd or if you have the set up on the system then  Run the setup of ACS 3.3.4. During the process it will prompt you to
    upgrade existing configuration. Make sure you check that option else we will
    loose the database. Now you need to hit next.next to finish the 3.3.4 upgrade.
    4)     Once you are at 3.3.4, take a backup and keep it handy.
    5)     Run the setup of 4.1.1. During this process it will prompt you to
    upgrade existing configuration. Make sure you check that option else we will
    loose the database. Now you need to hit next.next to finish the 4.1 upgrade.
    6)Once you are at 4.1.1.24 take a backup and keep it handy.
    7)     Run the setup of 4.2. During this process it will prompt you to
    upgrade existing configuration. Make sure you check that option else we will
    loose the database. Now you need to hit next.next to finish the 4.2 upgrade.
    8)     Once you are at 4.2 take a backup and keep it handy. Now run the
    patch 12 and take a backup again.
    9)     Now fresh install 4.2 on your new production server and install patch
    12. Restore the 4.2 patch 12 backup and you should be all set.

  • Error creating a new user profile service application: The specified database is not a valid synchronization database

    When trying to create a new user profile service application on a new SharePoint install I get the following error:
    "The specified database is not a valid synchronization database"
    The installation then fails and does not create the third database. 
    I found some threads with similar problems but it involved upgrading an existing db.  In this case we want to create a new one.  Here is the relevant ULS log info:
    Starting schema provisioning of SynchronizationDatabase 'SP15_TEST_ENT_SyncDB'
    Provisioning the SP15_TEST_ENT_SyncDB database with the script at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Template\SQL\SPS\drop_procs.sql.
    Provisioning the SP15_TEST_ENT_SyncDB database with a script stream.
    Ensuring that the SP15_TEST_ENT_SyncDB database exists . . .
    The SP15_TEST_ENT_SyncDB database does not exist. 
    It will now be created.
    Setting the AutoClose option to False on the database SP15_TEST_ENT_SyncDB.
    Setting the ArithAbort option to True on the database SP15_TEST_ENT_SyncDB.
    Setting the TruncLogOnChkpt option to True on the database SP15_TEST_ENT_SyncDB.
    Starting schema evaluation of existing SynchronizationDatabase 'SP15_TEST_ENT_SyncDB'
    Validate Database: validating sync database
    Validate Database: validation failed: Error code -2
    Application error when access /_admin/NewProfileServiceApplicationSettings.aspx, Error=The specified database is not a valid synchronization database 
     at Microsoft.Office.Server.Administration.SynchronizationDatabase.Provision()   
     at Microsoft.Office.Server.Administration.UserProfileApplication.Provision()   
     at Microsoft.SharePoint.Portal.UserProfiles.AdminUI.NewProfileServiceSettingsPage.DoCreateApplication()   
     at Microsoft.SharePoint.Portal.UserProfiles.AdminUI.NewProfileServiceSettingsPage.OnOkButtonClick(Object sender, EventArgs e)   
     at System.EventHandler.Invoke(Object sender, EventArgs e)   
     at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)   
     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    Microsoft.SharePoint.Administration.SPDatabaseException: The specified database is not a valid synchronization database  
     at Microsoft.Office.Server.Administration.SynchronizationDatabase.Provision()   
     at Microsoft.Office.Server.Administration.UserProfileApplication.Provision()   
     at Microsoft.SharePoint.Portal.UserProfiles.AdminUI.NewProfileServiceSettingsPage.DoCreateApplication()   
     at Microsoft.SharePoint.Portal.UserProfiles.AdminUI.NewProfileServiceSettingsPage.OnOkButtonClick(Object sender, EventArgs e)   
     at System.EventHandler.Invoke(Object sender, EventArgs e)   
     at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)   
     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> Microsoft.SharePoint.Administration.SPDatabaseException:
    The specified database is not a valid synchronization database   
     at Microsoft.Office.Server.Administration.SynchronizationDatabase.Provision()   
     at Microsoft.Office.Server.Administration.UserProfileApplication.Provision()   
     at Microsoft.SharePoint.Portal.UserProfiles.AdminUI.NewProfileServiceSettingsPage.DoCreateApplication()   
     at Microsoft.SharePoint.Portal.UserProfiles.AdminUI.NewProfileServiceSettingsPage.OnOkButtonClick(Object sender, EventArgs e)   
     at System.EventHandler.Invoke(Object sender, EventArgs e)   
     at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)   
     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)   
     at System.Web.UI.Page.HandleError(Exception e)   
     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)   
     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)   
     at System.Web.UI.Page.ProcessRequest()   
     at System.Web.UI.Page.ProcessRequest(HttpContext context)   
     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()   
     at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
    I Tried to create another one under a different name (databases also) and I get the same error. 
    The SharePoint instance has the march mandatory update installed.  The sql instance we are using is an existing SQL cluster for other SharePoint poc's. 
    Has anybody seen this issue before? 

    I had the same problem and could not figure out what was wrong for the longest time.  I then had the idea to check in the model system database to see if there were any extra custom tables in that database.  Any tables that are in the model database
    are put into any new database when it is created.  I had some custom tables in the model database so I deleted the custom tables in the model database and deleted the failed user profile service application and its databases and then tried to recreate
    the user profile service application again and it worked with no errors

  • Unable to refresh the schema of FIM MA.Getting an error in Event viewer ""the current version of database is not compatible with the one expected by Forefront Identity Manager service. The current version of database is : 1116. The expected version is :1"

    Hi,
    We have installed FIM MA with an account that have all the sufficient rights.It got created successfully and worked for Full Import and Full Sync. But, due to some version incompatabilities, we have installed a patch.PFB link for the patch.
    http://support.microsoft.com/en-us/kb/2969673/en-us
    Now, we are trying to refresh the schema of FIM MA. While doing that we are facing an error "Failed to connect to database". The user account with which we are connecting has read and write permissions on DB.In the event viewer some errors are
    logged like  "the current version of database is not compatible with the one expected by Forefront Identity Manager service. The current version of database is : 1116. The expected version is :1122" with event ID 3. PFB images for more detailed
    view.
    Please advice how to fix the issue.
    Thanks
    Prasanthi.

    Hello,
    seems to me that you maybe only updated the syncengine but not portal/webservice.
    I had that error once after an recovery from scratch and forgot one of the hotfixes to apply to all services.
    -Peter
    Peter Stapf - ExpertCircle GmbH - My blog:
    JustIDM.wordpress.com

Maybe you are looking for