Oracle Error Codes Database » Oracle 11g

ORA-19390: The profile type is not valid

Oracle 11g Release 2 — Fri, 04 Nov 2011 23:16:45 +0000

ORA-19390: The profile type is not valid

Database version: Oracle 11g Release 2 (11.2)

Cause: The profile type is not valid.

Solution: Check the available profile types.

ORA-19389: LOB types are not supported for SQL binds

Oracle 11g Release 2 — Thu, 03 Nov 2011 23:16:45 +0000

ORA-19389: LOB types are not supported for SQL binds

Database version: Oracle 11g Release 2 (11.2)

Cause: A LOB type was provided in a SQL bind list.

Solution: Replace the LOB binds with legal bind types or try another SQL.

ORA-19388: operation not supported for “SQL Tuning Set” type

Oracle 11g Release 2 — Wed, 02 Nov 2011 23:16:45 +0000

ORA-19388: operation not supported for “SQL Tuning Set” type

Database version: Oracle 11g Release 2 (11.2)

Cause: The attempted operation was unsupported for the type of the given SQL Tuning Set.

Solution: Check the SQL Tuning Set and retry the operation.

ORA-19387: “SQL Tuning Set” “string” belongs to another tuning task

Oracle 11g Release 2 — Tue, 01 Nov 2011 23:16:45 +0000

ORA-19387: “SQL Tuning Set” “string” belongs to another tuning task

Database version: Oracle 11g Release 2 (11.2)

Cause: The user attempted to tune a task-managed SQL Tuning Set belonging to one task within the scope of another task.

Solution: Check the SQL Tuning Set and retry the operation.

ORA-19386: target object already exists for tuning task “string”

Oracle 11g Release 2 — Mon, 31 Oct 2011 23:16:45 +0000

ORA-19386: target object already exists for tuning task “string”

Database version: Oracle 11g Release 2 (11.2)

Cause: An attempt was made to set a target object for a tuning task when one had already been set.

Solution: Create a new task if another target object is needed.

ORA-19385: staging table is empty

Oracle 11g Release 2 — Sun, 30 Oct 2011 23:16:45 +0000

ORA-19385: staging table is empty

Database version: Oracle 11g Release 2 (11.2)

Cause: An attempt was made to perform an operation on an empty staging table.

Solution: Check the staging table to make sure that it has rows.

ORA-19384: cannot pack into staging table from previous version

Oracle 11g Release 2 — Sat, 29 Oct 2011 23:16:45 +0000

ORA-19384: cannot pack into staging table from previous version

Database version: Oracle 11g Release 2 (11.2)

Cause: An attempt was made to perform a pack operation on a staging table from a previous version.

Solution: Create a staging table in the current version and retry the operation.

ORA-19381: cannot create staging table in SYS schema

Oracle 11g Release 2 — Fri, 28 Oct 2011 23:16:45 +0000

ORA-19381: cannot create staging table in SYS schema

Database version: Oracle 11g Release 2 (11.2)

Cause: The user attempted to create a staging table in the sys schema

Solution: Create the table in another schema.

ORA-19380: invalid plan filter

Oracle 11g Release 2 — Thu, 27 Oct 2011 23:16:45 +0000

ORA-19380: invalid plan filter

Database version: Oracle 11g Release 2 (11.2)

Cause: The user specified an invalid filter for the plan when calling the select_sqlset table function.

Solution: Adjust the the filter to be one of the following values and retry the operation: MAX_ELAPSED_TIME, MAX_CPU_TIME, MAX_DISK_READS, MAX_OPTIMIZER_COST, MAX_BUFFER_GETS, FIRST_LOADED LAST_LOADED, FIRST_GENERATED, or LAST_GENERATED.

ORA-19379: invalid time_limit or repeat_interval

Oracle 11g Release 2 — Wed, 26 Oct 2011 23:16:45 +0000

ORA-19379: invalid time_limit or repeat_interval

Database version: Oracle 11g Release 2 (11.2)

Cause: The user specified a NULL value for either the time_limit or the repeat_interval, or a repeat_interval that is greater than the time_limit

