1
Messages

Cause: Either the program heap memory or the shared memory area is out of space.

Action: Restart the application.

Cause: Program attempted to allocate a chunk of memory larger than 64K bytes under 16-bit windows.

Action: Work with smaller chunks of memory.

Cause: An invalid pointer was detected by the database.

Action: Restart the application.

Cause: A possible memory corruption was detected when freeing an object.

Action: If this error persists, restart the application.

Cause: Your program or the database attempted to free an array that was already free.

Action: No action required.

Cause: An invalid pointer was detected by the database.

Action: Restart the application. If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: An operation wrote beyond the end of a dynamic array.

Action: Check your program to be sure you are not writing more bytes than were allocated for the dynamic array. If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: Program attempted to save a data buffer into a dynamic array that is too small.

Action: Increase the size of the dynamic array. If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: Database needed a low-level lock but could not find one available.

Action: Retry the operation. If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: A low-level lock did not release as expected.

Action: If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: An operation on a low-level lock failed.

Action: If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: An operation on a low-level lock failed.

Action: If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: An error occurred when creating an internal event.

Action: If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: An error occurred when deleting an internal event.

Action: If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: An error occurred while a thread or session was waiting for an internal event.

Action: If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: An error occurred while waiting for an internal event.

Action: If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: An error occurred while waiting for an internal event.

Action: If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: An error occurred when setting an event, possibly when waking a waiting thread.

Action: If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: The database or your program is attempting to use more than the operating system defined number of wait events. (64 on Windows NT)

Action: If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: The database could not create the shared memory cache area.

Action: The operating system could be out of virtual memory. Call Oracle Customer Support for assistance.

Cause: The database could not release the shared memory area.

Action: Reboot the system, call Oracle Customer Support for assistance.

Cause: The database could not allocate a page of shared memory for the cache.

Action: Shut down all Oracle Lite sessions, and restart.

Cause: The database detected a possible corruption in the shared memory.

Action: Shut down all Oracle Lite sessions and restart, or call Oracle Customer Support for assistance.

Cause: The database detected an invalid internal pointer.

Action: Call Oracle Customer Support for assistance.

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.

Cause: SQL attempted to divide by zero.

Action: Check the SQL statement for syntax errors, and then reissue the statement.

Cause: A result string was too large for the allocated buffer and characters were lost from the right side of the string.

Action: Check the SQL statement for errors, or allocate a larger buffer.

Cause: The database detected an invalid attempt to convert characters in a string to a date or number.

Action: Check the string, and remove the invalid characters.

Cause: The database detected an error while executing the SUBSTR SQL function.

Action: Check the input string and the function parameters for errors, and modify as necessary before reissuing the SQL statement.

Cause: The database detected an error while executing the SQL TRIM function.

Action: Check the input string and the function parameters, and modify as necessary before reissuing the SQL statement.

Cause: A multiplication operation generated a result larger than 38 digits.

Action: Check the input string, and modify as necessary.

Cause: The database ran out of memory while executing a LIKE or TO_CHAR function.

Action: Simplify the input strings, if possible.

Cause: A NULL value was detected by the database, but Oracle Lite cannot tell you about it because the application did not provide an indicator variable.

Action: Provide an indicator variable, and re-compile the application.

Cause: Reserved for future use.

Action: No action required.

Cause: Invalid escape sequence detected by the database in the search string provided to the LIKE function.

Action: Check the search string for errors, or simplify the search string.

Cause: The escape character in the search string of the LIKE function must be a single (possibly multi-byte) character.

Action: Check the search string.

Cause: An INTERVAL computation exceeded the precision of the column or datatype.

Action: Modify the column size, or choose a larger datatype.

Cause: Oracle Lite could not read the system clock.

Action: Report this as an "Abnormal Condition".

Cause: Year exceeds 9999 or an error occurred while adding an interval to a date column.

Action: Check the input string for errors. If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: Character string could not be converted to a valid DATE, TIME, or TIMESTAMP value.

Action: Check the input string, and modify it as necessary. The input string must match one of the formats for literal strings, or as specified by the format string in a TO_DATE function.

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: The datatype of the column specified for the TRUNC function cannot be rounded.

Action: Check for syntax errors, and reissue the SQL statement.

Cause: The TO_CHAR function cannot operate on the specified datatype.

Action: See the online help for the TO_CHAR function, and then correct the SQL statement.

Cause: The format string for a TO_NUMBER conversion was invalid.

Action: Check the format string for errors, and then reissue the SQL statement.

Cause: The input string in a TO_NUMBER conversion was invalid.

Action: Check the input string for errors, and then reissue the SQL statement.

Cause: The date or time is not valid.

Action: Check the input value for errors.

Cause: The LIKE function can only operate on character data.

Action: Convert or cast the data to a character value, or check the SQL statement for errors.

Cause: Certain transformations between datatypes are prohibited, for example DATE to NUMBER.

Action: Check the SQL syntax and try again.

Cause: The result of a string operation exceeds 32000 bytes.

Action: Check the SQL syntax, and try again.

Cause: The search pattern in a LIKE clause contains an illegal or missing character following the escape character.

Action: Check the search pattern, and try again.

Cause: The specified database parameter, NLS_SORT, is invalid

Action: Use only valid NLS_SORT value.

Cause: Calling program failed to supply a pointer for a return value.

Action: Call Oracle Customer Support for assistance.

Cause: Calling program failed to supply a pointer for a required value.

Action: Call Oracle Customer Support for assistance.

Cause: Calling program failed to supply a pointer to required options.

Action: Call Oracle Customer Support for assistance.

Cause: Internal memory allocation error.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error. Calling program failed to supply a context pointer.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error. Calling program failed to supply a pointer to a name buffer.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error. Calling program failed to supply an object reference.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error. The database detected a negative volume ID when opening a database file.

Action: Call Oracle Customer Support for assistance.

Cause: The system reported an error while performing a disk seek operation.

Action: Check your hard drive, or reboot the operating system.

Cause: The system reported an error while performing a disk read operation.

Action: Check your hard drive, or reboot the operating system.

Cause: The system reported an error while performing a disk write operation.

Action: Check your hard drive, or reboot the operating system.

Cause: The database failed to open a database or log file, or the file header was corrupted. Possibly caused by using an incorrect password to decrypt the database.

Action: Give the correct password, check your hard drive, or reboot the operating system.

Cause: System reported an error while closing a disk file.

Action: Check your hard drive, or reboot the operating system.

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: A database file with the same volume ID is already mounted.

Action: Use the DBINFO utility to check the volume IDs of the database files.

Cause: Program attempted to open too many internal group files.

Action: Call Oracle Customer Support for assistance.

Cause: Program attempted to open too many database files.

Action: The maximum number of open database files is system-dependent.

Cause: Either the hard drive is out of space or the extent size specified when the database was created is too small.

Action: Check the space available on the hard drive, or recreate the database file with more extents.

Cause: Internal error. The database detected a corrupted object ID or attempted to reference an object that has been freed.

Action: Call Oracle Customer Support for assistance.

Cause: The database detected a corrupted file header.

Action: Check your hard drive for errors. If the error persists, call Oracle Customer Support for assistance.

Cause: Database name cannot exceed 128 characters.

Action: Choose a shorter database name.

Cause: The database could not open the specified database file.

Action: Check the database name and verify that the file exists. Oracle Lite looks for database files in the current working directory. If you are using ODBC, Oracle Lite looks for database files in the directory specified by the data source name specified at connect time.

Cause: Internal error. The database is unable to find a free page buffer.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error. The page buffer table may be corrupted.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error caused by referencing an object that has been deleted.

Action: Call Oracle Customer Support for assistance. If using OKAPI directly, you need to okFix the object.

