Oracle driver error - 62

Invalid character. Too many values. Missing coma. Ambiguous column usage. Invalid relational operator. Invalid or missing option. FROM keyword not found where expected.

Missing INTO keyword. Value not compatible with target column type. SQL command not properly ended. Group function not allowed. Missing expression. Not a single group function. Table or view does not exist. Not enough values. Invalid DROP option. Name is already used by an existing object. Are you getting the same error message? Are you sure that the hat file us in the lib directory?

I meant "jar file in the lib directory"! This error got solved now. Massive thanks to Yavor and Mark for providing help. There were a couple of things which were needed for oracle. The connection string was incorrect. The right conenction shtring needs to follow the format.

Aparana Gupta. Hi Biswajit, Yavor,. Error: Cannot load Oracle database driver oracle. Is the JDBC driver on the classpath? Please let me know on how to solve this error? Please take ojdbc6. You should put it in lib folder next to the other DbFit. This looks like different issue. Please file separate bug with steps how to reproduce it.

Please file new issue and provide steps how to reproduce it. Skip to content. Star 2. New issue. Jump to bottom. Labels bug. Copy link. Action: Check if the related descriptor was added to the session or the query is done on the right object or class. The descriptor where named query is defined is not added to the session.

Action: Check if the related descriptor was added to the session or the query is done on the right class. Cause: The size query given on the queries returning cursor streams is not correct.

The execution of the size query did not return any size. Action: If the cursor stream query was custom query than check the size query specified else report this problem to Technical Support. Cause: Objects cannot be written in unit of work using modify queries, they must be registered.

Action: Objects are registered in the unit of work and during commit unit of work will do the required changes to the database. Usually this happens because of mis-spelled query key. Action: Check the query key specified in the expression and make sure that a query key was added to the descriptor. Cause: Objects and the database cannot be changed through the server session; all changes must be done through a client session's unit of work.

The objects cannot be changed on the server session by modifying queries. Objects are changed in the client sessions acquired from this server session.

Cause: No concrete class indicated for the type in this row. The type indicator read from the database row has no entry in the type indicator hashtable or if class extraction method was used, it did not return any concrete class type. The exception is thrown when sub classes are being read. Action: Check class extraction method if specified or check the descriptor to see if all the type indicator values were specified or not.

Cause: No cursor support provided for abstract class multiple table descriptors using expressions. Action: Consider using custom SQL or multiple queries. Cause: There are no fields to be insert into the table. You must define at least one mapping for this table.

Cause: Query is not defined. When executing query on the session the parameter which takes query is null. Action: The unit of work, once released, cannot be reused unless commitAndResume is called. Cause: An attempt has been made to read from the cursor streams beyond its limits beyond the end of the stream. Action: Ensure the stream is being checked for an "end of stream" condition before attempting to retrieve more objects.

Cause: The reference class in the query is not specified. A reference class must be provided. Cause: Refresh is not possible if caching is not set. The read queries which skip cache to read objects cannot be used to do refresh the object. Refreshing is not possible without identity. Cause: Did not find size query.

Size only supported on expression queries, unless a size query is given. Cause: The SQL statement has not been properly set. The user should never encounter this unless queries have been customized. Cause: Data read and data modify queries is being executed without the session name. Only object-level queries can be directly executed by the session broker, unless the query is named. Action: Session broker has no idea about such queries about which session to execute the query on.

Specify the session name. The report query result returned is without primary key values. An object from the result can only be created only if primary keys were also read.

Action: Check documentation on retrievePriamryKeys on report query. Action: Check session if the descriptor was added or not or else check class extraction method. Cause: Cannot delete an object of read-only class. Thrown in unit of work when trying to delete an object that is marked as read only. Action: Check ExpressionOperator class to see a list of all of the operators supported. This is a TopLink development exception that users should not encounter.

Cause: The number of attributes requested does not match the attributes returned from the database in report query. This usually happens if one gives custom query on the report query. Action: Check the custom query if it is specified or report this problem to Technical Support. Cause: Partial Objects are never put in the cache. Partial object queries are not allowed to maintain the cache or be edited. You must set dontMaintainCache. Action: Call the dontMaintainCache method before executing the query.

Cause: An outer join getAllowingNull is only valid for one to one mappings, and cannot be used for the mapping. Action: Do not attempt to use getAllowingNull for mappings other than one to one. This is TopLink development exception and user should never encounter this problem unless a custom container policy has been written. This is a TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Thrown when looking for clone method on the container class. The clone is needed to create clones of the container in unit of work. Thrown when new interface container policy is being created using Java reflection. Key cannot be compared with the keys currently in the map. Throws Java reflection exception while accessing method. The operation is not supported. Action: Check the class documentation and look for the corresponding method that should be used.

