Deinstall 12.2.0.1 Grid Infrastructure Home After Being Upgraded to 18c GI

Grid Infrastructure 12.2.0.2 has been upgraded to 18c GI successfully. So 12.2.0.1 GI_HOME needs to be de-installed.  There are two ways to uninstall the old GI_HOME ( 12.2.0.1)

1) Detach GI_HOME and Remove the GI_HOME manually:

$ export ORACLE_HOME=/u01/app/grid/12.2.0.1
$ $ORACLE_HOME/OPatch/opatch lsinventory -all
$ cd $ORACLE_HOME/oui/bin
$ ./runInstaller -silent -detachHome ORACLE_HOME="/u01/app/grid/12.2.0.1"
$ unset ORACLE_HOME

-- as root user

# cd /u01/app/grid
# rm -fr 12.2.0.1

For any reason, if the above command fails, then on every node:

$ export ORACLE_HOME=/u01/app/grid/12.2.0.1 
$ $ORACLE_HOME/OPatch/opatch lsinventory -all 
$ cd $ORACLE_HOME/oui/bin 
$ ./runInstaller -silent -local -detachHome ORACLE_HOME="/u01/app/grid/12.2.0.1"
$ unset ORACLE_HOME
-- as root user
# cd /u01/app/grid
# rm -fr 12.2.0.1

2) Deinstall old GI_HOME by using “deinstall” tool :

a) Log in as root, change the permission and ownership of the old GI_HOME ( 12.2.0.1) on both nodes.

# chmod -R 755 /u01/app/12.2.0.1/grid
# chown -R grid /u01/app/12.2.0.1/grid
# chown grid /u01/app/12.2.0.1

b) Run “deinstall” under the to be deleted GI_HOME( /u01/app/12.2.0.1/grid).

$ /u01/app/12.2.0.1/grid/deinstall/deinstall

Checking for required files and bootstrapping ...
Please wait ...
Location of logs /u01/app/oraInventory/logs/

############ ORACLE DECONFIG TOOL START ############


######################### DECONFIG CHECK OPERATION START ################
## [START] Install check configuration ##
...
..
.

c) Refer and check the logs :

The Log of Deinstall 12.2.0.1 GI_HOME

How to Disable RAC Databases Automatic Startup

Sometimes we need disable automatic startup of RAC databases , due to server resource issues or server maintenance, etc. Here are a couple of common methods :

Subscribe to get access

Read more of this content when you subscribe today.

[DBT-11211] The Automatic Memory Management option is not allowed when the total physical memory is greater than 4GB

In 12.2.0.1, when creating a multitenant CDB database by using DBCA, the below error occurs:

[DBT-11211] The Automatic Memory Management option is not allowed
            when the total physical memory is greater than 4GB
DBT-11211
DBT-11211

Workaround

Choose to use ASMM ( Automatic Shared Memory Management ) instead of AMM ( Automatic Memory Management ).

DBCA Memory Option
DBCA Memory Option

Silent Installation of Oracle 12.2.0.1 RAC Software on Linux 7

Silent Installation of Oracle RAC Binary

This post demonstrates how to install Oracle 12.2.0.1 RAC binary in silent on Oracle Linux 7.

Subscribe to get access

Read more of this content when you subscribe today.

Database Logon Trigger to Block Sessions from Some Users using Toad,SQL Developer….

Here is an example of  database logon trigger for blocking specific users from accessing database through tools like  Toad or SQL Developer tools, etc.

Subscribe to get access

Read more of this content when you subscribe today.

Any database users with “ADMINISTER DATABASE TRIGGER” will bypass the database logon trigger.

SQL> grant ADMINISTER DATABASE TRIGGER to testuser;

Grant succeeded.

SQL> connect testuser
Enter password:
Connected.