ORA-01863: the year is not supported for the current calendar

Cause : The yaer is ont supoprted ofr thec urren tcalenadr.

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

Pleas echeckt he doucmentaiton tof ind otu whaty ears rae supoprted ofr thec urren tcalenadr.

update : 22-09-2017
ORA-01863

ORA-01863 - the year is not supported for the current calendar
ORA-01863 - the year is not supported for the current calendar

  • ora-31493 : could not prepare session for LogMiner session
  • ora-03201 : the group number specification is invalid
  • ora-32575 : Explicit column default is not supported for modifying views
  • ora-24752 : OCI_TRANS_NEW flag must be specified for local transactions
  • ora-25017 : cannot reference NEW ROWID for movable rows in before triggers
  • ora-09870 : spini: failure initializing maximum number of open files.
  • ora-16197 : Invalid DB_UNIQUE_NAME parameter specification
  • ora-02162 : invalid value for MAXDATAFILES
  • ora-16110 : user procedure processing of logical standby apply DDL
  • ora-10583 : Can not recovery file string renamed as missing during test recovery
  • ora-00108 : failed to set up dispatcher to accept connection asynchronously
  • ora-31090 : invalid database schema name "string"
  • ora-07843 : sllfcl: LIB$FREE_VM failure
  • ora-12420 : required procedures and functions not in policy package "string"
  • ora-00741 : logfile size of (string) blocks exceeds maximum logfile size
  • ora-26509 : null materialized view control structure
  • ora-22166 : collection is empty
  • ora-38413 : elementary attribute name may not be longer than 32 characters
  • ora-39064 : unable to write to the log file
  • ora-06794 : TLI Driver: shadow process could not retrieve protocol info
  • ora-03214 : File Size specified is smaller than minimum required
  • ora-31404 : all input parameters are null
  • ora-36816 : (XSTBLFUNC09) The workspace object dimension is of datatype string which does not support custom member upserts.
  • ora-16813 : log apply service not running on apply instance string recorded by the broker
  • ora-25315 : unsupported configuration for propagation of buffered messages
  • ora-02057 : 2PC: string: bad two-phase recovery state number string from string
  • ora-09791 : slembdf: translation error, unable to translate error file name.
  • ora-00114 : missing value for system parameter SERVICE_NAMES
  • ora-33298 : (AWUPG01) Analytic Workspace string is already in the newest format allowed by the current compatibility setting
  • ora-16720 : no LOG_ARCHIVE_DEST_n initialization parameters available
  • 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.