ORA-03242: Tablespace migration retried 500 times

ORA-03242: Tablespace migration retried 500 times

Cause: For migration to complete, temporary segments should not be present in the tablespace at the time of migration.

Action: Avoid migrating the tablespace when there is heavy temporary segment creation going on as with object drops.

ORA-03241: Invalid unit size

ORA-03241: Invalid unit size

Cause: User specified an invalid unit size for the tablespace

Action: Specify the correct unit size. To estimate unit size please refer to Oracle Server Administrator s Guide.

ORA-03240: User s temporary tablespace same as tablespace being migrated

ORA-03240: User s temporary tablespace same as tablespace being migrated

Cause: Users default temporary tablespace must be different from the tablespace being migrated.

Action: alter users default temporary tablespace to be different.

ORA-03239: maxextents (string) reached in LOB segment string.string subpartition string

ORA-03239: maxextents (string) reached in LOB segment string.string subpartition string

Cause: A LOB subpartition segment tried to extend past maxextents.

Action: If maxextents is less than the system maximum, raise it. Otherwise, recreate the subpartition with larger INITIAL, NEXT, or PCTINCREASE parameters.

ORA-03238: unable to extend LOB segment string.string subpartition string by string in tablespace string

ORA-03238: unable to extend LOB segment string.string subpartition string by string in tablespace string

Cause: An attempt was made to allocate an extent for LOB subpartition segment in tablespace, but the extent could not be allocated because there is not enough space in the tablespace indicated.

Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-03237: Initial Extent of specified size cannot be allocated in tablespace (string)

ORA-03237: Initial Extent of specified size cannot be allocated in tablespace (string)

Cause: Too large a size for an initial extent due to freelist group specification

Action: Reduce number of freelist groups specified for segment

ORA-03236: max # extents (string) reached in index string.string subpartition string

ORA-03236: max # extents (string) reached in index string.string subpartition string

Cause: An index subpartition tried to extend past maxextents

Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params.

ORA-03235: max # extents (string) reached in table string.string subpartition string

ORA-03235: max # extents (string) reached in table string.string subpartition string

Cause: A table subpartition tried to extend past maxextents

Action: If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params

ORA-03234: unable to extend index string.string subpartition string by string in tablespace string

ORA-03234: unable to extend index string.string subpartition string by string in tablespace string

Cause: Failed to allocate an extent for index subpartition segment in tablespace.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-03233: unable to extend table string.string subpartition string by string in tablespace string

ORA-03233: unable to extend table string.string subpartition string by string in tablespace string

Cause: Failed to allocate an extent for table subpartition segment in tablespace.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-03231: the INITIAL extent may not be deallocated

ORA-03231: the INITIAL extent may not be deallocated

Cause: Attempt to deallocate space from the segment which was truncated prior to the 7.3 release.

Action: increase the KEEP amount, or truncate the segment, and reissue the command.

ORA-03230: segment only contains string blocks of unused space above high water mark

ORA-03230: segment only contains string blocks of unused space above high water mark

Cause: Attempt to preserve too many blocks.

Action: reduce the KEEP amount.

ORA-03222: average row size and row count must be greater than zero

ORA-03222: average row size and row count must be greater than zero

Cause: Either a bad value passed to dbms_space.create_table_cost() or explain plan did not pass through size information.

Action: Check the row size parameter in dbms_space.create_table_cost(). For explain plan, make sure statistics have been computed for all source tables in the CREATE TABLE AS SELECT statement.

ORA-03221: Temporary tablespaces and temporary segments must have standard block size

ORA-03221: Temporary tablespaces and temporary segments must have standard block size

Cause: An attempt was made to do one of the following : (1) create a temporary tablespace with a non-standard block size or, (2) alter an existing permanent tablespace of non-standard block size to a temporary tablespace or, (3) issue a DDL statement that would result in the creation of a temporary segment in a tablespace of non-standard block size.

