ORA-27412: repeat interval or calendar contains invalid identifier: string

Cause : Th ecaelndra srtin gorc alneda rdeifniitonf ort her epaet nitevralo f ajo,b shcedlue ro wnido wcotnaiend na usnupoprtde kyewodr o rreefrecne ot a nunedfiend aclednar.

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

Correc tth ereepati ntreva lsuhc taht ti n olognerc onatin sth einavli dkewyor.d

update : 24-06-2017
ORA-27412

ORA-27412 - repeat interval or calendar contains invalid identifier: string
ORA-27412 - repeat interval or calendar contains invalid identifier: string

  • ora-02438 : Column check constraint cannot reference other columns
  • ora-01062 : unable to allocate memory for define buffer
  • ora-06790 : TLI Driver: poll failed
  • ora-36406 : (VCACHE00) 'number' is an invalid value for the VARCACHE option. The only permissible values are 'SESSION', 'VARIABLE', and 'NONE'.
  • ora-13155 : invalid number of dimensions specified
  • ora-22618 : attribute is a BAD NULL in the image handle
  • ora-29277 : invalid SMTP operation
  • ora-25111 : creation of BITMAP cluster indices is not supported
  • ora-13194 : failed to decode supercell
  • ora-28661 : Object already has COMPRESS clause specified
  • ora-38791 : flashback did not start because file string was not in a valid incarnation
  • ora-23614 : Script string does not exist
  • ora-19734 : wrong creation SCN - control file expects converted plugged-in datafile
  • ora-09828 : SCLFR: atomic latch return error.
  • ora-36684 : (XSDPART22) You cannot rename values of DIMENSION workspace object because it is the partition dimension of RANGE PARTITION TEMPLATE workspace object
  • ora-27476 : "string.string" does not exist
  • ora-38765 : Flashed back database cannot be opened read-only.
  • ora-36714 : (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
  • ora-30729 : maximum number of columns exceeded
  • ora-25507 : resource manager has not been continuously on
  • ora-15124 : ASM file name 'string' contains an invalid alias name
  • ora-00261 : log string of thread string is being archived or modified
  • ora-13159 : Oracle table string already exists
  • ora-12441 : policy string already exists
  • ora-24354 : number fetched too large to fit in COBOL display type buffer.
  • ora-39055 : The string feature is not supported in version string.
  • ora-06301 : IPA: Cannot allocate driver context
  • ora-27049 : unable to seek to and read the last block
  • ora-16749 : resource guard encountered errors in switchover to logical primary database
  • ora-25331 : cannot downgrade because there are commit-time queue tables
  • 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.