Cause: Internal error caused by referencing an object that has been deleted. Each object in the database, such as a row has a unique object identifier (OID) that identifies the location of the object in secondary storage. Each database file is divided into fixed size chunks called disk pages. An OID can become invalid when the:

• disk page being referred by the OID does not exist in the database file.

• physical read or write of the disk page fails due to an operating system related error.

• address of the object (as indicated by the internal encoding in the OID) in the disk page is outside the page.

• object is not found in the page.

Action: If using OKAPI directly, you need to okFix the object. Otherwise call Oracle Customer Support for assistance.

Cause: Program attempted to read a portion of a BLOB that does not exist.

Action: Check the offset or length parameters in the call, and try again.

Cause: The application or the database asked for an illegal comparison operation.

Action: Call Oracle Customer Support for assistance.

Cause: The application attempted to update an object belonging to a different class. This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: Internal error.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error.

Action: Call Oracle Customer Support for assistance.

Cause: Program attempted to insert a row where a unique or primary key constraint would be violated.

Action: Modify the SQL statement or object attribute, and reissue it.

Cause: Primary key values cannot be null.

Action: Specify a primary key value.

Cause: The database could not find a record matching the search key.

Action: This is generally not a fatal error and should be handled by the application.

Cause: Internal error.

Action: Call Oracle Customer Support for assistance.

Cause: The total length of all columns in a multi-column index key exceeds 1000 bytes.

Action: Specify a shorter set of columns.

Cause: Internal error. The database found an invalid page in an index.

Action: Drop and recreate the index.

Cause: Internal error. The database found a bad index.

Action: Drop and recreate the index.

Cause: The database could not locate an internal group file with the specified name.

Action: Call Oracle Customer Support for assistance.

Cause: The database or application attempted to perform an index search on an attribute or column with no index.

Action: Create the index.

Cause: An internal group file with the same class name already exists.

Action: Choose another name for the file.

Cause: Internal error.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error. Invalid index type.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error.

Action: Call Oracle Customer Support for assistance.

Cause: The database cannot sort LONG, LONG VARCHAR, or LONG VARBINARY columns.

Action: If the values are unique in the first 1000 bytes, create an index.

Cause: The application or database may have: closed a database while transactions were still outstanding, freed a transaction still in progress, or reused a transaction handle when the transaction was still in progress.

Action: COMMIT or ROLLBACK any outstanding transactions.

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: There are two threads of execution, and each one is waiting for the other to release a resource.

Action: Close some windows, or restart the application.

Cause: One connection issued a SELECT FOR UPDATE NOWAIT, but the current row is locked by another connection.

Action: The error is reported to allow your application to proceed when a row is locked by another connection (rather than waiting until the other connection frees the lock). You may want to perform some other processing and then try to acquire the lock later.

Cause: Internal error.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error, or the shared memory cache is corrupted.

Action: Call Oracle Customer Support for assistance.

Cause: Either you are attempting to update a read-only database, or you are calling a stored procedure using a SELECT statement without the FOR UPDATE clause.

Action: Verify that your ODB file is in read-only mode and change it if necessary.

Cause: The database detected that an invalid cursor is attempting to scan a class or index.

Action: Restart the application.

Cause: The database detected that an invalid cursor is attempting to scan a class or index.

Action: Restart the application.

Cause: Internal error.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error.

Action: Call Oracle Customer Support for assistance.

Cause: Attempting to decrypt an non-encrypted database.

Action: No action required.

Cause: The database failed to open a database file. This can occur when the mounting database is created using a different collation sequence than the one already mounted.

Action: Avoid mounting database files with different collation sequences at the same time.

Cause: Calling program supplied a null object pointer.

Action: Specify an object pointer.

Cause: Calling program supplied a null return pointer.

Action: Specify a return pointer.

Cause: Calling program supplied a null name pointer.

Action: Specify a name pointer.

Cause: Calling program supplied a null environment handle.

Action: Specify an environment handle.

Cause: Calling program supplied an invalid environment handle.

Action: Specify a valid environment handle.

Cause: Calling program supplied a null class pointer.

Action: Specify a class pointer.

Cause: Calling program supplied a null attribute pointer.

Action: Specify an attribute pointer.

Cause: The attribute position number supplied by the calling program exceeds the number of attributes in the class.

Action: Specify an attribute position number that is equal to, or smaller than, the number of attributes in the class.

Cause: Calling program supplied a null buffer pointer which should point to attribute data.

Action: Specify a buffer pointer that points to attribute data.

Cause: Calling program supplied a null pointer where a valid pointer is needed.

Action: Specify a valid pointer.

Cause: Calling program supplied a null database handle.

Action: Specify a valid database handle.

Cause: Calling program supplied a null group handle.

Action: Specify a valid handle for the group object.

Cause: Attempting to create a new database file while a transaction is active.

Action: COMMIT or ROLLBACK any open transactions.

Cause: Calling program attempted to reference a database file that is not connected.

Action: Open the database file that matches the volume ID in the object being fetched.

Cause: Calling program attempted to reference a database file that is not connected or that may be corrupted.

Action: Open the database file that matches the volume ID in the object being updated.

Cause: Calling program attempted to open too many database connections.

Action: Close some connections.

Cause: Calling program attempted to open a database with the same volume ID as the one already open.

Action: Database volume IDs must be unique on the system. Use DBINFO program to verify the ID.

Cause: 6 databases or catalogs are already connected.

Action: Close some connections.

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: The database detected an invalid transaction ID.

Action: Call Oracle Customer Support for assistance.

Cause: The database detected a resource deadlock between threads, sessions, or tasks.

Action: Restart the application.

Cause: The okTransact() function was called with an invalid argument.

Action: Check the function syntax, and then reissue the call.

Cause: Program attempted to set the isolation level to an illegal value.

Action: Check the argument in the call, and then try again.

Cause: You called a stored procedure using the SELECT statement without the FOR UPDATE clause. This procedure then tried to issue the SELECT statement with the FOR UPDATE clause.

Action: Modify your outer SELECT statement to use the FOR UPDATE clause.

Cause: Program attempted to register a group but found that the group name already exists.

Action: Choose another name for the new group.

Cause: Internal error. The database detected a corrupted group object.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error. Don't attempt to delete meta objects.

Action: Call Oracle Customer Support for assistance.

Cause: Internal error. Calling program attempted to create a BLOB in the temporary object group.

Action: Call Oracle Customer Support for assistance.

Cause: The application is trying to insert a NULL value into an attribute or column, which would violate a NOT NULL constraint.

Action: Supply a value for the attribute or column.

Cause: The okGetAttrVal() function was called without copying the return value to a buffer.

Action: Supply a buffer and set the flag or fix the object before reissuing the function call.

Cause: Internal error. Object cache may be corrupted.

Action: Restart the application, and call Oracle Customer Support for assistance.

Cause: Invalid lock mode specified in calls to the okLoadGroup() or okFixObj() functions.

Action: Check the lock mode parameter for errors, and then reissue the function call.

Cause: There was an attempt to register another group, which would exceed the number of groups allowed in a database.

Action: Use fewer groups.

Cause: There was an attempt to update an object that is not fixed.

Action: Call the okFixObj() function before updating the object.

Cause: The buffer specified in the okGetAttrVal() function call is too small for the data to be returned.

Action: Specify a larger buffer for the return value.

Cause: Calling program attempted to add an attribute to a class (or a column to a table) without defining a non-NULL default value where a NOT NULL constraint is also present.

Action: Specify a non-NULL default value.

Cause: Your insert, delete, or update statement has resulted in the violation of a foreign key constraint.

Action: Check the values used in the statement and correct them.

Cause: Your ALTER TABLE statement is attempting to create a primary key for a table that already has one.

Action: Drop the existing primary key first.

Cause: Your ALTER TABLE statement attempted to drop a named constraint where none exists.

