* PDB can act as a recovery catalog
* Recovery catalog is not supported when connected to pluggable database
* You must register the whole CDB agains the PDB catalog
http://sqlerr.blogspot.com/2016/07/setup-pluggable-database-pdb-as.html
RMAN
-
Setup pluggable database (PDB) as a recovery catalog for all other pluggable DBs in the container
-
Problème de compilation de trigger RMAN après montée de version en 12.2
alter trigger RMAN.VPC_CONTEXT_TRG disable;=> marche pas :(
lancer :
@?/rdbms/admin/dbmsrmanvpc.sql -vpd rman
puis UPGRADE CATALOG ;
-
Migrate database from One RMAN catalog to another RMAN catalog
Migrate database from One RMAN catalog to another RMAN catalog
http://www.nazmulhuda.info/migrate-database-from-one-rman-catalog-to-another-rman-catalog
Migrate database from One RMAN catalog to another RMAN catalog
In that scenario we will move catalog from stagecat(source catalog) to target database CLOUD.
[oracle@rmancatalog2 ~]$ rman target / catalog=rman/kjh7Rjsr1
Recovery Manager: Release 11.2.0.3.0 - Production on Wed Dec 21 09:28:47 2016
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: CLOUD (DBID=1801493836)
connected to recovery catalog database
RMAN> list db_unique_name all;
List of Databases
DB Key DB Name DB ID Database Role Db_unique_name
------- ------- ----------------- --------------- ------------------
49382 DB2 3896599226 PRIMARY DB2
49382 DB2 3896599226 STANDBY DB1
1 DB1 4139331099 PRIMARY DB1
1 DB1 4139331099 STANDBY DB2SQL> select * from rman.rc_database;
DB_KEY
DBINC_KEY
DBID
NAME
RESELOGS_CHANGE#
RESETLOGS_TIME
1
247199
4139331099
DB1
116371882675
06/07/2015 18:23
49382
49383
3896599226
DB2
90051108188
09/02/2012 16:18
RMAN> import catalog rman/U98wsjdw2#@stagecat;
Starting import catalog at 2016-12-21 09:36:33
connected to source recovery catalog database
import validation complete
Finished import catalog at 2016-12-21 09:36:40
RMAN> list db_unique_name all;
List of Databases
DB Key DB Name DB ID Database Role Db_unique_name
------- ------- ----------------- --------------- ------------------
548781 DB3 829073653 PRIMARY DB3
514674 DB4 1753676295 PRIMARY DB4
523618 DB5 3779067219 PRIMARY DB5
551022 DB6 4018492764 PRIMARY DB6
545408 DB7 4110887114 PRIMARY DB7SQL> select * from rman.rc_database;
DB_KEY
DBINC_KEY
DBID
NAME
RESELOGS_CHANGE#
RESETLOGS_TIME
1
247199
4139331099
DB1
116371882675
06/07/2015 18:23:36
49382
49383
3896599226
DB2
90051108188
09/02/2012 16:18:57
548781
548782
829073653
DB3
1
08/09/2015 09:48:37
514674
514675
1753676295
DB4
1
29/06/2015 09:19:03
523618
523619
3779067219
DB5
1
27/08/2015 12:55:47
551022
551023
4018492764
DB6
1
02/09/2015 09:18:20
545408
545409
4110887114
DB7
1
22/06/2015 13:41:30
On the Source Catalog, the database will be automatically unregistered after the IMPORT CATALOG. If you need to retain the catalog on the source side even after the import then use keyword NO UNREGISTER.
Example:
RMAN> import catalog rman/U98wsjdw2#@stagecat no unregister;
-
Sauvegarde Full RMAN avec stratégie
La commande de backup full rman avec une stratégie de backup incrémentale (c'est à dire chaque jour une nouvelle sauvegarde ) est :
backup incremental level 0 device type disk database;
-
Valider une consistence de données avec RMAN
Oracle 11G comes with some additional checks for integrity checking. Can be done at database, tablespace, datafile, controlfile and block level.
source : http://www.online-database.eu/index.php/oracle-11g/139-validate-physical-and-logical-consistency
-
Commandes utiles RMAN
Liste des commandes utiles RMAN