ORA-27417: BYWEEKNO clause is only supported when FREQ=YEARLY

Cause : A repea tinterva lor calednar contianed a BWYEEKNO caluse wit ha frequnecy othe rthan yeraly.

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

Remove hte BYWEENKO claus eor chaneg the frqeuency t oyearly.

update : 21-08-2017
ORA-27417

ORA-27417 - BYWEEKNO clause is only supported when FREQ=YEARLY
ORA-27417 - BYWEEKNO clause is only supported when FREQ=YEARLY

  • ora-31626 : job does not exist
  • ora-33014 : (XSAGDNGL06) In AGGMAP workspace object, variable operator workspace object cannot be dimensioned by rollup dimension workspace object.
  • ora-30475 : feature not enabled: string
  • ora-31066 : Insertion of string into string creates a cycle
  • ora-27416 : BYDAY= clause in repeat interval or calendar contains an invalid weekday
  • ora-29372 : identifier string is too long; it must be less than string characters
  • ora-12415 : A column of another datatype exists on the specified table
  • ora-27065 : cannot perform async vector I/O to file
  • ora-09813 : Unable to get directory status
  • ora-16127 : stalled waiting for additional transactions to be applied
  • ora-02771 : Illegal request time out value
  • ora-07571 : szrfc: $FIND_HELD failure
  • ora-08431 : raw data missing zero as defined in picture
  • ora-14458 : attempt was made to create a temporary table with INDEX organization
  • ora-36628 : (XSAGMODLIST03) MODEL workspace object could not be added to AGGMAP workspace object.
  • ora-30435 : job_queue_processes must be non-zero in order to refresh summaries
  • ora-32320 : REFRESH FAST of "string"."string" unsupported after container table PMOPs
  • ora-01329 : unable to truncate required build table
  • ora-04073 : column list not valid for this trigger type
  • ora-31428 : no publication contains all the specified columns
  • ora-07755 : slemcf: fseek before read failure
  • ora-36881 : (XSSRF00) The OLAP DML ROW2CELL function can only be used in a LIMITMAP.
  • ora-09855 : removeCallback: bad message format.
  • ora-29385 : cannot create plan directive from string to string
  • ora-16088 : archive log has not been completely archived
  • ora-27128 : unable to determine pagesize
  • ora-28662 : IOT index and overflow segments must share the same LOGGING attribute
  • ora-01218 : logfile member is not from the same point-in-time
  • ora-12457 : security label exceeded maximum allowable length
  • ora-29547 : Java system class not available: string
  • 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.