Action: Check that the constraint exists, or check the ALTER TABLE statement for syntax errors.

Cause: Your ALTER TABLE statement attempted to drop a NOT NULL constraint.

Action: Recreate the table without the NOT NULL constraint.

Cause: You are attempting to drop an index that does not exist.

Action: Check the index name, and then reissue the SQL statement.

Cause: Check constraint defined in the table/class is violated.

Action: Correct the new data value being inserted or updated.

Cause: You are using an unsupported expression or an SQL function such as ROUND() in a check constraint.

Action: Simplify the check constraint definition or define triggers to implement some check constraints.

Cause: You are using a duplicate constraint (primary key or check) name.

Action: Correct the check constraint definition and provide unique names for constraints.

Cause: A class with the same name already exists.

Action: Choose another name for the new class.

Cause: There was an attempt to define a relationship with a class that has not been declared.

Action: Declare the referenced class, and then define the relationship.

Cause: There was an attempt to reference a class that was already deleted.

Action: Check the class name.

Cause: Could not find an attribute or method with the specified name for the class.

Action: Check the name, and try again.

Cause: An attribute or column with that name already exists.

Action: Choose another name.

Cause: Invalid index type in a call to okCreateIndex().

Action: Check the index type parameter.

Cause: Invalid direction parameter in a call to okIterate().

Action: Check the parameter, modify as necessary, and reissue the call to okIterate().

Cause: Iterator number is invalid or its state is corrupted.

Action: Check the iterator number.

Cause: Cursor is invalid, or its state is corrupted.

Action: Check the cursor number.

Cause: Calling program supplied an invalid search operator in okCreateIterator().

Action: Check the search conditions, and reissue the function call.

Cause: Calling program supplied an invalid search connective in okCreateIterator().

Action: Specify a valid connective, and reissue the function call.

Cause: The database detected too many open iterators at one time.

Action: Close some iterators.

Cause: Ordered iterator cannot be created because there is no index for ORDER BY attribute.

Action: Create an index for the ORDER BY attribute and reissue the function call.

Cause: Ordered iterator cannot be created because the class might have subclasses and isImmediate flag is false.

Action: Set isImmediate flag to true and reissue the function call.

Cause: Calling program attempted to create a relationship between two classes or tables where a relationship already exists with either the parent attribute, the column, or the child attribute or column. Attributes can only participate in one parent-child relationship.

Action: Simplify the object hierarchy.

Cause: Calling program attempted to delete a relationship using okDeleteRel() but the relationship was not found.

Action: This is a non-fatal error, and no action is required.

Cause: A relationship to another object cannot be broken.

Action: Drop the dependent object first, and then try deleting the object.

Cause: Calling program passed an invalid relationship type parameter in call to okCreateRel().

Action: Check the parameter, and then reissue the function call.

Cause: The database cannot find one of the attributes specified in the relationship.

Action: Check the parameters specified in the call to okCreateRel().

Cause: Classes in a relationship must exist in the same database file.

Action: Check the parameters to okCreateRel(), and reissue the function call.

Cause: The database was unable to record an additional relationship in an attribute, possibly because the attribute was defined with a fixed size.

Action: Redefine the class, making the attribute a dynamic array of relationship references.

Cause: The attribute was defined as permitting only a single parent relationship.

Action: Redefine the class, making the attribute a dynamic array of relationship references.

Cause: Relationship attributes must be defined as references to instances of the related class. Either the from or to pointer in this case is defined as a reference to a different class.

Action: Redefine the class, and make the attribute a reference to the correct class.

Cause: Calling program attempted a BLOB operation on a non-BLOB attribute.

Action: Check the parameters, and reissue the operation.

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: The named object cannot be found in the directory.

Action: Check the object name, and then try again.

Cause: An object with the same name already exists in the directory.

Action: Choose another name for the object.

Cause: Object name is invalid.

Action: Use proper construction for name paths.

Cause: Named object directories must be empty before they can be deleted.

Action: Delete the remaining objects in the directory, and then delete the directory.

Cause: Calling program supplied an invalid pointer for the directory.

Action: Specify a valid pointer for the directory.

Cause: Calling program supplied a null pointer for directory.

Action: Specify a valid pointer for the directory.

Cause: Calling program supplied an invalid object name.

Action: Check the object name, and see the rules for object naming in the online help.

Cause: Calling program supplied a null pointer where a valid dynamic array is required.

Action: Specify a valid pointer to the dynamic array.

Cause: A multi-dimensional array is used as a search expression, in a relationship or as a default value for an attribute.

Action: Such use is not supported.

Cause: You may not use ALTER TABLE to do schema evolution on a snapshot.

Action: Such use is not supported.

Cause: DML is not permitted on a table while it hasa constraint set to DISABLE VALIDATE.

Action: Change the constraint state to something other than DISABLE VALIDATE.

Cause: An attempt was made to insert a NULL value into a column with a NOT NULL constraint.

Action: Check the value being inserted or change the column NOT NULL constraint to allow a NULL value.

Cause: There are no rows that match the search criteria in the query.

Action: The table may be empty. Check the SQL query, and modify it as necessary before reissuing it.

Cause: Not enough descriptors were allocated for a DESCRIBE operation.

Action: Only part of the results will be reported.

Cause: The database returns this message when an error is detected while disconnecting from the database.

Action: Reopen the database, and verify that no data was lost.

Cause: Aggregate functions such as SUM and AVG discard any NULL values they encounter.

Action: No action is required. This is simply a warning.

Cause: The database is out of heap memory or object cache memory.

Action: Restart the application.

Cause: The application is unable to connect to the database.

Action: This may indicate that the information specified in the connect string is invalid. Check the connect string for errors, and then try connecting to the database again.

Cause: The application is unable to establish a new database connection.

Action: This may indicate that the information specified in the connect string is invalid. Check the connect string for errors, and then try connecting to the database again.

Cause: The calling program passed an invalid environment handle.

Action: Check the handle, and modify it as necessary before trying again.

Cause: The calling program passed an invalid handle.

Action: Check the handle, and modify it as necessary before trying again.

Cause: Calling program passed an invalid session object.

Action: Check the object, and modify it as necessary before trying again.

Cause: The number of question marks in a SQL statement does not match the number of host variables specified.

Action: Check the SQL statement for errors, and supply more host variables to match the number of question marks.

Cause: The number of items in the SELECT list do not match the number of host variables specified to receive the results.

Action: Specify a matching number of the correct type of host variables.

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: A SQL statement that should only return one row returned multiple rows.

Action: Check the SQL statement for syntax errors and correct as necessary, or check the referenced table.

Cause: The database detected an invalid statement state when opening a cursor.

Action: If you are programming directly to the ODBC interface, you may have issued a call out of sequence. If this is not the case, call Oracle Customer Support for assistance.

Cause: The application attempted to open a cursor for an UPDATE, DELETE, or INSERT statement.

Action: Don't declare a cursor for an UPDATE, DELETE, OR INSERT statement.

Cause: The database attempted to change the datatype of a column to an incompatible datatype.

Action: Call Oracle Customer Support for assistance, and provide the SQL statement that caused the error.

Cause: Internal error. The database is looking for a descriptor that doesn't exist.

Action: Call Oracle Customer Support for assistance.

Cause: The database detected a table with the same name when executing a CREATE TABLE statement.

Action: Choose another name for the new table and run the CREATE TABLE statement again, or drop the existing table.

Cause: A SQL statement referenced a catalog that doesn't exist in the current directory.

Action: Copy the referenced database file into the directory specified by the ODBC data source name that you used to connect to the database.

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 name as necessary.

Cause: The database detected a cursor in an invalid state.

Action: Close the cursor, and reissue the SQL statement.

Cause: The host variable type specified is incompatible with the datatype to be returned. For example, an integer variable cannot receive data from a FLOAT column.

