Backup log Check 8i(‘old style’ backups)
Job details
| Name: | Backup log Check 8i(‘old style’ backups) |
| Platform: | Oracle |
| Category: | Availability |
| Description: | Checks for errors in a log file (e.i. backup log). For backups not using RMAN. |
| Long description: | Checks for errors in a log file (e.i. backup log). For backups not using RMAN, but using a script that uses ‘alter tablespace xx backup;’ and creates a log file. (Oracle 8i only). |
| Version: | 2.4 |
| Default schedule: | 55 6 * * |
| Requires engine install: | Yes |
| Compatibility tag: | .[type=‘instance’ & databasetype=‘oracle’]/.[hasengine=‘YES’ & version like ‘8%’ & _priv_read_dba_directories = ‘1′] |
Parameters
| Name | Default value | Description |
|---|---|---|
| backup log name | backup log | The name of the backup file. |
| backup log path | backup path | The path name of the backup file. |
| backup log error text | warning | Defines which strings (errors) the Check must look for. Values must be separated with commas (,). |
| backup log confirm text | successful | The Check loop throughout the log file, searching for a “confirm” text. If the Check do not find at least |
| backup log date format | dd-mm-yyyy hh24:mi | If a value is assigned to the parameter |
| backup log date position | backup finished | If the log-file has a date/time stamp in it, you can have the Check to check how |
| backup log max lines | 20000 | If the log has more lines than the value of this parameter, then the Check terminates and |
| backup log line HWM | 0 | If the log-file is an append-type log (as alert and listener logs), the parameter must not be 0 (zero). |
| backup log nls lang | English | Defines handling of language-specific date-format used by the dbwatch parameter “backup log date format”. |
| backup log expire time | 24 | You can specify how old the log-file is allowed to be before the Check returns the |
| backup log max elapsed time | 60 | Define the maximum running time the Check can execute (values are in seconds). If the |
| backup log error text allowed | NULL | Specifies the error strings which are excluded. |
Job Summary
- Purpose: The primary function of this monitoring job is to check for errors and confirmations in backup logs for Oracle 8i databases that use old-style backup methods, i.e., those not utilizing RMAN but instead using scripts that execute commands like “alter tablespace xx backup;”. The job also assesses the recency and integrity of the logs.
- Why: This job is essential to ensure the reliability and execution of backups, which are critical for data recovery and business continuity. Failure to detect issues in the backup log might lead to loss of data, difficulties in restoring databases, and potential business downtimes.
- Manual checking: To manually verify the backup logs, administrators can access the specific directory where logs are stored and review them for errors or confirmation strings. Specific SQL commands related to log verification might include direct queries into system views or directories where these logs are maintained.
Details of the Implementation
The monitoring job operates by the following procedures and conditions:
- Reviewing backup logs to identify specific error texts and confirmation texts.
- Checking the timestamp within the log file to ascertain if the log is recent and relevant, based on provided parameters like date position and date format.
- Evaluating the number of lines in the backup log to ensure it does not exceed a pre-configured maximum.
- Ensuring the log is not too old by comparing its creation time against a specified expiry time.
Tables Used
| Parameter | Type | Description |
|---|---|---|
| Backup Log Name | String | Name of the backup log file |
| Backup Log Path | String | Path where the backup log is stored |
| Backup Log Error Text | String | Specifies strings to identify as errors in the log |
| Backup Log Confirm Text | String | Confirmation strings that must be found in the log |
| Backup Log Date Format | String | Format of the date in the log |
| Backup Log Date Position | String | Unique string near the date to identify the timestamp |
| Backup Log Max Lines | Number | Maximum lines the log can have before issuing a warning |
| Backup Log Line HWM | Number | High watermark for lines already read |
| Backup Log NLS Lang | String | Language-specific date format handling |
| Backup Log Expire Time | Number | Time after which an old log will trigger a warning |
| Backup Log Max Elapsed Time | Number | Maximum runtime of the check before termination |
Dependencies
The job has dependencies on several Oracle database management objects and other checks such as:
- CHECK_FILELOG and GET_FILELOG_STATUS: Both procedures play critical roles in accessing and evaluating the log files.
- DBA_DIRECTORIES: This view in Oracle is crucial for determining accessible directories.
Reporting and Alerts
Reports generated by dbWatch based on this task provide insights into:
- Status and content of the backup log.
- Definitions and paths of directory objects used.
Conclusion
This dbWatch job plays a pivotal role in ensuring the health, integrity, and timeliness of backup processes for Oracle 8i databases using script-based backups. Early detection of errors and regular validation of backup log files safeguard against potential data recovery failures.