RE: Process problem with OEM

Yup, there certainly is. It seems as though you need to clean them up manually (kill each process *iff* you can clearly identify which ones), or bounce the instance to clean them up. I haven't had the luxury of keeping them around long enough to see if they'll timeout and disappear on their own...

And don't try to startup or shutdown an instance with OEM 2.1. If I remember my testing, about twenty extra processes float around. I also noticed that trying to connect to an 8iR2 instance on OpenVMS as SYSDBA when the instance doesn't have the password file setup causes about four extra processes to hang around.

Rich Jesse                          System/Database Administrator
Rich.Jesse_at_qtiworld.com             QTI -- Sussex, WI USA

> -----Original Message-----
> From: alan.aschenbrenner_at_ihs.com [mailto:alan.aschenbrenner_at_ihs.com]
> Sent: Wednesday, July 26, 2000 13:56
> To: Multiple recipients of list ORACLE-L
> Subject: Process problem with OEM
>
>
> Hi,
>
> Recently we have been working with OEM and have noticed a
> problem with
> it leaving sessions hanging after shutting down OEM console
> and studio. We
> are running both the management server and the oracle 8.1.6
> server on the
> same platform, Solaris 2.6. We are running the OEM console /
> studio from
> windows NT. Has anyone had problems with database processes
> hanging around
> after disconnecting?

This message has been scanned for viruses with Trend Micro's Interscan VirusWall. Received on Wed Jul 26 2000 - 17:14:46 CDT