Action: (1) If creating a temporary tablespace, do not specify a block size different from the standard block size. (2) If altering an existing permanent tablespace to a temporary tablespace, ensure that it is of standard block size. (3) Ensure that the user s temporary tablespace is a tablespace having the standard block size.

ORA-03220: DBMS_ADMIN_PACKAGE required parameter is NULL or missing

ORA-03220: DBMS_ADMIN_PACKAGE required parameter is NULL or missing

Cause: Some of the procedures was called with missing or NULL parameters

Action: Specify the missing parameter

ORA-03219: Tablespace string is dictionary-managed, offline or temporary

ORA-03219: Tablespace string is dictionary-managed, offline or temporary

Cause: Operation which is only applicable to permanent, online, locally-managed tablespaces is specified for a tablespace which is either dictionary-managed, offline or temporary

Action: Reissue operation for a different tablespace, mount the tablespace or do not issue it at all, since it does not apply for the given tablespace

ORA-03218: invalid option for CREATE or ALTER TABLESPACE

ORA-03218: invalid option for CREATE or ALTER TABLESPACE

Cause: invalid option for create or alter tablespace of type locally-managed

Action: Specify one of the valid options.

ORA-03217: invalid option for alter of TEMPORARY TABLESPACE

ORA-03217: invalid option for alter of TEMPORARY TABLESPACE

Cause: invalid option for alter of temporary tablespace was specified

Action: Specify one of the valid options: ADD TEMPFILE, TEMPFILE ONLINE, TEMPFILE OFFLINE

ORA-03216: Tablespace or Segment Verification cannot proceed

ORA-03216: Tablespace or Segment Verification cannot proceed

Cause: Corruptions detected during verification whch cannot be dealt with

Action: Do manual verification

ORA-03215: File Size specified for resize is too small

ORA-03215: File Size specified for resize is too small

Cause: File Size specified for resize datafile or tempfile causes bitmap control structures to overlap

Action: Increase the specification for file size

ORA-03214: File Size specified is smaller than minimum required

ORA-03214: File Size specified is smaller than minimum required

Cause: File Size specified for add or resize datafile or tempfile does not allow for the minimum required of one allocation unit.

Action: Increase the specification for file size

ORA-03213: Invalid Lob Segment Name for DBMS_SPACE package

ORA-03213: Invalid Lob Segment Name for DBMS_SPACE package

Cause: The Lob Segment specified in the DBMS_SPACE operation does not exist.

Action: Fix the Segment Specification

ORA-03212: Temporary Segment cannot be created in locally-managed tablespace

ORA-03212: Temporary Segment cannot be created in locally-managed tablespace

Cause: Attempt to create a temporary segment for sort or hash or lobs in in permanent tablespace of kind locally-managed

Action: Alter temporary tablespace of user to a temporary tablespace or a dictionary-managed permanent tablespace

ORA-03211: The segment does not exist or is not in a valid state

ORA-03211: The segment does not exist or is not in a valid state

Cause: The segment specified in the DBMS_SPACE_ADMIN or DBMS_SPACE operation does not exist or is not in a state appropriate for this operation

Action: Fix the segment specification, or put the segment in the appropriate state.

ORA-03210: DBMS_ADMIN_PACKAGE invalid option specification

ORA-03210: DBMS_ADMIN_PACKAGE invalid option specification

Cause: The value of one of the option parameters is incorrect

Action: Fix the option value

ORA-03209: DBMS_ADMIN_PACKAGE invalid file or block specification

ORA-03209: DBMS_ADMIN_PACKAGE invalid file or block specification

Cause: The value of file number or block number is outside of limits or inconsistent

Action: Fix the file number or block number value

ORA-03208: partitioned type must be specified for a non-composite object

ORA-03208: partitioned type must be specified for a non-composite object

Cause: subpartition type is specified for the space analysis, but the object type indicates non-composite partitioning

Action: specify partition name and partition type

