Oracle Auditing
measurement error codes
When the Get Oracle Database Measurements job encounters a problem during scan file download, processing, or package assembly, it emits a structured log message with a unique error code (OM001–OM017). Use these codes to identify the exact failure and determine the corrective action.
Archive and file processing (OM001–OM006)
| Code | Log message | Description | What to do next |
|---|---|---|---|
| OM001 | Failed to process DB scan archive: {archive_path}. Skipping archive. | An I/O or processing error occurred while reading a DB scan archive. The archive was skipped. | Verify disk quota on the BFI server. Rerun Get Oracle Database Measurements. |
| OM002 | Failed to process database file '{file_name}' in archive '{archive_name}'. Skipping file. | An I/O or processing error occurred while reading a specific file within a DB scan archive. The file was skipped. | Verify disk quota on the BFI server. Rerun Get Oracle Database Measurements. |
| OM003 | Errors encountered during automatic DB scan processing. | A summary code indicating that one or more errors occurred during automatic scan processing. Earlier log entries contain specific error codes. | Check earlier log entries for specific OM error codes. Rerun Get Oracle Database Measurements. |
| OM004 | Errors encountered during manual DB scan processing. | A summary code indicating that one or more errors occurred during manual scan processing. Earlier log entries contain specific error codes. | Check the integrity of files in /wlp/usr/servers/server1/data/sam/oracleAuditingManuallyUploaded. Re-upload files if needed. |
| OM005 | Intermediate DB report file missing. Omitting from the final package. | An intermediate DB report file that was expected to be included in the package was not found on disk. | Verify disk quota and write permissions on the output folder. Check whether the file is locked by another process. |
| OM006 | I/O error writing file {filename} to Oracle auditing package. Skipping file. | An I/O error occurred while writing a file to the Oracle Auditing package. The file was omitted from the package. | Verify disk quota and write permissions on the output folder. Check whether the file is locked by another process. |
Packaging and hardware mapping (OM007–OM013)
| Code | Log message | Description | What to do next |
|---|---|---|---|
| OM007 | There is not any Oracle auditing hardware scan collected | No Oracle hardware scan data was available when the package was built. The package is marked as partially complete because hardware details are missing. | Run BFI Hardware Scans – Detailed hardware scan and ensure data is uploaded. Then rerun Get Oracle Database Measurements. |
| OM008 | Failed to pack hardware scans. Hardware data will be missing from the package. | An error occurred while adding hardware scan data to the package. Hardware data is absent from the package. | Verify disk quota and write permissions. Check for locked files. |
| OM009 | There is not any Oracle auditing VM manager scan collected | No Oracle VM Manager scan data was available when the package was built. The package is marked as partially complete because VM Manager details are missing. | Run BFI Hardware Scans – VM Manager Scan and ensure data is uploaded. Then rerun Get Oracle Database Measurements. |
| OM010 | Failed to pack VM manager scans. VMM data will be missing from the package. | An error occurred while adding VM Manager scan data to the package. VMM data is absent from the package. | Verify disk quota and write permissions. Check for locked files. |
| OM011 | Hardware inventory missing for hostname: {hostname}. Writing row without HW details. | Hardware inventory data is completely missing for the specified hostname. A row was written without hardware details. | Run BFI Hardware Scans – Detailed hardware scan or VM Manager Scan and ensure data is uploaded. |
| OM012 | Incomplete hardware details for hostname: {hostname}. Partial data written. | Hardware details for the specified hostname are incomplete. A row with partial hardware data was written. | Run BFI Hardware Scans – Detailed hardware scan or VM Manager Scan and ensure data is uploaded. |
| OM013 | Failed to retrieve hardware details for file: {file_name}. Continuing with empty HW columns. | Hardware details could not be retrieved for the specified file. The row is written with empty hardware columns. | Run BFI Hardware Scans – Detailed hardware scan or VM Manager Scan and ensure data is uploaded. |
File integrity and downloads (OM014–OM017)
| Code | Log message | Description | What to do next |
|---|---|---|---|
| OM014 | Failed to parse host and instance name from filename: {file_name}. Skipping file. | BFI derives the hostname and database instance name from the Oracle options scan filename and assumes the hostname contains no underscores. The file could not be parsed and was skipped. | If the Oracle endpoint hostname contains underscores, contact Support. |
| OM015 | File ended prematurely (missing end-of-file marker). The file may be corrupted. | The Oracle options scan file is truncated or missing the expected end-of-file marker, likely because the disk was full on the endpoint when the auditing query ran. | Check the Oracle database endpoint for insufficient disk space. Free disk space if possible, then rerun the scan. If the issue persists, contact Support. |
| OM016 | Unrecoverable error downloading scan files from BigFix. | A non-recoverable error occurred while downloading scan archives from BigFix. No scan data was processed for this run. | Verify BigFix Client and Relay connectivity. Check BigFix server logs for download failures. |
| OM017 | Download Errors Summary: | A summary message emitted when one or more per-host download errors were encountered. Detailed per-host error messages follow immediately after this entry in the log. | Review the specific per-host error details that follow in tema.log to determine the root cause for each failed host. |