Tuesday, November 16, 2021

Remove Oracle Multimedia in 19c

 Few of the Oracle documentation says Oracle Multimedia is deprecated in 19c. You might see the component name Oracle Multimedia (ORDIM) in the dba_registry once you login into the database, it might not function anymore. But still, to clean it up from the database end, you can implement the below steps.

[oracle@sajidserver01 ~]$ sqlplus "/ as sysdba"

SQL> alter session set "_oracle_script"=TRUE;

Session altered.

SQL> drop user MDSYS cascade;

User dropped.

SQL> @?/rdbms/admin/catcmprm.sql ORDIM

Session altered.

About to remove Oracle Multimedia.

Checking to see if anyone is using Oracle Multimedia.

Session altered.

Oracle Multimedia is not being used

PL/SQL procedure successfully completed.

Session altered.

Are you sure you want to remove Oracle Multimedia (Y/N): Y

PL/SQL procedure successfully completed.

Session altered.

Removing Oracle Multimedia

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

Commit complete.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

Session altered.

Session altered.

SQL> alter session set "_oracle_script"=FALSE;

Session altered.

Now check your dba_registry it will be clean.

SQL> SELECT comp_id,comp_name,version FROM dba_registry where comp_id='ORDIM';

no rows selected

Make sure the above steps are implemented in all the pluggable databases as well. If not the databases will end up in restricted mode and users will not be able to connect.

######
Note:
######

If you face the below error while dropping the component name.

ERROR at line 1:
ORA-28014: cannot drop administrative users

To bypass it try using alter session set "_oracle_script"=TRUE; then you will be good to drop the component.

Friday, September 24, 2021

[INS-41210] one of the available network subnets is marked for use by ASM.

 When you opt for Advanced Installation for 12.1.0.2 Grid installation on RHEL 8 operating system and when you do designate the private interfaces subnets either as "ASM" or as "ASM & Private". You will get [INS-41210] one of the available network subnets is marked for use by ASM.



Solution:

Just use "Private" rather than "ASM & Private" for both the private interface subnets and leave the last one as Public for the Public interface subnet.

Friday, August 6, 2021

runcluvfy.sh command gets hung on 19c before Grid Installation

 When you are running pre-check for cluster installation using runcluvfy command in 19c to install on RHEL 8 operating system, it gets hung and does not generate any report.

[grid@sajidserver01 19000]$ ./runcluvfy.sh stage -pre crsinst -n sajidserver01,sajidserver02 -verbose==>hangs

To get the detailed output, you can follow the below workaround. By setting an environment variable.

[grid@sajidserver01 19000]$ export CV_ASSUME_DISTID=OL7
[grid@sajidserver01 19000]$ ./runcluvfy.sh stage -pre crsinst -n sajidserver01,sajidserver02 -verbose

     | |  | |  | |
     | |  | |  | |
     | |  | |  | |   Output is Truncated
   \                /
     \            /
       \        /
         \    /
           \/

CVU operation performed:  stage -pre crsinst
Date:  Aug 6, 2021 11:55:22 PM
CVU home:/usr/app/grid/product/19000/
User: grid

Hope this helps with Grid 19c RAC builds.


Friday, June 18, 2021

How to detach and attach Oracle Home to an inventory

Sometimes when you are working on database patching, you will notice opatch lsinventory will be completely corrupted. In the next few minutes, I will walk you through a step-by-step process of getting it fixed.

#####
Error:
#####
List of Homes on this system:
  Home name= OraGI12c_Home1, Location= "/usr/12.2/grid"
  Home name= agent13c2, Location= "/usr/agent13c/agent_13.2.0.0.0"
  Home name= OraDB12_Home1, Location= "/usr/product/12.2.0.2"
OPatchSession cannot load inventory for the given Oracle Home /usr/agent13c/agent_13.2.0.0.0. Possible causes are:
   No read or write permission to ORACLE_HOME/.patch_storage
   Central Inventory is locked by another OUI instance
   No read permission to Central Inventory
   The lock file exists in ORACLE_HOME/.patch_storage
   The Oracle Home does not exist in Central Inventory
   OUI-67073:UtilSession failed: RawInventory gets null OracleHomeInfo
UtilSession failed: RawInventory gets null OracleHomeInfo
Log file location: /usr/agent13c/agent_13.2.0.0.0/cfgtoollogs/opatch/opatch2021-01-02_01-30-00PM_1.log

####
Fix:
####

Detach and attach the home to fix it like below. Then check opatch lsinventory to make sure it is properly fixed. This system is a two-node Oracle RAC. One beauty is, this does not require any database downtime and can be fixed on the fly.

cd /usr/agent13c/agent_13.4.0.0.0/oui/bin
[oracle@sajidserver01 bin]$ ./detachHome.sh ORACLE_HOME=/usr/agent13c/agent_13.2.0.0.0 ORACLE_HOME_NAME=agent13c2 CLUSTER_NODES=sajidserver01, sajidserver02 INVENTORY_LOCATION=/usr/oraInventory LOCAL_NODE=sajidserver01
Launcher log file is /tmp/OraInstall2021/launcher2021-01-02_01-58-40PM.log.
Ignoring command-line variable "INVENTORY_LOCATION=/usr/oraInventory".
Checking swap space: must be greater than 500 MB.   Actual 34811 MB    Passed
Checking if this platform requires a 64-bit JVM.   Actual 64    Passed (64-bit not required)
detachHome was successful.
Logs successfully copied to /usr/oraInventory/logs.
cd /usr/agent13c/agent_13.2.0.0.0/oui/bin