Action: Specify a host variable with the correct type.

Cause: The application cannot fetch LONG VARCHAR, LONG VARBINARY, and REF data into a host variable as part of a SQL statement.

Action: Fetch LONG types using appropriate BLOB functions, such as SQLGetData in ODBC.

Cause: The number of host variables specified by the program does not match the number of input parameters required by the SQL statement.

Action: Check that the host variables match the input parameters.

Cause: The number of host variables specified by the program does not match the number of columns returned by the SQL statement.

Action: Check that the host variables match the SELECT list.

Cause: 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.

Cause: An embedded SQL program called sqlNameDesc(), but a column descriptor with the same name already exists.

Action: Choose a different name for the column, and reissue the SQL statement.

Cause: The number of column descriptors does not match the number of columns indicated by the SQL statement.

Action: Check the SQL statement for syntax errors, or modify the number of descriptors to match the number of columns.

Cause: Internal error. The database was asked to describe an invalid descriptor item.

Action: Call Oracle Customer Support for assistance.

Cause: A SQL statement violated an integrity constraint when executed.

Action: No action required. The affected rows will be rolled back to their previous state.

Cause: The database attempted to insert data directly into a DATE, TIME, TIMESTAMP, LONG VARCHAR, or LONG VARBINARY column.

Action: Cast the date or time values using TO_DATE(), and insert the BLOB data using the ODBC function SQLPutData().

Cause: The database can't perform a DELETE operation because dependent objects and a RESTRICT constraint exist.

Action: Delete the dependent objects, and then reissue the DELETE statement.

Cause: An embedded SQL program supplied an invalid statement handle or name.

Action: Check the program for errors.

Cause: A SQL statement attempted to use a feature or function that Oracle Lite does not yet use.

Action: Rewrite the statement, and eliminate the call to the unsupported feature or function.

Cause: A SQL statement referenced a catalog that does not exist in the current directory.

Action: Copy the referenced database file into the directory specified by the ODBC data source name that you used to connect to the database.

Cause: The database found a schema with the same name while executing a CREATE SCHEMA statement.

Action: Run DELETE CASCADE on the old schema, or supply a different name for the new schema.

Cause: Program attempted to access a database system table.

Action: Check the program for errors, and eliminate any calls to database system tables.

Cause: A SQL statement referenced a catalog that already exists.

Action: If you are using CREATE DATABASE, choose a different name.

Cause: The database could not find the schema name specified in the current catalog.

Action: Use CREATE SCHEMA to create the schema name in the catalog.

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.

Cause: The current schema does not have the permissions required to GRANT a privilege to another schema.

Action: No action is required because Oracle Lite does not enforce privileges.

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: Program attempted to update or delete a cursor by specifying a position in a SELECT cursor.

Action: Check the name of the cursor specified in the SELECT statement, and reissue the statement.

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: The value by which a sequence should be incremented is set to zero.

Action: Recreate the SEQUENCE.

Cause: After creating a new sequence, a program must fetch a sequence's NEXTVAL value before it can access the CURRVAL value.

Action: Get the NEXTVAL, and then get the CURRVAL.

Cause: When creating or altering a sequence, the MINVALUE must be less than the MAXVALUE if the INCREMENT BY is positive. If INCREMENT BY is negative, the MAXVALUE must be less than the MINVALUE.

Action: Check the arguments in the CREATE SEQUENCE statement for errors, and then reissue the statement.

Cause: When creating or altering a sequence, the sequence starting value must be between MINVALUE and MAXVALUE.

Action: Check the arguments in the CREATE SEQUENCE statement for errors, and then reissue the statement.

Cause: The MAXVALUE of a sequence has been reached and cannot be exceeded.

Action: Run ALTER SEQUENCE to increase the MAXVALUE.

Cause: The MINVALUE of a decreasing sequence has been reached and may not be exceeded.

Action: Run ALTER SEQUENCE to lower the MINVALUE.

Cause: SQL statement referenced a sequence that does not exist.

Action: Create the sequence, and then reissue the SQL statement.

Cause: An ALTER TABLE...DROP COLUMN statement attempted to drop the only column in a table.

Action: DROP the table instead.

Cause: A SQL statement referenced a view that does not exist.

Action: Create the view with CREATE VIEW, and then reissue the SQL statement.

Cause: A DROP INDEX statement named an index that could not be found.

Action: Check the index name, and then reissue the SQL statement.

Cause: A DROP SYNONYM statement referenced a synonym that does not exist.

Action: Check the synonym name, and then reissue the SQL statement.

Cause: As a result of another SQL statement that may have dropped a table, view, or sequence, a synonym exists for an object that no longer exists.

Action: DROP the synonym, or recreate the object to which it refers.

Cause: A CREATE SYNONYM statement tried to give the same name to the synonym as its target.

Action: Choose another name for the synonym.

Cause: A hierarchical join SELECT statement that called CONNECT BY may be recursing. Hierarchical joins may not exceed 32 levels.

Action: Ensure that the SQL statement can't loop back on itself.

Cause: A CREATE SYNONYM statement found a synonym with the same name.

Action: Choose a different name for the synonym, and then reissue the SQL statement.

Cause: An embedded SQL program tried to read a diagnostic condition that does not exist.

Action: Check the call to sqlGetDiagCondPtr() for syntax errors.

Cause: A program tried to open or close a database connection where none exists.

Action: Exit and try to connect again. If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: Program attempted to disconnect when a transaction appears to be active.

Action: COMMIT or ROLLBACK any pending transactions, and then disconnect.

Cause: Connections take the name of the catalog, so this indicates that a catalog with the same name is already open.

Action: Use or close the existing connection.

Cause: A maximum of 16 columns can participate in an index or a table's primary key.

Action: Reduce the number of columns in the index.

Cause: Program attempted to create an object with a name that already exists.

Action: Choose another name.

Cause: Tables can contain only one primary key.

Action: Recreate the table with the appropriate primary key.

Cause: An ALTER TABLE statement attempted to drop a primary key where none exists.

Action: Check that the primary key exists, or correct the ALTER TABLE statement.

Cause: An ALTER TABLE statement attempted to drop a UNIQUE constraint where none exists.

Action: Check that the UNIQUE constraint exists, or correct the ALTER TABLE statement.

Cause: An ALTER TABLE statement attempted to drop a named constraint where none exists.

Action: Check that the constraint exists, or check the ALTER TABLE statement for syntax errors.

Cause: An ALTER TABLE statement attempted to drop a NOT NULL constraint.

Action: The table must be recreated without the NOT NULL constraint.

Cause: Read-only snapshot tables can't be modified by the local user.

Action: Change the application so that it does not modify snapshots.

Cause: A SQL statement that included a hierarchical join attempted to join with another table.

Action: Don't use CONNECT BY to establish a join.

Cause: The database is protecting the user from dropping the schema currently in use.

Action: Log on as a different user, and then drop the schema.

Cause: The SYSTEM schema is protected from being dropped.

Action: No action required. Don't attempt to drop the SYSTEM schema.

Cause: A snapshot table is being refreshed, possibly as part of a long-running transaction, and may not be modified until the refresh cycle completes or is aborted.

Action: Disconnect, and abort the refresh operation if necessary.

Cause: User attempted to create an index on a view or sequence.

Action: No action required. Create indexes only on base tables.

Cause: The column specified in a SQL statement could not be found.

Action: Check that the column, table, and user/schema exist.

Cause: A DROP TRIGGER statement failed to find the trigger named for deletion.

Action: Check the name, and reissue the SQL statement.

Cause: A CREATE TRIGGER statement found that a trigger with the same name already exists.

Action: Check the SQL statement for syntax errors, and then reissue the SQL statement. Alternatively, drop the duplicate trigger, and then reissue the SQL statement.

