Tag: Backup

  • Oracle 12c – causing problem by solving it!?!

    Oracle 12c – causing problem by solving it!?!

    Oracle 12c – causing problem by solving it!?! Regular readers of our blog probably already know that for most of our databases we’re using two storage layers to keep our backups – NAS volumes as a primary layer and tapes as secondary one – please check “Datafile without backups – how to restore?” for more

    Explore →

  • Potential of “import catalog” command

    Potential of “import catalog” command

    Potential of “import catalog” command Since version 11.1 of Oracle database, there is very useful command available, allowing DBAs to easily move RMAN recovery catalog schemas between databases. Its functionality is even broader, as it also allows one catalog schema to be merged into another – either the whole schema or just the metadata of

    Explore →

  • Datafile without backups – how to restore?

    Datafile without backups – how to restore?

    Datafile without backups – how to restore? Have you ever had a problem with restoring datafiles without any backups available? It’s easy, of course if you have all archived logs from the time datafile was created. Please check it here: Re-Creating Data Files When Backups Are Unavailable. Moreover, RMAN is clever enough to create empty

    Explore →

  • Importance of testing yours backup strategy

    Importance of testing yours backup strategy

    Importance of testing yours backup strategy Most of you for sure know, that ability to restore data in case of failure is a primary skill for each DBA. You should always be able to restore and recover data you’re responsible for. This is an axiom. To be sure, that you’re able to do it, you

    Explore →

  • Backups in Data Guard environment

    Backups in Data Guard environment

    Backups in Data Guard environment Physical standby databases seem to be ideal candidates for offloading backups from primary ones. Instead of "wasting" resources (unless you're already using Active Data Guard for example), you could avoid affecting primary performance while backing up your database, especially if your storage is under heavy load even during normal (user-

    Explore →

  • How to verify if archived log deletion policy is correctly applied?

    How to verify if archived log deletion policy is correctly applied?

    How to verify if archived log deletion policy is correctly applied? What is the best way to handle archived logs deletion in environments with standby and downstream capture databases? One could use own scripts, to delete for example all backed up archived logs, older than n days. But better way, will be to set RMAN

    Explore →