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 : 20-09-2017
ORA-25531

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

  • ora-12048 : error encountered while refreshing materialized view "string"."string"
  • ora-33998 : (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.
  • ora-24437 : OCIStmtExecute called before OCIStmtPrepare2.
  • ora-06021 : NETASY: connect failed
  • ora-35018 : (QFCHECK01) The analytic workspace and EIF file definitions of workspace object have a mismatched data type.
  • ora-10361 : check buffer change vector count consistency
  • ora-07209 : sfofi: file size limit was exceeded.
  • ora-29834 : REF datatype not supported with operators
  • ora-24037 : schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE
  • ora-32301 : object-relational materialized views must be primary key based
  • ora-33282 : (DBERR11) Cannot wait for analytic workspace string to become available since doing so would cause a deadlock.
  • ora-10588 : Can only allow 1 corruption for normal media/standby recovery
  • ora-39310 : call to DBMS_SCHEMA_COPY.CLEAN_FAILED_CLONE is not legal
  • ora-28107 : policy was disabled
  • ora-27086 : unable to lock file - already in use
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-25312 : Cannot specify nonzero sender protocol
  • ora-29874 : warning in the execution of ODCIINDEXALTER routine
  • ora-14308 : partition bound element must be one of: string, datetime or interval literal, number, or NULL
  • ora-23437 : template authorization already exists for user
  • ora-07709 : sksaprs: archiving to a remote host is not allowed
  • ora-16238 : attempt to use version 9 log
  • ora-07564 : sldext: wildcard in filename or extension
  • ora-14190 : only one ENABLE/DISABLE ROW MOVEMENT clause can be specified
  • ora-25234 : NEXT_TRANSACTION navigation option invalid for queue table string.string
  • ora-38486 : FUNCTION/PACKAGE/TYPE already exists for the attribute set
  • ora-12495 : cannot disable an enabled level, category, or release category
  • ora-24339 : cannot set server group name after connecting to server
  • ora-32342 : The EXPLAIN_MVIEW facility failed to explain the materialized view statement
  • ora-26053 : Row was not loaded due to conversion error.
  • 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.