ORA-25531: MTTR specified is too small: string

Cause : The current FAST_START_MTTR_TARGET setting or a candidate MTTR setting is too small for MTTR advisory.

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

Set a larger FAST_START_MTTR_TARGET or candidate MTTR.

update : 24-07-2017
ORA-25531

ORA-25531 - MTTR specified is too small: string
ORA-25531 - MTTR specified is too small: string

  • ora-01667 : cannot add any more tablespaces: limit of string exceeded
  • ora-28664 : a partitioned table may not be coalesced as a whole
  • ora-28275 : Multiple mappings for user nickname to LDAP distinguished name exist.
  • ora-13509 : error encountered during updates to a AWR table
  • ora-25156 : old style outer join (+) cannot be used with ANSI joins
  • ora-19225 : XP0005 - XQuery static type error: expected non empty type got empty sequence
  • ora-29322 : SCN string size too long -- maximum size 58 bytes/characters
  • ora-40306 : wide data not supported for decision tree model create
  • ora-14123 : duplicate NOREVERSE clause
  • ora-30087 : Adding two datetime values is not allowed
  • ora-37038 : (XSMLTDCL04) You cannot change definitions of objects in analytic workspace string because it is attached in MULTI mode.
  • ora-24780 : cannot recover a transaction while in an existing transaction
  • ora-15042 : ASM disk "string" is missing
  • ora-39709 : incomplete component downgrade; string downgrade aborted
  • ora-02209 : invalid MAXTRANS option value
  • ora-13024 : polygon has less than three segments
  • ora-30959 : The indexed column is not stored in CLOB.
  • ora-38441 : System could not derive the list of STORED and INDEXED attributes.
  • ora-27030 : skgfwrt: sbtwrite2 returned error
  • ora-23452 : flavor string of object group "string"."string" is already published
  • ora-19015 : Invalid XML tag identifier (string)
  • ora-30339 : illegal dimension attribute name
  • ora-21602 : operation does not support the specified typecode
  • ora-10615 : Invalid tablespace type for temporary tablespace
  • ora-12853 : insufficient memory for PX buffers: current stringK, max needed stringK
  • ora-01906 : BACKUP keyword expected
  • ora-21525 : attribute number or (collection element at index) string violated its constraints
  • ora-32401 : materialized view log on "string"."string" does not have new values
  • ora-16818 : Fast-Start Failover suspended
  • ora-22970 : name does not correspond to an object view
  • 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.