Home » RDBMS Server » Server Utilities » Schema Expired & Locked after import (Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit, Linux)
Schema Expired & Locked after import [message #655087] Sun, 21 August 2016 23:59 Go to next message
praveenpraj
Messages: 19
Registered: October 2011
Location: India
Junior Member
Friends, why Schemas are getting "EXPIRED & LOCKED" automatically after import (impdp).

SELECT resource_name,resource_type,limit FROM dba_profiles WHERE profile='DEFAULT';
RESOURCE_NAME	        RESOURCE_TYPE	LIMIT
COMPOSITE_LIMIT	          KERNEL	UNLIMITED
SESSIONS_PER_USER	  KERNEL	UNLIMITED
CPU_PER_SESSION	          KERNEL	UNLIMITED
CPU_PER_CALL	          KERNEL	UNLIMITED
LOGICAL_READS_PER_SESSION KERNEL	UNLIMITED
LOGICAL_READS_PER_CALL	  KERNEL	UNLIMITED
IDLE_TIME	          KERNEL	UNLIMITED
CONNECT_TIME	          KERNEL	UNLIMITED
PRIVATE_SGA	          KERNEL	UNLIMITED
FAILED_LOGIN_ATTEMPTS	  PASSWORD	10
PASSWORD_LIFE_TIME	  PASSWORD	UNLIMITED
PASSWORD_REUSE_TIME	  PASSWORD	UNLIMITED
PASSWORD_REUSE_MAX	  PASSWORD	UNLIMITED
PASSWORD_VERIFY_FUNCTION  PASSWORD	NULL
PASSWORD_LOCK_TIME	  PASSWORD	1
PASSWORD_GRACE_TIME	  PASSWORD	7
Re: Schema Expired & Locked after import [message #655089 is a reply to message #655087] Mon, 22 August 2016 00:38 Go to previous messageGo to next message
John Watson
Messages: 7184
Registered: January 2010
Location: Global Village
Senior Member
Can you copy/paste a demonstration? Perhaps query dba_users, run impdp, and query dba_users again?

[Updated on: Mon, 22 August 2016 00:39]

Report message to a moderator

Re: Schema Expired & Locked after import [message #655090 is a reply to message #655087] Mon, 22 August 2016 00:46 Go to previous messageGo to next message
Michel Cadot
Messages: 65254
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Maybe they are expired and locked in the export dump.
Please post the command line and log of import.
Is this an original import or a Data Pump import?

[Updated on: Mon, 22 August 2016 00:48]

Report message to a moderator

Re: Schema Expired & Locked after import [message #663806 is a reply to message #655087] Tue, 20 June 2017 16:24 Go to previous messageGo to next message
rodrigo.jg
Messages: 2
Registered: June 2017
Junior Member
I was Have the same problem on all users importing database 10g to 12.2.0.

IMPDP Log..
ORA-39384: Warning: User xxx has been locked and the password expired.

Re: Schema Expired & Locked after import [message #663807 is a reply to message #663806] Tue, 20 June 2017 18:20 Go to previous messageGo to next message
BlackSwan
Messages: 25748
Registered: January 2009
Location: SoCal
Senior Member
rodrigo.jg wrote on Tue, 20 June 2017 14:24
I was Have the same problem on all users importing database 10g to 12.2.0.

IMPDP Log..
ORA-39384: Warning: User xxx has been locked and the password expired.

[oracle@vbgeneric ~]$ oerr ora 39384
39384, 00000, "Warning: User %s has been locked and the password expired."
// *Cause:   Oracle Data Pump displayed this message while importing users
//           because it determined that a user was created with a password
//           version that is no longer supported. See the documentation for
//           PASSWORD_VERSIONS in the system view DBA_USERS for more 
//           information.
// *Action:  Connect AS SYSDBA and unlock the account and set a password 
//           for the user.  This can be done by issuing an 
//           "ALTER USER <username> ACCOUNT UNLOCK;" command followed by
//           an "ALTER USER <username> IDENTIFIED BY <password>;" command.
//           See the documentation for the SQLNET.ORA parameter
//           SQLNET.ALLOWED_LOGON_VERSION_SERVER which explains how to
//           control which password versions will be created when the
//           password for the user is reset.
Re: Schema Expired & Locked after import [message #663808 is a reply to message #663807] Tue, 20 June 2017 18:54 Go to previous message
rodrigo.jg
Messages: 2
Registered: June 2017
Junior Member
I set following...

SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8
SQLNET.ALLOWED_LOGON_VERSION_SERVER=8


But in sqlnet.ora from GRID. It is need to configure in sqlnet.ora from RDBMS infrastructure.
It's work now.

Thanks
Previous Topic: Issue in SQL loader control file
Next Topic: impdp without CREATE USER metadata
Goto Forum:
  


Current Time: Thu Dec 14 12:43:08 CST 2017

Total time taken to generate the page: 0.09491 seconds