Solution: Provide a non-null value and make sure time_limit >= repeat_interval

ORA-19378: invalid mode

Oracle 11g Release 2 — Tue, 25 Oct 2011 23:16:45 +0000

ORA-19378: invalid mode

Database version: Oracle 11g Release 2 (11.2)

Cause: The user specified an invalid mode argument to the capture function.

Solution: Provide a mode argument that was defined in the dbmssqlt file

ORA-19377: no “SQL Tuning Set” with name like “string” exists for owner like “string”

Oracle 11g Release 2 — Mon, 24 Oct 2011 23:16:45 +0000

ORA-19377: no “SQL Tuning Set” with name like “string” exists for owner like “string”

Database version: Oracle 11g Release 2 (11.2)

Cause: The user specified a filter to a pack/unpack function for the SQL Tuning Set that targets no STS in the SYS schema or the staging table, respectively

Solution: Provide a different filter after checking the state of the system

ORA-19376: no privileges on tablespace provided or tablespace is offline

Oracle 11g Release 2 — Sun, 23 Oct 2011 23:16:45 +0000

ORA-19376: no privileges on tablespace provided or tablespace is offline

Database version: Oracle 11g Release 2 (11.2)

Cause: The user tried to create a staging table on a tablespace on which he does not have any space allocated, or it is offline

Solution: Allocate space on the tablespace, bring it online, and retry

ORA-19375: no CREATE TABLE privilege on schema “string”

Oracle 11g Release 2 — Sat, 22 Oct 2011 23:16:45 +0000

ORA-19375: no CREATE TABLE privilege on schema “string”

Database version: Oracle 11g Release 2 (11.2)

Cause: The user tried to create a staging table when he is missing the CREATE TABLE privilege on the specified schema.

Solution: Grant the privilege to the user and retry

ORA-19374: invalid staging table

Oracle 11g Release 2 — Fri, 21 Oct 2011 23:16:45 +0000

ORA-19374: invalid staging table

Database version: Oracle 11g Release 2 (11.2)

Cause: The user specified an invalid staging table to one of the pack, unpack, or remap stgtab routines, or the user does not have the correct privileges on the staging table

Solution: Provide a correct staging table or grant the appropriate privileges

ORA-19373: invalid staging table or tablespace

Oracle 11g Release 2 — Thu, 20 Oct 2011 23:16:45 +0000

ORA-19373: invalid staging table or tablespace

Database version: Oracle 11g Release 2 (11.2)

Cause: The user attempted to create a staging table and specified an invalid staging table (or one that already exists) or tablespace

Solution: Check the arguments and try again.

ORA-19372: invalid update condition

Oracle 11g Release 2 — Wed, 19 Oct 2011 23:16:45 +0000

ORA-19372: invalid update condition

Database version: Oracle 11g Release 2 (11.2)

Cause: The user attempted to call load_sqlset with an invalid update condition.

Solution: Check the update condition (e.g., NEW.COL1_NAME >= OLD.COL2_NAME) and retry the operation.

ORA-19371: invalid update option

Oracle 11g Release 2 — Tue, 18 Oct 2011 23:16:45 +0000

ORA-19371: invalid update option

Database version: Oracle 11g Release 2 (11.2)

Cause: The user attempted to call load_sqlset with an update option that is different than REPLACE and ACCUMULATE.

Solution: Adjust the update option and retry the operation.

ORA-19361: ONLINE option not allowed with this type of index

Oracle 11g Release 2 — Mon, 17 Oct 2011 23:16:45 +0000

ORA-19361: ONLINE option not allowed with this type of index

Database version: Oracle 11g Release 2 (11.2)

Cause: The ONLINE option was specified to validate the structure of a system-generated metadata index

Solution: The ONLINE option can not be used with system-generated metadata indexes such as an LOB index, an IOT Top index, an Index on Clusters etc., Run query without using the ONLINE option.

ORA-19336: Missing XML root element

Oracle 11g Release 2 — Sun, 16 Oct 2011 23:16:45 +0000

