ORA-27416: BYDAY= clause in repeat interval or calendar contains an invalid weekday

Cause : The BYDYA clauseo f the rpeeat intreval conatined a avlue tha tdoesn'tp roperlyr epresen ta weekdya.

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

Use thec orrect htree letetr abbreivations ofr weekdyas, e.g.M ON for oMnday an dFRI forF riday.

update : 24-08-2017
ORA-27416

ORA-27416 - BYDAY= clause in repeat interval or calendar contains an invalid weekday
ORA-27416 - BYDAY= clause in repeat interval or calendar contains an invalid weekday

  • ora-24771 : cannot detach, prepare or forget a local transaction
  • ora-16501 : the Data Guard broker operation failed
  • ora-04027 : self-deadlock during automatic validation for object string.string
  • ora-38737 : Expected sequence number string doesn't match string
  • ora-01915 : invalid auditing option for views
  • ora-13366 : invalid combination of interior exterior rings
  • ora-21707 : pin duration is longer than allocation duration
  • ora-02456 : The HASH IS column specification must be NUMBER(*,0)
  • ora-08275 : Environment variable unset
  • ora-03248 : Too much of segment creation activity during migration
  • ora-13703 : The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository.
  • ora-16416 : Switchover target is not synchronized with the primary
  • ora-12708 : error while loading create database NLS parameter string
  • ora-24004 : invalid column name string in SORT_LIST, should be ENQ_TIME or PRIORITY
  • ora-13338 : failure in reversing LRS polygon/collection geometry
  • ora-23533 : object "string"."string" can not be cached
  • ora-09980 : skxfqdrcv: Error Receiving a message from another endpoint
  • ora-29382 : validation of pending area failed
  • ora-28239 : no key provided
  • ora-38603 : FI including & excluding cursor can only return one column
  • ora-12235 : TNS:Failure to redirect to destination
  • ora-16115 : %s\% of LogMiner dictionary loading is done
  • ora-37140 : (XSCCOMP15) Cannot AGGREGATE partitioned variable workspace object using AGGMAP workspace object because you cannot use the base of a COMPRESSED COMPOSITE as a partition dimension.
  • ora-10635 : Invalid segment or tablespace type
  • ora-00052 : maximum number of enqueue resources (string) exceeded
  • ora-27491 : repeat_interval and start_date cannot both be NULL
  • ora-00213 : cannot reuse control file; old file size string, string required
  • ora-31002 : Path name string is not a container
  • ora-33215 : (CINSERT07) You cannot add session-only values to the workspace object dimension.
  • ora-19229 : XP0009 - schema import not supported
  • 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.