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 : 20-08-2017

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

  • ora-19557 : device error, device type: string, device name: string
  • ora-00349 : failure obtaining block size for 'string'
  • ora-16045 : circular archive log destination dependency chain
  • ora-13226 : interface not supported without a spatial index
  • ora-22972 : NULL value not allowed in PRIMARY KEY-based object identifier
  • ora-00825 : cannot set db_block_buffers if sga_target set
  • ora-19924 : there are no row with id string
  • ora-30046 : Undo tablespace string not found in control file.
  • ora-24084 : DBLINK name in address field of agent string is not unique within the first 24 bytes
  • ora-13832 : category name specified is invalid
  • ora-31093 : null or invalid value specified for parameter : string
  • ora-13800 : concurrent DDL failure on SQL repository objects
  • ora-40001 : value for string must be greater than zero
  • ora-03135 : connection lost contact
  • ora-12169 : TNS:Net service name given as connect identifier is too long
  • ora-37073 : (XSMCSESS01) Applied relation workspace object must be dimensioned by dimension workspace object.
  • ora-01426 : numeric overflow
  • ora-30395 : dimension options require the COMPATIBLE parameter to be string or greater
  • ora-25449 : invalid variable name: string
  • ora-16820 : Fast-Start Failover observer is no longer observing this database
  • ora-12562 : TNS:bad global handle
  • ora-27199 : skgfpst: sbtpcstatus returned error
  • ora-02298 : cannot validate (string.string) - parent keys not found
  • ora-19526 : only one location allowed for parameter string
  • ora-32315 : REFRESH FAST of "string"."string" unsupported after mixed DML and Direct Load
  • ora-38029 : object statistics are locked
  • ora-06549 : PL/SQL: failed to dynamically open shared object (DLL): string
  • ora-16503 : site ID allocation failure
  • ora-03119 : two-task detected inconsistent datatype specification
  • ora-04097 : DDL conflict while trying to drop or alter a trigger
  • 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.