RMAN PDB Backup

Task 1:- Run RMAN to connect to CDB with a user with SYSDBA or SYSBACKUP privilege

Administrative Privileges

Oracle Database 12c is expected to have few more administrative privileges apart from the traditional SYSDBA, SYSOPER and SYSASM. DBAs are using SYSDBA and SYSOPER for a long time. SYSDBA is a super user type of privilege which can be used for shutdown, startup, backup and recovery of the database. SYSOPER privilege is operator type of privilege which can be used for shutdown and startup of the database.

Oracle added the SYSASM system privilege in Oracle Database 11g Release 1 to be used exclusively to administer Automatic Storage Management (ASM).So SYSASM system privilege is used to manage ASM.

Oracle Database 12c has added three more new administrative privileges called SYSBACKUP, SYSDG and SYSKM in addition to the old administrative privileges SYSDBA, SYSOPER and SYSASM.

SYSDBA

SYSOPER

SYSASM

SYSBACKUP

SYSDG

SYSKM

SYSBACKUP:-

Backup and Recovery is such an important role a database administrator plays every day and it makes sense to separate that role to handle all the backup and recovery administrations.  Sysbackup seems to be created for managing the backup and recovery administration.

Task 2:-As usual backup all datafiles of the PDB database ,controlfile and SPFILE and archive logs

after increase value of db_recovery_file_dest_size to 10GB

Note :-

DB_RECOVERY_FILE_DEST specifies the default location for the flash recovery area.

The flash recovery area contains multiplexed copies of current control files and online redo logs,as well as archived redo logs, flashback logs, and RMAN backups.

Tasks 3:- Perform a whole PDB backup

A new RMAN command allow you to backup all datafiles of the pluggable database.

BACKUP PLUGGABLE DATABASE pdb1;

Task 4:-Perform a partial PDB backup of the tablespace USERS

Backup Tablespace PDB1:USERS

A new RMAN command allow you to backup some datafiles of the pluggable database.

Hope it helps. Please stay tuned, add me to your G+ Circles!! Your feedback always helps me and motivates me to blog more, please leave your valuable comment that is always a pleasure to read.

Many Thanks,

Regards

Senthilkumar Devaraj

RMAN Whole CDB Backup

Task 1:- Run RMAN to connect to CDB with a user with SYSDBA or SYSBACKUP privilege

Administrative Privileges

Oracle Database 12c is expected to have few more administrative privileges apart from the traditional SYSDBA, SYSOPER and SYSASM. DBAs are using SYSDBA and SYSOPER for a long time. SYSDBA is a super user type of privilege which can be used for shutdown, startup, backup and recovery of the database. SYSOPER privilege is operator type of privilege which can be used for shutdown and startup of the database.

Oracle added the SYSASM system privilege in Oracle Database 11g Release 1 to be used exclusively to administer Automatic Storage Management (ASM).So SYSASM system privilege is used to manage ASM.Oracle Database 12c has added three more new administrative privileges called SYSBACKUP, SYSDG and SYSKM in addition to the old administrative privileges SYSDBA, SYSOPER and SYSASM.

SYSDBA

SYSOPER

SYSASM

SYSBACKUP

SYSDG

SYSKM

SYSBACKUP:-

Backup and Recovery is such an important role a database administrator plays every day and it makes sense to separate that role to handle all the backup and recovery administrations.  Sysbackup seems to be created for managing the backup and recovery administration.

Task 2:-As usual backup all datafiles of the database (CDB and all PDB),controlfile and SPFILE and archive logsafter increase value of db_recovery_file_dest_size to 10GB

Note :-

DB_RECOVERY_FILE_DEST specifies the default location for the flash recovery area.

The flash recovery area contains multiplexed copies of current control files and online redo logs,

as well as archived redo logs, flashback logs, and RMAN backups.

Task 3:- Trigger the Whole CDB Backup .

Hope it helps. Please stay tuned, add me to your G+ Circles!! Your feedback always helps me and motivates me to blog more, please leave your valuable comment that is always a pleasure to read.

Many Thanks,

Regards

Senthilkumar Devaraj

Instance parameters changes on Pluggable Database

                 In this example, I am going to show you some of the parameters can be changed in a pluggable database, if the impact is limited to the current container.  However, the global parameters like SGA_TARGET can be set only through root container – CDB$ROOT. A new column ISPDB_MODIFIABLE is added  in V$PARAMETER view to list the parameters modifiable from a PDB.

Lab :-

                        Container Database : CDB1

                        Pluggable Database : PDB1

Overview:

1.     Log into CDB1 as sys

2.     Check the current value of instance parameter optimizer_use_sql_plan_baselines'.

3.     Log into PDB1 as sys

4.     Check the current value of instance parameter 'optimizer_use_sql_plan_baselines'.

5.     Change the Instance parameter value to FALSE in PDB1

6.     Check the instance parameter value changes

Task 1:- Log into CDB1 as sys

Task 2:- Check the current value of instance parameter 'optimizer_use_sql_plan_baselines'

Task 3:- Log into PDB1 as sys

Task 4:- Check the current value of instance parameter 'optimizer_use_sql_plan_baselines'

Task 5:- Change the Instance parameter value to FALSE in PDB1

To check the parameter value at CDB .

Another Method:-

To change PDB1 instance parameter value through CDB1 database  .

To check the parameter value at PDB

Hope it helps. Please stay tuned, add me to your G+ Circles!! Your feedback always helps me and motivates me to blog more, please leave your valuable comment that is always a pleasure to read.

Many Thanks,

Regards

Senthilkumar Devaraj