Cause: The number of arguments in a call to a stored procedure doesn't match the number of arguments expected by the procedure.

Action: Check the SQL statement for syntax errors, and then reissue the call.

Cause: There are too many active SQL statements.

Action: Close each SQL statement handle when the program has finished using it.

Cause: The Blob object is not created.

Action: This is an internal error. Call Oracle Customer Support for assistance.

Cause: Invalid attempt to create a Blob object.

Action: This is an internal error. Call Oracle Customer Support for assistance.

Cause: A REMOVE or ROLLBACK statement failed to find the savepoint name.

Action: Check the name, and reissue the SQL statement.

Cause: A SAVEPOINT statement found that a savepoint with the same name already exists.

Action: Check the SQL statement for a duplicate savepoint name, and reissue the SQL statement.

Cause: The cursor type can't be used in conjunction with the current isolation level.

Action: Check the cursor type and reassign a different cursor type.

Cause: A CREATE TABLE statement referenced a table name that already exists.

Action: Drop the old table or ignore the error.

Cause: A column name was specified twice in a CREATE or INSERT statement. Column names must be unique within a table, view, or cluster.

Action: In a CREATE statement, change one of the column names to a new, unique column name. In an INSERT statement, remove one of the duplicate names.

Cause: Either the schema name is not recognized, or an attempt was made to use a schema while not connected as that user.

Action: If the cause is an unrecognized schema name, then use an existing schema. If the cause is that a user is connected with an incorrect user name, then disconnect and connect again with the correct user name.

Cause: An invalid table name was referenced in a SQL statement.

Action: Check the table name, and reissue the SQL statement.

Cause: An invalid column name was referenced in a SQL statement.

Action: Check the column name, and reissue the SQL statement.

Cause: A SELECT statement provided an invalid alias for one of the result columns.

Action: Alias names must be single words and legal object names, or be enclosed in double quotation marks.

Cause: An INSERT...VALUES statement may not have specified enough values for all the columns, or it may have specified too many values.

Action: Look at the table definition and specify values for all columns for which defaults aren't defined.

Cause: The number of view columns specified in a CREATE VIEW statement does not match the number of columns specified in the SELECT statement that defines the view.

Action: Ensure that the number of view columns specified in the CREATE VIEW statement matches the number specified in the SELECT statement.

Cause: The maximum length for a CHAR or VARCHAR column is 2048 bytes.

Action: Check the column definition, and ensure that the length does not exceed 2048 bytes.

Cause: The maximum precision of a number is 38 digits.

Action: Check the NUMBER column definition for errors.

Cause: The maximum scale of a number column must be less than the precision.

Action: Modify the NUMBER column definition so that the scale is less than the precision.

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, and then try inserting the data into the column.

Cause: The datatype of a literal or expression does not match the datatype of the column with which it is being compared.

Action: Use a TO_CHAR, TO_NUMBER, TO_DATE, or CAST function to cast the expression to the correct datatype, and then try the comparison again.

Cause: The datatype of a parameter could not be determined from the syntax.

Action: Check the SQL statement for syntax errors.

Cause: An expression mixed incompatible datatypes, such as attempting to add a character value to a numeric expression.

Action: Check the expression for errors.

Cause: An interval computation resulted in an invalid value.

Action: Call Oracle Customer Support for assistance.

Cause: Interval expression was not fully qualified.

Action: See the SQL-92 specification for interval expression syntax.

Cause: A feature that Oracle Lite knows how to parse was recognized but can't be run.

Action: Don't try to use that feature at this time.

Cause: The input datatype cannot be converted to the desired output datatype.

Action: Check the SQL statement syntax, and correct the input datatype.

Cause: Oracle Lite could not add a foreign key reference due to an error in the declaration. Either the referenced table does not exist, or the table does not have a unique key.

Action: Check that the referenced table exists and has a unique key.

Cause: The specified table contains no columns that can be updated.

Action: This may not be an error.

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: Certain SQL statements do not allow sub-queries.

Action: Rewrite the SQL statement and eliminate the sub-query.

Cause: GROUP BY is not allowed in a WHERE clause, and certain columns are illegal for GROUP BY operations.

Action: Check the GROUP BY clause in the SQL statement, and then reissue the statement.

Cause: The database detected a syntax error in a GROUP BY SQL statement.

Action: Check the SQL statement for errors, and then reissue it.

Cause: SQL statement contains invalid CASE syntax.

Action: Check the statement and try again.

Cause: SQL statement contains invalid syntax for the UNION or MINUS operators.

Action: Check the statement and try again.

Cause: SQL statement contained a syntax error.

Action: Inspect the statement for misspellings and missing parentheses, and then reissue it. Refer to the online SQL help for the correct syntax for the statement type.

Cause: SQL statement contains invalid syntax for an outer join.

Action: Check the statement and try again.

Cause: A CREATE DATABASE statement contained an invalid database size parameter.

Action: Check the parameter for errors and reissue the SQL statement. See the SQL online help for valid parameter values.

Cause: A CREATE DATABASE statement contained an invalid extent size parameter.

Action: Check the parameter for errors and reissue the SQL statement. See the SQL online help for valid parameter values.

Cause: A CREATE DATABASE statement contained an invalid database ID.

Action: Check the parameter for errors and reissue the SQL statement. See the SQL online help for valid parameter values.

Cause: An attempt was made to reference a sequence in a FROM list, which is not permitted. A sequence can only be referenced in a SELECT list.

Action: Check the statement syntax, correct the reference, and try again.

Cause: A SELECT list cannot include both a group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, and an individual column expression, unless the individual column expression is included in a GROUP BY clause.

Action: Drop either the group function or the individual column expression from the SELECT list or add a GROUP BY clause that includes all individual column expressions listed.

Cause: The GROUP BY clause does not contain all the expressions in the SELECT clause. SELECT expressions that are not included in a group function must be listed in the GROUP BY clause. The group functions are: AVG, COUNT, MAX, MIN, SUM, STDDEV, and VARIANCE.

Action: Include in the GROUP BY clause all SELECT expressions that are not group function arguments.

Cause: SQL statement contains a reference to an unknown Java procedure type.

Action: Stored procedures must return SQL datatypes. Check the procedure definition.

Cause: There are too many columns in a CREATE TABLE statement.

Action: Reduce the number of columns in a table.

Cause: The keyword after ON DELETE is invalid.

Action: Correct the spelling of the keyword to CASCADE.

Cause: When dropping a table or view, you may only specify CASCADE or RESTRICT.

Action: Correct the DROP statement syntax.

Cause: Only the COUNT () function can take the asterisk as an argument.

Action: Correct the arguments to the SQL function.

Cause: An SQL function was used without providing the correct number of arguments.

Action: Check the arguments for all SQL functions in the statement.

Cause: An ODBC function name was used without the {fn X} curly braces.

Action: Use the {fn X} curly braces.

Cause: A CREATE SEQUENCE or ALTER SEQUENCE keyword is misspelled or the sequence is invalid.

Action: Correct the spelling of the keyword.

Cause: Outer join condition did not specify a column or a valid comparison operator.

Action: Correct the SQL statement.

Cause: Your query contains an expression in the group by clause. Only column references are allowed.

Action: Change your query or use a view.

Cause: You are trying to connect to the database with an invalid user name.

Action: Double-check to make sure you are using the correct user name.

Cause: A single-row subquery returns more than one row.

Action: Correct the query so that the subquery returns at the maximum one row.

Cause: Some identifier cannot take a zero-length string.

Action: Provide a non-zero-length string.

Cause: A CREATE procedure/function statement found that a procedure/function with the same name already exists.

Action: Check the SQL statement for duplicate procedure/function name, and reissue the SQL statement.

Cause: A SQL statement referenced a procedure/function that does not exist.

Action: Create the procedure/function with CREATE procedure/function and then reissue the SQL statement.

