Category: Registering a Target Database

Recovery Catalog Versions – RMAN Backups and Reporting

19/07/2024

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…
Read More: Recovery Catalog Versions – RMAN Backups and Reporting
Registering a Target Database – RMAN Backups and Reporting

19/06/2024

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…
Read More: Registering a Target Database – RMAN Backups and Reporting
Delete Backups, Based on Retention Policy – RMAN Backups and Reporting

19/01/2024

You can report on backups that RMAN has determined to be obsolete per the retention policy, as follows: RMAN> report obsolete; To delete obsolete backups, run the DELETE OBSOLETE command: RMAN> delete obsolete; You are prompted with this: Do you really want to delete the above objects (enter YES or NO)? If you are scripting…
Read More: Delete Backups, Based on Retention Policy – RMAN Backups and Reporting
Set the Autobackup of the Control File – RMAN Backups and Reporting

19/12/2023

You should always configure RMAN to back up the control file automatically after running any RMAN BACKUP or COPY command or after you make physical changes to the database that result in updates to the control file (such as adding/removing a data file). Use the SHOW command to display the current setting of the control…
Read More: Set the Autobackup of the Control File – RMAN Backups and Reporting
Determine the Location for the Snapshot Control File – RMAN Backups and Reporting

19/11/2023

RMAN requires a read-consistent view of the control file for the following tasks: • Synchronizing with the recovery catalog • Backing up the current control file RMAN creates a snapshot copy of the current control file that it uses as a read-consistent copy while it is performing these tasks. This ensures that RMAN is working…
Read More: Determine the Location for the Snapshot Control File – RMAN Backups and Reporting
Use Online Backups – RMAN Backups and Reporting

19/10/2023

Most 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,…
Read More: Use Online Backups – RMAN Backups and Reporting
Restricting Changes to SYSTEM at PDB- Large Objects

19/04/2023

In 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…
Read More: Restricting Changes to SYSTEM at PDB- Large Objects
Modifying Initialization Parameters Specific to a PDB- Large Objects

19/03/2023

Oracle 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…
Read More: Modifying Initialization Parameters Specific to a PDB- Large Objects
Managing a Listener in a PDB Environment- Large Objects

19/02/2023

Recall from Chapter 2 that a listener is the process that enables remote network connections to a database. Most database environments require a listener to operate. When a client attempts to connect to a remote database, the client provides three key pieces of information: the host the listener is on, the host port the listener…
Read More: Managing a Listener in a PDB Environment- Large Objects
Administrating Pluggable Databases- Large Objects

19/01/2023

We have already covered many administration tasks for CDBs and PDBs. The PDBs are considered application databases or configured for user objects and data. You still have administrative tasks that need to be performed while connected directly to the PDB. You can open/close a PDB, check its status, show currently connected users, and so on.…
Read More: Administrating Pluggable Databases- Large Objects