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 : 27-05-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-14177 : STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
  • ora-32602 : FREEPOOLS and FREELIST GROUPS cannot be used together
  • ora-39181 : Only partial table data may be exported due to fine grain access control on string
  • ora-07705 : sksaprs: device name buffer too small
  • ora-01903 : EVENTS keyword expected
  • ora-40223 : data mining model import failed, job name=string, error=string
  • ora-23328 : mview base table "string"."string" differs from master table "string"."string"
  • ora-02458 : HASHKEYS must be specified for a HASH CLUSTER
  • ora-12402 : invalid format string: string
  • ora-07804 : slpdtb: number too large for supplied buffer
  • ora-02183 : valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-27012 : skgfrd: read from file failed
  • ora-22806 : not an object or REF
  • ora-30358 : summary and materialized view are not in same schema
  • ora-12442 : policy column "string" already used by an existing policy
  • ora-01804 : failure to initialize timezone information
  • ora-36846 : (XSLMGEN16) AW name is greater than 30 bytes
  • ora-09274 : szrfc: insufficient role name buffer space
  • ora-31512 : name cannot contain double quotation marks
  • ora-32587 : Cannot drop nonexistent string supplemental logging
  • ora-19830 : error from target database: string
  • ora-13863 : Statistics aggregation for service(module/action) string is not enabled
  • ora-31080 : type not specified for attribute or element "string"
  • ora-15128 : ASM file name 'string' exceeds maximum length string
  • ora-13237 : internal error during R-tree concurrent updates: [string]
  • ora-01569 : data file too small for system dictionary tables
  • ora-39776 : fatal Direct Path API error loading table string
  • ora-00027 : cannot kill current session
  • ora-23615 : Block number string does not exist for script string
  • ora-29803 : missing ANCILLARY keyword
  • 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.