My Oracle Support Banner

Starting of "ora.qosmserver" Fails after Applying Windows Bundle Patch (Doc ID 2384880.1)

Last updated on FEBRUARY 19, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Microsoft Windows x64 (64-bit)

Symptoms

ora.qosmserver fails to start after applying Windows Bundle Patch.
When executing rootcrs.pl -postpatch, the following error occurs.

CRS-2807: Resource 'ora.qosmserver' failed to start automatically.

Output of GI alert log

CRS-5818: Aborted command 'start' for resource 'ora.qosmserver'
CRS-2757: Command 'Start' timed out waiting for response from the resource 'ora.qosmserver'.
CRS-2807: Resource 'ora.qosmserver' failed to start automatically.

Output of crsd.trc

2018-02-20 16:30:05.810 : CRSD:7452: {1:62145:2} {1:62145:2} Created alert : (:CRSPE00221:) : Start action timed out!
2018-02-20 16:30:05.810 : CRSPE:7452: {1:62145:2} Start action failed with error code: 3
2018-02-20 16:30:05.813 : CRSRPT:3292: {1:62145:2} Published to EVM CRS_ACTION_FAILURE for ora.qosmserver

Output of crsd_scriptagent_system.trc

2018-02-20 16:25:05.753 : AGFW:8872: {1:62145:2} Agent received the message: RESOURCE_START[ora.qosmserver 1 1] ID 4098:1084
2018-02-20 16:25:05.753 : AGFW:8872: {1:62145:2} Preparing START command for: ora.qosmserver 1 1
2018-02-20 16:25:05.753 : AGFW:8872: {1:62145:2} ora.qosmserver 1 1 state changed from: UNKNOWN to: STARTING
2018-02-20 16:25:05.757 :CLSDYNAM:2816: [ora.qosmserver]{1:62145:2} [start] Executing action script: $GRID_HOME\bin\jwcctl.bat[start]
2018-02-20 16:25:06.037 :CLSDYNAM:2816: [ora.qosmserver]{1:62145:2} [start] Start JWC
2018-02-20 16:26:05.546 : AGFW:8872: {1:62145:2} Agent received the message: AGENT_HB[Engine] ID 12293:1774
2018-02-20 16:27:05.536 : AGFW:8872: {1:62145:2} Agent received the message: AGENT_HB[Engine] ID 12293:2214
2018-02-20 16:27:35.547 : AGFW:8872: {1:62145:2} Agent received the message: AGENT_HB[Engine] ID 12293:2367
2018-02-20 16:28:35.541 : AGFW:8872: {1:62145:2} Agent received the message: AGENT_HB[Engine] ID 12293:2619
2018-02-20 16:29:05.542 : AGFW:8872: {1:62145:2} Agent received the message: AGENT_HB[Engine] ID 12293:2834
2018-02-20 16:29:35.540 : AGFW:8872: {1:62145:2} Agent received the message: AGENT_HB[Engine] ID 12293:2930
2018-02-20 16:30:05.547 : AGFW:8872: {1:62145:2} Agent received the message: AGENT_HB[Engine] ID 12293:2950
2018-02-20 16:30:05.769 : AGENT:5624: {1:62145:2} {1:62145:2} Created alert : (:CRSAGF00113:) : Aborting the command: start for resource: ora.qosmserver 1 1
2018-02-20 16:30:05.769 :CLSDYNAM:5624: [ora.qosmserver]{1:62145:2} [start] Killing action script: start

Changes

Apply Windows Bundle Patch.
This issue happens after applying the following patches.

- WINBP 12.2.0.1.171017 (<Patch:26758841>)
- WINBP 12.2.0.1.171130 (<Patch:27002286>)
- WINBP 12.2.0.1.180116 (<Patch:27162931>)

Cause

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
Symptoms
Changes
Cause
Solution
References


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