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 : 23-09-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-01986 : OPTIMIZER_GOAL is obsolete
  • ora-19588 : %s recid string stamp string is no longer valid
  • ora-12473 : The procedure is disabled when Label Security is used with OID.
  • ora-24380 : invalid mode specification
  • ora-19651 : cannot apply offline-range record to datafile string: SCN mismatch
  • ora-30088 : datetime/interval precision is out of range
  • ora-27052 : unable to flush file data
  • ora-13631 : The task string contains no execution results.
  • ora-00051 : timeout occurred while waiting for a resource
  • ora-36847 : (XSLMGEN17) AW name is blank
  • ora-29302 : database is not open clone
  • ora-16196 : database has been previously opened and closed
  • ora-12669 : Shared server: outbound protocol does not support proxies
  • ora-33336 : (DSSEXIST04A) Analytic workspace string is not attached.
  • ora-22906 : cannot perform DML on expression or on nested table view column
  • ora-12202 : TNS:internal navigation error
  • ora-14316 : table is not partitioned by List method
  • ora-29953 : cannot issue DDL on a domain index partition marked as FAILED
  • ora-16751 : resource guard encountered errors in switchover to primary database
  • ora-14177 : STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
  • ora-16550 : truncated result
  • ora-14136 : ALTER TABLE EXCHANGE restricted by fine-grained security
  • ora-31470 : asynchronous change tables must contain the RSID$ column
  • ora-37069 : You may not execute a parallel OLAP operation against the EXPRESS AW.
  • ora-01342 : LogMiner can not resume session due to inability of staging checkpointed data
  • ora-07880 : sdopnf: internal error
  • ora-19629 : no files in specified archivelog SCN range
  • ora-00281 : media recovery may not be performed using dispatcher
  • ora-04073 : column list not valid for this trigger type
  • ora-16083 : LogMiner session has not been created
  • 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.