Agent log errors
This topic lists errors that you might encounter when working with agent logs, along with suggested solutions to those errors. Refer to Viewing the agent log files for ETL runs for more information about the location of agent logs.
Error message | Issue | Action |
---|---|---|
3_AGENT_LOGS scenario fails with the following error message: | A failure occurred in the AgentLog_oracle.nsh or AgentLog_sqlserver.nsh script. | Check the log files in the BDSSAInstallationDirectory/logs/ |
LOAD_STG_FILE_AGENT_LOG scenario fails at the | A failure occurred in the core sqlldr or bcp call to the database. | Check the log files in the BDSSAInstallationDirectory/ |
The LOAD_STG_FILE_AGENT_ | The ETL (ODI) setup is incorrect. | Contact BMC Customer Support. |
The BCP.in.log file contains the following error message: | One of the following agentLogFilesDirectory conditions exists:
| Refer to Viewing the agent log files for ETL runs for more information and perform one of the following procedures:
|
Not all of the rows in the agent files were 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. |
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. | Complete the following steps:
|
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 message: | 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 Customer Support for a customized fix. |
Comments
Log in or register to comment.