Inactive Account Lock

In oracle 12.2 database, parameter INACTIVE_ACCOUNT_TIME introduced for user profiles.
The INACTIVE_ACCOUNT_TIME profile parameter locks a user account if that has not logged in to the database  in  specified number of days. Default value for INACTIVE_ACCOUNT_TIME is 35. The minimum setting is 15 and the maximum is 24855.

Last Login Time of User:

In release previous to 12c, to get last login time details of the user, we have to enable “AUDIT SESSION” and then query the AUD$ table but in case of 12c we can get from table USER$ and in SPARE6 column.

USER$ table was in 11gR2 :

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

Below column added in 12c:

SPARE6: Last login time of the user.

Oracle Database 12c Feature:

1. Last Login Time of User:

2.Inactive Account Lock:

3.Invisible Columns in Oracle Database 12c:

4.Parameter MAX_STRING_SIZE to EXTENDED :Store More in VARCHAR2.

5.READ Privilege:

6.Unified Auditing :

7.ASMCMD Commands for Password File Management:

8.Exporting View Data:

9.No Logging Option in Data Pump Import:

A new feature has been added in datapump of oracle 12c. We can import data with nologgin option i.e without generating logs. We sometimes face issue while importing big tables, as it generates lot of archive logs.

TRANSFORM=DISABLE_ARCHIVE_LOGGING:Y – This parameter can be used to make the impdp nologging.

TRANSFORM=DISABLE_ARCHIVE_LOGGING:Y:TABLE

TRANSFORM=DISABLE_ARCHIVE_LOGGING:Y:INDEX

impdp dumpfile=dbaclass.dmp logfile=dbaclass.log directory=DUMP tables=test.TEST TRANSFORM=DISABLE_ARCHIVE_LOGGING:Y

Previously, If we are loading data to an existing partitioned table using impdp, then despite mentioning parallel option, partitions were getting loaded one by one, Which slowdown the import process.

TRUST_EXISTING_TABLE_PARTITIONS — tells Data Pump to load partition data in parallel into existing tables. You should use this option when you are using Data Pump to create the table from the definition in the export database before the table data import is started. This is done as part of a migration when the metadata is static and can be moved before the databases are taken off line in order to migrate the data. Moving the metadata separately minimizes downtime. If you use this option and if other attributes of the database are the same (for example, character set), then the data from the export database goes to the same partitions in the import database.

impdp dumpfile=test1_%U.dmp

logfile=imp_test1.log

directory=EXPDP

table_exists_action=APPEND

data_options=TRUST_EXISTING_TABLE_PARTITIONS

parallel=8

10.Rename and Replace ASM Disk(s) in Diskgroup:

11.Added Administrative Privileges:

12.Adding, Dropping, Truncating Multiple Partitions:

13.Merging and Splitting Multiple Partitions:

14.Use of Sequence Value in Column DEFAULT:

15.Cascaded Truncate:

16.New Row Limiting Clause in SELECT:

17.