OCA will not launch and the CORBA service terminates with error 10015 (Doc ID 551791.1)

Last updated on OCTOBER 12, 2016

Applies to:

Oracle Communications ASAP - Version: 4.6.0 to 5.2.3 - Release: 4.6 to 5.2
Information in this document applies to any platform.
This issue concerns ASAP and the ORBIXD CORBA server.

***Checked for relevance on 09-Feb-2010***

Symptoms

The Customer cannot access the OCA either through the thick Windows client or through the WebLogic web page.

In the thick client the login process will time out. In the web client login screen the CORBA - CORB{$ENV_ID} - process may not be listed.

The ASAP command line tool, status, will not list the CORB{$ENV_ID} process or executing

ps -fe | grep corbaOCASvr

will not list any processes related to the faulty ASAP environment.

Also, the orbixd ORBIX process will likely not be running so

ps -fe | grep orbixd

will not list the process. NB: If there are multiple orbix processes on the server, others will be listed.

The customer can check the CORB{$ENV_ID}.diag files. At the end of the latest diagnostic file, "error 10015" will be reported and the corbaOCASvr process will then terminate.

Note, the Control server (CTRL) may attempt to restart the corbaOCASvr process at regular intervals - in which multiple instances of this error will be within the diagnostic files.

The customer can check the status of the orbixd server by executing the following command when logged into the ASAP environment:

catit -x $CORB

This should return a set of data similar to this example:

[28856:New Connection (srvpltestgcc1,IT_daemon,*,asapa1,pid=16189,optimised) ]


Server details for server : CORBPLA1

Comms : tcp
Code : cdr
Activation : shared
Owner : asapa1
Launch : ;all;
Invoke : ;all;
Well known port : 6593

Marker Launch Command

* -- Persistent Launch Only --

If the orbixd process is not running or not responding, repeated messages will occur. An example of this would be:

$ catit -x $CORB
[28869:Retrying connection to host `srvpltestgcc1' port 1771]
[28869:Retrying connection to host `srvpltestgcc1' port 1771]
[28869:Retrying connection to host `srvpltestgcc1' port 1771]
[28869:Retrying connection to host `srvpltestgcc1' port 1771]

Changes

The server may have recently been rebooted or there have been disk space or memory issues.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms