My Oracle Support Banner

How to apply a patch if / been executed partially to a GI home (Doc ID 1980634.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version and later
Generic Linux
Generic UNIX


During an installation or upgrade of a Grid Infrastructure (GI) home, while executing the or from the first node, an error could be reported due to a bug and a patch is required.

If the issue is known before executing the /, can simply apply the patch with 'opatch apply' command to lay down the patch. However, if or has been partially run and failed, the following steps is required to overcome the issue, especially if the failure already pass the phase that init entries update is done.

Following is an example of upgrading from to GI home, three nodes cluster, namely lc1n1, lc1ntwo and lc1nthree.

This will encounter <Bug 19453778> due to hostname length difference, and need to apply GI PSU (Jan 2015), patch number 20132450


This is the error reported during on node1 (lc1n1)

[root@lc1n1 ~]# /u02/app/
Performing root user operation.

. . . . .

Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Using configuration parameter file: /u02/app/
2015/02/12 15:51:22 CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector.

2015/02/12 15:52:32 CLSRSC-4003: Successfully patched Oracle Trace File Analyzer (TFA) Collector.

2015/02/12 15:52:43 CLSRSC-464: Starting retrieval of the cluster configuration data

2015/02/12 15:53:08 CLSRSC-465: Retrieval of the cluster configuration data has successfully completed.

2015/02/12 15:53:09 CLSRSC-363: User ignored prerequisites during installation

2015/02/12 15:53:35 CLSRSC-515: Starting OCR manual backup.

2015/02/12 15:53:40 CLSRSC-516: OCR manual backup successful.

2015/02/12 15:53:50 CLSRSC-468: Setting Oracle Clusterware and ASM to rolling migration mode

2015/02/12 15:53:50 CLSRSC-482: Running command: '/u02/app/ -silent -upgradeNodeASM -nonRolling false -oldCRSHome /u01/app/ -oldCRSVersion -nodeNumber 1 -firstNode true -startRolling true'

ASM configuration upgraded in local node successfully.

2015/02/12 15:54:03 CLSRSC-469: Successfully set Oracle Clusterware and ASM to rolling migration mode

2015/02/12 15:54:03 CLSRSC-466: Starting shutdown of the current Oracle Grid Infrastructure stack

2015/02/12 15:54:54 CLSRSC-467: Shutdown of the current Oracle Grid Infrastructure stack has successfully completed.

OLR initialization - successful
2015/02/12 16:00:30 CLSRSC-329: Replacing Clusterware entries in file '/etc/inittab'

CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
2015/02/12 16:05:59 CLSRSC-115: Start of resource 'ora.ctssd' failed

2015/02/12 16:05:59 CLSRSC-117: Failed to start Oracle Clusterware stack

2015/02/12 16:05:59 CLSRSC-245: Failed to start Cluster Time Synchronization Service (CTSS)

Died at /u02/app/ line 804.
The command '/u02/app/ -I/u02/app/ -I/u02/app/ /u02/app/  -upgrade' execution failed



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.