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 : 19-08-2017
ORA-25531

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

  • ora-02450 : Invalid hash option - missing keyword IS
  • ora-30359 : Query rewrite is not supported on SYS materialized views
  • ora-13831 : SQL profile name specified is invalid
  • ora-29392 : cpu parameters for level string for plan string must be zero
  • ora-02448 : constraint does not exist
  • ora-00331 : log version string incompatible with ORACLE version string
  • ora-01466 : unable to read data - table definition has changed
  • ora-00309 : log belongs to wrong database
  • ora-07404 : sfareq: Timeout occurred waiting for request to complete.
  • ora-16737 : the redo transport service for standby database "string" has an error
  • ora-16659 : failover operation in progress
  • ora-31505 : cannot alter or drop predefined change set
  • ora-10580 : Can not modify datafile header during test recovery
  • ora-01025 : UPI parameter out of range
  • ora-29274 : fixed-width multibyte character set not allowed for a URL
  • ora-09283 : sllfsk: error skipping records
  • ora-19615 : some files not found in backup set
  • ora-01177 : data file does not match dictionary - probably old incarnation
  • ora-24017 : cannot enable enqueue on QUEUE, string is an exception queue
  • ora-24014 : invalid value string, RETENTION_TIME should be FOREVER or non-negative
  • ora-19740 : text is longer than string
  • ora-23386 : replication parallel push cannot create slave processes
  • ora-24905 : invalid recepient protocol attribute passed into OCI call
  • ora-24803 : illegal parameter value in lob read function
  • ora-01140 : cannot end online backup - all files are offline or readonly
  • ora-31610 : cannot call this function from a non-master process
  • ora-12830 : Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
  • ora-02714 : osnpwr: message send failure
  • ora-01342 : LogMiner can not resume session due to inability of staging checkpointed data
  • ora-16206 : database already configured as Logical Standby database
  • 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.