ORA-27491: repeat_interval and start_date cannot both be NULL

Cause : An attepmt was mdae to se tboth reepat_intevral and tsart_dat eto equa lNULL fo ra Schedluer windwo or schdeule.

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

If eithre repeati_ntervalo r startd_ate is est to eqaul NULL,t he othe rshould eb set toa non-NULL value.

update : 28-06-2017

ORA-27491 - repeat_interval and start_date cannot both be NULL
ORA-27491 - repeat_interval and start_date cannot both be NULL

  • ora-36180 : (XSAGGR08) AGGREGATE cannot function because there is a permission clause associated with variable workspace object.
  • ora-16165 : LGWR failed to hear from network server
  • ora-00028 : your session has been killed
  • ora-01658 : unable to create INITIAL extent for segment in tablespace string
  • ora-01792 : maximum number of columns in a table or view is 1000
  • ora-22292 : Cannot open a LOB in read-write mode without a transaction
  • ora-38767 : flashback retention target parameter mismatch
  • ora-39084 : cannot detach job string for user string
  • ora-25462 : evaluation context not specified
  • ora-19227 : XP0007 - fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content.
  • ora-36641 : (XSDUNION20) The concat dimension must be defined as UNIQUE because base dimension workspace object contains custom member values.
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-02724 : osnpbr: cannot send break message to orapop
  • ora-39957 : invalid warning category
  • ora-16655 : specified target standby database invalid
  • ora-29319 : datafile string is not correct
  • ora-00701 : object necessary for warmstarting database cannot be altered
  • ora-36163 : (XSMXAGGR06) The AGGREGATE function cannot be run on more than one variable at a time.
  • ora-06114 : NETTCP: SID lookup failure
  • ora-16602 : object must be disabled to perform this operation
  • ora-06549 : PL/SQL: failed to dynamically open shared object (DLL): string
  • ora-01275 : Operation string is not allowed if standby file management is automatic.
  • ora-02172 : The PUBLIC keyword is not appropriate for a disable thread
  • ora-09260 : sigpidu: error obtaining process id
  • ora-29879 : cannot create multiple domain indexes on a column list using same indextype
  • ora-09801 : Unable to get user ID from connection
  • ora-01490 : invalid ANALYZE command
  • ora-29393 : user string does not exist or is not logged on
  • ora-19507 : failed to retrieve sequential file, handle="string", parms="string"
  • ora-01231 : cannot make read write - file string is offline
  • 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.