Articles tagged

Incomplete / Complete recovery using RMAN cold backup

0
3
Offline backups (also known as Cold or consistent backups) are taken when the database is in a consistent state, i.e. the database has been shut down with the SHUTDOWN NORMAL, SHUTDOWN IMMEDIATE, or SHUTDOWN TRANSACTIONAL commands. As part of a consistent shutdown, redo has been applied to the data files and the System Change number (SCN) in the data f… Read more

Why Virtual Private Catalog?

0
1
Recovery Manager (RMAN) is the preferred tool to backup and recover the Oracle Database. You can use recovery catalog or the control file of the target database for RMAN Repository, but Recovery Catalog is the preferred method as it offers several advantages over the others, like reporting operations, simple recovery in case of control file damage, and more. Generally in… Read more

12c Dataguard : Recover from Service

0
3
Rolling Forward a Physical Standby Database Using the RECOVER Command A standby database is a transactionally-consistent copy of the production database. It enables production Oracle database to survive disasters and data corruption. If the production database becomes unavailable because of a planned or an unplanned outage, Data Guard can switch a standby database to the production role, minimizing the downtime associated… Read more

Oracle Database 12c – RMAN New Features: Part 2

0
1
Oracle Database 12c has new enhancements and additions to Recovery Manager (RMAN).  The Recovery Manager continues to enhance and extend the reliability, efficiency, and availability of Oracle Database Backup and Recovery. In this article series, I will be explaining the new features and how it will help the Oracle community. See new features covered in Part 1 – Oracle Databas… Read more

Optimizing Transaction Log Throughput

As a DBA, it is vital to manage transaction log growth explicitly, rather than let SQL Server auto-growth events "manage" it for you. If you undersize the log, and then let SQL Server auto-grow it in small increments, you'll end up with a very fragmented log. Examples in the article, extracted from SQL Server Transaction Log Management by Tony Davis and Gail Shaw, demonstrate how this can have a significant impact on the performance of any SQL Server operations that need to read the log.… Read more

Documentation: Shoulda, Coulda, Woulda

Every sysadmin knows that they should be documenting everything they can; not only is it good practice, it can be the difference between a speedy recovery and a lost job when something does go wrong. Barry Morrison delves into just what you should be covering, even if you think you can't spare the time.… Read more

SQL Backup Pro for the Accidental DBA

If you've suddenly found yourself responsible for maintaining and backing up your company's servers, you're an 'accidental DBA'. If you've been dropped in the deep end, let Grant Fritchey show you through the backup and restore functionality of Red Gate's SQL Backup Pro, showing you how to schedule regular backups, compress, restore and document your backups with ease.… Read more

Disaster Recovery for SQL Server Databases

High-Availability depends on how quickly you can recover a production system after an incident that has caused a failure. This requires planning, and documentation. If you get a Disaster Recovery Plan wrong, it can make an incident into a catastrophe for the business. Hugo Shebbeare discusses some essentials, describes a typical system, and provides sample documentation.… Read more