Re: sysman, dbsnmp, assword change in em/dbconsole

It's the issues of scale that bug me.  This is a pretty ugly process and
the scripting will be doublely so.  If you have a rolling password policy
(and you should) then you'll need to do this regularly on all your systems.  

BTW, I just installed a test 11g db and changed the sysman pw following
the 10g metalink note.  The procedure seemed to work, but the nightly
sysman jobs did not feel well in the morning.  Thar be dragons here.

On Wed, Dec 03, 2008 at 10:00:22AM -0500, Robert Buda wrote:
> Hi,
> It's actually not as bad as it seems. I don't remember the details for
> dbconsole, but I know that after you restart services, the password gets
> encrypted in the file so it does not stay clear text for very long. I agree
> that they could provide a better mechanism for changing the password.
> Bob
> Robert Buda
> Buda Consulting, Inc
> 100 Overlook Center, 2nd Floor
> Princeton, NJ 08540
> 609 375-2368
> -----Original Message-----
> From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
> On Behalf Of Ray Stell
> Sent: Tuesday, December 02, 2008 9:47 AM
> To: oracle-l@xxxxxxxxxxxxx
> Subject: sysman, dbsnmp, assword change in em/dbconsole
> Interested in 11g here.
> There are these notes, 259387.1 and 259379.1, on the atrocious password
> change procedures for sysman and dbsnmp.  I see some notes on mgmt_view, but
> nothing for a standalone dbconsole.  Is there anything "special" for this
> guy?
> Putting clear text strings in files...well, isn't that special?
> --
> No virus found in this incoming message.
> Checked by AVG -
> Version: 8.0.176 / Virus Database: 270.9.12/1824 - Release Date: 12/2/2008
> 9:31 AM

Other related posts: