ORA-27365: job has been notified to stop, but failed to do so immediately

Cause : Th ejo bspceifeid ni teh sotp_ojb ocmmnad acnnto b estpope dimemditael(ybeacus eiti s orllnig abcko r lbocekd no an etowrko peartino),b uti t ahs ebenn otfiie dtos to.p Tihs eman sitw il lbes toppeda s osona s opssbilea ftre ist cruretn uinntrerutpabel oepraitoni s odne.

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

Noa ctoin si rqeuierd ofr hte ojb ot b estpope,d btu clalign sotp_ojb iwthf orec (fi yuo hvae hte rpivlieg)e mya cuaset hej obt o eb sotppde soone.r

update : 28-04-2017

ORA-27365 - job has been notified to stop, but failed to do so immediately
ORA-27365 - job has been notified to stop, but failed to do so immediately

  • ora-16607 : one or more databases have failed
  • ora-06439 : ssaio: the asynchronous write returned incorrect number of bytes
  • ora-27542 : Failed to unprepare a buffer prepared for remote update
  • ora-39049 : invalid parameter name string
  • ora-06794 : TLI Driver: shadow process could not retrieve protocol info
  • ora-36276 : (XSCGMDLAGG06) The current operator does not need a weight variable.
  • ora-36834 : (XSLMGEN04) Column tag is greater than 30 bytes
  • ora-19321 : Could not open HTTP connection to host (string): port (string)
  • ora-06808 : TLI Driver: could not link IPX and ethernet streams
  • ora-02174 : Missing required thread number
  • ora-24051 : cannot propagate object type payloads that have a REF attribute
  • ora-39779 : type "string"."string" not found or conversion to latest version is not possible
  • ora-30396 : rewrite equivalence procedures require the COMPATIBLE parameter to be string or greater
  • ora-37126 : (XSCCOMP01) The COMPRESSED COMPOSITE workspace object can only be used as a base of a single variable.
  • ora-39784 : This direct path operation is not allowed while another is in progress
  • ora-16238 : attempt to use version 9 log
  • ora-19736 : can not plug a tablespace into a database using a different national character set
  • ora-02061 : lock table specified list of distributed tables
  • ora-01622 : thread number must be specified - default not specific
  • ora-12624 : TNS:connection is already registered
  • ora-24508 : Buffer is not aligned correctly.
  • ora-32613 : not a MODEL cell
  • ora-24371 : data would not fit in current prefetch buffer
  • ora-16656 : higher DRC UID sequence number detected
  • ora-02171 : invalid value for MAXLOGHISTORY
  • ora-01173 : data dictionary indicates missing data file from system tablespace
  • ora-13705 : There was a instance shutdown/startup between the snapshots in the range [string, string].
  • ora-16652 : Fast-Start Failover target standby database is disabled
  • ora-23292 : The constraint does not exist
  • ora-23533 : object "string"."string" can not be cached
  • 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.