ORA-09293: sksasmo: unable to send message to console

Cause : An error was returned while attempting to send a message to the console operator

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

See OSD error accompanying this message

update : 18-08-2017
ORA-09293

ORA-09293 - sksasmo: unable to send message to console
ORA-09293 - sksasmo: unable to send message to console

  • ora-19288 : XP0017 - invalid number of arguments to function - string
  • ora-28292 : No Domain Policy registered for Kerberos based authentication
  • ora-10262 : Don't check for memory leaks
  • ora-36996 : (XSRELGID13) Valueset workspace object should be defined over dimension workspace object.
  • ora-01594 : attempt to wrap into rollback segment (string) extent (string) which is being freed
  • ora-02141 : invalid OFFLINE option
  • ora-32634 : automatic order MODEL evaluation does not converge
  • ora-29894 : base or varray datatype does not exist
  • ora-14630 : subpartition resides in offlined tablespace
  • ora-07250 : spcre: semget error, unable to get first semaphore set.
  • ora-27070 : async read/write failed
  • ora-32830 : result code string returned by Messaging Gateway agent
  • ora-14304 : List partitioning method expects a single partitioning column
  • ora-13137 : failed to generate tablespace sequence number
  • ora-16790 : the value of the configurable property is invalid
  • ora-23376 : node string is not compatible with replication version "string"
  • ora-02256 : number of referencing columns must match referenced columns
  • ora-19003 : Missing XML root element name
  • ora-37023 : (XSMLTUPD01) Object workspace object cannot be updated without dimension workspace object.
  • ora-00115 : connection refused; dispatcher connection table is full
  • ora-19260 : XQ0040 - invalid namespace node in element constructor
  • ora-16222 : automatic Logical Standby retry of last action
  • ora-19202 : Error occurred in XML processingstring
  • ora-32337 : cannot alter materialized view with pending changes refresh on commit
  • ora-24014 : invalid value string, RETENTION_TIME should be FOREVER or non-negative
  • ora-10587 : Invalid count for ALLOW n CORRUPTION option
  • ora-19634 : filename required for this function
  • ora-17501 : logical block size string is invalid
  • ora-28536 : error in processing Heterogeneous Services initialization parameters
  • ora-02216 : tablespace name expected
  • 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.