EM Java Support was (jdk16 to jdk17 frustration)
Date: Mon, 7 Mar 2016 09:09:00 +0000
Message-ID: <CABe10sbMZMLv7Txmhr+LwRW+OmOe==JWDBD0=E6mxmMSx3uyLQ_at_mail.gmail.com>
For various reasons, most of which I'm not entirely happy with, we'll be applying every current appropriate PSU to our EM software stack (hey,at least, we have a non-prod EM on which to screw up). I don't know if this was the root of Dave's frustrations - it looks like some bad advice from support in his case, but I can understand it if it was.
The "natural" to me approach was to look at Note 2074802.1 <https://support.oracle.com/epmos/faces/DocumentDisplay?id=2074802.1> (Patch Set Update and Critical Patch Update Availability Document January 2016) . That has a section for each release of EM.
In the EM section we have a table that includes *Base Platform Fusion
Middleware home *that refers us to the WebLogic part of the same document
that includes *Oracle Java SE home *that in turn contains a link to Note
1492980.1: How to Maintain the Java SE Installed or Used with FMW 11g
Products
<https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&sourceId=2074802.1&id=1492980.1>
which
says contrary to the note Courtney references below.
"*It is always supported to update the JDK/JRE to the latest minor version
> of an installed release" *
In addition, the FMW note references the procedure Dave describes of installing in a new home and updating the java path in various files. The EM specific note suggests backing up the old JDK and replacing with the new one.
For anyone like me who may have to patch the entire EM stack, it would be nice if MOS had a note along the lines of 1492980.1 *Note XXXXXX.1 How to maintain the EM software stack*, rather than a set of links to notes designed for each component from which one has to reconstruct the whole picture. That would also likely be useful for cases such as Dave's.
On Thu, Feb 11, 2016 at 7:35 PM, Courtney Llamas <courtney.llamas_at_oracle.com
> wrote:
> Have you contacted support? EM 12.1.0.x does not support JDK 1.7, you
> can only go to the latest of JDK 1.6…
>
>
>
> [image: https://mosemp.us.oracle.com/epmos/adf/images/t.gif]
>
> *How to Upgrade JDK to 1.6 Update 95 on OMS 12.1.0.4 or 12.1.0.5 (Doc ID
> 2059426.1)*
>
>
>
>
>
> *From:* Timur Akhmadeev [mailto:timur.akhmadeev_at_gmail.com]
> *Sent:* Thursday, February 11, 2016 2:00 AM
>
> *To:* Herring, David
> *Cc:* oracle-l_at_freelists.org
> *Subject:* Re: jdk16 to jdk17 frustration
>
>
>
> In this case I'd try to find something more from emctl logs/trace files if
> those are available. Looks like there are ways to configure them:
> https://blogs.oracle.com/EMMAA/entry/maintaining_trace_and_log_files
>
> Depending on what/how exactly emctl tries to start and where exactly this
> fails you can go further.
>
>
>
> Also I'd try to start NM manually directly and see if this works or not,
> what's in logs, etc.
>
>
>
> On Wed, Feb 10, 2016 at 8:10 PM, Herring, David <HerringD_at_dnb.com> wrote:
>
> I'm actually not starting NM directly but indirectly from the OMS start ->
> $OMS_HOME/bin/emctl start oms. The various components start until it gets
> to NM and that's when it fails. This happens shortly after the Webtier
> starts and I've confirmed this by using "strace" to track progress as best
> I can. In the output I can see opmn commands completing but then not a
> whole lot of help until NM fails. The NM process actually gets created but
> that's it.
>
>
>
> Regards,
>
>
>
> Dave
>
>
>
> *From:* Timur Akhmadeev [mailto:timur.akhmadeev_at_gmail.com]
> *Sent:* Wednesday, February 10, 2016 1:47 AM
> *To:* Herring, David
> *Cc:* oracle-l_at_freelists.org
> *Subject:* Re: jdk16 to jdk17 frustration
>
>
>
> Hi,
>
>
>
> so you try to start NM and it fails with NoClassDefFoundError?
>
> can you show full texts of how you actually start Node Manager and full
> content of its out files right from the start.
>
>
>
> On Wed, Feb 10, 2016 at 2:01 AM, Herring, David <HerringD_at_dnb.com> wrote:
>
> Folks, I have an SR open w/ Oracle that appears to be going nowhere so I'm
> hoping that someone can at least lead me in a direction where I'll make
> progress. Here's the situation (all in the context of EM 12c):
>
> · We're having issues with our WL Admin console page and I opened
> an SR to resolve the problem.
>
> · I was told to upgrade JDK which should resolve the problem.
> Right now our various versions in the EM stack are:
>
> o OMS 12.1.0.5.160119
>
> o WebLogic 10.3.6.0.13
>
> o JDK 1.6.0_43
>
> · In trying to upgrade to JDK 1.7.0_95 I wanted to avoid a
> release-specific path. Right now JDK1.6 sits under $MW_HOME/jdk16/jdk. As
> part of the move to JDK1.7 I want to start using $MW_HOME/jdk, as I'm
> assuming in the future any JDK upgrades would be specific to FMW for EM.
>
> · I followed MOS docs 1309855.1 and 1616397.1 to make sure I
> covered everything necessary. As far as I can tell all that's involved is
> stopping processes, plopping the new release in a directory, updating key
> files to point to this new directory and start everything back up.
>
>
>
> When I start up the OMS I get the following:
>
>
>
> Node Manager Could Not Be Started
>
> Check Node Manager log file for details:
> .../NodeManager/emnodemanager/nodemanager.log
>
> Oracle Management Server is Down
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> oracle/jdbc/OraclePreparedStatement
>
>
>
> The nodemanager.log file isn't very helpful, giving me the following over
> and over:
>
>
>
> <Feb 9, 2016 6:58:59 AM> <WARNING> <I/O error while closing socket
> connection>
>
> java.net.SocketException: Connection reset
>
> ...
>
>
>
> Has anyone successfully upgraded the JDK and in the process moved
> $JAVA_HOME to a new location from the base install of EM? Does anyone know
> a way to get more information out of NM as to why he's failing?
>
>
>
> I'm sure someone is going to ask:
>
> · Why are you upgrading JDK? The whole EM stack is suppose to be
> a black box? Answer: I'd love to NOT upgrade JDK but it's per a request of
> Oracle to resolve a different issue.
>
> · Why place the new JDK under $MW_HOME? Why not keep it
> completely out of the EM software directories? Answer: I can see the point
> and to tell the truth I didn't think of that initially. Currently this is
> an EM-only host so JDK has no point other than with EM.
>
>
>
> Regards,
>
>
>
> Dave
>
>
>
>
>
> --
>
> Regards
> Timur Akhmadeev
>
>
>
>
>
> --
>
> Regards
> Timur Akhmadeev
>
-- Niall Litchfield Oracle DBA http://www.orawin.infoReceived on Mon Mar 07 2016 - 10:09:00 CET
-- http://www.freelists.org/webpage/oracle-l