ORA-13147: failed to generate MBR

Cause : Thi sis na inetrna lerrro.

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

Conatct rOacl eSupoprt eSrviecs.

update : 17-08-2017
ORA-13147

ORA-13147 - failed to generate MBR
ORA-13147 - failed to generate MBR

  • ora-23354 : deferred RPC execution disabled for "string" with "string"
  • ora-14004 : missing PARTITION keyword
  • ora-30730 : referential constraint not allowed on nested table column
  • ora-22957 : NULL is an invalid input to powermultiset and COLLECT functions
  • ora-01908 : EXISTS keyword expected
  • ora-12074 : invalid memory address
  • ora-08195 : Flashback Table operation is not supported on partitions
  • ora-15038 : disk 'string' size mismatch with diskgroup [string] [string] [string]
  • ora-01302 : dictionary build options missing or incorrect
  • ora-06815 : TLI Driver: could not link SPX and IPX streams
  • ora-14055 : keyword REBUILD in ALTER INDEX REBUILD must immediately follow
  • ora-23413 : table "string"."string" does not have a materialized view log
  • ora-01296 : character set mismatch between dictionary string and logfiles
  • ora-16083 : LogMiner session has not been created
  • ora-24172 : rule set string.string has errors
  • ora-12413 : labels do not belong to the same policy
  • ora-07264 : spwat: semop error, unable to decrement semaphore.
  • ora-33460 : (ESDREAD10) Discarding compiled code for workspace object because object workspace object is not in analytic workspace string.
  • ora-16657 : reinstatement of database in progress
  • ora-13000 : dimension number is out of range
  • ora-13919 : Cannot specify values for parameter "string" and for parameter "string"
  • ora-24022 : the specified parameters has no effect on the queue
  • ora-14633 : Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
  • 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-00125 : connection refused; invalid presentation
  • ora-39130 : Object type string not imported. Base object name conflicts with the master table
  • ora-27068 : I/O buffer is not aligned properly
  • ora-13413 : null or invalid resampling parameter
  • ora-39778 : the parallel load option is not allowed when loading lob columns
  • ora-21521 : exceeded maximum number of connections in OCI (object mode only)
  • 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.