Error in restructuring a database

Hello,<BR><BR>We encounter a recurrent exception error when restructuring one of our Essbase Database :<BR><BR>[Fri Apr 28 23:29:35 2006]Local/Brpobsol/Ptbdp015/Batch01/Error(1070051)<BR>Duplicate key [0.65] found in AVL-Tree.<BR>[Fri Apr 28 23:29:35 2006]Local/Brpobsol/Ptbdp015/Batch01/Info(1008108)<BR>Essbase Internal Logic Error [7101]<BR>[Fri Apr 28 23:29:35 2006]Local/Brpobsol/Ptbdp015/Batch01/Info(1008106)<BR>Exception error log [E:\SYSAPP\ESSBASE\app\Brpobsol\Ptbdp015\log00072.xcp] is being created...<BR><BR>The .xcp file is like this : <BR><BR>Assertion Failure - id=7101 condition='((( sts == 0 )))'<BR> - line 2782 in file indavl.c<BR> - arguments [0] [0] [0] [0]<BR><BR><BR>Our Essbase version is 6.5.1<BR><BR>Thanks for your answer, this is a very blocking issue.<BR><BR><BR><BR><BR>

The only solution is to pass this to Hyperion and get them to look at it.<BR><BR>They can generally make a few valid suggestions as to what might be the issue.

Similar Messages

  • Error: Unable to Load Database

    Anyone seen this error: "Unable to Load Database"? How to recover? A link or a page for me to read would work too. thx! James

    The usual cause for this is that the database has become corrupted - or one or more key files was somehow deleted. Take a look at the application log and see if there is a more detailed message. Unfortunately, if the data has been corrupted, you will have to recover from backup, or rebuild your cube.To get the database started, you can go into the database directory and delete the *.ind, *.pag, *.tct, *.ind and *.esm files. This will allow the app to start, but the data will be GONE - you will HAVE to reload and calc it, or restore from backup.Regards,Jade--------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

  • Error saving job  to database for standard jobs scheduling

    Hi,
        In IDES server when iam goto Tr.code -- SM36 -- Standard Jobs -- Default Scheduling iam getting below error.
    Error saving job  to database
    Message no. BT117
    Diagnosis
    The SAP system was unable to save the current job in the database. This failure suggests that there is a problem with the database system or with the network connections between the SAP application servers and the database system.
    System Response
    Job not saved and not scheduled.
    Procedure
    To analyze this problem, start by checking the system log for messages about network or database problems.  You can also use the computing center management system to check your system for problems.
    Guide me for the same.
    Thanku

    HI,
    Sometimes this error will come.
    Try to schedule jobs manually using SM36 instead of using standard job button.
    Also you can check this thread
    Re: Error saving job SAP_REORG_JOBS to database
    Which seems to report same problem.
    Its nothing to take with database conenctivity as SAP is up and running .
    Try this and revert.
    Regards,

  • Resolution to error - Unable to update Database Statistics

    OK, If there's one thing i hate most about SAP, its the dreaded installation, I am always so paranoid, as to something will definitely go wrong,
    Lately i realized that it aint my mind , but the damn installation itself is pretty damn stupid. Why cant SAP leave the installation packaging to professionals like installshield...
    Unfortunately SAP doesnt think of it as a better idea, so until then lets try to resolve as many errors as possible thru these forums..
    Here's one error resolution ,i am pretty sure, many are checking for..
    Use the following procedure to resolve error
    <b>Warning - "loading of sql client library oci.dll failed"
    Error - Unable to update Database Statistics, Check BRCONNECT.log</b>
    The problem seems to be with the SAP Patch Collection InstallMaster disc Material No.(<b>51032143_13</b>).
    To resolve the problem, here's what needs to be done,
    1)Install DB Instance as usual.Then after the installation errors out due to loading of sql
    client library oci.dll ..
    2)I unsar the downloaded DBATOOLS.sar (Thanks for the Link Andreaz!!!)
    log into sapnet (eg. service.sap.com) with your user-id/pwd:
    -> downloads -> support packages and patches -> entry by application group -> additional
    components -> sap kernel -> now chose either 32 or 64 bit; either unicode or non-unicode ->
    sap kernel 6.40 -> windows server -> oracle -> download the package DBATOOLS Package for
    Oracle 9.2.x ... brconnect is part of that package...
    3)Copy the files in the Unsar'd package, as follows
         overwrite br*.exe to S:\usr\sap\R31\SYS\exe\run
         overwrite initSID.sap to S:\usr\sap\R31\SYS\exe\run & 
    S:\usr\sap\R31\SYS\exe\nuc\NTI386
         overwrite libsbt.dll to S:\usr\sap\R31\SYS\exe\run &
    S:\usr\sap\R31\SYS\exe\nuc\NTI386
         overwrite sapdba_role.sql to S:\usr\sap\R31\SYS\exe\run &
    S:\usr\sap\R31\SYS\exe\nuc\NTI386
    4) Retry the installation again & Guess what!! it works....
    Warning-: I initially tried a shortcut by replacing DBATOOLS.sar on the installmaster disc, rather than following above steps, but that doesnt seem to work, the installation fails as as soon as Tablespace creation starts. So the shortcut aint a good one..

    Well, it looks like you resolved your problem yourself.
    you can send feedback to SAP directly instead of posting this here in a forum.

  • Error in creating Duplicate Database in same server..

    Hi,
    I am getting following error when creating duplicate database
    DB Version=10.2.0.4
    $ rman target sys/sys@test nocatalog auxiliary /
    Recovery Manager: Release 10.2.0.4.0 - Production on Mon Sep 28 15:13:32 2009
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: TEST (DBID=1702666620, not open)
    using target database control file instead of recovery catalog
    connected to auxiliary database: CLNTEST (not mounted)
    RMAN> DUPLICATE TARGET DATABASE TO "CLNTEST";
    Starting Duplicate Db at 28-SEP-09
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=156 devtype=DISK
    contents of Memory Script:
    set until scn 597629461;
    set newname for datafile 1 to
    "/u01/data_new/clonetest/system01.dbf";
    set newname for datafile 2 to
    "/u01/data_new/clonetest/undotbs01.dbf";
    set newname for datafile 3 to
    "/u01/data_new/clonetest/sysaux01.dbf";
    set newname for datafile 4 to
    "/u01/data_new/clonetest/users01.dbf";
    set newname for datafile 5 to
    "/u01/data_new/clonetest/example01.dbf";
    set newname for datafile 6 to
    "/u01/data_new/clonetest/undotbs02.dbf";
    set newname for datafile 7 to
    "/u01/data_new/clonetest/alweb1.dbf";
    set newname for datafile 8 to
    "/u01/data_new/clonetest/indx1.dbf";
    restore
    check readonly
    clone database
    executing Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 28-SEP-09
    using channel ORA_AUX_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/28/2009 15:13:40
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 8 found to restore
    RMAN-06023: no backup or copy of datafile 7 found to restore
    RMAN-06023: no backup or copy of datafile 6 found to restore
    RMAN-06023: no backup or copy of datafile 5 found to restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    RMAN-06023: no backup or copy of datafile 3 found to restore
    RMAN-06023: no backup or copy of datafile 2 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    RMAN> crosscheck backupset of datafile 1;
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=154 devtype=DISK
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    RMAN> crosscheck backupset of datafile 2;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    RMAN> crosscheck backupset of datafile 3;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    RMAN> crosscheck backupset of datafile 4;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    RMAN> crosscheck backupset of datafile 5;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    RMAN> crosscheck backupset of datafile 6;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    RMAN> crosscheck backupset of datafile 7;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    Thanks,

    Hi,
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/ora10g/product/10.2.0/db_1/dbs/snapcf_TEST.f'; # default
    Thanks,

  • Gating error while creating standby database in oracle 11g

    Dear Gurus
    I am getting following error while creating standby database. My database version is oracle 11g 11.2.0.1 in Redhat 5.2
    RMAN> duplicate target database for standby from active database;
    Starting Duplicate Db at 10-MAY-12
    using channel ORA_AUX_DISK_1
    contents of Memory Script:
    backup as copy reuse
    targetfile '/oracle/product/11.2.0/dbhome_1/dbs/orapworcl' auxiliary format
    '/oracle/product/11.2.0/dbhome_1/dbs/orapwstdb' ;
    executing Memory Script
    Starting backup at 10-MAY-12
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/10/2012 15:44:18
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/10/2012 15:44:18
    ORA-17629: Cannot connect to the remote database server
    ORA-17627: ORA-12528: TNS:listener: all appropriate instances are blocking new connections
    ORA-17629: Cannot connect to the remote database server
    RMAN>
    Regards
    Rabi

    Hello;
    Generally for the connection to work you need to add something like this to the listener.ora file :
    (SID_DESC =
        (global_dbname = STANDBY.hostname)
        (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
        (sid_name = STANDBY)
    )You should stop and start the listener on the Standby after adding this. Also your tnsnames.ora must be correct on both the primary and the Standby.
    Also you need an INIT for the Standby side :
    STANDBY.__db_cache_size=343932928
    STANDBY.__java_pool_size=4194304
    STANDBY.__large_pool_size=4194304
    STANDBY.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
    STANDBY.__pga_aggregate_target=281018368
    STANDBY.__sga_target=834666496
    STANDBY.__shared_io_pool_size=0
    STANDBY.__shared_pool_size=469762048
    STANDBY.__streams_pool_size=0
    audit_file_dest='/u01/app/oracle/admin/PRIMARY/adump'
    audit_trail='db'
    compatible='11.2.0.0.0'
    control_files='/u01/app/oracle/oradata/PRIMARY/control01.ctl','/u01/app/oracle/oradata/PRIMARY/control02.ctl'
    db_block_size=8192
    db_domain='SOME.DOMAIN.COM'
    db_flashback_retention_target=2880
    db_name='PRIMARY'
    db_recovery_file_dest_size=2147483648
    db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
    diagnostic_dest='/u01/app/oracle'
    dispatchers='(PROTOCOL=TCP) (SERVICE=PRIMARYXDB)'
    log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST'
    open_cursors=300
    pga_aggregate_target=277872640
    processes=150
    remote_login_passwordfile='EXCLUSIVE'
    sga_target=833617920
    undo_tablespace='UNDOTBS1'
    log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STANDBY'
    log_archive_dest_2='SERVICE=PRIMARY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) '
    LOG_ARCHIVE_DEST_STATE_1=ENABLE
    LOG_ARCHIVE_DEST_STATE_2=DEFER
    LOG_ARCHIVE_MAX_PROCESSES=30
    FAL_SERVER=STANDBY
    STANDBY_FILE_MANAGEMENT=AUTO
    DB_UNIQUE_NAME=STANDBYFinally
    startup nomount
    Start RMAN and issue duplicate command
    $ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
    RMAN>duplicate target database for standby from active database NOFILENAMECHECK;
    Keys to success
    1. New Standby start NOMOUNT on new password file. ( On Oracle 11 you must copy and rename the file from Primary server )
    2. Hard coded listener on new Standby server.
    3. Correct tnsnames.ora files.
    4. Correct duplicate command.
    Please consider closing some of you old answered questions
    Best Regards
    mseberg
    Edited by: mseberg on May 10, 2012 7:06 AM

  • ORA-12709: error while loading create database character set

    I installed Oracle 8.05 on Linux successfully: was able to login
    whith SQLPlus, start and stop the db whith svrmgrl etc.
    During this install I chose WE8ISO8859P9 as the database
    characterset when prompted.
    After that I installed Oracle Application Server 3.02, and now
    I'm getting the
    ORA-12709: error while loading create database character set
    message when I try to start up the database, and the database
    won't mount.
    Platform is RedHat Linux 5.2.
    NLS_LANG set to different settings,
    e.g. AMERICAN_AMERICA.WE8ISO8859P9
    but without success.
    Anyone any clue?
    Thanks!
    null

    Jogchum Reitsma (guest) wrote:
    : I installed Oracle 8.05 on Linux successfully: was able to
    login
    : whith SQLPlus, start and stop the db whith svrmgrl etc.
    : During this install I chose WE8ISO8859P9 as the database
    : characterset when prompted.
    : After that I installed Oracle Application Server 3.02, and now
    : I'm getting the
    : ORA-12709: error while loading create database character set
    : message when I try to start up the database, and the database
    : won't mount.
    : Platform is RedHat Linux 5.2.
    : NLS_LANG set to different settings,
    : e.g. AMERICAN_AMERICA.WE8ISO8859P9
    : but without success.
    : Anyone any clue?
    : Thanks!
    You can create the database with WE8DEC character set
    and to use the WE8ISO8859P9 on the client or even on Linux.
    The NLS_LANG setting doesn't effect the database, but the
    interface with the database. The same setting can be used in de
    windows 95/98/NT registry.
    null

  • ORA-12709: error while loading create database character set after upgrade

    Dear All
    i m getting ORA-12709: error while loading create database character set, After upgraded the database from 10.2.0.3 to 11.2.0.3 in ebusiness suit env.
    current application version 12.0.6
    please help me to resolve it.
    SQL> startup;
    ORACLE instance started.
    Total System Global Area 1.2831E+10 bytes
    Fixed Size 2171296 bytes
    Variable Size 2650807904 bytes
    Database Buffers 1.0133E+10 bytes
    Redo Buffers 44785664 bytes
    ORA-12709: error while loading create database character set
    -bash-3.00$ echo $ORA_NLS10
    /u01/oracle/PROD/db/teche_st/11.2.0/nls/data/9idata
    export ORACLE_BASE=/u01/oracle
    export ORACLE_HOME=/u01/oracle/PROD/db/tech_st/11.2.0
    export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH
    export PERL5LIB=$ORACLE_HOME/perl/lib/5.10.0:$ORACLE_HOME/perl/site_perl/5.10.0
    export ORA_NLS10=/u01/oracle/PROD/db/teche_st/11.2.0/nls/data/9idata
    export ORACLE_SID=PROD
    -bash-3.00$ pwd
    /u01/oracle/PROD/db/tech_st/11.2.0/nls/data/9idata
    -bash-3.00$ ls -lh |more
    total 56912
    -rw-r--r-- 1 oracle oinstall 951 Jan 15 16:05 lx00001.nlb
    -rw-r--r-- 1 oracle oinstall 957 Jan 15 16:05 lx00002.nlb
    -rw-r--r-- 1 oracle oinstall 959 Jan 15 16:05 lx00003.nlb
    -rw-r--r-- 1 oracle oinstall 984 Jan 15 16:05 lx00004.nlb
    -rw-r--r-- 1 oracle oinstall 968 Jan 15 16:05 lx00005.nlb
    -rw-r--r-- 1 oracle oinstall 962 Jan 15 16:05 lx00006.nlb
    -rw-r--r-- 1 oracle oinstall 960 Jan 15 16:05 lx00007.nlb
    -rw-r--r-- 1 oracle oinstall 950 Jan 15 16:05 lx00008.nlb
    -rw-r--r-- 1 oracle oinstall 940 Jan 15 16:05 lx00009.nlb
    -rw-r--r-- 1 oracle oinstall 939 Jan 15 16:05 lx0000a.nlb
    -rw-r--r-- 1 oracle oinstall 1006 Jan 15 16:05 lx0000b.nlb
    -rw-r--r-- 1 oracle oinstall 1008 Jan 15 16:05 lx0000c.nlb
    -rw-r--r-- 1 oracle oinstall 998 Jan 15 16:05 lx0000d.nlb
    -rw-r--r-- 1 oracle oinstall 1005 Jan 15 16:05 lx0000e.nlb
    -rw-r--r-- 1 oracle oinstall 926 Jan 15 16:05 lx0000f.nlb
    -rw-r--r-- 1 oracle oinstall 1.0K Jan 15 16:05 lx00010.nlb
    -rw-r--r-- 1 oracle oinstall 958 Jan 15 16:05 lx00011.nlb
    -rw-r--r-- 1 oracle oinstall 956 Jan 15 16:05 lx00012.nlb
    -rw-r--r-- 1 oracle oinstall 1005 Jan 15 16:05 lx00013.nlb
    -rw-r--r-- 1 oracle oinstall 970 Jan 15 16:05 lx00014.nlb
    -rw-r--r-- 1 oracle oinstall 950 Jan 15 16:05 lx00015.nlb
    -rw-r--r-- 1 oracle oinstall 1.0K Jan 15 16:05 lx00016.nlb
    -rw-r--r-- 1 oracle oinstall 957 Jan 15 16:05 lx00017.nlb
    -rw-r--r-- 1 oracle oinstall 932 Jan 15 16:05 lx00018.nlb
    -rw-r--r-- 1 oracle oinstall 932 Jan 15 16:05 lx00019.nlb
    -rw-r--r-- 1 oracle oinstall 951 Jan 15 16:05 lx0001a.nlb
    -rw-r--r-- 1 oracle oinstall 944 Jan 15 16:05 lx0001b.nlb
    -rw-r--r-- 1 oracle oinstall 953 Jan 15 16:05 lx0001c.nlb
    Starting up:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options.
    ORACLE_HOME = /u01/oracle/PROD/db/tech_st/11.2.0
    System name: SunOS
    Node name: proddb3.zakathouse.org
    Release: 5.10
    Version: Generic_147440-19
    Machine: sun4u
    Using parameter settings in server-side spfile /u01/oracle/PROD/db/tech_st/11.2.0/dbs/spfilePROD.ora
    System parameters with non-default values:
    processes = 200
    sessions = 400
    timed_statistics = TRUE
    event = ""
    shared_pool_size = 416M
    shared_pool_reserved_size= 40M
    nls_language = "american"
    nls_territory = "america"
    nls_sort = "binary"
    nls_date_format = "DD-MON-RR"
    nls_numeric_characters = ".,"
    nls_comp = "binary"
    nls_length_semantics = "BYTE"
    memory_target = 11G
    memory_max_target = 12G
    control_files = "/u01/oracle/PROD/db/apps_st/data/cntrl01.dbf"
    control_files = "/u01/oracle/PROD/db/tech_st/10.2.0/dbs/cntrl02.dbf"
    control_files = "/u01/oracle/PROD/db/apps_st/data/cntrl03.dbf"
    db_block_checksum = "TRUE"
    db_block_size = 8192
    compatible = "11.2.0.0.0"
    log_archive_dest_1 = "LOCATION=/u01/oracle/PROD/db/apps_st/data/archive"
    log_archive_format = "%t_%s_%r.dbf"
    log_buffer = 14278656
    log_checkpoint_interval = 100000
    log_checkpoint_timeout = 1200
    db_files = 512
    db_file_multiblock_read_count= 8
    db_recovery_file_dest = "/u01/oracle/fast_recovery_area"
    db_recovery_file_dest_size= 14726M
    log_checkpoints_to_alert = TRUE
    dml_locks = 10000
    undo_management = "AUTO"
    undo_tablespace = "APPS_UNDOTS1"
    db_block_checking = "FALSE"
    session_cached_cursors = 500
    utl_file_dir = "/usr/tmp"
    utl_file_dir = "/usr/tmp"
    utl_file_dir = "/u01/oracle/PROD/db/tech_st/10.2.0/appsutil/outbound"
    utl_file_dir = "/u01/oracle/PROD/db/tech_st/10.2.0/appsutil/outbound/PROD_proddb3"
    utl_file_dir = "/usr/tmp"
    plsql_code_type = "INTERPRETED"
    plsql_optimize_level = 2
    job_queue_processes = 2
    cursor_sharing = "EXACT"
    parallel_min_servers = 0
    parallel_max_servers = 8
    core_dump_dest = "/u01/oracle/PROD/db/tech_st/10.2.0/admin/PROD_proddb3/cdump"
    audit_file_dest = "/u01/oracle/admin/PROD/adump"
    db_name = "PROD"
    open_cursors = 600
    pga_aggregate_target = 1G
    workarea_size_policy = "AUTO"
    optimizer_secure_view_merging= FALSE
    aq_tm_processes = 1
    olap_page_pool_size = 4M
    diagnostic_dest = "/u01/oracle"
    max_dump_file_size = "20480"
    Tue Jan 15 16:16:02 2013
    PMON started with pid=2, OS id=18608
    Tue Jan 15 16:16:02 2013
    PSP0 started with pid=3, OS id=18610
    Tue Jan 15 16:16:03 2013
    VKTM started with pid=4, OS id=18612 at elevated priority
    VKTM running at (10)millisec precision with DBRM quantum (100)ms
    Tue Jan 15 16:16:03 2013
    GEN0 started with pid=5, OS id=18616
    Tue Jan 15 16:16:03 2013
    DIAG started with pid=6, OS id=18618
    Tue Jan 15 16:16:03 2013
    DBRM started with pid=7, OS id=18620
    Tue Jan 15 16:16:03 2013
    DIA0 started with pid=8, OS id=18622
    Tue Jan 15 16:16:03 2013
    MMAN started with pid=9, OS id=18624
    Tue Jan 15 16:16:03 2013
    DBW0 started with pid=10, OS id=18626
    Tue Jan 15 16:16:03 2013
    LGWR started with pid=11, OS id=18628
    Tue Jan 15 16:16:03 2013
    CKPT started with pid=12, OS id=18630
    Tue Jan 15 16:16:03 2013
    SMON started with pid=13, OS id=18632
    Tue Jan 15 16:16:04 2013
    RECO started with pid=14, OS id=18634
    Tue Jan 15 16:16:04 2013
    MMON started with pid=15, OS id=18636
    Tue Jan 15 16:16:04 2013
    MMNL started with pid=16, OS id=18638
    DISM started, OS id=18640
    ORACLE_BASE from environment = /u01/oracle
    Tue Jan 15 16:16:08 2013
    ALTER DATABASE MOUNT
    ORA-12709 signalled during: ALTER DATABASE MOUNT...

    ORA-12709 signalled during: ALTER DATABASE MOUNT...Do you have any trace files generated at the time you get this error?
    Please see these docs.
    ORA-12709: WHILE STARTING THE DATABASE [ID 1076156.6]
    Upgrading from 9i to 10gR2 Fails With ORA-12709 : Error While Loading Create Database Character Set [ID 732861.1]
    Ora-12709 While Trying To Start The Database [ID 311035.1]
    ORA-12709 when Mounting the Database [ID 160478.1]
    How to Move From One Database Character Set to Another at the Database Level [ID 1059300.6]
    Thanks,
    Hussein

  • Error while loading create database charecter set

    Hello,
    I have completed instalation Oracle 9iV2 on Redhat 7.3 without any problems.
    After I reboot the system, and try to start database, I have got error mesage:
    ORA-12709: error while loading create database character set
    Could anyone help?
    Thanks

    ORA-12709 error while loading create database character set
    Cause: This is an internal error.
    Action: Contact Oracle Support Services.

  • Error while opening the database.--urgent---pls help...

    Hi,
    Got the below error while opening the database.
    Database version is :10.1.0.4.0
    database is in noarchive log mode.
    the database is coming in to no-mount state and mount state quite easily but not able to open the database.
    Got the below error while opening the database.
    ORA-00600: internal error code, arguments: [4194], [37], [31], [], [], [], [], []
    ORA-00600: internal error code, arguments: [4194], [37], [31], [], [], [], [], []
    Mon Sep 29 15:32:39 2008
    Errors in file /xxx/udump/aaa_ora_18737.trc:
    ORA-00600: internal error code, arguments: [4194], [37], [31], [], [], [], [], []
    ORA-00600: internal error code, arguments: [4194], [37], [31], [], [], [], [], []
    Mon Sep 29 15:32:41 2008
    DEBUG: Replaying xcb 0xc0000000350c1c18, pmd 0xc0000000353b21f0 for failed op 8
    Doing block recovery for file 2 block 9483
    No block recovery was needed.
    on Sep 29 15:34:01 2008
    Errors in file /xxx/udump/aaa/bdump/aaa_pmon_18723.trc:
    ORA-00600: internal error code, arguments: [4194], [37], [31], [], [], [], [], []
    Mon Sep 29 15:34:04 2008
    Errors in file /xxx/udump/aaa/bdump/aaa_pmon_18723.trc:
    ORA-00600: internal error code, arguments: [4194], [37], [31], [], [], [], [], []
    PMON: terminating instance due to error 472
    Instance terminated by PMON, pid = 18723
    Please help me....................

    Hi..
    This ORA-600 refers to a mismatch has been detected between Redo records and rollback (Undo) records.Is better to lock a call with oracle support.Secondly, apply latest patch on the DB.
    I had expereiced the same error, but my DB was in open mode, so i created a new undo tablespace and changed the undo_tablespace parameter and it worked.
    Anand

  • Error while Registering the Database with Catalog..

    I m creating recovery catalog in same database, and getting the errors.
    1. I have created TOOLS tablespace
    2.CREATE USER RMAN2
    SQL> CREATE USER rman IDENTIFIED BY cat
    2 TEMPORARY TABLESPACE temp
    3 DEFAULT TABLESPACE tools
    4 QUOTA UNLIMITED ON tools;
    CREATE USER rman IDENTIFIED BY cat
    ERROR at line 1:
    ORA-01920: user name 'RMAN' conflicts with another user or role name
    SQL> ed
    Wrote file afiedt.buf
    1 CREATE USER rman2 IDENTIFIED BY cat
    2 TEMPORARY TABLESPACE temp
    3 DEFAULT TABLESPACE tools
    4* QUOTA UNLIMITED ON tools
    SQL> /
    User created.
    3. GRANT RECOVERY_CATALOG_OWNER
    SQL> GRANT RECOVERY_CATALOG_OWNER TO rman2;
    Grant succeeded.
    4. To create the recovery catalog:
    1. Connect to the database that will contain the catalog as the catalog owner.
    H:\>rman catalog rman2/cat@rock
    Recovery Manager: Release 10.2.0.1.0 - Production on Fri Sep 5 10:45:52 2008
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to recovery catalog database
    2. Run the CREATE CATALOG command to create the catalog.
    RMAN> CREATE CATALOG;
    recovery catalog created
    3. Optionally, start SQL*Plus and query the recovery catalog to see which tables were created:
    H:\>sqlplus
    SQL*Plus: Release 10.2.0.1.0 - Production on Fri Sep 5 11:53:36 2008
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Enter user-name: rman2/cat
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> select count(*) from cat;
    COUNT(*)
    91
    SQL> ed
    Wrote file afiedt.buf
    1 select owner, table_name, tablespace_name
    2 from dba_tables
    3* where table_name='DB'
    SQL> /
    OWNER TABLE_NAME
    TABLESPACE_NAME
    RMAN2 DB
    TOOLS
    RMAN DB
    ABAMCO_TEST
    Next step is to registering the Database in the Recovery Catalog.
    Registering a Database in the Recovery Catalog
    H:\>rman TARGET / CATALOG rman2/cat@rock
    Recovery Manager: Release 10.2.0.1.0 - Production on Fri Sep 5 11:56:09 2008
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04005: error from target database:
    ORA-01031: insufficient privileges
    I m getting above error while registering the Database with Catalog,
    Can anybody help me how can I register the Database with Catalog.????
    Waiting for Reply!!!!!!!

    Dear Manoj I can log in at TARGET Database.
    H:\>rman
    Recovery Manager: Release 10.2.0.1.0 - Production on Fri Sep 5 12:41:59 2008
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    RMAN> connect target sys/rock
    connected to target database: ROCK (DBID=3255117147)
    RMAN>
    ============================================================
    USING CONNECT STRING as you said.
    H:\>rman target "sys/rock@rock as sysdba" catalog rman2/cat@rock
    Argument Value Description
    target quoted-string connect-string for target database
    catalog quoted-string connect-string for recovery catalog
    nocatalog none if specified, then no recovery catalog
    cmdfile quoted-string name of input command file
    log quoted-string name of output message log file
    trace quoted-string name of output debugging message log file
    append none if specified, log is opened in append mode
    debug optional-args activate debugging
    msgno none show RMAN-nnnn prefix for all messages
    send quoted-string send a command to the media manager
    pipe string building block for pipe names
    timeout integer number of seconds to wait for pipe input
    checksyntax none check the command file for syntax errors
    Both single and double quotes (' or ") are accepted for a quoted-string.
    Quotes are not required unless the string contains embedded white-space.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00552: syntax error in command line arguments
    RMAN-01009: syntax error: found "as": expecting one of: "append, at, auxiliary, catalog, cmdfile, clone, checksyntax, debug, log, msglog, mask, msgno, nocatalog, pipe, rcvcat, script, slaxdebug, send, target, timeout, trace"
    RMAN-01007: at line 0 column 16 file: command line arguments
    H:\>rman
    It didnt work either.
    I have only one database rock, and created recovery catalog in it. I want to register rock database with recovery catalog.

  • Error when making a database call froman ejb

    Hello,
    I am getting the following error when accessing the database from an ejb -
    java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
         java.rmi.RemoteException
         at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.mapSystemException(ShutdownUtilDelegate.java:68)
         at javax.rmi.CORBA.Util.mapSystemException(Util.java:65)
         at com.ejb._EULookupRemoteIF_Stub.fetchAllLookups(Unknown Source)
         at com.ejb._EULookupRemoteIF_Stub.fetchAllLookups(Unknown Source)
         at com.servlets.login.EUClsLoginServlet.doPost(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
         at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
         at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
         at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:157)
         at com.iplanet.ias.web.WebContainer.service(WebContainer.java:598)
    Caused by: java.rmi.RemoteException
         at com.sun.enterprise.iiop.POAProtocolMgr.mapException(POAProtocolMgr.java:451)
         at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:545)
         at com.ejb.EUClsLookupBean_EJBObjectImpl.fetchAllLookups(EUClsLookupBean_EJBObjectImpl.java:101)
         at com.ejb._EUClsLookupBean_EJBObjectImpl_Tie._invoke(Unknown Source)
         at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:569)
         at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:211)
         at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:113)
         at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:275)
         at com.sun.corba.ee.internal.iiop.LocalClientRequestImpl.invoke(LocalClientRequestImpl.java:96)
         at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(ClientDelegate.java:237)
         at com.sun.corba.ee.internal.POA.GenericPOAClientSC.invoke(GenericPOAClientSC.java:97)
         at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
         at com.ejb._EULookupRemoteIF_Stub.fetchAllLookups(Unknown Source)
         ... 16 more
    Any help?

    Please look in those 16 other stack traces for more details, there should be an actual SQLException if
    it's a database problem, and/or the actual bean method that caused the problem.
    Regards,
    Marina

  • Error while connecting MYSQL Database

    Hi,
    I use a 30 days trial of Crystal Reports 2008. When i try to connect with the database i always get the next error: [http://www.visiscan.nl/error.jpg]
    The database is 4.1GB large and there is 10GB free space on the database.
    Anybody can tell me what to do?

    Hi Tom,
    As I understand the error while connecting to database is
    u201CFailed to retrieve data from databaseu201D
    There could be some could be multiple reasons for this.
    If you are using an ODBC connection then try to check the DSN. Recreate the same and then try.
    If the database is oracle check if native client is installed and try to ping from the native client to check if it responds.
    When connecting to Oracle, ensure that the Service name is identical to that used in the <ORA_HOME>/network/admin/tnsnames.ora file on the BusinessObjects XI Release 2 server.
    For ODBC databases, ensure that the ODBC DSN is exactly the same in the ODBC Manager as on the BusinessObjects XI Release 2 server.
    Please let us know if this helps
    Regards,
    Aditya Joshi

  • Error while starting the Database

    Hi,
    I am getting the following error while starting the Database instance.
    ORA-03113: end-of-file on communication channel.
    How to fix this issue? i tried some of the options mentioned in docs in metalink. But still i am not able to fix.
    Anypointers on this is appreciated.
    Thanks & Regards,
    Srikanth

    Can you paste lines from alertlog file..

  • Error message while creating database

    Log error
    while creating new database
    Robot-properties
    XML Parsing Error: junk after document element
    Location: http://portalserver/psconsole/faces/search/RobotPropertiesHome.jsp
    Line Number 18, Column 1:<body id="_id3" onload="return _id3_jsObject
    I have created my new search engine .
    and the robot is not running.I getting log error.
    and no directory is created with the search name.
    please help me with the fields..
    creating search server..
    required Port:
    required Configuration Name:
    Required Instance:
    *Web Container Administration*
    Required Administration Host:
    Required Administration Port:
    Required Administrator:
    Required Administration Password:
    *Web Container Directories*
    Required Install Directory:
    Required Instance Directory:
    Required Document Root Directory:

    Kriti Sundar Mazumder wrote:
    Hi
    I am getting an following error message, while creating database connection pool
    in weblogic 7.
    "<Jun 18, 2004 4:52:36 AM CDT> <Error> <JDBC> <001060> <Cannot startup connection
    pool "MyJDBCConnectionPool" java.sql.SQLException: [IBM][JDBC Driver] CLI0647E
    Error allocating DB2 environment handle, rc=-1.>"
    Can anyone help me out in this regard
    Regards
    KritiHi. I am no expert, but it sounds like a problem with the privileges the user
    has... The best thing is to step back to a simpler environment. Can you try
    connecting to DB2 with a simple program like utils.dbping? Please look at our
    driver docs for the DB2 driver, because there are several variations in connect
    properties depending on the type of DB2 you are connecting to...
    Joe

Maybe you are looking for