You can have this type of problem with the listener, if your system
is low on contiguous disc sectors. You can check that by issuing
a "DISCFREE A" command at the MPE prompt. On the listing
produced, for each disc you will find a line labeled:

        LARGEST FREE AREA:              nnnn

where nnnn is the largest contiguous free space available.
If this value is too small, sometimes the listener can going
dead.

Patrick

> -----Original Message-----
> From: IT - Finn Iversen Clausen [SMTP:[log in to unmask]]
> Sent: 14 January 1999 11:38
> To:   'Patrick Fourny'
> Subject:      SV: Oracle 7.3.2.3.0.
> 
> Tanks for Your reply.
> 
> Could You get a little more concrete about contig. sectors (listener
> process
> going dead)?
> 
> Best regards
> Finn I Clausen
> Møller & Co. A/S, Denmark
> 
> > -----Oprindelig meddelelse-----
> > Fra:        Patrick Fourny [SMTP:[log in to unmask]]
> > Sendt:      14. januar 1999 11:19
> > Til:        [log in to unmask]
> > Cc: 'IT - Finn Iversen Clausen'
> > Emne:       RE: Oracle 7.3.2.3.0.
> > 
> > Hi,
> > 
> > we are currently running the same version of Oracle on our system
> and
> > don't have any problems using "STARTUP" and "SHUTDOWN" commands
> > via batch files. An example of this follows with its output:
> > 
> > !JOB ORA7SHUT,USERNAME.ACCTNAME;HIPRI;OUTCLASS=,5
> > !SETVAR oracle_home "/SYS/ORACLE"
> > !SETVAR oracle_sid "732"
> > !SVRMGRL
> > CONNECT INTERNAL
> > SHUTDOWN
> > EXIT
> > !EOD
> > !EOJ
> > 
> > JOB ORA7SHUT,MANAGER.SYS,PUB.
> > Priority = DS; HIPRI; Time = UNLIMITED seconds.
> > Job number = #j655.
> > THU, JAN 14, 1999, 11:02 AM.
> > HP3000  Release: C.55.00   User Version: C.55.00
> > MPE/iX  HP31900 C.05.08  Copyright Hewlett-Packard 1987.
> > All rights reserved.
> > :SETVAR oracle_home "/SYS/ORACLE"
> > :SETVAR oracle_sid "732"
> > :SVRMGRL
> > 
> > 
> > Oracle Server Manager Release 2.3.2.0.0 - Production
> > 
> > Copyright (c) Oracle Corporation 1994, 1995. All rights reserved.
> > 
> > Oracle7 Server Release 7.3.2.3.0 - Production Release
> > With the distributed, replication, parallel query and Spatial Data
> > options
> > PL/SQL Release 2.3.2.3.0 - Production
> > 
> > SVRMGR> Connected.
> > SVRMGR> Database closed.
> > Database dismounted.
> > ORACLE instance shut down.
> > SVRMGR> Server Manager complete.
> > 
> > :EOJ
> > CPU sec. = 8.  elapsed min. = 1.  THU, JAN 14, 1999, 11:02 AM.
> > 
> > For the listener process going dead, check your contig. sectors with
> > "DISCFREE A". The largest free area should be big enough to allow
> > a new connection to be created (due to the fork() call made by the
> > listener).
> > 
> > Regards,
> > 
> >  _|_|_|_|_|  _|_|_|_|_|        / \         P. Fourny
> >  _|      _|  _|      _|       /| |\        System Engineer
> >  _|      _|  _|             \  | |  /      AC Automation Center
> SA/NV
> >  _|_|_|_|_|  _|          ----\     /--     Keiberg Business Park
> >  _|      _|  _|          ----/     \--     Brussels Airport Area 
> >  _|      _|  _|      _|     /  / \  \      Excelsiorlaan 85
> >  _|      _|  _|_|_|_|_|       /| |\        B-1930 Zaventem 
> > 
> > 
> > > -----Original Message-----
> > > From:     IT - Finn Iversen Clausen [SMTP:[log in to unmask]]
> > > Sent:     13 January 1999 22:43
> > > To:       [log in to unmask]
> > > Subject:  Oracle 7.3.2.3.0.
> > > 
> > > Hei there - Denmark is calling.
> > > 
> > > We are using our 995/400 as an DB-server with Oracle version
> 7.3.2.3.0
> > > (Win95 clients).
> > > 
> > > Everything is running Ok, when keeping "fingers off", but we are
> not
> > > able to
> > > control our OracleDB via batchjobs, ie. "STARTUP" and "SHUTDOWN"
> for
> > > backup-purposes (error messages like "END OF COMMUNICATION
> CHANNEL"
> > > occurs).
> > > Issuing the commands from a MPE-session works OK, but who wants to
> get
> > > an
> > > IBM-like OracleDB-administrator working late hours (MPE is build
> for
> > > working
> > > 24-hours a day - i'm not).
> > > 
> > > Also very often we have problems with our Oracle network listener
> > > "going
> > > dead" (client says "LOST CONTACT"). Seems to relate to often start
> /
> > > shutdown of DB and listener. Only way arround is shutting down the
> > > HP3000.
> > > 
> > > Anyone having experience with Oracle on MPE?
> > > 
> > > Best regards
> > > Finn I Clausen
> > > Møller & Co. A/S, Denmark.