ORA-09923: Can't spawn process - user log directory not created properly

Cause : ORACLE was unable to spawn a background process because the directory that holds the trace files of the dedicated server processes was not created properly.

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

Examine the directory pointed to by the initialization parameter "user_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

update : 27-05-2017
ORA-09923

ORA-09923 - Can't spawn process - user log directory not created properly
ORA-09923 - Can't spawn process - user log directory not created properly

  • ora-16124 : transaction string string string is waiting on another transaction
  • ora-33068 : (XSAGDNGL33) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must specify a positive dimension offset.
  • ora-19550 : cannot use backup/restore functions while using dispatcher
  • ora-15030 : diskgroup name "string" is in use by another diskgroup
  • ora-37135 : (XSCCOMP10) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. The RELATION statement for dense dimension workspace object must precede RELATION statements over the bases of the COMPRESSED COMPOSITE.
  • ora-12070 : cannot offline instantiate materialized view "string"."string"
  • ora-26530 : unable to build materialized view refresh control list
  • ora-29701 : unable to connect to Cluster Manager
  • ora-29275 : partial multibyte character
  • ora-30034 : Undo tablespace cannot be specified as temporary tablespace
  • ora-06579 : Bind variable not big enough to hold the output value
  • ora-34019 : (MSCGADD03) workspace object is not a LIST PARTITION TEMPLATE.
  • ora-25503 : cannot open database because the database is being quiesced
  • ora-12544 : TNS:contexts have different wait/test functions
  • ora-01147 : SYSTEM tablespace file string is offline
  • ora-02425 : create table failed
  • ora-14160 : this physical attribute may not be specified for a table subpartition
  • ora-09873 : TASDEF_OPEN: open error when opening tasdef@.dbf file.
  • ora-38782 : cannot flashback database to non-guaranteed restore point 'string'
  • ora-13431 : GeoRaster metadata rasterType error
  • ora-23405 : refresh group number string does not exist
  • ora-13227 : SDO_LEVEL values for the two index tables do not match
  • ora-16650 : command incompatible when Fast-Start Failover is enabled
  • ora-04093 : references to columns of type LONG are not allowed in triggers
  • ora-19020 : invalid dereference of XMLType columns
  • ora-25245 : agent name cannot be specified if address is a single-consumer queue or an exception queue
  • ora-24168 : rule string.string cannot have default evaluation context
  • ora-29959 : error in the execution of the string routine for one or more of the index partitions
  • ora-16202 : Skip procedure requested to replace statement
  • ora-39175 : Encryption password is not needed.
  • 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.