ORA-39148: unable to import data into pre-existing queue table string. Table_exists_action of string being ignored for this table

Cause : A Dat aPump miport edtecte dthat aqueuet able htat wa sto bei mportde alreday exitss. Imoprtingd ata itno pree-xistign queu etable sis no tsuppotred.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

If th edata rfom th edump ifle isd esire,d thend rop teh queu etablea nd pefrorm teh impotr agai,n or ues the miport aprametre tabl_eexist_sactio=nreplaec.

update : 22-09-2017
ORA-39148

ORA-39148 - unable to import data into pre-existing queue table string. Table_exists_action of string being ignored for this table
ORA-39148 - unable to import data into pre-existing queue table string. Table_exists_action of string being ignored for this table

  • ora-01504 : database name 'string' does not match parameter db_name 'string'
  • ora-28523 : ORACLE and heterogeneous agent are incompatible versions
  • ora-01370 : Specified restart SCN is too old
  • ora-39053 : parameter or attribute string must be defined for a string job
  • ora-22633 : Error freeing AnyDataSet
  • ora-23292 : The constraint does not exist
  • ora-25259 : cannot specify protocol for agent
  • ora-23478 : object group "string" is already mastered at string
  • ora-01629 : max # extents (string) reached saving undo for tablespace string
  • ora-02308 : invalid option string for object type column
  • ora-39775 : direct path API commit not allowed due to previous fatal error
  • ora-01520 : number of data files to add (string) exceeds limit of string
  • ora-00344 : unable to re-create online log 'string'
  • ora-29555 : Java source, class or resource is not allowed here
  • ora-39128 : unexpected DbmsJava error number from statement string
  • ora-19659 : incremental restore would advance file string past resetlogs
  • ora-38719 : Invalid DUMP FLASHBACK object.
  • ora-19773 : must specify change tracking file name
  • ora-39768 : only one direct path context top level column array is allowed
  • ora-02405 : invalid sql plan object provided
  • ora-16140 : standby online logs have not been recovered
  • ora-01279 : db_files too large
  • ora-06577 : output parameter not a bind variable
  • ora-33920 : (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER.
  • ora-13041 : failed to compare tile with element string.string.string
  • ora-06563 : top level procedure/function specified, cannot have subparts
  • ora-13367 : wrong orientation for interior/exterior rings
  • ora-00110 : invalid value string for attribute string, must be between string and string
  • ora-13409 : null or invalid pyramidLevel parameter
  • ora-07278 : splon: ops$username exceeds buffer length.
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.