ORA-23420: interval must evaluate to a time in the future

Cause : The parameter "interval" evaluates to a time earlier than SYSDATE.

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

Choose an expression that evaluates to a time later than SYSDATE.

update : 26-05-2017
ORA-23420

ORA-23420 - interval must evaluate to a time in the future
ORA-23420 - interval must evaluate to a time in the future

  • ora-22974 : missing WITH OBJECT OID clause
  • ora-09804 : Class conversion from binary to ORACLE failed.
  • ora-08185 : Flashback not supported for user SYS
  • ora-31442 : operation timed out while acquiring lock on string
  • ora-00566 : cannot request processor group - NUMA not enabled
  • ora-25957 : join index where clause cannot contain cycles
  • ora-01584 : unable to get file size of control file to be backed up
  • ora-07501 : scgtoa: $deq unexpected return
  • ora-02212 : duplicate PCTFREE option specification
  • ora-30973 : invalid Path Table option for XML Index
  • ora-14104 : RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices
  • ora-30445 : workload queries not found
  • ora-02040 : remote database string does not support two-phase commit
  • ora-39765 : stream must be reset before used in a column array conversion
  • ora-19811 : cannot have files in DB_RECOVERY_FILE_DEST with keep attributes
  • ora-30159 : OCIFileOpen: Cannot create the file or cannot open in the requested mode
  • ora-24083 : cannot specify remote subscribers for string QUEUE string
  • ora-28603 : statement not permitted on empty tables
  • ora-00234 : error in identifying or opening snapshot or copy control file
  • ora-22160 : element at index [string] does not exist
  • ora-23307 : replicated schema string already exists
  • ora-08234 : smsget: cannot get instance listener address
  • ora-01043 : user side memory corruption [string], [string], [string], [string]
  • ora-29821 : specified primary operator does not exist
  • ora-36668 : (XSDPART06) string is not a legal RANGE partition.
  • ora-36170 : (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.
  • ora-14060 : data type or length of a table partitioning column may not be changed
  • ora-00481 : LMON process terminated with error
  • ora-32031 : illegal reference of a query name in WITH clause
  • ora-01518 : CREATE DATABASE must specify more than one log file
  • 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.