ORA-09717: osnsui: maximum number of user interrupt handlers exceeded.

ORA-09717: osnsui: maximum number of user interrupt handlers exceeded.

Cause: The internal limit on the number of user interrupt handlers has been exceeded.

Action: Reduce the number of simulataneous logons or reduce the number of user interrupt handlers.

ORA-09716: kslcll: Unable to fix in-flux lamport latch.

ORA-09716: kslcll: Unable to fix in-flux lamport latch.

Cause: One Oracle process died while still holding a lamport latch.

Action: Exit (kill) all Oracle user processes. Shutdown (abort) and restart Oracle RDBMS kernel.

ORA-09715: orasrv: cannot obtain puname

ORA-09715: orasrv: cannot obtain puname

Cause: Orasrv cannot obtain the name of the PU. (Possible OS error)

Action: Check if the PUs are named (consistend).

ORA-09714: Two Task interface: cannot obtain puname

ORA-09714: Two Task interface: cannot obtain puname

Cause: The TXIPC driver cannot obtain the name of the PU. (Possible OS error)

Action: Check if the PUs are named (consistend).

ORA-09712: orasrv: log archiver already connected.

ORA-09712: orasrv: log archiver already connected.

Cause: An existing connection has already been made from log archiver to orasrv.

Action: Stop trying to connect.

ORA-09711: orasrv: archmon already connected.

ORA-09711: orasrv: archmon already connected.

Cause: An existing connection has already been made from archmon to orasrv.

Action: Stop trying to connect.

ORA-09710: soarcv: buffer overflow.

ORA-09710: soarcv: buffer overflow.

Cause: The internal buffer is not big enough to hold the message read.

Action: Internal error. Contact customer support representative.