Resuming Database Upgrade Assistant after Error

If your database upgrade by database upgrade assistant is caught by a glitch, a dialogue box may appear with options of “Ignore”, or “Abort”. There could be a situation whereby you can ignore the error and continue with the upgrade process. But, before you could do this, you would need to resolve the problem that encountered, before clicking the Ignore button to continue.

Installing Oracle 12c R2 Database Software on Linux 6 and Linux 7

In this article I would explain how to install Oracle 12c R2 database software on Linux 6 and Linux 7. If you want to use ASM as storage and/or Oracle Restart feature, you would need to install 12c R2 Grid Infrastructure before proceeding to install RDBMS software. You must be using at least Linux 6.4 for installation on Linux 6.

ORA-16191: Primary log shipping client not logged on standby

Password file difference is one of the biggest causes of log shipping failure from primary database to the standby. Follow this document to resolve ORA-1619. Following is what would appear in the alert log file if log shipping fails because of password file differences between primary site and standby site.

Fractured block found during backing up datafile

This error means that RMAN found an inconsistent block during the backup of a datafile. It is quite likely that on second attempt to read the block, RMAN is able to find a consistent image of the block, hence no further action would be required. But, if you need to perform a block recovery, this article will be worth reading. Alert log file will show message similar to the following when this error is reported.

ASM Disk not Accessible and not Appearing in V$ASM_DISK

If you are using ASMLib for your ASM storage and it is working perfectly fine; then, after adding a new ASM Disk you suddenly realize that although new disk is being listed by “oracleasm listdisks” command, it is still not appearing in V$ASM_DISK view. As a result, you are not able to add this new disk in your diskgroup because disk is not accessible to ASM instance. One reason of this could be that ASMLib configuration is not as it should be. Reasons could be: OS patching, oracleasm kernel driver update etc.