ORA-27036: translation error, unable to expand file name

Cause : additional information indicates sltln/slnrm error, and also indicates which function encountered the error

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

check additional information

update : 26-04-2017
ORA-27036

ORA-27036 - translation error, unable to expand file name
ORA-27036 - translation error, unable to expand file name

  • ora-23349 : cannot generate replication support for functions
  • ora-07476 : slsget: cannot get mapped memory statistics.
  • ora-02294 : cannot enable (string.string) - constraint changed during validation
  • ora-14523 : Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]
  • ora-01209 : data file is from before the last RESETLOGS
  • ora-12401 : invalid label string: string
  • ora-12492 : DBLOW cannot be changed
  • ora-23417 : unknown materialized view type: string
  • ora-07473 : snclrd: read error when trying to read sgadef.dbf file.
  • ora-33010 : (XSAGDNGL04) Relation workspace object is duplicated in the AGGMAP workspace object.
  • ora-29515 : exit called from Java code with status string
  • ora-01523 : cannot rename data file to 'string' - file already part of database
  • ora-38414 : invalid datatype for the attribute string
  • ora-27203 : skgfpqb: sbtpcquerybackup returned error
  • ora-16805 : change of LogXptMode property violates overall protection mode
  • ora-23430 : argument "string" cannot be NULL or empty string
  • ora-13910 : Parameter string cannot be NULL.
  • ora-22608 : cannot add an attribute to the already generated image handle
  • ora-37185 : length of string (string) exceeds maximum (string)
  • ora-01342 : LogMiner can not resume session due to inability of staging checkpointed data
  • ora-24774 : cannot switch to specified transaction
  • ora-16660 : FSFO operation attempted in absence of a broker configuration
  • ora-19224 : XP0004 - XQuery static type mismatch: expected - string got - string
  • ora-13138 : could not determine name of object string
  • ora-01255 : cannot shutdown - file string in recovery manager backup
  • ora-13863 : Statistics aggregation for service(module/action) string is not enabled
  • ora-01913 : EXCLUSIVE keyword expected
  • ora-28561 : unable to set date format on non-Oracle system
  • ora-23337 : priority or value not in priority group string
  • ora-12029 : LOB columns may not be used as filter columns
  • 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.