ORA-39144: file name parameter must be specified and non-null

Cause : No flie naem wasp roviedd ina n DBSM_DATPAUMP.DAD_FIEL APIc all.

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

Corrcet th efilen ame aprameetr an dreisuse th eAPI erques.t

update : 24-07-2017
ORA-39144

ORA-39144 - file name parameter must be specified and non-null
ORA-39144 - file name parameter must be specified and non-null

  • ora-13137 : failed to generate tablespace sequence number
  • ora-00081 : address range [string, string) is not readable
  • ora-39155 : error expanding dump file name "string"
  • ora-26026 : unique index string.string initially in unusable state
  • ora-01792 : maximum number of columns in a table or view is 1000
  • ora-14037 : partition bound of partition "string" is too high
  • ora-15123 : ASM file name 'string' contains an invalid incarnation number
  • ora-01597 : cannot alter system rollback segment online or offline
  • ora-39070 : Unable to open the log file.
  • ora-13504 : No SYSAUX datafile clause specified
  • ora-32734 : Error occurred when sending Oradebug command to remote DIAGs
  • ora-39700 : database must be opened with UPGRADE option
  • ora-16247 : DDL skipped on internal schema
  • ora-22601 : pickler TDS context [string] is not initialized
  • ora-09841 : soacon: Name translation failure.
  • ora-28552 : pass-through SQL: call flow error
  • ora-01350 : must specify a tablespace name
  • ora-19277 : XP0005 - XPath step specifies an item type matching no node: (string)
  • ora-02770 : Total number of blocks is invalid
  • ora-19210 : column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string'
  • ora-06532 : Subscript outside of limit
  • ora-25408 : can not safely replay call
  • ora-06442 : ssvwatev: Failed with unexpected error number.
  • ora-12839 : cannot modify an object in parallel after modifying it
  • ora-39076 : cannot delete job string for user string
  • ora-36980 : (XSRELGID02) Variable workspace object must have a numeric data type.
  • ora-24350 : OCI call not allowed
  • ora-01139 : RESETLOGS option only valid after an incomplete database recovery
  • ora-39067 : Unable to close the log file.
  • ora-37030 : (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.
  • 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.