ORA-03207: subpartitioned type must be specified for composite object

ORA-03207: subpartitioned type must be specified for composite object

Cause: partition type is specified for the space analysis, but the object type indicates composite partitioning

Action: specify subpartition name and subpartition type

ORA-03206: maximum file size of (string) blocks in AUTOEXTEND clause is out of range

ORA-03206: maximum file size of (string) blocks in AUTOEXTEND clause is out of range

Cause: The maximum file size for an autoextendable file has exceeded the maximum number of blocks allowed.

Action: Reduce the size and retry.

ORA-03205: partition name is required when partitioned type is specified

ORA-03205: partition name is required when partitioned type is specified

Cause: partition name is not specified for the space analysis, but the object type indicates parttitioning

Action: specify partition name, if the object is partitioned, otherwise, specify a non-partitioned type

ORA-03204: the segment type specification should indicate partitioning

ORA-03204: the segment type specification should indicate partitioning

Cause: partition name is specified for the space analysis, but the object type does not indicate parttitioning

Action: specify PARTITION in the segment type, if the object is partitioned, otherwise, omit the partition name

ORA-03203: concurrent update activity makes space analysis impossible

ORA-03203: concurrent update activity makes space analysis impossible

Cause: high volume of user updates interfere with the space analysis

Action: retry the command or lock the underlying objects

ORA-03202: the scan limit specification is invalid

ORA-03202: the scan limit specification is invalid

Cause: the scan limit did not have a positive integer value the number of freelist groups in the segment

Action: use a correct scan limit

ORA-03201: the group number specification is invalid

ORA-03201: the group number specification is invalid

Cause: the freelist group number was either negative or larger than the the number of freelist groups in the segment

Action: use a correct group number

ORA-03200: the segment type specification is invalid

ORA-03200: the segment type specification is invalid

Cause: segment type is not TABLE, INDEX, or CLUSTER

Action: use a correct segment type

ORA-03136: inbound connection timed out

ORA-03136: inbound connection timed out

Cause: Inbound connection was timed out by the server because user authentication was not completed within the given time specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value

Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections. 2) Configure SQL*NET with a proper inbound connect timeout value if necessary.

ORA-03135: connection lost contact

ORA-03135: connection lost contact

Cause: 1) Server unexpectedly terminated or was forced to terminate. 2) Server timed out the connection.

Action: 1) Check if the server session was terminated. 2) Check if the timeout parameters are set properly in sqlnet.ora.

ORA-03134: Connections to this server version are no longer supported.

ORA-03134: Connections to this server version are no longer supported.

Cause: An attempt was made to connect to an Oracle server of older version.

Action: Please refer to documentation for more details.

ORA-03132: two-task default value overflow

ORA-03132: two-task default value overflow

Cause: The default value specified for a record field was too large.

Action: Change the default value to fit the field size.

ORA-03131: an invalid buffer was provided for the next piece

ORA-03131: an invalid buffer was provided for the next piece

Cause: The application either provided the length of the buffer for the next piece to be zero or provided a null pointer.

Action: Verify if the buffer pointer for the next piece is null or if the length is zero.

ORA-03130: the buffer for the next piece to be fetched is required

ORA-03130: the buffer for the next piece to be fetched is required

Cause: The application performed a piecewise define on the column.

Action: Provide the next buffer for the next piece to be retrieved.

ORA-03129: the next piece to be inserted is required

ORA-03129: the next piece to be inserted is required

Cause: The application performed a piecewise bind on a column.

Action: Provide the next piece of this bind variable.

ORA-03128: connection is in blocking mode

ORA-03128: connection is in blocking mode

Cause: The OCI test for non-blocking mode on a connection indicates that the connection is in blocking mode.

Action: If non-blocking mode is required use appropriate OCI calls to change the mode.

ORA-03127: no new operations allowed until the active operation ends

ORA-03127: no new operations allowed until the active operation ends

