My Oracle Support Banner

OUD12C - After Applying Bundle Patch ( patch: 28492345) - Unable To Start OUD Instance Created In Domain (Doc ID 2520411.1)

Last updated on JULY 15, 2019

Applies to:

Oracle Unified Directory - Version and later
Information in this document applies to any platform.



After applying the Oct 2018 Bundle Patch ( patch: 28492345), when trying to start the existing instances following the same procedure:

./ oud1

It fails with below listed error:

Starting system Component oud1 ...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting 
Type help() for help on available commands

Reading domain from /$OUD_HOME/MiddleWare-Home/user_projects/domains/base_domain

Please enter Node Manager pswd:
Connecting to Node Manager ...
<Sep 14, 2018 12:00:33 AM PDT> <Info> <Security> <BEA-090905> <Disabling theCry.>
<Sep 14, 2018 12:00:33 AM PDT> <Info> <Security> <BEA-090906> <Changing thedefae this change, specify>
<Sep 14, 2018 12:00:33 AM PDT> <Info> <Security> <BEA-090909> <Using the configuostnameVerifier$NullHostnameVerifier.>
Successfully Connected to Node Manager.

Starting server oud1 ...
This Exception occurred at Fri Sep 14 00:00:47 PDT 2018.
weblogic.nodemanager.NMException: Received error message from Node Manager Serveed information.]. Please check Node Manager log for details.
Error: Error occurred while performing nmStart : Error Starting server oud1 : ReManager log for details.Use dumpStack() to view the full stacktrace :
Exiting WebLogic Scripting Tool.



 Apply OUD 12C Oct 18 Bundle Patch


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.