Oracle Upgrade (DBUA) error

Hi
Which execuring the command "dbua" for upgrade, I get the following error
Exception in thread "main" java.security.AccessControlException: access denied (java.lang.RuntimePermission setIO)
        at java.security.AccessControlContext.checkPermission(Unknown Source)
        at java.security.AccessController.checkPermission(Unknown Source)
        at java.lang.SecurityManager.checkPermission(Unknown Source)
        at java.lang.System.checkIO(Unknown Source)
        at java.lang.System.setErr(Unknown Source)
        at oracle.ops.mgmt.trace.Trace.enableLogging(Trace.java:751)
        at oracle.ops.mgmt.trace.Trace.enableLogging(Trace.java:720)
        at oracle.sysman.assistants.dbma.backend.CompManager.setLoggings(CompManager.java:3390)
        at oracle.sysman.assistants.dbma.backend.CompManager.initialize(CompManager.java:297)
        at oracle.sysman.assistants.dbma.ui.UICompManager.initialize(UICompManager.java:141)
        at oracle.sysman.assistants.dbma.Dbma.execute(Dbma.java:90)
        at oracle.sysman.assistants.dbma.Dbma.statusMain(Dbma.java:177)
        at oracle.sysman.assistants.dbma.Dbma.main(Dbma.java:158)
let me how to get rid of this problem..
Thanks in advance !
Regards
Madhu

Hi Madhusudhan,
Did you run dbua with ora<sid> user? It is clearly a user rights issue.
Regards,
János

Similar Messages

  • J2EE Engine Jcontrol Error :Oracle upgrade 10 to11  :ODBC driver Solution

    Hello Every one,
    To  make a valuable information for Oracle upgrade from Oracle 10 to oracle 11.2.0.2 on Java environment.
    Please do the following changes to avoid JDBC driver version error.
    Memo : When The upgrade happens the JDBC drivers are overwritten under drive:/oracle/.../JDBC/lib
    you will not see classes12.jar and nls_charset12.jar which is a part of Oracle 10 and JDBC driver version. Thereis no such files for Oracle 11. The application is not supported under Oracle 11.
    Following steps will make the J2ee Engine work.
    1. Upgrade SDK to 1.6. and verify using Java -version. Set Path and Class path.
    2. Since the Jdk is changed now do update in this 3 files
      a. SID_JC01_hostname 
    In this file update the parameter "jstartup/vm/home = C:\Program Files\Java\jdk1.6.0_26"
    b. Also for SID_SCS00_Hostname
    3. Check for j2ee/dbdriver = $(DIR_EXECUTABLE)\ojdbc14.jar    which can work with this version at this time or need to change to ojdbc6.jar
    in profile parameter, bootstrap properties (:\usr\sap\sid\jc01\j2ee\cluster\bootstrap), and template configuaration file in usr\sap\sid\jc01\j2ee
    4. Copy classes12.jar and nls_charset12.jar in \oracle\jdbc\lib from any Oracle 10 installation. and set in classpath.
    5. Hope last the password in secure  store is correct.
    Restart the cluster.
    This is exclusively of your oracle is upgraded and J2ee does not come up.
    Regards,
    Chetan Poojary.

    I think you'd need to contact Oracle support to get access to older versions of the driver.
    Since 8.0.5 isn't supported any longer, however, is it possible for you to update your Oracle client to one of the supported releases-- 8.1.7 or 9i?
    Justin

  • Oracle Upgrade --  Pre-Upgrade 10.2.0.4 to 11.2.0.1

    Hello,
    I want to do an Oracle Upgrade to version 11.2g!
    At this point I did some things (in Windows Server 2003 X64):
    1-) Install Oracle 10.2.0.1 (DVD Media);
    2-) Installation of Oracle patchset 10.2.0.4 (note 871735);
    3-) Installation of interim / last generics patch (note 1137346);
    4-) Installation of SAP ECC 6.0 SR3 by SAPInst
    5-) After SAP installation I did all the corrections in Oracle parameters as it mentioned in note 830576.
    As you see above, all the SAP system was well installed!
    But now I want to do the Oracle Upgrade process to the last version, Oracle DB 11.2g  (11.2.0.1)... and so I´m following the Upgrade guide "Upgrade to Oracle Database 11g Release 2 (11.2) Windows.pdf" with some SAP notes for Upgrade process.
    So I´m at this point in planning chapter where is recommended to check so things in actual database, one of this checks are running some SQL-scripts to perform an Oracle database upgrade with DBUA to release 11.2 (as mentioned in note 1431793 - Oracle 11.2.0: Upgrade Scripts)
    I ran two Pre-Scripts, the @pre_upgrade_status.sql and @pre_upgrade_tasks.sql but both outputs showed some warnings and they are worrying me... so what I ask to you is some kind of help in analyse of them and tell me if this issues are relevant for the upgrading process and if so, what you recommend me to do to correct their!
    Next I will post here this two log scripts... they are long!!!

    PRE_UPGRADE_TASKS.log:
    SQL> @pre_upgrade_tasks.sql
    PRE-UPGRADE Tasks: === START ===
    2010-08-05 18:24:13                                                                               
    Recompiling invalid objects
    This reduces the number of invalid objects as much as possible.
    COMP_TIMESTAMP UTLRP_BGN  2010-08-05 18:24:13                                                      
    DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
    DOC>   objects in the database. Recompilation time is proportional to the
    DOC>   number of invalid objects in the database, so this command may take
    DOC>   a long time to execute on a database with a large number of invalid
    DOC>   objects.
    DOC>
    DOC>   Use the following queries to track recompilation progress:
    DOC>
    DOC>   1. Query returning the number of invalid objects remaining. This
    DOC>       number should decrease with time.
    DOC>          SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
    DOC>
    DOC>   2. Query returning the number of objects compiled so far. This number
    DOC>       should increase with time.
    DOC>          SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
    DOC>
    DOC>   This script automatically chooses serial or parallel recompilation
    DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
    DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
    DOC>   On RAC, this number is added across all RAC nodes.
    DOC>
    DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
    DOC>   recompilation. Jobs are created without instance affinity so that they
    DOC>   can migrate across RAC nodes. Use the following queries to verify
    DOC>   whether UTL_RECOMP jobs are being created and run correctly:
    DOC>
    DOC>   1. Query showing jobs created by UTL_RECOMP
    DOC>          SELECT job_name FROM dba_scheduler_jobs
    DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
    DOC>
    DOC>   2. Query showing UTL_RECOMP jobs that are running
    DOC>          SELECT job_name FROM dba_scheduler_running_jobs
    DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
    DOC>#
    COMP_TIMESTAMP UTLRP_END  2010-08-05 18:24:15                                                      
    DOC> The following query reports the number of objects that have compiled
    DOC> with errors (objects that compile with errors have status set to 3 in
    DOC> obj$). If the number is higher than expected, please examine the error
    DOC> messages reported with each object (using SHOW ERRORS) to see if they
    DOC> point to system misconfiguration or resource constraints that must be
    DOC> fixed before attempting to recompile these objects.
    DOC>#
                      0                                                                               
    DOC> The following query reports the number of errors caught during
    DOC> recompilation. If this number is non-zero, please query the error
    DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
    DOC> are due to misconfiguration or resource constraints that must be
    DOC> fixed before objects can compile successfully.
    DOC>#
                              0                                                                        
    Purging Recyclebin
    This reduces the time needed for upgrading the database.
    Truncating SYS.AUD$
    This reduces the time needed for upgrading the database.
    Gathering Oracle Dictionary Statistics
    This reduces the time needed for upgrading the database.
    Running Pre-Upgrade-Information Tool utlu112i.sql
    This is a mandatory task for manual database upgrades.
    This tool is also run in pre_upgrade_status.sql.
    Oracle Database 11.2 Pre-Upgrade Information Tool 08-05-2010 18:24:45                              
    Script Version: 11.2.0.1.0 Build: 003                                                              
    Database:                                                                               
    --> name:          PRD                                                                             
    --> version:       10.2.0.4.0                                                                      
    --> compatible:    10.2.0                                                                          
    --> blocksize:     8192                                                                            
    --> platform:      Microsoft Windows x86 64-bit                                                    
    --> timezone file: V4                                                                               
    Tablespaces: [make adjustments in the current environment]                                         
    --> SYSTEM tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 905 MB                                                                 
    --> PSAPUNDO tablespace is adequate for the upgrade.                                               
    .... minimum required size: 84 MB                                                                  
    --> SYSAUX tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 210 MB                                                                 
    --> PSAPTEMP tablespace is adequate for the upgrade.                                               
    .... minimum required size: 61 MB                                                                  
    Flashback: OFF                                                                               
    Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]                                
    Note: Pre-upgrade tool was run on a lower version 64-bit database.                                 
    --> If Target Oracle is 32-Bit, refer here for Update Parameters:                                  
    -- No update parameter changes are required.                                                       
    --> If Target Oracle is 64-Bit, refer here for Update Parameters:                                  
    WARNING: --> "shared_pool_size" needs to be increased to at least 472 MB                           
    Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]                               
    -- No renamed parameters found. No changes are required.                                           
    Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]                   
    --> remote_os_authent            11.1       DEPRECATED                                             
    --> background_dump_dest         11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    --> user_dump_dest               11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    Components: [The following database components will be upgraded or installed]                      
    --> Oracle Catalog Views         [upgrade]  VALID                                                  
    --> Oracle Packages and Types    [upgrade]  VALID                                                  
    Miscellaneous Warnings                                                                             
    WARNING: --> Database is using a timezone file older than version 11.                              
    .... After the release migration, it is recommended that DBMS_DST package                          
    .... be used to upgrade the 10.2.0.4.0 database timezone version                                   
    .... to the latest version which comes with the new release.                                       
    Recommendations                                                                               
    Oracle recommends gathering dictionary statistics prior to                                         
    upgrading the database.                                                                            
    To gather dictionary statistics execute the following command                                      
    while connected as SYSDBA:                                                                               
    EXECUTE dbms_stats.gather_dictionary_stats;                                                                               
    Oracle recommends removing all hidden parameters prior to upgrading.                                                                               
    To view existing hidden parameters execute the following command                                   
    while connected AS SYSDBA:                                                                               
    SELECT name,description from SYS.V$PARAMETER WHERE name                                        
            LIKE '\_%' ESCAPE '\'                                                                               
    Changes will need to be made in the init.ora or spfile.                                                                               
    Oracle recommends reviewing any defined events prior to upgrading.                                                                               
    To view existing non-default events execute the following commands                                 
    while connected AS SYSDBA:                                                                         
      Events:                                                                               
    SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2                           
          WHERE  UPPER(name) ='EVENT' AND  isdefault='FALSE'                                                                               
    Trace Events:                                                                               
    SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2                           
          WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'                                                                               
    Changes will need to be made in the init.ora or spfile.                                                                               
    PRE-UPGRADE Tasks: === FINISHED ===
    SQL> spool off

  • Oracle Upgrade 9.2.0.5.0 to 10.2.0,2

    Hi!
    Please help!, We are doing an oracle upgrade from 9.2.0.5.0 to 10.2.0.2 in HP-UX but the DBUA stops with the following in the logs:
    In the user trace I see this:
    ORA-942 on service$ trapped and ignored during OPEN for migrate
    unexpected exception err=604, err2=942
    In the oracle_server.log
    CREATE OR REPLACE TYPE sys.streams$transformation_info
    ERROR at line 1:
    ORA-03113: end-of-file on communication channel
    About 20 minutes later in the oracle alert log a core dump:
    ORA-07445: exception encountered: core dump [koputilassert()+12] [SIGBUS] [unkno
    wn code] [0x000000000] [] []
    Please any advice would be greatly appreciated.
    Thanks in advance
    Erika
    Edited by: ERIKA BORREGO on May 21, 2008 6:36 PM

    Looks like metalink 435400.1
    I suggest you open a call @ SAP and let them look on the system.
    Markus

  • Oracle Upgrade from 10g to 11g [BRANCHED BY MODERATOR]

    Hi Deepak/Folks,
    Another question that I have is that while doing the Oracle Upgrade on an EP server, the patches were not installed properly and I had to shut down the Patches installation after it did not do anything for a while.
    Now when I try to install the patches it fails telling me that the Installed patches cannot be verified, I had written to SAP and they told me to follow the
    SAP note 1862446 - Inventory
    load failed... OPatch cannot load inventory for the given Oracle Home
    and re-create the oracle  inventory.
    This has also not helped in anyway.
    Is there a solution to this problem.
    Following is the error that I am getting when I try to Install the patches
    Getting pre-run patch inventory...
    Getting pre-run patch inventory...failed.
    Cannot get pre-run patch inventory.
    Refer to log file
      $ORACLE_HOME/cfgtoollogs/mopatch/mopatch-2014_08_06-14-52-51.log
    when I open the log file specified here I get the following
    more mopatch-2014_08_06-14-52-51.log
    more /oracle/<SID>/11203/cfgtoollogs/mopatch/mopatch-2014_08_06-15-01-51.log
    MOPatch - Install Multiple Oracle Patches in One Run - 2.1.15.
    Copyright (c) 2007, 2013, Oracle and/or its affiliates. All rights reserved.
    Version:       2.1.15
    Revision:      5.1.2.26
    Command-line:  /oracle/<SID>/11203/MOPatch/mopatch.sh -v -s SAP11203P_1312-20009978.zip
    Oracle Home:   /oracle/<SID>/11203
    RDBMS version: 11.2.0.3.0
    OPatch version:11.2.0.3.3
    Clean-up:      supported
    PSUs:          supported
    Log file:      $ORACLE_HOME/cfgtoollogs/mopatch/mopatch-2014_08_06-15-01-51.log
    Patch base:    .
    Patch source:  SAP11203P_1312-20009978.zip
    Link script:   ./link.mts<SID>ua.sh
    Readmes:       <none>
    Strpd. Readmes:<none>
    make utility:  /usr/ccs/bin/make
    unzip utility: /oracle/<SID>/11203/bin/unzip
    User name:     ora<SID>
    Working dir:   /oracle/stage
    System:        HP-UX mts<SID>ua B.11.31 U ia64 2468369872 unlimited-user license
    Disk free:     11734549 KBytes on /oracle/<SID>
    Disk required: 886496 KBytes on /oracle/<SID>
    Getting pre-run patch inventory...
    executing: "/oracle/<SID>/11203/OPatch/opatch" lsinventory -retry 0 -xml "./mopatch-187-21696-tmpdir/preinv.xml"
    ========================================================
    GENERIC OPATCH VERSION - FOR USE IN SAP ENVIRONMENT ONLY
    ========================================================
    Oracle Interim Patch Installer version 11.2.0.3.3
    Copyright (c) 2012, Oracle Corporation.  All rights reserved.
    Oracle Home       : /oracle/<SID>/11203
    Central Inventory : /oracle/<SID>/oraInventory
       from           : /oracle/<SID>/11203/oraInst.loc
    OPatch version    : 11.2.0.3.3
    OUI version       : 11.2.0.3.0
    Log file location : /oracle/<SID>/11203/cfgtoollogs/opatch/opatch2014-08-06_15-01-56PM_1.log
    List of Homes on this system:
    Inventory load failed... OPatch cannot load inventory for the given Oracle Home.
    Possible causes are:
       Oracle Home dir. path does not exist in Central Inventory
       Oracle Home is a symbolic link
       Oracle Home inventory is corrupted
    LsInventorySession failed: OracleHomeInventory gets null oracleHomeInfo
    OPatch failed with error code 73
    Getting pre-run patch inventory...failed.
    Cannot get pre-run patch inventory.  Exiting.
    I would appreciate if you folks can help me out on this
    Thanks
    APS

    FOLLOW UP QUESTION BRANCHED:
    Oracle Upgrade from 10g to 11g [BRANCHED BY MODERATOR]

  • Oracle Upgrade 8.1.7.4 to 10g in Red hat linux

    Dear All,
    We are planning to upgrade our oracle database from 8i to 10g along with the Redhat linux upgrade from  2.4.9-e 27 ent to Red Hat Linux 5. In my study and also from Installation guides and oracle upgrade guides I made sure that its possible to upgrade our database from 8.1.7.4.
    So I have planned the below options to do the same and not sure about the possibilities. If anyone have thoughts and idea on the same please suggest me.
    We dont have plan to migrate the development hardware and the sap version is 4.7E
    Option 1: Upgrade the Linux to 5 and then upgrading the database to 10g usign upgrade assistant tool
    Option 2: Export the database using sapinst tool and then crashing the server. Installing linux5 and importing the database using sapinst tool.(I am aware this is not a good idea since there is no migration in hardware but it will be helpful in production since we are migrating the production system).
    Option 3: Performing DBUA assistant in development and sapinst method in production.(helpful in disaster recovery)
    Could you please suggest on the same?
    My query is that.
    If i am performing oracle export from 8.1.7.4 and if i am import the same in oracle 10g using the sapinst tool. Will this work? or it will create a problem in table level. I am looking for answers for this Question. Kindly explain me on this.
    Regards
    Vijay

    Re: Restoring data from 9i to 10g
    The above link was useful to me
    Regards
    Vijay

  • Oracle Upgrade from 8.1.7.4 to 9.2

    Hi ALL,
    I am having a problem when i am trying to upgrade oracle from 8.1.7 to 9.2.
    I have installed Oracle 9i in seperate oracle home directory than the original 8.1.7 home directory. After that i have removed oracle_home = sid from <SID>adm user environment as described in sap upgrade manual.i have logged in again to activate the variables. When i am trying to start database upgrade assistant in new oracle 9i. it is showing me the old oracle home and asking me to upgrade. when i press enter..it is erroring out saying ora 12560 error.
    Guys, could you please let us know why these error occured. Did i miss something as i followed sap document on oracle upgrade.
    Thanks in advance..

    Hello vales,
    Even i dont know how it worked .. upgrade assistant started working when i logged in with administrator account with which i installed oracle installations...
    Thanks

  • ORA-01017: invalid username/password; after Oracle Upgrade 9.2.06 to 10.2

    Hi
    I did an oracle Upgrade from Oracle Upgrade 9.2.06 to 10.2 as per SAP Documentation.
    and after the upgrade was successful i changed the password of SAPABT (sapowner)
    and now it is giving an error in work folder  <b>dev_wo</b>
    while connecting can any one help please ?
    Tue Feb 06 18:55:20 2007
    C  Client NLS settings: AMERICAN_AMERICA.WE8DEC
    C  Logon as OPS$-user to get SAPABT's password
    C  Connecting as /@ABT on connection 0 (nls_hdl 0) ... (dbsl 640 110706)
    C  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    C    0 WE8DEC                                                    1   044FAB58   045000D4   044FF95C
    C  Attaching to DB Server ABT (con_hdl=0,svchp=044FF8A8,svrhp=04503F14)
    C  Starting user session (con_hdl=0,svchp=044FF8A8,srvhp=04503F14,usrhp=08C48D68)
    C  Now '/@ABT' is connected (con_hdl 0, nls_hdl 0).
    C  Got SAPABT's password from OPS$-user
    C  Disconnecting from connection 0 ...
    C  Close user session (con_hdl=0,svchp=044FF8A8,usrhp=08C48D68)
    C  Now I'm disconnected from ORACLE
    C  Connecting as SAPABT/<pwd>@ABT on connection 0 (nls_hdl 0) ... (dbsl 640 110706)
    C  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    C    0 WE8DEC                                                    1   044FAB58   045000D4   044FF95C
    C  Starting user session (con_hdl=0,svchp=044FF8A8,srvhp=04503F14,usrhp=08C48D68)
    C  *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
    [dboci.c      4473]
    C  *** ERROR => CONNECT failed with sql error '1017'
    [dbsloci.c    11297]
    B  ***LOG BY2=> sql error 1017   performing CON [dbsh#3 @ 1204] [dbsh    1204 ]
    B  ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dbsh#3 @ 1204] [dbsh    1204 ]
    B  ***LOG BY2=> sql error 1017   performing CON [dblink#2 @ 419] [dblink  0419 ]
    B  ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dblink#2 @ 419] [dblink  0419 ]
    M  ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c   1284]

    SQL> connect / as sysdba
    Connected.
    SQL> SELECT OWNER FROM DBA_TABLES WHERE TABLE_NAME = 'SAPUSER';
    OWNER
    OPS$CTSINTCOSNW5\ABTADM
    SQL> SELECT OWNER, TABLE_OWNER, TABLE_NAME FROM DBA_SYNONYMS WHERE SYNONYM_NAME
    = 'SAPUSER';
    OWNER                          TABLE_OWNER
    TABLE_NAME
    OPS$CTSINTCOSNW5\SAPSERVICEABT OPS$CTSINTCOSNW5\ABTADM
    SAPUSER
    SQL>
    Followed the note 400241       Problems with ops$ or sapr3 connect to Oracle       
    Problem got solved via the
    Updating BR * Tools
    brconnect -u / -c -f stats -t all -f collect -p 4 in  Oracle Database Guide 4.3.6 BRCONNECT
    Call BRTOOLS, Select Additional Functions --> Change password for database user.
    in my case it is sapabt user
    Thanks for the quick reply

  • Oracle upgrade with DataGuard

    Hello Experts,
    We have to upgrade oracle db from 10.2.0.2 to 11g.
    While upgrading to PRD system there is DR system also, which uses DataGuard for archive update on DR system.
    I would like to know that we need to take special care for DataGuard or DBUA will take care of DataGuard mechanism?
    Thanks in advance.
    Regards,
    Yogesh

    Hi Yogesh,
    in a SAP environment it is even more specific than the standard oracle upgrade guide (because of the compatible parameter and SAP scripts).
    We discussed this already in this thread: Upgrade to Oracle 11G in standby environment
    Regards
    Stefan

  • Oracle Upgrade interrupted inbetween, How to start the database?

    Hi All,
    Oracle upgrade is interrupted in between during the migration.
    could you please provide me with the detail steps to start the database again with the 9i.
    Thanks,
    Anu.

    Where is "in the middle"? Using dbua? During filesystem copy? Without specifying where it broke the only thing one can suggest is to restore everything from before the upgrade (Oracle binaries and database).
    Markus

  • Oracle.jms.AQjmsException: Error creating the db_connection( OSB PS2.)

    hi All,
    I am beginner in OSB 11g. Please excuse me if I am asking any dumb question.
    I am trying to post messages to Oracle AQ by configuring JMS Destination in OSB Alert destination
    I have configured AQ JMS in weblogic 10.3.3 ( OSB PS2) following the blog (http://jianmingli.com/wp/?p=2950)
    When i invoked my proxy OSB proxy service i am getting following exception. Can you please help if i am missing any kind of setup while configuring the JMS Module.
    Caused By: oracle.jms.AQjmsException: Error creating the db_connection
         at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:625)
         at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
         at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
         at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
         at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
         at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
         at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
         at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.getSession(JmsOutboundMessageContext.java:399)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.newMessage(JmsOutboundMessageContext.java:621)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.setRequestMetaData(JmsOutboundMessageContext.java:229)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.access$100(JmsOutboundMessageContext.java:72)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext$SendAction.run(JmsOutboundMessageContext.java:788)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.security.Security.runAs(Security.java:61)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:551)
         at com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:680)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
         at $Proxy111.sendMessageAsync(Unknown Source)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageWithoutService(TransportManagerImpl.java:489)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:417)
         at com.bea.wli.sb.init.FrameworkStarter$TransportServiceImpl.sendMessageAsync(FrameworkStarter.java:391)
         at com.bea.alsb.alert.action.jms.JmsActionProvider.executeAction(JmsActionProvider.java:345)
         at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:105)
         at com.bea.alsb.alert.pipeline.PipelineAlertManager.processAlert(PipelineAlertManager.java:59)
         at stages.logging.runtime.AlertRuntimeStep.processMessage(AlertRuntimeStep.java:125)
         at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
         at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:102)
         at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
         at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
         at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
         at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
         at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
         at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
         at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
         at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
         at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
         at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
         at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
         at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
         at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
         at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:566)
         at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
         at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
         at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
         at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
         at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
         at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
         at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)

    hi All,
    Here is the actual exception while posting message into AQ ( AQ JMS) from OSB.
    Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
    at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
    at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
    Not sure what is missing in my AQ JMS configuration. Please help.
    Regards,
    Nagi

  • Oracle Upgrade to 9i for BO 5i

    I'm preparing for an Oracle upgrade from 8.1.6 to 9.2 and a unix server migration via Oracle Export / Import. Potentially going on to 10g at a later point.
    Will importing the BO user and re-pointing users to the new database be sufficient to upgrade the BO elements or are there other steps? I believe some overnight jobs are kicked off externally by what sounds like the "SDK" so I don't believe there are any server related BO elements in BO 5i.
    All help appreciated. Information on the ground here is quite sketchy and I'm not a BO person.
    Regards

    you can always upgrade to new versions from lower versions.
    (upgradation to 9i from 7.x is also possible)

  • O1034 Oracle not available error

    Right, I'm running on a Windows Xp platform, I've installed ok and it runs ok. I have manually altered the password of user HR from within sqlplus, and everything is fine.The problem comes when I switch off and switch back on, I am unable to start the database.
    Running sqlplus system/password gives me ORA-01034 Oracle not available and ORA-27101: Shared memory realm does not exist.
    I have tried running stobdb.bat and startdb.bat which both run ok, but I still get the oracle not available error when going into sqlplus. It seems that the PC does not install the oracle set up on booting perhaps? I also cannot access the "Go to database home page", from my web browser, but I'm not sure if it is necessary to access that home page?

    We are seeing this a little bit, and not sure what is causing it at this stage. Starting the database manually seems to help, or at least points to the root cause problems.
    The steps to start the database manually are posted at Re: ORA-01033 after starting and trying to connect. and also posted below
    To shutdown manually go to the SQL Command Line (as the OS user that installed Oracle).
    At the SQL Prompt SQL> issue
    connect / as sysdba
    For example
    SQL> connect / as sysdba
    Connected.
    Then type
    shutdown immediate;
    You should see the following
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    Then type
    startup
    You should see the following
    SQL> startup
    ORACLE instance started.
    Total System Global Area 599785472 bytes
    Fixed Size 1249348 bytes
    Variable Size 192942012 bytes
    Database Buffers 402653184 bytes
    Redo Buffers 2940928 bytes
    Database mounted.
    Database opened.
    Just to be sure, also try a select
    select count(*) from hr.employees;
    You should see
    SQL> select count(*) from hr.employees;
    COUNT(*)
    107
    Any problems or errors reported with any of these steps, please let us know.

  • MAIL: The upgrade failed - error occurred during upgrade. launching Mail Import assistant  to repair damaged index did not work

    After installing Yosemite, the Mail required an upgrade. the upgrade was completed but resulted in a message: The upgrade failed. error occurred during the upgrade, check continue to launch Mail Import Assistant.
    This resulted in an instruction: Your mail index has been damaged. To repair it quit mail. Mail will repair index next time you open mail.
    Following this instruction resulted in the same failure message being repeated continuously.
    How do I proceed to upgrade the Mail app.?

    If doing as the alert directs (relaunching Mail) has no effect, see below.
    The new version of Mail stores its database in a different format than the old one, so the database has to be converted before Mail can use it. Sometimes the conversion fails because the old database is corrupt. The easy way to recover is to discard the old database and start afresh. You can do that without losing any messages, provided that:
    ☞ All your incoming mail accounts are on an IMAP or Exchange server
    ☞ You store sent messages on the server
    ☞ You don't have any "On My Mac" mailboxes
    Most well-known independent mail services such as iCloud and Gmail are based on IMAP. On the other hand, ISP-hosted mail services almost always use POP. If your ISP is one of your mail service providers (or the only one), you probably can't use this procedure. Ask for further instructions in that case.
    If you know that the conditions above are satisfied, continue as follows.
    Quit Mail if it's running. Back up all data.
    Open the Library folder in your home folder by holding down the option key and selecting
              Go ▹ Library
    from the Finder menu bar. Inside it is a subfolder named "Mail." Move that folder to the Desktop. You're not moving the Mail application; you're moving a folder named "Mail."
    Open the Internet Accounts pane in System Preferences and recreate your mail accounts other than iCloud with the same settings as before. To recreate an iCloud mail account, all you have to do is open the iCloud preference pane and check the box marked Mail.
    Launch Mail. If all goes well, your mailboxes should be restored automatically. The messages will be downloaded from the servers, so it may take a long time if you have very large mailboxes. Some people have mailboxes in the gigabyte range, and that may be a problem if your bandwidth usage is metered.
    If the mailboxes are created successfully, you can delete the folder you moved to the Desktop. You may have to recreate your Mail rules, signatures, and custom stationery. If it's very important to you not to have to do all that, ask for instructions before deleting the folder.

  • I just upgraded to Yosemite. Iphoto is now broken.  Upon upgrade receiving error "This update is not available for this Apple ID either because it was bought by a different user or the item was refunded or cancelled."

    I just upgraded to Yosemite. Iphoto is now broken.  Upon upgrade receiving error "This update is not available for this Apple ID either because it was bought by a different user or the item was refunded or cancelled."

    Perform the following, stopping with the first one which works:
    1. Open the Mac App Store's Purchases tab. If you're prompted to accept iPhoto into your Apple ID, do so.
    2. Move it out of the Applications folder(it may need to be put into the Trash temporarily), and then see if you can download it for free from its individual product page.
    3. Click here and contact Apple.
    (116137)

Maybe you are looking for