AHF - Autonomous Health Framework (TFA - ORACHK) (MOSC)

MOSC Banner

Check of ASM_DISKSTRING validity?

edited Sep 9, 2020 2:12PM in AHF - Autonomous Health Framework (TFA - ORACHK) (MOSC) 1 commentAnswered ✓

I've been pointed here as apparently it isn't possible to raise an SR against ORACHK. One  of the checks in ORACHK 12.1.0.2.1 is for ASM_DISKSTRING being set to null or /dev/*. The rationale appears to be that these settings can cause OCSSD not to start during an upgrade. However if the system is using ASMLIB then null is the default and recommended value for ASM_DISKSTRING. Can this check be enhanced/modified to test for the existence of asmlib disks? FWIW I've never seen a failure with asmlib and a null discovery string.  

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center