Searchctl to Start SES Mode 1 Gives: Error While Executing Action: "startall" Improper Listener Port:0 or Improper/ No listener.ora File (Doc ID 2134430.1)

Last updated on OCTOBER 12, 2018

Applies to:

Symptoms

When attempting to start SES using searchctl startall which is installed using mode 1 ,
the following error occurs.

<May 4, 2016 1:45:51 AM MDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Serv
ices GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 4, 2016 1:45:51 AM MDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Serv
ices GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 4, 2016 1:45:51 AM MDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted ce
rtificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 4, 2016 1:45:51 AM MDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading
of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 4, 2016 1:45:51 AM MDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For
authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the Al
gorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 4, 2016 1:45:51 AM MDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificat
e list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 4, 2016 1:45:51 AM MDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For auth
orized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.84
0.113549.1.1.11.>
The Oracle WebLogic NodeManager (E_app_middleware_wlserver) service is starting.
The Oracle WebLogic NodeManager (E_app_middleware_wlserver) service was started successfully.

The requested service has already been started.

More help is available by typing NET HELPMSG 2182.

Starting backend ...
listener.ora file is not found
[Ljava.lang.StackTraceElement;@ac1046

Error while executing action: "startall"

Improper Listener Port:0 or Improper/ No listener.ora File

Cause

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