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-06-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-00032 : invalid session migration password
  • ora-23308 : object string.string does not exist or is invalid
  • ora-25118 : invalid DUMP DATAFILE/TEMPFILE option
  • ora-06537 : OUT bind variable bound to an IN position
  • ora-01574 : maximum number of concurrent transactions exceeded
  • ora-36161 : (XSAGGRRUVCV) Aggregation variable workspace object cannot have itself as a COUNTVAR.
  • ora-02439 : Unique index on a deferrable constraint is not allowed
  • ora-13518 : Invalid database id (string)
  • ora-30771 : Cannot add more than one referential constraint on REF column "string"
  • ora-36170 : (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.
  • ora-16632 : instance being added to database profile
  • ora-14160 : this physical attribute may not be specified for a table subpartition
  • ora-16601 : site contains required resources that are disabled
  • ora-12229 : TNS:Interchange has no more free connections
  • ora-33082 : (XSAGDNGL41) In AGGMAP workspace object, the non-dimensioned valueset workspace object must have a parent QDR in its VALUESET statement over the VALUESET's base dimension.
  • ora-12706 : this CREATE DATABASE character set is not allowed
  • ora-31622 : ORACLE server does not have string access to the specified file
  • ora-02177 : Missing required group number
  • ora-02356 : The database is out of space. The load cannot continue
  • ora-07550 : sftopn: $CONNECT failure
  • ora-39156 : error parsing dump file name "string"
  • ora-31413 : change set string is currently being advanced
  • ora-04054 : database link string does not exist
  • ora-06771 : TLI Driver: error reading version
  • ora-19552 : device type string is invalid
  • ora-16197 : Invalid DB_UNIQUE_NAME parameter specification
  • ora-24775 : cannot prepare or commit transaction with non-zero lock value
  • ora-28178 : password not provided by proxy
  • ora-02466 : The SIZE and INITRANS options cannot be altered for HASH CLUSTERS.
  • ora-16079 : standby archival not enabled
  • 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.