Showing posts with label dbua. Show all posts
Showing posts with label dbua. Show all posts

Thursday, May 04, 2017

12.2c dbua complains 10G version password being used

since dbua complains, and I checked the 12.1 database to be upgraded.
"In exclusive mode, accounts which oly have the 10G password version (see DBA_USERS.PASSWORD_VERSIONS)"   ...


There is one account RMAN somehow is having 10G version password.

SQL> select username, password_versions from dba_users where username='RMAN';

USERNAME
--------------------------------------------------------------------------------
PASSWORD_VER
------------
RMAN
10G

although the parameter sensitive is already true, set the minimum allowed version in sqlnet.ora (SQLNET.ALLOWD_LOGON_VERSION_SERVER) to 10. but still not worked for me.

Finally, solution worked for me is to change its password manually.

SQL> password
Changing password for RMAN
Old password:
New password:
Retype new password:
Password changed
SQL> select username, password_versions from dba_users where username='RMAN';

USERNAME
--------------------------------------------------------------------------------
PASSWORD_VER
------------
RMAN
10G 11G 12C


SQL> password
Changing password for RMAN
Old password:
New password:
Retype new password:
Password changed
SQL> select username, password_versions from dba_users where username='RMAN';

USERNAME
--------------------------------------------------------------------------------
PASSWORD_VER
------------
RMAN
10G 11G 12C

Monday, June 04, 2012

DBUA complains database not in mounted state

"The Upgrade Assistant failes in bringing up the database XXX. Oracle Home /oracle/XXX/11202 obtained from file /etc/oratab was used to connect to the database. Either the database is not running from Oracle Home /oracle/XXX/11202 or the correct Initialization Parameter file (pfile) was not found" Then it asks me to locate the pfile.

My case is similar to http://scn.sap.com/thread/1938507

So cat the Welcome_.txt 

> cat  Welcome_TTTT.txt
The presence of this file indicates that the database is opened up with the new Oracle Home binaries.

/software/orattt/admin/cfgtoollogs/dbua/logs_bak> ls -lrt
total 188
-rw-r----- 1 orattt orattt    102 Oct 21  2010 Welcome_TTTT.txt
-rw-r----- 1 orattt orattt 140879 May 24 16:03 sqls.log
-rw-r----- 1 orattt orattt   2104 May 24 16:07 PreUpgradeResults.html
-rw-r----- 1 orattt orattt  20034 May 24 16:07 trace.log

That is the culprit.

After I rename the directory, everything goes smoothly.