Release Notes › Known Issues › Appliance (non-UI) › Excessive Number of ELMAdapter Log Files

Excessive Number of ELMAdapter Log Files

Symptom:

A large number of Adapter log files can accumulate on the CA Enterprise Log Manager server. This is atypical, in that the norm is to append log messages in a single log file. The problem can be caused by enabling tracing.

To determine whether this problem exists

1. Schedule reports and alerts and run ODBC queries, such as the following:

   select event_logname,count(*) from view_event where event_time_gmt >= timestampadd(hh,-1,now()) AND event_time_gmt <= now() group by event_logname;
   

2. Log in to the CA Enterprise Log Manager server using SSH and provide the caelmadmin user name and password.
3. su to root and provide the root password.
4. Navigate to the iTechnology folder:

   cd /opt/CA/SharedComponents/iTechnology
   

5. Determine whether an excessive number of log files have been created due to querying through ODBC drivers. These files are named ELMAdapter_<oaserverpid>_-IP.log.

Solution:

If this problem exists, ensure error tracing is disabled as follows:

1. Log in to the management CA Enterprise Log Manager server using SSH and provide the caelmadmin user name and password.
2. su to root and provide the root password.
3. Navigate to the iTechnology folder:

   cd /opt/CA/SharedComponents/iTechnology
   

4. Open oaserver-dm.ini for edit.
5. Scroll to [Service_0] and ensure the tracing is set as disable. If not, change it to match the following example:

   ServiceDebugLogLevel=0
   ServiceIPLogOption=Disable All Tracing
   

6. Restart the ODBC Service as follows:
   1. Select the Administration tab and the Services subtab.
   2. Click ODBC Server.
   3. Do one of the following:
      • If Enable Service is not selected, select Enable Service and click Save.
      • If Enable Service is selected, clear the Enable Service checkbox, click Save, select Enable Service, and click Save again.