Re: ORA-27123 when migrating (9.0.1 to 9.2.0.3)

g8rb8 wrote:
> Hello-
>
>
>
> I am in the midst of migrating an instance from 9.0.1 on Sun Sparc 5.8
> to 9.2.0.3.
>
>
>
> This instance(TEST) was running on this server at 9.0.1 prior to the
> upgrade without a problem. The new version of Oracle was installed an a
> couple of instances upgraded via the Export/import method. Another DBA
> performed these tasks.
>
>
>
> No problems were reported by users testing the self service applications
> nor the Internet Native Applications, but I do not know how much testing
> has taken place.
>
>
>
> At this point, I have taken over the server, and I chose to migrate the
> instance, via the STARTUP MIGRATE command. Everything appeared fine, I
> followed up with the catalog upgrade script u0900010.sql and then
> upgraded the other components with the cmpdbmig.sql script. After
> restarting, I ran utlrp.
>
>
>
> Everything ran fine without errors.
>
>
>
> I then edited the init.ora and removed the _system_trig_enabled
> parameter. Restarted, created a spfile from the pfile, and changed and
> bounced the listener.
>
>
>
> Everything still appeared fine. All processes are up, all system
> objects are valid. Oracle can log in as system, or '/ as sysdba'
> just fine.
>
>
>
> When I went to my normal UNIX userid for the application I administer, I
> got a ora-27123 - when attempting to login via sqlplus as system, or any
> other administrative user.
>
>
>
> I checked the previously created instances, and got the same error. I
> then shut down the spare instances to free up the segments, and that
> didn't help.
>
>
>
> Has anyone seen this behavior before and can send me some hints?
>
>
>
> Thanks much! g8r
>
>
> --
> Posted via http://dbforums.com

The ORA-27123 error indicates
"unable to attach to shared memory segment".

This might occur because incorrect permissions exist on the "oracle" executable file.
(Did you run root.sh during your migration process?)

HTH & YMMV HAND! Received on Sun Aug 24 2003 - 08:46:01 CDT