Changing Oracle System Account Passwords

Changing the four most common Oracle system account (SYSTEM, SYS, SYSMAN, & DBSNMP) passwords is a straightforward process. You needn't worry about breaking connections between the database and other systems because they shouldn't be using these accounts.

SYSTEM and SYS can be changed hassle-free from SQL*Plus.

SQL> alter user system identified by new_password;

SYSMAN and DBSNMP are both used by Oracle Enterprise Manager. A little bit of preparation is necessary to keep OEM functioning.

1. Stop DB Console and the Agent.

emctl stop dbconsole
emctl stop agent

2. You can now change the passwords for both accounts.

3. Edit $ORACLE_HOME/sid/sysman/emd/targets.xml

Look for: <property encrypted="TRUE" name="password" value="####"></property>

Put your password in for the value and change ENCRYPTED to FALSE.
When you restart DB Control it will encrypt the password in the file.

4. Edit $ORACLE_HOME/sid/sysman/config/emoms.properties

Set oracle.sysman.eml.mntr.emdRepPwd to your password.
Set oracle.sysman.eml.mntr.emdRepPwdEncrypted to FALSE.

Again, DB Control will encrypt the password when it is restarted.

5. Restart DB Control.

emctl start dbcontrol

Comments

Post a Comment

Popular posts from this blog

Auditing user logon and logoff in Oracle

To track when a user logs on or off Oracle, enable auditing and audit CONNECT in your database.  Then you can query DBA_AUDIT_TRAIL to find logon and logoff info. alter session SET NLS_DATE_FORMAT = 'DD-MM-YYYY HH24:MI:SS'; select username, action,action_name,timestamp,logoff_time from dba_audit_trail where action_name = 'LOGON' and username = '&user'; Here are some more helpful links: http://itechshare.blogspot.com/2010/06/oracle-how-to-track-logon-logout-in.html http://itechshare.blogspot.com/2010/06/oracle-why-dbaaudittrail-shows-more.html
Read more

RMAN Restore vs. Recovery - what's the difference?

RESTORE is used to restore the datafiles from a backup. You can restore up to the time of the backup or a point before using SET UNTIL . You would lose any changes made to the database after the backup by performing only a RESTORE. RECOVER is used to roll the database forward after a RESTORE by applying the redo logs. In essence, RECOVER = RESTORE + redo logs. The following example assumes you have lost your control files and datafiles, but still have your redo logs. $ rman target / nocatalog RMAN> startup nomount; RMAN> restore controlfile from '/oback/controlfile'; RMAN> alter database mount; RMAN> restore database; RMAN> recover database; RMAN> alter database open resetlogs;
Read more