66 OKSK-00000 to OKSK-00029

OKSK-00000: %2 %3

Cause: Informational.

Action: None

OKSK-00001: %2 %3

Cause: Informational.

Action: None

OKSK-00002: %2 %3

Cause: Informational.

Action: None

OKSK-00003: %2 %3

Cause: Informational.

Action: None

OKSK-00004: Module load succeeded. Build information: %2 %3 %4

Cause: Informational.

Action: None

OKSK-00005: Module failed to load and start with status %2. Build information: %3 %4 %5

Cause: Informational.

Action: None

OKSK-00006: Module unloaded.

Cause: Informational.

Action: None

OKSK-00007: Information has been saved in the file %2 . Include the contents of this file if reporting a problem to Oracle.

Cause: Informational.

Action: None

OKSK-00008: Cluster Membership Change starting - Incarnation %2.

Cause: Informational.

Action: None

OKSK-00009: Cluster Membership Change complete.

Cause: Informational.

Action: n/a

OKSK-00010: Persistent OKS log opened at %2.

Cause: Informational.

Action: None

OKSK-00011: Failed to allocate kernel memory for %2.

Cause: Unable to allocate memory for a required function.

Action: Contact Oracle Support Services.

OKSK-00012: Failed to open %2.

Cause: Unable to open a persistent OKS log file. Likely an invalid file path was specified or there was an internal error.

Action: Ensure that the file or directory exists else. If it does, contact Oracle Support Services.

OKSK-00013: Terminating Persistent OKS log.

Cause: Persistent OKS logging terminated due to the previous message.

Action: Informational.

OKSK-00014: Unable to generate an persistent OKS log file name.

Cause: Failed to generate an persistent OKS log fime name.

Action: Internal error.

OKSK-00015: Persistent log thread creation failed.

Cause: Failed to create a kernel thread.

Action: Internal error.

OKSK-00016: Configuration error: buffer size %2 bytes is out of range.

Cause: The user selected an invalid buffer size.

Action: Select a different buffer size.

OKSK-00017: Configuration error: interval timer of %2 ms is out of range.

Cause: The user selected an invalid timer interval.

Action: Select a different timer value.

OKSK-00018: Configuration error: low water level of %2 bytes isout of range.

Cause: The user selected an invalid low water value.

Action: Select a different low water value.

OKSK-00019: Configuration error: high water level of %2 bytes is out of range.

Cause: The user selected an invalid high water value.

Action: Select a different high water value.

OKSK-00020: Configuration error: maximum number of log files (%2) is out of range.

Cause: The user selected an invalid maximum file number value.

Action: Select a different file number value.

OKSK-00021: Configuration error: The maximum file size of %2 bytes is out of range.

Cause: The user selected an invalid maximum log file size value.

Action: Select a different maximum log file size value.

OKSK-00022: File write error: File name '<varname>string</varname>'.

Cause: A write to the persistent OKS log file failed - possibly due to a full file system. Otherwise, it is an internal error. The in-memory OKS log will contain details regarding the error.

Action: Free up file systems space and restart the OKS persistent log ('acfsutil plogconfig -d <varname>dir</varname>'). If freeing up file system space does not resolve the problem, contact Oracle Support Services.

OKSK-00023: Cluster membership node list:

Cause: Informational.

Action: None

OKSK-00024: Node %2 (Interconnect address: %3.%4.%5.%6)

Cause: Informational.

Action: None

OKSK-00025: Cluster membership node count: %2, Local Node Number: %3.

Cause: Informational.

Action: None

OKSK-00026: Cluster membership rebuild manager failed to initialize.

Cause: Informational.

Action: Contact Oracle Support.

OKSK-00027: Oracle kernel distributed lock manager hash size is %2

Cause: Informational.

Action: None

OKSK-00028: In memory kernel log buffer address: %2, size: %3

Cause: Informational.

Action: None

OKSK-00029: Unable to %2 the log buffer.

Cause: Informational.

Action: None