Skip to main content
Matrix42 Self-Service Help Center

Troubleshooting Oracle DB and Datacenter Compliance

Troubleshooting

This article describes various problem scenarios. If you cannot find your problem, we recommend that you execute the inventory manually step by step to localize your problem. A description of how to perform the inventory manually can be found in this article.

Scan jobs are not initiated

Check the time settings of the scan appliance.

Target system is not inventoried

Is the target system transferred to the scan appliance?

Check the configuration settings of the "Oracle Database Inventory" or "Datacenter Inventory" data provider to find out whether the target system is handed over to the scan appliance.

  • If you select the target systems individually, the server must be contained within the respective list of included systems.
  • If you select the target systems dynamically, based on an ASQL criterion, the target system must be included in the list of affected computers.

Has the data provider been executed? 

Please check whether the "Oracle Database Inventory" or "Datacenter Inventory" data provider has been executed. It must be executed twice a day, once to transfer the systems to be inventoried to the scan appliance, and a second time to collect and import the result data.

Please refer to the article How to Configure the Inventory Data Provider

Do the required services run in the scan appliance? 

Please check the scan appliance with the following commands to find out whether the services are running:
netstat –an | grep 9001
netstat –an | grep 9002

If the services are running, the result should look as follows:

If one of the services is not running, you must restart the services with the following command:
/etc/init.d/eRunBook stop
/etc/init.d/eRunBook start

Does the agent cause an error on the target system? 

The agent log can be found in the file system of the server to be inventoried.

Windows: 
C:\Program Files (x86)\eRunbook\log\agent.log

Linux/Unix:
/opt/eRunBook/Product/Agent/Log/agent.log

Please watch out for potential problems (e.g., […] connect error : Connection refused […]) and analyze the specific causes of such problems. Reinstall the agent, if necessary.

Refer to the article How to Install the Agents.

Does the agent have access to the database? 

During Oracle database inventory, you may have to check the permissions of the respective user in the system and on the Oracle database.

Please refer to the article Permission for the Oracle databases.

Can the scan appliance communicate with the agent? 

Check the agent log, which can be found in the file system of the server to be inventoried.

Windows: 
C:\Program Files (x86)\eRunbook\log\agent.log

Linux/Unix:
/opt/eRunBook/Product/Agent/Log/agent.log

Potential error:
ERROR while accepting connections, but carry on anyway : (0) Success
accept: cancel connect from 10.10.1.3

The cause of this known problem is an incorrect configuration. The following reference can be found in the agent log (example):

Server IP LIST: server ip list (1): 10.10.38.239, ,

Background: It seems that a "server ip" was specified during agent installation, which restricts IP addresses that may be used to trigger scan jobs (= IP address of the appliance).

In this case you must modify the agent configuration. The configuration file can be found on the target system in the following directories:

Windows:
C:\Program Files (x86)\eRunbook\product\agent\etc\eRunbook.conf

Linux:
/opt/eRunBook/Product/Agent/etc/eRunbook.conf

Wrong entry (example):
server_ip= 10.10.38.239

Correct the specified IP address to ensure that it matches the IP address of the scan appliance. Alternatively, you can use a wildcard:
server_ip= *

Firewalls that block communications between the scan appliance and the agent could also cause problems. Please ensure that the required ports are activated in both directions.

Has the target system been detected and inventoried? 

Log into the web front-end of the scan appliance and select the "Matrix42_License" instance. Check whether the target system is listed accordingly. Check whether the operating system has been detected and whether the IP address is correct.

Have errors occurred during the inventory process? 

Log into the web front-end of the scan appliance and select the "Matrix42_License" instance. Open the entry of the target system and check whether the following information is displayed:
Document = Scan Data
Chapter = xx ORACLE DBs

  • Was this article helpful?