Error on WLS Patching in EBS R122 - Patch was not found in the patch catalog

Today I have faced an issue with WLS patching and observed the MT ETCC utility has listed the patches missing from the WLS home. However some of those patches are already applied and those installed patches also listed in MT ETCC report as not applied. So I have checked whether patches are properly applied or not with using following command - "bsu.sh -report | grep -i XXXX"  and observed below error message.

$ bsu.sh -report | grep -i XXXX

ERROR..................... Patch "XXXX" was not found in the patch catalog. Make sure your catalog is up to date.
WARNING................... Archive for Patch "XXXX" is not availabe, details skipped. Download the archive to generate the full report.
Patch ID.................. XXXX  
$

Then I tried to remove that WLS patch, but got error as "Encountered unrecognized patch ID"

$ sh bsu.sh -remove -patchlist=XXXX  -prod_dir=$MW_HOME/wlserver_10.3 -verbose

Encountered unrecognized patch ID: XXXX       

Again try to install that patch, now this time noticed that "Patch already installed:XXXX in profile: Default"

$ sh bsu.sh -install -patchlist=XXXX -prod_dir=$MW_HOME/wlserver_10.3 -patch_download_dir=$MW_HOME/utils/bsu/cache_dir -verbose

Patch already installed: XXXX in profile: Default  

Using below command, I have confirmed that WLS patch catalog was corrupt or missing for file system "fs1". That's why the MT ETCC is listing all patches as missing for WLS as no patch data is recorded for this home.   DownloadDir (/u01/HYDINFRA/working/WLSPathces) was used non-default directory for patching and that directory (/u01/HYDINFRA/working/WLSPathces) also does not exist.

$ cd $FMW_HOME/utils/bsu
$ bsu.sh -view -status=applied -prod_dir=$FMW_HOME/wlserver_10.3                                                
    ProductName:       WebLogic Server                                                                                                           
    ProductVersion:    10.3 MP6                                                                                                                  
    Components:        WebLogic Server/Core Application Server,WebLogic Server/Admi                                                              
                       nistration Console,WebLogic Server/Configuration Wizard and                                                               
                       Upgrade Framework,WebLogic Server/Web 2.0 HTTP Pub-Sub Serve                                                              
                       r,WebLogic Server/WebLogic SCA,WebLogic Server/WebLogic JDBC                                                              
                        Drivers,WebLogic Server/Third Party JDBC Drivers,WebLogic S                                                              
                       erver/WebLogic Server Clients,WebLogic Server/WebLogic Web S                                                              
                       erver Plugins,WebLogic Server/UDDI and Xquery Support,WebLog
                       ic Server/Evaluation Database,WebLogic Server/Workshop Code
                       Completion Support
    BEAHome:           /u01/HYDINFRA/R122EBS/fs1/FMW_Home
    ProductHome:       /u01/HYDINFRA/R122EBS/fs1/FMW_Home/wlserver_10.3
    PatchSystemDir:    /u01/HYDINFRA/R122EBS/fs1/FMW_Home/utils/bsu
    PatchDir:          /u01/HYDINFRA/R122EBS/fs1/FMW_Home/patch_wls1036
    Profile:           Default
    DownloadDir:       /u01/HYDINFRA/working/WLSPathces
    JavaVersion:       1.6.0_29
    JavaVendor:        Sun
    
    
    Patch ID:          XXXX
    Patch ID:          XXXX
    Patch ID:          XXXX (XXXXXXXX)
    Patch ID:          XXXX (XXXXXXXX)
    Patch ID:          XXXX (XXXXXXXX)
    Patch ID:          XXXX (XXXXXXXX)
    Patch ID:          XXXX (XXXXXXXX)
    Patch ID:          XXXX (XXXXXXXX)
    Patch ID:          XXXX (XXXXXXXX)
    Patch ID:          XXXX (XXXXXXXX)
    
$

Workaround for this issue:

1) Created same directory structure and copied all missing patch information.

$ mkdir -p /u01/HYDINFRA/working/WLSPathces 

