ORA-07261: spdde: kill error, unable to send signal to process.

Cause : Kill system call returned an error. Possibly an attempt to destroy an already gone process.

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

Check errno.

update : 22-08-2017

ORA-07261 - spdde: kill error, unable to send signal to process.
ORA-07261 - spdde: kill error, unable to send signal to process.

  • ora-21521 : exceeded maximum number of connections in OCI (object mode only)
  • ora-39204 : No subsetting of tablespaces is allowed for transportable import.
  • ora-22306 : type "string"."string" already exists
  • ora-24804 : Lob read/write functions called while another OCI LOB read/write streaming is in progress
  • ora-36642 : (XSDUNION06) Concat dimension list contains duplicate leaf dimension workspace object.
  • ora-00228 : length of alternate control file name exceeds maximum of string
  • ora-16956 : Only SELECT or DML statements are supported for test execute.
  • ora-12545 : Connect failed because target host or object does not exist
  • ora-16737 : the redo transport service for standby database "string" has an error
  • ora-01234 : cannot end backup of file string - file is in use or recovery
  • ora-34001 : (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension.
  • ora-16792 : configuration property value is inconsistent with database setting
  • ora-27373 : unknown or illegal event source queue
  • ora-14615 : List value 'string' specified twice in subpartitions 'string', 'string'
  • ora-24008 : queue table string.string must be dropped first
  • ora-31100 : XDB Locking Internal Error
  • ora-01129 : user's default or temporary tablespace does not exist
  • ora-13128 : current tiling level exceeds user specified tiling level
  • ora-39203 : Partition selection is not supported over a network link.
  • ora-27502 : IPC error deleting OSD context
  • ora-38410 : schema extension not allowed for the table name
  • ora-30179 : invalid argument index used in a format code
  • ora-15152 : cluster in rolling upgrade
  • ora-19564 : error occurred writing string bytes at block number string
  • ora-19251 : XQ0031 - unsupported query version
  • ora-04935 : unable to get/convert SCN recovery lock
  • ora-12200 : TNS:could not allocate memory
  • ora-19557 : device error, device type: string, device name: string
  • ora-31431 : all source tables must belong to the synchronous change set
  • ora-39202 : Data cannot be filtered or selected in string jobs.
  • 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.