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-09-2017

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

  • ora-28107 : policy was disabled
  • ora-19237 : XP0017 - unable to resolve call to function - string:string
  • ora-29661 : Unable to find the superclass of the defined in the EXTERNAL NAME
  • ora-35021 : (QFCHECK08) The EIF file definition of workspace object has some partitions that are not present in the existing Analytic Workspace object.
  • ora-16607 : one or more databases have failed
  • ora-00288 : to continue recovery type ALTER DATABASE RECOVER CONTINUE
  • ora-27451 : %s cannot be NULL
  • ora-07581 : spstp: cannot derive SID from unexpected process name
  • ora-29287 : invalid maximum line size
  • ora-22063 : reading negative value [string] as unsigned
  • ora-13521 : Unregister operation on local Database id (string) not allowed
  • ora-29356 : These parameters can be specified only for directives that refer to consumer groups
  • ora-29252 : collection does not contain elements at index locations in call to dbms_sql.bind_array
  • ora-24004 : invalid column name string in SORT_LIST, should be ENQ_TIME or PRIORITY
  • ora-07232 : slemcc: fclose error.
  • ora-10563 : Test recovery had to corrupt data block (file# string, block# string) in order to proceed
  • ora-22060 : argument [string] is an invalid or uninitialized number
  • ora-31190 : Resource string is not a version-controlled resource
  • ora-22631 : attribute [string] is is not well-formed or does not match the type
  • ora-37139 : (XSCCOMP14) Cannot AGGREGATE workspace object using AGGMAP workspace object because you can not AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a PROTECT clause.
  • ora-23422 : Oracle Server could not generate an unused job number
  • ora-28120 : driving context already exists
  • ora-06540 : PL/SQL: compilation error
  • ora-30359 : Query rewrite is not supported on SYS materialized views
  • ora-12911 : permanent tablespace cannot be temporary tablespace
  • ora-31659 : status message was invalid type - detaching job
  • ora-32050 : %s operation failed
  • ora-09812 : Unable to get user clearance from connection
  • ora-08414 : error encountered in string
  • ora-13124 : unable to determine column id for column string
  • 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.