Troubleshooting ORA-27300 ORA-27…

Troubleshooting ORA-27300 ORA-27301 ORA-27302 errors [ID579365.1] 转到底部 

--------------------------------------------------------------------------------

修改时间:2013-4-25类型:TROUBLESHOOTING状态:PUBLISHED优先级:3 注释(0)    
 

In this Document

 Purpose
 Troubleshooting Steps
 References

--------------------------------------------------------------------------------

Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.1 to 11.2.0.3[Release 9.2 to 11.2]
Information in this document applies to any platform.

 

Purpose
This note helps identify the possible causes of the ORA-2730xerrors that have already been reported and provides solution whereavailable.  The errors are usually caused by OSsystem call error or OS configuration issue and are in the formof:

ORA-27300: OS system dependent operation:%s failed with status:%s
ORA-27301: OS failure message: %s
ORA-27302: failure occurred at: %s
Documentation is available at the OS level for some of thedependent operation or OS calls such as fork() or semget(). The'status' reported in the ORA-27300 error usually corresponds to aUnix error code defined in the "errno.h" header file on the OS,returned by the OS call.

For example,

ORA-27300: OS system dependent operation:fork failed withstatus: 11

A "man fork" shows:

The fork() function shall fail if:

EAGAIN (status 11) : The system lacked the necessary resourcesto create another process, or the system-imposed limit on the totalnumber of processes under execution system-wide or by a single user{CHILD_MAX} would be exceeded. EAGAIN corresponds to status 11.

The fork() function may fail if:

ENOMEM (status 12) : Insufficient storage space isavailable.
Troubleshooting Steps
The note is broken down by the status code.

STATUS  0
ORA-27300: OS system dependent operation:invalid_process_id failedwith status: 0
ORA-27301: OS failure message: Error 0
ORA-27302: failure occurred at: skgpalive1

     See Note 356640.1 ORA-27300, ORA-27301, ORA-27302 Failure OccurredAt Skgpalive1 During 'Shutdown'  - UnPublished Bug4923667.

    In 10.2.0.5 and up, see Note 1252265.1 - ORA-27300 ORA-27301ORA-27302: failure occurred at: skgpalive1 - bug 10010310.

ORA-27300: OS system dependent operation:invalid_process failedwith status: 0
ORA-27301: OS failure message: Error 0
ORA-27302: failure occurred at: skgpstime3
ORA-27144: attempt to kill process failed

    See Note 458442.1 > />10.2.0.3 PMONCRASHES ON STARTUP ON AIX 5L 5.3 ML05 -- WORKS onML06> />

STATUS 1 - EPERM Not owner
An attempt was made to modify a file that doesn't belong to theuser, or the user was forbidden to modify that file by its owner orsuper-user.
ORA-27300: OS system dependent operation:invalid_egid failed withstatus: 1
ORA-27301: OS failure message: Not owner
ORA-27302: failure occurred at: skgpwinit6
ORA-27303: additional information: startup egid = 202 (?), currentegid = 101 (dba)

     See Note 453959.1 Cannot Connect As "/ as sysdba" ORA-27140ORA-27300 ORA-27301

ORA-27512: IPC error posting a process
ORA-27300: OS system dependent operation:kill failed failed withstatus: 1
ORA-27301: OS failure message: Not owner
ORA-27302: failure occurred at:skgxppost1     

       See Note 3411021.8 - Bug 3411021  - Oracle processmay die due to ORA-27300/ORA-27301/ORA-27302 at skgxppost1

STATUS 2 -  ENOENT No such file or directory
This error occurs when trying to access a file or subdirectory thatdoes not exist.
ORA-12012: error on auto execute of job 71010
ORA-27370: job slave failed to launch a job of typeEXECUTABLE
ORA-27300: OS system dependent operation:accessing execution agentfailed with status: 2
ORA-27301: OS failure message: No such file or directory
ORA-27302: failure occurred at: sjsec 3

       See Note 277399.1 DBMS_SCHEDULER Fails To Execute Jobs WithProgram_type
EXECUTABLE On HP-UX

STATUS 3 - ESRCH No such process
The process number passed to the signal handling procedure belongsto
a process that doesn't exist, or it is already dead.
 In a RAC environment, errors of the form belowmay be seen causing process failures:
ORA-00603: ORACLE server session terminated by fatal error
ORA-27504: IPC error creating OSD context
ORA-27300: OS system dependent operation:sskgxp_select failed withstatus: 3
ORA-27301: OS failure message: No such process
ORA-27302: failure occurred at: skgxpvfymmtu
ORA-27303: additional information: MTU could not be verified. Didnot receive valid message.

         See Note 746888.1 ORA-27302: Failure Occurred at: skgxpvfymmtuSignalled in the Alert.log