Cause: Datatypes of expressions in corresponding positions are not the same. Characters, numerics or dates cannot be mixed.

Action: Check the datatypes of expressions. CAST conversion may be an option.

Cause: The number of table columns specified in a CREATE TABLE statement does not match the number of columns specified in the SELECT statement that defines the table.

Action: Ensure that the number of table columns specified in the CREATE TABLE statement and columns specified in the SELECT statement match.

Cause: An attempt was made to insert a NULL value into a column with a NOT NULL constraint.

Action: Check the value being inserted or change the column NOT NULL constraint to allow a NULL value.

Cause: Creating a temporary dir/file failed in CREATE JAVA SOURCE AS statement.

Action: Check if disk space is available, if the temporary directory path is valid, or if permission is proper.

Cause: The user name identifier has more than 30 characters.

Action: Use an identifier with under 30 characters.

Cause: A column is found whose type is not allowed in a GROUP BY clause.

Action: Check the column type for errors and then reissue it.

Cause: ROWID is not available for rows that are selected from a query that either contains a GROUP BY clause or a join operation, or the SQL statement is not a query.

Action: Rewrite the query or do not use the ROWID value.

Cause: The SELECT list is empty or all columns in the SELECT list are hidden columns.

Action: Rewrite the query.

Cause: Column to be modified cannot be set to null.

Action: No action required. Probably the column to be modified has primary key constraint.

Cause: May not specify column datatypes in CREATE TABLE from subquery.

Action: Remove column datatypes.

Cause: May not use a view here.

Action: Do not use a view.

Cause: May not specify START WITH in ALTER SEQUENCE.

Action: Do not specify START WITH.

Cause: Duplicate or conflicting MINVALUE / NOMINVALUE specifications.

Action: Double check ALTER SEQUENCE syntax.

Cause: Duplicate or conflicting MAXVALUE / NOMAXVALUE specifications.

Action: Double check ALTER SEQUENCE syntax.

Cause: The column precision cannot be decreased because the existing data cannot fit into the modified datatype.

Action: Check the ALTER TABLE MODIFY statement.

Cause: View was not created with valid base table(s).

Action: Make sure the base table is created and recompile the view using the ALTER VIEW view_name COMPILE command.

Cause: The query encountered some error during previous execution. The run time representation does not exist.

Action: Recompile the query and re-execute.

Cause: The specified MINVALUE in an ALTER SEQUENCE statement exceeds the current value.

Action: Change the MINVALUE to be less than the current value.

Cause: The specified MAXVALUE in an ALTER SEQUENCE statement is less than the current value.

Action: The MAXVALUE cannot be made to be less than the current value.

Cause: Driver-specific informational message.

Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Cause: The Driver Manager called the Driver's SQLSetConnectOption(), which sets connection options, and the driver returned an error.

Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Cause: Error with this implementation of ODBC.

Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.

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.

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.

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.

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.

Cause: A function was canceled before completing execution.

Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.

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.

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.

Cause: This error is function-specific.

Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.

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.

Cause: There is no open cursor for the statement.

Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.

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.

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.

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.

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.

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.

Cause: An invalid ODBC function was specified.

Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.

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.

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.

Cause: An invalid scope type was specified.

Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.

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.

Cause: An invalid index type was specified.

Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.

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.

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.

Cause: The maximum precision of the value of a column was exceeded or is invalid. This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

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.

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.

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.

Cause: An invalid value was specified for determining locking level.

Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.

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.

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.

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.

Cause: The cause is ODBC function-specific.

Action: See the Microsoft ODBC Programmer's Reference and SDK Guide for more information.

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.

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: An application caused a deadlock.

Action: The transaction has been automatically rolled back. Data should be resubmitted if necessary.

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.

Cause: CLASSPATH environment variable may not have been set correctly.

Action: Include JDK_HOME\lib\classes.zip in the CLASSPATH environment variable.

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.

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.

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.

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.

Cause: Internal error.

Action: If the product has been installed correctly and the error persists, call Oracle Customer Support for assistance.

Cause: The Oracle Lite class loader cannot find the package name.

Action: Check the package names in the fully-qualified class name.

Cause: A blob with the same name already exists.

Action: Choose another name for the blob.

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.

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.

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.

Cause: A package with the same name already exists.

Action: Choose a different name for the class.

Cause: Could not find the specified class object.

Action: Verify that the class exists.

Cause: Could not create the blob attribute for a class.

Action: Look for other errors on the error stack.

Cause: Could not get the size of a blob object.

Action: Check that the blob object exists and is the size you expect.

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.

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.

Cause: Could not set the value of a blob.

Action: Verify that the values are correct and that the blob data is readable.

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.

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.

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

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.

Cause: The Java object reference is corrupted.

Action: It is an internal error. Call Oracle Customer Support for assistance.

Cause: A Java class with the same name already exists.

Action: Choose another name for the class.

Cause: Most commonly refers to a problem when converting between Java and Oracle Lite datatypes.

Action: Check the calling parameters.

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.

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.

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.

Cause: The failing call contains an argument with an invalid value.

Action: Check for syntax errors, and reissue the statement with valid argument values.

Cause: A method was invoked without supplying an instance for the method to operate on.

Action: Supply an object to the method.

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.

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.

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.

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.

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.

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.

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.

Cause: After-delete triggers have neither OLD nor NEW values.

Action: Use a before-delete trigger if you must use attributes.

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.

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: This is an abnormal condition.

Action: Report this as an "Abnormal Condition".

Cause: There was a reference to an invalid attribute name.

Action: Check the attribute name, and try deleting the trigger again.

Cause: There was a reference to an invalid path name.

Action: Check the path name, and try again.

Cause: The system denied access to a necessary Java source file.

Action: Correct the access control on the required file.

Cause: Program supplied an invalid trigger type when creating a trigger.

Action: Correct the trigger type parameter in the calling program.

Cause: The domain of an attribute could not be mapped to a known type.

Action: Define the attribute domain in terms of known datatypes.

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.

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.

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.

Cause: Trigger methods can't return a value.

Action: Check the declaration of the method for errors.

Cause: The Java class specified is already attached to the table or class.

Action: Check the name and try again.

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.

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.

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.

Cause: Call to okCreate trigger failed to specify what kind of trigger to create.

Action: Check the call for errors and try again.

Cause: You have specified an argument to the method in a statement level trigger.

Action: Don't use any arguments.

Cause: The specified trigger could not be found.

Action: Check the trigger name in your code.

Cause: Program attempted to drop a trigger that doesn't exist.

Action: Check the trigger name in your code.

Cause: No update attributes were specified in a trigger that requires them.

Action: Supply the missing parameters, and try again.

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.

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.

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.

Cause:

Action:

Cause:

Action:

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.

Cause:

Action:

Cause:

Action:

Cause:

Action:

Cause:

Action:

Cause: Internal Error

Action: Contact your system administrator.

Cause: Cannot allocate memory for this process

Action: Increase available system memory by closing other applications, increase physical memory, or virtual memory size.

Cause: Memory is corrupt, or you have run out of memory.

Action: Increase available memory and restart Msync.

Cause: Out of memory.

Action: Increase memory.

Cause: PDB file contains more than 65535 records, or you are out of persistent memory.

Action: Delete unused PDB files to increase capacity.

Cause: Palm Database (PDB) file already exists, or you are out of memory.

Action: Delete PDB file if it exists, or delete other PDB files to increase capacity.

Cause: Out of memory.

Action: Delete PDB files to increase capacity

Cause: Class exists, out of memory, or there are too many objects in database

Action: Make sure database is created using ocapi.dll and is not too large.

Cause: Group exists, out of memory, or too many objects in the database.

Action: Make sure database is created by synchronizing with Mobile Sync that the file system is not full.

Cause: Out of memory, or too many objects in the database.

