spare6 in sys.use$

Security related values in the 12c SYS.USER$ table are

CTIME: Date & Time when user was created

PTIME: Date & Time when user password was last changed

LTIME: Date & Time when the user account was locked

LCOUNT: Number of failed login attempts

Added in Oracle Database 12c:

SPARE6: Last login time of the user.

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

ORA-04045 Errors And ORA-01031 during 12.2 DB upgrade via dbua

notice this in alert.log while running dbua.


ORA-12012: error on auto execute of job "APEX_050000"."ORACLE_APEX_MAIL_QUEUE"
ORA-04045: errors during recompilation/revalidation of RMAN.VPC_CONTEXT_TRG
ORA-01031: insufficient privileges


after upgrade, notice the object is invalid.

As this a RMAN catalog database, I will need to upgrade the catalog too.

connect catalog database as RMAN schema

> rman target /

Recovery Manager: Release 12.2.0.1.0 - Production on Thu May 4 19:14:10 2017

Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.

connected to target database: RCATT (DBID=4101766741)

RMAN> connect catalog rman@rcatpdb1

recovery catalog database Password:
connected to recovery catalog database
PL/SQL package RMAN.DBMS_RCVCAT version 12.01.00.02. in RCVCAT database is too old

RMAN> upgrade catalog;

recovery catalog owner is RMAN
enter UPGRADE CATALOG command again to confirm catalog upgrade

RMAN> upgrade catalog;

recovery catalog upgraded to version 12.02.00.01
DBMS_RCVMAN package upgraded to version 12.02.00.01
DBMS_RCVCAT package upgraded to version 12.02.00.01.



check invalid object again, and now no more invalid objects.