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-05-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-01774 : Dump undo option specified more than once
  • ora-01612 : instance string (thread string) is already enabled
  • ora-29839 : failed to validate implementation type
  • ora-32133 : Cannot get stream from LOB/FILE
  • ora-14646 : Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes
  • ora-12412 : policy package string is not installed
  • ora-21710 : argument is expecting a valid memory address of an object
  • ora-06909 : CMX: error during acknowledge of ORACLE_SID
  • ora-02458 : HASHKEYS must be specified for a HASH CLUSTER
  • ora-31014 : Attempted to delete the root container
  • ora-13642 : The specified string string provided for string cannot be converted to a date. The acceptable date format is string.
  • ora-24070 : cannot upgrade queue table string while it is being downgraded
  • ora-19511 : Error received from media manager layer, error text: string
  • ora-28353 : failed to open wallet
  • ora-16623 : stale DRC UID sequence number detected
  • ora-01500 : failure in getting date/time
  • ora-12712 : new character set must be a superset of old character set
  • ora-12484 : invalid OS label
  • ora-12058 : materialized view cannot use prebuilt table
  • ora-27198 : skgfpvl: sbtpcvalidate returned error
  • ora-16140 : standby online logs have not been recovered
  • ora-19958 : potential deadlock involving DIAG process
  • ora-09954 : scgcc: unexpected return status to callback of lock close
  • ora-07617 : $FORMAT_CLASS failed translating the binary label to a string
  • ora-01115 : IO error reading block from file string (block # string)
  • ora-13112 : cannot delete topo_geometry layer [string] from topology
  • ora-00062 : DML full-table lock cannot be acquired; DML_LOCKS is 0
  • ora-01618 : redo thread string is not enabled - cannot mount
  • ora-02474 : Fixed hash area extents used (string) exceeds maximum allowed (string)
  • ora-16408 : Incompatible archival Redo Branch lineage
  • 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.