ORA-35578: (SQLOUT11) SQL cursor 'number' cannot be used with CURRENT OF syntax
Cause: The CURRENT OF syntax in the WHERE clause tried to use a cursor that was not declared with the FOR UPDATE [ of ] SQL syntax
Action: Add the FOR UPDATE [ OF ] SQL syntax to the cursor specified
https://support.oracle.com/
http://www.oracle.com/
ORA-35282: (SNSYN166) The format of the AGGREGATE function is: AGGREGATE(varname USING aggmap-name [COUNTVAR intvar-name] [FORCECALC])
Cause: The user used incorrect syntax for the AGGREGATE function
Action: Correct the calling syntax
ORA-35280: (SNSYN165) The format of the AGGREGATE command is: AGGREGATE varname1 [varname2 varname3 ...] USING aggmap-name [COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA] [THREADS #]
Cause: The user used incorrect syntax for the AGGREGATE command
Action: Correct the calling syntax
ORA-35276: (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]
Cause: The user used incorrect syntax for the ALLOCATE command
Action: Correct the calling syntax
ORA-35180: (SNSYN103) The format of the OUTFILE command is: OUTFILE [APPEND] {EOF | TRACEFILE | filename [NOCACHE] [NLS_CHARSET name]}
Cause: The user specified incorrect syntax for the OUTFILE command
Action: none
ORA-35095: (QFSVNS01) One or more imported values of fixed-width dimension workspace object have been truncated
Cause: The data in the EIF file was exported from a dimension with wider values than the target dimension will accommodate
Action: Change the definition of the target dimension, or check to be sure that multiple values from the target dimension have not become identical during the import process. This could cause data loss as data from later dimension values overstores data imported earlier
ORA-35078: (QFHEAD05) An EIF extension file header for string is not in the correct format
Cause: An EIF extension file in multi-file IMPORT did not contain correct header information
Action: Check to be sure that EIFEXTENSIONPATH is set correctly and that all the extension files for the current IMPORT were created by the same EXPORT command as the main EIF file
ORA-35076: (QFHEAD04) CAUTION: The textual data in EIF file string is encoded in a character set that is not recognized by this version of string
Cause: IMPORT could not recognize the character set specification in the EIF file
Action: Check the imported text data. If it was not imported correctly, recreate the EIF file with a character set supported by the current Oracle version
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: If possible, set EIFVERSION in the exporting instance to a lower number, recreate the EIF file, and import the new file
ORA-35071: (QFHEAD06) EIF file string cannot be imported because analytic workspace string has not been upgraded to version string
Cause: User attempted to import from an EIF file that was created by a newer version of the product into an AW that was created by a older version of the product
Action: Make sure that the compatibility mode parameter in the init.ora of the importing instance specifies a version that is at least as high as the parameter was in the exporting instance. Then, convert the AW to the latest storage format and reexecute the import command. Alternatively, change the EIFVERSION option of the exporting instance to a lower number, recreate the EIF file, and import the new file