Skip to main content

Monitoring RMAN Backup with QBR Tools


The Quest Backup Reporter is a windows client application. It can connect too many databases at a time and reports directly from oracle data dictionary views and RMAN catalog. It does not make any modification to either database as well as RMAN configuration. It is just a read only reporting tools.
Quest Backup Reporter tools offers DBA a dashboard view of all oracle backup across one desktop view. Thus it is relatively easy for the DBA who is managing different database backup to check all the backup status at a time (on single screen) and to ensure the backup are valid and recoverable. QBR supports oracle version 9i onwards and OS Windows Server2003/XP/Vista/Win7/Win Server 2008 (32 or 64).
QBR requires .Net Framework ver. 2.0–3.5 for installation and does not require oracle client installation for operation: 

You can register target database using the menu Data source –> Register New Data source to access the information either through Control file or the RMAN catalog.



Once the targets are registered then you are able to check time of the successful and failure backup as well as real time status of running backup.

You can define policies if you need to meet backup with certain criteria such as retention period of backup of different types (full, level 0 and other incremental backup, archive log backup) and within various backup type you can define the days of the week as well as maximum run time.



Once a policy has been applied to a target you can click on the violations tab to see the types and categories of violations.
The Backup tab gives overview of the database backup as well as details of the particular backup. If you have already added recovery catalog you can see additional details of registered database.



Another very useful feature of QBR is checking growth of the backup size corresponding to its duration and Timelines for each type of backup.




Note: If you register more databases to QBR will take longer time to load them. This could results catalog database to slow and some other issues because it is continuously querying on the registered database catalog. 

Comments

Post a Comment

Popular posts from this blog

Tablespace Management using Toad

You can view all of your tablespace information using toad tablespace screen from Database –> Administer –> Tablespaces Here each table describes different detailed information across all the tablespaces in database. If you open this screen from the toad DBA module then you are also able to see the “space history” and “IO history” tab along with Files, Free space, object, Fragmentation. With these tab you are able to able perform space monitoring and planning steps. These tab permits you check graphically space and IO usage over time. Through this way DBA are also able to estimate ‘Object size’ based on this estimation. From the below “alter tablespace” tab you can §          Modify the tablespace and datafile size. §          Add new datafile to the tablespace.
Post a Comment
Read more

Import Excel Data into Oracle using Oracle form Button

Import Excel Data into Oracle using Oracle form Button 1. Create a button on the form with the name "IMPORT_EXCEL" and write a pl/sql on "WHEN BUTTON PRESSED" trigger. BEGIN IF :System.Cursor_Block<>'GL_DAILY_COMPOUND_HEADER' THEN   Go_Item('GL_DAILY_COMPOUND_HEADER.V_DATE'); END IF; IF :System.Mode = 'NORMAL' AND :System.Record_Status IN ('NEW','INSERT') THEN   IMPORT_EXCEL_PROC;   ---Form procedure ELSE  MESSAGE('Import allowed only for new entry!!!');  MESSAGE('Import allowed only for new entry!!!'); END IF; END; 2. Now write the procedure "IMPORT_EXCEL_PROC" into the program unit. Don't forget to create required table and folder for procedure IMPORT_EXCEL_PROC PROCEDURE IMPORT_EXCEL_PROC IS application    OLE2.Obj_Type; workbooks      OLE2.Obj_Type; workbook       OLE2.Obj_Type; worksheets      OLE2.Obj_Type; worksheet       OLE2.Obj_Type; ce...
Post a Comment
Read more

Changing National Character Set AL16UTF16 to UTF8

Changing National Character Set AL16UTF16 to UTF8 The national character set is used for data that is stored in table columns of the types NCHAR, NVARCHAR2, and NCLOB.  In contrast, the database character set is used for data stored in table columns of the types CHAR, VARCHAR2 and CLOB. Like the database character set, the national character set is defined when the database is initially created and can usually no longer be changed, at least not easily or without involving quite a lot of work (export, recreate database, import). Except when creating the database, where the national character set is defined explicitly, it can change implicitly even when upgrading the database from Oracle8i to Oracle9i (or Oracle10g). You require SYSDBA authorization to change the national character set. Changing the national character set means changing an Oracle Dictionary entry, but no data is changed.  $sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> Select property_...
Post a Comment
Read more