ORA-26735: operation not allowed on the specified file group version

Cause : One o rmore adtafilse or epxort dmup fil(es) weer missnig fro mthe sepcifie dfile rgoup vresion.

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

Retryt he opreationa fter dading lal thed ata flies an dData uPmp dupm files() to hte speicfied evrsion.

update : 29-05-2017
ORA-26735

ORA-26735 - operation not allowed on the specified file group version
ORA-26735 - operation not allowed on the specified file group version

  • ora-00403 : %s (string) is not the same as other instances (string)
  • ora-10573 : Test recovery tested redo from change string to string
  • ora-00473 : ARCH process terminated with error
  • ora-27421 : usage of string not supported in a calendar definition
  • ora-36676 : (XSDPART14) Missing dimension list for string.
  • ora-24000 : invalid value string, string should be of the form [SCHEMA.]NAME
  • ora-29342 : user string does not exist in the database
  • ora-10619 : Avoid assertions when possible
  • ora-29875 : failed in the execution of the ODCIINDEXINSERT routine
  • ora-30106 : reserved for future use
  • ora-23411 : materialized view "string"."string" is not in refresh group "string"."string"
  • ora-29549 : class string.string has changed, Java session state cleared
  • ora-02492 : missing required file block increment size in NEXT clause
  • ora-30734 : cannot specify scope constraint on ref column with rowid
  • ora-25305 : enqueue failed, expiration must be zero for queue string.string
  • ora-01551 : extended rollback segment, pinned blocks released
  • ora-29811 : missing STATISTICS keyword
  • ora-38713 : Flashback Database logging is already turned on.
  • ora-16065 : remote archival disabled at standby destination
  • ora-06569 : Collection bound by bind_array contains no elements
  • ora-19229 : XP0009 - schema import not supported
  • ora-19209 : invalid or unsupported formatting argument
  • ora-07283 : sksaprd: invalid volume size for archive destination.
  • ora-09944 : Password entry is corrupt.
  • ora-29849 : error occurred in the execution of ODCIINDEXSPLITPARTITION routine
  • ora-15002 : parameter LOCK_NAME_SPACE exceeds limit of string characters
  • ora-12164 : TNS:Sqlnet.fdf file not present
  • ora-08007 : Further changes to this block by this transaction not allowed
  • ora-39113 : Unable to determine database version
  • ora-24356 : internal error while converting from to COBOL display type.
  • 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.