skip to content »

sudebnyeresheniya.ru

Unexpected error occurred while updating required files

Make sure the name begins with a letter, contains only letters, digits and underscore and contains no more than 30 characters.An attempt was made to drop a level using the default or RESTRICT option in a dimension while references to that level remain in the dimension.

Check to see if the domain index has been implemented with system-managed storage tables.It is possible that the Java class was created from a damaged class file, in which case the CREATE should be reattempted with a correct class file.In that case, the class needs to be created with a resolver. If the CSS was not started, start it and then retry the database startup.The bound table does not contain elements at both index locations in call to bind_array of dbms_sql. Both define_array and bind_array have been called on this cursor. It is not possible for a cursor to both contain array binds and array defines. Array defines are used to move data from select queries into PL/SQL tables and array binds to bind PL/SQL tables to non-select queries.Both define_array and define_column have been called on this cursor. It is not possible for a cursor to both contain regular and array defines. Array defines are used to move data from select queries into PL/SQL tables and regular defines to move data from select queries into PL/SQL variables. (1) This user owns data in the transportable set, but this user is not specified in the TTS_OWNERS list of the import command line option, assuming that TTS_OWNERS is specified.Thereafter, use the DROP MATERIALIZED VIEW command rather than the DROP TABLE command to drop a materialized view.

Perform one of the following actions: - Remove the use of the PL/SQL function. - Disable the REWRITE option on the materialized view.

Use the DROP MATERIALIZED VIEW command to clean up the residual meta data for the materialized view.

Then use the CREATE MATERIALIZED VIEW statement to recreate the materialized view.

the current operation is not allowed because an undo tablespace containing active transactions is pending from a previous SWITCH UNDO operation.

The operation will be allowed again after all transactions in the previous undo tablespace are committed.

The function should be marked DETERMINISTIC only if it always returns the same result value for any given set of input argument values, regardless of any database state or session state.