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 : 28-06-2017
ORA-15199

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

  • ora-01525 : error in renaming data files
  • ora-19700 : device type exceeds maximum length of string
  • ora-12438 : repeated policy option: string
  • ora-32814 : propagation schedule string does not exist
  • ora-31529 : could not find publication for CDC subscriber view string.string
  • ora-16169 : LGWR network server invalid parameters
  • ora-23533 : object "string"."string" can not be cached
  • ora-12033 : cannot use filter columns from materialized view log on "string"."string"
  • ora-31017 : Error generating unique OID for XML document
  • ora-29805 : missing COLUMN keyword
  • ora-00001 : unique constraint (string.string) violated
  • ora-19575 : expected string blocks in file string, found string
  • ora-22634 : Error adding new instance to AnyDataSet
  • ora-36975 : (XSRELTBL15) You must specify a USING clause naming a relation with same level dimension as LEVELORDER valueset workspace object.
  • ora-30452 : cannot compute AVG(X), VARIANCE(X) or STDDEV(X), without COUNT(X) or SUM(X)
  • ora-14308 : partition bound element must be one of: string, datetime or interval literal, number, or NULL
  • ora-01550 : cannot drop system tablespace
  • ora-33336 : (DSSEXIST04A) Analytic workspace string is not attached.
  • ora-16163 : LGWR network server host attach error
  • ora-27203 : skgfpqb: sbtpcquerybackup returned error
  • ora-25218 : enqueue failed, delay must be zero for queue string.string
  • ora-24795 : Illegal string attempt made
  • ora-09853 : snyRemovePort: bad return code from request.
  • ora-07390 : sftopn: translate error, unable to translate file name.
  • ora-00567 : Requested processor group string is too large (maximum string)
  • ora-22304 : input type is not an object type
  • ora-09812 : Unable to get user clearance from connection
  • ora-30970 : option not supported for XML Index
  • ora-36800 : (XSTBLFUNC00) The OLAP_TABLE function can only have a single LOOP statement within the LIMITMAP
  • ora-16036 : invalid MANAGED recovery CANCEL option
  • 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.