Backup log Check 9i (‘old style’ backups)

Job details

Name:	Backup log Check 9i (‘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 9i only).
Version:	2.5
Default schedule:	15 5 * *
Requires engine install:	Yes
Compatibility tag:	.[type=‘instance’ & databasetype=‘oracle’]/.[hasengine=‘YES’ & version like ‘9%’ & _priv_read_dba_directories = ‘1′]

Name	Default value	Description
backup log name	backup.log	The name of the backup log file.
backup log path	null	The path name of the backup log file which is used to create directory object.
backup log directory name	DBW_BACKUP_DIR	The name of the directory object created with the DDL – “create directory”.
backup log error text	ORA-	Defines which strings (errors) the Check must look for. Values for this parameter must be
backup log line HWM	0	Each time the Check read the backup log, it registers how many rows have been checked.
backup log max lines	200000	If the backup log has more lines than the value of this parameter, then the Check terminates
backup log max elapsed time	60	Define the maximum running time the Check can execute (values are in seconds). If the execution ‘
backup log error text allowed	null	Specifies the error strings which are excluded.
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~~, you have to specify the date-format
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 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

Purpose: The purpose of this job is to monitor and validate the logs generated from Oracle 9i database backups that are conducted using scripts instead of RMAN (Recovery Manager). It checks for errors in the specified backup log file, ensuring that backups are executed correctly without errors.
Why: This job is crucial because it ensures the integrity and successful execution of backups for Oracle 9i databases. Monitoring old style backups through logs is essential as these backups do not utilize Oracle’s RMAN, which has its own comprehensive set of checks. Errors in backups can lead to data loss in case of database failure which necessitates a restore from these backups.
Manual checking: You can manually check the contents of the backup log in the database via SQL commands. For example:

SELECT log_text FROM "your_schema".dbw_filelogs WHERE log_type ='backup' ORDER BY row_no;

Object: “backup_log”
Description: Checks errors in a backup log file for non-RMAN database backups.
Method: The job reads the backup log file whose path and other properties are configured through various parameters. It searches for error texts specified in the parameters and ensures that particular confirmation texts are present, implying successful backups.

Log file specifics such as name, path, and directory name are defined.
Error texts to identify and confirm texts to look for in logs are specified.
High Water Mark for line reads, maximum allowable lines, and maximum elapsed time for job execution are configured to ensure efficient log checking.

Dependencies: Ensure the correct privileges like creating directory objects are granted to the user running the check. Also, depends on the existence of specified directory objects and proper configuration of DB parameters.
Pre-Execution Setup: Checks and grants necessary permissions to create directory objects. Ensures the required directory for reading logs is available or creates one if not present.
Execution: The Oracle procedure reads the log file, detects any errors based on configured parameters, checks for confirmation text, and evaluates the log file’s age and size.

Generates reports detailing backup log statuses and directory definitions.
Reports are configured to run hourly and include information on backup logs and directory objects used.
Alerts can be configured based on the outcomes of log file checks, such as errors found, missing confirmation texts, or logs that are too old.

A series of PL/SQL procedures and functions are employed to fetch parameters, read log files, check for errors, and update monitoring status based on the findings.
It handles exceptions by logging them and providing error feedback through the monitoring system.

Ensuring the regular truncation of the backup log can prevent issues with log size limits.
Appropriate scheduled frequencies for running this check should be balanced against the backup schedule to ensure timely detection of backup issues.

Detailed textual and tabular presentations in the dbWatch Control Center, listing backup log analyses and directory object information.
Possible output customization via SQL queries specific to the organization’s needs.