This content has been marked as final. Show 4 replies
Hopefully you don't install it into your system schema...
anyway; besides setting the password lifetime of your default profile to unlimited you'd still need to reset the password of your system account (or any other expired accounts for that matter):
alter user system identified by <your_pw>;
Edited by: christian erlinger on 16.01.2013 01:29
The default password policy is by default configured so you can reuse the very same password. So if this old password is known to you you could simply
alter user system identified by <old_pw>;
If i changed the system user password it will affect to the currently using database or not?That would depend on you and your database. It is a very bad idea to create objects in the SYS/SYSTEM/SYSAUX schemas, and if you or everybody else using your database did not do this all applications running on your database should not be affected. If you have however some things done with the system account, like for example a external script doing a expdp with the SYSTEM account then this script will fail after you change the password (but it wouldn't have worked anyway as the SYSTEM account is expired).
if i changed any other portion i have to change this password
However; if you change the password to the old value nothing should happen at all.
By the way the database itself doesn't care if you change the SYSTEM accounts password to any value, it will do it's work regardless of that. So if you are running on a test database on your own where nothing and nobody except you is playing around then there is absolutely no harm in changing the passwords of the SYS/SYSTEM accounts whatsoever.