Upgrading Oracle JSP Engine to 1.1.2

I'm trying to upgrade Oracle JSP Engine from 1.1.0.0.0 (which comes with Oracle 8.1.7) to 1.1.2.
I've downloaded new version from OTN and I used loadjava to update classes in the database. Now I'm trying to use ncomp to natively compile classes (like I've read in the Releases Notes) but I'm getting:
error in: FindClassesToNcomp :java.sql.SQLException: ORA-29532: Java call terminated by uncaught Java exception: java.sql.SQLException: java.sql.SQLException: failed to produce status report because of: java.sql.SQLException: got error at insert into jaccelerator$status oracle.jdbc.driver.OracleSQLException: ORA-01401: inserted value too large for column
ORA-06512: at "SYS.JACCELERATOR___FIND_CLASS_LIST", line 0
ORA-06512: at "SYS.JACCELERATOR_FIND_CLASS_LIST", line 1
ORA-06512: at line 1
Any idea??
Thanks in advance.
MJ.
null

Welcome to the discussions!
Adding RAM is the quickest and cheapest way to get a performance boost. As mentioned, the apps you use are not universal and will run through the Rosetta translator which is a rather RAM intensive operation.
My suggestion is to get at least 1GB and if it is not too much of a stretch to get 2GB. RAM is relatively inexpensive now and the benefits will be seen immediately.

Similar Messages

  • How to configure Oracle jsp engine on OAS4.0.8.1

    1. How to configure Oracle jsp engine on OAS4.0.8.1 for linux
    2. How to set the parameter on OAS. The Ojsp document only give examples depict the syntax used when running in an Apache/JServ 1.0 environment

    Anyone?

  • Oracle JSP engine on Apache

    Hi,
    We have Apache Web server 1.3.9 and Jserv 1.1b3. On top of this, we have installed Oracle JSP engine. We have put the names of all the required jar files and directories in jserv.properties file. But, when we try to access any jsp files from a browser we are getting following error:
    Request URI: /test.jsp
    Exception:
    oracle.jsp.provider.JspCompileException:
    Errors compiling: d:\demos\apache\htdocs\_pages\test.java
    Package javax.servlet.jsp not found in import. import javax.servlet.jsp.*;
    Any idea why this error is happening.
    Thanks in advance,
    null

    Apache JServ implements Servlet 2.0 -- this class library doesn't contain the JSP interface classes. The JSP interface classes are contained in the JSWDK 1.0 (or greater) available from Sun. Download and configure Apache to use this class library AFTER the reference to the servlet 2.0 class library. For more information please check out the Documentation section for JSPs on technet. It contains specific information on configuring/installing for Apache.

  • Oracle.jsp.dbutil ? plz help

    hey i would like to use the ConnCacheBean in my jsp, when i try
    to import import = "oracle.jsp.dbutil.*" i get: cannot acces
    directory oracle\jsp\dbutil verify that this directory is
    reachable from classpath and/or sourcecode.
    I added all the libs to the classpath, i can see the JSP RUNTIME
    Lib is included ( points to ojsp.jar ).
    Do i need to download and add something else to the CLASSPATH??
    Any help is welcomde!

    OK found it!
    It is in the ojsputil.jar file that comes with the latest oracle
    jsp engine, i added the jar to classpath and BINGO. Funny it
    isn't there by default!
    mvg

  • Oracle.jsp.dbutil

    I have tried to find oracle.jsp.dbutil but I have not found it any where on the Oracle site. Is this included somewhere in JDeveloper 9i? If not where can I download it?

    OK found it!
    It is in the ojsputil.jar file that comes with the latest oracle
    jsp engine, i added the jar to classpath and BINGO. Funny it
    isn't there by default!
    mvg

  • Where do I get the oracle.jsp.dbutil library

    Where do I get the oracle.jsp.dbutil library.
    Thanks

    Bernhard (guest) wrote:
    : thanx for the advice. I think the links you posted will be
    : helpful in the future.
    : I found the source of my troubles on the SUSE homepage (ver 6.1
    : does not use glibc 2.1).
    : So now I needto find out how to upgrade to glibc 2.1
    Upgrading to SuSe 6.2 would probably do the trick. Upgrade is
    really smooth, and will take approximately 1h. I was able
    to run oracle 8i client install on my PC and it works (32M,
    160MHZ pentium) quite satisfactory. On my server machine
    (450MHZ, 128MB) I'm running RH 6.0 and it also works fine.
    On SuSe, I removed the "Kaffee" JVM installed by default and
    downloaded JRE 1.1.7 from www.blackdown.org. I haven't tried
    the "kaffe" engine but Oracle documentation requires blackdown.
    Michael, if you read this, have you tried installing with the
    default JVM engine delivered with SuSe 6.2?
    As long as your operating system name doesn't start with "MS"
    you should be OK.
    : But first I will buy me a book about LINUX administration and
    : hope to find the time reading it.
    : Colin. (guest) wrote:
    : : Bernhard (guest) wrote
    : : : But anyway: This is my first try to install anything on
    : LINUX.
    : : : If anybody has some good advise for a rookie re.
    : installation
    : : : of ORACLE SERVER 8.15 on Linux I would be very thankful.
    : : Try these links, there's lots of good tips to be found (and
    : : thanks to the authors of these sites).
    : : => A SuSE developers home page for Oracle.
    : : www.suse.de/~mha/oracle/
    : : => Install Guide for Redhat.
    : : jordan.fortwayne.com/oracle/
    : : => Oracle tips & scripts
    : : www.akadia.com/html/dod-frame.html
    : : amoeba.sagemediagroup.com/oracle_linux_howto/
    : : www.orafaq.org/
    : : www.oracle-dba.com/
    : : www.kevinloney.com/
    : : www.bf.rmit.edu.au/~orafaq/contents.html
    : : www.lazydba.com/
    : : www.dbasupport.com/
    : : www.dbspecialists.com/
    : : altern.org/place4oracle/oracle_contents.html
    : : www.dbdomain.com
    null

  • Need to connect to upgraded Oracle EBS R12 version from R11. The current ODI set up is pointing to R11, Can i use the same connection to point to R12? Please hele experts..

    Need to connect to upgraded Oracle EBS R12 version from R11. The current ODI set up is pointing to R11, Can i use the same connection to point to R12? Please hele experts...
    Rp

    1. in physical connections part can i use the same work schema
    2. Can i use same contexts created or do i need to create everything as new and then try?
    Thanks,
    Rp.
    Hi,
    As you mentioned that you just upgraded the database, so the data is same and schema is same you can connect with the same work schema.
    Yes, you can use the same contexts , but need to do Reverse Engineering for your new database.
    And about data server, i think you also have no need to create new data server, if hostname,sid and port etc are same as these were with R11(consult with your DBAs regarding it)

  • Oracle Determinations Engine Data Source Connector for Batch Processing?

    I have been trying to find +"Oracle Determinations Engine Data Source Connector"+. I have OPA 10.2 installed.
    Where can I find this in the installation directory? or Does it not come as a part of the standard installation?

    For 10.4 we have a new runtime which does what the Data Source connector does plus a whole lot more.
    The feature to look for in the new release is the Batch Processor, and you will find the documentation and the application in the Oracle Policy Automation Runtime zip file.
    The documentation has been upgraded and it should be a lot easier to use than the old DSC.
    Cheers
    Frank

  • Webserver/jsp engine call into weblogic ejb container

    Which one of these architectures would give the best performance.
              First architecture:
              3 boxes -
              1st box - webserver(IIS or IPlaner) with a JSP engine. (The JSP's
              produce dynamic content.)
              2nd box - weblogic 5.1 hosting EJB's
              3rd box - Oracle or DB2
              The 1st box is used to server up dynamic contect. The JSP's make dynamic
              contect from calls into the EJB container in the 2nd box. The EJB's then
              calls the DB in the 3rd box.
              2nd architecture:
              3 boxes-
              1st box - webserver with weblogic plug-ins for IIS or IPlanet
              2nd box - weblogic 5.1 - hosting JSP pages and EJBs
              3rd box - Oracle or DB2
              The 1st box's webserver just receives the request to JSPs and lets the
              plug-in find the appropriate weblogic instance. The JSPs that are processed
              on the 2nd box make calls into the EJB container on the 2nd box. The EJBs
              then make calls to the DB on the 3rd box.
              thanks
              -cb
              

    thanks you both for you input
              "Cameron Purdy" <[email protected]> wrote in message
              news:[email protected]...
              > It is certainly more efficient in terms of JSP/Servlet to EJB invocations
              if
              > you use WebLogic to do all three (JSP/Servlet/EJB) due to the
              well-designed
              > client stubs for EJBs that do pass-by-reference. If you have lots of
              small
              > invocations to EJBs, that is a good reason to consider WL for all three
              > (JSP/Servlet/EJB).
              >
              > OTOH there are a good number of developers that I have spoken with that
              > prefer other Servlet engines. These developers have had excellent
              > experiences with WL EJB handling, but some issues with JSP/Servlets, or
              > simply needed features offered by other servers. A few may have decided
              on
              > a price basis. Some of the technical issues were related to WL class
              > loading issues that are scheduled to be completely improved in the fall WL
              > release.
              >
              > All of that said, I personally would probably stick with WL to do all
              three
              > (JSP/Servlet/EJB). I believe that I have found most of the problems that
              WL
              > has ;-) and I have come through the other side still really liking the
              > product -- so even it's worst points (like the linkage error that had me
              > pulling out my hair and even searching through the Sun JVM sources ;-)
              > aren't that bad because it is a strong enough product that there are
              always
              > ways to work through or around just about anything. If I had to look at a
              > different JSP/Servlet engine, I would start with Caucho Resin, simply
              > because I like their approach and I know it works well with WL.
              >
              > Lastly remember that in the J2EE world, "no one ever got fired for buying
              > BEA WebLogic!"
              >
              > --
              >
              > Cameron Purdy
              > http://www.tangosol.com
              >
              >
              > "Chris Bick" <[email protected]> wrote in message
              > news:[email protected]...
              > > So you would not support/advise an architecture that has the JSP/Servlet
              > > engine on a different box then weblogic? If this is the case, could you
              > > give some reasons why?
              > >
              > > thanks,
              > > -cb
              > > "Cameron Purdy" <[email protected]> wrote in message
              > > news:[email protected]...
              > > > 1. Your bottleneck will probably be the third box (database server)
              in
              > > > either scenario. That's probably your biggest up-front cost -- making
              > > sure
              > > > the db server is up to the task.
              > > > 2. The second architecture is suggested by WL. The reason is that if
              > box
              > > > #2 (WL) is a cluster, you can theoretically add more boxes easily to
              get
              > > > pseudo-linear scaling for JSP and EJB processing. Of course, that
              only
              > > > helps if your database is not a bottleneck ;-) WL cluster is $17k per
              > > CPU.
              > > > 3. The real answer is that it depends on your application and the
              > number
              > > of
              > > > users that you are expecting. You want to make sure that when your
              site
              > > is
              > > > loaded that there is no significant queueing of requests on the WL
              side.
              > > I
              > > > believe you can see that information in the WL monitor.
              > > >
              > > > --
              > > >
              > > > Cameron Purdy
              > > > http://www.tangosol.com
              > > >
              > > >
              > > > "Chris Bick" <[email protected]> wrote in message
              > > > news:[email protected]...
              > > > > Which one of these architectures would give the best performance.
              > > > >
              > > > > First architecture:
              > > > >
              > > > > 3 boxes -
              > > > >
              > > > > 1st box - webserver(IIS or IPlaner) with a JSP engine. (The
              > > JSP's
              > > > > produce dynamic content.)
              > > > > 2nd box - weblogic 5.1 hosting EJB's
              > > > > 3rd box - Oracle or DB2
              > > > >
              > > > > The 1st box is used to server up dynamic contect. The JSP's make
              > > dynamic
              > > > > contect from calls into the EJB container in the 2nd box. The
              EJB's
              > > then
              > > > > calls the DB in the 3rd box.
              > > > >
              > > > > 2nd architecture:
              > > > >
              > > > > 3 boxes-
              > > > >
              > > > > 1st box - webserver with weblogic plug-ins for IIS or IPlanet
              > > > > 2nd box - weblogic 5.1 - hosting JSP pages and EJBs
              > > > > 3rd box - Oracle or DB2
              > > > >
              > > > > The 1st box's webserver just receives the request to JSPs and lets
              the
              > > > > plug-in find the appropriate weblogic instance. The JSPs that are
              > > > processed
              > > > > on the 2nd box make calls into the EJB container on the 2nd box.
              The
              > > EJBs
              > > > > then make calls to the DB on the 3rd box.
              > > > >
              > > > > thanks
              > > > > -cb
              >
              >
              >
              

  • Is PTG a JSP Engine ??

    I would like to know whether Portal To Go is a JSP engine like Tomcat/gnujsp & jswdk ??
    Thanks in advance.

    Oracle Applications use BC4J, UIX, and JDeveloper.
    The UIX framework implements the Oracle "Browser Look And Feel" (BLAF) that our Oracle Applications self-service applications use.
    The UIX JSP tag library lets JSP developers do the same.

  • Error when upgrading Oracle Identity Manager 9.1.0.1 to OIM 9.1.0.2

    Hello friends,
    I upgraded Oracle Identity Manager 9.1.0.1 to Oracle Identity Manager 9.1.0.2,after the running the command to apply the patch:
    OIM_HOME/xellerate/setup/patch_weblogic.cmd/sh WEBLOGIC_ADMIN_PASSWORD OIM_DB_USER_PASSWORD
    I get the error:
    [wldeploy] [BasicOperation.execute():445] : Initiating deploy operation for app, Xellerate, on targets:
    [wldeploy] [BasicOperation.execute():447] : AdminServer
    [wldeploy] Task 2 initiated: [Deployer:149026]deploy application Xellerate on AdminServer.
    [wldeploy] dumping Exception stack
    [wldeploy] Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
    [wldeploy] Target state: deploy failed on Server AdminServer
    [wldeploy]
    [wldeploy]
    [wldeploy] There are 2 nested errors:
    [wldeploy]
    [wldeploy] weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
    [wldeploy] and
    [wldeploy]
    [wldeploy] weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
    [wldeploy] Target Assignments:
    [wldeploy] + Xellerate AdminServer
    [wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
    [wldeploy] Target state: deploy failed on Server AdminServer
    [wldeploy]
    [wldeploy]
    [wldeploy] There are 2 nested errors:
    [wldeploy]
    [wldeploy] weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
    [wldeploy] and
    [wldeploy]
    [wldeploy] weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
    [wldeploy] [ServerConnectionImpl.close():332] : Closing DM connection
    [wldeploy] [ServerConnectionImpl.close():352] : Unregistered all listeners
    [wldeploy] [ServerConnectionImpl.closeJMX():372] : Closed JMX connection
    [wldeploy] [ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection
    [wldeploy] [ServerConnectionImpl.closeJMX():396] : Closed Edit JMX connection
    [ant] Exiting C:\oracle\xellerate\setup\weblogic-setup.xml.
    BUILD FAILED
    C:\oracle\xellerate\Setup\setup.xml:448: The following error occurred while executing this line:
    C:\oracle\xellerate\setup\weblogic-setup.xml:310: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
    Target state: deploy failed on Server AdminServer
    There are 2 nested errors:
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
    and
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
    Caused by: C:\oracle\xellerate\setup\weblogic-setup.xml:310: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
    Target state: deploy failed on Server AdminServer
    There are 2 nested errors:
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
    and
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
    Caused by: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
    Target state: deploy failed on Server AdminServer
    There are 2 nested errors:
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
    and
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
    Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
    Target state: deploy failed on Server AdminServer
    There are 2 nested errors:
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
    and
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
    --- Nested Exception ---
    C:\oracle\xellerate\setup\weblogic-setup.xml:310: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
    Target state: deploy failed on Server AdminServer
    There are 2 nested errors:
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
    and
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
    Caused by: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
    Target state: deploy failed on Server AdminServer
    There are 2 nested errors:
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
    and
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
    Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
    Target state: deploy failed on Server AdminServer
    There are 2 nested errors:
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
    and
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
    --- Nested Exception ---
    weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
    Target state: deploy failed on Server AdminServer
    There are 2 nested errors:
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
    and
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
    Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
    Target state: deploy failed on Server AdminServer
    There are 2 nested errors:
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
    and
    weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
    Total time: 4 minutes 35 seconds
    How do I deal with this question?
    Thanks.

    This error generally occur if your server is up and you are running patch for upgrade, and its very common error.
    follow the troubleshoot step and get it done.
    page 36
    Troubleshooting the Application of the Patch on Oracle WebLogic Server
    http://docs.oracle.com/cd/E14899_01/doc.9102/e14764.pdf

  • Upgrade oracle 9.2.0.8.0 to 10.2.03 ORA-06512: at "SYS.VERSION_SCRIPT", lin

    Upgrade oracle 9.2.0.8.0 to 10.2.03. while runing catupgrd.sql script. i am geting error.
    SELECT version_script AS file_name FROM DUAL
    ERROR at line 1:
    ORA-20000: Upgrade not supported from version
    ORA-06512: at "SYS.VERSION_SCRIPT", line 52
    Please help me.
    AT

    Strange. Metalink doc 316889.1 says you should be able to upgrade following versions directly to 10.2.0.3.0
    8.1.7.4 -> 10.2.X.X.X
    9.0.1.4 or 9.0.1.5 -> 10.2.X.X.X
    9.2.0.4 or higher -> 10.2.X.X.X
    10.1.0.2 or higher -> 10.2.X.X.X
    Not too sure but may be you need to contact Oracle support.

  • Oracle 10g to 11g Upgrade - Oracle Clusterware problem

    Oracle10g RAC (2 Nodes) RHEL 4 64bit
    Hi All,
    I have began the procedure for upgrading Oracle Clusterware to 11g. However, during the install OUI was giving me certain error messages like it couldn't transfer the OUI installlogs to node 2. Well, I kept pushing through the install and after I ran the last rootupgrade script on node 2 it gave me the following error:
    Checking the existence of nodeapps on this node
    Exception in thread "main" java.lang.UnsupportedClassVersionError: oracle/ops/opsctl/OPSCTLDriver (Unsupported major.minor version 49.0)
    at java.lang.ClassLoader.defineClass0(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    Creating '/crs/home/install/paramfile.crs' with data used for CRS configuration
    Exception in thread "main" java.lang.UnsupportedClassVersionError: oracle/ops/opsctl/OPSCTLDriver (Unsupported major.minor version 49.0)
    at java.lang.ClassLoader.defineClass0(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    Failed to retrieve VIP details
    Exception in thread "main" java.lang.UnsupportedClassVersionError: oracle/ops/opsctl/OPSCTLDriver (Unsupported major.minor version 49.0)
    at java.lang.ClassLoader.defineClass0(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    Failed to retrieve VIP details
    Setting CRS configuration values in /crs/home/install/paramfile.crs
    So I ignored the error for the time being and after that I checked the status of crs and it gave me the following:
    [oracle@vtl-rac2 crsd]$ crsstatus
    HA Resource Target State
    ora.VMRACDEV.VMRACDEV1.inst ONLINE ONLINE on vtl-rac1
    ora.VMRACDEV.VMRACDEV2.inst ONLINE ONLINE on vtl-rac2
    ora.VMRACDEV.db ONLINE ONLINE on vtl-rac1
    ora.vtl-rac1.ASM1.asm ONLINE ONLINE on vtl-rac1
    ora.vtl-rac1.LISTENER_VTL-RAC1.lsnr ONLINE ONLINE on vtl-rac1
    ora.vtl-rac1.gsd ONLINE ONLINE on vtl-rac1
    ora.vtl-rac1.ons ONLINE OFFLINE
    ora.vtl-rac1.vip ONLINE ONLINE on vtl-rac1
    ora.vtl-rac2.ASM2.asm ONLINE ONLINE on vtl-rac2
    ora.vtl-rac2.LISTENER_VTL-RAC2.lsnr ONLINE ONLINE on vtl-rac2
    ora.vtl-rac2.gsd ONLINE ONLINE on vtl-rac2
    ora.vtl-rac2.ons ONLINE OFFLINE
    ora.vtl-rac2.vip ONLINE ONLINE on vtl-rac2
    So i tried to bring it back up by doing a crs_stop -all and crs_start -all and it gave me the following error:
    vtl-rac1 : CRS-1019: Resource ora.vtl-rac2.ons (application) cannot run on vtl-rac1
    Start of `ora.vtl-rac1.ons` on member `vtl-rac1` failed.
    vtl-rac2 : CRS-1019: Resource ora.vtl-rac1.ons (application) cannot run on vtl-rac2
    CRS-0223: Resource 'ora.VMRACDEV.db' has placement error.
    CRS-0215: Could not start resource 'ora.vtl-rac1.ons'.
    CRS-0215: Could not start resource 'ora.vtl-rac2.ons'.
    I am thinking that all of this is caused by the various issues I had with the install. If I am incorrect, then please let me know. If it is true, I would like to know if there are any 11g docs on how to clean up a failed clusterware upgrade. Any advice would be greatly appreciated on any of the situations I am having.
    Thank you

    Hi Chandra,
    Did CVU report any problems before the upgrade?No, there were no errors reported by CVU before the upgrade.
    I don't there is note out there for cleaning 11g CRS
    install...and I think can very use the 10g CRS note -
    239998.1.Yeah I might have to go that way.
    I have both the 11g CRS install and upgrade from 10g
    to 11CRS at
    http://chandradba.blogspot.com/2007/08/oracle-11g-rac-
    install-on-red-hat-50.html
    and
    http://chandradba.blogspot.com/2008/02/oracle-10g-crs-
    upgrade-to-11g-crs.html
    see if it helps.Yup, your guide is very simple, clear and error proof :) That's how mine when pretty much except right around 75% I started getting these strange errors of files not being able to be transferred to node 2. Anyways, it shouldn't be a problem as none of those errors were configuration related...or else I would have a messed up cluster.
    Well, I actually rebooted both machines and now the whole CRS stack is up!! So I guess I am ok. We'll just have to wait and see.
    Thanks for your help Chandra...I always appreciate it.

  • Closing Oracle Background Engine Window.

    Hello,
    I am working on Oracle Reports 6.0. When I run any report Oracle Background Engine Window opens & show which report is running. But after closing report still that window remains as it is. It there any way to close that window onces I complited report.
    null

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Vijay ([email protected]):
    Hello,
    I am working on Oracle Reports 6.0. When I run any report Oracle Background Engine Window opens & show which report is running. But after closing report still that window remains as it is. It there any way to close that window onces I complited report.
    <HR></BLOCKQUOTE>
    I guess it's designed so that it does not have to reload the Background Engine everytime you run the next report.
    Maybe in your case you do not run reports frequently, but in our office report runs are quite often so it's a feature that is quite welcomed.
    null

  • Error while upgrading Oracle SOA 10.1.3.3 to 10.1.3.5

    Hi,
    Iam trying to upgrade Oracle SOA ver.10.1.3.3 to 10.1.3.5 on a windows server.The following steps were followed.
    1. SOA was stopped. Back up of the SOA folder was taken.
    2. SOA uses the default Olite database. Connected to the BPEL schema and run the upgrade_10133_10135_olite.sql script.
    It errored out in the upgrade process of 10.1.3.3 to 10.1.3.4.
    The esb schema upgrade script executed without error. Have any one faced similar issue? or aware of the reason? Please help me out. Thanks in advance.
    The following is the log:
    SQL> @E:\Downloads\Installables\p8626084_101350_WINNT\Disk1\install\soa_schema_upgrade\bpel\scripts\upgrade_10133_10135_olite.sql
    SQL> SET FEEDBACK 1
    SQL> SET NUMWIDTH 10
    SQL> SET LINESIZE 80
    SQL> SET TRIMSPOOL ON
    SQL> SET TAB OFF
    SQL> SET PAGESIZE 100
    SQL> @@upgrade_10133_10134_olite.sql
    SQL> Rem
    SQL> Rem $Header: bpel/everest/src/modules/server/database/scripts/upgrade_10133_10134_olite.sql /st_pcbpel_10.1.3.1/11 2009/06/03 00:37:24 nverma Exp $
    SQL> Rem
    SQL> Rem upgrade_10133_10134_olite.sql
    SQL> Rem
    SQL> Rem Copyright (c) 2008, 2009, Oracle and/or its affiliates.
    SQL> Rem All rights reserved.
    SQL> Rem
    SQL> Rem NAME
    SQL> Rem upgrade_10133_10134_olite.sql - <one-line expansion of the name>
    SQL> Rem
    SQL> Rem DESCRIPTION
    SQL> Rem This script can be used to upgrade orabpel schema on olite database from 10.1.3.3.0 to 10.1.3.4.0
    SQL> Rem
    SQL> Rem NOTES
    SQL> Rem This script can be used to upgrade orabpel schema on olite database from 10.1.3.3.0 to 10.1.3.4.0
    SQL> Rem
    SQL> Rem MODIFIED (MM/DD/YY)
    SQL> Rem nverma 04/27/09 - Backport nverma_bug-8463393 from
    SQL> Rem nverma 04/14/09 - Backport nverma_bug-7171739 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem ramisra 06/05/08 -
    SQL> Rem ralmuell 03/28/08 - Sensor schema change for 6819678
    SQL> Rem ramisra 03/17/08 - Backport ramisra_bug-6845586 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem atam 03/06/08 - update version
    SQL> Rem nverma 01/29/08 - Upgrade script (10.1.3.3.0 to 10.1.3.4.0) for orabpel schema on olite
    SQL> Rem database.
    SQL> Rem nverma 01/29/08 - Created
    SQL> Rem
    SQL> SET ECHO ON
    SQL> SET FEEDBACK 1
    SQL> SET NUMWIDTH 10
    SQL> SET LINESIZE 80
    SQL> SET TRIMSPOOL ON
    SQL> SET TAB OFF
    SQL> SET PAGESIZE 100
    SQL> ALTER TABLE DLV_MESSAGE MODIFY (CONV_ID VARCHAR2(256))
    Table altered
    SQL> ALTER TABLE DLV_SUBSCRIPTION DROP CONSTRAINT DS_PK
    Table altered
    SQL> ALTER TABLE DLV_SUBSCRIPTION MODIFY (CONV_ID VARCHAR2(256))
    Table altered
    SQL> ALTER TABLE DLV_SUBSCRIPTION ADD CONSTRAINT DS_PK PRIMARY KEY(CONV_ID, SUBSCRIBER_ID)
    Table altered
    SQL> ALTER TABLE INVOKE_MESSAGE MODIFY (CONV_ID VARCHAR2(256))
    Internal Error:thinExecute: Result Communication Failed
    SQL> ALTER TABLE INVOKE_MESSAGE MODIFY (MASTER_CONV_ID VARCHAR2(256))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE NATIVE_CORRELATION MODIFY (CONVERSATION_ID VARCHAR2(1000))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE NATIVE_CORRELATION MODIFY (NATIVE_CORRELATION_ID VARCHAR2(1000))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE CUBE_INSTANCE MODIFY (CONVERSATION_ID VARCHAR2(256))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE TASK MODIFY (CONVERSATION_ID VARCHAR2(256))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE WORK_ITEM MODIFY (CUSTOM_ID VARCHAR2(256))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE DLV_SUBSCRIPTION DROP CONSTRAINT DS_PK
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE DLV_SUBSCRIPTION MODIFY (SUBSCRIBER_ID VARCHAR2(256))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE DLV_SUBSCRIPTION ADD CONSTRAINT DS_PK PRIMARY KEY(CONV_ID, SUBSCRIBER_ID)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE DLV_MESSAGE MODIFY (RES_SUBSCRIBER VARCHAR2(256))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> CREATE INDEX DDMR_DOCKEY ON DOCUMENT_DLV_MSG_REF(DOCKEY)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> CREATE INDEX CI_CUSTOM4 ON CUBE_INSTANCE (MODIFY_DATE)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE WFUserTaskViewGrant ADD ( granteeType VARCHAR2(20), applicationContext VARCHAR2(200) )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table cube_instance add ( at_count_id integer, at_event_id integer, at_detail_id integer )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values add error_message_temp clob
    Internal Error:AllocStatement: Request Communication Failed
    SQL> update activity_sensor_values set error_message_temp=error_message
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values drop column error_message
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values add error_message clob
    Internal Error:AllocStatement: Request Communication Failed
    SQL> update activity_sensor_values set error_message=error_message_temp
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values drop column error_message_temp
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values drop column error_message_temp
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table fault_sensor_values drop primary key
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table variable_sensor_values drop primary key
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values drop primary key cascade
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values add constraint activity_sensor_pk primary key(id, process_instance_id)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table variable_sensor_values add constraint variable_sensor_pk primary key(id, process_instance_id)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table variable_sensor_values add constraint variable_sensor_fk1 foreign key(activity_sensor_id, process_instance_id) references activity_sensor_values(id, process_instance_id)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table fault_sensor_values add constraint fault_sensor_pk primary key(id, process_instance_id)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values modify constraint activity_sensor_pk enable
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table variable_sensor_values modify constraint variable_sensor_pk enable
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table variable_sensor_values modify constraint variable_sensor_fk1 enable
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table fault_sensor_values modify constraint fault_sensor_pk enable
    Internal Error:AllocStatement: Request Communication Failed
    SQL> drop index activity_sensor_values_indx
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create index activity_sensor_values_indx on activity_sensor_values(process_instance_id, sensor_name, action_name)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> update version set guid = '10.1.3.4.0'
    Internal Error:AllocStatement: Request Communication Failed
    SQL> update version_server set guid = '10.1.3.4.0'
    Internal Error:AllocStatement: Request Communication Failed
    SQL> COMMIT
    Internal Error:AllocStatement: Request Communication Failed
    SQL> @@upgrade_10134_10135_olite.sql
    SQL> Rem Copyright (c) 2008, 2009, Oracle and/or its affiliates.
    SQL> Rem All rights reserved.
    SQL> Rem
    SQL> Rem NAME
    SQL> Rem
    SQL> Rem DESCRIPTION
    SQL> Rem
    SQL> Rem NOTES
    SQL> Rem <other useful comments, qualifications, etc.>
    SQL> Rem
    SQL> Rem MODIFIED (MM/DD/YY)
    SQL> Rem vnanjund 07/09/09 - Backport vnanjund_bug-8655721 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem mchinnan 07/07/09 - Backport mchinnan_bug-8636836 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem vnanjund 07/06/09 - olite fix
    SQL> Rem mchmiele 07/02/09 - Backport mchmiele_bug-8613538 from
    SQL> Rem mchmiele 07/01/09 - Backport mchmiele_bug-8613538 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem mchmiele 06/30/09 - Migrating processes with correlation sets
    SQL> Rem mchmiele 06/30/09 - Backport mchmiele_bug-8613538 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem mchmiele 06/29/09 - Olite resource tables
    SQL> Rem mchmiele 06/29/09 - Backport mchmiele_bug-8613538 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem ramisra 05/11/09 - Backport ramisra_bug-8498498 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem nverma 04/27/09 - Backport nverma_bug-8463393 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem mnanal 03/09/09 - Backport mnanal_bug-7286083 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem mnanal 02/10/09 - RFI bug 7022475
    SQL> Rem ramisra 01/02/09 - Backport ramisra_bug-7577303 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem ramisra 09/17/08 - Created
    SQL> Rem
    SQL> SET ECHO ON
    SQL> SET FEEDBACK 1
    SQL> SET NUMWIDTH 10
    SQL> SET LINESIZE 80
    SQL> SET TRIMSPOOL ON
    SQL> SET TAB OFF
    SQL> SET PAGESIZE 100
    SQL> -- Update version
    SQL> --
    SQL> update version set guid = '10.1.3.5.0' where dbtype = 'olite'
    Internal Error:AllocStatement: Request Communication Failed
    SQL> commit
    Internal Error:AllocStatement: Request Communication Failed
    SQL> CREATE table temp_attachment ( key varchar2( 50 ), bin blob )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> INSERT into temp_attachment (key,bin) SELECT key, bin FROM attachment
    Internal Error:AllocStatement: Request Communication Failed
    SQL> DROP table attachment
    Internal Error:AllocStatement: Request Communication Failed
    SQL> CREATE table attachment ( key varchar2( 50 ), content_type varchar2( 50 ), bin blob, constraint att_pk primary key( key ) )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> INSERT into attachment (key,bin) SELECT key, bin FROM temp_attachment
    Internal Error:AllocStatement: Request Communication Failed
    SQL> DROP table temp_attachment
    Internal Error:AllocStatement: Request Communication Failed
    SQL> DELETE FROM WFRoutingSlip rs WHERE NOT EXISTS (SELECT 1 FROM WFTask t WHERE t.taskid = rs.taskid)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE WFRoutingSlip ADD CONSTRAINT RoutingSlipTaskConstraint FOREIGN KEY (taskId) REFERENCES WFTask (taskId) ON DELETE CASCADE
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE process_descriptor ADD (last_change_time NUMBER(38))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> UPDATE process_descriptor SET last_change_time=(SELECT (SYSDATE - TO_DATE('01-01-1970','DD-MM-YYYY')) * (24*60*60*1000) FROM DUAL)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create index WFTaskTaskGroupId_I on WFTask(taskGroupId)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create index WFTaskWorkflowPattern_I on WFTask(workflowPattern)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> DELETE FROM domain_properties WHERE prop_id IN ( 'dspMinThreads' , 'dspMaxThreads', 'dspInvokeAllocFactor' )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE dlv_subscription ADD ( partner_link VARCHAR2(256) )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> UPDATE VERSION SET guid = '10.1.3.5.0'
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table WFTaskTimer add key varchar(100)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table WFAttachment modify (encoding varchar(100))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE dlv_subscription DROP CONSTRAINT ds_pk
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE dlv_subscription ADD CONSTRAINT ds_pk PRIMARY KEY (subscriber_id)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> DROP INDEX ds_conversation
    Internal Error:AllocStatement: Request Communication Failed
    SQL> CREATE INDEX ds_conversation ON dlv_subscription( conv_id )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> DROP INDEX ds_operation
    Internal Error:AllocStatement: Request Communication Failed
    SQL> CREATE INDEX ds_operation ON dlv_subscription( process_id, operation_name )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> drop table cx_resource
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create table cx_resource ( id integer, pid integer, name varchar(64), kind char(1), modify_date timestamp default sysdate, constraint cx_resource_pk primary key( id ), constraint cx_resource_no_dups_pk unique (pid,name) )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create index cx_resource_name_idx on cx_resource (name)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create index cx_resource_pid_idx on cx_resource (pid)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> drop table cx_content
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create table cx_content ( id integer, /* id of the resource content, pointing to Resource.id */ content blob, /* the content as a blob */ constraint cx_content_pk primary key( id ) )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> -- Add debugger tables
    SQL> --
    SQL> @@debugger_olite.ddl
    E:\Downloads\Installables\p8626084_101350_WINNT\Disk1\install\soa_schema_upgrade\bpel\scripts\debugger_olite.ddl (The system cannot find the file specified)
    SQL> ALTER TABLE work_item ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE dlv_subscription ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE ci_indexes ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE wi_exception ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE wi_fault ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE document_ci_ref ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE audit_trail ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE audit_details ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE cube_scope ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE attachment ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE attachment_ref ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE document_dlv_msg_ref ADD (dlv_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE xml_document ADD (doc_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create or replace view admin_list_cx as select ci.cikey, domain_ref as ci_domain_ref, process_id, revision_tag, creation_date ci_creation_date, creator ci_creator, modify_date ci_modify_date, modifier ci_modifier, state ci_state, priority ci_priority, title, status, stage, conversation_id, metadata, root_id, parent_id, test_run_id, index_1, index_2, index_3, index_4, index_5, index_6, ci.test_run_id from cube_instance ci, ci_indexes cx where ci.cikey = cx.cikey (+)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> COMMIT
    Internal Error:AllocStatement: Request Communication Failed

    Hi,
    IF ORACLE DATABASE HAS ALREADY HAS ORABPEL AND ORAESB USERS, I don't know password.:
    My remarks. If you upgrade a SOA suite to a higher version, you always need to known the passwords of the Oracle dehydration store (orabpel/orawsm/oraesb). If you do not know that, call your DBA. Otherwise try: the same password as the user name or try 'welcome1'. You could also force to change the password via the system user; alter user <user> identified by <password>;
    IS IT A GOOD IDEA TO UPGRADE Oracle SOA 10.1.3.1.0 to Oracle SOA 10.1.3.4.0?
    Yes! 10.1.3.4 is the succeeder of 10.1.3.3, in the beginning of next year 10.1.3.5 (with WLS 10.3) will come out. Note if you use 10.1.3.4 download also the latest patchset from metalink.
    Marc
    http://oroasoa.blogspot.com

Maybe you are looking for