1.9 POL 6000–6100 ODBC Driver Messages
Errors in this range are detected by the ODBC (Open Database Connectivity) Driver. The error code is accompanied by a SQL State, which is defined by the ODBC standard. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information. Your software may report other error codes that could help explain the error reported by the ODBC driver. Make sure to note all the error numbers that appeared when you file a trouble report.
- POL-6001 General warning
-
Cause: Driver-specific informational message.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6002 Disconnect error
-
Cause: The disconnect succeeded, but the database detected an error during the disconnect. Your ODBC driver may return a message with additional information.
-
Action: Reopen the database, and verify that no data was lost. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6003 Data truncated
-
Cause: The database loses data while copying from the database to the client, because the buffer is not large enough to return the entire string.
-
Action: Provide a large enough buffer to hold the entire value. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6004 Privilege not revoked
-
Cause: A REVOKE PRIVILEGE command failed.
-
Action: No action required because Oracle Lite does not enforce privileges. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6005 Invalid connection string attribute
-
Cause: The ODBC connect string specified contained an invalid keyword.
-
Action: Check the syntax of the connect string, modify it as necessary, and then try connecting again. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6006 Error in row
-
Cause: An error occurred in one or more rows.
-
Action: The ODBC driver may return a message with additional information. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6007 Option value changed
-
Cause: The ODBC driver didn't support the specified value for the argument and substituted a similar value.
-
Action: The ODBC driver may return a message with additional information. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6008 No rows were updated or deleted
-
Cause: No rows matched the criteria for an UPDATE or DELETE statement.
-
Action: If you want to update or delete rows, check for errors, and then reissue the SQL statement. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6009 More than one row was updated or deleted
-
Cause: The statement or argument contained a positioned UPDATE or DELETE statement, and more than one row was updated or deleted.
-
Action: The ODBC driver may return a message with additional information. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6010 Wrong number of parameters
-
Cause: The number of parameters specified in SQLBindParameter
does not match the number of parameters in the SQL statement.
-
Action: Check for syntax errors, and then reissue the SQL statement. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6011 Restricted datatype attribute violation
-
Cause: The data value could not be converted to the datatype specified. In Oracle Lite, this can also result when attempting to insert into a LONG column.
-
Action: Check for syntax errors, and then reissue the statement. Use SQLPutData()
to insert data into LONG columns. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6012 Unable to connect to data source
-
Cause: The driver was unable to establish a connection with the data source.
-
Action: Verify that the user name provided is valid for the database. You must CREATE SCHEMA for each user name in each Oracle Lite database file to use that user name at connect time. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6013 Connection is in use
-
Cause: The connection specified is already open.
-
Action: Use the existing connection or close it. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6014 Connection is not open
-
Cause: A program tried to close or access a database connection that is not open.
-
Action: Exit and try to connect again. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6015 The data source rejected the connection
-
Cause: The cause of this error is implementation-specific. This error could be an attempt to open a database file when another database file with the same DBFileID
is already open.
-
Action: Use the existing connection or close it. Look for other Oracle Lite error codes, and see the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6016 Connection failure during transaction
-
Cause: The connection failed during the execution of the function, and it can't be determined whether the requested COMMIT or ROLLBACK statement was completed before the failure occurred.
-
Action: Check the updated data to see if your changes are as expected. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6017 Communication link failure
-
Cause: The remote database is inaccessible.
-
Action: Ensure that the remote database is running, the communications network is functioning, and the appropriate database links are present, and then try executing the operation again. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6018 Insert value list does not match column list
-
Cause: An INSERT statement did not specify enough values for all the columns, or it specified too many values.
-
Action: Check the table definition and supply values for all columns for which defaults aren't defined. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6019 The number of values in the derived table does not match the number of columns
-
Cause: A CREATE VIEW statement did not specify enough values for all the columns, or it specified too many values.
-
Action: Check the table definition and supply values for all columns for which defaults aren't defined. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6020 The right side of the string was truncated
-
Cause: Not enough memory was allocated for a string so it had to be truncated.
-
Action: If the truncated string does not cause any problems, then this is not an error. Otherwise, call the routine that reported the error again with a larger string buffer. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6021 Numeric value out of range
-
Cause: A numeric value could not be converted or was too large for the datatype.
-
Action: Declare a larger datatype, or allocate a larger buffer. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6022 Error in assignment
-
Cause: The datatype of a literal or expression does not match the datatype of the column into which it is being inserted.
-
Action: Use a TO_CHAR, TO_NUMBER, TO_DATE or CAST function to cast the expression to the correct datatype. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6023 DATE, TIME, or TIMESTAMP field overflow
-
Cause: The SQLState
contained an invalid DATE, TIME, or TIMESTAMP value.
-
Action: Check the input values for errors, and then reissue the statement. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6024 Division by zero
-
Cause: The SQL statement contained an arithmetic expression that caused division by zero.
-
Action: Check for syntax errors, and then reissue the SQL statement. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6025 String data, length mismatch
-
Cause: The string data contained less data than was specified in the length buffer.
-
Action: If its OK that the string data was shorter than expected, then this may not be an error. Check the SQL input string for errors. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6026 Integrity constraint violation
-
Cause: The value of the parameter or literal in the SQL statement was NULL for a NOT NULL column, or a duplicate value was supplied for a column that is constrained to contain only unique values, or some other integrity constraint was violated.
-
Action: Check the input string for errors, and then try again. If a foreign key constraint is present, verify that the referenced table contains the matching value. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6027 Invalid cursor state
-
Cause: The SQL statement contained a positioned UPDATE or DELETE and the cursor was positioned before the start of the result set or after the end of the result set.
-
Action: Close the cursor, and reissue the SQL statement. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6028 Invalid transaction state
-
Cause: Program attempted to disconnect when a transaction is still active.
-
Action: COMMIT or ROLLBACK any pending transactions, and then reissue the disconnect. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6029 Invalid authorization specification
-
Cause: The user name or password specified in the connection string violated restrictions that are defined by the specified data source.
-
Action: Check the user name and password, and then try connecting again. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6030 Invalid cursor name
-
Cause: The SQL statement contained a positioned DELETE or UPDATE, and the database could not find a cursor with the name specified by the application.
-
Action: Check that the cursor is open and that the application has a valid name for it. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6031 Syntax error or access violation
-
Cause: Program attempted to access a database system table, or there was an error in the SQL statement.
-
Action: Check for syntax errors, and then reissue the SQL statement. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6032 Duplicate cursor name
-
Cause: The cursor name specified already exists.
-
Action: Check the cursor name, and reissue the SQL statement. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6033 Serialization failure
-
Cause: The transaction that was processing the SQL statement was terminated to prevent deadlock.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6034 Syntax error or access violation
-
Cause: The user didn't have the privileges to execute the specified SQL statement, or the driver was unable to lock the row as needed to perform the requested operation.
-
Action: Check the SQL statement for errors. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6035 Operation aborted
-
Cause: The data source was unable to process the cancel request.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6036 Driver does not support this function
-
Cause: A function that the driver does not support was attempted.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6037 Data source name was not found and no default driver specified
-
Cause: The driver manager will use the system default database because the data source name specified was not found in the ODBC.INI file or registry and there was no default driver specified, or the ODBC.INI file could not be found.
-
Action: Check the data source name, and reissue the connection statement if you don't want to use the default database. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6038 Specified driver could not be loaded
-
Cause: The driver listed in the data source specification in the ODBC.INI file or registry, or specified by the DRIVER keyword, was not found or could not be loaded for some other reason.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6039 Driver's SQLAllocEnv() failed
-
Cause: SQLAllocEnv() allocates memory for an environment handle, and must be called prior to calling any other ODBC function. During execution of the SQL statement, the Driver Manager called the driver's SQLAllocEnv(), and the driver returned an error.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6040 Driver's SQLAllocConnect failed
-
Cause: There is no memory allocated for a connection handle because the driver returned an error when the Driver Manager called SQLAllocConnect().
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6041 Driver's SQLSetConnectOption failed
-
Cause: The Driver Manager called the Driver SQLSetConnectOption()
method, which sets connection options, and the driver returned an error.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6042 No data source or driver specified - dialog prohibited
-
Cause: Could not establish a connection because there was no data source or driver specified in the connection string. The Driver Manager only tried the connection string specified by the application, rather than displaying a dialog box and prompting the user.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6043 Dialog failed
-
Cause: The Driver Manager attempted to display the SQL Data Sources dialog box and failed, or the login dialog box failed.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6044 Unable to load translation DLL
-
Cause: The specified translation file does not exist.
-
Action: Make sure you're using the correct translation file. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6045 The data source name specified is too long
-
Cause: The attribute value for the DSN keyword was longer than the maximum specified.
-
Action: Specify a shorter data source name, or check for errors in the input string. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6046 The driver name specified is too long
-
Cause: The attribute value for the DRIVER keyword was longer than 255 characters.
-
Action: Specify a shorter value, or check the input string for errors. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6047 DRIVER keyword syntax error
-
Cause: The keyword-value pair for the DRIVER keyword contained a syntax error.
-
Action: Check the keyword specified, and see the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
-
Cause: You enabled tracing through ODBC Spy or ODBC Administrator, but the Driver Manager couldn't write to the file you specified.
-
Action: Check the path name to the trace file. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6049 Base table or view already exists
-
Cause: The database detected a table with the same name when executing a CREATE TABLE or a CREATE VIEW statement.
-
Action: Choose another name for the new table and run the SQL statement again, or drop the existing table. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6050 Base table or view not found
-
Cause: A SQL statement referenced a table or view that the database could not find.
-
Action: Check the SQL statement for errors, and modify the table name or view as necessary. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6051 Index already exists
-
Cause: A CREATE INDEX statement attempted to create an index that already exists.
-
Action: You can ignore this error and use the existing index, or drop the existing index and create it again. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6052 Index not found
-
Cause: A DROP INDEX statement attempted to drop an index that doesn't exist.
-
Action: Check the statement for errors, and see the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6053 Column already exists
-
Cause: An ALTER TABLE statement attempted to add the name of a column that is already in the table. All column names must be unique within a table.
-
Action: Specify a unique name for the new column, and then re-execute the statement. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6054 Column not found
-
Cause: A SQL statement contained a reference to at least one column name that doesn't exist.
-
Action: Check the SQL statement for errors, and see the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6055 No default for column
-
Cause: An INSERT...VALUES statement did not specify a value for each column that has both a NOT NULL constraint and no default value; or the statement may have specified too many values.
-
Action: Check the table definition and specify values for all columns for which defaults aren't defined. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6056 General error
-
Cause: Error with this implementation of ODBC.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6057 Memory allocation failure
-
Cause: The database is out of heap memory or object cache memory.
-
Action: Restart the application. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6058 Invalid column number
-
Cause: The number of column names specified in a CREATE VIEW statement did not correspond to the number of columns listed in the SELECT clause. If column names are specified in a CREATE VIEW statement, exactly one name must be specified for each column or expression in the SELECT clause.
-
Action: Specify one view column name for each column in the SELECT clause. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6059 Program type is out of range
-
Cause: The value specified by the argument was not a valid SQL datatype.
-
Action: Check the calling program for errors. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6060 SQL datatype is out of range
-
Cause: There was an attempt to assign a value that doesn't match any of the valid values for the SQL datatype.
-
Action: Check the assignment, and try again. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6061 Operation canceled
-
Cause: A function was canceled before completing execution.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6062 Invalid argument value
-
Cause: The failing call contains an argument with an invalid value.
-
Action: Check for syntax errors, and reissue the statement with valid argument values. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6063 Function sequence error
-
Cause: An asynchronously executing function was called for the SQL statement, and was still executing when this function was called.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6064 Operation invalid at this time
-
Cause: This error is function-specific.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6065 Invalid transaction code specified
-
Cause: The specified transaction code does not correspond to an existing valid transaction. A COMMIT or ROLLBACK statement was expected.
-
Action: Check that the application uses a valid transaction code. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6066 No cursor name available
-
Cause: There is no open cursor for the statement.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6067 Invalid string or buffer length
-
Cause: A result string was too large for the allocated buffer, or the value is not valid.
-
Action: Check the SQL statement for errors, or allocate a larger buffer. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6068 Descriptor type is out of range
-
Cause: This descriptor type is not valid for the version of ODBC supported by the driver.
-
Action: Check the descriptor type, and try again. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6069 Operation type is out of range
-
Cause: The value specified is not valid for the version of ODBC supported by the driver.
-
Action: Check the value, and try again. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6070 Invalid parameter number
-
Cause: The number of arguments specified does not match the number of parameters.
-
Action: Check the SQL statement for syntax errors. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6071 Invalid scale value
-
Cause: The value specified for the argument was outside the range of values supported by the data source for a column of the specified datatype.
-
Action: Check the value, and See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6072 Function type is out of range
-
Cause: An invalid ODBC function was specified.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6073 Information type is out of range
-
Cause: An invalid ODBC information type was specified.
-
Action: Check the value, and See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6074 Column type is out of range
-
Cause: There was an attempt to insert a value with an invalid type in the specified column.
-
Action: Check the column type, and try again. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6075 Scope type is out of range
-
Cause: An invalid scope type was specified.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6076 Nullable type is out of range
-
Cause: An invalid value was specified for determining whether to return columns with NULL values.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6077 Uniqueness option type is out of range
-
Cause: An invalid index type was specified.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6078 Accuracy option type is out of range
-
Cause: An invalid value was specified for determining whether to return results.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6079 Direction option is out of range
-
Cause: An invalid value was specified for determining whether the Driver Manager fetches the next driver or data source name description in the list, or the search starts from the beginning of the list.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6080 Invalid precision value
-
Cause: The maximum precision of the value of a column was exceeded or is invalid. This is an abnormal condition.
-
- POL-6081 Invalid parameter type
-
Cause: Invalid command-line parameters were specified.
-
Action: Check the online help for the set of valid parameters, and then reissue the SQL statement. See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6082 Fetch type out of range
-
Cause: An invalid value was specified for determining how to move through the result set.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6083 Row value out of range
-
Cause: An invalid value was specified for determining how to move through the result set.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6084 Concurrency option out of range
-
Cause: An invalid value was specified for determining locking level.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6085 Invalid cursor position
-
Cause: A row that was deleted or in error was specified for the cursor position.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6086 Invalid driver completion
-
Cause: An invalid value was specified for determining whether the driver or Driver Manager should prompt for additional connection information.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6087 Invalid bookmark value
-
Cause: An invalid value was specified for retrieving the row set with a bookmark.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6088 Driver not capable of this operation
-
Cause: The cause is ODBC function-specific.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6089 Timeout expired
-
Cause: The timeout period expired before the data source returned the result set.
-
Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.
- POL-6090 No data at execution - values pending
-
Cause: This is an abnormal condition.
-
- POL-6091 Dynamic cursor is not supported in read committed mode.
-
Cause: Dynamic cursor is not supported in the read committed mode.
-
Action: Change to a supported combination of isolation levels and cursor types.
- POL-6100 Transaction has been rolled back due to a deadlock
-
Cause: An application caused a deadlock.
-
Action: The transaction has been automatically rolled back. Data should be resubmitted if necessary.
1.10 POL 8000–8090 Java Stored Procedures/Triggers Messages
Errors detected when attaching, detaching or executing stored procedures or triggers are normally reported through the JDBC, ODBC, or SQL layers. If the error occurs while executing a command through the Java Access Classes, a general POLException
error appears and is reported through the Java Virtual Machine.
- POL-8000 Could not start the Java Virtual Machine
-
Cause: The environment variable PATH may not contain a reference to javai.dll
-
Action: Include the JDK_HOME\
bin
directory in the PATH variable where JDK_HOME
is the root directory of the Java development environment.
- POL-8001 Could not find a Java system class
-
Cause: CLASSPATH environment variable may not have been set correctly.
-
Action: Include JDK_HOME\lib\classes.zip in the CLASSPATH environment variable.
- POL-8002 Exception raised in getMethod() call
-
Cause: Incompatible version of Java system classes.
-
Action: Make sure you have the JavaSoft JDK 1.1.4 (or later), or any Java virtual machine that is 100% compatible with it.
- POL-8003 Null method ID
-
Cause: Could not create an instance of Oracle Lite Java class loader.
-
Action: Check and make sure that the CLASSPATH contains a reference to the file jsp.jar.
- POL-8004 Java package not found
-
Cause: A package name mentioned in a fully-qualified Java class name does not exist.
-
Action: Check the class name, and correct it if necessary.
- POL-8005 Given name is not a package name
-
Cause: A package name mentioned in a fully-qualified Java class name is not the name of a package.
-
Action: Check the class name, and correct it if necessary.
- POL-8006 Error in creating package
-
Cause: Internal error.
-
Action: If the product has been installed correctly and the error persists, call
Oracle Customer Support for assistance.
- POL-8007 Error in finding package
-
Cause: The Oracle Lite class loader cannot find the package name.
-
Action: Check the package names in the fully-qualified class name.
- POL-8008 Error in naming the blob
-
Cause: A blob with the same name already exists.
-
Action: Choose another name for the blob.
- POL-8009 Class already exists
-
Cause: You specified the source or class path for a Java class that you are trying to attach to a table, but a Java class with the same name and different content already exists in the Oracle Lite database.
-
Action: Rename the class.
- POL-8010 Class with the specified name was not found
-
Cause: The Oracle Lite Java class loader cannot find a class with the name you specified in the Attach statement.
-
Action: Specify the correct name or modify the CLASSPATH to search the appropriate directory.
- POL-8011 Null class ID
-
Cause: Either jsp.jar is not in your CLASSPATH or a null is used as an Oracle Lite class reference.
-
Action: If you are using JAC or the C kernel interface (OKAPI), specify a non-null object reference in the API function call.
- POL-8012 Given class name is a package name
-
Cause: A package with the same name already exists.
-
Action: Choose a different name for the class.
- POL-8013 Error in finding Java class <schema_name>.<class_name>
-
Cause: Could not find the specified class object.
-
Action: Verify that the class exists.
- POL-8014 Error in creating blob for class
-
Cause: Could not create the blob attribute for a class.
-
Action: Look for other errors on the error stack.
- POL-8015 Error in finding blob size
-
Cause: Could not get the size of a blob object.
-
Action: Check that the blob object exists and is the size you expect.
- POL-8016 Error in reading blob value
-
Cause: Error reading the blob associated with a class definition when loading a class.
-
Action: Internal error. If the product has been installed correctly and the error persists, call
Oracle Customer Support for assistance.
- POL-8017 Error in reading class file
-
Cause: Error reading the class definition when loading a class.
-
Action: Include the directory in which the class file resides in the CLASSPATH environment, and restart the application.
- POL-8018 Error in setting blob value
-
Cause: Could not set the value of a blob.
-
Action: Verify that the values are correct and that the blob data is readable.
- POL-8019 Error in creating group
-
Cause: Unable to create the Java Classes group in the database.
-
Action: Internal error. If the product has been installed correctly and the error persists, call
Oracle Customer Support for assistance.
- POL-8020 Error in finding group
-
Cause: Unable to find the Java Classes group in the database.
-
Action: Use the Oracle Lite Designer to verify that the Java Classes group exists.
- POL-8021 Error in initializing environment
-
Cause: This is an abnormal condition.
-
- POL-8022 Error in finalizing environment
-
Cause: This is an abnormal condition.
-
- POL-8023 Error in creating database
-
Cause: This is an abnormal condition.
-
- POL-8024 Database not initialized
-
Cause: This is an abnormal condition.
-
- POL-8025 Exception raised in define class
-
Cause: Can be caused by a variety of errors when defining a class or attaching a Java class to an Oracle Lite class.
-
Action: Examine the calling parameters and error stack for more information.
- POL-8026 Failed to make or delete a global reference
-
Cause: The Java object reference is corrupted.
-
- POL-8027 The Java class already exists
-
Cause: A Java class with the same name already exists.
-
Action: Choose another name for the class.
- POL-8028 Error in calling a Java method
-
Cause: Most commonly refers to a problem when converting between Java and Oracle Lite datatypes.
-
Action: Check the calling parameters.
- POL-8029 The number of arguments given is not the same as the number of arguments in the method
-
Cause: The number of arguments specified does not match the number of arguments expected by the method.
-
Action: Check for syntax errors, and then reissue the statement.
- POL-8030 Wrong JNI signature. Database may be corrupted.
-
Cause: Internal error. The signature of Java methods recorded in the database has been corrupted.
-
Action: If the product has been installed correctly and the error persists, call
Oracle Customer Support for assistance.
- POL-8031 Null value cannot be used as an actual argument for a formal argument of Java primitive type
-
Cause: Attempt to pass a NULL value as an actual argument for a formal argument of Java primitive type in a Java stored procedure.
-
Action: Initialize these columns with a non-NULL value before invoking the Java procedure.
- POL-8032 Bad argument value
-
Cause: The failing call contains an argument with an invalid value.
-
Action: Check for syntax errors, and reissue the statement with valid argument values.
- POL-8033 No object given for instance method
-
Cause: A method was invoked without supplying an instance for the method to operate on.
-
Action: Supply an object to the method.
- POL-8034 This feature is not yet supported
-
Cause: There was an attempt to use a feature or function that Oracle Lite does not yet support.
-
Action: Rewrite the statement, and eliminate the call to the unsupported feature or function.
- POL-8035 No such attribute or method
-
Cause: The specified method or attribute could not be found.
-
Action: Check that the specified method or attribute exists and that it is attached to the correct class.
- POL-8036 Result buffer is too small
-
Cause: The returned value from a Java stored procedure is too long to fit into the result buffer allocated for it.
-
Action: Specify a larger buffer.
- POL-8037 Argument count of the trigger method does not match the number of argument names
-
Cause: There must be just as many argument names supplied when calling a method as were defined when declaring the method.
-
Action: Correct the number of arguments supplied in the call.
- POL-8038 Error in opening a file to read the class body
-
Cause: Your system detected an error when trying to read a class file.
-
Action: Check the file name, class path, and anything else that could affect file operations.
- POL-8039 ROWID (OID) cannot be used in a BEFORE-INSERT (BEFORE-CREATE) or an AFTER-DELETE
-
Cause: Since a row does not exist before it is inserted or after it is deleted, the use of ROWID in before-insert or after-delete triggers is prohibited.
-
Action: Don't use ROWID in these types of triggers.
- POL-8040 New column (attribute) value cannot be used for AFTER-INSERT (AFTER-CREATE), AFTER-UPDATE or any DELETE trigger
-
Cause: A NEW column value was used for an after-insert, an after-update, or delete trigger.
-
Action: If you want to pass the NEW value to the Java stored procedure, consider using a before trigger.
- POL-8041 Old column (attribute) value cannot be used for AFTER-DELETE trigger
-
Cause: After-delete triggers have neither OLD nor NEW values.
-
Action: Use a before-delete trigger if you must use attributes.
- POL-8042 NULL string is not allowed for argument name
-
Cause: Program tried to create a trigger and specified a positive argcount
, but a column (attribute) name is null.
-
Action: Check the parameter in the calling program.
- POL-8043 POP attempted on empty connection stack
-
Cause: This is an abnormal condition.
-
- POL-8044 PUSH attempted on full connection stack
-
Cause: This is an abnormal condition.
-
- POL-8045 TOP_CONN attempted on an empty connection stack
-
Cause: This is an abnormal condition.
-
- POL-8046 Attribute from which trigger is being deleted does not exist
-
Cause: There was a reference to an invalid attribute name.
-
Action: Check the attribute name, and try deleting the trigger again.
- POL-8047 Java source file path does not exist
-
Cause: There was a reference to an invalid path name.
-
Action: Check the path name, and try again.
- POL-8048 Access denied to Java source file
-
Cause: The system denied access to a necessary Java source file.
-
Action: Correct the access control on the required file.
- POL-8049 Arguments to the okCreateTrigger() function are inconsistent
-
Cause: Program supplied an invalid trigger type when creating a trigger.
-
Action: Correct the trigger type parameter in the calling program.
- POL-8050 Invalid attribute type
-
Cause: The domain of an attribute could not be mapped to a known type.
-
Action: Define the attribute domain in terms of known datatypes.
- POL-8051 The update attributes supplied were invalid for the class
-
Cause: The update attributes supplied to an update trigger were invalid or missing.
-
Action: Check the calling program for errors, and supply the missing attributes.
- POL-8052 COMMIT and ROLLBACK statements are not valid in a Java stored procedure
-
Cause: There was a reference to COMMIT and ROLLBACK statements in a Java stored procedure.
-
Action: Remove the references to COMMIT and ROLLBACK, and reissue the statement.
- POL-8053 No constructor matching the given constructor argument found
-
Cause: Can't find a matching Java constructor with the specified constructor arguments.
-
Action: Check the corresponding ALTER TABLE statement, and make sure the sequence of formal arguments in the constructor matches the sequence of the columns in the constructor sub-clause.
- POL-8054 Triggers must return void
-
Cause: Trigger methods can't return a value.
-
Action: Check the declaration of the method for errors.
- POL-8055 Java class is already attached to the table or class
-
Cause: The Java class specified is already attached to the table or class.
-
Action: Check the name and try again.
- POL-8056 Can't delete SYSTEM classes
-
Cause: There was an attempt to delete a system class.
-
Action: Check the class name, and try again. Don't try to delete a system class.
- POL-8057 Java method returned a long value that is outside the range
-
Cause: The Java method returned a long value that is outside the range of long values accepted by Oracle Lite.
-
Action: Check your code for errors, and make sure that all values returned are within the valid range.
- POL-8058 Row and statement triggers cannot be created in a single call
-
Cause: Row and statement triggers cannot be created in a single call to an okCreate
trigger or in a single SQL statement.
-
Action: Check the call for errors and try again.
- POL-8059 Trigger kind parameter missing
-
Cause: Call to okCreate
trigger failed to specify what kind of trigger to create.
-
Action: Check the call for errors and try again.
- POL-8060 Statement level triggers cannot have arguments
-
Cause: You have specified an argument to the method in a statement level trigger.
-
Action: Don't use any arguments.
- POL-8061 Trigger not found
-
Cause: The specified trigger could not be found.
-
Action: Check the trigger name in your code.
- POL-8062 No triggers exist for the table
-
Cause: Program attempted to drop a trigger that doesn't exist.
-
Action: Check the trigger name in your code.
- POL-8063 No update attributes supplied for a BEFORE-UPDATE or AFTER-UPDATE trigger
-
Cause: No update attributes were specified in a trigger that requires them.
-
Action: Supply the missing parameters, and try again.
- POL-8064 Trigger signature does not match the actual arguments
-
Cause: Data types of the procedure argument and the values specified in the trigger are not compatible.
-
Action: Correct the procedure arguments or the specified values in the trigger.
- POL-8065 Only oracle.pol.jac.POLconnection and java.sql.Connection are allowed in statement level triggers
-
Cause: You are attempting to create a statement-level trigger whose procedure requires arguments other than oracle.pol.jac.POLconnection and java.sql.Connection.
-
Action: Use a procedure which takes no arguments.
- POL-8066 Instance method cannot be used for BEFORE-CREATE (BEFORE-INSERT) and AFTER-DELETE triggers, or for any statement-level triggers, or by different classes
-
Cause: You are attempting to create a before insert or after delete trigger using a row-level stored procedure.
-
Action: Use a statement-level stored procedure.
- POL-8077 Attribute values cannot be specified as arguments when creating multiple update triggers in one statement
-
Cause:
-
Action:
- POL-8078 UPDATE trigger method argument can only be the attribute for which the trigger is created
-
Cause:
-
Action:
- POL-8079 Error translate multibyte string to Unicode string
-
Cause: Windows is unable to translate a multi-byte string to Unicode given the current character set specification.
-
Action: Correct the character set definition or eliminate the illegal character.
- POL-8080 Trigger name already exists
-
Cause:
-
Action:
- POL-8081 The created procedure is registered to a Java method that has a return value
-
Cause:
-
Action:
- POL-8082 The created function is registered to a Java method that returns void
-
Cause:
-
Action:
- POL-8083 No Java class attached to this table
-
Cause:
-
Action:
1.26 Oracle Lite Messages Help/Contacting Customer Support
Each message code follows the format Product ID-nnnnn, where nnnnn is an integer. Messages specific to an operating system or another Oracle product are not listed here, although the message code may be listed with a reference to another Oracle document.
Each description contains the message number and text as well as the following:
- Error message text
-
Cause: a description of the possible causes of the error.
-
Action: a description of the possible actions you can take to resolve the error.
Items in the error message text which appears in curly braces, for example, {publication name}, are replaced with values for objects which are then returned by the error message.
1.26.1 Abnormal Condition
Sometimes you may encounter an error that is known as an abnormal condition. These are errors for which the exact cause is not clear. The following sections describe the probable causes of abnormal conditions and the actions you can take to solve them.
1.26.1.1 Cause
Abnormal conditions may arise from one of the following causes:
1.26.1.2 Action
You should first contact your DBA and/or system administrator to determine if the message was caused by something other than Oracle Lite. If you determine that the message was not the result of user error or a system problem, you should take the following steps:
-
Write down the message number and its text.
-
Write down the circumstances that led up to the message. Try to recall the actions you took, the objects involved (if any), and the exact sequence of keys that you pressed prior to the message.
-
Call Oracle Customer Support for assistance.
1.26.2 About Java Access Class Exceptions
The Java Access Class errors are processed through the Java exception handling mechanism. Errors appear with names such as the following:
oracle.pol.jac.POLGroupNotFoundException
There are no error codes associated with these Java exceptions. If an internal error code causes a Java exception, the general oracle.pol.jac.POLException
appears and the internal error code that caused the exception is reported.
1.26.3 Oracle Customer Support
Some errors (such as internal errors) require you to call Oracle Customer Support to report the error. When you call Customer Support, you should have the following information available:
-
Your name, company, and Oracle Support ID number.
-
The hardware, operating system, and release number of the operating system on which Oracle Lite is running.
-
The complete version number of Oracle Lite that you were using when you encountered the error, including revision number and port release number, if any.
-
All other products and version numbers in use when the error occurred.
-
If you encountered one or more error codes or messages, the exact code numbers and message texts, in the order they appeared.
-
A description of the problem, including any unusual conditions.
-
The problem severity, according to the following codes:
-
1 = Program not usable. Critical impact on operations of a production system.
-
2 = Program not usable. Operations severely restricted.
-
3 = Program usable with limited functions. Not critical to overall operations.
-
4 = Problem circumvented by customer. Minimal effect, if any, on operations.