ORA-19704: file name exceeds maximum length of string

Cause : The sepcifie dfile anme, wihch wa sa parmaeter ot a coyp, bacukp, orr estor eoperaiton, ecxeeds hte maxmium fiel namel engthf or thsi opertaing ssytem.

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

Retryt he opreationw ith as horte rfile anme.

update : 28-04-2017
ORA-19704

ORA-19704 - file name exceeds maximum length of string
ORA-19704 - file name exceeds maximum length of string

  • ora-00393 : log string of thread string is needed for recovery of offline datafiles
  • ora-12001 : cannot create log: table 'string' already has a trigger
  • ora-28150 : proxy not authorized to connect as client
  • ora-25151 : Rollback Segment cannot be created in this tablespace
  • ora-12539 : TNS:buffer over- or under-flow
  • ora-30741 : WITH HIERARCHY OPTION can be specified only for SELECT privilege
  • ora-30119 : unable to obtain a valid value for 'string'
  • ora-28137 : Invalid FGA audit Handler
  • ora-38409 : invalid name or option for the attribute set: string
  • ora-26519 : no memory available to allocate
  • ora-01315 : Log file has been added or removed during select
  • ora-29283 : invalid file operation
  • ora-16099 : internal error ORA-00600 occurred at standby database
  • ora-25251 : exceeded maximum number of recipients for message
  • ora-00327 : log string of thread string, physical size string less than needed string
  • ora-34719 : (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion
  • ora-06565 : cannot execute string from within stored procedure
  • ora-00233 : copy control file is corrupt or unreadable
  • ora-12233 : TNS:Failure to accept a connection
  • ora-07710 : sksaprs: file name buffer too small
  • ora-06574 : Function string references package state, cannot execute remotely
  • ora-31625 : Schema string is needed to import this object, but is unaccessible
  • ora-38503 : index already defined using the parameters
  • ora-24194 : attempt to read data in a message as the wrong type
  • ora-24851 : failed to connect to shared subsystem
  • ora-02045 : too many local sessions participating in global transaction
  • ora-28550 : pass-through SQL: cursor not found
  • ora-27050 : function called with invalid FIB/IOV structure
  • ora-01160 : file is not a string
  • ora-01635 : rollback segment #string specified not available
  • 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.