>> Oracle 9.2.0.1.0
> ORA-27302: failure occurred at: skgpwreset1
> ORA-27303: additional information: invalid shared ctx
> ORA-27146: post/wait initialization 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 occurred at: sskgpsemsper
> I did not shutdown the previous instance (nine characters) which was
> started for the RMAN duplication before it failed
Kill the processes of this instance at the OS level and proceed with the
duplication with your new auxiliary instance configuration.
> I am also running
> one production database and two standby databases on the same server
A production database that uses the same ORACLE_HOME? How come you haven't
upgraded your Oracle installation yet?
-----
échangez opinions et commentaires dans les forums de discussion.
http://www.usenetgratuit.com/
trub3101 - 28 Sep 2007 14:27 GMT
> >> Oracle 9.2.0.1.0
> > ORA-27302: failure occurred at: skgpwreset1
[quoted text clipped - 16 lines]
> -----
> ?changez opinions et commentaires dans les forums de discussion.http://www.usenetgratuit.com/
I have only just stepped into this role recently!
trub3101 - 28 Sep 2007 14:29 GMT
> >> Oracle 9.2.0.1.0
> > ORA-27302: failure occurred at: skgpwreset1
[quoted text clipped - 16 lines]
> -----
> ?changez opinions et commentaires dans les forums de discussion.http://www.usenetgratuit.com/
Hi Jerome,
Mmmm.. How can I identify the instance at the OS level?
Thanks for you input by the way.
trub3101 - 28 Sep 2007 14:32 GMT
> > >> Oracle 9.2.0.1.0
> > > ORA-27302: failure occurred at: skgpwreset1
[quoted text clipped - 24 lines]
>
> - Show quoted text -
Pretend you did not see my earlier reply. Where is that embarrassment
smiley again?
Jerome Vitalis - 28 Sep 2007 14:49 GMT
> > Mmmm.. How can I identify the instance at the OS level?
Hmm, if memory serves, on Solaris, "ps auxww|grep <SID>" should do the
trick (I haven't any solaris box near me at the moment).
Otherwise try "ps -ef|grep <SID>".
Be careful since some processes might belong to other instances whose name
contains your <SID> (though it should not be the case since you said this
<SID> name is too long!)
> > Thanks for you input by the way.- Hide quoted text -
> Pretend you did not see my earlier reply. Where is that embarrassment
> smiley again?
;-)
-----
échangez opinions et commentaires dans les forums de discussion.
http://www.usenetgratuit.com/
trub3101 - 28 Sep 2007 17:53 GMT
> > > Mmmm.. How can I identify the instance at the OS level?
>
[quoted text clipped - 13 lines]
> -----
> ?changez opinions et commentaires dans les forums de discussion.http://www.usenetgratuit.com/
After reducing the number of processes in my init.ora file I managed
to log on and perform the duplication successfully. The other solution
apparently was to increase the semaphore parameters in /etc/system
SEMMSL and SEMMNI.
Thanks again for your input Jerome!
tb3101
trub3101 - 28 Sep 2007 14:43 GMT
> > >> Oracle 9.2.0.1.0
> > > ORA-27302: failure occurred at: skgpwreset1
[quoted text clipped - 24 lines]
>
> - Show quoted text -
Hi Jerome,
I killed the processes at the OS level for the old instance (nine
characters) which was still there pmon, arc, etc...
However, I am still unable to log into the new instance (eight
characters). Same error.
I doubt whether I will be able to proceed with the RMAN duplication if
I am unable to startup nomount the instance.
Of course I could be wrong!
Cheers,
tb3101
Jerome Vitalis - 28 Sep 2007 17:45 GMT
> I killed the processes at the OS level for the old instance (nine
> characters) which was still there pmon, arc, etc... However, I am still
[quoted text clipped - 4 lines]
>
> Of course I could be wrong!
According to the error message you get, you have run out of OS semaphores.
You'll have to investigate with commands like ipcs whether you have to
tune the OS to allow for more semaphores for your new instance or if some
semaphores from your defunct instances are still present.