ORA-32125: Attribute type is not appropriate

ORA-32125: Attribute type is not appropriate

Cause: The return type of the get method does not match the type of the attribute being passed.

Action: Call the appropriate get method.

ORA-32124: Illegal attribute passed

ORA-32124: Illegal attribute passed

Cause: The attribute passed is not applicable for the described object.

Action: Pass a valid attribute.

ORA-32123: Attribute number is out of range

ORA-32123: Attribute number is out of range

Cause: The attribute number passed is greater than the total number of attributes of the described object.

Action: Pass the attribute number within the allowable range.

ORA-32121: Source FILE is null

ORA-32121: Source FILE is null

Cause: The source FILE instance on which the operation was attempted was null.

Action: Use a valid, non-null source FILE instance for this operation.

ORA-32120: Buffer size is less than amount specified

ORA-32120: Buffer size is less than amount specified

Cause: The buffer size specified for the FILE read or write operation was less than the amount to be read or written.

Action: The buffer size must be equal to or greater than than the amount to be read from or written to the FILE.

ORA-32118: Cannot perform operation on a null FILE

ORA-32118: Cannot perform operation on a null FILE

Cause: The FILE instance on which the operation was attempted was null.

Action: Use a valid, non-null FILE instance to perform this operation.

ORA-32117: Source LOB is null

ORA-32117: Source LOB is null

Cause: The source LOB instance on which the operation was attempted was null.

Action: Use a valid, non-null source LOB instance for this operation.

ORA-32116: Buffer size is less than amount specified

ORA-32116: Buffer size is less than amount specified

Cause: The buffer size specified for the LOB read or write operation was less than the amount to be read or written.

Action: The buffer size must be equal to or greater than than the amount to be read from or written to the LOB.

ORA-32114: Cannot perform operation on a null LOB

ORA-32114: Cannot perform operation on a null LOB

Cause: The LOB instance on which the operation was attempted was null.

Action: Use a valid, non-null LOB instance to perform this operation.

ORA-32113: Null object passed

ORA-32113: Null object passed

Cause: Null object was passed.

Action: Pass a non-null object.

ORA-32110: Connection not specified

ORA-32110: Connection not specified

Cause: A null connection was passed.

Action: Pass a valid, non-null connection.

ORA-32109: invalid column or parameter position

ORA-32109: invalid column or parameter position

Cause: An invalid column or parameter position is specified.

Action: Specify a valid column or position number.

ORA-32108: max column or parameter size not specified

ORA-32108: max column or parameter size not specified

Cause: The max column or parameter size is not specified.

Action: Specify the max size by setMaxColumnSize or setMaxParamSize.

ORA-32107: internal OCI memory allocation failure

ORA-32107: internal OCI memory allocation failure

Cause: Memory could not be allocated from an OCI heap.

Action: Increase the process memory size.

ORA-32106: array fetch not allowed without setBuffer on all columns

ORA-32106: array fetch not allowed without setBuffer on all columns

Cause: The setBuffer method was not called for all column postions and the next method was called to fetch more than one row.

Action: Call the setBuffer method for all column positions if next is to to be called to fetch more than one row.

ORA-32104: cannot retrieve OCI error message

ORA-32104: cannot retrieve OCI error message

Cause: Error message after an OCI call could not be retrieved.

Action: This is an internal OCCI Error. Please contact customer support.

ORA-32103: error from OCI call

ORA-32103: error from OCI call

Cause: An error code other than OCI_ERROR is returned from an OCI call.

Action: This is an internal OCCI Error. Please contact customer support.

ORA-32102: invalid OCI handle

ORA-32102: invalid OCI handle

Cause: An invalid OCI handle is passed to an OCI call.

Action: This is an internal OCCI Error. Please contact customer support.

ORA-32101: cannot create OCI Environment

ORA-32101: cannot create OCI Environment

Cause: An OCI Environment could not be created for OCCI

Action: Insure that the parameters to the creatEnvironment method are valid

ORA-32100: operation invalid on transient object

ORA-32100: operation invalid on transient object

Cause: Trying to perform an operation on transient object which is is valid only on persistent objects

Action: Make sure object is persistent

ORA-32060: channel failure

ORA-32060: channel failure

Cause: Channel failure between foreground and background process.

Action: Check foreground trace files for errors.

ORA-32059: deadlock detected on mapping structures

ORA-32059: deadlock detected on mapping structures

Cause: Mapping structures already locked by the same session.

Action: Unlock mapping structures before proceeding with current operation.

ORA-32058: operation restricted to SYSDBA users

ORA-32058: operation restricted to SYSDBA users

Cause: Operation requires SYSDBA priviliges.

Action: Connect to the database as SYSDBA.

ORA-32057: invalid lock mode

ORA-32057: invalid lock mode

Cause: An invalid mode was used for a lock operation.

Action: Specify one of expected lock modes.

ORA-32056: invalid number of extents

ORA-32056: invalid number of extents

Cause: Invalid number of extents used for map operation.

Action: Specify a non-negative number of extents.

ORA-32055: invalid file type

ORA-32055: invalid file type

Cause: Invalid file type used when mapping files.

Action: Specify one of expected file types.

ORA-32054: lost communication with FMPUTL process

ORA-32054: lost communication with FMPUTL process

Cause: Lost communication with mapping utility.

Action: Check FMON and FMPUTL trace files for errors.

ORA-32053: operation not supported

ORA-32053: operation not supported

Cause: Mapping libraries do not support operation.

Action: Check whether mapping libraries are available and whether operation is supported by the libraries.

FMON trace files for an ORA-32052 error. ORA-32052: failed to start mapping service

FMON trace files for an ORA-32052 error. ORA-32052: failed to start mapping service

Cause: The mapping service failed to start properly.

Action: Check FMON trace files for errors.

ORA-32051: mapping service not available

ORA-32051: mapping service not available

Cause: The mapping service was never started or previously failed to start properly.

Action: Set FILE_MAPPING to TRUE if it is not currently set. Otherwise, check

ORA-32050: %s operation failed

ORA-32050: %s operation failed

Cause: A mapping operation failed.

Action: Check FMON trace files for errors.

ORA-32037: unsupported use of LEVEL in membership condition

ORA-32037: unsupported use of LEVEL in membership condition

Cause: An attempt was made to use LEVEL in membership condition with subquery that is not supported.

Action: Rewrite query to avoid using LEVEL in membership condition

ORA-32036: unsupported case for inlining of query name in WITH clause

ORA-32036: unsupported case for inlining of query name in WITH clause

Cause: There is at least one query name which is inlined more than once because it s definition query is too simple and references another query name. This is currently unsupported yet.

Action: remove such query name and retry

ORA-32035: unreferenced query name defined in WITH clause

ORA-32035: unreferenced query name defined in WITH clause

Cause: There is at least one WITH clause query name that is not referenced in any place.

Action: remove the unreferenced query name and retry

ORA-32034: unsupported use of WITH clause

ORA-32034: unsupported use of WITH clause

Cause: Inproper use of WITH clause because one of the following two reasons: 1. nesting of WITH clause within WITH clause not supported yet 2. For a set query, WITH clause can t be specified for a branch. 3. WITH clause can t sepecified within parentheses.

Action: correct query and retry

ORA-32033: unsupported column aliasing

ORA-32033: unsupported column aliasing

Cause: column aliasing in WITH clause is not supported yet

Action: specify aliasing in defintion subquery and retry

ORA-32032: free temporary object number not available

ORA-32032: free temporary object number not available

Cause: Too many queries using temp table transformation are currently being run to use up all temporay object numbers.

Action: Turn off temporary table transformation or wait, then retry

ORA-32031: illegal reference of a query name in WITH clause

ORA-32031: illegal reference of a query name in WITH clause

Cause: forward or recursive reference of a query name in WITH clause is not allowed.

Action: Correct query statement, then retry.

ORA-32028: Syslog facility or level not recognized

ORA-32028: Syslog facility or level not recognized

Cause: Syslog facility or level did not conform to the standard facility or level provided in the syslog.h file

Action: Specify a facility or level such as LOCAL1.NOTICE which conforms to the syslog.h file

ORA-32027: There is no string column with the matching type in string.string.

ORA-32027: There is no string column with the matching type in string.string.

Cause: An attempt was made to set the audit table to a table or view object that does not have a column with the same name and type as the one in the audit table.

Action: Specify a valid table or view object for the audit table option.

ORA-32026: %s.string has fewer columns compared to string table.

ORA-32026: %s.string has fewer columns compared to string table.

Cause: An attempt was made to set the audit table to a table or view object that has fewer columns compared to the base audit table.

Action: Specify a valid table or view object for the audit table option.

ORA-32025: %s.string is not a table or view object.

ORA-32025: %s.string is not a table or view object.

Cause: An attempt was made to set the audit table to a non-table object or a non-view object.

