ORA-10266: Trace OSD stack usage

Cause : Porters should implement this to help them debug their stack implementations. It should be used in at least smcstk().

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


update : 17-08-2017

ORA-10266 - Trace OSD stack usage
ORA-10266 - Trace OSD stack usage

  • ora-30186 : '' must be followed by four hexdecimal characters or another ''
  • ora-29502 : NAMED keyword required in CREATE JAVA RESOURCE
  • ora-12466 : default level is greater than the user's maximum
  • ora-14023 : creation of GLOBAL partitioned cluster indices is not supported
  • ora-29973 : Unsupported query or operation during change notification registration
  • ora-31399 : Cannot contact LDAP server string at port number
  • ora-01654 : unable to extend index string.string by string in tablespace string
  • ora-38612 : FI item length cannot exceed half of one database block.
  • ora-13765 : Value "string" is illegal for a result limit.
  • ora-04082 : NEW or OLD references not allowed in table level triggers
  • ora-16041 : Remote File Server fatal error
  • ora-36768 : (XSAGGCNTMOVE06) An aggregation variable and its AGGCOUNT must have the same base dimensions.
  • ora-16071 : dependency archived log file not found string
  • ora-12489 : default label not within clearance range
  • ora-09881 : sstasfre/sstasdel: shmdt error, unable to detach tas read page
  • ora-06538 : statement violates string RESTRICT_REFERENCES pragma
  • ora-02479 : error while translating file name for parallel load
  • ora-01613 : instance string (thread string) only has string logs - at least 2 logs required to enable.
  • ora-24032 : object string exists, index could not be created for queue table string
  • ora-13122 : invalid topo_geometry specified
  • ora-02758 : Allocation of internal array failed
  • ora-39784 : This direct path operation is not allowed while another is in progress
  • ora-32601 : value for retention cannot be provided
  • ora-04044 : procedure, function, package, or type is not allowed here
  • 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-28201 : Not enough privileges to enable application role 'string'
  • ora-06755 : TLI Driver: cannot close transport endpoint
  • ora-02403 : plan table does not have correct format
  • ora-08458 : invalid format parameter
  • ora-30462 : unsupported operator: string
  • 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.