Action: Delete other unused PDBs to increase capacity.

Cause: Corrupted database, or out of memory.

Action: Delete database and resynchronize.

Cause: Application file exists locally already, or is too large.

Action: Delete excess files to increase disk capacity

Cause: Destination directory not found.

Action: Create the directory where the application should go and resynchronize. See the "Packaging Wizard" Chapter of the Developer's Guide for the platform in question, for example, Developer's Guide for Windows 32

Cause: An invalid index was specified.

Action: Check the server side index definition using the CV$ALL_PUBLICATION _INDEX system catalog view. See the "System Catalog View" Appendix of the Developer's Guide for the platform in question, for example, Developer's Guide for Windows 32.

Cause: Cannot create error log entries.

Action: Purge old log entries.

Cause: Shared library does not exist or has become corrupted.

Action: Re-install shared libraries.

Cause: Corrupted shared library.

Action: Reinstall okapi.prc shared library or use static consolidator.

Cause: Obsolete.

Action: Contact your system administrator.

Cause: Compression error.

Action: Contact your system administrator.

Cause: Obsolete.

Action: Contact your system administrator.

Cause: Server does not support this client.

Action: Upgrade server or client so that the versions match.

Cause: Error occurs when sending data through socket.

Action: Check network connection and resynchronize.

Cause: Error occur when sending data three socket.

Action: Check network connect and resync.

Cause: Server reported an error.

Action: Check server log and fix server.

Cause: Login failed.

Action: Check login name and password and resynchronize.

Cause: Client database exists or is locked.

Action: Make sure conscli.odb is not being used, and there is enough disk space.

Cause: Cannot open temporary compressed data.

Action: Check diskspace and make sure no other process is purging temp files during sync.

Cause: Cannot open temporary compressed data.

Action: Check diskspace and make sure no other process is purging temporary files during synchronization.

Cause: Server sent a bad sync packet to the client.

Action: Check version of server or reinstall Mobile Client from Mobile Server.

Cause: Disk failure or other system problems.

Action: Check file system.

Cause: HTTP read/write problem

Action: Check network connect and proxy server

Cause: DNS failed to find host by name

Action: Check server name, DNS servers and network connection

Cause: gethostbyname failed.

Action: Check DNS settings of client machine.

Cause: Cannot find the proxy server.

Action: Check proxy server hostname and DNS server.

Cause: The server is down.

Action: Restart the Mobile Server or proxy.

Cause: Proxy server is down.

Action: Restart proxy server or verify proxy hostname.

Cause: Socket write error.

Action: Check network connection.

Cause: Cannot write POST data to socket.

Action: Check network connection, proxy server and server timeouts.

Cause: Cannot read entire HTTP header.

Action: Check Mobile Server and proxy server.

Cause: Error when reading data from socket.

Action: Check Mobile Server and network connection.

Cause: Socket dropped during sync process.

Action: Check network connection.

Cause: Cannot load network library.

Action: Check network stack and see if has enough memory to load stacks.

Cause: System SSL error.

Action: Check operating system, re-install the SSL components.

Cause: Cannot load SSL libraries

Action: Install necessary operating system patches or libraries.

Cause: Cannot disconnect from server cleanly.

Action: Check network connection, and proxy server settings.

Cause: Cannot make SSL connection.

Action: Check SSL settings in the Mobile Server configuration file.

Cause: Failed at SSL handshake stage.

Action: Check client OS and server SSL version supported.

Cause: Cannot load remote certificate.

Action: Check server key manager.

Cause: Cannot load SSL library.

Action: Re-install operating system SSL support libraries.

Cause: Operating system library error or corrupted during transmission.

Action: Check connection, or SSL support for client and server.

Cause: Operating system library error or corrupted during transmitting.

Action: Check connection, or SSL support for client and server.

Cause: The execution of the specified method failed. This message is usually followed by a more detailed message describing the cause of the problem.

Action: Examine the detailed message to find the cause of the problem.

Cause: Your class, which should extend from the base class TemplateParser, does not contain the specified method.

Action: Ensure that all methods as returned by the method getWRB_TAGS() exist in your class. Also, make sure that the signature of the method is correct.

Cause: The execution of the specified method failed. This message is followed by a more detailed message describing the cause of the problem.

Action: Examine the detailed message to find the cause of the problem.

Cause: The table does not contain a column with the specified number.

Action: Find the correct column number. Column numbers start at 1.

Cause: A JDBC connection to the database could not be created.

Action: Contact your system administrator.

Cause: A JDBC statement, used to execute SQL statements could not be created.

Action: Contact your system administrator.

Cause: The database table does not contain a column with the specified name.

Action: Find the correct name for the column.

Cause: The ProcessForm servlet requires the specified HTML parameter to be present in the HTML form.

Action: Add the parameter to the form and re-submit the form.

Cause: The HTML template could not be parsed. This message is usually followed by a detailed message describing the nature of the problem.

Action: Examine the detailed message to determine the cause of the problem.

Cause: The SQL statement generating the list of values returned too many columns. Only one or two columns are supported.

Action: Change the SQL statement to return the correct number of columns.

Cause: The list of values select field could not be created, most likely due to an error in the SQL statement.

Action: Correct the SQL statement that is used to populate the list of values.

Cause: The WebToGoHtmlPage object in which you attempted to substitute a WRB_INC tag (with a text string), is of an incorrect type.

Action: You can only substitute a WRB_INC tag in WebToGoHtmlPage objects that are constructed based on a WebToGoFile object.

Cause: A JDBC error occurred. This message is usually followed by a detailed message describing the nature of the problem.

Action: Examine the detailed message to determine the cause of the problem.

Cause: The user has been granted access by the administrator, but the user's connection privilege has not been raised to administrative privilege.

Action: Use the Control Center to edit the user's privileges. Change the user's privilege to Administrator.

Cause: There was a server-side error while retrieving the specified information for the specified system object.

Action: Turn debugging on at the server side for more detail.

Cause: There was a server-side error while retrieving the specified information.

Action: Turn debugging on at the server side for more detail.

Cause: The Administrator cannot remove the Control Center application from the Web-to-Go system.

Action: Do not attempt to remove the Control Center from Web-to-Go.

Cause: The object the administrator is attempting to create would overwrite an already existing object in the system.

Action: Either edit the existing object or create a new one with a unique name.

Cause: The Control Center cannot find any entries in the repository that match your query.

Action: Use more general criteria for the search, or use no criteria to return all objects of the given type in the repository.

Cause: The administrator attempted to use the Control Center while in off-line mode.

Action: Only use the Control Center while online.

Cause: The administrator cannot be removed from the system.

Action: Do not attempt to remove the specified user from the system.

Cause: The user that you attempted to create already exists in the system.

Action: Modify the existing user.

Cause: jar file is wrong.

Action: Must use jar file from Packaging wizard.

Cause: The application already exists in the system.

Action: Delete previous one before trying to create a new one.

Cause: The Control Center cannot find any entries in the repository that match your query.

Action: Search with more general criteria, or none at all to retrieve all objects of that type in the repository.

Cause: You cannot change your own password in the User Properties page.

Action: Go to Workspace select Configuration tab and click change password link.

Cause: You cannot remove yourself from the system.

Action: Do not attempt to remove the specified user from the system.

Cause: The specified resource does not exist in the system.

Action: Create the desired resource and re-run the script.

Cause: The snapshot parameter is not registered with the server.

Action: Ensure that the parameter is registered on the server.

Cause: The user name or password cannot be null.

Action: Verify that the user name and password contain values.

Cause: Platform value passed is invalid.

Action: Pass valid Platform value.

Cause: Applet is not able to make connection with the Web-to-go server.

Action: Contact your system administrator.

Cause: Web-to-go application servlet has returned a null object.

Action: Examine the servlet and return a serializable object.

