PASSWORD_HISTORY

sol1 : http://www.linkedin.com/answers/technology/information-technology/databases/TCH_ITS_DBS/1009571-41077099 
"exclude=PASSWORD_HISTORY" to you impdp command
sol2:

DataPump Import (IMPDP) Fails With Errors ORA-39083 ORA-6550 PLS-00103 On Object Type PASSWORD_HISTORY [ID 1053162.1] Applies to: Oracle Server - Enterprise Edition - Version 10.1.0.2 and later Information in this document applies to any platform. ***Checked for relevance on 28-NOV-2012*** Symptoms When importing a dump file with IMPDP the following errors are raised: Starting "BACKUPUSERR1"."dp_21426_12": Processing object type SCHEMA_EXPORT/DEFAULT_ROLE Processing object type SCHEMA_EXPORT/PASSWORD_HISTORY ORA-39083: Object type PASSWORD_HISTORY failed to create with error: ORA-06550: line 1, column 26976: PLS-00103: Encountered the symbol "DECLARE" Failing sql is: DECLARE SUBTYPE HIST_RECORD IS SYS.DBMS_PSWMG_IMPORT.ARRAYOFHISTORYRECORDS; HIST_REC HIST_RECORD; i number := 0; BEGIN i := i+1; HIST_REC(i).USERNAME := 'STAGESET3R1'; HIST_REC(i).PASSWORD := 'C42005196432786D'; HIST_REC(i).PASSWD_DATE := '11-DEC-09'; i := i+1; HIST_REC(i).USERNAME := 'STAGESET3R1'; HIST_REC(i).PASSWORD := '58E0C666771D9EE6'; Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA Checking the USER_HISTORY$ contents of the originating database reveals that this table contains a lot of rows. Cause The cause of this problem has been identified in Bug 8589857. It is caused by IMPDP incorrectly splitting up the generation of the PL/SQL code filling the USER_HISTORY$ table in the target database into multiple pieces, where this should have been a single PL/SQL block. Solution The issue will be fixed in the 12.1 release and has been fixed in the 11.2.0.2 patchset. For other releases, download and apply Patch 8589857 which is available from My Oracle Support. Please note that this is a generic patch that can be applied in any platform. Download and review the README for patch 8589857. Apply patch 8589857 in a test environment. Re-test the issue If the issue has been resolved, then migrate the solution as appropriate to other environments.