Oracle 12c – Recover Database with RMAN

 

This article gives the steps in performing a RMAN recovery of a database in 12c.    This procedure was performed on a OEL 7.2 and assumes that a full backup has already successfully completed.

 

 

  1. Logon to your database server as the Oracle software owner.

 

mylinux# su – oracle

Password:

Last login: Sun Sep 18 13:45:52 UTC 2016 on pts/1

mylinux# 

 

  1. Start RMAN and connect to target database.

 

mylinux# rman

Recovery Manager: Release 12.1.0.2.0 – Production on Mon Sep 19 13:46:06 2016

Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect target /

connected to target database: ORCL (DBID=3153769526)

RMAN>

 

  1. Issue a startup mount command, do not open the database.

 

RMAN> startup mount;

 

  1. Use the SHOW command to determine channels to use, or the CONFIGURE command to create channel.

 

RMAN> show all;

 

  1. Issue the RESTORE command.

 

RMAN> restore database;

 

  1. Issue the RECOVER command.

 

RMAN> recover database;

 

  1. Issue the database OPEN command.

 

RMAN> alter database open;

 

  1. This completes the recovery of Oracle 12c database.

Larry Catt

OCP

Oracle 12c – Perform post upgrade tasks

Oracle recommended that the following tasks be performed after the upgrade of Oracle RDBMS to 12c.

 

 

  1. Backup the database – make a full backup of the system after upgrade.
  2. Execute postupgrade_fixups.sql – The Database Upgrade Assistance BDUA executes this script as a normal upgrade process.  Execute this script anytime or after manual upgrade process.  This script generates three types of upgrade info for administrator.
    1. General Warning.
    2. Errors
  3. Gather Fixed Objects statistics – Execute DBMS_STATS.GATHER_FIXED_OBJECTS_STATS post upgrade and after the database has been running in normal operation for a few days. This can improve overall performance of the database.
  4. Reset Passwords to Enforce Case-Sensitivity – Execute DBMS_VERIFIER.EXPIRE_ACCOUNTS_WITHOUT_LATEST_VERIFIER procedure to force users which are not using the latest password restrictions to reset password on next logon.
  5. Set Threshold Values for Tablespace Alerts – After upgrade tablespace alerts are shutoff. Id tablespaces which need to have alerts set and set them.
  6. Migrate from rollback segments to Automatic Undo Mode – If migrated database was before 11g, you were using rollback segments, you must migrate database to Automatic Undo to take advantage of increased performance.
  7. Migrate Tables from LONG to LOB – LOB of type (BFILE,BLOB, CLOB, NCLOB) have a lot of advantage over LONG. Use ALTER TABLE command to convert LONG to CLOB and LONG RAW to BLOB.

 

 

Larry Catt

OCP