Action: Specify a valid table or view object for the audit table option.

ORA-32024: invalid directory specified for audit_file_dest parameter

ORA-32024: invalid directory specified for audit_file_dest parameter

Cause: Either the directory does not exist or it is not writable.

Action: Retry the command by specifying a valid directory or granting appropriate directory permissions.

ORA-32022: parameter value longer than string characters

ORA-32022: parameter value longer than string characters

Cause: An attempt was made to alter a parameter value but the combined length of all the parameter values was more than the allowed maximum.

Action: Reduce the parameter value length and retry the command. For the DISPATCHERS parameter, use listener aliases to reduce value length.

ORA-32021: parameter value longer than string characters

ORA-32021: parameter value longer than string characters

Cause: An attempt was made to alter a parameter value but the number of characters in the parameter value was longer than the allowed maximum. For a list parameter, one of the values in the list was longer than the allowed maximum.

Action: Reduce the parameter value length and retry the command. For the DISPATCHERS parameter, use listener aliases to reduce value length.

ORA-32020: SID=* clause needed to modify this parameter

ORA-32020: SID=* clause needed to modify this parameter

Cause: The parameter did not have the same value on all RAC instances.

Action: Retry the command by specifying SID=*

ORA-32019: The parameter SPFILE cannot be updated in the server parameter file.

ORA-32019: The parameter SPFILE cannot be updated in the server parameter file.

Cause: An attempt was made to update the parameter SPFILE in the server parameter file.

Action: Convert the server parameter file into a parameter file and then add the parameters needed and recreate the server parameter file.

ORA-32018: parameter cannot be modified in memory on another instance

ORA-32018: parameter cannot be modified in memory on another instance

Cause: Parameter adjustment can take a very long time

Action: Modify the parameter individually on each instance using the SID clause of the alter system command

ORA-32017: failure in updating SPFILE

ORA-32017: failure in updating SPFILE

Cause: A failure occured while updating the SPFILE.

Action: See associated errors.

ORA-32016: parameter string cannot be updated in SPFILE

ORA-32016: parameter string cannot be updated in SPFILE

Cause: Database is mounted.

Action: Unmount the database to update the parameter in the SPFILE

ORA-32015: unable to restore SPFILE

ORA-32015: unable to restore SPFILE

Cause: Failure during SPFILE restore. It could be that the restore destination is not valid.

Action: Further diagnostic information should be in the error stack.

ORA-32014: error processing parameter string from the SPFILE restore image

ORA-32014: error processing parameter string from the SPFILE restore image

Cause: Failure during processing of parameters from restored SPFILE. It could be that restore image of the SPFILE is corrupted.

Action: Further diagnostic information should be in the error stack.

ORA-32013: failure in verifying parameters from the restored SPFILE

ORA-32013: failure in verifying parameters from the restored SPFILE

Cause: Failure during processing of parameters from restored SPFILE. It could be that restore image of the SPFILE is corrupted.

Action: Further diagnostic information should be in the error stack.

ORA-32012: failure in processing system parameters from restored SPFILE

ORA-32012: failure in processing system parameters from restored SPFILE

Cause: Failure during processing of parameters from restored SPFILE

Action: Further diagnostic information should be in the error stack.

ORA-32011: cannot restore SPFILE to location already being used by the instance

ORA-32011: cannot restore SPFILE to location already being used by the instance

Cause: A restore operation trying to write to an SPFILE that was used to startup the instance.

Action: Specify a different SPFILE name

ORA-32010: cannot find entry to delete in SPFILE

ORA-32010: cannot find entry to delete in SPFILE

Cause: The SPFILE did not contain the sid.parameter entry.

Action: Change the sid and or or the parameter.

ORA-32009: cannot reset the memory value for instance string from instance string

ORA-32009: cannot reset the memory value for instance string from instance string

Cause: Memory resets of local parameters are only allowed.

Action: Retry the query for the local instance if needed.

ORA-32008: error while processing parameter update at instance string

ORA-32008: error while processing parameter update at instance string

Cause: An error occured while processing a parameter on a remote instance.

Action: See accompanying error messages.

ORA-32007: internal

ORA-32007: internal

Cause: A parameter error occured.

Action: Call Oracle support.

ORA-32006: %s initialization parameter has been deprecated

ORA-32006: %s initialization parameter has been deprecated

Cause: A deprecated parmeter was specified at startup

Action: Consult Oracle documentation to find new parameters to use instead.