My Oracle Support Banner

Failed To Start Control Server After ASAP Installation (Doc ID 2909132.1)

Last updated on SEPTEMBER 04, 2024

Applies to:

Oracle Communications ASAP - Version 7.4.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On ASAP 7.4.0.1.0 version with Linux version 8.6

 

Following error is seen when trying to start ASAP server:

"Failed to start Master Control Server CTRL<ENV_ID>"

 

This is new fresh installation of ASAP 7.4. The installation was successful with no errors.

Also, following error is seen in ASAP.Console file:

 


On checking interfaces file, it's empty.

Also, ASAP database tables having ASAP config information such as TBL_APPL_PROC, TBL_COMPONENT, tbl_listeners, tbl_server_info do not have any rows.

ASAP tables having NE config information such as tbl_ne_config, tbl_resource_pool, tbl_comm_param etc empty.

Only ASAP tables having service model information such as tbl_asdl_config, tbl_csdl_config, tbl_csdl_asdl etc have rows populated with data.

The ASAP installation logs (such as asap74ServerLinux.log) do not log any errors. Also, the screen shot of ASAP GUI installation shows the Installation Overall Status is Successful.

 

Changes

 

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


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