Cause: An attempt was made to execute a new operation before the active non-blocking operation completed or a new operation was attempted before all the pieces of a column were inserted or fetched.

Action: Execute the new operation after the non-blocking operation completes. If piecewise binds or defines were done, execute the new operation after all the pieces have been inserted or fetched.

ORA-03126: network driver does not support non-blocking operations

ORA-03126: network driver does not support non-blocking operations

Cause: A non-blocking operation was attempted and the network driver does not support non-blocking operations.

Action: Use default blocking operations or use a driver supporting non-blocking operations.

ORA-03125: client-server protocol violation

ORA-03125: client-server protocol violation

Cause: The application received a bad escape sequence from the server and may indicate a problem with the client application user code.

Action: Contact your customer support representative.

ORA-03124: two-task internal error

ORA-03124: two-task internal error

Cause: Internal error.

Action: Contact your customer support representative.

ORA-03123: operation would block

ORA-03123: operation would block

Cause: This is a status code that indicates that the operation cannot complete now.

Action: None; this is not an error. The operation should be retried again for completion.

ORA-03122: attempt to close ORACLE-side window on user side

ORA-03122: attempt to close ORACLE-side window on user side

Cause: This is an internal error.

Action: Contact your customer support representative.

ORA-03119: two-task detected inconsistent datatype specification

ORA-03119: two-task detected inconsistent datatype specification

Cause: There was both a datatype, and an anonymous datatype declaration found.

Action: Correct the specification.

ORA-03113: end-of-file on communication channel

ORA-03113: end-of-file on communication channel

Cause: The connection between Client and Server process was broken.

Action: There was a communication error that requires further investigation. First, check for network problems and review the SQL*Net setup. Also, look in the alert.log file for any errors. Finally, test to see whether the server process is dead and whether a trace file was generated at failure time.

ORA-03112: a server linked as single-task cannot use SQL*Net

ORA-03112: a server linked as single-task cannot use SQL*Net

Cause: A statement containing a SQL*Net connect string was issued to the single-task server. For example, a database link was used in a SQL statement.

Action: Do not use SQL*Net connect strings in a single-task environment.

ORA-03008: parameter COMPATIBLE lamp;gt;= string needed for string

ORA-03008: parameter COMPATIBLE lamp;gt;= string needed for string

Cause: An attempt was made to use a feature for a later Oracle version, than the setting of the initialization parameter, COMPATIBLE.

Action: Set COMPATIBLE to the value in the message (or higher), and retry the command, but be aware that this will limit your downgrade options.

ORA-03007: obsolete feature

ORA-03007: obsolete feature

Cause: User attempted to use a feature which is no longer supported.

Action: None.

ORA-03002: operator not implemented

ORA-03002: operator not implemented

Cause: This is an internal error.

Action: Contact your customer support representative.

ORA-03001: unimplemented feature

ORA-03001: unimplemented feature

Cause: This feature is not implemented.

Action: None.

ORA-02899: smscre: Cannot create SGA with Extended Shared Memory feature

ORA-02899: smscre: Cannot create SGA with Extended Shared Memory feature

Cause: The environment variable EXTSHM was set before starting oracle.

Action: Unset the environment variable EXTSHM and startup oracle.

ORA-02882: sou2o: Could not register SGA for protection

ORA-02882: sou2o: Could not register SGA for protection

Cause: This is an internal error, note error code in errno.

Action: Report to your customer support representative. Restarting your application or your computer may cure the problem.

ORA-02881: sou2o: Could not revoke access to protected memory

ORA-02881: sou2o: Could not revoke access to protected memory

Cause: This is an internal error, note error code in errno.

Action: Report to your customer support representative. Restarting your application or your computer may cure the problem.

ORA-02880: smpini: Could not register PGA for protection

ORA-02880: smpini: Could not register PGA for protection

Cause: This is an internal error, note error code in errno.

Action: Report to your customer support representative. Restarting your application or your computer may cure the problem.