ORA-39005: inconsistent arguments

Cause : The current API cannot be executed because of inconsistencies between arguments of the API call. Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further describe the error.

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

Modify the API call to be consistent with itself.

update : 17-08-2017
ORA-39005

ORA-39005 - inconsistent arguments
ORA-39005 - inconsistent arguments

  • ora-01879 : the hh25 field must be between 0 and 24
  • ora-26706 : cannot downgrade capture process
  • ora-06449 : The list IO or the sysvendor is not installed.
  • ora-16953 : Type of SQL statement not supported.
  • ora-02773 : Invalid maximum client wait time
  • ora-08449 : invalid numeric symbol found in picture mask
  • ora-27102 : out of memory
  • ora-07491 : scgrcl: cannot cancel lock request.
  • ora-15196 : invalid ASM block header [string:string] [string] [string] [string] [string != string]
  • ora-06440 : ssaio: the asynchronous read returned incorrect number of bytes
  • ora-31643 : unable to close dump file "string"
  • ora-29398 : invalid privilege name specified
  • ora-36970 : (XSRELTBL12) workspace object must be a self-relation.
  • ora-07290 : sksagdi: specified directory for archiving does not exist.
  • ora-16086 : standby database does not contain available standby log files
  • ora-31105 : User does not own lock "string"
  • ora-22371 : Table contains data of type string.string, version string, which does not exist
  • ora-14019 : partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
  • ora-02001 : user SYS is not permitted to create indexes with freelist groups
  • ora-36222 : (XSLPDSC03) duplicate IGNORE or DENSE information for dimension workspace object
  • ora-02733 : osnsnf: database string too long
  • ora-23457 : invalid flavor ID string
  • ora-39123 : Data Pump transportable tablespace job aborted string
  • ora-02287 : sequence number not allowed here
  • ora-06406 : NETCMN: error sending break message
  • ora-22341 : cannot assign supertype instance to subtype
  • ora-32342 : The EXPLAIN_MVIEW facility failed to explain the materialized view statement
  • ora-06017 : NETASY: message receive failure
  • ora-19659 : incremental restore would advance file string past resetlogs
  • ora-10568 : Failed to allocate recovery state object: out of SGA memory
  • 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.