Announcement

Collapse
No announcement yet.

OTM CU3 upgrade to CU4

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

  • OTM CU3 upgrade to CU4

    Hi Gurus,

    We are on OTM CU3
    with OTM applications on HP-PARISC(64-bit) and OTM databse on HP-ITANIUM(64-bit).

    HP-PARISC(64-bit) HP-UX B.11.23
    HP-ITANIUM(64-bit) HP-UX B.11.23

    and now we would like to go for the upgrade of OTM CU3 to OTM CU4.
    1) Is the CU4 update patch released for the above mentioned ?
    2) as metioned in OTMFAQ, Patchset 6705191 is released for Linux x86, HP-PARISC 10.20 platform...but not for the above platform?
    do we have to wait for the CU4 patch to be released or istheir any way?

    regards,
    sandeep kiran.J

  • #2
    Re: OTM CU3 upgrade to CU4

    Sandeep,

    Yes, the OTM v5.5 CU04 patch has been released for HP-UX, though is seems that they simply mis-categorized it as HP-UX 10.20. There's only one version of the patch for HP-UX (6705191). If you're running OAS (rather than WebLogic), then you should also apply patch 6759308.

    --Chris

    Comment


    • #3
      Re: OTM CU3 upgrade to CU4

      hi Chris,

      when should i apply the patch 6759308(oc4j)?

      1)I have applied the patch 6705191.
      2)db....dbpatch55.sql executed without errors.
      3)NOw should i bring up the OTM or apply the patch 6759308. As patch has to be applied on top of CU4
      please confirm on these things
      ******************************************
      I have applied the patch 6759308. And started OTM services
      otmapp55 start...went on fine, even checked logs to confirm. But, when i start the otmweb55 it hangs no log is created.what would be my next move.

      I have checked the GC3App folder it has deployed till gc3deploy65 and after that i.e till gc3deploy69 there is no deployment.
      # ./otmweb55 start
      Waiting for App Server to finish startup


      thanks
      sandeep
      Last edited by sandeep kiran kumar; March 31, 2008, 11:58.

      Comment


      • #4
        Re: OTM CU3 upgrade to CU4

        Sandeep,

        I'm not sure what you mean by the following, can you explain in more detail?
        I have checked the GC3App folder it has deployed till gc3deploy65 and after that i.e till gc3deploy69 there is no deployment.
        What are gc3deploy65 and gc3deploy69?

        If the OTM Web startup never gets past the "Waiting for App Server to finish startup" line, then it means that it's waiting for the OTM Application server to respond on a designated port. To troubleshoot this, look at your otmweb55 script and see what hostname/port it's waiting for -- then ensure this matches your OTM App server. This may be caused by a typo during the installation process.

        --Chris

        Comment


        • #5
          Re: OTM CU3 upgrade to CU4

          Chris,

          Scenerio: Upgraded OTM5.5 CU3 to CU4 and OAS to 10.1.3.3

          OAS is configured on default ports as below
          OC4J HTTP Port =8888OC4J ORMI Port =23791JMS Server Port=9127

          # netstat -an|grep 23791
          tcp 0 0 127.0.0.1.23791 *.* LISTEN
          # netstat -an|grep 8888
          tcp 0 0 127.0.0.1.8888 *.* LISTEN
          # netstat -an|grep 9127
          tcp 0 0 *.9127 *.* LISTEN
          #

          From glog.properties
          ==============
          # application server URL and port
          appserver=picasso.go2uti.com
          appserver.port=23791/GC3App

          Tried starting otm web services commenting out the line
          $JAVA_HOME/bin/java glog.util.admin.WaitForServer picasso.go2uti.com 23791

          OTM Web services - Tomcat & Apache came up fine.

          Tomcat console says - OTM Application Server is not available.

          tomcat console.log file content
          ====================
          INFO | jvm 1 | 2008/04/01 11:17:53 | Created MBeanServer with ID: 6025e7:1190886fa89:-8000icasso.go2uti.com:1
          INFO | jvm 1 | 2008/04/01 11:17:55 | Apr 1, 2008 11:17:55 AM org.apache.catalina.startup.Catalina load
          INFO | jvm 1 | 2008/04/01 11:17:55 | INFO: Initialization processed in 1222 ms
          INFO | jvm 1 | 2008/04/01 11:17:55 | Apr 1, 2008 11:17:55 AM org.apache.catalina.core.StandardService start
          INFO | jvm 1 | 2008/04/01 11:17:55 | INFO: Starting service Catalina
          INFO | jvm 1 | 2008/04/01 11:17:55 | Apr 1, 2008 11:17:55 AM org.apache.catalina.core.StandardEngine start
          INFO | jvm 1 | 2008/04/01 11:17:55 | INFO: Starting Servlet Engine: Apache Tomcat/5.5.16
          INFO | jvm 1 | 2008/04/01 11:17:55 | Apr 1, 2008 11:17:55 AM org.apache.catalina.core.StandardHost start
          INFO | jvm 1 | 2008/04/01 11:17:55 | INFO: XML validation disabled
          INFO | jvm 1 | 2008/04/01 11:17:59 | Apr 1, 2008 11:17:58 AM org.apache.catalina.core.ApplicationContext log
          INFO | jvm 1 | 2008/04/01 11:17:59 | INFO: Marking servlet Initialize as unavailable
          INFO | jvm 1 | 2008/04/01 11:17:59 | Apr 1, 2008 11:17:58 AM org.apache.catalina.core.StandardContext loadOnStartup
          INFO | jvm 1 | 2008/04/01 11:17:59 | SEVERE: Servlet /GC3 threw load() exception
          INFO | jvm 1 | 2008/04/01 11:17:59 | javax.servlet.UnavailableException: The OTM Application Server is not available.
          INFO | jvm 1 | 2008/04/01 11:17:59 | at glog.webserver.util.BaseServlet.init(BaseServlet.j ava:401)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.apache.catalina.core.StandardWrapper.loadServl et(StandardWrapper.java:1105)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.apache.catalina.core.StandardWrapper.load(Stan dardWrapper.java:932)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.apache.catalina.core.StandardContext.loadOnSta rtup(StandardContext.java:3917)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.apache.catalina.core.StandardContext.start(Sta ndardContext.java:4197)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.apache.catalina.core.ContainerBase.start(Conta inerBase.java:1013)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.apache.catalina.core.StandardHost.start(Standa rdHost.java:71
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.apache.catalina.core.ContainerBase.start(Conta inerBase.java:1013)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.apache.catalina.core.StandardEngine.start(Stan dardEngine.java:442)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.apache.catalina.core.StandardService.start(Sta ndardService.java:450)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.apache.catalina.core.StandardServer.start(Stan dardServer.java:709)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.apache.catalina.startup.Catalina.start(Catalin a.java:551)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at java.lang.reflect.Method.invoke(Method.java:324)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.apache.catalina.startup.Bootstrap.start(Bootst rap.java:275)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.apache.catalina.startup.Bootstrap.main(Bootstr ap.java:413)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at java.lang.reflect.Method.invoke(Method.java:324)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at org.tanukisoftware.wrapper.WrapperStartStopApp.run (WrapperStartStopApp.java:159)
          INFO | jvm 1 | 2008/04/01 11:17:59 | at java.lang.Thread.run(Thread.java:534)
          INFO | jvm 1 | 2008/04/01 11:18:00 | [GC
          INFO | jvm 1 | 2008/04/01 11:18:00 | 209792K->32246K(1023424K), 0.2929161 secs]
          INFO | jvm 1 | 2008/04/01 11:18:02 | [GC
          INFO | jvm 1 | 2008/04/01 11:18:02 | 242038K->61915K(1023424K), 0.5158889 secs]
          INFO | jvm 1 | 2008/04/01 11:18:05 | [GC
          INFO | jvm 1 | 2008/04/01 11:18:05 | 271707K->91277K(1023424K), 0.5370416 secs]
          INFO | jvm 1 | 2008/04/01 11:18:05 | Apr 1, 2008 11:18:05 AM org.apache.jk.common.ChannelSocket init
          INFO | jvm 1 | 2008/04/01 11:18:05 | INFO: JK: ajp13 listening on /10.103.106.18:8009
          INFO | jvm 1 | 2008/04/01 11:18:05 | Apr 1, 2008 11:18:05 AM org.apache.jk.server.JkMain start
          INFO | jvm 1 | 2008/04/01 11:18:05 | INFO: Jk running ID=0 time=0/112 config=null
          INFO | jvm 1 | 2008/04/01 11:18:06 | Apr 1, 2008 11:18:06 AM org.apache.catalina.storeconfig.StoreLoader load
          INFO | jvm 1 | 2008/04/01 11:18:06 | INFO: Find registry server-registry.xml at classpath resource
          INFO | jvm 1 | 2008/04/01 11:18:06 | Apr 1, 2008 11:18:06 AM org.apache.catalina.startup.Catalina start
          INFO | jvm 1 | 2008/04/01 11:18:06 | INFO: Server startup in 11409 ms
          INFO | jvm 1 | 2008/04/01 11:19:30 | Apr 1, 2008 11:19:30 AM org.apache.catalina.core.ApplicationContext log
          INFO | jvm 1 | 2008/04/01 11:19:30 | INFO: Marking servlet glog.webserver.servlet.umt.Login as unavailable
          #

          OTM is unavailable after applying CU4 patch.

          Kindly help us resolving this upgrade issue.


          Thanks.

          Comment


          • #6
            Re: OTM CU3 upgrade to CU4

            From the information you've provided, it sounds like OAS may not be bound correctly. The netstat shows it listening on 127.0.0.1 (localhost):
            # netstat -an|grep 23791
            tcp 0 0 127.0.0.1.23791 *.* LISTEN
            But the startup scripts and glog configuration files are trying to connect to it via the hostname picasso.go2uti.com. Initially, it looks like a mis-match when installing.

            Was this working prior to the installation of CU4?

            Were the OAS configuration files manually modified, to make it listen on 127.0.0.1?

            Hope this helps!

            --Chris

            Comment


            • #7
              Re: OTM CU3 upgrade to CU4

              Hi Chris,

              Prior to CU4 upgrade everything was working fine.As mentioned before we had an upgrade from CU3 to CU4 and OTM 5.5 CU3 was up and running.

              Was this working prior to the installation of CU4?
              Yes.
              Were the OAS configuration files manually modified, to make it listen on 127.0.0.1?
              No.


              Regards
              sandeep

              Comment


              • #8
                Re: OTM CU3 upgrade to CU4

                Sandeep,

                In that case, I don't know why you're experiencing this error. From the netstat output, it's clear that OAS is now listening on localhost (127.0.0.1), but I can't imagine why the patch would make this change to your OAS configuration.

                I'd recommend opening an SR with Oracle. Once resolved, though, please report back here - as it may help others in the future!

                Thanks,
                --Chris

                Comment


                • #9
                  Re: OTM CU3 upgrade to CU4

                  Hi Chris,

                  Issue resolved
                  solution:

                  Before making changes
                  # netstat -an|grep 23791
                  tcp 0 0 127.0.0.1.23791 *.* LISTEN

                  Made an entry to the rmi.xml

                  /CRP2O/otmv55/oas/j2ee/home/config/rmi.xml
                  change host"10.103.106.18"
                  $ netstat -an|grep 23791
                  tcp 0 0 10.103.106.18.23791 *.* LISTEN

                  thanks
                  sandeep

                  Comment


                  • #10
                    Re: OTM CU3 upgrade to CU4

                    Sandeep,

                    Thanks for posting your solution. So I'm guessing that the line was previously set to "127.0.0.1" or "localhost"?

                    Strange that the CU did this -- I'd like to find out if others have had the same issue.

                    Good luck going forward!

                    --Chris

                    Comment

                    Working...
                    X