Now attach the home.

[oracle@sajidserver01 bin]$ ./attachHome.sh ORACLE_HOME=/usr/agent13c/agent_13.2.0.0.0 ORACLE_HOME_NAME=agent13c2 CLUSTER_NODES=sajidserver01, sajidserver02 INVENTORY_LOCATION=/usr/oraInventory LOCAL_NODE=sajidserver01
Launcher log file is /tmp/OraInstall2021-02-17_02-59-22PM/launcher2021-02-17_02-59-22PM.log.
Checking swap space: must be greater than 500 MB.   Actual 34811 MB    Passed
Checking if this platform requires a 64-bit JVM.   Actual 64    Passed (64-bit not required)
attachHome was successful.
Logs successfully copied to /usr/oraInventory/logs.

Check the inventory, it will be fixed.

[oracle@sajidserver01 bin]$ opatch lsinventory
Oracle Interim Patch Installer version 13.9.4.2.2
Copyright (c) 2021, Oracle Corporation.  All rights reserved.
Oracle Home       : /usr/agent13c/agent_13.2.0.0.0
Central Inventory : /usr/oraInventory
   from                  : /usr/agent13c/agent_13.2.0.0.0/oraInst.loc
OPatch version    : 13.9.4.2.2
OUI version       : 13.9.4.0.0
Log file location : /usr/agent13c/agent_13.2.0.0.0/cfgtoollogs/opatch/opatch2021-01-02_07-00-50PM_1.log
   | |  | |  | |
     | |  | |  | |
     | |  | |  | |   Output is Truncated
  \                /
    \            /
      \        /
        \    /
          \/
OPatch succeeded.

Now your inventory is back in business.

Tuesday, May 11, 2021

Oracle RAC instance start and stop

Oracle RAC instance start and stop

[oracle@sajidserver1~]$srvctl status database -d sajiddb
Instance sajiddb2 is running on node sajidserver2
Instance sajiddb1 is running on node sajidserver1

[oracle@sajidserver1]srvctl stop instance –d sajiddb –i sajiddb1 -f
PRKO-3122 : -instance option or -node option is required for stopping an instance of database null

There is nothing wrong with the above command, but it suddenly stopped working. Anyhow, if you notice the error (PRKO-3122 : -instance option or -node option is required for stopping an instance of database null). To make it work, use the below command.

[oracle@sajidserver1]srvctl stop instance –db sajiddb –instance sajiddb1 -f
[oracle@sajidserver1]

The above command works for various oracle database versions 19c/18c/12c. Similarly to start the instance you can use the below command.

[oracle@sajidserver1]srvctl start instance –db sajiddb –instance sajiddb1
[oracle@sajidserver1]

Monday, February 15, 2021

Installing Oracle Enterprise Manager Cloud Control 13c Release 4 (13.4.0.0) on Oracle Linux 7

 

        In this post, I will be discussing installing Oracle Enterprise Manager Cloud Control 13c Release 4 (13.4.0.0) on Oracle Enterprise Linux 7. OEM makes the life of DBA or DMA much easier. You need to have the appropriate Linux OS packages, kernel parameters, and database parameters to be in place.  First, you need to install the repository database, for step by step instructions to install 12.2 database you can follow (Link)


[oracle@sajidserver ~]$ cd /usr/app/stage/

[oracle@sajidserver stage]$ ls -ltr

-rwxrwxr-x 1 oracle oinstall 1623577684 Jul 20 14:38 em13400_linux64.bin

-rwxrwxr-x 1 oracle oinstall 2109004737 Jul 20 14:48 em13400_linux64-2.zip

-rwxrwxr-x 1 oracle oinstall 2047749474 Jul 20 14:55 em13400_linux64-3.zip

-rwxrwxr-x 1 oracle oinstall 2117312528 Jul 20 15:05 em13400_linux64-4.zip

-rwxrwxr-x 1 oracle oinstall  808014516 Jul 20 15:09 em13400_linux64-5.zip

-rwxrwxr-x 1 oracle oinstall 2143125187 Jul 20 15:27 em13400_linux64-6.zip

-rwxrwxr-x 1 oracle oinstall 1879163226 Jul 20 15:34 em13400_linux64-7.zip

[oracle@sajidserver stage]$ ./em13400_linux64.bin

Launcher log file is /tmp/OraInstall2020_15AM/launcher2020_AM.log.

Extracting the installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Done

Checking monitor: must be configured to display at least 256 colors.  Actual unknown.  

Checking swap space: must be greater than 512 MB.   Actual 2047 MB    Passed

Checking if this platform requires a 64-bit JVM.   Actual 64    Passed (64-bit not required)

You must fulfill these requirements before continuing.

Continue? (yes [y] / no [n]) [n]

y

You have confirmed that the product can be installed on this platform.

Continuing with the installation.













At this point, you are done with the installation of  Oracle Enterprise Manager Cloud Control 13c Release 4 (13.4.0.0) on Oracle Linux 7. Please email me if anyone needs any advice during the installation, will be happy to help. Happy Monitoring!.