The flashcards below were created by user
Tralala
on FreezingBlue Flashcards.
-
How are backups managed?
With RMAN and EM Cloud Control
-
What can be backed up?
- Backup entire CDB
- Only the root of the CDB
- Any or all of the PDBs
-
If the whole CDB is backed up, what is backed up?
Root, all the PDBs, Seed and the archived redo logs.
-
From a whole CDB backup, what can be recovered?
- The whole CDB
- The root only
- One or more PDBs
-
To backup a CDB, what is specific about the user performing the backup?
- Must be a common user
- Must have SYSBACKUP ot SYSDBA
-
What RMAN command is issued to backup an entire CDB?
RMAN> BACKUP DATABASE;
-
What RMAN command is issued to backup an entire CDB including archivelogs?
RMAN> BACKUP DATABASE PLUS ARCHIVELOG;
-
What RMAN command is issued to backup root?
- RMAN> BACKUP DATABASE ROOT;
- RMAN> BACKUP PLUGGABLE DATABASE 'CDB$ROOT'; - quotes due to $
-
How is a pluggable database backed up?
- Connected to root: RMAN> BACKUP PLUGGABLE DATABASE PDB01, PDB02;
- Connected to root: RMAN> BACKUP PLUGGABLE DATABASE PDB03, 'CDB$ROOT';
- Connected to PDB: RMAN> BACKUP DATABASE;
-
What new column is to be found in the backup relates V$ and RC_ views?
PLUGGABLE_DBID
-
Which view shows backup information for all PDBs?
RC_PDBS
-
On ALTER DATABASE BACKUP CONTROLFILE TO TRACE what happens?
A script of all the data files that belong to the root container as well as all the PDBs.is generated
-
Without RMAN, how can the entire CDB be backed up?
- SQL> alter database begin backup;
- SQL> alter database end backup;
-
When connected to a PDB as a local user via RMAN, how are archived log backed up?
They can't
-
How is a non RMAN backup performed in a pluggable database?
- Connect to the PDB - This cannot be done as Root
- ALTER PLUGGABLE DATABASE pdb01 BEGIN|END BACKUP;
- ALTER DATABASE BEGIN|END BACKUP;
-
How are archived logs backup up?
Same a a non-PDB, but must be connected to Root
-
How is an individual tablespace backed up for a PDB?
- Connected to root: BACKUP TABLESPACE pdb02:sysaux
- Connected to PDB: BACKUP TABLESPACE sysaux;
-
What can be recovered?
- entire CDB
- only root
- a single PDB
- a portion of a PDB (tablespace datafile)
-
Why do Oracle not recommend restoring the ROOT of CDB?
Can introduce metadata inconsistencies.
-
How is whole CDB recovered?
- Connect to root as common user with SYSBACKUP ot SYSDBA
- CDB must be in mount mode
- RESTORE DATABASE ROOT;
- RECOVER DATABASE ROOT;
- Restore SEED and ALL PDBs
- RESTORE PLUGGABLE DATABASE ‘PDB$SEED’, pdb01, pdb02;
- RECOVER PLUGGABLE DATABASE ‘PDB$SEED’, pdb01, pdb02;
- ALTER DATABASE OPEN;
- ALTER PLUGGABLE DATABASE OPEN;
-
How is a complete recovery of a PDB performed?
- Connected to root:
- RMAN> RECOVER PLUGGABLE DATABASE PDB01;
- RMAN> RESTORE PLUGGABLE DATABASE PDB01;
- RMAN> ALTER PLUGGABLE DATABASE PDB01 OPEN;
- Connected to PDB:
- RMAN> RESTORE DATABASE;
- RMAN> RECOVER DATABASE;
- RMAN> ALTER DATABASE OPEN;
-
What happens if a CDB instance opens and the a tempfile is missing or corrupted?
A new one is created automatically and a message written to the alert log
-
What happens if a PDB instance opens and the a local tempfile is missing or corrupted?
A new one must be created manually
-
How does one connect to a PDB in RMAN?
rman target sys/password@PDB01
-
How does one recover a PDB from a missing datafile?
- rman target sys/password@PDB01
- ALTER DATABASE DATAFILE 11 OFFLINE;
- RESTORE DATAFILE 11;
- RECOVER DATAFILE 11;
- ALTER DATABASE DATAFILE 11 ONLINE;
-
How is flashback database enabled?
- Database must be in archivelog mode
- ALTER DATABASE FLASHBACK ON;
-
What are the steps the flashback a CBD?
- Ensure flashback is on
- Connect to ROOT as SYSDBA or SYSBACKUP
- SHUTDOWN IMMEDIATE;
- STARTUP MOUNT;
- FLASHBACK DATABASE TO TIMESTAMP SYSDATE-(5/24/60);
- ALTER DATABASE OPEN RESETLOGS;
-
What are the steps to flashback a PDB?
Can't perform flashback on a PDB
-
What happens if a PDB has been recovered with a PITR and a flashback database is attempted to before the PITR?
- An error is generated
- ORA-38866: Data file for pluggable database must be offline to flashback across a PDB point in time recovery.
-
If a PDB has been recovered with a PITR, what are the steps to flashback a database to before the PITR?
- 1 Backup Entire CDB
- 2 Close PTIR PDB
- 3 Offline all datafiles for PDB
- 4 Flashback Database
- 5 Open all database except PTIR PDB
- 6 Restore PTIR PDB from backup
- 7 Online all datafiles for PDB
- 8 Open PTIR PDB
-
How does one do a Point-In-TIme recovery of a PBD with RMAN?
- RUN {
- ALTER PLUGGABLE DATABASE pdb01 CLOSE;
- SET UNTIL TIME "TO_DATE('06-FEB-2015 14:25:00','DD-MON-YYYY HH24:MI:SS')";
- RESTORE PLUGGABLE DATABASE pdb01;
- RECOVER PLUGGABLE DATABASE pdb01;
- ALTER PLUGGABLE DATABASE pdb01 OPEN RESETLOGS;
- }
-
At what level is a Instance Recovery performed?
- A CDB level, not possible at PDB level.
- The instance is the CDB
-
If the root system or undo files were lost, what would happen and what recover would be required?
- The instance would crash
- startup mount
- restore tablespace SYSTEM | UNDOTBS1
- recover tablespace SYSTEM | UNDOTBS1
- alter database open
- alter pluggable database all open
-
If the root sysaux was lost, what would happen and what recover would be required?
- The instance would remain open, root and PDBs would remain open
- alter tablespace sysaux offline
- restore tablespace SYSAUX
- recover tablespace SYSAUX
- alter database open
-
If a PDB SYSTEM tablespace is lost, what happens. How is recovery done?
- If PDB was closed:
- restore tablespace pdb01:system
- recover tablespace pdb01:system
- If PDB was open:
- shutdown CDB
- startup mount;
- restore tablespace pdb01:system
- recover tablespace pdb01:system
- alter database open;
- alter pluggable database all open;
-
If a PDB NON-SYSTEM tablespace is lost, what happens. How is recovery done?
- SQL: connect sys@pdb01
- SQL: alter tablespace user offline immediate
- RMAN: restore tablespace pdb01:users
- RMAN: recover tablespace pdb01:users
- SQL: alter tablespace user online
|
|