11 Troubleshooting

This chapter describes how to troubleshoot Oracle Communications Converged Application Server installations.

About Troubleshooting Converged Application Server Installations

The Converged Application Server installer and the Domain Configuration Wizard write information to log files. You can check those log files for information about errors and actions performed during the installation process.

About Converged Application Server Installation Log Files

The Converged Application Server installation logs can be found at Central_inventory_location/oraInventory/logs, where Central_inventory_location is the directory path to the oraInventory directory. If you do not know the location of your Oracle Inventory directory, you can find it in the Oracle_Home/oraInst.loc file. Oracle_Home is the directory that serves as the repository for common files that are used by Oracle Communications products installed on the same machine, such as Converged Application Server and WebLogic Server.

The following install log files are written to the log directory:

  • installdate-time-stamp.log

    The main log file.

  • installdate-time-stamp.out

    This log file contains the output and error streams during the installation.

  • installProfiledate-time-stamp.log

    This log file contains the overall statistics such as time taken to complete the installation, as well as configuration, memory, and CPU details.

  • oraInstalldate-time-stamp.out

    This log file contains the output stream of the copy session.

  • oraInstalldate-time-stamp.err

    This log file contains the error stream of the copy session.

Changing the Installer Logging Level

To change the logging level, add the -logLevel parameter when you start the installer at a command prompt. For example: 

java -jar occas_generic.jar -logLevel info

The following shows valid values for -logLevel from most detailed to least detailed:

  • severe

  • warning

  • info

  • config

You can also specify logging details from detailed to least detailed in the following manner:

  • fine

  • finer

  • finest

About Domain Configuration Log Files

If you encounter errors when configuring a Converged Application Server domain, you can start the Fusion Middleware Configuration Wizard with the appropriate logging options.

To enable domain configuration logging, go to Oracle_Home/oracle_common/common/bin and enter the following command: 

./config.sh -log=log_filename -log_priority=log_level

Table 11-1 Configuration Wizard Log File Options

Parameter Description

-log

Specify the location of your log file.

If you specify a log file name, it is created in the same directory as the config.sh script unless you add a path component. Log files are otherwise created in Oracle_Home/logs.

Other values that can be specified with -log are:

  • stdout

    Writes the error message to the standard output stream.

  • stderr

    Writes the error message to the standard error stream.

  • disable

    Disables default logging so that no log files are generated in Oracle_Home/logs.

-Log_priority

Specify the level of detail you want included in your logs.

The following list shows the acceptable values:

  • OFF
  • SEVERE
  • WARNING
  • INFO
  • CONFIG
  • FINE
  • FINER
  • FINEST

AIC Troubleshooting

Consider the following when troubleshooting the AI Connector.

JVM Troubleshooting

  • Use tools like Java Flight Recorder (JFR) and Java Mission Control (JMC) to capture and analyze JVM runtime behavior for performance issues.
  • Collect JVM diagnostics using the jcmd utility to identify memory, thread, and GC-related problems.
  • Monitor key JVM metrics such as heap usage, garbage collection activity, and thread performance to detect bottlenecks early.
  • Analyze GC logs and memory usage to identify memory leaks or excessive garbage collection pauses.

Startup Failures

Issue: Starting the AIC fails with this message:
ERROR [main] c.o.n.a.AICStartUp - Configured OCI config file does not exist or is not readable/regular: /home/sdp/.oci/config
Resolution:
  • Verify that in the AIC VM .oci configuration is present and AIC gets connected to OCI properly.
  • Validate that in the $sh startAIC.sh we should get the below console Logs.
    INFO  [main] c.o.n.a.AICStartUp - Registering OCI provider...
INFO  [main] c.o.n.a.p.i.o.OCIAIServiceProvider - OCI AI Service Provider initialized
INFO  [main] c.o.n.a.p.AIServiceRegistry - Registered AI provider: oci with capabilities: [SPEECH_TO_TEXT]
INFO  [main] c.o.n.a.AICStartUp - OCI provider registered
INFO  [main] c.o.n.a.AICStartUp - Initializing AI Connections Manager...
INFO  [main] c.o.n.a.AICStartUp - AI Connections Manager initialized
INFO  [main] c.o.n.a.AICStartUp - Initializing provider configurations...
INFO  [main] c.o.n.a.p.AIConnectionsManager - Initializing AI services with 1 provider configurations
INFO  [main] c.o.n.a.p.i.o.OCIAIServiceProvider - OCI AI Service Provider initialized
INFO  [main] c.o.n.a.p.AIConnectionsManager - Initialized AI service provider: oci
INFO  [main] c.o.n.a.AICStartUp - Provider configurations initialized
INFO  [main] c.o.n.a.AICStartUp - Initializing orchestration service...

Enable Debug Logs

Enable debug logs to get detailed visibility into AGS/MGS processing and internal flows (request/response), which helps in troubleshooting issues.

  1. In the Edit Tree, select Custom Resource, and then serverdebug, and then SIP Server Debug, and then Servers, and then <engine-name>.
  2. Enable the MGS slider to get MGS debug logs.
  3. Enable the AGS slider to get AGS debug logs.
  4. Select Save, select the shopping cart, and select Commit Changes.