ORA-00235: controlfile fixed table inconsistent due to concurrent update

Hi,
While our system is loading lot of data, we are getting failures during level 0 RMAN backup with following error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 07/16/2004 00:10:35
ORA-00235: controlfile fixed table inconsistent due to concurrent update
Per Oracle rep suggestions, we have already increased our redo log files (we have 12 groups with 1 file each) to 1GB each file. THe log_checkpoint_interval is also set to 87382. (OS block size 4k)
This is on Oracle 9.2.0.5 system on Windows 2000 AS clustered system.
During normal loading operation per statspack report the redo size is 1-2.5MB/second. This may be causing checkpoints every second.
Any suggestions to reduce contention of control file during RMAN level 0 backups?
Thanks
Satish

One of the major guideline to adapt the best possible your database when RMAN is used is to configure the database as a Shared Server.
Your database is working as a Shared or Dedicated Server ?
Joel Pérez
http://otn.oracle.com/experts

Similar Messages

  • ERROR: could not serialize access due to concurrent update

    Hi.
    I use ejb+glassfish+postgres in my project.
    The project is a web application for finansial data transfering.
    I have three DBs, long global transactions, serializable isolation level, container-managed transaction.
    When i test the project with concurent threads, i get an exception: "ERROR: could not serialize access due to
    concurrent update"
    I read that when you get suck kind of error, your program must rollback current transaction and then reply this transaction.
    what do i need to do to complete this transaction? :
    1) rollback and reply transaction
    2) maybe, the are other ways to reply transaction (for example: glassfish configurations, ....)
    Edited by: 856539 on 04.05.2011 8:10

    If your DAO is nicely separated from your service layer as it should be then the solution I suggested above works and doesn't require you to change many classes because you can catch the expection in the DAO layer and do the retry in the DAO layer. That's where the solution belongs too because it's only applicable for your current database solution (Postgres). i.e If you change your database solution you need to change your DAO anyway, but only your DAO. If you put the solution in your service layer (or client layer) then you need to change those layers when you change your database solution which defeats the purpose of the separation.
    If you still want the interceptor approach, you need to check if the transaction has been marked for rollback back, then you need to join the transaction with EM.join and from there you attempt to close and discard the joined transaction before starting another one to invoke the retry operation on. Bear in mind that you only do the rety when the transaction was marked for roll back because of that specific exception. Needless to say that this doesn't seem to be a clean way to handle your transactions (if you can get it to work that is).

  • PGError: ERROR: could not serialise access due to concurrent update profile - profile manager 2

    trying to push free apps to devices using profile manager 2 - apps install fine but then need an apple id to run. wierd thing is it was working this morning but not now and i dont know whats changed!

    If your DAO is nicely separated from your service layer as it should be then the solution I suggested above works and doesn't require you to change many classes because you can catch the expection in the DAO layer and do the retry in the DAO layer. That's where the solution belongs too because it's only applicable for your current database solution (Postgres). i.e If you change your database solution you need to change your DAO anyway, but only your DAO. If you put the solution in your service layer (or client layer) then you need to change those layers when you change your database solution which defeats the purpose of the separation.
    If you still want the interceptor approach, you need to check if the transaction has been marked for rollback back, then you need to join the transaction with EM.join and from there you attempt to close and discard the joined transaction before starting another one to invoke the retry operation on. Bear in mind that you only do the rety when the transaction was marked for roll back because of that specific exception. Needless to say that this doesn't seem to be a clean way to handle your transactions (if you can get it to work that is).

  • ORA-00235 Standby Database Controlfile problem

    Dear fellow dbas,
    I am just starting to become acquainted with high availability and have to solve following problem.
    We have a RAC database with a standby database that is out of sync. In fact the standby database is running in async mode but archived redo logs are not applied.
    They are successfully forwarded from the primary instance to the standby db though. Looking at the alert.log I discovered an ORA-00235 error - control file fixed table inconsistent due to concurrent update.
    As a result of this I have a huge gap between the primary and standby database.
    Can you please give me a step to step tutorial, how I can resolve this issue?
    Any help is appreciated!
    Many thanks,
    Sebastian

    Hello Anand,
    I am using 11.1.0.7.0.
    My standby database is a cluster database as well. I shut both instances down using srvctl and created a standby controlfile from my primary instance, which I copied to the respective locations referred to in the spfile of my dataguard database. Afterwards I started up and issued a ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
    The database does not open and the alert.log states ORA-01124 "cannot recover datafile 1 - file is in use or recovery".
    Next, the background media recovery process was shut down.
    What should I do, to get my standby back running?
    Should I place the primary database in backup mode and copy the datafiles to my standby db?
    Afterwards I would create a standby controlfile again and overwrite the standby ones.
    Maybe you assist in pointing at the next steps.
    Many thanks,
    Sebastian

  • Ora-01219 database not open; only queries on fixed tables and views.

    Hi everyone
    There is another post stating this error, but since the source is different, I think is okay to make a different post as well.
    Our database was working fine until the other day, when suddenly power went off, UPS was damaged and didn't hold, and when we restarted the database this is what happens:
    Using Enterprise Manager Console, we can make a succesful connection in the same machine, but if we choose Schema, the following error appears:
    ora-01219 database not open; only queries on fixed tables and views.
    When accesing from a different machine:
    ORA-01033: ORACLE initialization or shutdown in progress
    Thanks in advance

    Here is the last entries of alert log
    Fatal NI connect error 12638, connecting to:
    (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
    VERSION INFORMATION:
         TNS for 32-bit Windows: Version 11.1.0.7.0 - Production
         Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 11.1.0.7.0 - Production
    Time: 20-JUL-2010 15:48:31
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12638
    TNS-12638: Fallo de recuperación de credenciales
    ns secondary err code: 0
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
    Tue Jul 20 15:50:50 2010
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 11.1.0.7.0.
    Using parameter settings in server-side spfile E:\ORACLE\CRIMINALISTICA\PRODUCT\11.1.0\DB_1\DATABASE\SPFILECRIM.ORA
    System parameters with non-default values:
    processes = 150
    memory_target = 816M
    control_files = "E:\ORACLE\ORADATA\CRIM\CONTROL01.CTL"
    control_files = "E:\ORACLE\ORADATA\CRIM\CONTROL02.CTL"
    control_files = "E:\ORACLE\ORADATA\CRIM\CONTROL03.CTL"
    db_block_size = 8192
    compatible = "11.1.0.0.0"
    db_recovery_file_dest = "E:\Oracle\flash_recovery_area"
    db_recovery_file_dest_size= 2G
    undo_tablespace = "UNDOTBS1"
    remote_login_passwordfile= "EXCLUSIVE"
    db_domain = ""
    dispatchers = "(PROTOCOL=TCP) (SERVICE=CRIMXDB)"
    audit_file_dest = "E:\ORACLE\ADMIN\CRIM\ADUMP"
    audit_trail = "DB"
    db_name = "CRIM"
    open_cursors = 300
    diagnostic_dest = "E:\ORACLE"
    Tue Jul 20 15:50:55 2010
    PMON started with pid=2, OS id=1688
    Tue Jul 20 15:50:55 2010
    VKTM started with pid=3, OS id=2236 at elevated priority
    Tue Jul 20 15:50:55 2010
    DIAG started with pid=4, OS id=2332
    Tue Jul 20 15:50:55 2010
    DBRM started with pid=5, OS id=2328
    Tue Jul 20 15:50:55 2010
    PSP0 started with pid=6, OS id=2432
    VKTM running at (20)ms precision
    Tue Jul 20 15:50:55 2010
    DIA0 started with pid=7, OS id=2160
    Tue Jul 20 15:50:55 2010
    MMAN started with pid=8, OS id=2156
    Tue Jul 20 15:50:55 2010
    DBW0 started with pid=9, OS id=2064
    Tue Jul 20 15:50:55 2010
    LGWR started with pid=10, OS id=3176
    Tue Jul 20 15:50:55 2010
    CKPT started with pid=11, OS id=3180
    Tue Jul 20 15:50:55 2010
    SMON started with pid=12, OS id=3184
    Tue Jul 20 15:50:55 2010
    RECO started with pid=13, OS id=3188
    Tue Jul 20 15:50:55 2010
    MMON started with pid=14, OS id=3192
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    starting up 1 shared server(s) ...
    ORACLE_BASE from environment = E:\Oracle
    Tue Jul 20 15:50:55 2010
    MMNL started with pid=15, OS id=3196
    Tue Jul 20 15:50:56 2010
    alter database mount exclusive
    Setting recovery target incarnation to 2
    Successful mount of redo thread 1, with mount id 1304879008
    Database mounted in Exclusive Mode
    Lost write protection disabled
    Completed: alter database mount exclusive
    alter database open
    Errors in file e:\oracle\diag\rdbms\crim\crim\trace\crim_dbw0_2064.trc:
    ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
    ORA-01110: data file 9: 'E:\ORACLE\ORADATA\STOPCRIM5\STOPCRIM5TABLESPACE.ORA'
    ORA-27047: unable to read the header block of file
    OSD-04006: fallo de ReadFile(); no se ha podido leer del archivo
    O/S-Error: (OS 38) Se ha alcanzado el final del archivo.
    Errors in file e:\oracle\diag\rdbms\crim\crim\trace\crim_dbw0_2064.trc:
    ORA-01157: cannot identify/lock data file 16 - see DBWR trace file
    ORA-01110: data file 16: 'E:\ORACLE\ORADATA\PRUEBACARLOS\PRUEBACARLOSTABLESPACE.ORA'
    ORA-27047: unable to read the header block of file
    OSD-04006: fallo de ReadFile(); no se ha podido leer del archivo
    O/S-Error: (OS 38) Se ha alcanzado el final del archivo.
    Errors in file e:\oracle\diag\rdbms\crim\crim\trace\crim_dbw0_2064.trc:
    ORA-01157: cannot identify/lock data file 17 - see DBWR trace file
    ORA-01110: data file 17: 'E:\ORACLE\ORADATA\PRUEBACARLOS\PRUEBACARLOSINDEX.ORA'
    ORA-27047: unable to read the header block of file
    OSD-04006: fallo de ReadFile(); no se ha podido leer del archivo
    O/S-Error: (OS 38) Se ha alcanzado el final del archivo.
    ORA-1157 signalled during: alter database open...
    Tue Jul 20 16:04:39 2010
    db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.

  • ORA-00214: controlfile '

    Hi All
    My machine had a restart and now the database mounts.... doesn't open
    with following error..
    version is Oracle Release 10.1.0.4.2 -
    ORA-00214: controlfile 'K:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\CONTROL02.CTL' version 46509 inconsistent with file
    'K:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\CONTROL01.CTL' version 46507
    Thanks in advance
    Srisankar

    Here is the fix from Metalink note 1014751.6.
    https://metalink2.oracle.com/metalink/plsql/f?p=130:14:7463074268617192659::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,1014751.6,1,1,1,helvetica
    fix:
    The solution consists in opening the database with a single good copy
    of the control file and then shutting the database down and copying
    that version of the control file onto the other mirrored copies.
    That will cause the next startup to succeed. The steps to be followed
    are:
    1. If the database is still up, do a shutdown abort now.
    2. Edit the init.ora file for this instance (or config.ora in an ifile
    configuration).
    Find the CONTROL_FILES parameter and modify it to include
    just ONE copy of the control file that you have reasons to
    believe is up-to-date. For example, if you only have two
    mirrored copies X and Y of the control file:
    CONTROL_FILES = (X, Y)
    and you know you have accidentally overwritten X with an old
    copy, make
    CONTROL_FILES = (Y)
    If you are not sure about it, choose any one of the control file
    copies and remove or comment out all the other copies from the
    CONTROL_FILES parameter.
    3. Start up the database in restricted mode.
    STARTUP RESTRICT
    If the database comes up fine, move on to Step 4.
    If instead you get ORA-1122, ORA-1110, and ORA-1207, go back to
    Step 2 and make the CONTROL_FILES parameter point to another one
    of the mirrored copies. If you have already tried each and
    every one of the mirrored copies unsuccessfully, you must create
    a new control file for the database. See the Solution Reference
    to PR entry 1012929.6 ("How to Recreate the Control File").
    If you get ORA-1113 and ORA-1110 pointing to one of the datafiles,
    it means the copy of the control file you picked is good, but
    the referenced datafile must be recovered before the database can be
    opened. Try issuing a RECOVER DATABASE command and applying the
    logs you are prompted for. You may have to resort to the online
    logs to complete media recovery. For further details, see the
    Solution Reference to PR entry 1012943.6 on ORA-1113. Once the
    datafile is recovered, issue an ALTER DATABASE OPEN.
    4. Shut the database down (normal or immediate).
    5. Make all copies of the control file consistent.
    Copy the good mirrored copy of the control file that you just used
    to bring the database up onto all other copies, as originally listed
    in the CONTROL_FILES parameter of your init.ora file (or config.ora
    in an ifile configuration).
    6. Restore the CONTROL_FILES parameter to its original value.
    Edit the init.ora file for this instance (or config.ora in an ifile
    configuration) to make the CONTROL_FILES parameter include
    all mirrored copies of the control file again.
    7. Start up the database.

  • Customise table inconsistency between ABAP Dictionary and the databas

    Hi all,
    I have encountered a problem where by, I was not able to activate a table due to inconsistency between ABAP Dictionary and the database.
    After I run the SE14--> Check Database object. It has show that there is a missing Unique Index(Primary Index) at the Database Level, but at ABAP Dictionary it is there.
    I have try to recreate the primary index at the Database level, but failed. Because one of the primary key field is been dropped from this table.
    So now, may I know how can I still make this table Active again?
    Is it save to folllow the following solution that I found on internet?
    Syntax error in SDCC, table inconsistency between ABAP Dictionary and the database, transport error 8 during the generation of ABAP Dictionary. When you call Transaction SDCC, a termination occurs due to a putative syntax error because a table is not known or active. When you check this with the ABAP dictionary (SE11), you notice, that the table is active or inactive, however it is not possible to activate it. The activation might terminate with the error message 'Inconsistency between ABAP Dictionary and database'. A check of the affected object also delivers this error.
    Solution
    Proceed as follows:
    Log on as user DDIC
    Call Transaction SE14
    Enter the affected table name and
    select EDIT
    In the following screen, choose Table -> Reconstruct
    Confirm the execution
    Call Transaction SE11
    Enter the affected table name
    Display
    Activate
    Thanks.
    CK

    I managed to solved this by
    Solution
    Proceed as follows:
    Log on as user DDIC
    Call Transaction SE14
    Enter the affected table name and
    select EDIT
    In the following screen, choose Table -> Reconstruct
    Confirm the execution
    Call Transaction SE11
    Enter the affected table name
    Display
    Activate
    Thanks.
    CK

  • ORA-19612: datafile 0 not restored due to missing data

    Hello,
    I'm testing a restore of the controlfile. The database is in archivelog mode and autobackup is set to ON. I successfully did a full backup and backup as copy database.
    To test I did the following:
    - note the DBID
    - shutdown the database
    - renamed both controlfiles:
    $ mv /u02/rcat/control01.ctl /u02/rcat/control01.ctl_old
    $ mv /u02/fra/rcat/control02.ctl /u02/fra/rcat/control02.ctl_old
    When I try to restore the controlfile form autobackup I receive the following error. What could be reason please?
    [rcat@oel54]$ rman target /
    Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 10 00:07:41 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: RCAT (not mounted)
    RMAN> set dbid 502889862;
    executing command: SET DBID
    RMAN> restore controlfile from autobackup;
    Starting restore at 10-DEC-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=19 device type=DISK
    recovery area destination: /u02/fra
    database name (or database unique name) used for search: RCAT
    channel ORA_DISK_1: AUTOBACKUP /u02/fra/RCAT/autobackup/2010_12_09/o1_mf_s_737336682_6j2pyv2l_.bkp found in the recovery area
    channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101210
    channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101209
    channel ORA_DISK_1: restoring control file from AUTOBACKUP /u02/fra/RCAT/autobackup/2010_12_09/o1_mf_s_737336682_6j2pyv2l_.bkp
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 12/10/2010 00:09:55
    ORA-19870: error while restoring backup piece /u02/fra/RCAT/autobackup/2010_12_09/o1_mf_s_737336682_6j2pyv2l_.bkp
    ORA-19612: datafile 0 not restored due to missing data
    $ ll /u02/fra/RCAT/autobackup/2010_12_09/o1_mf_s_737336682_6j2pyv2l_.bkp
    -rw-r----- 1 oracle dba 10354688 Dec  9 23:44 /u02/fra/RCAT/autobackup/2010_12_09/o1_mf_s_737336682_6j2pyv2l_.bkpThanks!

    The file was indeed corrupted as below will show.
    Very strange. Perhaps something with the latest Virtualbox or the SSD/hybrid harddrive. (host MacOSX 10.6, guest Oracle Linux 5.5 UEK)
    $ mv /u02/rcat/control01.ctl_old /u02/rcat/control01.ctl
    $ mv /u02/fra/rcat/control02.ctl_old /u02/fra/rcat/control02.ctl
    SQL> startup mount
    ORACLE instance started.
    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-00264: no recovery required
    SQL> alter database open;
    Database altered.
    $ rman target /
    connected to target database: RCAT (DBID=502889862)
    RMAN> backup current controlfile;
    piece handle=/u02/fra/RCAT/backupset/2010_12_10/o1_mf_ncnnf_TAG20101210T012420_6j2wsoko_.bkp
    Finished backup at 10-DEC-10
    Starting Control File and SPFILE Autobackup at 10-DEC-10
    piece handle=/u02/fra/RCAT/autobackup/2010_12_10/o1_mf_s_737342662_6j2wspvf_.bkp comment=NONE
    Finished Control File and SPFILE Autobackup at 10-DEC-10
    RMAN> restore validate controlfile;
    piece handle=/u02/fra/RCAT/autobackup/2010_12_10/o1_mf_s_737342662_6j2wspvf_.bkp tag=TAG20101210T012422
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: validation complete, elapsed time: 00:00:02
    Finished restore at 10-DEC-10
    SQL> shutdown immediate
    $ mv /u02/rcat/control01.ctl /u02/rcat/control01.ctl_old
    $ mv /u02/fra/rcat/control02.ctl /u02/fra/rcat/control02.ctl_old
    SQL> startup nomount
    $ rman target /
    connected to target database: RCAT (not mounted)
    RMAN> set dbid 502889862;
    RMAN> restore controlfile from autobackup;
    Starting restore at 10-DEC-10
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=19 device type=DISK
    recovery area destination: /u02/fra
    database name (or database unique name) used for search: RCAT
    channel ORA_DISK_1: AUTOBACKUP /u02/fra/RCAT/autobackup/2010_12_10/o1_mf_s_737342662_6j2wspvf_.bkp found in the recovery area
    channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101210
    channel ORA_DISK_1: restoring control file from AUTOBACKUP /u02/fra/RCAT/autobackup/2010_12_10/o1_mf_s_737342662_6j2wspvf_.bkp
    channel ORA_DISK_1: control file restore from AUTOBACKUP complete
    output file name=/u02/rcat/control01.ctl
    output file name=/u02/fra/rcat/control02.ctl
    Finished restore at 10-DEC-10

  • MCOD Installation - Error ORA-1403 when accessing table SAPUSER

    Hello.
    We are in middle of a MCOD installation of 4.7 x 2.00 SR1 with BW 3.1 on Windows 2003/Oracle.
    BW 3.1 is up and running, while 4.7 fails on R3loads.
    Following are SAP000.log and SAPUSER.log files:
    SAP000.log
    ===============================
    D:\usr\sap\D11\SYS\exe\run/R3load.exe: START OF LOG: 20060507193904
    D:\usr\sap\D11\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
    D:\usr\sap\D11\SYS\exe\run/R3load.exe: version R6.40/V1.4
    D:\usr\sap\D11\SYS\exe\run/R3load.exe -dbcodepage 1100 -i D:\Program Files\sapinst_instdir\R3E_472SR1_ABAP_NUC\DB/SAP0000.cmd -l D:\Program Files\sapinst_instdir\R3E_472SR1_ABAP_NUC\DB/SAP0000.log -stop_on_error
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
    (DB) ERROR: DDL statement failed
    (DROP TABLE "REPOLOAD")
    DbSlExecute: rc = 103
      (SQL error 942)
      error message returned by DbSl:
    ORA-00942: table or view does not exist
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    DbSl Trace: ORA-406 occured when executing SQL statement (parse error offset = 0)
    (DB) ERROR: DDL statement failed
    (CREATE TABLE "REPOLOAD" ( "PROGNAME" VARCHAR2(40) DEFAULT ' ' NOT NULL , "R3STATE" VARCHAR2(1) DEFAULT ' ' NOT NULL , "MACH" NUMBER(5) DEFAULT 0 NOT NULL , "UNAM" VARCHAR2(12) DEFAULT ' ' NOT NULL , "UDAT" VARCHAR2(8) DEFAULT '00000000' NOT NULL , "UTIME" VARCHAR2(6) DEFAULT '000000' NOT NULL , "L_DATALG" NUMBER(10) DEFAULT 0 NOT NULL , "Q_DATALG" NUMBER(10) DEFAULT 0 NOT NULL , "SDAT" VARCHAR2(8) DEFAULT '00000000' NOT NULL , "STIME" VARCHAR2(6) DEFAULT '000000' NOT NULL , "MINOR_VERS" NUMBER(5) DEFAULT 0 NOT NULL , "MAJOR_VERS" NUMBER(10) DEFAULT 0 NOT NULL , "LDATA" BLOB , "QDATA" BLOB  ) TABLESPACE PSAPD11620 STORAGE (INITIAL 0000000016K NEXT 0000040960K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
    DbSlExecute: rc = 99
      (SQL error 406)
      error message returned by DbSl:
    ORA-00406: COMPATIBLE parameter needs to be 9.2.0.0.0 or greater
    (DB) INFO: disconnected from DB
    D:\usr\sap\D11\SYS\exe\run/R3load.exe: job finished with 1 error(s)
    D:\usr\sap\D11\SYS\exe\run/R3load.exe: END OF LOG: 20060507193905
    ========================================
    SAPUSER.log
    ==============================
    D:\usr\sap\D11\SYS\exe\run/R3load.exe: START OF LOG: 20060507193834
    D:\usr\sap\D11\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
    D:\usr\sap\D11\SYS\exe\run/R3load.exe: version R6.40/V1.4
    D:\usr\sap\D11\SYS\exe\run/R3load.exe -dbcodepage 1100 -i D:\Program Files\sapinst_instdir\R3E_472SR1_ABAP_NUC\DB/SAPUSER.cmd -l D:\Program Files\sapinst_instdir\R3E_472SR1_ABAP_NUC\DB/SAPUSER.log -stop_on_error
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
    (DB) INFO: disconnected from DB
    D:\usr\sap\D11\SYS\exe\run/R3load.exe: job completed
    D:\usr\sap\D11\SYS\exe\run/R3load.exe: END OF LOG: 20060507193835
    ==============================================
    Kindly look into it.
    Thanks
    KT

    Hi KT,
    Actually the problem is not ORA-1403, but the <i>ORA-00406: COMPATIBLE parameter needs to be 9.2.0.0.0 or greater</i>.
    Please update the COMPATIBLE parameter in your init<SID>.ora file and restart the database. This should fix your problem.
    Kind regards,
    Alexander Webster
    P.S. points are appreciated if my reply was helpfull.
    Message was edited by: Alexander Webster
    Removed typo

  • Trying to run JBoss with Oracle8i - Error: "error while fixing table name"

    I'm trying to configure Jboss_3_2_1 to run with Oracle 8i. I intend to use it to deploy EJB on the Oracle DataSource.
    I have already change the following files:
    oracle-ds.xml -> changed the <connection-url> tag to my configuration
    oracle-xa-ds.xml -> changed the <xa-datasource-property name="URL"> tag
    to my configuration. But I'm not sure how to exactly configure this
    property.
    My first doubt is:
    Using the Oracle 8i, witch of the two config files above I should use to the datasource tag in the jbosscmp-odbc.xml file.
    The second one is:
    Using the XAOracleDS (Oracle 8i) as the <datasource>, and the <datasource-mapping> tag as Oracle8 (as suggested in the jbosscmp-odbc.xml file) I get the following error message from the JBoss server:
    17:12:19,500 INFO [EjbModule] Created
    17:12:19,515 INFO [EjbModule] Starting
    17:12:19,515 INFO [EntityContainer] Starting
    17:12:19,953 ERROR [EntityContainer] Starting failed
    org.jboss.deployment.DeploymentException: Error while fixing table name; - neste
    d throwable: (org.jboss.util.NestedSQLException: Failed to register driver for:
    oracle.jdbc.driver.OracleDriver; - nested throwable: (java.lang.ClassNotFoundExc
    eption: oracle.jdbc.driver.OracleDriver); - nested throwable: (org.jboss.resourc
    e.JBossResourceException: Failed to register driver for: oracle.jdbc.driver.Orac
    leDriver; - nested throwable: (java.lang.ClassNotFoundException: oracle.jdbc.dri
    ver.OracleDriver)))
    at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:68)
    at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.<init>(JDBCEnt
    ityBridge.java:119)
    at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBC
    StoreManager.java:438)
    at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManage
    r.java:372)
    at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManag
    er.java:170)
    at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:339)
    at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
    92)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
    ler.java:966)
    at $Proxy11.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:392)
    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy21.start(Unknown Source)
    at org.jboss.ejb.EjbModule.startService(EjbModule.java:329)
    at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
    92)
    at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
    ler.java:966)
    at $Proxy11.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:392)
    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy19.start(Unknown Source)
    at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:540)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:824)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
    at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy7.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
    tScanner.java:302)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
    canner.java:476)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
    doScan(AbstractDeploymentScanner.java:200)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
    bstractDeploymentScanner.java:273)
    at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
    92)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
    ler.java:966)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:392)
    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy5.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:597)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy6.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:365)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:272)
    at org.jboss.Main.boot(Main.java:150)
    at org.jboss.Main$1.run(Main.java:388)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: org.jboss.util.NestedSQLException: Failed to register driver for: ora
    cle.jdbc.driver.OracleDriver; - nested throwable: (java.lang.ClassNotFoundExcept
    ion: oracle.jdbc.driver.OracleDriver); - nested throwable: (org.jboss.resource.J
    BossResourceException: Failed to register driver for: oracle.jdbc.driver.OracleD
    river; - nested throwable: (java.lang.ClassNotFoundException: oracle.jdbc.driver
    .OracleDriver))
    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(Wrapp
    erDataSource.java:106)
    at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:39)
    ... 90 more
    Caused by: org.jboss.resource.JBossResourceException: Failed to register driver
    for: oracle.jdbc.driver.OracleDriver; - nested throwable: (java.lang.ClassNotFou
    ndException: oracle.jdbc.driver.OracleDriver)
    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.g
    etDriver(LocalManagedConnectionFactory.java:280)
    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.c
    reateManagedConnection(LocalManagedConnectionFactory.java:146)
    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.cr
    eateConnection(InternalManagedConnectionPool.java:352)
    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.ge
    tConnection(InternalManagedConnectionPool.java:151)
    at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePo
    ol.getConnection(JBossManagedConnectionPool.java:643)
    at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManage
    dConnection(BaseConnectionManager2.java:413)
    at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedCo
    nnection(TxConnectionManager.java:331)
    at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateC
    onnection(BaseConnectionManager2.java:488)
    at org.jboss.resource.connectionmanager.BaseConnectionManager2$Connectio
    nManagerProxy.allocateConnection(BaseConnectionManager2.java:798)
    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(Wrapp
    erDataSource.java:102)
    ... 91 more
    Caused by: java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
    at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.g
    etDriver(LocalManagedConnectionFactory.java:262)
    ... 100 more
    17:12:20,671 WARN [ServiceController] Problem starting service jboss.j2ee:jndiN
    ame=ejb/LocalUsuarioEJB,service=EJB
    org.jboss.deployment.DeploymentException: Error while fixing table name; - neste
    d throwable: (org.jboss.util.NestedSQLException: Failed to register driver for:
    oracle.jdbc.driver.OracleDriver; - nested throwable: (java.lang.ClassNotFoundExc
    eption: oracle.jdbc.driver.OracleDriver); - nested throwable: (org.jboss.resourc
    e.JBossResourceException: Failed to register driver for: oracle.jdbc.driver.Orac
    leDriver; - nested throwable: (java.lang.ClassNotFoundException: oracle.jdbc.dri
    ver.OracleDriver)))
    at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:68)
    at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.<init>(JDBCEnt
    ityBridge.java:119)
    at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBC
    StoreManager.java:438)
    at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManage
    r.java:372)
    at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManag
    er.java:170)
    at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:339)
    at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
    92)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
    ler.java:966)
    at $Proxy11.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:392)
    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy21.start(Unknown Source)
    at org.jboss.ejb.EjbModule.startService(EjbModule.java:329)
    at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
    92)
    at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
    ler.java:966)
    at $Proxy11.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:392)
    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy19.start(Unknown Source)
    at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:540)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:824)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
    at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy7.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
    tScanner.java:302)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
    canner.java:476)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
    doScan(AbstractDeploymentScanner.java:200)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
    bstractDeploymentScanner.java:273)
    at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
    92)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
    ler.java:966)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:392)
    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy5.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:597)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
    nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy6.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:365)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:272)
    at org.jboss.Main.boot(Main.java:150)
    at org.jboss.Main$1.run(Main.java:388)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: org.jboss.util.NestedSQLException: Failed to register driver for: ora
    cle.jdbc.driver.OracleDriver; - nested throwable: (java.lang.ClassNotFoundExcept
    ion: oracle.jdbc.driver.OracleDriver); - nested throwable: (org.jboss.resource.J
    BossResourceException: Failed to register driver for: oracle.jdbc.driver.OracleD
    river; - nested throwable: (java.lang.ClassNotFoundException: oracle.jdbc.driver
    .OracleDriver))
    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(Wrapp
    erDataSource.java:106)
    at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:39)
    ... 90 more
    Caused by: org.jboss.resource.JBossResourceException: Failed to register driver
    for: oracle.jdbc.driver.OracleDriver; - nested throwable: (java.lang.ClassNotFou
    ndException: oracle.jdbc.driver.OracleDriver)
    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.g
    etDriver(LocalManagedConnectionFactory.java:280)
    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.c
    reateManagedConnection(LocalManagedConnectionFactory.java:146)
    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.cr
    eateConnection(InternalManagedConnectionPool.java:352)
    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.ge
    tConnection(InternalManagedConnectionPool.java:151)
    at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePo
    ol.getConnection(JBossManagedConnectionPool.java:643)
    at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManage
    dConnection(BaseConnectionManager2.java:413)
    at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedCo
    nnection(TxConnectionManager.java:331)
    at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateC
    onnection(BaseConnectionManager2.java:488)
    at org.jboss.resource.connectionmanager.BaseConnectionManager2$Connectio
    nManagerProxy.allocateConnection(BaseConnectionManager2.java:798)
    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(Wrapp
    erDataSource.java:102)
    ... 91 more
    Caused by: java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
    at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.g
    etDriver(LocalManagedConnectionFactory.java:262)
    ... 100 more
    Can somebody please helpe me to correctly configure these files and put this application to run?

    Copy jca/oracle-ds.xml to deploy dir. Modify oracle-ds.xml configuration file. Set <driver-class>oracle.jdbc.driver.OracleDriver</driver-class> and <connection-url>jdbc:oracle:oci8:@<database></connection-url>
    Modify standardjaws.xml configuration file.
    Set <datasource> and <type-mapping> elements.
    <jaws>
    <datasource>java:/OracleDS</datasource>
    <type-mapping>Oracle8</type-mapping>
    </jaws>
    Modify standardjbosscmp-jdbc.xml configuration file.
    Set the <datasource> and <datasource-mapping> elements.
    <jbosscmp-jdbc>
    <defaults>
    <datasource>java:/OracleDS</datasource>
    <datasource-mapping>Oracle8</datasource-mapping>
    </defaults>
    </jbosscmp-jdbc>
    Modify login-config.xml configuration file with Oracle database settings.
    Add the following <application-policy/> element to login-config.xml.
    <application-policy name = "OracleDbRealm">
    <authentication>
    <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule"
    flag = "required">
    <module-option name = "principal">sa</module-option>
    <module-option name = "userName">sa</module-option>
    <module-option name = "password"></module-option>
    <module-option name ="managedConnectionFactoryName">
    jboss.jca:service=LocalTxCM,name=OracleDS
    </module-option>
    </login-module>
    </authentication>
    </application-policy>

  • Help Needed to Sum Column in Fixed Table

    I am new to LiveCycle.  I need to sum a column in a fixed table.  My rows are summing correctly.  I have tried every formula on the web both in FormCalc and Javascript.  I've cut and pasted script from Adobe templates and from forms on the web.  Nothing is working.  Each change produces a new set of errors.  The Hierarchy is:  (untitled Subform) (page 2), Table 2, Header Row {Header Row contains Year 1, Year 2...Year 5}, Row1 {Row1 contains Text Title, Cell2, Cell3, Cell4, Cell5, Cell6, (untitled Numeric Field) which is a calculated sum of Years 1-5}, Row2, Row3...Row7 are exactly the same.  I want to calculate the sum of each column in the footer row but I keep getting script errors.

    I am new to LiveCycle.  I need to sum a column in a fixed table.  My rows are summing correctly.  I have tried every formula on the web both in FormCalc and Javascript.  I've cut and pasted script from Adobe templates and from forms on the web.  Nothing is working.  Each change produces a new set of errors.  The Hierarchy is:  (untitled Subform) (page 2), Table 2, Header Row {Header Row contains Year 1, Year 2...Year 5}, Row1 {Row1 contains Text Title, Cell2, Cell3, Cell4, Cell5, Cell6, (untitled Numeric Field) which is a calculated sum of Years 1-5}, Row2, Row3...Row7 are exactly the same.  I want to calculate the sum of each column in the footer row but I keep getting script errors.

  • Abap import error DbSl Trace: ORA-1403 when accessing table SAPUSER

    hi all
    I am installing ERP  6.0 (ABAP) on win2003 cluster, oracle 10g, I have error at database instance intallation. here some logs
    DD03L.log
    I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20090812102157
    I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#18 $ SAP
    I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Apr  3 2009 09:03:56
    I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i DD03L.cmd -dbcodepage 4103 -l DD03L.log -stop_on_error
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (RTF) ########## WARNING ###########
         Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
    (TPL) ERROR: unknown template variable "tablespace"
    I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
    I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20090812102157
    import_monitor.log
    ERROR: 2009-08-12 10:21:57 com.sap.inst.migmon.LoadTask run
    Loading of 'DD03L' import package is interrupted with R3load error.
    Process 'I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i DD03L.cmd -dbcodepage 4103 -l DD03L.log -stop_on_error' exited with return code 2.
    For mode details see 'DD03L.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    WARNING: 2009-08-12 10:22:25
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2009-08-12 10:22:25
    1 error(s) during processing of packages.
    INFO: 2009-08-12 10:22:25
    Import Monitor is stopped.
    sapinst_dev.log
    ERROR      2009-08-12 10:22:25.718
               CJSlibModule::writeError_impl()
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    TRACE      2009-08-12 10:22:25.718 [iaxxejsbas.hpp:483]
               EJS_Base::dispatchFunctionCall()
    JS Callback has thrown unknown exception. Rethrowing.
    ERROR      2009-08-12 10:22:25.734 [sixxcstepexecute.cpp:951]
    FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
    TRACE      2009-08-12 10:22:25.781 [iaxxgenimp.cpp:752]
                CGuiEngineImp::showMessageBox
    <html> <head> </head> <body> <p> An error occurred while processing service SAP ERP 6.0 Support Release 3 > SAP Systems > Oracle > High-Availability System > Based on AS ABAP > Database Instance( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You may now </p> <ul> <li> choose <i>Retry</i> to repeat the current step. </li> <li> choose <i>View Log</i> to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAP/DB. </p> </body></html>
    TRACE      2009-08-12 10:22:25.781 [iaxxgenimp.cpp:1255]
               CGuiEngineImp::acceptAnswerForBlockingRequest
    Waiting for an answer from GUI
    sapinst.log
    WARNING 2009-08-12 10:22:25.718
    Execution of the command "C:\j2sdk1.4.2_21-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
    java version "1.4.2_21"
    Java(TM) Platform, Standard Edition for Business (build 1.4.2_21-b03)
    Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_21-b03, mixed mode)
    Import Monitor jobs: running 1, waiting 1, completed 26, failed 0, total 28.
    Loading of 'DD03L' import package: ERROR
    Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.
    ERROR 2009-08-12 10:22:25.718
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    ERROR 2009-08-12 10:22:25.734
    FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
    any idea
    Regards
    ABH

    hi
    All logs are above (include import_monitor.log and java)
    thanks

  • ORA-01171: datafile 6 going offline due to error advancing checkpoint

    Hi
    Anyone here know what cause this error? This error happened after backup at night.The data file then went offline. Anyone know the reason?
    Thanks
    Excerpt from alert.log:
    Mon Feb 26 20:34:45 2007
    Errors in file d:\oracle\admin\live\bdump\live_ckpt_1064.trc:
    ORA-01171: datafile 6 going offline due to error advancing checkpoint
    ORA-01122: database file 6 failed verification check
    ORA-01110: data file 6: 'D:\ORACLE\ORADATA\LIVE\VGSM_DB01.DBF'
    ORA-01208: data file is an old version - not accessing current version
    Contents of d:\oracle\admin\live\bdump\live_ckpt_1064.trc
    Dump file d:\oracle\admin\live\bdump\live_ckpt_1064.trc
    Mon Feb 26 20:34:45 2007
    ORACLE V9.2.0.1.0 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.0 Service Pack 4, CPU type 586
    Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.1.0 - Production
    Windows 2000 Version 5.0 Service Pack 4, CPU type 586
    Instance name: live
    Redo thread mounted by this instance: 1
    Oracle process number: 5
    Windows thread id: 1064, image: ORACLE.EXE
    *** 2007-02-26 20:34:45.000
    *** SESSION ID:(4.1) 2007-02-26 20:34:45.000
    ORA-01171: datafile 6 going offline due to error advancing checkpoint
    ORA-01122: database file 6 failed verification check
    ORA-01110: data file 6: 'D:\ORACLE\ORADATA\LIVE\VGSM_DB01.DBF'
    ORA-01208: data file is an old version - not accessing current version

    Thanks
    I looked at applicaiton log and found there are message on audit trail:
    26/02/2007     20:03:56     Oracle.live     Audit trail: ACTION : 'CONNECT' DATABASE USER: '/' PRIVILEGE : SYSDBA CLIENT USER: PHARMA\OmniBack CLIENT TERMINAL: AUSALDB03 STATUS: 0 .
    26/02/2007     20:01:35     Oracle.live     Audit trail: ACTION : 'CONNECT' DATABASE USER: '/' PRIVILEGE : SYSDBA CLIENT USER: PHARMA\OmniBack CLIENT TERMINAL: AUSALDB03 STATUS: 0 .
    But the datbase was not shotdown immediately, it was shutdown next day as shown below:
    27/02/2007     12:17:46     Oracle.live     Audit trail: ACTION : 'CONNECT' DATABASE USER: '/' PRIVILEGE : SYSDBA CLIENT USER: AUSALDB03\oborj0 CLIENT TERMINAL: AUSALDB03 STATUS: 0 .
    27/02/2007     12:17:45     Oracle.live     AUSALDB03     Initializing PGA for process ARC1 in instance live.
    27/02/2007     12:17:44     Oracle.live     Initializing PGA for process ARC0 in instance live.
    27/02/2007     12:17:44     Oracle.live     Initializing PGA for process RECO in instance live.
    27/02/2007     12:17:44     Oracle.live     Initializing PGA for process SMON in instance live.
    27/02/2007     12:17:43     Oracle.live     Initializing PGA for process CKPT in instance live.
    27/02/2007     12:17:43     Oracle.live     Initializing PGA for process LGWR in instance live.
    27/02/2007     12:17:43     Oracle.live     Initializing PGA for process DBW0 in instance live.
    27/02/2007     12:17:42     Oracle.live     Initializing PGA for process PMON in instance live.
    27/02/2007     12:17:42     Oracle.live     Initializing SGA for instance live.
    27/02/2007     12:17:42     Oracle.live     Audit trail: ACTION : 'STARTUP' DATABASE USER: '/' PRIVILEGE : SYSDBA CLIENT USER: AUSALDB03\oborj0 CLIENT TERMINAL: Not Available STATUS: 0 .
    27/02/2007     12:17:11     Oracle.live     Instance live has been terminated.
    27/02/2007     12:17:10     Oracle.live     All process in instance live stopped
    27/02/2007     12:17:09     Oracle.live     Shutdown normal performed on instance live.
    27/02/2007     12:17:09     Oracle.live     Audit trail: ACTION : 'SHUTDOWN' DATABASE USER: '/' PRIVILEGE : SYSDBA CLIENT USER: AUSALDB03\oborj0 CLIENT TERMINAL: AUSALDB03 STATUS: 0 .
    27/02/2007     12:13:31     Oracle.live     Audit trail: ACTION : 'CONNECT' DATABASE USER: '/' PRIVILEGE : SYSDBA CLIENT USER: AUSALDB03\oborj0 CLIENT TERMINAL: AUSALDB03 STATUS: 0 .
    Do you think the database was not shutdown properly at that time? If backup of datafile was carried on with database still open, it may cause the errors as shwon on oracle alert log file, but I am not sure.
    Also I found the database was shutdown properly on the othe day but with user name ="sys"! Do you think this username cause the problem of shutdown?
    24/02/2007     20:04:54     Oracle.live     Audit trail: ACTION : 'CONNECT' DATABASE USER: 'sys' PRIVILEGE : SYSDBA CLIENT USER: PHARMA\AUSALDB03$ CLIENT TERMINAL: AUSALDB03 STATUS: 0 .
    24/02/2007     20:04:54     Oracle.liveInitializing PGA for process ARC1 in instance live.
    24/02/2007     20:04:53     Oracle.live     Initializing PGA for process ARC0 in instance live.
    24/02/2007     20:04:53     Oracle.liveInitializing PGA for process RECO in instance live.
    24/02/2007     20:04:53     Oracle.live     Initializing PGA for process SMON in instance live.
    24/02/2007     20:04:53     Oracle.live     Initializing PGA for process CKPT in instance live.
    24/02/2007     20:04:52     Oracle.live     Initializing PGA for process LGWR in instance live.
    24/02/2007     20:04:52     Oracle.live     Initializing PGA for process DBW0 in instance live.
    24/02/2007     20:04:52     Oracle.live     Initializing PGA for process PMON in instance live.
    24/02/2007     20:04:51     Oracle.live     Initializing SGA for instance live.
    24/02/2007     20:04:51     Oracle.live     Audit trail: ACTION : 'STARTUP' DATABASE USER: '/' PRIVILEGE : SYSDBA CLIENT USER: PHARMA\AUSALDB03$ CLIENT TERMINAL: Not Available STATUS: 0 .
    24/02/2007     20:04:51     Oracle.live     Audit trail: ACTION : 'CONNECT' DATABASE USER: 'sys' PRIVILEGE : SYSDBA CLIENT USER: PHARMA\AUSALDB03$ CLIENT TERMINAL: AUSALDB03 STATUS: 0 .
    24/02/2007     20:00:17     Oracle.live     Instance live has been terminated.
    24/02/2007     20:00:15     Oracle.live     All process in instance live stopped
    24/02/2007     20:00:11     Oracle.live     Shutdown normal performed on instance live.
    24/02/2007     20:00:11     Oracle.live     Audit trail: ACTION : 'SHUTDOWN' DATABASE USER: '/' PRIVILEGE : SYSDBA CLIENT USER: PHARMA\AUSALDB03$ CLIENT TERMINAL: AUSALDB03 STATUS: 0 .
    24/02/2007     20:00:08     Oracle.live     Audit trail: ACTION : 'CONNECT' DATABASE USER: 'sys' PRIVILEGE : SYSDBA CLIENT USER: PHARMA\AUSALDB03$ CLIENT TERMINAL: AUSALDB03 STATUS: 0 .
    Thanks for your help!
    Li

  • Why am I getting this error message in SQL Developer-ORA-01735: invalid ALTER TABLE OPTION?

    To Whom it may Concern,
    I am attempting to add two columns Comm_id and Ben_id to a table in SQL Developer (Oracle).
    Here is the syntax I am using:
    ALTER TABLE ACCTMANAGER
    ADD (Comm_id NUMBER(10)),
    Ben_id VARCHAR(2);
    The spool file I'm getting as a result of the script above:
    Error starting at line 1 in command:
    ALTER TABLE ACCTMANAGER
    ADD (Comm_id NUMBER(10)),
    Ben_id VARCHAR(2)
    Error report:
    SQL Error: ORA-01735: invalid ALTER TABLE option
    01735. 00000 -  "invalid ALTER TABLE option"
    *Cause:   
    *Action:
    DESC acctmanager
    Thank you in advance.

    4b60e01f-2ea5-40fe-a161-fc12d38d09e5 wrote:
    To Whom it may Concern,
    I am attempting to add two columns Comm_id and Ben_id to a table in SQL Developer (Oracle).
    Here is the syntax I am using:
    ALTER TABLE ACCTMANAGER
    ADD (Comm_id NUMBER(10)),
    Ben_id VARCHAR(2);
    The spool file I'm getting as a result of the script above:
    Error starting at line 1 in command:
    ALTER TABLE ACCTMANAGER
    ADD (Comm_id NUMBER(10)),
    Ben_id VARCHAR(2)
    Error report:
    SQL Error: ORA-01735: invalid ALTER TABLE option
    01735. 00000 -  "invalid ALTER TABLE option"
    *Cause:  
    *Action:
    DESC acctmanager
    Thank you in advance.
    try as below instead
    ALTER TABLE ACCTMANAGER
    ADD (Comm_id NUMBER(10), Ben_id VARCHAR(2));

  • Time series inconsistency due to change in Fiscal variant/Storage bucket

    Hi All,
    We got into the situation where running time series consistency check on a DP planning area fails with  the message pointing to, 'changes to Fiscal variant'.  We are unable to track any changes to the fiscal variant though there is a possibility that storage bucket horizon could have been changed. Is there a way to correct/synch this by running a report?
    We are trying to avoid re-initialization here, though this is an option, for the obvious reasons to backup the data in production. Is there an alternative solution to fix this inconsistency?
    Cheers!

    Dear Ashok,
    You should never change a FYV when this FYV is used in a storage
    bucket profile which is used in a planning area and if time series
    objects are already created. It is no problem to maintain the FYV for
    an additional time range, but changes and deletion of periods should
    never be made if the FYV is actively used. You should not
    change existing periods. If you want to make any changes to buckets
    in your FYV or delete buckets, you should always make a COMPLETE
    backup of ALL your data from the planning area into an InfoCube,
    then delete the time series objects for the planning area (and with
    this all the data in liveCache) and then change the FYV. After that,
    you can create time series objects again and reload the data from the
    Backup-InfoCube into the planning area. If you do these steps, you
    will not risk to loose any data. The data in the InfoCube will be
    the backup you can reload.
    As some processes check the FYV some time before and after it is used,
    it is very recommendable to maintain the FYV at least 2 - 3 years in
    the past and in the future. E.g. if you create time series objects up
    from 2001 you should maintain your FYV at least back to 1999 and if you
    create time series objects until 2006, you should maintain your FYV
    at least until 2008. It might be that you never experience problems if
    you do not maintain the FYV in this time range, but some processes do
    additional checks and then it can come to problems
    Regards,
    Rakesh

Maybe you are looking for