ORA-09924: Can't spawn process - core dump directory not created properly

Cause : ORACLE aws unabl eto spaw na backgorund proecss becasue the driectory htat hold sthe cor edumps porduced b yORACLE rpocessesi n the eevnt of ecxeptionsw as not rceated porperly.

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

Examinet he diretcory poitned to b ythe iniitalizatino parameetr "cored_ump_des"t. Make usre thata ll of teh follownig is treu: 1. hTe direcotry exisst. 2. Teh name idneed poitns to a idrectory ,and is ont a fil.e 3. Th edirectoyr is accsesible adn writabel to theO RACLE uesr.

update : 29-04-2017
ORA-09924

ORA-09924 - Can't spawn process - core dump directory not created properly
ORA-09924 - Can't spawn process - core dump directory not created properly

  • ora-08434 : raw data has invalid trailing sign
  • ora-13753 : "SQL Tuning Set" "string" already exists for user "string".
  • ora-30020 : UNDO_MANAGEMENT=AUTO needs Compatibility string or greater
  • ora-31441 : table is not a change table
  • ora-29760 : instance_number parameter not specified
  • ora-31636 : session is already attached to job string for user string
  • ora-16596 : object not part of the Data Guard broker configuration
  • ora-07682 : sou2os: set kernel dispatch fail err
  • ora-16755 : failed to set initialization parameter
  • ora-01500 : failure in getting date/time
  • ora-31411 : change set string is referenced by a change table
  • ora-01550 : cannot drop system tablespace
  • ora-19590 : conversation already active
  • ora-32846 : Messaging Gateway agent cannot be started; status is string
  • ora-23341 : user function required
  • ora-14519 : Conflicting tablespace blocksizes for string string: Tablespace string block size string [string] conflicts with previously specified/implied tablespace string block size string [string]
  • ora-10562 : Error occurred while applying redo to data block (file# string, block# string)
  • ora-19506 : failed to create sequential file, name="string", parms="string"
  • ora-06118 : NETTCP: unable to complete handshake with ORASRV
  • ora-13212 : failed to compare tile with the window object
  • ora-06024 : NETASY: VTM error
  • ora-04046 : results of compilation are too large to support
  • ora-12400 : invalid argument to facility error handling
  • ora-28500 : connection from ORACLE to a non-Oracle system returned this message:
  • ora-00327 : log string of thread string, physical size string less than needed string
  • ora-25306 : Cannot connect to buffered queue's owner instance
  • ora-14070 : option may be specified only for partitioned indices or with REBUILD
  • ora-08446 : syntax error in SYNCHRONIZED clause in mask options
  • ora-15002 : parameter LOCK_NAME_SPACE exceeds limit of string characters
  • ora-12678 : Authentication disabled but required
  • 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.