000027942 - KB-1482 - Oracle import fails with ORA-600 error

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000027942
Applies ToAffected Versions: 4.1
While trying to import an ACM Oracle backup file (Export_AVDB_avuser.dmp) and they get the following error in the import log file.


Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC
ORA-31684: Object type TYPE:"AVUSER"."RES_ROW" already exists
ORA-31684: Object type TYPE:"AVUSER"."ROLE_TYPEID_TYPE" already exists
ORA-31684: Object type TYPE:"AVUSER"."ROLE_DEFINITION_TYPE" already exists
ORA-31684: Object type TYPE:"AVUSER"."ROLE_MEMBERSHIP_TYPE" already exists
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW01" prematurely terminated
ORA-31672: Worker process DW01 died unexpectedly.
Job "AVUSER"."AVDB_IMPORT_AVUSER" stopped due to fatal error at 16:02:55
ORA-39014: One or more workers have prematurely exited.


Review of the terminal output while running the import script, shows an additional error while dropping the 'avuser' (an action required to do a full import, and which is done as part of the ACM IMPORT_AVDB_Avuser.sh script):


ORA-00600: internal error code, arguments: [psdtyfnd_with_suffix], [], [], [], [], [], [], []

The customer also tried to import the file directly, using the impdb command without using the ACM script. To do this, the first step is to drop the Oracle user AVUSER and this resulted in this error:

Enter user-name: sys as sysdba
Enter password:
Connected to:
Oracle Database 10g Release - 64bit Production
SQL> drop user AVUSER cascade;
drop user AVUSER cascade
ERROR at line 1:
ORA-00600: internal error code, arguments: [psdtyfnd_with_suffix], [], [], [], [], [], [], []
CauseReview of the Oracle Metalink Support website reveals that this is a known problem with the impdb utility (and sqlplus user drop function), where temporary duplicate tables are created and not correctly removed. Oracle further states that they have not yet identified the root cause, but that the corrective action is to drop these duplicates (in the correct order). Once these duplicates are gone, the 'drop user' and the import functions work properly.
Attached is a sql script, (run as AVUSER, as noted in the comments of the sql script) that can be made available to customers, on a case by case basis in the event this error occurs. Instructions for the execution of this script are included in the script comments.


Note that occasionally, downloading files can result in inadvertant CR (carriage returns) in the script, which can result in PL/SQL errors. Ensure that your terminal width is set to 132 cols to help avoid this problem in the future.