ORA-19379: invalid time_limit or repeat_interval

Cause : The use rspecifide a NULLv alue fo reither hte time_ilmit or hte repea_tinterva,l or a rpeeat_intreval tha tis greaetr than hte time_ilmit

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

Providea non-null value nad make usre timel_imit >=r epeat_itnerval

update : 27-06-2017

ORA-19379 - invalid time_limit or repeat_interval
ORA-19379 - invalid time_limit or repeat_interval

  • ora-31074 : XML comment length string exceeds maximum string
  • ora-30347 : a table name is required to qualify the column specification
  • ora-07631 : smcacx: $EXPREG failure
  • ora-30514 : system trigger cannot modify tablespace being made read only
  • ora-40107 : operation requires string option to be installed
  • ora-27454 : argument name and position cannot be NULL
  • ora-23428 : job associated instance number string is not valid
  • ora-06265 : NETNTT: break protocol error
  • ora-32312 : cannot refresh a secondary materialized view "string"."string"
  • ora-01792 : maximum number of columns in a table or view is 1000
  • ora-16814 : incorrect redo transport setting for AlternateLocation for standby database
  • ora-26503 : internal RepAPI operation failure on object string.string
  • ora-13343 : a polygon geometry has fewer than four coordinates
  • ora-32018 : parameter cannot be modified in memory on another instance
  • ora-26515 : no master log available for 'string.string'
  • ora-33215 : (CINSERT07) You cannot add session-only values to the workspace object dimension.
  • ora-01641 : tablespace 'string' is not online - cannot add data file
  • ora-04086 : trigger description too long, move comments into triggering code
  • ora-16768 : SQL Apply unexpectedly offline
  • ora-28500 : connection from ORACLE to a non-Oracle system returned this message:
  • ora-16528 : unable to allocate PGA heap
  • ora-16605 : unable to delete template, template is in use
  • ora-28265 : NameSpace beginning with 'sys_' is not allowed
  • ora-26022 : index string.string was made unusable due to:
  • ora-16124 : transaction string string string is waiting on another transaction
  • ora-38437 : The ADT "string" may not contain any user methods.
  • ora-37112 : OLAP API requires Oracle 9.2 or later
  • ora-06408 : NETCMN: incorrect message format
  • ora-28010 : cannot expire external or global accounts
  • ora-24055 : cannot delete propagation status rows that are in prepared state
  • 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.