STATUS 6 - ENXIO No such device or address
I/O error on a component of a device that is missing.
Windows specific:

ORA-27300: OS system dependent operation:SuspendThread failedwith status: 6
ORA-27301: OS failure message: The handle is invalid.
ORA-27302: failure occurred at: sssxcpttcs6

       See BUG: 6991131 -  Status: 32,Not a Bug
This is an issue during shutdown. We send a shutdown message toMMON and we wait for 30 sec to check if it has gone away. If itstill exists then we collect the diagnostic information and try tosuspend the target thread ("MMON" in this case). However we findthat target thread handle is no longer valid since the thread hasexited or about to exit. This causes the error to be reported inthe alert.log. This error may be ignored during the shutdownprocess as long as it doesn't hang since the target thread wasgoing away at the time we tried to collect the diaginformation.

======

ORA-27300: OS system dependent operation:GetThreadTimes failedwith status: 6
ORA-27301: OS failure message: The handle is invalid.
ORA-27302: failure occurred at: skgpalive

See unpublished  BUG: 6455284 - Status 80 :DNFS NT: ORA-27300,ORA-27301,ORA-27302: FAILURE OCCURRED AT:SKGPALIVE

Fixed in 11.1.0.7 and 11.2.

 

STATUS 8 - ENOEXEC Exec format error
Attempt was made to execute a file that does not have an executableformat.
ORA-27300: OS system dependent operation:CreateThread failed withstatus: 8
ORA-27301: OS failure message: Not enough storage is available toprocess this command.
ORA-27302: failure occurred at: ssthrddcr.

    See Note466370.1 ORA-7445 [ACCESS_VIOLATION] [unable_to_trans_pc][UNABLE_TO_WRITE] ORA-27301 OS failure message Not enough storageORA-27300 ORA-27302> />

   For Windows, see Note225349.1 Implementing Address Windowing Extensions (AWE) or VLM onWindows Platforms

STATUS 11 - EAGAIN No more processes
Executing a fork and the system's process table is full, or theuser is not allowed to create more process.

ORA-27300: OS system dependent operation:fork failed withstatus: 11
ORA-27301: OS failure message: Resource temporarilyunavailable
ORA-27302: failure occurred at: skgpspawn3

    See Note 392006.1 Ora-27300 OS system dependent operation forkfailed with status 11

Maximum number of PROCESSES allowed per user may be too low (forexample: maxuproc on AIX, maxuprc on HP andSolaris.  On Solaris 10, checkproject.max-lwps)

    @See Bug 7620133 - project.max-lwps was changed from the defaultwhich is 2 billion.

ORA-27300: OS system dependent operation:socket failed withstatus: 11
ORA-27301: OS failure message: Resource temporarilyunavailable
ORA-27302: failure occurred at: sskgxpcre1

    See Note364353.1 ORA-00603 ORA-27504 ORA-27300 ORA-27504 in the AlertLog
(HP port specific)

    1. SetMAX_ASYNC_PORTS to a value high enough
    2.Deactivate async io at os level.

ORA-27300: OS system dependent operation:ioctl failed withstatus: 11
ORA-27301: OS failure message: Resource temporarilyunavailable
ORA-27302: failure occurred at: skgxpvaddr1

    SeeNote.6629265.8 Bug 6629265 - Intermittent ORA-27504 / ORA-27300ioctl error 11

When system resources are overloaded, an intermittent failure tocreate a socket can cause new processes to fail to start with aboveerrors.

STATUS 12 - ENOMEM Not enough core / memory
During an exec or a break, the program asked for more memory thanthe one available by the system. This error also occurs when thereare too many segmentation registers which are required for thearrangement of text data or stack segments.

ORA-27300: OS system dependent operation:fork failed withstatus: 12
ORA-27301: OS failure message: Not enough space
ORA-27302: failure occurred at: skgpspawn3

    See Note 465002.1  Database Crash With ErrorORA-00490    

    Note580552.1 Ora-04030 Ora-07445 Ora-27300 Ora-27301 Ora-27302 CrashedDatabase

    Note560309.1> /> Database Cannot StartDue to Lack of Memory

 

 ** All related to swap space beingdepleted.  Check the OS system logs for moreinformation. On some Operating Systems increasing nproc ormaxuprc  is required **>/>

STATUS 13 - EACCES Permission denied
An attempt was made to access a forbidden file by the protectionsystem.
ORA-27300: OS system dependent operation:accessing execution agentfailed with status: 13
ORA-27301: OS failure message: Permission denied
ORA-27302: failure occurred at: sjsec 3

     See Note 557153.1  ORA-27370, ORA-27301(Permissiondenied) when running job of type EXECUTABLE .
Restart the Oracle database using an appropriate user account(often the "oracle" user).

STATUS 17 - EEXIST File exists
An existing file was entered as a parameter of a command that willmodify it.

ORA-27300: OS system dependent operation:semget failed withstatus: 17
ORA-27301: OS failure message: File exists
ORA-27302: failure occurred at: sskgpcreate

    See Note 123905.1 ORA-27154 on Database Startup After SystemCrash
Remove stray shared memory segments and semaphores.
 

STATUS 22 -  EINVAL Invalid argument
Invalid argument passed.
For example: Passing an unknown signal in the signal function.

ORA-27300: OS system dependent operation:semctl failed withstatus: 22
ORA-27301: OS failure message: Invalid argument
ORA-27302: failure occurred at: sskgpwrm1
ORA-27157: OS post/wait facility removed
ORA-27300: OS system dependent operation:semop failed with status:36
ORA-27301: OS failure message: Identifier removed
ORA-27302: failure occurred at: sskgpwwait1

     See Note 438205.1 > />ORA-27300ORA-27301 ORA-27302 ORA-27157 Database Crash Semaphores/sharedmemory might have been removed>/>

ORA-27300: OS system dependent operation:mpctl_ldomspus failed withstatus: 22
ORA-27301: OS failure message: Invalid argument
ORA-27302: failure occurred at: skgsnnprocs 

    See BUG: 7232946 - ORA-600[KSKRECONFIGNUMA2] CAUSES INSTANCECRASH
    10.2.0.4.0

    It lookslike this is all resulting of NUMA issues because of NUMA featureis enabled by default starting with10.2.0.4.   To disable NUMA youneed to see the following db parameters:

    _db_block_numa=1
    _enable_NUMA_optimization=FALSE

 

ORA-27300: OS system dependent operation:pw_postv failed withstatus: 22
ORA-27301: OS failure message: Invalid argument
ORA-27302: failure occurred at: sskgpwvp3
ORA-27303: additional information: ukid, errno, post_count =0x7a9d93eb191f0b4e, 22, 3

    See Note6441119.8 - unpublished Bug 6441119 - Instance crash due toORA-27300 / ORA-27152
    An ORA-27300error from sskgpwpost or sskgpwvectorpost can lead to an instancecrash.

ORA-00600: internal error code, arguments: [ksbmoveme4], [], [],[], [], [], [], []
ORA-27300: OS system dependent operation:run on node failed withstatus: 22
ORA-27301: OS failure message: Invalid argument
ORA-27302: failure occurred at: skgpmoveme:1

    See Note848387.1 - With NUMA Enabled, Database Fails To Open With ORA-600[ksbmoveme4], ORA-27300, ORA-27301, ORA-27302 Errors Reported

STATUS 28 - ENOSPC No space left on device
When writing to a file, the device runs out of space.
ORA-27154: post/wait create failed
ORA-27300: OS system dependent operation:semget failed with status:28
ORA-27301: OS failure message: No space left on device
ORA-27302: failure occured at: sskgpcreates

       See Note 314179.1 Instance Startup Fails With ErrorORA-27154,ORA-27300,ORA-27301,ORA-27302

Oracle 10.2 Installation Guide (for Solaris 8 and 9):
semsys:seminfo_semmns 1024
semsys:seminfo_semmsl 256

STATUS 59
ORA-00603: ORACLE server session terminated by fatal error
ORA-27504: IPC error creating OSD context
ORA-27300: OS system dependent operation:sendmsg failed withstatus: 59
ORA-27301: OS failure message: Message too long
ORA-27302: failure occurred at: sskgxpsnd1

    See RAC:Note 300956.1 Ora-27302: sskgxpsnd1 - Starting Instance

                   Note 295832.1 - Unable To Create Database Ora-00603, ORA-27300

STATUS 63
ORA-00603: ORACLE server session terminated by fatal error
ORA-27504: IPC error creating OSD context
ORA-27300: OS system dependent operation:ioctl failed with status:63
ORA-27301: OS failure message: Out of stream resources
ORA-27302: failure occurred at: skgxpvaddr1

Specifically error code 63 is ENOSR, "out of streams resources",as reported in the ora-27301 message.

STATUS 227
ORA-27300: OS system dependent operation:bind failed with status:227
ORA-27301: OS failure message: Can't assign requested address
ORA-27302: failure occurred at: sskgxpcre3

