Category: Use Incremental Backups
-
Recovery Catalog Versions – RMAN Backups and Reporting
Read More: Recovery Catalog Versions – RMAN Backups and ReportingI recommend that you create a recovery catalog for each version of the target databases that you are backing up. Doing so will save you some headaches with compatibility issues and upgrades. I have found it easier to use a recovery catalog when the database version of the rman client is the same version used…
-
Use Incremental Backups – RMAN Backups and Reporting
Read More: Use Incremental Backups – RMAN Backups and ReportingIncremental backup strategies are appropriate for large databases in which only a small portion of the database blocks change from one backup to the next. If you are in a data warehouse environment, you may want to consider an incremental backup strategy, because it can greatly reduce the size of your backups. For example, you…
-
Use Online Backups – RMAN Backups and Reporting
Read More: Use Online Backups – RMAN Backups and ReportingMost production databases have 24/7 availability requirements. Therefore, you need to take online RMAN backups. Your database must be in archivelog mode for online backups and to be able to recover to a point in time. You need to consider carefully how to place archivelogs, how to format them, how often to back them up,…
-
Types of Backups with RMAN – RMAN Backups and Reporting
Read More: Types of Backups with RMAN – RMAN Backups and ReportingThe are the different types of backups: • Full backup: All modified blocks associated with the data file are backed up. A full backup is not a backup of the entire database. For example, you can make a full backup of one data file. • Incremental level 0 backup: This backs up the same blocks…
-
Dropping a PDB- Large Objects
Read More: Dropping a PDB- Large ObjectsOccasionally, you may need to drop a PDB. You may want to do so because you do not need the PDB anymore or because you are transferring (unplugging/plugging) to a different CDB and you want to drop the PDB from the original CDB. If you need to remove a PDB, you can do it in…
-
Restricting Changes to SYSTEM at PDB- Large Objects
Read More: Restricting Changes to SYSTEM at PDB- Large ObjectsIn administering the PDB, the parameters can be changed as described at the PDB level. You can also change these parameters for a PDB at the CDB level. The changes can be restricted so that only CDB administrators can modify these settings for the PDB. This will allow the CDB DBAs to know how many…
-
Modifying Initialization Parameters Specific to a PDB- Large Objects
Read More: Modifying Initialization Parameters Specific to a PDB- Large ObjectsOracle allows some initialization parameters to be modified while connected as a privileged user to a PDB. You can view these parameters via the following query: SQL> select name from v$parameter where ispdb_modifiable=’TRUE’ order by name; Here is a snippet of the output: NAME sort_area_size sql_trace sqltune_category star_transformation_enabled statistics_level When you make initialization parameter changes…
-
Relocating a PDB- Large Objects
Read More: Relocating a PDB- Large ObjectsRelocating a PDB is an online action instead of unplugging and plugging a database. The source can be open for read and write, and there is minimal or no downtime. The files that are associated with the PDB are moved to a new location, and the PDB is added in the target CDB and then…
-
Refreshable Clone- Large Objects
Read More: Refreshable Clone- Large ObjectsIn creating a clone, it is a copy as of that point in time. A refreshable clone can sync back to the source PDB. This makes this clone useful for testing upgrades, making changes, and even switching the roles of a sourcing PDB and its refreshable clone. This can be useful for resources and possible…
-
Cloning the Seed Database- Large Objects
Read More: Cloning the Seed Database- Large ObjectsThe CREATE PLUGGABLE DATABASE statement can be used to create a PDB by copying the seed database’s data files. To do this, first, connect to the root container database as the SYS user (or a common user with create PDB privileges):$ sqlplus sysuser/ Cr4zyPa$$word1@mmdb23c as sysdba. The following SQL statement creates a pluggable database named…
Search
Popular Posts
-
Recovery Catalog Versions – RMAN Backups and Reporting
I recommend that you create a recovery catalog for each version of the target databases that you are backing up. Doing so will save you some headaches with compatibility issues and upgrades. I have found it easier to use a recovery catalog when the database version of the rman client is the same version used…
-
Registering a Target Database – RMAN Backups and Reporting
Now, you can register a target database with the recovery catalog. Log in to the target database server. Ensure that you can establish connectivity to the recovery catalog database. For instance, one approach is to populate the TNS_ADMIN/tnsnames.ora file with an entry that points to the remote database. On the target database server, register the…
-
Creating a Recovery Catalog – RMAN Backups and Reporting
When I use a recovery catalog, I prefer to have a dedicated database that is used only for the recovery catalog. This ensures that the recovery catalog is not affected by any maintenance or downtime required by another application (and vice versa). Listed next are the steps for creating a recovery catalog: 1. Create a…