Chuck
12-10-2002, 08:24 AM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
All my database events log in as a user who's password recently
changed. I made the change in the OEM preferred credentials too and
all appeared to be running okay for a couple of days. Now events that
worked since the password change are failing with an invalid
username/password, however I can click on the same database in the
OEM console's network explorer and log right in using the same
preferred credentials. Why is this happening?
Worse is that once the event fails, the only way to get it running
again seems to be deleting and reregistering it. Is there a better
way to get failed events running again? There are way too many events
where this is happening for reregistration to be a viable option.
- - --
Chuck
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBPfYVKVVYIIV9CtSHEQKBawCg/gycX2WWtDycIJeV+A+A8Ls6OhkAn0bB
Dz3jTq0+Vhnylg5d1elHWqwW
=uMyr
-----END PGP SIGNATURE-----
Hash: SHA1
All my database events log in as a user who's password recently
changed. I made the change in the OEM preferred credentials too and
all appeared to be running okay for a couple of days. Now events that
worked since the password change are failing with an invalid
username/password, however I can click on the same database in the
OEM console's network explorer and log right in using the same
preferred credentials. Why is this happening?
Worse is that once the event fails, the only way to get it running
again seems to be deleting and reregistering it. Is there a better
way to get failed events running again? There are way too many events
where this is happening for reregistration to be a viable option.
- - --
Chuck
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBPfYVKVVYIIV9CtSHEQKBawCg/gycX2WWtDycIJeV+A+A8Ls6OhkAn0bB
Dz3jTq0+Vhnylg5d1elHWqwW
=uMyr
-----END PGP SIGNATURE-----