Cause: Deleted objects cannot have reference after being deleted. Use anyOf rather than get. Use get rather than anyOf. Action: Change the expression such that the query in not done across a variable one to one mapping. Cause: This expression cannot determine if the object conforms in memory, you must set the query to check the database. Action: Change the query such that it does not attempt to conform to the results of the query.

Cause: Object comparisons can only use the equal or notEqual operators, other comparisons must be done through query keys or direct attribute level comparisons. Action: Ensure the query uses only equal and notEqual if object comparisons are being used. Cause: Object comparisons can only be used with mappings; other mapping comparisons must be done through query keys or direct attribute level comparisons.

Action: Use a query key instead of attempting to compare objects across the mapping. Action: Change the query such that it does not attempt to use object when using parameterized queries. Cause: Object comparison cannot be used for target foreign key relationships. Query on the source primary key instead. Cause: The redirection query was not configured properly, the class or method name was not set.

Cause: The redirection query's method is not defined or define with the wrong arguments. Cause: There is a class mismatch between the example object and the reference class specified for this query. Cause: The expression has not been initialized correctly. Only a single ExpressionBuilder should be used for a query. For parallel expressions, the query class must be provided to the ExpressionBuilder constructor, and the query's ExpressionBuilder must always be on the left side of the expression.

Cause: The type of the constant, used for comparison in the expression, does not match the type of the attribute. Cause: Uninstantiated ValueHolder detected. You must instantiate the relevant Valueholders to perform this in-memory query. Action: Instantiate the valueholders for the collection you want to query on.

Cause: You attempted to allocate client sessions before logging into the server. Note: This error also appears in multithreaded environments as a result of concurrency issues. Check that all of your threads are synchronized. Cause: The pool name used while acquiring client session from the server session does not exist. Action: Check the pool name given while acquiring client session and all the existing pools on the server session. Cause: The maximum number of connections in a connection pool should be more than the minimum number of connections.

Cause: Pools must all be added before login on the server session has been done. Once logged in pools cannot be added. This method should be called before login on server session. The Java type of the field to be written to the database has no corresponding type on the database. Verify that the descriptor has been properly registered with the session. Action: Check if the related descriptor to the class was added to the session.

Cause: This is a TopLink development exception and user should never encounter this problem. It happens when a copy of vector is created with start and end index. It happens when test cases are executed.

Action: Report this problem to Technical Support. This error commonly occurs if you attempt to commit an invalid or previously committed UnitOfWork. If ValidationException. Cause: TopLink. Action: Ensure that there is a TopLink. Cause: Child descriptors do not have an identity map; they share their parent's. An Identity map is added to the child descriptor.

A child descriptor shares its parent's identity map. Cause: The user should never encounter this problem. Cause: The login instance provided to the login method is incorrect. Cause: This is a TopLink development exception and users should never encounter it. Cause: The key on the database row is not either of type String or of type DatabaseField.

Action: The objects in the unit of work are written to database by registering and committing the unit of work. Cause: You cannot set read pool size after the server session has already been logged in. Action: Descriptors are added to the sessions contained in the session broker.

Cause: Cannot remove from the set of read-only classes in a nested unit of work. A nested unit of work's set of read-only classes must be equal to or a superset of its parent's set of read-only classes. Cause: Cannot change the set of read-only classes in a unit of work after that unit of work has been used.

Changes to the read-only set must be made when acquiring the unit of work or immediately after. Cause: Invalid Map class was specified for the container policy. Cause: The key method on the map container policy is not defined. This is a TopLink development exception and a user should never encounter it. The Java2 Collection interface is supported using the useCollectionClass method.

Cause: Release attempted on a session that is not a client session. Only client sessions may be released. Cause: Acquire attempted on a session that is not a client session. Client sessions may only be acquired from server sessions. Action: Do not use OptimisticLocking with stored procedure generation. Cause: The wrong object was registered into the unit of work.

It should be the object from the parent cache. Action: Verify the data source name. Check the nested SQL exception to determine the cause of the error. Typical problems include:. The driver is not on the classpath. The user or password is incorrect. The database server url or driver name is not properly specified. In order to use field level locking, a unit of work must be used for ALL writes. Cause: A toplink. Action: Validate the classpath and the location of the TopLink resource bundle.

Cause: When generating the project class the descriptors must not be initialized. Action: Ensure the descriptors are not initialized before generating the project class. Cause: The sessionName specified on the deployment descriptor does not match any session specified in the TopLink properties file. Cause: A FinderException was thrown when trying to load an object from the class with the primary key. Cause: The aggregate object cannot be directly registered in the unit of work.

It must be associated with the source owner object. Cause: The TopLink properties file specified multiple project files for the server. Only one project file can be specified.