DB Starts with SQLPlus not SRVCTL

Reason why DB was able to be started using SQL*Plus and not srvctl because DB was configured incorrectly with srvctl.

$ srvctl start database -d DB01
PRCR-1079 : Failed to start resource ora.db01.db
CRS-5017: The resource action "ora.db01.db start" encountered the following error:
ORA-01078: failure in processing system parameters. 
For details refer to "(:CLSN00107:)" in "/u01/app/oracle/product/11.2.0/grid_2/log/host01/agent/ohasd/oraagent_oracle//oraagent_log".

CRS-2674: Start of 'ora.db01.db' on 'host01' failed

--- Spfile pointing to  (more...)

Cloning Goldengate Integrated Capture and DB

Using DBMS_STREAMS_ADM To Cleanup GoldenGate

Let’s say you want to clone DB and Goldengate implementation from PROD to DEV, then you need to drop the capture that was registered with PROD database.

This is what happens when dependencies are introduced / created.

select capture_name from dba_capture;

No Guarantees with opatch -report or CheckConflict

I have performed the following checks.

# $GRID_HOME/OPatch/opatch auto /media/swrepo/JUL2017PSU/26030799 -report -ocmrf /tmp/ocm.rsp
$ $GRID_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /media/swrepo/JUL2017PSU/26030799

Actual patching failed.

# $GRID_HOME/OPatch/opatch auto /media/swrepo/JUL2017PSU/26030799 -ocmrf /tmp/ocm.rsp
Executing /u01/app/oracle/product/11.2.0/grid/perl/bin/perl 
-patchdir /media/swrepo/JUL2017PSU -patchn 26030799 
-ocmrf /tmp/ocm.rsp -paramfile /u01/app/oracle/product/11.2.0/grid/crs/install/crsconfig_params

This is the main log file: /u01/app/oracle/product/11.2.0/grid/cfgtoollogs/opatchauto2017-10-09_10-35-34.log

This file will show your detected configuration and all the steps that opatchauto attempted to do  (more...)

Upgrade 12.2 Journey – Fixing MEMORY_TARGET

As it turns out, root cause for MEMORY_TARGET is due to configuration.

Setting SQL> alter system set memory_target=0 scope=spfile; was the initial work around, the better solution is to fix root cause.

From alert_+ASM.log

WARNING: You are trying to use the MEMORY_TARGET feature. 
This feature requires the /dev/shm file system to be mounted for at least 1073741824 bytes. 
/dev/shm is either not mounted or is mounted with available space less than this size. 

Upgrade 12.2 Journey – Troubleshooting FAILED GRID Upgrade from to

First, I am very thankful to all the bloggers out there.
It would have been nearly impossible to find resolution on one’s own.

ASM not starting with ORA-00845 – how to fix ASM parameter file

One issue after GI upgrade


[oracle@db-asm-1 ~]$ . oraenv <<< +ASM 
ORACLE_SID = [+ASM] ? The Oracle base remains unchanged with value /u01/app/oracle 

[oracle@db-asm-1 ~]$ sqlplus / as sysasm 
SQL*Plus: Release Production on Mon Oct 9  (more...)

Upgrade 12.2 Journey – Failed GRID Upgrade from to

Oracle Restart Upgrade Failed simply because CRS diskgroup is OFFLINE.

               OFFLINE OFFLINE      db-asm-1                 STABLE

Resolution coming up.

Upgrade Log

[oracle@db-asm-1 ~]$ crsctl query has releaseversion
Oracle High Availability Services release version on the local node is []

[oracle@db-asm-1 ~]$ crsctl query has softwareversion
Oracle High Availability Services version on the local node is []
[oracle@db-asm-1 ~]$

00:58:42 SYS @ +ASM:>show parameter pfile

NAME                                 TYPE         (more...)

Upgrade 12.2 Journey – ORAchk Failed To Detect compatible.asm= Issue

Ran orachk and it did not detect compatibility issues.

./orachk -u -o pre

WARNING OS Check Package cvuqdisk-1.0.9-1-x86_64 is recommended but NOT installed All Database Servers
WARNING OS Check Package unixODBC-devel-2.2.14-11.el6-i686 is recommended but NOT installed All Database Servers
WARNING OS Check Package unixODBC-2.2.14-11.el6-i686 is recommended but NOT installed All Database Servers
WARNING OS Check ORACLE_HOME environment variable is set for database software owner All Database Servers

Upgrade 12.2 Journey – Preparation for 12.2 Upgrade

This is exactly what I did last time and upgrade will fail due to compatible.asm=

Goal now is to now to detect and prevent the failure.

Let’s see if ORAchk – Health Checks for the Oracle Stack (Doc ID 1268927.2) will detect this.

[oracle@db-asm-1 ~]$ asmcmd lsattr -G CRS -l
Name                     Value
access_control.enabled   FALSE
access_control.umask     066
au_size                  4194304
cell.smart_scan_capable  FALSE
compatible.asm  (more...)

Upgrade 12.2 Journey – Apply July 2017 PSU

Patches to apply before upgrading Oracle GI and DB to (Doc ID 2180188.1)

GI PSU 22646198 (Apr 2016) Grid Infrastructure Patch Set Update (GI PSU)
Recommended to install latest* GI PSU

Patch Set Update and Critical Patch Update July 2017 Availability Document (Doc ID 2261562.1)

    OPatch utility version or later

    Patch 26030799 - Oracle  (more...)

Upgrade 12.2 Journey – Why Upgrade Failed

I already know upgrade will fail and will reproduce to show how to resolve the issue.

Curious how did it happened.

Without the benefit of knowing what will happened, is there any way this could have been detected.

RTFM – but did not find anything in the matter.

From Vagant:

TASK [oraasm-createdg : ASMCA | List ASM diskgroups]

From alert_+ASM.log: