skgpspawn failed encounter in alert.log
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 2 of 2

Thread: skgpspawn failed encounter in alert.log

  1. #1
    Join Date
    Oct 2001
    Posts
    52

    skgpspawn failed encounter in alert.log

    Hi,
    Below error message found in alert.log. Anyone have any idea with regards to this error?
    Please advise.

    Thanks & regards,
    GS
    Mon Oct 20 15:41:23 2003
    skgpspawn failed:category = 27142, depinfo = 12, op = fork, loc =
    skgpspawn3
    skgpspawn failed:category = 27142, depinfo = 12, op = fork, loc =
    skgpspawn3
    skgpspawn failed:category = 27142, depinfo = 12, op = fork, loc =
    skgpspawn3
    skgpspawn failed:category = 27142, depinfo = 12, op = fork, loc =
    skgpspawn3
    skgpspawn failed:category = 27142, depinfo = 12, op = fork, loc =
    skgpspawn3

  2. #2
    Join Date
    Nov 2000
    Location
    Israel
    Posts
    268
    This is related to dispatcher (MTS/Shared server).
    The dispatcher was unable to spawn a new shared server process to handle requests.
    When you are running shared server (MTS) and more shared servers need to be started, they are automatically started up to the number of max shared servers specified in the init.ora file.
    This problem is occurring because you are running out of resources on your machine that are required for the servers to startup.

    Solutions:
    1. Increase swap or memory.
    2. Reduce the number of shared servers (dispatchers) that can be started.
    It is better to ask and appear ignorant, than to remain silent and remain ignorant.

    Oracle OCP DBA 9i,
    C++, Java developer

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width