ORA-13514: Metric Capture too close to last capture, group string

Cause : The metric capture cannot be executed because it is too close to the last capture (within 1 centi-second).

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

add some delay and reissue command to retry.

update : 30-04-2017
ORA-13514

ORA-13514 - Metric Capture too close to last capture, group string
ORA-13514 - Metric Capture too close to last capture, group string

  • ora-01558 : out of transaction ID's in rollback segment string
  • ora-06433 : ssaio: LSEEK error, unable to seek to requested block.
  • ora-19265 : XQ0045 - invalid or unknown prefix string in function declaration
  • ora-13117 : [string]_RELATION$ table does not exist
  • ora-36679 : (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object.
  • ora-01189 : file is from a different RESETLOGS than previous files
  • ora-06436 : ssaio: asynchronous I/O failed due to incorrect parameters.
  • ora-14124 : duplicate REVERSE clause
  • ora-08206 : ora_addr: cannot translate address file name
  • ora-08008 : another instance is mounted with USE_ROW_ENQUEUES = string
  • ora-13187 : subdivision failed
  • ora-30573 : AUTO segment space management not valid for this type of tablespace
  • ora-12224 : TNS:no listener
  • ora-00277 : illegal option to the UNTIL recovery flag string
  • ora-16700 : the standby database has diverged from the primary database
  • ora-33302 : (DBVALID01) SEVERE ERROR: Record number multiply used.
  • ora-32589 : unable to drop minimal supplemental logging
  • ora-12068 : updatable mview log for mview "string"."string" does not exist
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-01564 : rollback segment is not PUBLIC
  • ora-02068 : following severe error from stringstring
  • ora-25204 : invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP
  • ora-06562 : type of out argument must match type of column or bind variable
  • ora-01634 : rollback segment number 'string' is about to go offline
  • ora-02837 : Unable to unlink temporary file
  • ora-00983 : cannot audit or noaudit SYS user actions
  • ora-21701 : attempt to flush objects to different servers
  • ora-13000 : dimension number is out of range
  • ora-08320 : scnget: Call to scnget before scnset or scnfnd.
  • ora-06022 : NETASY: channel open failure
  • 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.