Re: OMS doesnt start up after reboot

"Howard J. Rogers" <hjr_at_dizwell.com> schrieb im Newsbeitrag news:40c57759$0$1588$afc38c87_at_news.optusnet.com.au...
> Has the IP address on the machine changed since it did work? For example,
is
> this DHCP, and the lease just expired?
>
> What database did OMS store its repository in, and is that database still
in
> working order, and can you connect to it via the tnsnames alias you say is
> still configured correctly?
>
> Ultimately, you could always drop one OMS repository and re-configure
> another.
>
> Also, as Daniel Morgan would say: patch to 9.2.0.4 at least. :-)

  Okay, se. thanks for this. The Oracle instance that the OEM is connected to seemed to be up and running. I tried connecting there using SQL*Plus. It worked. What I didnt do was carry out a statement that would produce rollback info, like a DML statement. Then I got error messages coming in from end users of applications that work with the said instance reporting ORA-01552: cannot use system rollback segment for non-system tablespace

  So I checked on the instance (9i_at_Win2000) and found that since the reboot it was running with UNDO_MANAGEMENT=MANUAL parameter whereas before it was in AUTO mode. Since there is only one rollback segment for system purposes, ORA-01552 was just to obvious to happen. After I set UNDO_MANAGEMENT back to AUTO, restarted the instance, the users had no complaints anymore and guess what: OEM would come up!

  Of course now I wonder how can UNDO_MANAGEMENT just jump from AUTO to MANUAL during a reboot ? It puzzles me, I have never observed that before and I hope to never observe it again...!

>
> Regards
> HJR
>
>
>
> "André Hartmann" <andrehartmann_at_hotmail.com> wrote in message
> news:40c569e0_at_olaf.komtel.net...
> > Hi,
> >
> > after rebooting the computer (Win2000) that has my Oracle Management
> > Server (9i), the OMS would not start up again. The oms.nohup gives the
> > following message.. I am sorry that part of it is in german, but the
> system
> > is in german. The critical part "VXA-2019" says something like "error
when
> > starting up the service". I "googled" the error and someone who posted
the
> > same thing got a reply regarding a faulty tnsnames.ora. However my
> > tnsnames.ora is still correct. The computer just got rebooted and before
> it
> > worked fine for many months.
> >
> > Can anyone help me to track the cause ?
> >
> > Thanks,
> > André
> > :(
> >
> > OEMCTL für Windows NT: Version 9.2.0.1.0 Production
> > Copyright (c) 1998, 2002, Oracle Corporation. Alle Rechte vorbehalten.
> > Oracle Management Server wird hochgefahren...VXA-3008 : OMS-Dienste
werden
> > hochgefahren, bitte warten.
> >
> > oracle.sysman.vxn.VxnBootstrapException:
> > oracle.sysman.vxn.VxnBootstrapException: VXA-2019 : Fehler beim
Hochfahren
> > von Dienst: vdf
> > at oracle.sysman.vxa.VxaAppServer.startServices(VxaAppServer.java:1788)
> > at oracle.sysman.vxa.VxaAppServer.main(VxaAppServer.java:3144)
> >
> > Fehler beim Hochfahren von Oracle Management Server.
> > oracle.sysman.vxn.VxnBootstrapException: VXA-2019 : Fehler beim
Hochfahren
> > von Dienst: vdfjava.lang.NullPointerException:
> > at
> >
>

oracle.sysman.vdm.VdmNotificationManager.stopService(VdmNotificationManager.
> > java:2538)
> > at oracle.sysman.vxa.VxaAppServer.stopServices(VxaAppServer.java:1415)
> > at oracle.sysman.vxa.VxaAppServer.exit(VxaAppServer.java:2533)
> > at oracle.sysman.vxa.VxaAppServer.main(VxaAppServer.java:3166)
> > "Could not start management server. Initialization failure"
> >
> >
>
>
Received on Tue Jun 08 2004 - 04:25:49 CDT