Cause: APPLET_SUPPORT_ENABLE=YES is missing from webtogo.ora

Action: Please add APPLET_SUPPORT_ENABLE=YES in webtogo.ora and restart Mobile Client for Web-To-Go.

Cause: User tried to write data to a stream that is already closed.

Action: Re-open the stream before writing data.

Cause: User tried to read data from a stream that is already closed.

Action: Re-open the stream before reading.

Cause: Invalid parameter is passed to the write method of the stream.

Action: Verify the validity of your input buffer.

Cause: The input buffer is too small to hold the data the user attempts to read.

Action: Increase the buffer size and read the data again.

Cause: User tried to open a stream with an invalid file name.

Action: Provide correct file name and open the stream.

Cause: System could not locate the specified file.

Action: Verify the existence of the file in the file system.

Cause: The directory may already exist in the system.

Action: Verify the existence of the directory.

Cause: The directory may not be empty.

Action: Delete all files in the directory before deleting the directory.

Cause: System failed to write the data to the file.

Action: Verify the validity of your input buffer.

Cause: System could not truncate the file.

Action: The file may be opened by another user. Close all open references to the file.

Cause: Stream handle used for the operation is invalid.

Action: Re-open the file (stream).

Cause: You attempted to create a directory that already exists.

Action: Select a different name for the new directory.

Cause: You attempted to delete a directory that is not empty (contains other directories and/or files).

Action: Delete all files from the directory before deleting the directory itself.

Cause: You attempted to delete the root directory.

Action: This action is not permitted.

Cause: System could not locate the specified directory.

Action: Verify the existence of the directory.

Cause: File may not exist.

Action: Check for the existence of the file.

Cause: The specified TNS name (Oracle Lite DSN) may not exist.

Action: Verify the TNS name (DSN) and try again.

Cause: The number of arguments specified with the command is incorrect.

Action: Re-execute the command with the correct syntax.

Cause: You specified a command that is not supported by the tool.

Action: Check the syntax of the command.

Cause: The script file executed completely, with no errors.

Action: No action necessary, this message is informative only.

Cause: User attempted to delete an open file.

Action: Close the file before deleting it.

Cause: User tried to open a file from an unmounted file system.

Action: Mount the file system and try again.

Cause: Web-to-go server could not connect to the repository.

Action: Provide a valid user name and password for the repository user.

Cause: The path to the script file is invalid.

Action: Check the path of the script file and ensure that you have read access privileges on the file.

Cause: The script file contains an error at the specified line.

Action: Correct the error in the script file and re-execute the command.

Cause: A keyword, other than the given keyword, is in the script file at the specified line.

Action: Correct the error in the script file and re-execute the command.

Cause: User attempted to access a protected URL.

Action: Contact your system administrator to grant proper access.

Cause: The browser idle time exceeded the LOGON EXPIRATION TIME.

Action: Log on again.

Cause: User attempted to access a protected URL.

Action: Contact the system administrator to get proper access.

Cause: Logon information may be incorrect.

Action: Provide correct information.

Cause: Logon information may be incorrect.

Action: Provide correct information.

Cause: Logon information may be incorrect.

Action: Provide correct information.

Cause: System could not locate the URL specified by the user.

Action: Check the URL and try again.

Cause: System could not locate the URL specified by the user.

Action: Check the URL and try again.

Cause: An error occurred in your application.

Action: Contact the application vendor.

Cause: User action caused an error.

Action: See the details displayed on your browser.

Cause: The Web-to-go server may be down.

Action: Contact the system administrator.

Cause: An error occurred in your system.

Action: Contact the system administrator.

Cause: The Web-to-go server may be down.

Action: Contact your system administrator.

Cause: You can only change your configuration settings while in online mode.

Action: Switch to online mode and try again.

Cause: Incorrect logon information provided.

Action: Provide valid information.

Cause: The application has been suspended by the administrator

Action: Please try again at a later time. If the application is not available, contact your system administrator.

Cause: The application has been suspended by the administrator

Action: Please try again at a later time. If the application is not available, contact your system administrator.

Cause: User does not have CONNECT privilege to log on to the system.

Action: Contact your system administrator for this privilege.

Cause: The system can not change your password. Either the current password is incorrect, or the new passwords do not match.

Action: Verify that you specified the correct current password. If you entered the new password twice, make sure the values match. Retry the operation.

Cause: The system can not save your new user preferences. This is due to invalid input, or a more serious system error.

Action: Verify your input to make sure you specified legal values for your preferences. If this is the case, and you still receive this message, contact the system administrator. The system administrator should turn on the Web-to-go log messages to obtain more detailed information regarding the cause of this problem.

Cause: The system can not change your password. The new password can not be the same as the old password.

Action: Select a password that is different from your current password and retry the operation.

Cause: The administrator can only connect to the Mobile server directly.

Action: Connect as administrator to the server directly, or connect to the client as a different user.

Cause: The administrator can only connect to the Mobile server directly.

Action: Connect as administrator to the server directly, or connect to the client as a different user.

Cause: The Web-to-Go version was not available

Action: Contact your system administrator

Cause: The Web-to-Go version was not available

Action: Contact your system administrator

Cause: The XML file is not well-formed.

Action: Examine the XML file using a text or XML editor.

Cause: Failed to publish due to network or authorization reasons.

Action: Examine the file wtgpack.log in the Web-to-go root directory for more information.

Cause: Failed to publish due to network or authorization failure, or a non-valid XML file.

Action: Examine the file wtgpack.log in the Web-to-go root directory for more information.

Cause: Failed to publish due to network or authorization failure, or a non-valid XML file.

Action: Examine the file wtgpack.log in the Web-to-go bin directory for more information.

Cause: The file, wtgos.dll, is required to view the context-sensitive HTML help documentation.

Action: Make sure wtgos.dll is in the Web-to-go bin directory.

Cause: The application definition already exist on the server.

Action: Use -o to override the existing definition on the server.

Cause: the application name that user provides, does not exists in the workspace xml file.

Action: Make sure the application name is correct, note the application is case-sensitive.

Cause: Packaged Web to Go application jar file contains web.xml that contains the application definition.

Action: Make sure the web.xml file exists in the jar file

Cause: Mobile Server started at the admin port only, the administrator hasn't logged in yet.

Action: Make sure the server is running completely with the database user's username and password.

Cause: For Palm files. The file extension is removed because Palm does not support any extensions.

Action: Please rename files to be unique even when file extensions are removed.

Cause: The FileName cannot be null.

Action: Please examine the File name passed.

Cause: The specified file does not exist in the system.

Action: Please contact your system administrator.

Cause: Application Id cannot be null.

Action: Please examine the Application Id passed.

Cause: Unable to find job class.

Action: Please contact your system administrator.

Cause: Error in retrieving Sequence.

Action: Please contact your system administrator.

Cause: Data saved successfully, Unable to refresh data.

Action: Please contact your system administrator.

Cause: Error in getting data.

Action: Please contact your system administrator.

Cause: The Administrator attempted to use this application in on-line mode.

Action: Only use this application in off-line.

Cause: Job can only be scheduled for future time.

Action: Please go back and change Date / Time.

Cause: Error in saving file.

Action: Please contact your system administrator.

Cause: File does not contain a valid SSL certificate for SSL communication with Mobile Server.

Action: Please contact your system administrator and ensure that a valid SSL certificate is uploaded to the Mobile Server repository.

Cause: This feature is only available if server is running in SSL mode.

Action: Please contact your system administrator.

Cause: In Branch Office mode only one user can own one Branch Office server.

Action: Please go back and login as different user.

Cause: The Mobile Client for Web-To-Go can not synchronized because Branch office service is not running.

Action: Please start Branch office service.

Cause: a description of the possible causes of the error.

Action: a description of the possible actions you can take to resolve the error.