ORA-19336: Missing XML root element

Database version: Oracle 11g Release 2 (11.2)

Cause: The XML being generated does not have an enclosing root element.

Solution: The XML generated must have a root element

ORA-19335: Invalid format type object

Oracle 11g Release 2 — Sat, 15 Oct 2011 23:16:45 +0000

ORA-19335: Invalid format type object

Database version: Oracle 11g Release 2 (11.2)

Cause: An invalid format type object was specified for the XML function

Solution: Specify a valid format type object

ORA-19334: Invalid column specification for CREATE_DBURI operator

Oracle 11g Release 2 — Fri, 14 Oct 2011 23:16:45 +0000

ORA-19334: Invalid column specification for CREATE_DBURI operator

Database version: Oracle 11g Release 2 (11.2)

Cause: All columns must be valid and pointing to the same table or view

Solution: Specify valid list of columns that are from the same table or view.

ORA-19333: Invalid flags for the CREATE_DBURI operator

Oracle 11g Release 2 — Thu, 13 Oct 2011 23:16:45 +0000

ORA-19333: Invalid flags for the CREATE_DBURI operator

Database version: Oracle 11g Release 2 (11.2)

Cause: The flags argument given to the DBURI operator is invalid

Solution: Specify a valid flag value (TEXT) for the DBURI operator

ORA-19332: Invalid column in the CREATE_DBURI operator

Oracle 11g Release 2 — Wed, 12 Oct 2011 23:16:45 +0000

ORA-19332: Invalid column in the CREATE_DBURI operator

Database version: Oracle 11g Release 2 (11.2)

Cause: The argument to the CREATE_DBURI operator can only be a column.

Solution: Specify a valid column name for the operator

ORA-19331: Last argument to CREATE_DBURI operator must be a column

Oracle 11g Release 2 — Tue, 11 Oct 2011 23:16:45 +0000

ORA-19331: Last argument to CREATE_DBURI operator must be a column

Database version: Oracle 11g Release 2 (11.2)

Cause: The final argument to the CREATE_DBURI operator must be a column to which the reference is being created.

Solution: Specify a valid column name in the query.

ORA-19330: Type ’string’.’string’ not installed. Please install the type before using the CREATE_DBURI operator

Oracle 11g Release 2 — Mon, 10 Oct 2011 23:16:45 +0000

ORA-19330: Type ’string’.’string’ not installed. Please install the type before using the CREATE_DBURI operator

Database version: Oracle 11g Release 2 (11.2)

Cause: The type required for the CREATE_DBURI operator has not been installed correctly.

Solution: Read the installation notes to install the type correctly.

ORA-19323: Invalid url string

Oracle 11g Release 2 — Sun, 09 Oct 2011 23:16:45 +0000

ORA-19323: Invalid url string

Database version: Oracle 11g Release 2 (11.2)

Cause: The URL must be a valid URL string

Solution: Specify a valid url string

ORA-19322: An error occurred while reading from host (string): port (string)

Oracle 11g Release 2 — Sat, 08 Oct 2011 23:16:45 +0000

ORA-19322: An error occurred while reading from host (string): port (string)

Database version: Oracle 11g Release 2 (11.2)

Cause: An error occurred while reading from the HTTP host

Solution: Specify a valid host name and port to read from

ORA-19321: Could not open HTTP connection to host (string): port (string)

Oracle 11g Release 2 — Fri, 07 Oct 2011 23:16:45 +0000

ORA-19321: Could not open HTTP connection to host (string): port (string)

Database version: Oracle 11g Release 2 (11.2)

Cause: A HTTP connection could not be opened to the host

Solution: Specify a valid host name and port to connect to

ORA-19320: Host name not specified in HTTP URL

Oracle 11g Release 2 — Thu, 06 Oct 2011 23:16:45 +0000

ORA-19320: Host name not specified in HTTP URL

Database version: Oracle 11g Release 2 (11.2)

Cause: A host name was not specified in the HTTP url

Solution: Specify a host name in the HTTP url when creating the URL string