ORA-15199: Internal ASM tracing event number 15199

Cause : Set this event only under the supervision of Oracle development.

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

Traces execution of ASM. Level indicates verbosity of tracing.

update : 17-08-2017

ORA-15199 - Internal ASM tracing event number 15199
ORA-15199 - Internal ASM tracing event number 15199

  • ora-06905 : CMX: connect error
  • ora-27039 : create file failed, file size limit reached
  • ora-25353 : branch marked for deletion
  • ora-01542 : tablespace 'string' is offline, cannot allocate space in it
  • ora-27412 : repeat interval or calendar contains invalid identifier: string
  • ora-38472 : VARCHAR representation of the data item is too long.
  • ora-13756 : Cannot update attribute "string".
  • ora-27473 : argument string does not exist
  • ora-02090 : network error: attempted callback+passthru
  • ora-30038 : Cannot perform parallel insert on non-partitioned object
  • ora-07600 : slkmnm: $GETSYIW failure
  • ora-06926 : CMX: T_ERROR during read data
  • ora-03222 : average row size and row count must be greater than zero
  • ora-39952 : only numbers can be specified as range values
  • ora-02399 : exceeded maximum connect time, you are being logged off
  • ora-00090 : failed to allocate memory for cluster database ORADEBUG command
  • ora-29930 : COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause
  • ora-08310 : sllfop: Bad value for recsize
  • ora-36400 : (XSSPROP02) workspace object is not a valid variable name.
  • ora-32575 : Explicit column default is not supported for modifying views
  • ora-39147 : cannot migrate Data Pump queue table ownership to this instance
  • ora-31023 : Index size error
  • ora-10902 : disable seghdr conversion for ro operation
  • ora-31070 : Invalid database user ID string
  • ora-25216 : invalid recipient, either NAME or ADDRESS must be specified
  • ora-29703 : error occurred in global enqueue service operation
  • ora-02360 : fatal error during data export/import initialization
  • ora-30555 : global index partitioning key is an expression
  • ora-30066 : test support - drop rollback segment wait
  • ora-23377 : bad name string for missing_rows_oname1 argument
  • 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.