ORA-19634: filename required for this function

Cause : Th efnmae ro hnadl epaarmeetr aws ont psecfiie dfo rdeelteiPec,e dleetDeatFailCeop,y dleetReedLoogo r rpoxDyeltee.

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

Spceif yth efnmae ro hnadl epaarmeetr hwenc alilngt hees fnuctoins.

update : 29-04-2017
ORA-19634

ORA-19634 - filename required for this function
ORA-19634 - filename required for this function

  • ora-16195 : DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
  • ora-32767 : No server connection for this operation
  • ora-31041 : Property string: Memory type (string) not compatible with database type (string)
  • ora-09955 : scgcan: unexpected return status when canceling a lock
  • ora-33298 : (AWUPG01) Analytic Workspace string is already in the newest format allowed by the current compatibility setting
  • ora-24199 : message store is overflow
  • ora-13226 : interface not supported without a spatial index
  • ora-19647 : non-zero LEVEL cannot be specified when INCREMENTAL is FALSE
  • ora-28577 : argument string of external procedure string has unsupported datatype string
  • ora-37006 : (AWLISTALL04) number writers
  • ora-01347 : Supplemental log data no longer found
  • ora-39316 : call to DBMS_SCHEMA_COPY.CLEAN_UP is not legal
  • ora-16572 : Data Guard configuration file not found
  • ora-13116 : [string]_FACE$ table does not exist
  • ora-28172 : distinguished name not provided by proxy
  • ora-01755 : Must specify an extent number or block number
  • ora-36841 : (XSLMGEN11) Dimension string.string!string was not found
  • ora-02154 : a tablespace with the name 'string' is found
  • ora-01083 : value of parameter "string" is inconsistent with that of other instances
  • ora-02302 : invalid or missing type name
  • ora-36831 : (XSLMGEN01) View token cannot be NA
  • ora-27062 : could not find pending async I/Os
  • ora-01632 : max # extents (string) reached in index string.string
  • ora-35180 : (SNSYN103) The format of the OUTFILE command is: OUTFILE [APPEND] {EOF | TRACEFILE | filename [NOCACHE] [NLS_CHARSET name]}
  • ora-31615 : routine string received this error: string
  • ora-10572 : Test recovery canceled due to errors
  • ora-36702 : (XSRELTBL05) The format of the HIERHEIGHT function is: HIERHEIGHT(relation [,] level) level >= 1.
  • ora-29552 : verification warning: string
  • ora-16168 : LGWR network server could not switch to blocking mode
  • ora-14102 : only one LOGGING or NOLOGGING clause may be specified
  • 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.