Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / Oracle / Oracle Server / September 2007

Tip: Looking for answers? Try searching our database.

Error whilst duplicating database using RMAN

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
trub3101 - 28 Sep 2007 12:49 GMT
Hi all,

Solaris 9

Oracle 9.2.0.1.0

I hoping someone can help me out with this. I have just tried to
duplicate a database using RMAN however, I made one fundamental error
- I tried to create the database name with more than eight characters
(nine to be exact!). I then quickly tried to quickly rectify this by
removing the underscore character which made up part of the database
name/ORACLE_SID to make it just eight characters.

I have also renamed pathnames (not neccesaary but I thought I'd do it
anyway to reflect the change) on the server as they were made up using
ORACLE_SID in them, renamed the init.ora file changing all occurrences
of the former db_name with the new db_name, consequently the
db_file_name_convert and log_file_name_convert parameters were
changed, I also changed the tnsnames.ora and listener.ora files to
include the new ORACLE_SID.

Now when I try to log into the new database I am getting this error:

SQL*Plus: Release 9.2.0.1.0 - Production on Fri Sep 28 12:08:18 2007

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

SQL> conn sys@testprd4.xxxx as sysdba
Enter password:
Connected to an idle instance.
SQL> startup nomount
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 I am also running
one production database and two standby databases on the same server
(if that helps!)

Any suggestions would be greatly appreciated.

tb3101
Jerome Vitalis - 28 Sep 2007 12:56 GMT
>> 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.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.