How to Disable Transparent HugePages on Oracle Linux 7

It is recommended by Oracle to disable Linux native Transparent HugePages on Oracle database servers, to avoid potential Oracle database performance issues.

This post introduces how to disable Linux native Transparent HugePages, and verify Transparent Hugepages disabled or not.

Subscribe to get access

Read more of this content when you subscribe today.

Upgrade Oracle Grid Infrastructure from 12.2.0.1 to 18c

Contents

  • Pre-requisite checks
    • User ID for both oracle and grid user
    • Oracle ASM LIB configurations
    • Oracle Grid Infrastructure and Oracle RAC Packages
    • Stop Transparent HugePages
    • install cvuqdisk
    • grid/oracle profiles
    • Check and setup resource Limits
    • Run ORAchk utility to have pre-upgrading checks
    • run the command runcluvfy.sh stage -pre crsinst -upgrade to check the readiness of your Oracle Clusterware installation for upgrades
    • Download and apply the latest opatch utility onto GI home and DB homes
  • Upgrading Oracle Grid Infrastructure
  • Post Oracle Grid Infrastructure Upgrading
    • Check SCAN configuration
    • Post Upgrading Cluster Verification
    • Run Orachk -u -o post
    • Check all cluster resource status

Subscribe to get access

Read more of this content when you subscribe today.

Cleanup .patch_storage Directory under ORACLE_HOME

Now and then, DBA might experience disk space issues while patching and upgrading GI or DB. Under ORACLE_HOME there is a .patch_storage directory which uses huge disk space and stores all the patches already applied onto ORACLE_HOME.  Some are backup files and directories.

Following are the common methods to solve the disk space issues under ORACLE_HOME due to huge .patch_storage directory size.

Subscribe to get access

Read more of this content when you subscribe today.

CLSRSC-488: Patching the Grid Infrastructure Management Repository database failed

opatchauo failed when applying GI release update.

[root@racnode1 ~]# /u01/app/12.2.0.1/grid/OPatch/opatchauto 
                     apply /media/sf_Software/12201-190115/30501932
...
..
.
CRS-4123: Oracle High Availability Services has been started.
Oracle Clusterware active version on the cluster is [12.2.0.1.0]. 
                    The cluster upgrade state is [ROLLING PATCH]. 
The cluster active patch level is [1477401644].
CRS-2672: Attempting to start 'ora.drivers.acfs' on 'racnode1'
CRS-2676: Start of 'ora.drivers.acfs' on 'racnode1' succeeded
SQL Patching tool version 12.2.0.1.0 Production on Sat Mar 7 15:46:51 2020
Copyright (c) 2012, 2019, Oracle. All rights reserved.

Connecting to database...OK
Note: Datapatch will only apply or rollback SQL fixes for PDBs
that are in an open state, no patches will be applied to closed PDBs.
Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation
(Doc ID 1585822.1)
Bootstrapping registry and package to current versions...done
Determining current state...done
Adding patches to installation queue and performing prereq checks...done
Installation queue:
For the following PDBs: CDB$ROOT PDB$SEED GIMR_DSCREP_10
The following patches will be rolled back:
29708478 (DATABASE JAN 2019 RELEASE UPDATE REVISION 12.2.0.1.190716)
The following patches will be applied:
30593149 (DATABASE JAN 2020 RELEASE UPDATE 12.2.0.1.200114)

Installing patches...
Patch installation complete. Total patches installed: 6

Validating logfiles...
Patch 29708478 rollback (pdb CDB$ROOT): WITH ERRORS
logfile: /u01/app/grid/cfgtoollogs/sqlpatch/29708478/22988073/
   29708478_rollback__MGMTDB_CDBROOT_2020Mar07_15_47_52.log (errors)
Error at line 25435: Warning: Package Body created with compilation errors.
Error at line 25442: 24/12 PLS-00323: subprogram or cursor 'GET_OPTIONAL_PRIVILEGES' is
Error at line 25446: 2727/5 PL/SQL: Statement ignored
Error at line 25447: 2727/21 PLS-00306: wrong number or types of arguments in call to
Error at line 36437: Warning: Package Body created with compilation errors.
Error at line 36444: 18788/3 PL/SQL: Statement ignored
Error at line 36445: 18788/6 PLS-00201: identifier
Error at line 36448: 18792/3 PL/SQL: Statement ignored
Error at line 36449: 18792/3 PLS-00201: identifier
Patch 29708478 rollback (pdb PDB$SEED): WITH ERRORS
logfile: /u01/app/grid/cfgtoollogs/sqlpatch/29708478/22988073/
   29708478_rollback__MGMTDB_PDBSEED_2020Mar07_15_50_23.log (errors)
Error at line 36419: Warning: Package Body created with compilation errors.
Error at line 36426: 18788/3 PL/SQL: Statement ignored
Error at line 36427: 18788/6 PLS-00201: identifier
Error at line 36430: 18792/3 PL/SQL: Statement ignored
Error at line 36431: 18792/3 PLS-00201: identifier
Patch 29708478 rollback (pdb GIMR_DSCREP_10): WITH ERRORS
logfile: /u01/app/grid/cfgtoollogs/sqlpatch/29708478/22988073/
29708478_rollback__MGMTDB_GIMR_DSCREP_10_2020Mar07_15_50_23.log (errors)
Error at line 52094: Warning: Package Body created with compilation errors.
Error at line 52101: 18788/3 PL/SQL: Statement ignored
Error at line 52102: 18788/6 PLS-00201: identifier
Error at line 52105: 18792/3 PL/SQL: Statement ignored
Error at line 52106: 18792/3 PLS-00201: identifier

Please refer to MOS Note 1609718.1 and/or the invocation log
/u01/app/grid/cfgtoollogs/sqlpatch/sqlpatch_9475_2020_03_07_15_46_51/sqlpatch_invocation.log
for information on how to resolve the above errors.

SQL Patching tool complete on Sat Mar 7 15:54:51 2020
2020/03/07 15:54:51 CLSRSC-488: Patching the Grid Infrastructure 
                            Management Repository database failed.

After fixing the cause of failure Run opatchauto resume

]
OPATCHAUTO-68061: The orchestration engine failed.
OPATCHAUTO-68061: The orchestration engine failed with return code 1
OPATCHAUTO-68061: Check the log for more details.
OPatchAuto failed.

OPatchauto session completed at Sat Mar 7 15:54:52 2020
Time taken to complete the session 22 minutes, 24 seconds

opatchauto failed with error code 42
[root@racnode1 ~]#

Subscribe to get access

Read more of this content when you subscribe today.

Failover Cluster: Event ID 1257 Every 15 Minutes

For a newly created cluster,  there are many Event ID 1257 cluster events shown on Failover Cluster Manager.

Cluster network name resource failed registration of one or more associated
 DNS name(s) because the access to update the secure DNS zone was denied.

cluster Network name: 'Cluster Name'
DNS Zone: 'DNS Zone'

Ensure that cluster name object (CNO) is granted permissions to Secure 
DNS Zone.

Subscribe to get access

Read more of this content when you subscribe today.