DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3
  1. #1
    Join Date
    Mar 2001
    Can anyone explain what this means and how do I fix it??


    ------- PSIS alert log -------
    /oracle/PSIS/dmp/alert_PSIS.03Oct2001_0530:ORA-07265: sppst: semop error, unable to increment semaph
    /oracle/PSIS/dmp/alert_PSIS.03Oct2001_0530:ORA-07265: sppst: semop error, unable to increment semaph
    /oracle/PSIS/dmp/alert_PSIS.03Oct2001_0530:ORA-01092: ORACLE instance terminated. Disconnection forc
    /oracle/PSIS/dmp/alert_PSIS.03Oct2001_0530:ORA-01092: ORACLE instance terminated. Disconnection forc

  2. #2
    Join Date
    Dec 1999
    Cincinnati, Ohio USA
    Have you recently done a shutdown abort? If so here is some information....

    Error: ORA 7265
    Text: sppst: semop error, unable to increment semaphore.
    Cause: Semop system call returned an error. Semaphore set may not exist.
    Action: Check errno. Semaphore id is returned in sercose[0]. Check
    semaphore set existence. A possible cause for this error is that a
    "shutdown abort" was done while this process was running.

    *** Important: The notes below are for experienced users - See [NOTE:22080.1]

    Oracle on Unix uses semaphores to signal between processes.
    This error means that an Oracle process tried to signal another
    Oracle process but for some reason the semaphores no longer exist.

    This is an extremely common error which is reported to the ALERT
    log when an instance has been shutdown (and possibly restarted).

    Check the trace files for any other errors reported at the same
    time. If there are none this error can be safely ignored as it
    is almost certainly from an oracle process which was running before
    the database was shutdown and restarted.

  3. #3
    Join Date
    Mar 2001
    Looks like the database was forced to shutdown, ie., shutdown abort. Is there more to this log file?

    It just mentions the forced shutdown while your process was running. Either another admin did a shutdown abort or a scheduled program (like cron) took the database down in abort mode OR something major happened to the database instance (like an ora-600).

    are there any other trace files in the bdump or udump directories? They may tell you more.

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

We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.