ORA-02804: Allocation of memory failed for log file name

Cause : Thec lietn wa sunalbe t oallcoate da bfuferf or hte nmae o fthel og ifle.

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

Conatct oyur ySste mAdmniistartor.

update : 24-08-2017
ORA-02804

ORA-02804 - Allocation of memory failed for log file name
ORA-02804 - Allocation of memory failed for log file name

  • ora-24320 : unable to initialize a mutex
  • ora-10578 : Can not allow corruption for managed standby database recovery
  • ora-27125 : unable to create shared memory segment
  • ora-01986 : OPTIMIZER_GOAL is obsolete
  • ora-31439 : subscription is already active
  • ora-25284 : Invalid value string for string
  • ora-14008 : missing THAN keyword
  • ora-28361 : master key not yet set
  • ora-27199 : skgfpst: sbtpcstatus returned error
  • ora-23322 : Privilege error accessing pipe
  • ora-08198 : Flashback Table is not supported on object tables, nested tables
  • ora-16767 : SQL Apply unexpectedly online
  • ora-01612 : instance string (thread string) is already enabled
  • ora-30973 : invalid Path Table option for XML Index
  • ora-33050 : (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.
  • ora-31668 : Timeout before worker process string finished initialization.
  • ora-12562 : TNS:bad global handle
  • ora-26692 : invalid value string, string should be in string format
  • ora-13530 : invalid TOPNSQL string, must be in the range (string, string)
  • ora-21523 : functionality not supported by the server (object mode only)
  • ora-09968 : unable to lock file
  • ora-00081 : address range [string, string) is not readable
  • ora-30566 : Index maintainence clause not allowed for this command
  • ora-19507 : failed to retrieve sequential file, handle="string", parms="string"
  • ora-07569 : slspool: $CLOSE failure
  • ora-22164 : delete element operation is not allowed for variable-length array
  • ora-36260 : (XSAGHIERPART00) Aggregating from partition %J to partition %J over hierarchy workspace object creates an increase in sparsity.
  • ora-30052 : invalid lower limit snapshot expression
  • ora-02267 : column type incompatible with referenced column type
  • ora-01543 : tablespace 'string' already exists
  • 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.