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 : 30-04-2017

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

  • ora-00396 : error string required fallback to single-pass recovery
  • ora-30680 : debugger connection handshake failed
  • ora-16046 : Archive log destination failed due to failed dependent destination
  • ora-09275 : CONNECT INTERNAL is not a valid DBA connection
  • ora-13708 : Some snapshots in the range [string, string] were purged before the analysis was complete.
  • ora-00453 : backgroud process 'string' is dead
  • ora-22871 : ALTER TYPE with REPLACE is not allowed for pure incomplete types
  • ora-12171 : TNS:could not resolve connect identifier: string
  • ora-16109 : failed to apply log data from previous primary
  • ora-31059 : Cannot insert root XML document node if it already exists
  • ora-23325 : parameter type is not string
  • ora-14321 : cannot add/drop values to DEFAULT partition
  • ora-24308 : illegal define position
  • ora-39951 : incomplete values specified for PL/SQL warning settings
  • ora-02162 : invalid value for MAXDATAFILES
  • ora-19646 : cannot change size of datafile string from string to string
  • ora-19579 : archivelog record for string not found
  • ora-13384 : error in network schema: string
  • ora-09202 : sfifi: error identifying file
  • ora-00085 : current call does not exist
  • ora-34360 : (MXDSS15) number other users writing
  • ora-38725 : specified name "string" does not match actual "string"
  • ora-29501 : invalid or missing Java source, class, or resource name
  • ora-37039 : (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.
  • ora-06557 : null values are not allowed for any parameters to pipe icd's
  • ora-24091 : Destination queue string is the same as the source queue
  • ora-38413 : elementary attribute name may not be longer than 32 characters
  • ora-29517 : recursive resolution failed for a referenced class
  • ora-30939 : Order violation: Element 'string' may not follow element 'string'
  • ora-15031 : disk specification 'string' matches no disks
  • 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.