Agent log errors

3_AGENT_LOGS scenario fails with the following error message:
OS command returned 1

A failure occurred in the AgentLog_oracle.nsh or AgentLog_sqlserver.nsh script.

Check the log files in the BDSSAInstallationDirectory/logs/etl/AgentLogProcess directory for more details.

LOAD_STG_FILE_AGENT_LOG scenario fails at the Call sqlldr via Jython step.

A failure occurred in the core sqlldr or bcp call to the database.

Check the log files in the BDSSAInstallationDirectory/logs/etl/AgentLogProcess directory for more details.

The LOAD_STG_FILE_AGENT_LOG_SCEN_20080710175536.err log file contains the following error message:
"SnpContext does not exist."

The ETL (ODI) setup is incorrect.

Contact BMC Support.

The BCP.in.log file contains the following error message:
"Error = [Microsoft][SQL Native Client]Unable to open BCP host data-file."

One of the following agentLogFilesDirectory conditions exists:

• The directory does not exist.
• The directory is not accessible.
• The directory path has spaces in it.

Refer to Viewing the agent log files for ETL runs for more information and perform one of the following procedures:

• Create the directory path.
• Make the location accessible (which means readable and writable).
• Relocate the agent logs to a location in which the path does not contain spaces.

All rows present in the agent files were not loaded into the database.

Some rows might have been rejected by the database-specific loader utility.

Check the runtime log files for details about which rows failed to load and for what reason.
For Oracle systems, the logs are located in the runlogs directory.
For Microsoft SQL Server systems, check the BCP.in.log file in the BDSSAInstallationDirectory/logs/etl/AgentLogProcess directory.

The log run failed and the agent files that came from BMC Server Automation are no longer located in the logs directory.

Whenever an agent log run fails and exits cleanly, the data file generated by the run is moved to the notproc directory under the agentLogFilesDirectory in a concatenated format.
If there is a failure in ETL run, the original agent files remain in the agentfiles directory in the agentLogFilesDirectory.

Complete the following steps:

1. Navigate to the notproc directory in the agentLogFilesDirectory.
2. Identify the data file corresponding to your failed run.
3. Manually move it to the logs directory in the agentLogFilesDirectory.
4. Re-run the ETL script for agent logs.

The log run fails at the LOAD_STG_FILE_AGENT_LOG scenario when running on a Microsoft Windows Server 2008 server with an error message similar to the following:
org.apache.bsf.BSFException: exception from Jython: Traceback (innermost last):File "<string>", line 2, in ?
OSError: (0, 'Failed to execute command ([\'sh\', \'-c\', \'bcp_1 BSARA_DW_288.dbo.STG_FILE_AGENT_LOG 137.72.238.72 BSARA_DW **\']): java.io.IOException: CreateProcess: sh -c "bcp_1 BSARA_DW_288.dbo.STG_FILE_AGENT_LOG 137.72.238.72 BSARA_DW sa" error=2')

The ETL process does not recognize some of the newest Windows registry values used to indicate the OS type (a defect for this issue has been logged on the Sun Java site).

Contact BMC Support for a customized fix.