ORA-23501: refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0

Cause : Instantiation of a refresh template is not supported for database compatibility 8.0 or less.

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

Be sure the database compatibility is 8.1 or above.

update : 24-06-2017
ORA-23501

ORA-23501 - refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0
ORA-23501 - refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0

  • ora-12410 : internal policy error for policy: string Error: string
  • ora-07278 : splon: ops$username exceeds buffer length.
  • ora-29260 : network error: string
  • ora-07346 : slnrm: normalized file name is too long
  • ora-19815 : WARNING: string of string bytes is string%% used, and has string remaining bytes available.
  • ora-25120 : MINIMUM EXTENT option already specified
  • ora-33450 : (ESDREAD05) Discarding compiled code for workspace object because number now has more or fewer dimensions than it had when the code was compiled.
  • ora-14161 : subpartition number string: sum of PCTUSED and PCTFREE may not exceed 100
  • ora-14153 : only one of STORE IN or clause may be specified
  • ora-28534 : Heterogeneous Services preprocessing error
  • ora-29299 : Invalid handle for piecewise compress or uncompress
  • ora-23382 : materialized view repgroup "string"."string" is not registered at site string
  • ora-36677 : (XSDPART15) Duplicate value in value lists of number and number
  • ora-07600 : slkmnm: $GETSYIW failure
  • ora-19257 : XQ0037 - function or variable string in module already defined
  • ora-08104 : this index object string is being online built or rebuilt
  • ora-13296 : incorrect coordinate system specification
  • ora-16130 : supplemental log information is missing from log stream
  • ora-22312 : must specify either CASCADE or INVALIDATE option
  • ora-02076 : sequence not co-located with updated table or long column
  • ora-39317 : call to DBMS_SCHEMA_COPY.VALIDATION_CHECK is not legal
  • ora-01875 : time zone minute must be between -59 and 59
  • ora-01171 : datafile string going offline due to error advancing checkpoint
  • ora-39129 : Object type string not imported. Name conflicts with the master table
  • ora-32014 : error processing parameter "string" from the SPFILE restore image
  • ora-30969 : invalid syntax for PARAMETERS
  • ora-02345 : cannot create a view with column based on CURSOR operator
  • ora-06122 : NETTCP: setup failure
  • ora-14012 : resulting partition name conflicts with that of an existing partition
  • ora-29955 : error occurred in the execution of ODCIINDEXEXCHANGEPARTITION routine
  • 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.