Posts

Showing posts with the label Rman

RMAN Catalog Upgrade - DBMS.RCVCAT Version in RCVCAT database is not Current

Image
RMAN Catalog Upgrade Oracle Database upgrade is routine activity for Oracle DBA and with new database versions coming upgrading Database has become important to make sure you database does not go out of support. In this blog , We will discuss about a common problem which faced by DBA post DB upgrade. When your RMAN catalog is at the lower version WRT to you client Database then you get error "PL/SQL Package DBMS.RCVCAT Version in RCVCAT database is not Current" . In order to resolve this issue , We need to upgrade our RMAN Catalog. Below are the Steps to upgrade RMAN Catalog: 1)  Take the export backup of  RMAN catalog owner  account. expdp catlog_own/******* directory=dump1 dumpfile=RMANcatalog_own.dmp 2) Connect to RMAN Catalog and any client with higher version of the DB. rman target / catalog catalog_own/******@catalogdb.WORLD 3) Perform Catalog upgrade.          RMAN> upgrade catalog;    Recovery catalog owner is CATALO...

Oracle RMAN Compression

Image
Oracle RMAN Compression  Starting with Oracle 11g Oracle added several compression algorithms to compress data. They can be used for compressing tables, LOBs , compressed data pump exports or even RMAN backups. Unfortunately for some compression algorithms you need to purchase the “Advanced Compression Option”. The following table lists the available RMAN compression options, the most likely compression algorithm being used and states if an additional license is required: Use below command to Configure RMAN: To configure RMAN to use compression at all you can use: CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET; or CONFIGURE DEVICE TYPE TAPE BACKUP TYPE TO COMPRESSED BACKUPSET; To configure the different backup algorithms: CONFIGURE COMPRESSION ALGORITHM 'BASIC'; CONFIGURE COMPRESSION ALGORITHM 'NONE'; CONFIGURE COMPRESSION ALGORITHM 'LOW'; CONFIGURE COMPRESSION ALGORITHM 'MEDIUM'; CONFIGURE COMPRESSION ALGORITHM 'HIGH'; Test &...

Partial recovery of Oracle database using RMAN

Partial recovery of database using RMAN For oracle DBA ,Their could be situations where application team can request to restore partial database up to a point in Time.. (Means few application tablespace). In todays blog , We will discuss about how we can resolve such situation. Assumption is that we are doing partial database restore on the different server then production server. Below are the steps , We are going to follow for partial recovery: Step 1) Create pfile from spfile and make modifications as per the storage in New machine like the new disk group name etc. more inittedtdb.ora tedtdb.__db_cache_size=16240345088 tedtdb.__java_pool_size=67108864 tedtdb.__large_pool_size=67108864 tedtdb.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment tedtdb.__pga_aggregate_target=12884901888 tedtdb.__sga_target=19327352832 tedtdb.__shared_io_pool_size=0 tedtdb.__shared_pool_size=2415919104 tedtdb.__streams_pool_size=134217728 *._trace_files_public=TRUE *.audit_file_dest...

Oracle Block Corruption - Detection and Resolution

Oracle Block Corruption - Detection and Resolution Any kind of corruption in database can  lead to stand still operation of the organization and can cause sever impact to organisation. In this blog , We are going to discuss about Block Corruption of the oracle database. Block Corruption :  Oracle Block Corruption occurs due inconsistent block Header ,Footer ,Checksum or Structure. Depending on the kind of insistency ,We can divide corruption into Physical and Logical corruption. Physical Corruption is due to Bad header, header or footer mismatch ,Invalid Block checksum & misplaced block. Usually this kind of the block corruption are due to external reason and difficult to resolve by oracle utilities alone.  Logical Corruption is due to corrupt or invalid Block structure when block checksum is valid. This kind of the Corruption can be resolved by the Oracle Utilities. Detection of Block Corruption Whenever a corrupt block is read Oracle reports an error in the alert l...