Announcement

Collapse
No announcement yet.

Trouble with 5.5 CU6 on the way to 6.1 Upgrade

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Trouble with 5.5 CU6 on the way to 6.1 Upgrade

    Hello All,

    We are on OTM 5.5 CU5 in PROD. We are in the process of moving to OTM 6.1. In DEV, we need to get to 5.5 CU6 before we can go directly to 6.1.
    OS: Red Hat Enterprise 64-bit
    Database: Oracle 11.2 64-bit
    App: OAS
    Web: Apache/Tomcat

    We are just trying to get our DEV environment upgraded from 5.5 CU5 to 5.5 CU6. We had trouble running dbpatch_55.sql after applying the CU6 bin. The CSV update portion of dbpatch_55 crashed with jdbc errors. My OS admins got me past the JDBC problem by pointing the otm user to a standard java 1.6 JDK. The dbpatch_55.sql took almost 5 hours to run, with the CSV updates being the bottleneck. After it finally finished, the app server errored out on startup complaining about an invalid 'jrockit' option. I'm worried that they are taking the wrong path trying to use a 1.6 jdk on our app/web server with OTM 5.5. A couple questions:
    - on OTM 5.5 CU6, should we definitely be using the 1.4.2 jrockit JDK for OAS/Apache/Tomcat?
    - does the OTM 5.5 CU6 bin file on linux add the sourcing of the gc3env.sh into the app owner's .profile? We have an application startup menu on our app owner account's profile, and the . ./gc3env.sh line appears after the startup menu, so would not take effect. I'm wondering if the solution was as simple as moving that line above the startup menu in the app owner's profile.
    - The JDK in the Oracle Home of the database server has absolutely nothing to do with incoming jdbc connections, right?

    This is a bit of a ramble, but thanks in advance if you can help me out
    Joe Patton

    Technical Specialist, DB2-Oracle DBA
    Database Management and Support
    Parker Hannifin Corporation

  • #2
    Re: Trouble with 5.5 CU6 on the way to 6.1 Upgrade

    Update: we ended up downloading/installing 64-bit 1.5 jrockit jdk and OAS started successfully. All we were trying to do was get 5.5 CU6 operational so we could go to 6.1(which will switch us to the Weblogic app server). One other thing that tripped us up is while we were trying different JDK's, we weren't aware that dms.jar is shipped only with the app server, but the ojdbc dms jars need it in the path.
    Joe Patton

    Technical Specialist, DB2-Oracle DBA
    Database Management and Support
    Parker Hannifin Corporation

    Comment


    • #3
      Re: Trouble with 5.5 CU6 on the way to 6.1 Upgrade

      Good deal. Now that you're on v6.1, you should have WL running under the 64-bit version of JRockit 1.6. I'm sure you know this, but it may help others.

      --Chris

      Comment

      Working...
      X