ORA-25532: MTTR specified is too large: string

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

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

Set a smaller FAST_START_MTTR_TARGET or candidate MTTR.

update : 24-07-2017
ORA-25532

ORA-25532 - MTTR specified is too large: string
ORA-25532 - MTTR specified is too large: string

  • ora-12844 : cluster reconfiguration in progress
  • ora-01207 : file is more recent than control file - old control file
  • ora-22140 : given size [string] must be in the range of 0 to [string]
  • ora-02061 : lock table specified list of distributed tables
  • ora-01561 : failed to remove all objects in the tablespace specified
  • ora-15153 : cluster not in rolling upgrade
  • ora-36673 : (XSDPART11) Use simple leaf values to identify concat dimension values in a VALUES LESS THAN clause, rather than the format.
  • ora-22808 : REF dereferencing not allowed
  • ora-13065 : cannot delete a child layer with a parent layer
  • ora-31442 : operation timed out while acquiring lock on string
  • ora-06744 : TLI Driver: listener cannot bind
  • ora-14552 : cannot perform a DDL, commit or rollback inside a query or DML
  • ora-21612 : key is already being used
  • ora-40101 : Data Mining System Error string-string-string
  • ora-06735 : TLI Driver: client failed to close error conn
  • ora-12404 : invalid privilege string: string
  • ora-16704 : cannot modify a read-only property
  • ora-12226 : TNS:operating system resource quota exceeded
  • ora-28605 : bitmap indexes cannot be reversed
  • ora-09978 : skxfqhdel: Error Disconnecting from another endpoint.
  • ora-12221 : TNS:illegal ADDRESS parameters
  • ora-00269 : specified log file is part of thread string not string
  • ora-07803 : slpdtb: invalid packed decimal nibble
  • ora-39044 : Metadata transform string has already been specified.
  • ora-19283 : XQ0031 - It is a static error if the version number specified in a version declaration is not supported by the implementation.
  • ora-00400 : invalid release value string for parameter string
  • ora-14110 : partitioning column may not be of type ROWID
  • ora-08268 : create_ora_addr: cannot close nameserver
  • ora-36960 : (XSFCAST27) The value of the string expression must be an odd number. You specified number.
  • ora-36618 : (XSAGMODDIM00) workspace object is not a valid model for AGGMAP ADD.
  • 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.