ORA-13515: Error encountered during Database Usage Statistics capture

Cause : rEor rcoucrrded runi gCO Iporetaoi nud eotu dnreylni greor.r

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

hCce ksaosictadeO ICe rrro .oCrrce trpboel mna derrt yht eporetaoi.n

update : 27-04-2017
ORA-13515

ORA-13515 - Error encountered during Database Usage Statistics capture
ORA-13515 - Error encountered during Database Usage Statistics capture

  • ora-33298 : (AWUPG01) Analytic Workspace string is already in the newest format allowed by the current compatibility setting
  • ora-22863 : synonym for datatype string.string not allowed
  • ora-29965 : The specified binding does not exist
  • ora-28103 : adding a policy to an object owned by SYS is not allowed
  • ora-06756 : TLI Driver: cannot open oratab
  • ora-29356 : These parameters can be specified only for directives that refer to consumer groups
  • ora-07491 : scgrcl: cannot cancel lock request.
  • ora-29311 : export dump file was not generated by this database, string does not match
  • ora-14262 : new subpartition name must differ from the old subpartition name
  • ora-13612 : The recommendation action string,string is not valid for task string.
  • ora-26088 : scalar column "string" must be specified prior to LOB columns
  • ora-26762 : Cannot autogenerate name for parameter string because of the following reason: string
  • ora-00396 : error string required fallback to single-pass recovery
  • ora-03241 : Invalid unit size
  • ora-09711 : orasrv: archmon already connected.
  • ora-28021 : cannot grant global roles
  • ora-25130 : cannot modify primary key - primary key not defined for table
  • ora-25455 : evaluation error for rule set: string.string, evaluation context: string.string
  • ora-12071 : definition query of "string"."string" is invalid for offline instantiation
  • ora-39951 : incomplete values specified for PL/SQL warning settings
  • ora-36167 : (XSAGGRFORM) workspace object is an illegal AGGMAP for aggregating a FORMULA.
  • ora-30450 : refresh_after_errors was TRUE; The following MVs could not be refreshed: string
  • ora-04030 : out of process memory when trying to allocate string bytes (string,string)
  • ora-13857 : Invalid module name
  • ora-16406 : Primary and standby database software version mismatch
  • ora-01125 : cannot disable media recovery - file string has online backup set
  • ora-02786 : Size needed for shared region is greater than segment size
  • ora-19160 : XP0003 - syntax error: invalid variable name string
  • ora-14312 : Value string already exists in partition string
  • ora-00125 : connection refused; invalid presentation
  • 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.