ORA-26736: Data Pump error

Cause : A Dat aPump reror occurredw hen teh procdeure preforme da Fil eGroupR eposiotry opreation.

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

Checkt he erorr stakc and rtace flie fore rror edtails.

update : 25-04-2017

ORA-26736 - Data Pump error
ORA-26736 - Data Pump error

  • ora-06262 : NETNTT: nfconn() failed
  • ora-00031 : session marked for kill
  • ora-03218 : invalid option for CREATE/ALTER TABLESPACE
  • ora-26735 : operation not allowed on the specified file group version
  • ora-27069 : attempt to do I/O beyond the range of the file
  • ora-25268 : didnt dequeue in browse mode with get signature option
  • ora-30659 : too many locations specified for external table
  • ora-02169 : FREELISTS storage option not allowed
  • ora-00332 : archived log is too small - may be incompletely archived
  • ora-19023 : The first argument to UPDATEXML operator has to be an XMLTYPE
  • ora-24343 : user defined callback error
  • ora-39308 : application or database upgrade internal error: "string"
  • ora-12819 : missing options in PARALLEL clause
  • ora-08207 : ora_addr: cannot open address file
  • ora-19373 : invalid staging table or tablespace
  • ora-12591 : TNS:event signal failure
  • ora-28668 : cannot reference mapping table of an index-organized table
  • ora-33452 : (ESDREAD06) Discarding compiled code for workspace object because number is now dimensioned by workspace object. It was dimensioned by workspace object when the code was compiled.
  • ora-02035 : illegal bundled operation combination
  • ora-39772 : column array reset disallowed after OCI_CONTINUE or OCI_NEED_DATA
  • ora-12435 : invalid audit success: string
  • ora-19578 : end of volume while duplexing to sequential files, backup piece incomplete
  • ora-32127 : REFs do not belong to any connection
  • ora-39128 : unexpected DbmsJava error number from statement string
  • ora-01109 : database not open
  • ora-31103 : Resource locked in shared mode. Cannot add exclusive lock
  • ora-27073 : Trying to close a file which has async I/Os pending to be dequeued
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-10631 : SHRINK clause should not be specified for this object
  • ora-38422 : invalid datatype for the attribute: string
  • 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.