Communication problems

Description

CORBA cannot be initialized. After invocation of an OA command, the following error is reported:

Consolidated OA system or OAserver specific 6000 Cannot initialize CORBA ORB. 'CORBA::COMM_FAILURE'

OA client specific

Failed to initialize CORBA

Explanation

Possible reason for this problem may be that omniNames is not running on the consolidated OA system or OA server and, consequently, its host is not accessible to the OA client.

Workaround

Proceed as follows:
1. On the consolidated OA system or OA server, verify the status of the CORBA Naming Service daemon (service) (omniNames).

Run the command omniNames --status and inspect its output. If omniNames is not running, invoke the command omniNames --start or omniNames --restart as appropriate.

On Linux platform, omniORB.cfg is located in the directory /etc/opt/ivd.

Description

After invocation of an OA command, the following error is reported:
6001 Problems accessing CORBA Naming Service.

Explanation

omniNames (CORBA Naming Service daemon (service)) is not running in the OA implementation.

Workaround

Proceed as follows:
1. On the consolidated OA system or OA server, verify the status of the CORBA Naming Service daemon (service).

Run the command omniNames --status and inspect its output.

 

Description

After invocation of an OA command, the following error is reported:
6008 Cannot connect to Management Interface - probably not running.
'Requested name does not yet exist in the NameService.
Giving up. ivd/mgr/<ivd_server@company@com>/mif'

Explanation

Most probably the Management Interface (the process ivd-mif) is not running.

Workaround

Check if ivd-mif is running using the ivd --status command. If the process is stopped, you must restart OA with the ivd --restart command.

 

Description

When inspecting the OA error log of an improperly operating OA implementation, the following error entry is detected:
This machine (localhost.localdomain) has only localhost IP.
Misconfigured DNS on host: localhost.localdomain. Official name (hostent::h_name) is NULL.
Misconfigured DNS on host: localhost.localdomain. Official name (hostent::h_name) should contain FQDN.

Explanation

This behavior is caused by improper network configuration, when the network is not configured properly to resolve its host name to the fully-qualified domain name (FQDN) and IP.

Workaround

Check if the network settings (DHCP settings, the /etc/hosts file configuration, DNS resolution configuration, and so on) are correct, and modify them if necessary.

 

Description

After running the ivdfile command with any of the following options: --history, --recall, --migrate, --trigger-migration, the command fails and reports:
6004 Caught Corba exception.

Explanation

See Workaround.

Workaround

First, try to identify the problem as follows:
1. Find out the status of the OA partition with the command:
ivdpartition --status PartitionName
2. Check if the ivd-hsm process is running on the corresponding OA client.

Use the command ps -ef | grep ivd-hsm.

 

Description

In a distributed or mixed OA implementation, after the consolidated OA system or OA server is restarted, the ivdpartition -l -D command reports OA partitions on external OA clients as not mounted.

Explanation

The consolidated OA system or OA server lost connection with all external OA clients after it was restarted.

Workaround

On each external OA client, restart the OA processes using the ivd --restart command.
This needs to be done with the above OA implementations each time after the OA server or
the integrated OA system is restarted.