ORA-33445: (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent

Cause: Two variables are "partition-dependent" if they share any external partition target variables, or if one is the target of an external partition of the other. If object names referred to non-partition-dependent variables at compile time but refer to partition-dependent variables in the run-time context, the OLAP DML program, formula, or model will be automatically recompiled

Action: None needed

Back to previous menu

https://support.oracle.com/
http://www.oracle.com/

ORA-33443: (ESDREAD14) Discarding compiled code for workspace object because analytic workspace string is not attached

Cause: A program used an analytic workspace name in a qualified object name. The named analytic workspace is not attached at program run time

Action: No action necessary. The program will be automatically recompiled. It is likely that the recompile will fail with an appropriate exception code, in which case the signaled condition should be corrected and the program re-run

Back to previous menu

https://support.oracle.com/
http://www.oracle.com/

ORA-33429: (EIFMAKEF17) CAUTION: NTEXT expression will be exported with type TEXT

Cause: User attempted to export an expression whose data type is NTEXT, but but the EIFVERSION option indicates a version of Express / Oracle OLAP that does not support the NTEXT data type. The expression will be exported as a TEXT object instead

Action: No action needed

Back to previous menu

https://support.oracle.com/
http://www.oracle.com/

ORA-33427: (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT

Cause: User attempted to export an object whose data type is NTEXT, but but the EIFVERSION option indicates a version of Express / Oracle OLAP that does not support the NTEXT data type. The object will be exported as a TEXT object instead

Action: No action needed

Back to previous menu

https://support.oracle.com/
http://www.oracle.com/

ORA-33425: (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file

Cause: The user exported an object with data type NTEXT, but the EIF file that will result from the EXPORT command is not written in Unicode. Because no non-Unicode file can represent all possible Unicode data, it is possible that some data will be lost when converting from the Unicode NTEXT object to the EIF file. The EIF file will be written in the character set indicated by the "nls_charset" argument of the EXPORT command, or, if no such argument is present, in the database character set

Action: If the user is certain that the contents of the NTEXT object can be represented in the specified character set, then no action is necessary. Otherwise, the user can add "nls_charset 'UTF8'" to the EXPORT command string. This will result in the EIF file being written in UTF8 Unicode, which can represent all the data contained in NTEXT objects

Back to previous menu

https://support.oracle.com/
http://www.oracle.com/

ORA-33413: (EIFMAKEF01) You cannot export compressed composite workspace object because one of its bases has limited status or a PERMIT READ restriction

Cause: Export of a compressed composite to an EIF file or lob failed because one or more of the bases had some values that were not in the current status. This can be caused either by a LIMIT command or a PERMIT READ restriction on the dimension

Action: Either set the base dimensions' statuses to ALL and remove their PERMIT READ programs, or export using the NOAGGR keyword

Back to previous menu

https://support.oracle.com/
http://www.oracle.com/

ORA-33338: (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace

Cause: The command requires a non-temporary analytic workspace to operate on

Action: Specify an analytic workspace other than EXPTEMP

Back to previous menu

https://support.oracle.com/
http://www.oracle.com/

ORA-33336: (DSSEXIST04A) Analytic workspace string is not attached

Cause: The specified analytic workspace is currently not attached to the session, or the name is misspelled

Action: Attach the analytic workspace with the AW ATTACH command, or correct the spelling of the name

Back to previous menu

https://support.oracle.com/
http://www.oracle.com/

ORA-33334: (DSSEXIST04) Analytic workspace string is not attached

Cause: The specified analytic workspace is currently not attached to the session, or the name is misspelled

Action: Attach the analytic workspace with the AW ATTACH command, or correct the spelling of the name

Back to previous menu

https://support.oracle.com/
http://www.oracle.com/

ORA-33332: (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again

Cause: There is no currently active analytic workspace. The command that generated the error requires an active analytic workspace to operate on

Action: Execute an AW ATTACH or AW CREATE command to establish an active workspace

Back to previous menu

https://support.oracle.com/
http://www.oracle.com/