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.

ORA-09709: soacon: failed to accept a connection.

ORA-09709: soacon: failed to accept a connection.

Cause: The accept system call failed on the socket.

Action: Check additional information for OS error. Try connecting again.

ORA-09708: soacon: failed to bind socket to port.

ORA-09708: soacon: failed to bind socket to port.

Cause: The bind system call failed on the socket.

Action: Check additional information for OS error. Try connecting again.

ORA-09706: slsget: get_process_stats error.

ORA-09706: slsget: get_process_stats error.

Cause: get_process_stats system call returned an error. Possible OS error.

Action: Check additional information returned. Look for information in OS reference. Contact customer support.

ORA-09705: spcre: cannot initialize latch semaphore

ORA-09705: spcre: cannot initialize latch semaphore

Cause: The semaphore used for accessing latches could not be initialized

Action: Send trace file to your customer support representative, along with information on reproducing the error.

ORA-09704: sstascre: ftok error in creating test and set pages.

ORA-09704: sstascre: ftok error in creating test and set pages.

Cause: the ftok() library call failed in sstastcre().

Action: Verify that tasdef.dbf file exists. If it does then this is a possible system failure. Perhaps System V compatibility is not enabled.

ORA-09703: sem_release: cannot release latch semaphore

ORA-09703: sem_release: cannot release latch semaphore

Cause: The semaphore used for accessing latches could not be released

Action: Send trace file to your customer support representative, along with information on reproducing the error.

ORA-09702: sem_acquire: cannot acquire latch semaphore

ORA-09702: sem_acquire: cannot acquire latch semaphore

Cause: The semaphore used for accessing latches could not be seized

Action: Send trace file to your customer support representative, along with information on reproducing the error.

ORA-09701: scnfy: maximum number of processes exceeded

ORA-09701: scnfy: maximum number of processes exceeded

Cause: PROCESSES INIT.ORA parameter exceeded.

Action: Decrease the PROCESSES parameter and restart.

ORA-09700: sclin: maximum number of latches exceeded

ORA-09700: sclin: maximum number of latches exceeded

Cause: ORACLE wants to use more latches then available.

Action: increase INIT.ORA parameter latch_pages or decrease the amount of shared memory you are using.

ORA-09370: Windows 3.1 Two-Task driver ORACLE task timed out

ORA-09370: Windows 3.1 Two-Task driver ORACLE task timed out

Cause: See OSD error accompanying this message

Action: none

ORA-09369: Windows 3.1 Two-Task driver bad instance handle

ORA-09369: Windows 3.1 Two-Task driver bad instance handle

Cause: See OSD error accompanying this message

Action: none

ORA-09368: Windows 3.1 Two-Task driver unable to spawn ORACLE

ORA-09368: Windows 3.1 Two-Task driver unable to spawn ORACLE

Cause: See OSD error accompanying this message

Action: none

ORA-09367: Windows 3.1 Two-Task driver unable to deallocate shared memory

ORA-09367: Windows 3.1 Two-Task driver unable to deallocate shared memory

Cause: See OSD error accompanying this message

Action: none

ORA-09366: Windows 3.1 Two-Task driver unable to allocate shared memory

ORA-09366: Windows 3.1 Two-Task driver unable to allocate shared memory

Cause: See OSD error accompanying this message

Action: none

ORA-09365: Windows 3.1 Two-Task driver unable to destroy hidden window

ORA-09365: Windows 3.1 Two-Task driver unable to destroy hidden window

Cause: See OSD error accompanying this message

Action: none

ORA-09364: Windows 3.1 Two-Task driver unable to create hidden window

ORA-09364: Windows 3.1 Two-Task driver unable to create hidden window

Cause: See OSD error accompanying this message

Action: none

ORA-09363: Windows 3.1 Two-Task driver invalid context area

ORA-09363: Windows 3.1 Two-Task driver invalid context area

Cause: See OSD error accompanying this message

Action: none

ORA-09362: Windows 3.1 Two-Task driver unable to deallocate context area

ORA-09362: Windows 3.1 Two-Task driver unable to deallocate context area

Cause: See OSD error accompanying this message

Action: none

ORA-09361: Windows 3.1 Two-Task driver unable to lock context area

ORA-09361: Windows 3.1 Two-Task driver unable to lock context area

Cause: See OSD error accompanying this message

Action: none

ORA-09360: Windows 3.1 Two-Task driver unable to allocate context area

ORA-09360: Windows 3.1 Two-Task driver unable to allocate context area

Cause: See OSD error accompanying this message

Action: none

ORA-09354: Windows 32-bit Two-Task driver: ORACLE task unexpectedly died

ORA-09354: Windows 32-bit Two-Task driver: ORACLE task unexpectedly died

Cause: See OSD error accompanying this message

Action: none

ORA-09353: Windows 32-bit Two-Task driver unable to open event semaphore

ORA-09353: Windows 32-bit Two-Task driver unable to open event semaphore

Cause: See OSD error accompanying this message

Action: none

ORA-09352: Windows 32-bit Two-Task driver unable to spawn new ORACLE task

ORA-09352: Windows 32-bit Two-Task driver unable to spawn new ORACLE task

Cause: See OSD error accompanying this message

Action: none

ORA-09351: Windows 32-bit Two-Task driver unable to allocate shared memory

ORA-09351: Windows 32-bit Two-Task driver unable to allocate shared memory

Cause: See OSD error accompanying this message

Action: none

ORA-09350: Windows 32-bit Two-Task driver unable to allocate context area

