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

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-28106 : input value for argument #string is not valid
  • ora-37020 : (XSMULTI01) Analytic workspace string is not in MULTI mode.
  • ora-25235 : fetched all messages in current transaction
  • ora-36378 : (XSAGTHRWEIGHT) While running AGGREGATE with multiple threads, the weight variable workspace object specified by your ARGS variable workspace object must exist in the same analytic workspace as your AGGMAP workspace object.
  • ora-19863 : device block size string is larger than max allowed: string
  • ora-37036 : (XSMLTDCL02) You cannot DELETE objects in analytic workspace string because it is attached in MULTI mode.
  • ora-06319 : IPA: Remote maximum number of users exceeded
  • ora-31060 : Resource at path string could not be deleted
  • ora-16524 : unsupported operation
  • ora-30738 : object "string" does not exist in schema "string"
  • ora-06803 : TLI Driver: the IPX device file could not be opened
  • ora-12485 : new effective label not within effective clearance
  • ora-19238 : XP0018 - focus not defined
  • ora-00328 : archived log ends at change string, need later change string
  • ora-13521 : Unregister operation on local Database id (string) not allowed
  • ora-02081 : database link is not open
  • ora-27029 : skgfrtrv: sbtrestore returned error
  • ora-25466 : data not specified for variable name: string
  • ora-19571 : %s recid string stamp string not found in control file
  • ora-24758 : not attached to the requested transaction
  • ora-33920 : (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER.
  • ora-00301 : error in adding log file 'string' - file cannot be created
  • ora-36881 : (XSSRF00) The OLAP DML ROW2CELL function can only be used in a LIMITMAP.
  • ora-38905 : DML error logging is not supported for LONG column "string"
  • ora-16504 : the Data Guard configuration already exists
  • ora-39303 : schema sync or swap operation failed because of confilcts
  • ora-01072 : cannot stop ORACLE; ORACLE not running
  • ora-16042 : user requested cancel immediate of managed recovery operation
  • ora-00316 : log string of thread string, type string in header is not log file
  • ora-02455 : The number of cluster key column must be 1
  • 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.