Oracle DBA (12c/19c) Articles and Scripts

The following solution can be useful when there is a gap of some archive log at standby which was physically removed/deleted at production end,   And it was not applied to standby database. Solution Out line: Take the scn of last log missing from Standby, Take RMAN incremental backup using SCN clause from production, and apply on standby. refer Oracle Support doc...      Findout Which archive Log is missing and MRP Process waiting for which Archivelog   Findout the Current SCN of Standby Database   Cancel the Recovery mode of Standby DB   TAKE RMAN incremental Backup in Production Database using FROM SCN  clause   Take Controlfile backup for standby   Copy the backup peace to standby and catalog it   Recover the Database with NOREDO   Switch database to copy or Change datafile names   Start the recovery mode of Standby DB Ref: 836986.1 and 1531031.1 Steps to perform for Rolling forward a standby database using RMAN in...

  GOAL Prior to performing an RMAN restore, there are certain actions you can take to ensure its success. Rather than running a restore for hours only to find that it failed due to something avoidable in the first place, like a missing backuppiece, it would be better to get the environment fully prepared upfront. A lot of time and confusion can be saved if we have a check list to work with first. SOLUTION 1) Check the Operating System and RDBMS Version Ideally you should be restoring to the same operating system version and RDBMS Version. If restoring to a different operating system you may need to covert between the Endians. If restoring to a higher version of the RDBMS you need to perform an upgrade before the database can be open for use:      Restoring a database to a higher patchset (Doc ID  558408.1 ) The combinations of operating systems and RDBMS can be quite complex. See the following note for further details:      Frequently Asked Q...

  12C ASM New feature (Doc ID 1571975.1) APPLIES TO: Oracle Database - Enterprise Edition - Version 12.1.0.1 and later Information in this document applies to any platform. PURPOSE This document is a discussion of a few 12C ASM new features with examples: 1. Failgroup_repair_time 2. Online disk replace 3. Estimate Work 4. V$ASM_OPERATION view DETAILS 1. FAILGROUP_REPAIR_TIME For versions <= 11g, we had disk_repair_time, from 12C onwards we have failgroup_repair_time at the ASM level.  Because failure group outages are more likely to be transient in nature and because replacing all the disks in a failure group is a much more expensive operation than replacing a single disk, it would typically make sense for failure groups to have a larger repair time to ensure that all the disks do not get dropped automatically in the event of a failure group outage. By default, the value of this diskgroup level attribute is  24Hours .  To set this attribute at ASM diskgroup level,...