Infrastructure at your Service

RMAN Archives - Blog dbi services

Pierre Sicot

PDB RMAN backups available after plugging in on a new CDB with Oracle 18c

By | Database Administration & Monitoring | No Comments

With Oracle 18c, it is possible to use PDB rman backups created on the source CDB (they are called PREPLUGIN backups) when the PDB has been relocated to a target CDB. In my environment, my original CDB is DB18, with the PDB named pdborig. The target CDB is PSI18. The first step consist in running a rman backup on pdborig: oracle@localhost:/u00/app/oracle/ [DB18] rman target sys/manager@pdborig Recovery Manager: Release 18.0.0.0.0 – Production on Tue May 15…

 
Read More
Marc Wagner

RMAN debugging during catalog import

By | Database management, Oracle | No Comments

In this post I would like to share how I have been able to troubleshoot and solve a catalog import issue using RMAN debug function. As we can see, the error message provided by RMAN is not very helpful. oracle@vmtestoradg1:/home/oracle/ [RCAT12C] rman catalog rcat/manager Recovery Manager: Release 12.2.0.1.0 connected to recovery catalog database RMAN> import catalog rcat/manager@RCAT11G; Starting import catalog at 05-JAN-2018 14:11:45 connected to source recovery catalog database RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE…

 
Read More
Marc Wagner

ORACLE 11g to 12c RMAN catalog migration

By | Database management, Oracle | 2 Comments

This is a small migration demo of a 11g catalog (RCAT11G) to a new 12c catalog (RCAT12c). Demo databases environments have been easily managed thanks to DBI DMK tool. oracle@vmreforadg01:/home/oracle/ [RCAT11G] sqh SQL*Plus: Release 11.2.0.4.0 oracle@vmtestoradg1:/home/oracle/ [RCAT12C] sqh SQL*Plus: Release 12.2.0.1.0   Current configuration Displaying the list of databases registered in the RCAT11g catalog. SQL> select instance_name from v$instance; INSTANCE_NAME —————- RCAT11G SQL> select * from rcat.rc_database;     DB_KEY  DBINC_KEY       DBID NAME     RESETLOGS_CHANGE# RESETLOGS ———-…

 
Read More
Clemens Bleile

Workaround for bug 19566227/20563128 doing Cross Platform Migration (MOS Note 1389592.1)

By | Database Administration & Monitoring, Database management | One Comment

In a project I have to move an Oracle 11.2.0.4-DB (around 7TB in size) from Sparc Solaris (called Source in the remainder of this Blog) to Linux x86-64 (called Target in the remainder of the Blog). I.e. a platform migration from Big Endian to Little Endian. A good method to do that is described in My Oracle Support Note 1389592.1: 11G – Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup Basically I copy the…

 
Read More
Franck Pachot

12cR2 RMAN> REPAIR

By | Database management | One Comment

Do you know the RMAN Recovery advisor? It detects the problems, and then you: RMAN> list failure; RMAN> advise failure; RMAN> repair failure; You need to have a failure detected. You can run Health Check if it was not detected automatically (see https://blog.dbi-services.com/oracle-12c-rman-list-failure-does-not-show-any-failure-even-if-there-is-one/). In 12.2 you can run the repair directly, by specifying what you want to repair.  

 
Read More

Oracle 12c – Why you shouldn’t do a crosscheck archivelog all in your regular RMAN backup scripts

By | Database Administration & Monitoring | 3 Comments

Crosschecking in RMAN is quite cool stuff. With the RMAN crosscheck you can update an outdated RMAN repository about backups or archivelogs whose repository records do not match their physical status. For example, if a user removes archived logs from disk with an operating system command, the repository (RMAN controlfile or RMAN catalog) still indicates that the logs are on disk, when in fact they are not. It is important to know, that the RMAN…

 
Read More

Oracle 12c – Recreating a Controlfile in a Data Guard environment with noresetlogs

By | Database Administration & Monitoring, Database management | No Comments

Sometimes you might run into situations where the controlfile does not represent the backups and archivelogs correctly, because of a mismatch of the control_file_record_keep_time and the RMAN retention. The controlfile has non circular and a circular records. Non circular are e.g. database information, redo threads, datafiles and so on. These non circular records don’t age out, however, they can be reused, e.g. when a tablespace is dropped. The circular records are e.g. the log history,…

 
Read More

Oracle 12c – How to correct the error: “RMAN-20005: target database name is ambiguous”

By | Database Administration & Monitoring, Database management | No Comments

I do have a Data Guard environment, where I have configured the RMAN DB_UNIQUE_NAME persistent setting for my primary and the standby. With the RMAN DB_UNIQUE_NAME settings I am able to run reports my Oracle Data Guard environment from any database. I could e.g. list all archivelogs for SITE1 from SITE2 or the other ways around. Or I could show all persistent settings for SITE1 from SITE2 and of course the other way around. The…

 
Read More
Oracle Team

Oracle 12c – Issues with the HEATMAP Segment even if the heat map feature is not used

By | Database Administration & Monitoring, Database management | No Comments

When I don’t need I feature, I don’t turn it on, or do not use it because it reduces the possibility to run into issues. Most of the times this is true, however, during the preparation for an RMAN workshop, the RMAN list failure command showed me the following dictionary issue. RMAN> list failure; using target database control file instead of recovery catalog Database Role: PRIMARY List of Database Failures ========================= Failure ID Priority Status…

 
Read More