Infrastructure at your Service
When RMAN backups archivelogs, it does a logswitch before backing up all archivelogs. In some cases this log switching should be suppressed. This can be done with expression “until time ‘sysdate’”, which actually filters nothing. For example: backup archivelog until time ‘sysdate';
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…
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 ———-…
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…
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.
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…
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,…
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…
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…
Relying to much on the RMAN Data Recovery Advisor is not always the best idea. In a lot of situations, it tells you the right things, however, sometimes it tells you not the optimal things, and sometimes, RMAN list failure does not show any failure at all, even if there is one. So … let’s simulate quickly a loss of a datafile during the normal runtime of the database. The result is a clear error…