See BUG: 9059053 - Status 92 - Not a bug.

Solution:

Increase the udp port range, recommended setting is:
udp_smallest_anon_port=9000
udp_largest_anon_port=65535

STATUS 997
ORA-27300: OS system dependent operation:spcdr:9261:4200 failedwith status: 997
ORA-27301: OS failure message: Overlapped I/O operation is inprogress.
ORA-27302: failure occurred at: skgpspawn

    See Note 371074.1 ORA-27300 ORA-27301 ORA-27302 in alert log.Cannot connect to database.

Windows specific OS resource issue:
The maximum amount of addressable memory by a process ('oracle.exe'for example) running in a
32-Bit Windows environment has been reached.

STATUS 10054

ORA-27508 : IPC error sending a message
ORA-27300 : OS system dependent operation:IPCSOCK_Send failed withstatus: 10054
ORA-27301 : OS failure message: An existing connection was forciblyclosed by the remote host.
ORA-27302 : failure occurred at: send_3

     See Note 297498.1 Resolving Instance Evictions on WindowsPlatforms

Also on Windows:
The following observation was made:
These errors were received regardelss of the DOS command or BATCHfile executed:
ORA-27370: job slave failed to launch a job of typeEXECUTABLE
ORA-27300: OS system dependent operation:accessing execution agentfailed with status: 2
ORA-27301: OS failure message: Le fichier spécifié estintrouvable.
ORA-27302: failure occurred at: sjsec 6a
ORA-27303: additional information: Le fichier spécifié estintrouvable.

It was discovered that the OracleJobScheduler Service wasstopped.
Therefore, please check the OracleJobScheduler service if youencounter this problem.

For IBM AIX on POWER Systems (64-bit)
please see the following note:
Ora-27300: Os System Dependent Operation:Fork Failed With Status:12 <>

If you see either of these function codes Skgpspawnskgpspawn5
please refer to <1125188.1> ,<812115.1> &<435787.1> for details.

 

 

 

 

 

 

 

Ora-27300 OS system dependent operation:fork failed with status:11 [ID 392006.1]
 转到底部 

--------------------------------------------------------------------------------

修改时间:2013-3-5类型:PROBLEM状态:PUBLISHED优先级:3 注释(0)      
 

In this Document

 Symptoms
 Cause
 Solution
 References

--------------------------------------------------------------------------------

Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.8 andlater
Generic UNIX
Generic Linux
***Checked for relevance on 17-AUG-2012***

Symptoms
The following message reported in alert log:

Mon Sep 18 18:10:34 2006
Errors in file/u01/oracle/admin/orcl/bdump/orcl1_psp0_954436.trc:
ORA-27300: OS system dependent operation:fork failed with status:11
ORA-27301: OS failure message: Resource temporarilyunavailable
ORA-27302: failure occurred at: skgpspawn3
Mon Sep 18 18:10:35 2006
Process P073 died, see its trace file
 

Cause
The error messages indicating that oracle has problem in forkingmore process, the maximum number of PROCESSES allowed per usercould be too low.

This is configured by the following kernel settings:

  AIX: maxuproc

  HP and Solaris: maxuprc

  Solaris 10: project.max-lwps

  Linux: nproc (/etc/security/limits.conf)

Solution
The setting can be changed using platform specific commands. Forexample, on AIX:

1. login as root.

2. use smitty utility
    Select'System Environments'
    Select'Change / Show Characteristics of Operating System'
    Maximumnumber of PROCESSES allowed peruser'   --->change to an appropriate value

    OR

    usecommand line:
    chdev -lsys0 -a maxuproc <n>, where n is anappropraite value
 

 

From the AIX installation guide, the recommended value forparameter 'maxuproc' is 16384.

11gR1: http://download.oracle.com/docs/cd/B28359_01/install.111/b28258/preaix.htm#CEGJICGC
11gR2: http://download.oracle.com/docs/cd/E11882_01/install.112/e17162/pre_install.htm#CIHGFEBD

 

The following note suggests the recommended value for differentplatforms:

Oracle Database (RDBMS) on Unix AIX,HP-UX,Linux,Mac OSX,Solaris,Tru64 Unix Operating Systems Installation andConfiguration Requirements Quick Reference (8.0.5 to 11.2) (Doc ID169706.1)

--------------------------------------------------------------------------------

References

NOTE:169706.1 - Oracle Database (RDBMS) on UnixAIX,HP-UX,Linux,Mac OS X,Solaris,Tru64 Unix Operating SystemsInstallation and Configuration Requirements Quick Reference (8.0.5to 11.2)