$ cp -r /u01/HYDINFRA/R122EBS/fs1/FMW_Home/utils/bsu/cache_dir/*  /u01/HYDINFRA/working/WLSPathces

2) Re-tested BSU report and confirmed that no errors now.

$ bsu.sh -report | grep -i XXXX
      Patch ID.................. XXXX

3) Re-ran MT ETCC checker and noticed correct results returned.

To overcome this issue permanently, you need to ensure the next patch will be applied on the correct/default patch_download_dir.

$ cd $FMW_HOME/utils/bsu

$ bsu.sh -install -verbose -patchlist=XXXX  -prod_dir=$FMW_HOME/wlserver_10.3 -patch_download_dir=$FMW_HOME/utils/bsu/cache_dir 

Thats it. Hope this article will help you.

Thanks,
Chowdari

Oracle Database 19c Installation on Oracle Linux 7 (OL7)

This article describes the installation of Oracle Database 19c on Oracle Linux 7 (OL7) on VirtualBox.

Introduction:

For installing 19c in your laptop or desktop, computer should have minimum 4 GB or more of RAM required, and minimum 30GB or more of storage required.

This article uses the 64-bit versions of Oracle Linux 7 and Oracle 19c.

Prerequisite: Oracle Linux 7 Install on VirtualBox

Download Software:

Download Oracle 19c database software for Linux x86-64 from OTN or edelivery and copy the files to linux server (on VirtualBox) using winscp or shared folder.

Oracle Installation Prerequisites

Either you can perform Automatic setup  or Manual setup to complete the prerequisites.

Automatic Setup:

Install "oracle-database-preinstall-19c" package to perform all prerequisite setup. use the following command

# yum install -y oracle-database-preinstall-19c           

Manual Setup:

If you have not used the "oracle-database-preinstall-19c" package to perform all prerequisites, you have to manually perform the following setup tasks.

ORA-16698: 12c Dataguard Broker Setup Error

Recently I have configured dataguard on 12c database. While configuring dataguard broker I have encountered an "Error: ORA-16698: LOG_ARCHIVE_DEST_n parameter set for object to be added"

[oracle@primdb dbs]$ dgmgrl
DGMGRL for Linux: Version 12.1.0.2.0 - 64bit Production

Copyright (c) 2000, 2013, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/dataguard
Connected as SYSDG.
DGMGRL> CREATE CONFIGURATION 'DR_Config' AS PRIMARY DATABASE IS 'primdb' CONNECT IDENTIFIER IS primdb;
Error: ORA-16698: LOG_ARCHIVE_DEST_n parameter set for object to be added

Failed.
DGMGRL>
SQL>

Solution:

Generally you will not receive this error on earlier database versions (Pre 12c). As per Oracle database 12c documentation, "Any LOG_ARCHIVE_DEST_n parameters that have the SERVICE attribute set, and if the NOREGISTER attribute is Not set, then you must remove/clear the 'LOG_ARCHIVE_DEST_n' before creating the broker configuration". Clear archive destination for both primary and standby side and then configure the Dataguard broker.

Once you complete the DataGuard broker setup then revert back the LOG_ARCHIVE_DEST parameter to old values in both primary and standby side.

On Primary Side:

SQL> show parameter LOG_ARCHIVE_DEST_2

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_2                   string      SERVICE=standb  ASYNC VALID_FO
                                                 R=(ONLINE_LOGFILES,PRIMARY_ROL
                                                 E)  DB_UNIQUE_NAME=standb
SQL>

SQL> alter system set LOG_ARCHIVE_DEST_2='' scope=both;

System altered.

SQL> 


DGMGRL> CREATE CONFIGURATION 'DR_Config' AS PRIMARY DATABASE IS 'primdb' CONNECT IDENTIFIER IS primdb;
Configuration "DR_Config" created with primary database "primdb"
DGMGRL>

DGMGRL> show configuration;

Configuration - DR_Config

  Protection Mode: MaxPerformance
  Members:
  primdb - Primary database

Fast-Start Failover: DISABLED

Configuration Status:
DISABLED

DGMGRL>



On Standby Side:

SQL> show parameter LOG_ARCHIVE_DEST_2

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_2                   string      SERVICE=PRIMARY  ASYNC VALID_F
                                                 OR=(ONLINE_LOGFILES,PRIMARY_RO
                                                 LE)  DB_UNIQUE_NAME=primdb
SQL> alter system set LOG_ARCHIVE_DEST_2='' scope=both;

System altered.

SQL>


DGMGRL> ADD DATABASE 'standb' AS CONNECT IDENTIFIER IS standb MAINTAINED AS PHYSICAL;
Database "standb" added
DGMGRL>

DGMGRL> enable configuration;
Enabled.
DGMGRL> show configuration;

Configuration - DR_Config

  Protection Mode: MaxPerformance
  Members:
  primdb - Primary database
    standb - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS   (status updated 10 seconds ago)

DGMGRL> 

That's it.. Hope this article will help you.

Thanks,
Chowdari