ORA-09350: Windows 32-bit Two-Task driver unable to allocate context area

Cause: See OSD error accompanying this message

Action: none

ORA-09344: spsig: error signalling thread

ORA-09344: spsig: error signalling thread

Cause: This function may not be implemented.

Action: none

ORA-09342: Detached process terminated by Oracle during shutdown abort

ORA-09342: Detached process terminated by Oracle during shutdown abort

Cause: The user performed a shutdown abort.

Action: none

ORA-09341: scumnt: unable to mount database

ORA-09341: scumnt: unable to mount database

Cause: Another instance is currently mounting the database

Action: none

ORA-09340: Specified ORACLE_SID is either invalid or too long

ORA-09340: Specified ORACLE_SID is either invalid or too long

Cause: ORACLE_SID must be at the most 4 alphanumeric characters.

Action: none

ORA-09330: Session terminated internally by Oracle or by an Oracle DBA

ORA-09330: Session terminated internally by Oracle or by an Oracle DBA

Cause: Oracle to terminate that session after about a minute. This message also appears in the trace file if a shutdown abort is performed.

Action: none

ORA-09322: slpdtb: unable to convert packed decimal to binary

ORA-09322: slpdtb: unable to convert packed decimal to binary

Cause: internal error

Action: See OSD error accompanying this message

ORA-09321: slzdtb: unable to convert zoned decimal to binary

ORA-09321: slzdtb: unable to convert zoned decimal to binary

Cause: internal error

Action: See OSD error accompanying this message

ORA-09320: szrfc: unable to obtain the list of valid OS roles

ORA-09320: szrfc: unable to obtain the list of valid OS roles

Cause: OS roles may not be supported on this platform

Action: See OSD error accompanying this message

ORA-09319: slgtd: unable to obtain the current date and time

ORA-09319: slgtd: unable to obtain the current date and time

Cause: The system time might be set incorrectly

Action: See OSD error accompanying this message

ORA-09318: slkhst: unable to host out to operating system

ORA-09318: slkhst: unable to host out to operating system

Cause: There might not be enough memory for the command or hosting out may not be supported on this platform

Action: See OSD error accompanying this message

ORA-09317: szprv: insufficient privileges

ORA-09317: szprv: insufficient privileges

Cause: The password specified is invalid

Action: See OSD error accompanying this message

ORA-09316: szrpc: unable to verify password for role

ORA-09316: szrpc: unable to verify password for role

Cause: OS roles may not be supported for this platform

Action: See OSD error accompanying this message

ORA-09315: sql2tt: two-task error translating ORACLE_EXECUTABLE

ORA-09315: sql2tt: two-task error translating ORACLE_EXECUTABLE

Cause: Internal error

Action: See OSD error accompanying this message

ORA-09314: sltln: error translating logical name

ORA-09314: sltln: error translating logical name

Cause: Internal buffer may have overflowed

Action: See OSD error accompanying this message

ORA-09313: slsprom: error prompting user

ORA-09313: slsprom: error prompting user

Cause: May be out of resources

Action: See OSD error accompanying this message

ORA-09312: slspool: error spooling file to printer

ORA-09312: slspool: error spooling file to printer

Cause: Could be out of resources

Action: See OSD error accompanying this message

ORA-09311: slsleep: error temporarily suspending process

ORA-09311: slsleep: error temporarily suspending process

Cause: May be out of resources

Action: See OSD error accompanying this message

ORA-09310: sclgt: error freeing latch

ORA-09310: sclgt: error freeing latch

Cause: Internal error

Action: See OSD error accompanying this message

ORA-09301: osncon: local kernel only supported in standard mode

ORA-09301: osncon: local kernel only supported in standard mode

Cause: An attempt was made to connect to S: while in enhanced mode

Action: Restart Windows in standard mode

ORA-09300: osncon: unable to connect, DPMI not available

ORA-09300: osncon: unable to connect, DPMI not available

Cause: Unable to detect the presence of DPMI

Action: Restart Windows and retry

ORA-09293: sksasmo: unable to send message to console

ORA-09293: sksasmo: unable to send message to console

Cause: An error was returned while attempting to send a message to the console operator

Action: See OSD error accompanying this message

ORA-09292: sksabln: unable to build archive file name

ORA-09292: sksabln: unable to build archive file name

Cause: Bad directory or format specified

Action: Specify a valid directory in log_archive_format and a valid format string in log_archive_format in init.ora

ORA-09291: sksachk: invalid device specified for archive destination

ORA-09291: sksachk: invalid device specified for archive destination

Cause: Unable to access directory

Action: Specify a valid device in ARCHIVE control string

ORA-09290: sksaalo: error allocating memory for archival

ORA-09290: sksaalo: error allocating memory for archival

Cause: Could be out of memory

Action: See OSD error accompanying this message

ORA-09285: sllfop: unrecognizable processing option, incorrect format

ORA-09285: sllfop: unrecognizable processing option, incorrect format

Cause: Processing option passed is of incorrect format

Action: Consult your IUG for permissible formats

ORA-09284: sllfop: cannot allocate read buffer

ORA-09284: sllfop: cannot allocate read buffer

Cause: malloc() system call returned an error. The system might have run out of heap space

Action: Check additional information for the OS error.

ORA-09283: sllfsk: error skipping records

ORA-09283: sllfsk: error skipping records

Cause: File could be corrupted

Action: See OSD error accompanying this message

ORA-09282: sllfrb: error reading records

ORA-09282: sllfrb: error reading records

Cause: File could be corrupted

Action: See OSD error accompanying this message