Re: Solaris 2.2 + Oracle 7.0.15 problem

In article <CKxtMu.Cus_at_ireq.hydro.qc.ca>, stephane_at_tdsb-s.mais.hydro.qc.ca (Stephane Vachon) writes:
>
> Hello again,
>
> Can someone figure this one out...
>
> First configuration:
> --------------------
> Hardware: Sun SparcStation 10 Model 512 (2 cpu's)
> 64 Mb memory
> 6 Gb disk
> OS: Solaris 2.2
> Patches: All required mandatory patches + some others
> Installation: As a server
> Database: Oracle 7 release 7.0.15
> Comment: Everything is smooth, up and running for about a month
>
>
> Second configuration: (problems)
> --------------------
> Hardware: Sun SparcStation 10 Model 40
> 32 Mb memory
> 2 Gb disk
> OS: Same as first config.
> Patches: Same as first config.
> Installation: As a server
> Database: Same as first config.
> Comment: For the first database startup and shutdown,
> everything looks ok but in the next minutes
> or hours, when you try to use the database
> or try to use SQL*DBA instance startup you
> get the following messages:
>
> at startup: ORA-02725 osnpbr: cannot send break signal
> at console: PAGE GET GETS NULL PAGE
>
> Message description:
>
> 02725, 00000, "osnpbr: cannot send break signal"
> // *Cause: The Pipe driver could not send a break message to the ORACLE
> // shadow process.
> // *Action: Kill system call failed. Check errno and contact customer
> // support.
>
> Others: The only setup change is the hardware ???
> Did i miss a patch somewhere or is it a known
> problem ? I also noticed that a shared memory
> segment from oracle hangs in so i have to drop
> it with the (ipcrm -m #) command to try a
> fresh startup but like i said it doesn't work.
> Another thing, if i try to shutdown the computer
> and try to startup the database it works 50% of
> the time.
>
> Stephane, help me...

We had pretty much the same problem, also on a Sparc 10, model 40, 32mb, 2 gig of disk. To be truthful, we never found an acceptable explanation of what was going on. We got Solaris 2.3 late in 1993, and I trashed everything and started over from scratch (this was a demo system) and the problem has not come back.

I'd suggest going to 2.3 if you can swing it.

Bob

-- 
Bob Swisshelm                | swisshelm_at_Lilly.com     | 317 276 5472
Eli Lilly and Company        | Lilly Corporate Center  | Indianapolis, IN 46285