OCA will not launch and the CORBA service terminates with error 10015
(Doc ID 551791.1)
Last updated on FEBRUARY 01, 2022
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.
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
Changes
The server may have recently been rebooted or there have been disk space or memory issues.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |