ORA-35074: (QFHEAD02) EIF file string cannot be read by this version of string.

Cause : The EIF file was created with an internal version number indicating it may contain objects that are not compatible with the current Oracle OLAP version, or the EIF file is in an obsolete format.

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

If possible, set EIFVERSION in the exporting instance to a lower number, recreate the EIF file, and import the new file.

update : 20-09-2017

ORA-35074 - (QFHEAD02) EIF file string cannot be read by this version of string.
ORA-35074 - (QFHEAD02) EIF file string cannot be read by this version of string.

  • ora-00075 : process "string" not found in this instance
  • ora-29831 : operator binding not found
  • ora-01571 : redo version string incompatible with ORACLE version string
  • ora-27091 : unable to queue I/O
  • ora-15059 : invalid device type for ASM disk
  • ora-31160 : max substitution group size string exceeded by "string" (string) for head element "string" (string)
  • ora-00705 : inconsistent state during start up; shut down the instance, then restart it
  • ora-01799 : a column may not be outer-joined to a subquery
  • ora-23341 : user function required
  • ora-22992 : cannot use LOB locators selected from remote tables
  • ora-13428 : invalid modelCoordinateLocation
  • ora-01478 : array bind may not include any LONG columns
  • ora-12560 : TNS:protocol adapter error
  • ora-14103 : LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE
  • ora-16251 : LSP1 Background Build not permitted
  • ora-16778 : redo transport error for one or more databases
  • ora-06102 : NETTCP: cannot allocate context area
  • ora-30069 : Auto Undo-Management Error simulation - test site = string
  • ora-07655 : slsprom:$TRNLOG failure
  • ora-01883 : overlap was disabled during a region transition
  • ora-28661 : Object already has COMPRESS clause specified
  • ora-31104 : Cannot find lock with token "string" on "string" for unlock
  • ora-06920 : CMX: getbrkmsg illegal datatype
  • ora-30000 : missing either trim specification or char expression in TRIM
  • ora-01638 : parameter string does not allow ORACLE version string to mount cluster database
  • ora-16196 : database has been previously opened and closed
  • ora-39054 : missing or invalid definition of the SQL output file.
  • ora-36261 : (XSAGPARTDEP00) Can not Aggregate PARTITION TEMPLATE %J because the path of aggregation would recursively enter partition %J.
  • ora-15186 : ASMLIB error function = [string], error = [string], mesg = [string]
  • ora-24129 : table name string does not start with string prefix
  • 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.