20 01 error

20 01 error

TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity). One of the most common problems in setting up OpenVPN is. I am getting the error main.c error: expected identifier or '(' before '{' token. Can anybody Help me with this. I'm pretty new at c. V lighttpd[]: (connections.c) SSL: 1 errorFlib(20).

watch the thematic video

Error Tantsukool 20+1 \

20 01 error - opinion

This section lists each TopLink error code. Each error entry contains a description of the error, the probable cause, and the recommended action. Each error code corresponds to an exception class. See "Runtime and Development Exceptions" for more information.

A description shown in the actual exception thrown.

Cause: The most probable cause for the error.

Action: Suggestions for resolving the error.

ATTRIBUTE_AND_MAPPING_WITH_INDIRECTION_ MISMATCH

Cause: <attributeName> is not declared as type but the mapping uses indirection. Mapping is set to use indirection but the related attribute is not defined as type . It is thrown on foreign reference mappings.

Action: If you want to use indirection on the mapping, change the attribute to type . Otherwise, change the mapping associated with the attribute so that it does not use indirection.

ATTRIBUTE_AND_MAPPING_WITHOUT_INDIRECTION_ MISMATCH

Cause: <attributeName> is declared as type but the mapping is not using indirection. Attribute is defined to be of type but the mapping is not set to use indirection. It is thrown on foreign reference mappings.

Action: If you do not want to use indirection on the mapping, change the attribute to not be of type . Otherwise, change the mapping associated with the attribute to use indirection.

ATTRIBUTE_NAME_NOT_SPECIFIED

Cause: Attribute name is missing or not specified in the mapping definition.

Action: Specify the attribute name in the mapping by calling method .

ATTRIBUTE_TYPE_NOT_VALID

Cause: <attributeName> should be defined as type Vector, or a type that implements Map or Collection if using Java 2. It happens in one to many mapping, many to many mapping and collection mapping when mapping is set not to use indirection and attribute type is not declared of type .

Action: Declare the attribute to be of type .

CLASS_INDICATOR_FIELD_NOT_FOUND

Cause: The class indicator field has not been defined, however the descriptor has been set to use inheritance. When using inheritance, a class indicator field or class extraction method must be set. The class indicator field is used to create the right type of domain object

Action: Either a class indicator field or class extraction method must be set.

DIRECT_FIELD_NAME_NOT_SET

Cause: The direct field name from the target table is not set in the direct collection mapping. The field values form the collection in this mapping.

Action: Specify the direct field name by calling method .

FIELD_NAME_NOT_SET_IN_MAPPING

Cause: The field name is not set in the mapping. It is thrown from direct to field mapping, array mapping and structure mapping.

Action: Specify the field name by calling method .

FOREIGN_KEYS_DEFINED_INCORRECTLY

Cause: One to one mapping foreign key defined incorrectly. Multiple foreign key fields were set for one to one mapping by calling method .

Action: Use method to add multiple foreign key fields.

IDENTITY_MAP_NOT_SPECIFIED

Cause: The descriptor must use an identity map to use the Check cache does exist option. Descriptor has been set to not use identity map but the existence checking is set to be done on identity map.

Action: Either use identity map or set the existence checking to some other option.

ILLEGAL_ACCESS_WHILE_GETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: <attributeName> instance variable in object <objectName> is inaccessible. Instance variable in the domain object is not accessible. This exception is thrown when TopLink tries to access the instance variable using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_CLONING

Cause: Problem in cloning the object <domainObject>. Clone method <methodName> is not accessible. The method name specified using or the method to create clone on the domain object is not accessible by TopLink using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_CONSTRUCTOR_INSTANTIATION

Cause: The domain class does not define a public default constructor, which is needed by TopLink to create new instances of the domain class.

Action: Define one or use different instantiation policy.

ILLEGAL_ACCESS_WHILE_EVENT_EXECUTION

Cause: The descriptor callback method <eventMethodName> with as argument, is not accessible. This exception is thrown when TopLink tries to access the event method using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Trying to invoke inaccessible <methodName> on the object <objectName>. The underlying get accessor method to access an attribute in the domain object is not accessible. This exception is thrown when TopLink tries to access an attribute through method using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INSTANTIATING_METHOD_ BASED_PROXY

Cause: The method used by the Transformation mapping using a is illegal. This exception is thrown when TopLink tries to access the method using Java reflection. The problem is caused when method base value holder is getting instantiated.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INVOKING_ATTRIBUTE_METHOD

Cause: On transformation mapping the underlying attribute method used to retrieve value from the database row while reading transformation mapped attribute is not accessible.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INVOKING_FIELD_TO_METHOD

Cause: On transformation mapping the method <methodName> used to retrieve value from the object while writing transformation mapped attribute is not accessible. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INVOKING_ROW_EXTRACTION_ METHOD

Cause: Problem in extracting class from <row>; Static method <method> with <databaseRow> as argument, is not accessible. The method to extract class from row on the domain object is not accessible. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_METHOD_INSTANTIATION

Cause: Problem in creating new instance; the method <methodName> to create instances on the domain class is not accessible. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_OBSOLETE_EVENT_EXECUTION

Cause: The descriptor callback method <eventMethodName> with Session as argument, is inaccessible. This exception is thrown when TopLink tries to access the event method using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: The <attributeName> instance variable in the object <objectName> is not accessible through Java reflection. The error is thrown by Java and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_SETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Trying to invoke inaccessible method <setMethodName> on the object with parameter <parameter>. The attribute's set accessor method is not accessible through Java reflection. The error is thrown by Java and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_GETTING_VALUE_ THRU_INSTANCE_VARIABLE_ACCESSOR

Cause: Trying to get a value for an instance variable <attributeName> of type <typeName> from the object. The specified object is not an instance of the class or interface declaring the underlying field. An object is accessed to get the value of an instance variable that does not exist.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Trying to invoke method <methodName> on the object <objectName>. The get accessor method declaration on the domain object differs from the one that is defined. The number of actual and formal parameters differ, or an unwrapping conversion has failed.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_INSTANTIATING_METHOD_ BASED_PROXY

Cause: The method used by the method-based proxy in a Transformation mapping is getting illegal arguments when the value holder is getting instantiated. This exception is thrown when TopLink tries to access the method using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_INVOKING_ATTRIBUTE_ METHOD

Cause: The number of actual and formal parameters differ, or an unwrapping conversion has failed. On transformation mapping the method used to retrieve value from the database row while reading transformation mapped attribute is getting illegal argument.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_INVOKING_FIELD_TO_ METHOD

Cause: The number of actual and formal parameters differ for method <methodName> or an unwrapping conversion has failed. On transformation mapping the method used to retrieve value from the object while writing transformation mapped attribute is getting illegal argument. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_OBSOLETE_EVENT_ EXECUTION

Cause: he number of actual and formal parameters for the descriptor callback method <eventMethodName> differs, or an unwrapping conversion has failed. The callback event method is invoked with illegal argument. This exception is thrown when TopLink tries to invoke the event method using Java reflection. The error is a purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: Illegal value is being assigned to the attribute instance variable. Trying to set a value <value> for an instance variable <attributeName> of type <typeName> in the object. The specified object is not an instance of the class or interface declaring the underlying field, or an unwrapping conversion has failed.

TopLink does the assignment of value by using Java reflection. Java throws the error and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_SETTING_VALUE_THRU _METHOD_ACCESSOR

Cause: Illegal argument is being passed to the attribute's set accessor method. Trying to invoke method <setMethodName> on the object. The number of actual and formal parameters differs, or an unwrapping conversion has failed. Java throws the error and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

INSTANTIATION_WHILE_CONSTRUCTOR_INSTANTIATION

Cause: he class does not define a public default constructor, or the constructor raised an exception. The default constructor for the domain object is invoked to create new instance of the object while building new domain objects. If this Class represents an abstract class, an interface, an array class, a primitive type, or void; or if the instantiation fails for some other reason. Java throws the error and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

INVALID_DATA_MODIFICATION_EVENT

Cause: This is an exception that an application should never encounter. The exception can occur at the time of developing TopLink. In cases where one writes new mapping it is possible to get this exception. In direct collection mapping and many to many mapping the target table and relational table are populated at the end of the commit process and if data modification event is sent to any other mapping then this exception is thrown.

Action: Contact Technical Support.

INVALID_DATA_MODIFICATION_EVENT_CODE

Cause: This is an exception that an application should never encounter. The exception can occur at the time of developing TopLink. In cases where one writes new mapping it is possible to get this exception. In direct collection mapping and many to many mapping the target table and relational table are populated at the end of the commit process and if data modification event is sent to these two mappings with wrong event code then this exception is thrown.

Action: Contact Technical Support.

INVALID_DESCRIPTOR_EVENT_CODE

Cause: This is an exception that an application should never encounter. The exception can occur at the time of developing TopLink. The exception means that descriptor event manager does not support the event code passed in the event.

Action: Contact Technical Support.

INVALID_IDENTITY_MAP

Cause: Identity map constructor failed because an invalid identity map was specified. The identity map class given in the descriptor cannot be instantiated. The exception is Java exception thrown by Java reflection when TopLink is instantiating the identity map class. TopLink only wraps the Java exception.

Action: Inspect the internal exception and check the Java manuals.

JAVA_CLASS_NOT_SPECIFIED

Cause: The descriptor does not define a Java class. The Java class is not specified in the descriptor.

Action: Specify the Java Class

DESCRIPTOR_FOR_INTERFACE_IS_MISSING

Cause: A descriptor for the referenced interface is not added to the session.

Action: Add that descriptor to the session.

MAPPING_FOR_SEQUENCE_NUMBER_FIELD

Cause: A non-read-only mapping is not defined for the sequence number field. A mapping is required so that TopLink can put and extract values for the primary key.

Action: Define a mapping.

MISSING_CLASS_FOR_INDICATOR_FIELD_VALUE

Cause: Missing class for indicator field value <classFieldValue> of type <type>. There was no class entry found in the inheritance policy for the indicator field value read from the database. Probably the method was not called for the field value. The class and typeValue is stored in the hashtable and later on the class is extracted from the hashtable by passing as a key. Remember Integer(1) is not equal to Float(1), this is another major reason for this problem when the type of typeValue is different.

Action: Check descriptor.

MISSING_CLASS_INDICATOR_FIELD

Cause: The class indicator field is missing from the database row <row> that was read from the database. This is done in inheritance model where after reading rows from the database, child domain objects are to be constructed depending upon the type indicator values.

Action: Check the printed row to make sure the spelling is correct.

MISSING_MAPPING_FOR_FIELD

Cause: Missing mapping for field <field>; a mapping for the field is not specified.

Action: Define a mapping for the field.

NO_MAPPING_FOR_PRIMARY_KEY

Cause: A mapping for the primary key is not specified. There should be one non-read-only mapping defined for the primary key field.

Action: efine a mapping for the primary key.

MULTIPLE_TABLE_PRIMARY_KEY_NOT_SPECIFIED

Cause: The multiple table primary key mapping must be specified when a custom multiple table join is used. If multiple tables are specified in the descriptor and the join expression is customized then the primary keys for all the tables must be specified. If the primary keys are not specified then the exception is caused.

Action: Call method on the descriptor to set the primary keys.

MULTIPLE_WRITE_MAPPINGS_FOR_FIELD

Cause: There are multiple writable mappings for the field <fieldName> in the descriptor. Exactly one must be defined writable. The others must be specified as read-only. When multiple write mappings are defined for the field, TopLink cannot decide on which mapping to pick up for writing the value of the field in the database row hence the exception is thrown during the validation process of descriptors. The most common site for this problem is that sometimes the field has direct-to-field mapping and also one-to-one mapping. In this case if direct-to-field mapping has to be kept then one-to-one mapping should either be read-only or it should be target foreign key reference.

Action: Make one of those mappings read only.

NO_ATTRIBUTE_TRANSFORMATION_METHOD

Cause: The attribute transformation method name in the transformation mapping is not specified. This method is invoked internally by TopLink to retrieve value to store in the domain object.

Action: Define a method and set the method name on the mapping by calling method .

NO_FIELD_NAME_FOR_MAPPING

Cause: No field name is specified in direct-to-field mapping.

Action: Set the field by calling .

NO_FOREIGN_KEYS_ARE_SPECIFIED

Cause: Neither the selection criteria nor the foreign keys were specified on one-to-one mapping. If the selection criterion is not specified then TopLink tries to build one from the foreign keys specified in the mapping.

Action: Specify the fields.

NO_REFERENCE_KEY_IS_SPECIFIED

Cause: No query key named: <queryKey> found in: <descriptor>; no reference key from the target table is specified on direct collection mapping.

Action: Specify the fields by calling method .

NO_RELATION_TABLE

Cause: The relation table name is not set in this many-to-many mapping.

Action: Set relation table name by calling method .

NO_SOURCE_RELATION_KEYS_SPECIFIED

Cause: There are no source relation keys specified in this many-to-many mapping.

Action: Add source relation keys to the mapping.

NO_SUCH_METHOD_ON_FIND_OBSOLETE_METHOD

Cause: The descriptor callback method <selector> on the domain class was not found. It must take a or a as its argument. TopLink tries to invoke the method using Java reflection. It is a Java exception and TopLink is only wrapping the main exception.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_ON_INITIALIZING_ ATTRIBUTE_METHOD

Cause: The method <attributeMethodName> with parameters <databaseRow> or <databaseRow, session> is not found. TopLink wraps the Java reflection exception that is caused when the method is being created from the method name. This method is set by calling.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_CONSTRUCTOR_ INSTANTIATION

Cause: Inaccessible constructor. TopLink wraps the Java reflection exception that is caused when it is creating a new instance of the domain.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_CONVERTING_TO_METHOD

Cause: Method <methodName> not found with parameters () or (Session). TopLink wraps the Java reflection exception that is caused when it is creating a Method type from the method names in transformation mapping.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_FIELD_WHILE_INITIALIZING_ATTRIBUTES_ IN_INSTANCE_VARIABLE_ACCESSOR

Cause: The instance variable <attributeName> is not defined in the domain class or it is not accessible. TopLink wraps the Java reflection exception that is caused when it is creating a Field type from the attribute name.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_ ATTRIBUTES_IN_METHOD_ACCESSOR

Cause: The accessor method <setMethodName> or <getMethodName> is not defined for the attribute in the domain class <javaClassName>, or it is not accessible. TopLink wraps the Java reflection exception that is caused when it is creating a Method type from the method name.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_ CLASS_EXTRACTION_METHOD

Cause: The static class extraction method <methodName> with <databaseRow> as argument does not exist, or is not accessible. Java reflection exception wrapped in TopLink exception is thrown when class extraction method is being created from the method name in inheritance policy.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_COPY_POLICY

Cause: The clone method <methodName> with no arguments does not exist, or is not accessible. Java reflection exception wrapped in TopLink exception is thrown when a method to create clones is being created from the method name in copy policy.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_ INSTANTIATION_POLICY

Cause: The instance creation method <methodName> with no arguments does not exist, or is not accessible. Java reflection exception wrapped in TopLink exception is thrown when a method to create new instances is being created from the method name in instantiation policy.

Action: Inspect the internal exception and check the Java manuals.

NO_TARGET_FOREIGN_KEYS_SPECIFIED

Cause: The foreign keys in the target table are not specified in one-to-many mappings. These fields are not required if a selection criterion is given in the mapping but otherwise they must be specified.

Action: Set target foreign keys or selection criteria.

NO_TARGET_RELATION_KEYS_SPECIFIED

Cause: There are no target relation keys specified in many-to-many mappings.

Action: Call method to set the fields.

NOT_DESERIALIZABLE

Cause: The object cannot be de-serialized from the byte array read from the database. The exception is thrown when serialized object mapping is converting byte array into object.

Action: Inspect the internal exception and check the Java manuals.

NOT_SERIALIZABLE

Cause: The object cannot be serialized into byte array. The exception is thrown when serialized object mapping is object into byte array.

Action: Inspect the internal exception and check the Java manuals.

NULL_FOR_NON_NULL_AGGREGATE

Cause: Value of aggregate in the source object <object> is null. Null values not allowed for aggregate mappings unless allow null is specified in aggregate mapping.

Action: Call method ) on the mapping.

NULL_POINTER_WHILE_GETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: An object is accessed to get the value of an instance variable through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: The get accessor method is invoked to get the value of attribute through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: Null Pointer Exception is thrown while setting value of <attributeName> instance variable in the object to value. An object is accessed to set the value of an instance variable through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_SETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Null Pointer Exception is thrown while setting value through <setMethodName> method in the object with argument <argument>. The set accessor method is invoked to set the value of attribute through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

PARENT_DESCRIPTOR_NOT_SPECIFIED

Cause: Cannot find descriptor for parent class. The descriptor of a subclass has no parent descriptor.

Action: The method on the subclass descriptor must be called.

PRIMARY_KEY_FIELDS_NOT_SPECIFIED

Cause: The primary key fields are not set for this descriptor.

Action: Add primary key field names using method or .

REFERENCE_CLASS_NOT_SPECIFIED

Cause: The reference class is not specified in the foreign reference mapping.

Action: Set reference class by calling method

REFERENCE_DESCRIPTOR_IS_NOT_AGGREGATE

Cause: The referenced descriptor for <className> should be set to aggregate descriptor. An aggregate mapping should always reference a descriptor that is aggregate.

Action: Call method on the referenced descriptor.

REFERENCE_KEY_FIELD_NOT_PROPERLY_SPECIFIED

Cause: The table for the reference field must be the reference table. If the reference field name specified in the direct collection mapping is qualified with the table name then the table name should match the reference table name.

Action: Qualify the field with the proper name or change the reference table name.

REFERENCE_TABLE_NOT_SPECIFIED

Cause: The reference table name in the direct collection mapping is not specified.

Action: Use method on the mapping to set the table name.

RELATION_KEY_FIELD_NOT_PROPERLY_SPECIFIED

Cause: The table for the relation key field must be the relation table. If the source and target relation fields name specified in the many to many mapping are qualified with the table name then the table name should match the relation table name.

Action: Qualify the field with the proper name or change the relation table name.

RETURN_TYPE_IN_GET_ATTRIBUTE_ACCESSOR

Cause: The method <attributeMethodName> specified in the transformation mapping should have a return type set in the attribute because this method is used to extract value from the database row.

Action: Check the method and make appropriate changes.

SECURITY_ON_FIND_METHOD

Cause: The descriptor callback method <selector> with DescriptorEvent as argument is not accessible. Java throws security exception when a Method type is created from the method name using Java reflection. The method is a descriptor event callback on the domain object that takes DescriptorEvent as its parameter.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_ON_FIND_OBSOLETE_METHOD

Cause: The descriptor callback method <selector> with <session> as argument is not accessible. Java throws security exception when a Method type is created from the method name using Java reflection. The method is a descriptor event callback on the domain object which takes class and session as its parameters.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_ON_INITIALIZING_ATTRIBUTE_METHOD

Cause: Access to the method <attributeMethodName> with parameters <databaseRow> or <databaseRow, Session> has been denied. Java throws security exception when a Method type is created from the attribute method name using Java reflection. The attribute method specified in the transformation mapping is used to extract value from the database row and set by calling .

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_CONVERTING_TO_METHOD

Cause: Method: <methodName> ACCESS DENIED with <> or <session> parameters. Java throws security exception when a Method type is created from the method name using Java reflection. These are the methods that will extract the field value from the domain object in the transformation mapping.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_ATTRIBUTES_IN_ INSTANCE_VARIABLE_ACCESSOR

Cause: Access to the instance variable, <attributeName> in the class <javaClassName> is denied. Java throws security exception when creating Field type from the given attribute name using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_ATTRIBUTES_IN_ METHOD_ACCESSOR

Cause: The methods <setMethodName> and <getMethodName> in the object <javaClassName> are inaccessible. Java throws security exception when creating Method type from the given attribute accessor method name using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_CLASS_ EXTRACTION_METHOD

Cause: The static class extraction method <methodName> with DatabaseRow as argument is not accessible. Java throws security exception when creating Method type from the given class extraction method name using Java reflection. The method is used to extract class from the database row in inheritance policy.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_COPY_POLICY

Cause: The clone method <methodName> with no arguments is not accessible. Java throws security exception when creating Method type from the given method name using Java reflection. This method on copy policy is used to create clones of the domain object.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_INSTANTIATION_POLICY

Cause: The instance creation method <methodName> with no arguments is not accessible. Java throws security exception when creating Method type from the given method name using Java reflection. This method on instantiation policy is used to create new instances of the domain object.

Action: Inspect the internal exception and check the Java manuals.

SEQUENCE_NUMBER_PROPERTY_NOT_SPECIFIED

Cause: Either the sequence field name or the sequence number name is missing. To use sequence generated ids both the sequence number name and field name properties must be set.

Action: To use sequence-generated ids, both the sequence number name and field name properties must be set.

SIZE_MISMATCH_OF_FOREIGN_KEYS

Cause: The size of the primary keys on the target table does not match the size of the foreign keys on the source in one to one mapping.

Action: Check the mapping and the reference descriptor's primary keys.

TABLE_NOT_PRESENT

Cause: The table <tableName> is not present in the descriptor.

Action: Check the qualified field names specified in the mappings and descriptor, if these fields are qualified with the table name then those fields should have right table.

TABLE_NOT_SPECIFIED

Cause: No table is specified in the descriptor. Descriptor must have a table name defined.

Action: Call method or to set the tables on the descriptor.

TARGET_FOREIGN_KEYS_SIZE_MISMATCH

Cause: The size of the foreign keys on the target table does not match the size of the source keys on the source table in one to many mapping.

Action: Check the mapping.

TARGET_INVOCATION_WHILE_CLONING

Cause: Problem in cloning the object <domainObject> clone method. <methodName> triggered an exception. Java is throwing exception when clone method is invoked using Java reflection while cloning object. The clone method is specified on the copy policy that is usually invoked to create clones in unit of work.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_EVENT_EXECUTION

Cause: The underlying descriptor callback method <eventMethodName> with DescriptorEvent as argument, throws an exception. Java is throwing exception when descriptor event method is invoked using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_GETTING_VALUE_ THRU_METHOD_ACCESSOR

Cause: The method <methodName> on the object <objectName> is throwing an exception. Java is throwing exception while getting an attribute value from the object through method accessor.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INSTANTIATING_ METHOD_BASED_PROXY

Cause: Method has thrown an exception. Java is throwing exception while instantiating method based proxy. This happens while instantiating transformation mapping.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INVOKING_ ATTRIBUTE_METHOD

Cause: The underlying method throws an exception. Java is throwing exception while invoking attribute transformation method on transformation mapping. The method is invoked to extract value from the database row to set into the domain object.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INVOKING_FIELD_ TO_METHOD

Cause: The method <methodName> is throwing an exception. Java is throwing exception while invoking field transformation method on transformation mapping. The method is invoked to extract value from the domain object to set into the database row.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INVOKING_ROW_ EXTRACTION_METHOD

Cause: Problem in extracting class from row <row>, static method, <method> with <databaseRow as argument>. An exception was triggered Java is throwing exception while invoking class extraction method. The method is used to extract class type so that right kind of object can be created in inheritance model.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_METHOD_INSTANTIATION

Cause: Problem in creating new instance. Creation method <methodName> caused an exception. Java is throwing exception while invoking instantiation method. The method is used to create new instances of the domain objects.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_OBSOLETE_ EVENT_EXECUTION

Cause: The underlying descriptor callback method <eventMethodName> with <session> as argument, throws an exception. Java is throwing exception while invoking descriptor event method that takes session as its parameter.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_SETTING_VALUE_THRU_ METHOD_ACESSOR

Cause: The method <setMethodName> on the object is throwing an exception. Java is throwing exception while invoking set accessor method on the domain object to set an attribute value into the domain object.

Action: Inspect the internal exception and check the Java manuals.

VALUE_NOT_FOUND_IN_CLASS_INDICATOR_MAPPING

Cause: The indicator value is not found in the class indicator mapping in the parent descriptor for the class.

Action: Check on the inheritance policy.

WRITE_LOCK_FIELD_IN_CHILD_DESCRIPTOR

Cause: The child descriptor should not have a write lock field defined because it gets it from the parent descriptor.

Action: Check your child descriptor and remove the field.

DESCRIPTOR_IS_MISSING

Cause: The descriptor for the reference class <className> is missing from the mapping.

Action: Check session to see if the descriptor for the reference class was added.

MULTIPLE_TABLE_PRIMARY_KEY_MUST_BE_ FULLY_QUALIFIED

Cause: Multiple table primary key field names must be fully qualified. These fields names are given on the descriptor if it has more than one table.

Action: Specify the field names with table name.

ONLY_ONE_TABLE_CAN_BE_ADDED_WITH_THIS_METHOD

Cause: Only one table can be added through this method.

Action: Use to add multiple tables to descriptor.

NULL_POINTER_WHILE_CONSTRUCTOR_INSTANTIATION

Cause: Inaccessible constructor. Java is throwing this exception while invoking a default constructor to create new instances of the domain object.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_METHOD_INSTANTIATION

Cause: Problem in creating new instance <methodName> creation method is not accessible. Java is throwing an exception while calling a method to build new instance of the domain object. This method is given by the user to override the default behavior of creating new instances through class constructor.

Action: Inspect the internal exception and check the Java manuals.

NO_ATTRBUTE_VALUE_CONVERSION_TO_FIELD_VALUE_PROVIDED

Cause: The field conversion value for the attribute value <attributeValue> was not given in the object type mapping.

Action: Check the attribute value and provide a corresponding field value in the mapping.

NO_FIELD_VALUE_CONVERSION_TO_ATTRIBUTE_ VALUE_PROVIDED

Cause: The attribute conversion value for the <fieldValue> was not given in the object type mapping.

Action: Check the field value and provide a corresponding attribute value in the mapping.

LOCK_MAPPING_CANNOT_BE_READONLY

Cause: The domain object <className> cannot have a read only mapping for the write lock fields when the version value is stored in the object.

Action: Check the mappings on write lock fields.

LOCK_MAPPING_MUST_BE_READONLY

Cause: The domain object <className> should have a read only mapping for the write lock fields when the version value is stored in the cache.

Action: Check the mappings on write lock fields.

CHILD_DOES_NOT_DEFINE_ABSTRACT_QUERY_KEY

Cause: The queryKey <queryKeyName> is defined in the parent descriptor but not in the child descriptor. The descriptor has not defined abstract query key.

Action: Any implementors of interface descriptor must define the query key defined by abstract query key in the interface descriptor.

SET_EXISTENCE_CHECKING_NOT_UNDERSTOOD

Cause: The interface descriptor <parent> must have at least one abstract query key defined. The string given to the method is not understood.

Action: The string passed should be one of the following:

  • Check cache
  • Check database
  • Assume existence
  • Assume non-existence

VALUE_HOLDER_INSTANTIATION_MISMATCH

Cause: The mapping for the attribute uses indirection and must be initialized to a new ValueHolder.

Action: Ensure the mapping uses indirection and the attribute is initialized to a new .

NO_SUB_CLASS_MATCH

Cause: No sub-class matches this class <theClass> when inheritance is in aggregate relationship mapping.

Action: Verify the sub-class and the relationship mapping.

RETURN_AND_MAPPING_WITH_INDIRECTION_MISMATCH

Cause: The get method return type for the attribute () is not declared as type , but the mapping is using indirection.

Action: Ensure the get method returns a or change the mapping to not use indirection.

RETURN_AND_MAPPING_WITHOUT_INDIRECTION_ MISMATCH

Cause: The get method return type for the attribute is declared as type , but the mapping is not using indirection.

Action: Ensure the mapping is using indirection or change the return type from

PARAMETER_AND_MAPPING_WITH_INDIRECTION_ MISMATCH

Cause: The set method parameter type for the attribute is not declared as type , but the mapping is using indirection.

Action: Ensure the set method parameter is declared as a or the mapping is changed to not use indirection.

PARAMETER_AND_MAPPING_WITHOUT_INDIRECTION_ MISMATCH

Cause: The set method parameter type for the attribute is declared as type , but the mapping is not using indirection.

Action: Ensure the mapping is changed to use indirection or the set method parameter is not declared as a .

GET_METHOD_RETURN_TYPE_NOT_VALID

Cause: he get method return type for the attribute should be declared as type Vector (or a type that implements Map or Collection, if using Java2).

Action: The get method return type for the attribute should be declared as type Vector (or a type that implementsMap or Collection, if using Java2).

SET_METHOD_PARAMETER_TYPE_NOT_VALID

Cause: The set method parameter type for the attribute should be declared as type Vector (or a type that implements Map or Collection, if using Java2).

Action: The set method parameter type for the attribute should be declared as type Vector (or a type that implements Map or Collection, if using Java2).

ILLEGAL_TABLE_NAME_IN_MULTIPLE_TABLE_ FOREIGN_KEY

Cause: The table in the multiple table foreign key relationship refers to an unknown table.

Action: Verify the table name.

ATTRIBUTE_AND_MAPPING_WITH_TRANSPARENT_ INDIRECTION_MISMATCH

Cause: The attribute is not declared as a super-type of , but the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.

RETURN_AND_MAPPING_WITH_TRANSPARENT_ INDIRECTION_MISMATCH

Cause: The get method return type for the attribute is not declared as a super-type of , but the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.

PARAMETER_AND_MAPPING_WITH_TRANSPARENT_ INDIRECTION_MISMATCH

Cause: The set method parameter type for the attribute is not declared as a super-type of , but the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.

FIELD_IS_NOT_PRESENT_IN_DATABASE

Cause: Field <fieldname> is not present in the table <tableName> in the database.

Action: Verify the field name for the attribute.

TABLE_IS_NOT_PRESENT_IN_DATABASE

Cause: is not present in the database.

Action: Verify the table name for the descriptor.

MULTIPLE_TABLE_INSERT_ORDER_MISMATCH

Cause: The multiple table insert order Vector specified , has more/fewer tables than are specified in the descriptor . All the tables must be included in the insert order Vector.

Action: Verify that all table names for the descriptor are present and that there are no extras.

INVALID_USE_OF_TRANSPARENT_INDIRECTION

Cause: Transparent Indirection can only be used with CollectionMappings.

Action: Verify the mapping. It must be a collection mapping.

MISSING_INDIRECT_CONTAINER_CONSTRUCTOR

Cause: The indirect container class must implement the constructor.

Action: Implement the constructor for the container.

COULD_NOT_INSTANTIATE_INDIRECT_CONTAINER_CLASS

Cause: The indirect container class could not be instantiated using the constructor.

Action: Validate the constructor for the indirect container class.

INVALID_CONTAINER_POLICY

Cause: This container policy should only be used in JDK containerPolicy. It was instantiated for javaClass.

Action: Validate the container policy being used.

INVALID_CONTAINER_POLICY_WITH_TRANSPARENT_ INDIRECTION

Cause: The container policy is incompatible with transparent indirection.

Action: Change the container policy to be compatible with transparent indirection or do not use transparent indirection.

INVALID_USE_OF_NO_INDIRECTION

Cause: No Indirection should not receive this message.

Action: Change to use no indirection.

INDIRECT_CONTAINER_INSTANTIATION_MISMATCH

Cause: The mapping for the attribute uses transparent indirection and must be initialized to an appropriate container.

Action: Initialize the mapping to an appropriate container.

INVALID_MAPPING_OPERATION

Cause: Invalid mapping operation.

Action: Check the documentation for valid mapping operations.

INVALID_INDIRECTION_POLICY_OPERATION

Cause: Invalid indirection policy operation.

Action: Check the documentation for valid indirection policy operations.

REFERENCE_DESCRIPTOR_IS_NOT_ AGGREGATECOLLECTION

Cause: The reference descriptor for <className> should be set to aggregate collection descriptor.

Action: Set the reference descriptor to an aggregate collection descriptor.

INVALID_INDIRECTION_CONTAINER_CLASS

Cause: Invalid indirection container class.

Action: Verify the container class.

MISSING_FOREIGN_KEY_TRANSLATION

Cause: The mapping does not include a foreign key field linked to the primary key field.

Action: Link the foreign key to the appropriate primary key.

TRUCTURE_NAME_NOT_SET_IN_MAPPING

Cause: The structure name is not set.

Action: Set the structure name appropriately.

NORMAL_DESCRIPTORS_DO_NOT_SUPPORT_ NON_RELATIONAL_EXTENSIONS

Cause: Normal descriptors do not support non-relational extensions.

Action: Contact Technical Support.

PARENT_CLASS_IS_SELF

Cause: The descriptor's parent class has been set to itself.

Action: Contact Technical Support.

PROXY_INDIRECTION_NOT_AVAILABLE

Cause: An attempt to use proxy indirection has been made but JDK is not being used.

Action: Proxy indirection is only supported in JDK

INVALID_ATTRIBUTE_TYPE_FOR_PROXY_INDIRECTION

Cause: The attribute wasn't specified in the list of interfaces given to use Proxy Indirection.

Action: Verify the attribute

INVALID_GET_RETURN_TYPE_FOR _PROXY_INDIRECTION

Cause: The return type for the indirection policy is invalid for the indirection policy.

Action: Verify that the parameter type of the attribute's get method is correct for the indirection policy.

INVALID_SET_PARAMETER_TYPE_FOR_PROXY_ INDIRECTION

Cause: The parameter for the set method is incorrect for the indirection type.

Action: Verify that the parameter type of the attribute's set method is correct for the indirection policy.

INCORRECT_COLLECTION_POLICY

Cause: The container policy is invalid for the collection type.

Action: Check that the container policy is correct for the collection type.

INVALID_AMENDMENT_METHOD

Cause: The amendment method provided is invalid, not public, or cannot be found.

Action: Ensure the amendment method is public, static, returns void and has a single argument: Descriptor.

ERROR_OCCURRED_IN_AMENDMENT_METHOD

Cause: The specified amendment method threw an exception.

Action: Examine the returned exception for further details.

VARIABLE_ONE_TO_ONE_MAPPING_IS_NOT_DEFINED

Cause: There is no mapping for attribute.

Action: Validate the mapping and attribute.

TARGET_INVOCATION_WHILE_CONSTRUCTOR_ INSTANTIATION

Cause: Constructor is missing.

Action: Make the required constructor.

TARGET_INVOCATION_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: Constructor is missing.

Action: Make the required constructor.

ILLEGAL_ACCESS_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: Permissions do not permit access to the constructor.

Action: Adjust the Java security permissions to permit access to the constructor.

INSTANTIATION_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: An instantiation failed inside the associated constructor.

Action: Determine which objects are being instantiated, and ensure all are being done properly.

NO_SUCH_METHOD_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: A message send invoked from inside the constructor is invalid because the method does not exist.

Action: Correct the message send ensuring that the message exists.

NULL_POINTER_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: A message is being sent from inside a constructor to a null object.

Action: Avoid sending a message to an object that is null.

ILLEGAL_ACCESS_WHILE_METHOD_ INSTANTIATION_OF_FACTORY

Cause: A message is being sent to an object from inside a factory instantiation. Java has determined this message to be illegal.

Action: Determine why the message send is illegal, and replace the message with the proper legal one.

TARGET_INVOCATION_WHILE_METHOD_ INSTANTIATION_OF_FACTORY

Cause: Error inside the factory associated with the invocation of a target.

Action: Determine the faulty target, and replace with the correct target, or proper message send.

NULL_POINTER_WHILE_METHOD_ INSTANTIATION_OF_FACTORY

Cause: A message is being sent to null inside a factory instantiation.

Action: Avoid sending a message to null.

No such method

Cause: Tokens in the builder generated files are the subsets of all the tokens a Project Reader can understand. Each token has a related public method on TopLink. The exception would mean that the method name is incorrect.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not find post load method <methodName> on class <aClass>

Cause: The post load method defined in descriptor properties is not defined on the related domain class.

Action: Must define the method on the specified class.

Cannot write parameter <object> of class <type>

Cause: While creating project class the parameter tokens are read from the file and are converted to actual types before sending them to the methods. An unknown type will cause this exception.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not access method <method>

Cause: Java is throwing an illegal access reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invoking <applyResultMethod> raised exception <exception>

Cause: Java is throwing an invocation reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invalid arguments invoking: <applyResultMethod> with <receiver>

Cause: Java is throwing an invalid argument reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not access <applyResultMethod> with <receiver>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Parameter mismatch <method>; received <size> parameters

Cause: The number of parameters for the token read from the project or descriptor file do not match the number of parameters a related method can take.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Accessing <methodName> on <className> with <parameters>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not find section definition <section> when building section definitions for <target>

Cause: Invalid section name was found in the project or descriptor file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not convert <object> into an accessible Java class.

Cause: The parameter read from the file cannot be converted to a appropriate type.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

File not found

Cause: The project or descriptor file was not found.

Action: Check that the path was given correctly in a project reader and also the path is correct in project file.

Invalid class/method name format.

Cause: No one should actually be using the URL way of reading INI files. This is untested and undocumented feature.

Action: Use other ways of reading files.

Open failed for URL <url>

Cause: Open failed for URL.

Action: Inspect the internal exception and check the Java manuals.

Could not resolve INIFile location: <sourceString> using search paths <searchPaths>

Cause: The file was not found on the given search paths.

Action: Check your search paths.

Invoking <method> on <receiver>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invoking <method> on <receiver>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invalid character value; expecting $* format

Cause: An invalid character format was written to the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Unexpected character: {

Cause: Unexpected character { found while reading vector values from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Unexpected character: }

Cause: Unexpected character } found while reading vector values from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Expecting object, found token <nextToken>

Cause: Unexpected token found while reading from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Unexpected word

Cause: Unexpected token found while reading from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

setExistenceChecking <token>; not understood

Cause: Existence checking string specified on the descriptor is not understood.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Class <className> not found

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Not enough INI elements. Found <count>.

Cause: If the line in an INI file is incomplete, i.e., it does not have enough tokens.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Too many INI elements. Found <count>.

Cause: If the line in an INI file has more tokens then needed.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Error writing <writeString>

Cause: Could not write into the file. Perhaps are used and file or directory structure does not exist.

Action: Inspect the internal exception and check the Java manuals. Try using .

Illegal access exception

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Invocation target exception

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Attempting to instantiate <className> with default constructor.

Cause: Java is throwing reflection exception while instantiating the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Attempting to instantiate <className> with default constructor.

Cause: Java is throwing reflection exception while instantiating the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

IO Exception in next token

Cause: Java is throwing reflection. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

IOException on close.

Cause: Java is throwing reflection. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Invalid INI(URL) Method: <method>. Should return a string.

Cause: No one should actually be using the URL way of reading INI files. This is untested and undocumented feature.

Action: Use other ways of reading files.

Could not cast using <castString>.

Cause: An error occurred during an attempt to cast using the

Action: Validate the

A writer or a target file name must be specified

Cause: A writer or a target file name is not specified.

Action: A writer or a target file name must be specified.

IOException on open.

Cause: Java is throwing reflection. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Post Load Method Not Static

Cause: The method specified is not static.

Action: Modify the method to be static.

Project Not Found.

Cause: No projects were found in the specified directory.

Action: Verify the directory.

Multiple Projects With Name.

Cause: More than one project with the same name was found.

Action: Verify the project name.

WAIT_WAS_INTERRUPTED

Cause: In a multi threaded environment one of the waiting thread was interrupted.

Action: Usually such exceptions would mean restarting the application but it is totally dependent on the application.

WAIT_FAILURE_SERVER

Cause: Wait failure on ServerSession. When the number of non-pooled connections reach the threshold any more requests for such connection results in wait until some one releases the connection resource. If this wait was interrupted then an exception is thrown.

Action: Usually such exceptions would mean restarting the application but it is totally dependent on the application.

WAIT_FAILURE_CLIENT

Cause: Wait failure on ClientSession. When the number of pooled connections reach the threshold any more requests for such connection results in wait until some one releases the connection resource. If this wait was interrupted then an exception is thrown.

Action: Usually such exceptions would mean restarting the application but it is totally dependent on the application.

SIGNAL_ATTEMPTED_BEFORE_WAIT

Cause: A signal was attempted before wait on concurrency manager. This normally means that an attempt was made to commit or rollback a transaction before it was started, or to rollback a transaction twice.

Action: Check transactions in the application.

COULD_NOT_BE_CONVERTED

Cause: The object <object> of class <objectClass> could not be converted to <javaClass>. The object cannot be converted to given type.

Action: Check that the object being converted is of right type or not.

INCORRECT_DATE_FORMAT

Cause: The date in <dateString> is in an incorrect format. Expected format is YYYY-MM-DD.

Action: Check the date format.

INCORRECT_TIME_FORMAT

Cause: The time in <timeString> is in an incorrect format. Expected format is HH:MM:SS.

Action: Check the time format.

INCORRECT_TIMESTAMP_FORMAT

Cause: The timestamp <timestampString> is in an incorrect format. Expected format is YYYY-MM-DD HH:MM:sprers.euNNN.

Action: Check the timestamp format.

COULD_NOT_CONVERT_TO_BYTE_ARRAY

Cause: The String object must be of even length to be converted to a ByteArray. This object could not be converted to a ByteArray

Action: Check the object being converted.

COULD_NOT_BE_CONVERTED_TO_CLASS

Cause: The object <object> of class <objectClass> could not be converted to <javaClass>. The class <javaClass> is not on the CLASSPATH.

Action: Check that the class <javaClass> is on the CLASSPATH.

SQL_EXCEPTION

Cause: An SQL exception was encountered, thrown by the underlying JDBC bridge. TopLink only wraps that exception.

Action: One must inspect the internal exception thrown.

CONFIGURATION_ERROR_CLASS_NOT_FOUND

Cause: The driver class name was not found.

Action: Check the class name given in JDBCLogin.

DATABASE_ACCESSOR_NOT_CONNECTED

Cause: Session is not connected to the database while doing reading or writing on the database.

Action: An application may have to login again because the connection to the database might have been lost.

ERROR_READING_BLOB_DATA

Cause: Error reading blob data from the database. There are two possibilities for this exception, first is that the blob data was not read properly from the result set or the TopLink could not process the blob data using .

Action: Check if the underlying driver support blobs properly or not and if it does then report this problem to Technical Support.

OULD_NOT_CONVERT_OBJECT_TYPE

Cause: Could not convert object type on internal error. sprers.eu = <type>. The object from the result set cannot be converted to the type returned from the metadata information.

Action: Check if the underlying driver support the conversion type properly or not and if it does then report this problem to Technical Support.

LOGOUT_WHILE_TRANSACTION_IN_PROGRESS

Cause: An attempt has been made to logout while the transaction is still in progress. You cannot logout while a transaction is in progress.

Action: Wait until the transaction is over.

SEQUENCE_TABLE_INFORMATION_NOT_COMPLETE

Cause: The sequence information given to TopLink is not sufficiently complete to get the set of sequence numbers from the database. This usually happens on native sequencing on oracle database.

Action: Check the data given specially the sequence name given in TopLink.

ERROR_PREALLOCATING_SEQUENCE_NUMBERS

Cause: Error preallocating sequence numbers on the database; the sequence table information is not complete.

Action: Check if the sequence table was created on the database properly or not.

CANNOT_REGISTER_SYNCHRONIZATIONLISTENER_ FOR_UNITOFWORK

Cause: Cannot register Synchronization Listener: underlying_exception_string. When the TopLink Session is configured with an , any unit of work requested by a client must operate within the context of a JTS external global transaction. When a unit of work is created and the external global transaction is not in existence or if the system cannot acquire a reference to it, this error is reported.

Action: Ensure that a JTS transaction is in progress before acquiring the unit of work.

SYNCHRONIZED_UNITOFWORK_DOES_NOT_ SUPPORT_COMMITANDRESUME

Cause: Synchronized does not support the operation. When the TopLink Session is configured with an , any unit of work requested by a client must operate within the context of a JTS external global transaction (see Error code: ). The JTS specification does not support the concept of "checkpointing" a transaction, that is, committing the work done and then continuing to work within the same transaction context (JTS does not support nested transactions, either). Thus, if client code invokes on a "synchronized" unit of work, this error will be reported.

Action: None.

CONFIGURATION_ERROR_NEW_INSTANCE_ INSTANTIATION_EXCEPTION

Cause: Configuration error. Attempting to instantiate Driver: <javaClass>. Could not instantiate driver.

Action: Check the driver.

CONFIGURATION_ERROR_NEW_INSTANCE_ILLEGAL_ ACCESS_EXCEPTION

Cause: A configuration error occurred while attempting to instantiate . Could not instantiate driver.

Action: Check the driver.

TRANSACTION_MANAGER_NOT_SET_FOR_JTS_DRIVER

Cause: The transaction manager has not been set for the .

Action: Set a transaction manager for the .

NO_VERSION_NUMBER_WHEN_DELETING

Cause: An attempt was made to delete the object <object> but it has no version number in the identity map. This object either was never read or has already been deleted.

Action: Logging SQL is very helpful in understanding the reason why the exception is thrown. The last delete will show the object we are deleting that throws an exception.

OBJECT_CHANGED_SINCE_LAST_READ_WHEN_DELETING

Cause: The object state has changed in the database. The object <object> cannot be deleted because it has changed or been deleted since it was last read. This usually means that the row in the table was changed by some other application.

Action: Refreshing an object will refresh the object with the new data from the database.

NO_VERSION_NUMBER_WHEN_UPDATING

Cause: An attempt has been made to update the object <object> but it has no version number in the identity map. It may not have been read before being updated or has been deleted.

Action: Logging SQL is very helpful in understanding the reason why the exception is thrown. The last update will show the object we are updating that throws an exception.

OBJECT_CHANGED_SINCE_LAST_READ_WHEN_UPDATING

Cause: The object state has changed in the database. The object <object> cannot be updated because it has changed or been deleted since it was last read. This usually means that the row in the table was changed by some other application.

Action: Refreshing an object will refresh the object with the new data from the database.

MUST_HAVE_MAPPING_WHEN_IN_OBJECT

Cause: The object <aClass> must have a non-read-only mapping corresponding to the version lock field. The mapping was not defined for the locking field. It is needed when the lock value is stored in the domain object than in a cache.

Action: Define a mapping for the field.

NEED_TO_MAP_JAVA_SQL_TIMESTAMP

Cause: A write lock value which is stored in a domain object is not an instance of.

Action: Change the value of the attribute to be an instance of .

ADDITIONAL_SIZE_QUERY_NOT_SPECIFIED

Cause: Cursored SQL queries must provide an additional query to retrieve the size of the result set. Custom queries using cursor streams and not specifying the size query will cause this exception. The size query is used to retrieve the size of the number of object read from the database. This is done on JDBC compatible drivers because it provides no way to extract the size of the result set read. Non custom queries using cursor streams will have default queries generated by TopLink.

Action: Specify a size query.

AGGREGATE_OBJECT_CANNOT_BE_DELETED

Cause: Aggregated objects cannot be written or deleted independent of their owners. There is no identity maintained on such objects.

Action: Application's discretion.

ARGUMENT_SIZE_MISMATCH_IN_QUERY_AND_ QUERY_DEFINITION

Cause: The number of arguments provided to the query for execution does not match the number of arguments provided with the query definition.

Action: Check the query and query execution.

BACKUP_CLONE_IS_ORIGINAL_FROM_PARENT

Cause: The object of class with identity hashcode is not from this unit of work space but from the parent session. The object was never registered in this unit of work but read from the parent session and related to an object registered in the unit of work.

Action: Ensure that you are correctly registering your objects. If you are still having problems, you can use the method to help debug where the error occurred. Please see the manual and FAQ for more information.

BACKUP_CLONE_IS_ORIGINAL_FROM_SELF

Cause: The object clone of class with identity hashcode is the original to a registered new object. The unit of work clones registered new objects, so you must ensure that it is registered before it is reference by another object. If you do not want the new object to be cloned, used the U API.

Action: Ensure that you are correctly registering your objects. If you are still having problems, you can use the method to help debug where the error occurred. Please see the manual and FAQ for more information.

BATCH_READING_NOT_SUPPORTED

Cause: This mapping does not support batch reading. The optimization of batching the read of all the target rows is not supported for the mapping.

Action: The problem is a TopLink development problem and user should never encounter this unless the mapping is a new custom mapping. Contact Technical Support.

DESCRIPTOR_IS_MISSING

Cause: Missing descriptor for <reference Class>. The descriptor related to the class or the object is not found in the session.

Action: Check if the related descriptor was added to the session or the query is done on the right object or class.

DESCRIPTOR_IS_MISSING_FOR_NAMED_QUERY

Cause: Missing descriptor for <domain Class Name> for query named <queryName>. 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.

INCORRECT_SIZE_QUERY_FOR_CURSOR_STREAM

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.

INVALID_QUERY

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.

INVALID_QUERY_KEY_IN_EXPRESSION

Cause: The query key <key> does not exist. 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.

INVALID_QUERY_ON_SERVER_SESSION

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.

Action: Use client session's unit of work to change the object.

NO_CONCRETE_CLASS_INDICATED

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.

NO_CURSOR_SUPPORT

Cause: No cursor support provided for abstract class multiple table descriptors using expressions.

Action: Consider using custom SQL or multiple queries. <query>

OBJECT_TO_INSERT_IS_EMPTY

Cause: There are no fields to be insert into the table. The fields to insert into the table, <table> is empty. You must define at least one mapping for this table

Action: Must define at least one mapping for this table.

OBJECT_TO_MODIFY_NOT_SPECIFIED

Cause: An object to modify is required for a modify query.

Action: Ensure the query contains an object before executing.

QUERY_NOT_DEFINED

Cause: Query is not defined. When executing query on the session the parameter which takes query is null.

Action: Check if the query is passed properly.

QUERY_SENT_TO_INACTIVE_UNIT_OF_WORK

Cause: The unit of work has been released and is now inactive.

Action: The unit of work, once released, cannot be reused unless commitAndResume is called.

READ_BEYOND_QUERY

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.

REFERENCE_CLASS_MISSING

Cause: The reference class in the query is not specified. A reference class must be provided.

Action: Check the query.

REFRESH_NOT_POSSIBLE_WITHOUT_CACHE

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.

Action: Check query.

SIZE_ONLY_SUPPORTED_ON_EXPRESSION_QUERIES

Cause: Did not find size query. Size only supported on expression queries, unless a size query is given.

Action: Cursor streams on custom query should also define size query.

SQL_STATEMENT_NOT_SET_PROPERLY

Cause: The SQL statement has not been properly set. The user should never encounter this unless queries have been customized.

Action: Contact Technical Support.

INVALID_QUERY_ITEM

Cause: Invalid query item expression.

Action: Validate the Expression being used.

SELECTION_OBJECT_CANNOT_BE_NULL

Cause: The selection object passed to a read object or refresh was null.

Action: Check on the read query.

UNNAMED_QUERY_ON_SESSION_BROKER

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.

REPORT_RESULT_WITHOUT_PKS

Cause: ReportQuery without PKs cannot readObject. 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 on report query.

NULL_PRIMARY_KEY_IN_BUILDING_OBJECT

Cause: The primary key read from the row, <databaseRow> during the execution of the query was detected to be null; primary keys must not contain null.

Action: Check query and also the table on the database.

NO_DESCRIPTOR_FOR_SUBCLASS

Cause: The subclass has no descriptor defined for it.

Action: Check session if the descriptor was added or not or else check class extraction method.

CANNOT_DELETE_READ_ONLY_OBJECT

Cause: Cannot delete an object of read-only class. The class <className> is declared read-only in this unit of work. Thrown in unit of work when trying to delete an object that is marked as read only.

Action: Contact Technical Support.

INVALID_OPERATOR

Cause: The operator <data> used in the expression is not valid.

Action: Check class to see a list of all of the operators supported.

ILLEGAL_USE_OF_GETFIELD

Cause: Illegal use of <data> in expression. This is a TopLink development exception that users should not encounter.

Action: Report this problem to Technical Support.

ILLEGAL_USE_OF_GETTABLE

Cause: Illegal use of <data> in expression. This is a TopLink development exception that users should not encounter.

Action: Report this problem to Technical Support.

REPORT_QUERY_RESULT_SIZE_MISMATCH

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.

CANNOT_CACHE_PARTIAL_OBJECT

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 .

Action: Call the method before executing the query.

OUTER_JOIN_ONLY_VALID_FOR_ONE_TO_ONE

Cause: An outer join () is only valid for one to one mappings, and cannot be used for the mapping.

Action: Do not attempt to use for mappings other than one to one.

CANNOT_ADD_TO_CONTAINER

Cause: Cannot add <anObject> to a <containerClass> using <policy>. This is TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Contact Technical Support.

METHOD_INVOCATION_FAILED

Cause: The method invocation of <aMethod> on the object <anObject> threw a Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

CANNOT_CREATE_CLONE

Cause: Cannot create a clone of <anObject> using <policy>. This is a TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Report this problem to Technical Support.

METHOD_NOT_VALID

Cause: The method <methodName> is not valid to call on object <aReceiver>. This is a TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Contact Technical Support.

METHOD_DOES_NOT_EXIST_IN_CONTAINER_CLASS

Cause: The method named <methodName> was not found in class <aClass>. Thrown when looking for clone method on the container class. The clone is needed to create clones of the container in unit of work.

Action: Define clone method on the container class.

COULD_NOT_INSTANTIATE_CONTAINER_CLASS

Cause: The class <aClass> cannot be used as the container for the results of a query since it cannot be instantiated. Thrown when new interface container policy is being created using Java reflection.

Action: Check Java documentation on the internal exception.

MAP_KEY_NOT_COMPARABLE

Cause: Could not use object <anObject> of type <objectClass> as a key into <aContainer> which is of type <containerClass>. Key cannot be compared with the keys currently in the map. Throws Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

CANNOT_ACCESS_METHOD_ON_OBJECT

Cause: Cannot reflectively access the method <aMethod> for object: <anObject> of type <anObjectClass>. Throws Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

CALLED_METHOD_THREW_EXCEPTION

Cause: The method <aMethod> was called reflectively on object <object> of class <objectClass> and threw an exception. Throws Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

INVALID_OPERATION

Cause: Invalid operation <operation> on cursor. The operation is not supported.

Action: Check the class documentation and look for the corresponding method that should be used.

CANNOT_REMOVE_FROM_CONTAINER

Cause: Cannot remove <anObject> of type <anObjectClass> from <aContainerClass> using <policy>. This is TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Contact Technical Support.

CANNOT_ADD_ELEMENT

Cause: Cannot add element to the collection container policy (cannot add <anObject> of type <anObjectClass> to a <aContainerClass>).

Action: Check Java documentation on the internal exception.

BACKUP_CLONE_DELETED

Cause: Deleted objects cannot have reference after being deleted. The object clone of class <sprers.euss()> with identity hashcode (sprers.eutyHashCode()) <sprers.eutyHashCode(clone)> has been deleted, but still has references.

Action: Ensure that you are correctly registering your objects. If you are still having problems, you can use the method to help debug where the error occurred. Please see the manual and FAQ for more information.

CANNOT_COMPARE_TABLES_IN_EXPRESSION

Cause: Cannot compare table reference to <data> in expression

Action: Check the expression

INVALID_TABLE_FOR_FIELD_IN_EXPRESSION

Cause: Field has invalid table in this context for field <data> in expression.

Action: Check the expression

INVALID_USE_OF_TO_MANY_QUERY_KEY_IN_EXPRESSION

Cause: Invalid use of a query key representing a to-many relationship <data> in expression. Use rather than .

Action: Use the operator instead of .

INVALID_USE_OF_ANY_OF_IN_EXPRESSION

Cause: Invalid use of for a query key not representing a to-many relationship <data> in expression. Use rather than .

Action: Use the operator instead of .

CANNOT_QUERY_ACROSS_VARIABLE_ONE_TO_ ONE_MAPPING

Cause: Querying across a variable one-to-one mapping is not supported.

Action: Change the expression such that the query in not done across a variable one to one mapping.

ILL_FORMED_EXPRESSION

Cause: Ill-formed expression in query, attempting to print an object reference into a SQL statement for <queryKey>.

Action: Contact Technical Support.

CANNOT_CONFORM_EXPRESSION

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.

INVALID_OPERATOR_FOR_OBJECT_EXPRESSION

Cause: Object comparisons can only use the or operators, other comparisons must be done through query keys or direct attribute level comparisons.

Action: Ensure the query uses only and if object comparisons are being used.

UNSUPPORTED_MAPPING_FOR_OBJECT_COMPARISON

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.

OBJECT_COMPARISON_CANNOT_BE_PARAMETERIZED

Cause: Object comparisons cannot be used in parameter queries.

Action: Change the query such that it does not attempt to use object when using parameterized queries.

INCORRECT_CLASS_FOR_OBJECT_COMPARISON

Cause: The class of the argument for the object comparison is incorrect.

Action: Ensure the class for the query is correct.

CANNOT_COMPARE_TARGET_FOREIGN_KEYS_ TO_NULL

Cause: Object comparison cannot be used for target foreign key relationships. Query on the source primary key instead.

Action: Query on source primary key.

INVALID_DATABASE_CALL

Cause: Invalid database call - the call must be an instance of DatabaseCall: <call>.

Action: Ensure the call being used is a DatabaseCall.

INVALID_DATABASE_ACCESSOR

Cause: Invalid database accessor - the accessor must be an instance of DatabaseAccessor: <accessor>.

Action: Ensure the accessor being used is a DatabaseAccessor.

METHOD_DOES_NOT_EXIST_ON_EXPRESSION

Cause: Method: <methodName> with argument types: <argTypes> cannot be invoked on Expression.

Action: Ensure the method being used is a supported method.

IN_CANNOT_BE_PARAMETERIZED

Cause: Queries using IN cannot be parameterized.

Action: Either disable the query prepare or binding.

REDIRECTION_CLASS_OR_METHOD_NOT_SET

Cause: The redirection query was not configured properly, the class or method name was not set.

Action: Check the configuration for the redirection class.

REDIRECTION_METHOD_NOT_DEFINED_CORRECTLY

Cause: The redirection query's method is not defined or define with the wrong arguments. It must be public static and have arguments DatabaseQuery, DatabaseRow, Session (the interface).

Action: Check the redirection query's method as above.

REDIRECTION_METHOD_ERROR

Cause: The redirection query's method invocation threw an exception.

Action: Check the redirection method for problems.

EXAMPLE_AND_REFERENCE_OBJECT_CLASS_MISMATCH

Cause: There is a class mismatch between the example object and the reference class specified for this query.

Action:

iOS update and restore errors

Learn how to solve iOS update and restore errors.

Try these steps first

  1. On a Mac with macOS Catalina  or later, make sure your Mac is up to date. If you have a Mac with macOS Mojave or earlier, or a PC, make sure you have the latest version of iTunes.
  2. If your device couldn't be restored and you get a message that "an unknown error occurred [error number]," use these steps. 

If you still see the error, try the steps below.

Choose your error number or message

To learn what to do, choose your error:

  • 1, 2, 3, 4, 6, 9, 10, 11, 12, 13, 14, 16, 17 
  • 20, 21, 23, 26, 27, 28, 29, 34, 35, 36, 37,
    40, 53, 56
  • , , , , , 
  • , , , , , , , 
    –, , ,
  • , , , , 
  • , , , , , , 
  • , , ,

Update the software on your Mac or PC

If you see error 10, your iOS device might have a newer version of iOS than is supported by your computer. You'll need to update the software on your Mac or iTunes on Windows before you can update or restore your iOS device.

macOS and later:

  1. Disconnect and then reconnect your iOS device to your computer. You might need to unlock your iOS device before it is recognized by your Mac.
  2. When you see a message that says a software update is required to connect to your iOS device, click Install to download and install the software so your Mac can update or restore your iOS device.

Windows: Update to latest version of iTunes.

If you continue to see error 10, or you don't see a dialog asking you to update the software on your mac, contact Apple Support.

Make sure that your device can communicate with Apple servers

If you see error , your computer is downloading necessary software. Wait for the download to finish, then try again.

If you see one of the errors below, your computer might not be able to connect to Apple servers or your iPhone, iPad, or iPod touch:

  • 17, , , , , , , , , , ,
  • "There was a problem downloading the software."
  • "The device isn't eligible for the requested build."

Here's what to check:

  1. Make sure that your computer can communicate with the Apple software-update servers.
  2. Check your third-party security software.

If you see error , your computer is unable to update your device because it's passcode locked and the device wasn't unlocked for the update or restore. Unlock your device and try again. Learn what to do if you forgot your passcode.

If you still see an error, contact Apple Support.

Cellular Update Failed or Apple Pay Not Available alert

If you see either "Cellular Update Failed" or "Apple Pay requires an Update on this iPhone" alert after an update, learn what to do.

Check your security software

Check your USB connections

If you see error , , or , use these steps.

If you see one of the errors below, check your USB connection, USB cable, USB port, or computer:

  • 13, , , , , , , –
  • , , , , ,
  • An error that includes "invalid response"

Here's what to check. Try again after each step:

  1. Use the USB cable that came with your device. If you don't have it, try a different Apple USB cable. 
  2. Switch to a different USB port on your computer. Don't plug into your keyboard.
  3. Switch to a USB port on a different computer.
  4. If you still see the error, check for other USB issues, check your third-party security software, then check your hardware.

If you still see an error, contact Apple Support.

Check your hardware

If you see error 53, use these steps.

If you see one of the errors below, you might have a hardware issue:

  • 1, 3, 11, 12, 13, 16
  • 20, 21, 23, 26, 27, 28, 29, 34, 35, 36, 37, 40, 56
  • , , , , , ,

Here's what to check. Try again after each step:

  1. If iTunes is already open, quit and reopen it.
  2. Check your third-party security software.
  3. Make sure that your USB cable, computer, and network are reliable. Then try twice more to restore your device.
  4. Check for outdated or modified software. 

If you still see the error, contact Apple Support.

Published Date: 

Symptoms

Assume that you have an Always On Availability Group (AG) in an instance of Microsoft SQL Server or  When you back up a secondary replica that is running under asynchronous-commit mode, the backup operation may fail occasionally. Additionally, you may receive the following error message:

Error: , Severity: 20, State: 1.

The log scan number (nnn:nnn:nnn) passed to log scan in database 'dbname' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.

Resolution

This problem is fixed in the following updates for SQL Server:

Cumulative Update 13 for SQL Server

Cumulative Update 4 for SQL Server Service Pack 2

Cumulative Update 11 for SQL Server Service Pack 1

About SQL Server builds

Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server:

Latest cumulative update for SQL Server

The latest build for SQL Server

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology Microsoft uses to describe software updates.

1. Result Codes versus Error Codes

Overview

Many of the routines in the SQLite C-language Interface return numeric result codes indicating either success or failure, and in the event of a failure, providing some idea of the cause of the failure. This document strives to explain what each of those numeric result codes means.

"Error codes" are a subset of "result codes" that indicate that something has gone wrong. There are only a few non-error result codes: SQLITE_OK, SQLITE_ROW, and SQLITE_DONE. The term "error code" means any result code other than these three.

Result codes are signed bit integers. The least significant 8 bits of the result code define a broad category and are called the "primary result code". More significant bits provide more detailed information about the error and are called the "extended result code"

Note that the primary result code is always a part of the extended result code. Given a full bit extended result code, the application can always find the corresponding primary result code merely by extracting the least significant 8 bits of the extended result code.

All extended result codes are also error codes. Hence the terms "extended result code" and "extended error code" are interchangeable.

For historic compatibility, the C-language interfaces return primary result codes by default. The extended result code for the most recent error can be retrieved using the sqlite3_extended_errcode() interface. The sqlite3_extended_result_codes() interface can be used to put a database connection into a mode where it returns the extended result codes instead of the primary result codes.

All result codes are integers. Symbolic names for all result codes are created using "#define" macros in the sqlite3.h header file. There are separate sections in the sqlite3.h header file for the result code definitions and the extended result code definitions.

Primary result code symbolic names are of the form "SQLITE_XXXXXX" where XXXXXX is a sequence of uppercase alphabetic characters. Extended result code names are of the form "SQLITE_XXXXXX_YYYYYYY" where the XXXXXX part is the corresponding primary result code and the YYYYYYY is an extension that further classifies the result code.

The names and numeric values for existing result codes are fixed and unchanging. However, new result codes, and especially new extended result codes, might appear in future releases of SQLite.

The 31 result codes are defined in sqlite3.h and are listed in alphabetical order below:

The 74 extended result codes are defined in sqlite3.h and are listed in alphabetical order below:

The meanings for all result code values are shown below, in numeric order.

(0) SQLITE_OK

The SQLITE_OK result code means that the operation was successful and that there were no errors. Most other result codes indicate an error.

(1) SQLITE_ERROR

The SQLITE_ERROR result code is a generic error code that is used when no other more specific error code is available.

(2) SQLITE_INTERNAL

The SQLITE_INTERNAL result code indicates an internal malfunction. In a working version of SQLite, an application should never see this result code. If application does encounter this result code, it shows that there is a bug in the database engine.

SQLite does not currently generate this result code. However, application-defined SQL functions or virtual tables, or VFSes, or other extensions might cause this result code to be returned.

(3) SQLITE_PERM

The SQLITE_PERM result code indicates that the requested access mode for a newly created database could not be provided.

(4) SQLITE_ABORT

The SQLITE_ABORT result code indicates that an operation was aborted prior to completion, usually be application request. See also: SQLITE_INTERRUPT.

If the callback function to sqlite3_exec() returns non-zero, then sqlite3_exec() will return SQLITE_ABORT.

If a ROLLBACK operation occurs on the same database connection as a pending read or write, then the pending read or write may fail with an SQLITE_ABORT or SQLITE_ABORT_ROLLBACK error.

In addition to being a result code, the SQLITE_ABORT value is also used as a conflict resolution mode returned from the sqlite3_vtab_on_conflict() interface.

(5) SQLITE_BUSY

The SQLITE_BUSY result code indicates that the database file could not be written (or in some cases read) because of concurrent activity by some other database connection, usually a database connection in a separate process.

For example, if process A is in the middle of a large write transaction and at the same time process B attempts to start a new write transaction, process B will get back an SQLITE_BUSY result because SQLite only supports one writer at a time. Process B will need to wait for process A to finish its transaction before starting a new transaction. The sqlite3_busy_timeout() and sqlite3_busy_handler() interfaces and the busy_timeout pragma are available to process B to help it deal with SQLITE_BUSY errors.

An SQLITE_BUSY error can occur at any point in a transaction: when the transaction is first started, during any write or update operations, or when the transaction commits. To avoid encountering SQLITE_BUSY errors in the middle of a transaction, the application can use BEGIN IMMEDIATE instead of just BEGIN to start a transaction. The BEGIN IMMEDIATE command might itself return SQLITE_BUSY, but if it succeeds, then SQLite guarantees that no subsequent operations on the same database through the next COMMIT will return SQLITE_BUSY.

See also: SQLITE_BUSY_RECOVERY and SQLITE_BUSY_SNAPSHOT.

The SQLITE_BUSY result code differs from SQLITE_LOCKED in that SQLITE_BUSY indicates a conflict with a separate database connection, probably in a separate process, whereas SQLITE_LOCKED indicates a conflict within the same database connection (or sometimes a database connection with a shared cache).

(6) SQLITE_LOCKED

The SQLITE_LOCKED result code indicates that a write operation could not continue because of a conflict within the same database connection or a conflict with a different database connection that uses a shared cache.

For example, a DROP TABLE statement cannot be run while another thread is reading from that table on the same database connection because dropping the table would delete the table out from under the concurrent reader.

The SQLITE_LOCKED result code differs from SQLITE_BUSY in that SQLITE_LOCKED indicates a conflict on the same database connection (or on a connection with a shared cache) whereas SQLITE_BUSY indicates a conflict with a different database connection, probably in a different process.

(7) SQLITE_NOMEM

The SQLITE_NOMEM result code indicates that SQLite was unable to allocate all the memory it needed to complete the operation. In other words, an internal call to sqlite3_malloc() or sqlite3_realloc() has failed in a case where the memory being allocated was required in order to continue the operation.

(8) SQLITE_READONLY

The SQLITE_READONLY result code is returned when an attempt is made to alter some data for which the current database connection does not have write permission.

(9) SQLITE_INTERRUPT

The SQLITE_INTERRUPT result code indicates that an operation was interrupted by the sqlite3_interrupt() interface. See also: SQLITE_ABORT

(10) SQLITE_IOERR

The SQLITE_IOERR result code says that the operation could not finish because the operating system reported an I/O error.

A full disk drive will normally give an SQLITE_FULL error rather than an SQLITE_IOERR error.

There are many different extended result codes for I/O errors that identify the specific I/O operation that failed.

(11) SQLITE_CORRUPT

The SQLITE_CORRUPT result code indicates that the database file has been corrupted. See the How To Corrupt Your Database Files for further discussion on how corruption can occur.

(12) SQLITE_NOTFOUND

The SQLITE_NOTFOUND result code is exposed in three ways:

  1. SQLITE_NOTFOUND can be returned by the sqlite3_file_control() interface to indicate that the file control opcode passed as the third argument was not recognized by the underlying VFS.

  2. SQLITE_NOTFOUND can also be returned by the xSetSystemCall() method of an sqlite3_vfs object.

  3. SQLITE_NOTFOUND an be returned by sqlite3_vtab_rhs_value() to indicate that the right-hand operand of a constraint is not available to the xBestIndex method that made the call.

The SQLITE_NOTFOUND result code is also used internally by the SQLite implementation, but those internal uses are not exposed to the application.

(13) SQLITE_FULL

The SQLITE_FULL result code indicates that a write could not complete because the disk is full. Note that this error can occur when trying to write information into the main database file, or it can also occur when writing into temporary disk files.

Sometimes applications encounter this error even though there is an abundance of primary disk space because the error occurs when writing into temporary disk files on a system where temporary files are stored on a separate partition with much less space that the primary disk.

(14) SQLITE_CANTOPEN

The SQLITE_CANTOPEN result code indicates that SQLite was unable to open a file. The file in question might be a primary database file or one of several temporary disk files.

(15) SQLITE_PROTOCOL

The SQLITE_PROTOCOL result code indicates a problem with the file locking protocol used by SQLite. The SQLITE_PROTOCOL error is currently only returned when using WAL mode and attempting to start a new transaction. There is a race condition that can occur when two separate database connections both try to start a transaction at the same time in WAL mode. The loser of the race backs off and tries again, after a brief delay. If the same connection loses the locking race dozens of times over a span of multiple seconds, it will eventually give up and return SQLITE_PROTOCOL. The SQLITE_PROTOCOL error should appear in practice very, very rarely, and only when there are many separate processes all competing intensely to write to the same database.

(16) SQLITE_EMPTY

The SQLITE_EMPTY result code is not currently used.

(17) SQLITE_SCHEMA

The SQLITE_SCHEMA result code indicates that the database schema has changed. This result code can be returned from sqlite3_step() for a prepared statement that was generated using sqlite3_prepare() or sqlite3_prepare16(). If the database schema was changed by some other process in between the time that the statement was prepared and the time the statement was run, this error can result.

If a prepared statement is generated from sqlite3_prepare_v2() then the statement is automatically re-prepared if the schema changes, up to SQLITE_MAX_SCHEMA_RETRY times (default: 50). The sqlite3_step() interface will only return SQLITE_SCHEMA back to the application if the failure persists after these many retries.

(18) SQLITE_TOOBIG

The SQLITE_TOOBIG error code indicates that a string or BLOB was too large. The default maximum length of a string or BLOB in SQLite is 1,,, bytes. This maximum length can be changed at compile-time using the SQLITE_MAX_LENGTH compile-time option, or at run-time using the sqlite3_limit(db,SQLITE_LIMIT_LENGTH,) interface. The SQLITE_TOOBIG error results when SQLite encounters a string or BLOB that exceeds the compile-time or run-time limit.

The SQLITE_TOOBIG error code can also result when an oversized SQL statement is passed into one of the sqlite3_prepare_v2() interfaces. The maximum length of an SQL statement defaults to a much smaller value of 1,,, bytes. The maximum SQL statement length can be set at compile-time using SQLITE_MAX_SQL_LENGTH or at run-time using sqlite3_limit(db,SQLITE_LIMIT_SQL_LENGTH,).

(19) SQLITE_CONSTRAINT

The SQLITE_CONSTRAINT error code means that an SQL constraint violation occurred while trying to process an SQL statement. Additional information about the failed constraint can be found by consulting the accompanying error message (returned via sqlite3_errmsg() or sqlite3_errmsg16()) or by looking at the extended error code.

The SQLITE_CONSTRAINT code can also be used as the return value from the xBestIndex() method of a virtual table implementation. When xBestIndex() returns SQLITE_CONSTRAINT, that indicates that the particular combination of inputs submitted to xBestIndex() cannot result in a usable query plan and should not be given further consideration.

(20) SQLITE_MISMATCH

The SQLITE_MISMATCH error code indicates a datatype mismatch.

SQLite is normally very forgiving about mismatches between the type of a value and the declared type of the container in which that value is to be stored. For example, SQLite allows the application to store a large BLOB in a column with a declared type of BOOLEAN. But in a few cases, SQLite is strict about types. The SQLITE_MISMATCH error is returned in those few cases when the types do not match.

The rowid of a table must be an integer. Attempt to set the rowid to anything other than an integer (or a NULL which will be automatically converted into the next available integer rowid) results in an SQLITE_MISMATCH error.

(21) SQLITE_MISUSE

The SQLITE_MISUSE return code might be returned if the application uses any SQLite interface in a way that is undefined or unsupported. For example, using a prepared statement after that prepared statement has been finalized might result in an SQLITE_MISUSE error.

SQLite tries to detect misuse and report the misuse using this result code. However, there is no guarantee that the detection of misuse will be successful. Misuse detection is probabilistic. Applications should never depend on an SQLITE_MISUSE return value.

If SQLite ever returns SQLITE_MISUSE from any interface, that means that the application is incorrectly coded and needs to be fixed. Do not ship an application that sometimes returns SQLITE_MISUSE from a standard SQLite interface because that application contains potentially serious bugs.

(22) SQLITE_NOLFS

The SQLITE_NOLFS error can be returned on systems that do not support large files when the database grows to be larger than what the filesystem can handle. "NOLFS" stands for "NO Large File Support".

(23) SQLITE_AUTH

The SQLITE_AUTH error is returned when the authorizer callback indicates that an SQL statement being prepared is not authorized.

(24) SQLITE_FORMAT

The SQLITE_FORMAT error code is not currently used by SQLite.

(25) SQLITE_RANGE

The SQLITE_RANGE error indices that the parameter number argument to one of the sqlite3_bind routines or the column number in one of the sqlite3_column routines is out of range.

(26) SQLITE_NOTADB

When attempting to open a file, the SQLITE_NOTADB error indicates that the file being opened does not appear to be an SQLite database file.

(27) SQLITE_NOTICE

The SQLITE_NOTICE result code is not returned by any C/C++ interface. However, SQLITE_NOTICE (or rather one of its extended error codes) is sometimes used as the first argument in an sqlite3_log() callback to indicate that an unusual operation is taking place.

(28) SQLITE_WARNING

The SQLITE_WARNING result code is not returned by any C/C++ interface. However, SQLITE_WARNING (or rather one of its extended error codes) is sometimes used as the first argument in an sqlite3_log() callback to indicate that an unusual and possibly ill-advised operation is taking place.

() SQLITE_ROW

The SQLITE_ROW result code returned by sqlite3_step() indicates that another row of output is available.

() SQLITE_DONE

The SQLITE_DONE result code indicates that an operation has completed. The SQLITE_DONE result code is most commonly seen as a return value from sqlite3_step() indicating that the SQL statement has run to completion. But SQLITE_DONE can also be returned by other multi-step interfaces such as sqlite3_backup_step().

() SQLITE_OK_LOAD_PERMANENTLY

The sqlite3_load_extension() interface loads an extension into a single database connection. The default behavior is for that extension to be automatically unloaded when the database connection closes. However, if the extension entry point returns SQLITE_OK_LOAD_PERMANENTLY instead of SQLITE_OK, then the extension remains loaded into the process address space after the database connection closes. In other words, the xDlClose methods of the sqlite3_vfs object is not called for the extension when the database connection closes.

The SQLITE_OK_LOAD_PERMANENTLY return code is useful to loadable extensions that register new VFSes, for example.

() SQLITE_ERROR_MISSING_COLLSEQ

The SQLITE_ERROR_MISSING_COLLSEQ result code means that an SQL statement could not be prepared because a collating sequence named in that SQL statement could not be located.

Sometimes when this error code is encountered, the sqlite3_prepare_v2() routine will convert the error into SQLITE_ERROR_RETRY and try again to prepare the SQL statement using a different query plan that does not require the use of the unknown collating sequence.

() SQLITE_BUSY_RECOVERY

The SQLITE_BUSY_RECOVERY error code is an extended error code for SQLITE_BUSY that indicates that an operation could not continue because another process is busy recovering a WAL mode database file following a crash. The SQLITE_BUSY_RECOVERY error code only occurs on WAL mode databases.

() SQLITE_LOCKED_SHAREDCACHE

The SQLITE_LOCKED_SHAREDCACHE result code indicates that access to an SQLite data record is blocked by another database connection that is using the same record in shared cache mode. When two or more database connections share the same cache and one of the connections is in the middle of modifying a record in that cache, then other connections are blocked from accessing that data while the modifications are on-going in order to prevent the readers from seeing a corrupt or partially completed change.

() SQLITE_READONLY_RECOVERY

The SQLITE_READONLY_RECOVERY error code is an extended error code for SQLITE_READONLY. The SQLITE_READONLY_RECOVERY error code indicates that a WAL mode database cannot be opened because the database file needs to be recovered and recovery requires write access but only read access is available.

() SQLITE_IOERR_READ

The SQLITE_IOERR_READ error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to read from a file on disk. This error might result from a hardware malfunction or because a filesystem came unmounted while the file was open.

() SQLITE_CORRUPT_VTAB

The SQLITE_CORRUPT_VTAB error code is an extended error code for SQLITE_CORRUPT used by virtual tables. A virtual table might return SQLITE_CORRUPT_VTAB to indicate that content in the virtual table is corrupt.

() SQLITE_CANTOPEN_NOTEMPDIR

The SQLITE_CANTOPEN_NOTEMPDIR error code is no longer used.

() SQLITE_CONSTRAINT_CHECK

The SQLITE_CONSTRAINT_CHECK error code is an extended error code for SQLITE_CONSTRAINT indicating that a CHECK constraint failed.

() SQLITE_AUTH_USER

The SQLITE_AUTH_USER error code is an extended error code for SQLITE_AUTH indicating that an operation was attempted on a database for which the logged in user lacks sufficient authorization.

() SQLITE_NOTICE_RECOVER_WAL

The SQLITE_NOTICE_RECOVER_WAL result code is passed to the callback of sqlite3_log() when a WAL mode database file is recovered.

() SQLITE_WARNING_AUTOINDEX

The SQLITE_WARNING_AUTOINDEX result code is passed to the callback of sqlite3_log() whenever automatic indexing is used. This can serve as a warning to application designers that the database might benefit from additional indexes.

() SQLITE_ERROR_RETRY

The SQLITE_ERROR_RETRY is used internally to provoke sqlite3_prepare_v2() (or one of its sibling routines for creating prepared statements) to try again to prepare a statement that failed with an error on the previous attempt.

() SQLITE_ABORT_ROLLBACK

The SQLITE_ABORT_ROLLBACK error code is an extended error code for SQLITE_ABORT indicating that an SQL statement aborted because the transaction that was active when the SQL statement first started was rolled back. Pending write operations always fail with this error when a rollback occurs. A ROLLBACK will cause a pending read operation to fail only if the schema was changed within the transaction being rolled back.

() SQLITE_BUSY_SNAPSHOT

The SQLITE_BUSY_SNAPSHOT error code is an extended error code for SQLITE_BUSY that occurs on WAL mode databases when a database connection tries to promote a read transaction into a write transaction but finds that another database connection has already written to the database and thus invalidated prior reads.

The following scenario illustrates how an SQLITE_BUSY_SNAPSHOT error might arise:

  1. Process A starts a read transaction on the database and does one or more SELECT statement. Process A keeps the transaction open.
  2. Process B updates the database, changing values previous read by process A.
  3. Process A now tries to write to the database. But process A's view of the database content is now obsolete because process B has modified the database file after process A read from it. Hence process A gets an SQLITE_BUSY_SNAPSHOT error.

() SQLITE_LOCKED_VTAB

The SQLITE_LOCKED_VTAB result code is not used by the SQLite core, but it is available for use by extensions. Virtual table implementations can return this result code to indicate that they cannot complete the current operation because of locks held by other threads or processes.

The R-Tree extension returns this result code when an attempt is made to update the R-Tree while another prepared statement is actively reading the R-Tree. The update cannot proceed because any change to an R-Tree might involve reshuffling and rebalancing of nodes, which would disrupt read cursors, causing some rows to be repeated and other rows to be omitted.

() SQLITE_READONLY_CANTLOCK

The SQLITE_READONLY_CANTLOCK error code is an extended error code for SQLITE_READONLY. The SQLITE_READONLY_CANTLOCK error code indicates that SQLite is unable to obtain a read lock on a WAL mode database because the shared-memory file associated with that database is read-only.

() SQLITE_IOERR_SHORT_READ

The SQLITE_IOERR_SHORT_READ error code is an extended error code for SQLITE_IOERR indicating that a read attempt in the VFS layer was unable to obtain as many bytes as was requested. This might be due to a truncated file.

() SQLITE_CORRUPT_SEQUENCE

The SQLITE_CORRUPT_SEQUENCE result code means that the schema of the sqlite_sequence table is corrupt. The sqlite_sequence table is used to help implement the AUTOINCREMENT feature. The sqlite_sequence table should have the following format:

CREATE TABLE sqlite_sequence(name,seq);

If SQLite discovers that the sqlite_sequence table has any other format, it returns the SQLITE_CORRUPT_SEQUENCE error.

() SQLITE_CANTOPEN_ISDIR

The SQLITE_CANTOPEN_ISDIR error code is an extended error code for SQLITE_CANTOPEN indicating that a file open operation failed because the file is really a directory.

() SQLITE_CONSTRAINT_COMMITHOOK

The SQLITE_CONSTRAINT_COMMITHOOK error code is an extended error code for SQLITE_CONSTRAINT indicating that a commit hook callback returned non-zero that thus caused the SQL statement to be rolled back.

() SQLITE_NOTICE_RECOVER_ROLLBACK

The SQLITE_NOTICE_RECOVER_ROLLBACK result code is passed to the callback of sqlite3_log() when a hot journal is rolled back.

() SQLITE_ERROR_SNAPSHOT

The SQLITE_ERROR_SNAPSHOT result code might be returned when attempting to start a read transaction on an historical version of the database by using the sqlite3_snapshot_open() interface. If the historical snapshot is no longer available, then the read transaction will fail with the SQLITE_ERROR_SNAPSHOT. This error code is only possible if SQLite is compiled with -DSQLITE_ENABLE_SNAPSHOT.

() SQLITE_BUSY_TIMEOUT

The SQLITE_BUSY_TIMEOUT error code indicates that a blocking Posix advisory file lock request in the VFS layer failed due to a timeout. Blocking Posix advisory locks are only available as a proprietary SQLite extension and even then are only supported if SQLite is compiled with the SQLITE_EANBLE_SETLK_TIMEOUT compile-time option.

() SQLITE_READONLY_ROLLBACK

The SQLITE_READONLY_ROLLBACK error code is an extended error code for SQLITE_READONLY. The SQLITE_READONLY_ROLLBACK error code indicates that a database cannot be opened because it has a hot journal that needs to be rolled back but cannot because the database is readonly.

() SQLITE_IOERR_WRITE

The SQLITE_IOERR_WRITE error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to write into a file on disk. This error might result from a hardware malfunction or because a filesystem came unmounted while the file was open. This error should not occur if the filesystem is full as there is a separate error code (SQLITE_FULL) for that purpose.

() SQLITE_CORRUPT_INDEX

The SQLITE_CORRUPT_INDEX result code means that SQLite detected an entry is or was missing from an index. This is a special case of the SQLITE_CORRUPT error code that suggests that the problem might be resolved by running the REINDEX command, assuming no other problems exist elsewhere in the database file.

() SQLITE_CANTOPEN_FULLPATH

The SQLITE_CANTOPEN_FULLPATH error code is an extended error code for SQLITE_CANTOPEN indicating that a file open operation failed because the operating system was unable to convert the filename into a full pathname.

() SQLITE_CONSTRAINT_FOREIGNKEY

The SQLITE_CONSTRAINT_FOREIGNKEY error code is an extended error code for SQLITE_CONSTRAINT indicating that a foreign key constraint failed.

() SQLITE_READONLY_DBMOVED

The SQLITE_READONLY_DBMOVED error code is an extended error code for SQLITE_READONLY. The SQLITE_READONLY_DBMOVED error code indicates that a database cannot be modified because the database file has been moved since it was opened, and so any attempt to modify the database might result in database corruption if the processes crashes because the rollback journal would not be correctly named.

() SQLITE_IOERR_FSYNC

The SQLITE_IOERR_FSYNC error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to flush previously written content out of OS and/or disk-control buffers and into persistent storage. In other words, this code indicates a problem with the fsync() system call in unix or the FlushFileBuffers() system call in windows.

() SQLITE_CANTOPEN_CONVPATH

The SQLITE_CANTOPEN_CONVPATH error code is an extended error code for SQLITE_CANTOPEN used only by Cygwin VFS and indicating that the cygwin_conv_path() system call failed while trying to open a file. See also: SQLITE_IOERR_CONVPATH

() SQLITE_CONSTRAINT_FUNCTION

The SQLITE_CONSTRAINT_FUNCTION error code is not currently used by the SQLite core. However, this error code is available for use by extension functions.

() SQLITE_READONLY_CANTINIT

The SQLITE_READONLY_CANTINIT result code originates in the xShmMap method of a VFS to indicate that the shared memory region used by WAL mode exists buts its content is unreliable and unusable by the current process since the current process does not have write permission on the shared memory region. (The shared memory region for WAL mode is normally a file with a "-wal" suffix that is mmapped into the process space. If the current process does not have write permission on that file, then it cannot write into shared memory.)

Higher level logic within SQLite will normally intercept the error code and create a temporary in-memory shared memory region so that the current process can at least read the content of the database. This result code should not reach the application interface layer.

() SQLITE_IOERR_DIR_FSYNC

The SQLITE_IOERR_DIR_FSYNC error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to invoke fsync() on a directory. The unix VFS attempts to fsync() directories after creating or deleting certain files to ensure that those files will still appear in the filesystem following a power loss or system crash. This error code indicates a problem attempting to perform that fsync().

() SQLITE_CANTOPEN_DIRTYWAL

The SQLITE_CANTOPEN_DIRTYWAL result code is not used at this time.

() SQLITE_CONSTRAINT_NOTNULL

The SQLITE_CONSTRAINT_NOTNULL error code is an extended error code for SQLITE_CONSTRAINT indicating that a NOT NULL constraint failed.

() SQLITE_READONLY_DIRECTORY

The SQLITE_READONLY_DIRECTORY result code indicates that the database is read-only because process does not have permission to create a journal file in the same directory as the database and the creation of a journal file is a prerequisite for writing.

() SQLITE_IOERR_TRUNCATE

The SQLITE_IOERR_TRUNCATE error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to truncate a file to a smaller size.

() SQLITE_CANTOPEN_SYMLINK

The SQLITE_CANTOPEN_SYMLINK result code is returned by the sqlite3_open() interface and its siblings when the SQLITE_OPEN_NOFOLLOW flag is used and the database file is a symbolic link.

() SQLITE_CONSTRAINT_PRIMARYKEY

The SQLITE_CONSTRAINT_PRIMARYKEY error code is an extended error code for SQLITE_CONSTRAINT indicating that a PRIMARY KEY constraint failed.

() SQLITE_IOERR_FSTAT

The SQLITE_IOERR_FSTAT error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to invoke fstat() (or the equivalent) on a file in order to determine information such as the file size or access permissions.

() SQLITE_CONSTRAINT_TRIGGER

The SQLITE_CONSTRAINT_TRIGGER error code is an extended error code for SQLITE_CONSTRAINT indicating that a RAISE function within a trigger fired, causing the SQL statement to abort.

() SQLITE_IOERR_UNLOCK

The SQLITE_IOERR_UNLOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error within xUnlock method on the sqlite3_io_methods object.

() SQLITE_CONSTRAINT_UNIQUE

The SQLITE_CONSTRAINT_UNIQUE error code is an extended error code for SQLITE_CONSTRAINT indicating that a UNIQUE constraint failed.

() SQLITE_IOERR_RDLOCK

The SQLITE_IOERR_UNLOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error within xLock method on the sqlite3_io_methods object while trying to obtain a read lock.

() SQLITE_CONSTRAINT_VTAB

The SQLITE_CONSTRAINT_VTAB error code is not currently used by the SQLite core. However, this error code is available for use by application-defined virtual tables.

() SQLITE_IOERR_DELETE

The SQLITE_IOERR_UNLOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error within xDelete method on the sqlite3_vfs object.

() SQLITE_CONSTRAINT_ROWID

The SQLITE_CONSTRAINT_ROWID error code is an extended error code for SQLITE_CONSTRAINT indicating that a rowid is not unique.

() SQLITE_IOERR_BLOCKED

The SQLITE_IOERR_BLOCKED error code is no longer used.

() SQLITE_CONSTRAINT_PINNED

The SQLITE_CONSTRAINT_PINNED error code is an extended error code for SQLITE_CONSTRAINT indicating that an UPDATE trigger attempted do delete the row that was being updated in the middle of the update.

() SQLITE_IOERR_NOMEM

The SQLITE_IOERR_NOMEM error code is sometimes returned by the VFS layer to indicate that an operation could not be completed due to the inability to allocate sufficient memory. This error code is normally converted into SQLITE_NOMEM by the higher layers of SQLite before being returned to the application.

() SQLITE_CONSTRAINT_DATATYPE

The SQLITE_CONSTRAINT_DATATYPE error code is an extended error code for SQLITE_CONSTRAINT indicating that an insert or update attempted to store a value inconsistent with the column's declared type in a table defined as STRICT.

() SQLITE_IOERR_ACCESS

The SQLITE_IOERR_ACCESS error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xAccess method on the sqlite3_vfs object.

() SQLITE_IOERR_CHECKRESERVEDLOCK

The SQLITE_IOERR_CHECKRESERVEDLOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xCheckReservedLock method on the sqlite3_io_methods object.

() SQLITE_IOERR_LOCK

The SQLITE_IOERR_LOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error in the advisory file locking logic. Usually an SQLITE_IOERR_LOCK error indicates a problem obtaining a PENDING lock. However it can also indicate miscellaneous locking errors on some of the specialized VFSes used on Macs.

() SQLITE_IOERR_CLOSE

The SQLITE_IOERR_ACCESS error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xClose method on the sqlite3_io_methods object.

() SQLITE_IOERR_DIR_CLOSE

The SQLITE_IOERR_DIR_CLOSE error code is no longer used.

() SQLITE_IOERR_SHMOPEN

The SQLITE_IOERR_SHMOPEN error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xShmMap method on the sqlite3_io_methods object while trying to open a new shared memory segment.

() SQLITE_IOERR_SHMSIZE

The SQLITE_IOERR_SHMSIZE error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xShmMap method on the sqlite3_io_methods object while trying to enlarge a "shm" file as part of WAL mode transaction processing. This error may indicate that the underlying filesystem volume is out of space.

() SQLITE_IOERR_SHMLOCK

The SQLITE_IOERR_SHMLOCK error code is no longer used.

() SQLITE_IOERR_SHMMAP

The SQLITE_IOERR_SHMMAP error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xShmMap method on the sqlite3_io_methods object while trying to map a shared memory segment into the process address space.

() SQLITE_IOERR_SEEK

The SQLITE_IOERR_SEEK error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xRead or xWrite methods on the sqlite3_io_methods object while trying to seek a file descriptor to the beginning point of the file where the read or write is to occur.

() SQLITE_IOERR_DELETE_NOENT

The SQLITE_IOERR_DELETE_NOENT error code is an extended error code for SQLITE_IOERR indicating that the xDelete method on the sqlite3_vfs object failed because the file being deleted does not exist.

() SQLITE_IOERR_MMAP

The SQLITE_IOERR_MMAP error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xFetch or xUnfetch methods on the sqlite3_io_methods object while trying to map or unmap part of the database file into the process address space.

() SQLITE_IOERR_GETTEMPPATH

The SQLITE_IOERR_GETTEMPPATH error code is an extended error code for SQLITE_IOERR indicating that the VFS is unable to determine a suitable directory in which to place temporary files.

() SQLITE_IOERR_CONVPATH

The SQLITE_IOERR_CONVPATH error code is an extended error code for SQLITE_IOERR used only by Cygwin VFS and indicating that the cygwin_conv_path() system call failed. See also: SQLITE_CANTOPEN_CONVPATH

() SQLITE_IOERR_VNODE

The SQLITE_IOERR_VNODE error code is a code reserved for use by extensions. It is not used by the SQLite core.

() SQLITE_IOERR_AUTH

The SQLITE_IOERR_AUTH error code is a code reserved for use by extensions. It is not used by the SQLite core.

() SQLITE_IOERR_BEGIN_ATOMIC

The SQLITE_IOERR_BEGIN_ATOMIC error code indicates that the underlying operating system reported and error on the SQLITE_FCNTL_BEGIN_ATOMIC_WRITE file-control. This only comes up when SQLITE_ENABLE_ATOMIC_WRITE is enabled and the database is hosted on a filesystem that supports atomic writes.

() SQLITE_IOERR_COMMIT_ATOMIC

The SQLITE_IOERR_COMMIT_ATOMIC error code indicates that the underlying operating system reported and error on the SQLITE_FCNTL_COMMIT_ATOMIC_WRITE file-control. This only comes up when SQLITE_ENABLE_ATOMIC_WRITE is enabled and the database is hosted on a filesystem that supports atomic writes.

() SQLITE_IOERR_ROLLBACK_ATOMIC

The SQLITE_IOERR_ROLLBACK_ATOMIC error code indicates that the underlying operating system reported and error on the SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE file-control. This only comes up when SQLITE_ENABLE_ATOMIC_WRITE is enabled and the database is hosted on a filesystem that supports atomic writes.

() SQLITE_IOERR_DATA

The SQLITE_IOERR_DATA error code is an extended error code for SQLITE_IOERR used only by checksum VFS shim to indicate that the checksum on a page of the database file is incorrect.

() SQLITE_IOERR_CORRUPTFS

The SQLITE_IOERR_CORRUPTFS error code is an extended error code for SQLITE_IOERR used only by a VFS to indicate that a seek or read failure was due to the request not falling within the file's boundary rather than an ordinary device failure. This often indicates a corrupt filesystem.

20 01 error

iOS update and restore errors

Learn how to solve iOS update and restore errors.

Try these steps first

  1. On a Mac with macOS Catalina  or later, make sure your Mac is up to date. If you have a Mac with macOS Mojave or earlier, or a PC, make sure you have the latest version of iTunes.
  2. If your device couldn't be restored and you get a message that "an unknown error occurred [error number]," use these steps. 

If you still see the error, try the steps below.

Choose your error number or message

To learn what to do, choose your error:

  • 1, 2, 3, 4, 6, 9, 10, 11, 12, 13, 14, 16, 17 
  • 20, 21, 23, 26, 27, 28, 29, 34, 35, 36, 37,
    40, 53, 56
  • , , , , , 
  • , , , , , , , 
    –, , ,
  • , , , , 
  • , , , , , , 
  • , , ,

Update the software on your Mac or PC

If you see error 10, your iOS device might have a newer version of iOS than is supported by your computer. You'll need to update the software on your Mac or iTunes on Windows before 20 01 error can update or restore your iOS device.

macOS and later:

  1. Disconnect and then reconnect your iOS device to your computer. You might need to unlock your iOS device before it is recognized by your Mac.
  2. When you see a message that says a software update is required to connect to your iOS device, click Install to download and install the software so your Mac can update or restore your iOS device.

Windows: Update to latest version of iTunes.

If you continue to see error 10, or you don't see a dialog asking you to update the software on your mac, contact Apple Support.

Make sure that your device can communicate with Apple servers

If you see error , your computer is downloading necessary software, 20 01 error. Wait for the download to finish, 20 01 error, then try again.

If you see one of the errors below, your computer might not be able to connect to Apple servers or your iPhone, iPad, or iPod touch:

  • 17,,20 01 error,,
  • "There was a problem downloading the software."
  • "The device isn't eligible for the requested build."

Here's what to check:

  1. Make sure that your computer can communicate with the Apple software-update servers.
  2. Check your third-party security software.

If you see error , your computer is unable to update your device because it's passcode locked and the device wasn't unlocked for the update or restore, 20 01 error. Unlock your device and try again. Learn what to do if you forgot your passcode.

If you still see an error, contact Apple Support.

Cellular Update Failed or Apple Pay Not Available alert

If you see either "Cellular Update Failed" or "Apple Pay requires an Update on this iPhone" alert after an update, learn what to do.

Check your security software

Check your USB connections

If you see error, or , use these steps.

If you see one of the errors below, check your USB connection, USB cable, USB port, 20 01 error, or computer:

Here's what to check, 20 01 error. Try again after each step:

  1. Use the USB cable that came with your device. If you don't have it, try a different Apple USB cable. 
  2. Switch to a different USB port on your computer. Don't plug into your keyboard.
  3. Switch to a USB port on a different computer.
  4. If you still see the error, check for other USB issues, check your third-party security software, then check your hardware.

If you still see an error, contact Apple Support.

Check your hardware

If you see error 53, use these steps.

If you see one of the errors below, you might have a hardware issue:

  • 1, 20 01 error, 3, 11, 12, 20 01 error, 13, 16
  • 20, 21, 23, 20 01 error, 26, 27, 28, 29, 34, 35, 36, 37, 40, 56
  • , 20 01 error,

Here's what to check. Try again after each step:

  1. If iTunes is already open, quit and reopen it.
  2. Check your third-party security software.
  3. Make sure that your USB cable, computer, 20 01 error, and network are reliable. Then try twice more to restore your device.
  4. Check for outdated or modified software. 

If you still see the error, contact Apple Support.

Published 20 01 error

This section lists each TopLink error code. Each error entry contains a description of the error, the probable cause, and the recommended action. Each error code corresponds to an exception class. See "Runtime and Development Exceptions" for more information.

A description shown in the actual exception thrown.

Cause: The most probable cause for the error.

Action: Suggestions for resolving the error.

ATTRIBUTE_AND_MAPPING_WITH_INDIRECTION_ MISMATCH

Cause: <attributeName> is not declared as type but the mapping uses indirection. Mapping is set to use indirection but the related attribute is not defined as type. It is thrown on foreign reference mappings.

Action: If you want to use indirection on the mapping, change the attribute to type. Otherwise, change the mapping associated with the attribute so that it does not use indirection.

ATTRIBUTE_AND_MAPPING_WITHOUT_INDIRECTION_ MISMATCH

Cause: 20 01 error is declared as type but the mapping is not using indirection. Attribute is defined to be of type but terror pack css mapping is not set to use indirection. It is thrown on foreign reference mappings.

Action: If you do not want to use indirection on the mapping, change the attribute to not be of type. Otherwise, change the mapping associated with the attribute to use indirection.

ATTRIBUTE_NAME_NOT_SPECIFIED

Cause: Attribute name is missing or not specified in the mapping definition.

Action: Specify the attribute name in the mapping by calling method .

ATTRIBUTE_TYPE_NOT_VALID

Cause: <attributeName> should be defined as type Vector, or a type that implements Map or Collection if using Java 2. It happens in one to many mapping, many to 20 01 error mapping and collection mapping when mapping is set not to use indirection and attribute type is not declared of type.

Action: Declare the attribute to be of type.

CLASS_INDICATOR_FIELD_NOT_FOUND

Cause: The class indicator field has not been defined, however the descriptor has been set to use inheritance, 20 01 error. When using inheritance, a class indicator field or class extraction method must be set. The class indicator field is used to create the right type of domain object

Action: Either a class indicator field or class extraction method must be set.

DIRECT_FIELD_NAME_NOT_SET

Cause: The direct field name from the target table is not set in the direct collection mapping. The field values form the collection in this mapping.

Action: Specify the direct field name by calling method .

FIELD_NAME_NOT_SET_IN_MAPPING

Cause: The field name is not set in the mapping. It is thrown from direct to field mapping, array mapping and structure mapping.

Action: Specify the field name by calling 20 01 error .

FOREIGN_KEYS_DEFINED_INCORRECTLY

Cause: One to one mapping foreign key defined incorrectly. Multiple foreign key fields were set for one to one mapping by calling method .

Action: Use method to add multiple foreign key fields.

IDENTITY_MAP_NOT_SPECIFIED

Cause: The descriptor must use an identity map to use the Check cache does exist option. Descriptor has been set to not use identity map but the existence checking is set to be done on identity map.

Action: Either use identity map or set the existence checking to some other option.

ILLEGAL_ACCESS_WHILE_GETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: <attributeName> instance 20 01 error in object <objectName> is inaccessible, 20 01 error. Instance variable in the domain object is not accessible. This exception is thrown when TopLink tries to access the instance variable using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_CLONING

Cause: Problem in cloning the object <domainObject>. Clone method <methodName> is not accessible, 20 01 error. The method name specified using or the method to create clone on the domain object is not accessible by TopLink using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_CONSTRUCTOR_INSTANTIATION

Cause: The domain class does not define a public default constructor, which is needed by TopLink to create new instances of the domain class.

Action: Define one or use different instantiation policy.

ILLEGAL_ACCESS_WHILE_EVENT_EXECUTION

Cause: The descriptor callback method <eventMethodName> with as argument, is not accessible. This exception is thrown when TopLink tries to access the event method using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Trying to invoke inaccessible <methodName> on the object <objectName>, 20 01 error. The underlying get accessor method to access an attribute in the domain object is not accessible. This exception is thrown when TopLink tries to access an attribute through method using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INSTANTIATING_METHOD_ BASED_PROXY

Cause: The method used by the Transformation mapping using a is illegal. This exception is thrown when TopLink tries to access the method using Java reflection, 20 01 error. The problem is caused when method 20 01 error value holder is getting instantiated.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INVOKING_ATTRIBUTE_METHOD

Cause: On transformation mapping the underlying attribute method used to retrieve value from the database row while reading transformation mapped attribute is not accessible.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INVOKING_FIELD_TO_METHOD

Cause: On transformation mapping the method <methodName> used to retrieve value from the object 20 01 error writing transformation mapped attribute is not accessible. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception error code 0x80043001 check the Java manuals.

ILLEGAL_ACCESS_WHILE_INVOKING_ROW_EXTRACTION_ METHOD

Cause: Problem in extracting class from <row>; Static method <method> with <databaseRow> as argument, 20 01 error, is not accessible. The method to extract class from row on the domain object is not accessible. The error is 3g iphone error 1013 Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_METHOD_INSTANTIATION

Cause: Problem in creating new instance; the method <methodName> to create instances on the domain class is not accessible. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_OBSOLETE_EVENT_EXECUTION

Cause: The descriptor callback method <eventMethodName> with Session as argument, is inaccessible. This exception is thrown when TopLink tries to access the event method using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: The <attributeName> instance variable in the object <objectName> is not accessible through Java reflection. The error is thrown by Java and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_SETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Trying to invoke inaccessible method <setMethodName> error taskfailed event exception, aborting the object with parameter <parameter>. The motorola v8 critical error set accessor method is not accessible through Java reflection. The error is thrown by Java and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_GETTING_VALUE_ THRU_INSTANCE_VARIABLE_ACCESSOR

Cause: Trying to get a value for an instance variable <attributeName> 20 01 error type <typeName> from the object. The specified object is not an instance of the class or interface declaring the underlying field. An object is accessed to get the value of an instance variable that does not exist.

Action: Mount error12 cannot allocate memory the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: 20 01 error Trying to invoke method <methodName> on the object <objectName>. The get accessor method declaration on the domain object differs from the one that is defined. The number of actual and formal parameters differ, or an unwrapping conversion has failed.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_INSTANTIATING_METHOD_ BASED_PROXY

Cause: The method used by the method-based proxy in a Transformation mapping is getting illegal arguments when the value holder is getting instantiated. This exception is thrown 20 01 error TopLink tries to access the method using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_INVOKING_ATTRIBUTE_ METHOD

Cause: The number of actual and formal parameters differ, or an unwrapping conversion has failed. On transformation mapping the method used to retrieve value from the database row while reading transformation mapped attribute is getting illegal argument.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_INVOKING_FIELD_TO_ METHOD

Cause: The number of actual and formal parameters differ for method <methodName> or an unwrapping conversion has failed. On transformation mapping the method used to retrieve value from the object while writing transformation mapped attribute is getting illegal argument. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_OBSOLETE_EVENT_ EXECUTION

Cause: he number of actual and formal parameters for the descriptor callback method <eventMethodName> differs, or an unwrapping conversion has failed. The callback event method is invoked with illegal argument. This exception is thrown when TopLink tries to invoke the event method using Java reflection. The error is a purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: Illegal value is being assigned to the attribute instance variable. Trying to set a value <value> for an instance variable <attributeName> of type <typeName> in the object. The specified object is not an instance of the class or interface declaring the underlying field, or an unwrapping conversion has failed.

TopLink does the assignment of value by using Java reflection. Java throws the error and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_SETTING_VALUE_THRU _METHOD_ACCESSOR

Cause: Illegal argument is being passed to the attribute's set accessor method. Trying to invoke method <setMethodName> on the object. The number of actual and formal parameters differs, or an unwrapping conversion has failed. Java throws the error and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

INSTANTIATION_WHILE_CONSTRUCTOR_INSTANTIATION

Cause: he class does not define a public default constructor, or the constructor raised an exception. The default constructor for the domain object is invoked to create new instance of the object while building new domain objects. If this Class represents an abstract class, 20 01 error, an interface, an array class, a primitive type, or void; or if the instantiation fails for some other reason. Java throws the error and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

INVALID_DATA_MODIFICATION_EVENT

Cause: This is an exception that an application should never encounter, 20 01 error. The exception can occur at the time of developing TopLink. In cases where one writes new mapping it is possible to get this exception. In 20 01 error collection mapping and wow error filter to many mapping the target table and relational table are populated at the end of the commit process and if data modification event is sent to any other mapping then this exception is thrown.

Action: Contact Technical Support.

INVALID_DATA_MODIFICATION_EVENT_CODE

Cause: This is an exception that an application should never encounter. The exception can occur at the time of developing TopLink. In cases where one writes new mapping it is possible to get this exception. In direct collection mapping and many to many mapping the target table and relational table are populated at the end of the commit process and if data modification event is sent to these two mappings with wrong event code then this exception is thrown.

Action: Contact Technical Support.

INVALID_DESCRIPTOR_EVENT_CODE

Cause: This is an exception that an application should never encounter, 20 01 error. The exception can occur at the time of developing TopLink. The exception means that descriptor event manager does not support the event code passed in the event.

Action: Contact Technical Support.

INVALID_IDENTITY_MAP

Cause: Identity map constructor failed because an invalid identity map was specified. The identity map class given in the descriptor cannot be instantiated. The exception is Java exception thrown by Java reflection when TopLink is instantiating the identity map class. TopLink only wraps the Java exception.

Action: Inspect the internal exception and check the Java manuals.

JAVA_CLASS_NOT_SPECIFIED

Cause: The descriptor does not define a Java class. The Java class is not specified in the descriptor.

Action: Specify the Java Class

DESCRIPTOR_FOR_INTERFACE_IS_MISSING

Cause: A descriptor for the referenced interface is not added to the session.

Action: Add that descriptor to the session.

MAPPING_FOR_SEQUENCE_NUMBER_FIELD

Cause: A non-read-only mapping is not defined for the sequence number field. A mapping is required so that TopLink can put and extract values for the primary key.

Action: Define a mapping.

MISSING_CLASS_FOR_INDICATOR_FIELD_VALUE

Cause: Missing class for indicator field value <classFieldValue> of type <type>. There was no class entry found in the inheritance policy for the indicator field value read from the database. Probably the method was not called for the field value. The class and typeValue is stored in the hashtable and later on the class is extracted from the hashtable by passing as a key. Remember Integer(1) is not equal to Float(1), this is another major reason for this problem when the type of typeValue is different.

Action: Check descriptor.

MISSING_CLASS_INDICATOR_FIELD

Cause: The class indicator field is missing from the database row <row> that was read from the database. This is done in inheritance model where after reading rows from the database, child domain objects are to be constructed depending upon the type indicator values.

Action: 20 01 error the printed row to make sure the spelling is correct.

MISSING_MAPPING_FOR_FIELD

Cause: Missing mapping for field <field>; a mapping for the field is not specified.

Action: Define a mapping for the field.

NO_MAPPING_FOR_PRIMARY_KEY

Cause: A mapping for the primary key is not specified. There should be one non-read-only mapping defined for the primary key field.

Action: efine a mapping for the primary key.

MULTIPLE_TABLE_PRIMARY_KEY_NOT_SPECIFIED

Cause: The multiple table primary key mapping must be specified when a custom multiple table join is used. If multiple tables are specified in the descriptor and the join expression is customized then the primary keys for all the tables must be specified. If the primary keys are not specified then the exception is caused.

Action: Call method on the descriptor to set the primary keys.

MULTIPLE_WRITE_MAPPINGS_FOR_FIELD

Cause: There are multiple writable mappings for the field <fieldName> in the descriptor. Exactly one must be defined writable. The others must be specified as read-only. When multiple write mappings are defined for the field, 20 01 error, TopLink cannot decide on which mapping to pick up for writing the value of the field in the database row hence the exception is thrown during the validation process of descriptors. The most common site for this problem is that sometimes the field has direct-to-field mapping and also one-to-one mapping. In this case if direct-to-field mapping has to be kept then one-to-one mapping should either be read-only or it should be target foreign key reference.

Action: Make one of those mappings read only.

NO_ATTRIBUTE_TRANSFORMATION_METHOD

Cause: The attribute transformation method name in the transformation mapping is not specified. This method is invoked internally by TopLink to retrieve value to store in the domain object.

Action: Define a method and set the method name on the mapping by calling method .

NO_FIELD_NAME_FOR_MAPPING

Cause: No field name is specified in direct-to-field mapping.

Action: Set the field by calling .

NO_FOREIGN_KEYS_ARE_SPECIFIED

Cause: Neither the selection criteria nor the foreign keys were specified on one-to-one mapping. If the selection criterion is not specified then TopLink tries to build one from the foreign keys specified in the mapping.

Action: Specify the fields.

NO_REFERENCE_KEY_IS_SPECIFIED

Cause: No query key named: <queryKey> found in: <descriptor>; no reference key from the target table is specified on direct collection mapping.

Action: Specify the fields by calling 20 01 error .

NO_RELATION_TABLE

Cause: The relation table name is not set in this many-to-many mapping.

Action: Set relation table name by calling method .

NO_SOURCE_RELATION_KEYS_SPECIFIED

Cause: There are no source relation keys specified in this many-to-many mapping.

Action: Add source relation keys to the mapping.

NO_SUCH_METHOD_ON_FIND_OBSOLETE_METHOD

Cause: The descriptor callback method <selector> on the domain class was not found. It must take a or a as its argument. TopLink tries to invoke the method using Java reflection. It is a Java exception and TopLink is only wrapping the main exception.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_ON_INITIALIZING_ ATTRIBUTE_METHOD

Cause: The method <attributeMethodName> with parameters <databaseRow> or <databaseRow, session> is not found. TopLink wraps the Java reflection exception that is caused when the method is being created from the method name. This method is set by calling.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_CONSTRUCTOR_ INSTANTIATION

Cause: Inaccessible constructor. TopLink wraps the Java reflection exception that is caused when it is creating a new instance of the domain.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_CONVERTING_TO_METHOD

Cause: Method <methodName> not found with parameters () 20 01 error (Session). TopLink wraps the Java reflection exception that is caused when it is creating a Method 20 01 error from the method names in transformation 20 01 error.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_FIELD_WHILE_INITIALIZING_ATTRIBUTES_ IN_INSTANCE_VARIABLE_ACCESSOR

Cause: The instance variable <attributeName> is not defined in the domain class or it is not accessible. TopLink wraps the Java reflection exception that is caused when it is creating a Field type from the attribute name.

Action: Inspect the internal 20 01 error and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_ ATTRIBUTES_IN_METHOD_ACCESSOR

Cause: The accessor method <setMethodName> or <getMethodName> is not defined for the attribute in the domain class <javaClassName>, or it is not accessible. TopLink wraps the Java reflection exception that is caused when it is creating a Method type from the method name.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_ CLASS_EXTRACTION_METHOD

Cause: The static class extraction method <methodName> with <databaseRow> as argument does not exist, or is not accessible. Java reflection exception wrapped in TopLink exception is thrown when class extraction method is being created from the method name in inheritance policy.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_COPY_POLICY

Cause: The clone method <methodName> with no arguments does not exist, 20 01 error, or is not accessible. Java reflection exception wrapped in TopLink exception is thrown when a method to create clones is being created from the method name in copy policy.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_ INSTANTIATION_POLICY

Cause: The instance creation method <methodName> with no arguments does not exist, or is not accessible. Java reflection exception wrapped in TopLink exception is thrown when a method to create new instances is being created from the method name in instantiation policy.

Action: Inspect the internal exception and check the Java manuals.

NO_TARGET_FOREIGN_KEYS_SPECIFIED

Cause: The foreign keys in the target table are not specified in one-to-many mappings. These fields are not required if a selection criterion is given in the mapping but otherwise they must be specified.

Action: Set target foreign keys or selection criteria.

NO_TARGET_RELATION_KEYS_SPECIFIED

Cause: There are no target relation keys specified in many-to-many mappings.

Action: Call method to set the fields.

NOT_DESERIALIZABLE

Cause: The object cannot be de-serialized from the byte array read from the database. The exception is thrown when serialized object mapping is converting byte array into object.

Action: Inspect the internal exception and check the Java manuals.

NOT_SERIALIZABLE

Cause: The object cannot be serialized into byte array, 20 01 error. The exception is thrown when serialized object mapping is object into byte array.

Action: Inspect the internal exception and check the Java manuals.

NULL_FOR_NON_NULL_AGGREGATE

Cause: Value of aggregate in the source object <object> is null. Null values not allowed for aggregate mappings unless allow null is specified in aggregate mapping.

Action: Call method ) on the mapping.

NULL_POINTER_WHILE_GETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: An object is accessed to get the value of an instance variable through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: The get accessor method is invoked to get the value of attribute through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: Null Pointer Exception is thrown while setting value of <attributeName> instance variable in the object to value. An object is accessed to set the value of an instance variable through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_SETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Null Pointer Exception is thrown while setting value through <setMethodName> method in the object with argument <argument>. The set accessor method is invoked to set the value of attribute through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

PARENT_DESCRIPTOR_NOT_SPECIFIED

Cause: Cannot find descriptor for parent class. The descriptor of a subclass has no parent descriptor.

Action: The method on the subclass descriptor must be called.

PRIMARY_KEY_FIELDS_NOT_SPECIFIED

Cause: The primary key fields are not set for this descriptor.

Action: Add primary key field names using method or .

REFERENCE_CLASS_NOT_SPECIFIED

Cause: The reference class is not specified in the foreign reference mapping.

Action: Set reference class by calling startx io error 104

REFERENCE_DESCRIPTOR_IS_NOT_AGGREGATE

Cause: The referenced descriptor for <className> should be set to aggregate descriptor. An aggregate mapping should always reference a descriptor that is aggregate.

Action: Call method on the referenced descriptor.

REFERENCE_KEY_FIELD_NOT_PROPERLY_SPECIFIED

Cause: The table for the reference field must be the reference table, 20 01 error. If the reference field name specified in the direct collection mapping is qualified with the table name then the table name should match 20 01 error reference table name.

Action: Qualify the field with the proper name or change the reference table name.

REFERENCE_TABLE_NOT_SPECIFIED

Cause: The reference table name in the direct collection mapping is not specified.

Action: Use method on the mapping to set the table name.

RELATION_KEY_FIELD_NOT_PROPERLY_SPECIFIED

Cause: The table for the relation key field must be the relation table. If the source and target relation fields name specified in the many to many mapping are qualified with the table name then the table name should match the relation table name.

Action: Qualify the field with the proper name or change the relation table name.

RETURN_TYPE_IN_GET_ATTRIBUTE_ACCESSOR

Cause: The method <attributeMethodName> specified in the transformation mapping should have a return type set in the attribute because this method is used to extract value from the database row.

Action: Check the method and make appropriate changes.

SECURITY_ON_FIND_METHOD

Cause: The descriptor callback method <selector> with DescriptorEvent as argument is not accessible. Java throws security exception when a Method type is created from the method name using Java reflection. The method is a descriptor event callback on the domain object that takes DescriptorEvent as its parameter.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_ON_FIND_OBSOLETE_METHOD

Cause: The descriptor callback method <selector> with <session> as argument is not accessible. Java throws security exception when a Method type is created from the method name using Java reflection. The method is a descriptor event callback on the domain object which takes class and session as its parameters.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_ON_INITIALIZING_ATTRIBUTE_METHOD

Cause: Access to the method <attributeMethodName> with parameters <databaseRow> or <databaseRow, 20 01 error, Session> has been denied. Java throws security exception when a Method type is created from the attribute method name using Java reflection. The attribute method specified in the transformation mapping is used to extract value from the database row and set by calling .

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_CONVERTING_TO_METHOD

Cause: Method: <methodName> ACCESS DENIED with <> or <session> parameters. Java throws security exception when a Method type is created from the method name using Java reflection. These are the methods that will extract the field value from the domain object in the transformation mapping.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_ATTRIBUTES_IN_ INSTANCE_VARIABLE_ACCESSOR

Cause: Access to the instance variable, <attributeName> in the class <javaClassName> is denied. Java throws security exception when creating Field type from the given attribute name using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_ATTRIBUTES_IN_ METHOD_ACCESSOR

Cause: The methods <setMethodName> and <getMethodName> in the object <javaClassName> are inaccessible. Java throws security exception when creating Method type from the given attribute accessor method name using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_CLASS_ EXTRACTION_METHOD

Cause: The static class extraction method <methodName> with DatabaseRow as argument is not accessible. Java throws security exception when creating Method type from the given class extraction method name using Java reflection. The method is used to extract class from the database row in inheritance policy.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_COPY_POLICY

Cause: The clone method <methodName> with no arguments is not accessible. Java throws security exception when creating Method type from the given method name using Java reflection. This method on copy policy is used to create clones of the domain object.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_INSTANTIATION_POLICY

Cause: The instance creation method <methodName> with no arguments is not accessible. Java throws security exception when creating Method type from the given method name using Java reflection, 20 01 error. This method on instantiation policy is used to create new instances of the domain object.

Action: Inspect the internal exception and check the Java manuals.

SEQUENCE_NUMBER_PROPERTY_NOT_SPECIFIED

Cause: Either the sequence field name or the sequence number name is missing. To use sequence generated ids both the sequence number name and field name properties must be set.

Action: To use sequence-generated ids, both the sequence winphlash error 149 name and field name properties must be set.

SIZE_MISMATCH_OF_FOREIGN_KEYS

Cause: The size of the primary keys on the target table does 20 01 error match the size of the foreign keys on the source in one to one mapping.

Action: Check the mapping and the reference descriptor's primary keys.

TABLE_NOT_PRESENT

Cause: The table <tableName> is not present in the descriptor.

Action: Check the qualified field names specified in the mappings and descriptor, 20 01 error, if these fields are qualified with the table name then those fields should have right table.

TABLE_NOT_SPECIFIED

Cause: No table is specified in 20 01 error descriptor. Descriptor must have a table name defined.

Action: Call method or to set the tables on the descriptor.

TARGET_FOREIGN_KEYS_SIZE_MISMATCH

Cause: The size of the foreign keys on the target table does not match the size of the source keys on the source table in one to many mapping.

Action: Check the mapping.

TARGET_INVOCATION_WHILE_CLONING

Cause: 20 01 error in cloning the object <domainObject> clone method. <methodName> triggered an exception. Java is throwing exception when clone method is invoked using Java reflection while cloning object. The clone method is specified on the copy policy that is usually invoked to create clones in unit of work.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_EVENT_EXECUTION

Cause: The underlying descriptor callback method <eventMethodName> with DescriptorEvent as argument, throws an exception. Java is throwing exception when descriptor event method is invoked using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_GETTING_VALUE_ THRU_METHOD_ACCESSOR

Cause: The method <methodName> on the object <objectName> is throwing an exception. Java is throwing exception while getting an attribute value from the object through method accessor.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INSTANTIATING_ METHOD_BASED_PROXY

Cause: Method has thrown an exception. Java is throwing exception while instantiating method based proxy. This happens while instantiating transformation mapping.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INVOKING_ ATTRIBUTE_METHOD

Cause: The underlying method throws an exception. Java is throwing exception while invoking attribute transformation method on transformation mapping. The method is invoked to extract value from the database row to set into the domain object.

Action: Inspect the internal exception and exception in thread main java.lang.noclassdeffounderror la2 the Java manuals.

TARGET_INVOCATION_WHILE_INVOKING_FIELD_ TO_METHOD

Cause: The method <methodName> is throwing an exception. Java is throwing exception 20 01 error invoking field transformation method on transformation mapping. The method is invoked to extract value from the domain object to set into the database row.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INVOKING_ROW_ EXTRACTION_METHOD

Cause: Problem in extracting class from row <row>, static method, <method> with <databaseRow as argument>, 20 01 error. An exception was triggered Java is throwing exception while invoking class extraction method, 20 01 error. The method is used to extract class type so 20 01 error right kind of object can be created in inheritance model.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_METHOD_INSTANTIATION

Cause: Problem in creating new instance. Creation method <methodName> caused an exception. Java is throwing exception while invoking instantiation method. The method is used to create new instances of chrome runtime error this aplication domain objects.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_OBSOLETE_ EVENT_EXECUTION

Cause: The underlying descriptor callback method <eventMethodName> with <session> as argument, throws an exception. Java is throwing exception while invoking descriptor event method that takes session as its parameter.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_SETTING_VALUE_THRU_ METHOD_ACESSOR

Cause: The method <setMethodName> on the object is throwing an exception. Java is throwing exception while invoking set accessor method on the domain object to set an attribute value into the domain object.

Action: Inspect the internal exception and check the Java manuals.

VALUE_NOT_FOUND_IN_CLASS_INDICATOR_MAPPING

Cause: The indicator value is not found in the class indicator mapping in the parent descriptor for the class.

Action: Check on the inheritance policy.

WRITE_LOCK_FIELD_IN_CHILD_DESCRIPTOR

Cause: The child descriptor should not have a write lock field defined because it gets it from the parent descriptor.

Action: Check your child descriptor and remove the field.

DESCRIPTOR_IS_MISSING

Cause: The descriptor for the reference class <className> is missing from the mapping.

Action: Check session to see if the descriptor for the reference class was added.

MULTIPLE_TABLE_PRIMARY_KEY_MUST_BE_ FULLY_QUALIFIED

Cause: Multiple table primary key field names must be fully qualified. These fields names are given on the descriptor if it has more than one table.

Action: Specify the field names with table name.

ONLY_ONE_TABLE_CAN_BE_ADDED_WITH_THIS_METHOD

Cause: Only one table can be added through this method.

Action: Use to add multiple tables to descriptor.

NULL_POINTER_WHILE_CONSTRUCTOR_INSTANTIATION

Cause: Inaccessible constructor. Java is throwing this exception while invoking a default constructor to create new instances of the domain object.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_METHOD_INSTANTIATION

Cause: Problem in creating new instance <methodName> creation method is not accessible. Java is throwing an exception while calling a method to build new terrorizmge karsi kures of the domain object. This method is given by the user to override the default behavior of creating new instances through class constructor.

Action: Inspect the internal exception and check the Java manuals.

NO_ATTRBUTE_VALUE_CONVERSION_TO_FIELD_VALUE_PROVIDED

Cause: The field conversion value for the attribute value <attributeValue> was not given in the object type mapping, 20 01 error.

Action: Check the attribute value and provide a corresponding field value in the mapping.

NO_FIELD_VALUE_CONVERSION_TO_ATTRIBUTE_ VALUE_PROVIDED

Cause: The attribute conversion value for the <fieldValue> was not given in the object type mapping.

Action: Check the field value and provide a corresponding attribute value in the mapping.

LOCK_MAPPING_CANNOT_BE_READONLY

Cause: The domain object <className> cannot have a read only mapping for the write lock fields when the version value is stored in the object.

Action: Check the mappings on write lock fields.

LOCK_MAPPING_MUST_BE_READONLY

Cause: The domain object <className> should have a read only mapping for the write lock fields when the version value is stored in the cache.

Action: Check the mappings on write lock fields.

CHILD_DOES_NOT_DEFINE_ABSTRACT_QUERY_KEY

Cause: The queryKey <queryKeyName> is defined in the parent descriptor but not in the child descriptor, 20 01 error. The descriptor has not defined abstract query key.

Action: Any implementors of interface descriptor must define the query key defined by abstract query key in the interface descriptor.

SET_EXISTENCE_CHECKING_NOT_UNDERSTOOD

Cause: The interface descriptor <parent> must have at least one abstract query key defined. The string given to the method is not understood.

Action: The string passed should be one of the following:

  • Check cache
  • Check database
  • Assume existence
  • Assume non-existence

VALUE_HOLDER_INSTANTIATION_MISMATCH

Cause: The mapping for the attribute uses indirection and must be initialized to a new ValueHolder.

Action: Ensure the mapping uses indirection and the attribute is initialized to a new .

NO_SUB_CLASS_MATCH

Cause: No sub-class matches this class <theClass> when inheritance is in aggregate relationship mapping.

Action: Verify the sub-class and the relationship mapping.

RETURN_AND_MAPPING_WITH_INDIRECTION_MISMATCH

Cause: The get method return type for the attribute () is not declared as type20 01 error, but the mapping is using indirection.

Action: Ensure the get method returns a or change the mapping to not use indirection.

RETURN_AND_MAPPING_WITHOUT_INDIRECTION_ MISMATCH

Cause: The get method return type for the attribute is declared as typebut the mapping is not using indirection.

Action: Ensure the mapping is using indirection or change the return type from

PARAMETER_AND_MAPPING_WITH_INDIRECTION_ MISMATCH

Cause: The set method parameter type for the attribute is not declared as typebut the mapping is using indirection.

Action: Ensure the set method parameter is declared as a or the mapping is changed to not use indirection.

PARAMETER_AND_MAPPING_WITHOUT_INDIRECTION_ MISMATCH

Cause: The set method parameter type for the attribute is declared as typebut the mapping is not using indirection.

Action: Ensure the mapping is changed to use indirection or the set method parameter is not declared as a .

GET_METHOD_RETURN_TYPE_NOT_VALID

Cause: he get method return type for the attribute should be declared as type Vector (or a type that implements Map or Collection, if using Java2).

Action: The get method return type for the attribute should be declared as type Vector (or a type that implementsMap or Collection, if using Java2).

SET_METHOD_PARAMETER_TYPE_NOT_VALID

Cause: The set method parameter type for the attribute load dll error explay be declared as type Vector (or a type that implements Map or Collection, if using Java2).

Action: The set method parameter type for the attribute should be declared as type Vector (or a type that implements Map or Collection, if using Java2).

ILLEGAL_TABLE_NAME_IN_MULTIPLE_TABLE_ FOREIGN_KEY

Cause: The table in the multiple table foreign key relationship refers to an unknown table.

Action: Verify the table name.

ATTRIBUTE_AND_MAPPING_WITH_TRANSPARENT_ INDIRECTION_MISMATCH

Cause: The attribute is not declared as a super-type ofbut the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.

RETURN_AND_MAPPING_WITH_TRANSPARENT_ INDIRECTION_MISMATCH

Cause: The get method return type for the attribute is not declared as a super-type ofbut the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.

PARAMETER_AND_MAPPING_WITH_TRANSPARENT_ INDIRECTION_MISMATCH

Cause: The set method parameter type for the attribute is not declared as a super-type ofbut the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.

FIELD_IS_NOT_PRESENT_IN_DATABASE

Cause: Field <fieldname> is not present in the table <tableName> in the database.

Action: Verify the field name for the attribute.

TABLE_IS_NOT_PRESENT_IN_DATABASE

Cause: is not present in the database.

Action: Verify the table name for the descriptor.

MULTIPLE_TABLE_INSERT_ORDER_MISMATCH

Cause: The multiple table insert order Vector specifiedhas more/fewer tables than are specified 20 01 error the descriptor. All the tables must be included in the insert order Vector.

Action: Verify that all table names for the descriptor are present and that there are no extras.

INVALID_USE_OF_TRANSPARENT_INDIRECTION

Cause: Transparent Indirection can only be used with CollectionMappings.

Action: Verify the mapping. It must be a collection mapping.

MISSING_INDIRECT_CONTAINER_CONSTRUCTOR

Cause: The indirect container class must implement the constructor.

Action: Implement the constructor for the container.

COULD_NOT_INSTANTIATE_INDIRECT_CONTAINER_CLASS

Cause: The indirect container class could not be instantiated using the constructor.

Action: Validate the constructor for the indirect container class.

INVALID_CONTAINER_POLICY

Cause: This container policy should only be used in JDK containerPolicy, 20 01 error. It was instantiated for javaClass.

Action: Validate the container policy being used.

INVALID_CONTAINER_POLICY_WITH_TRANSPARENT_ INDIRECTION

Cause: The container policy is incompatible with transparent indirection.

Action: 20 01 error the container policy to be compatible with transparent indirection or do not use transparent indirection.

INVALID_USE_OF_NO_INDIRECTION

Cause: No Indirection should not receive this message.

Action: Change to use no indirection.

INDIRECT_CONTAINER_INSTANTIATION_MISMATCH

Cause: The mapping for the attribute uses transparent indirection and must be initialized to an appropriate container.

Action: Initialize the mapping 20 01 error an appropriate container.

INVALID_MAPPING_OPERATION

Cause: Invalid mapping operation.

Action: Check the documentation for valid mapping operations.

INVALID_INDIRECTION_POLICY_OPERATION

Cause: Invalid indirection policy operation.

Action: Check the documentation for valid indirection policy operations.

REFERENCE_DESCRIPTOR_IS_NOT_ AGGREGATECOLLECTION

Cause: The reference descriptor for <className> should be set to aggregate collection descriptor.

Action: Set the reference descriptor to an aggregate collection descriptor.

INVALID_INDIRECTION_CONTAINER_CLASS

Cause: Invalid indirection container class.

Action: Verify the container class.

MISSING_FOREIGN_KEY_TRANSLATION

Cause: The mapping does not include a foreign key field linked to the primary key field.

Action: Link the foreign key to the appropriate primary key.

TRUCTURE_NAME_NOT_SET_IN_MAPPING

Cause: The structure name is not set.

Action: Set the structure name appropriately.

NORMAL_DESCRIPTORS_DO_NOT_SUPPORT_ NON_RELATIONAL_EXTENSIONS

Cause: Normal descriptors do not support non-relational extensions.

Action: Contact Technical Support.

PARENT_CLASS_IS_SELF

Cause: The descriptor's parent class has been set to itself.

Action: Contact Technical Support.

PROXY_INDIRECTION_NOT_AVAILABLE

Cause: An attempt to use proxy indirection has been made but JDK is not being used.

Action: Proxy indirection is only supported in JDK

INVALID_ATTRIBUTE_TYPE_FOR_PROXY_INDIRECTION

Cause: The attribute wasn't specified in the list of interfaces given to use Proxy Indirection.

Action: Verify the attribute

INVALID_GET_RETURN_TYPE_FOR _PROXY_INDIRECTION

Cause: The return type for the indirection policy is invalid for the indirection policy.

Action: Verify that the parameter type of the attribute's get method is correct 20 01 error the indirection policy.

INVALID_SET_PARAMETER_TYPE_FOR_PROXY_ INDIRECTION

Cause: The parameter for the set method is incorrect for the indirection type.

Action: Verify that the parameter type of the attribute's set method is correct for the indirection policy.

INCORRECT_COLLECTION_POLICY

Cause: The container policy is invalid for the collection type.

Action: Check that the container policy is correct for the collection type.

INVALID_AMENDMENT_METHOD

Cause: The amendment method provided is invalid, not public, or cannot be found.

Action: Ensure the amendment method is public, static, returns void and has a single argument: Descriptor.

ERROR_OCCURRED_IN_AMENDMENT_METHOD

Cause: The specified amendment method threw an exception.

Action: Examine the returned exception for further details.

VARIABLE_ONE_TO_ONE_MAPPING_IS_NOT_DEFINED

Cause: There is no mapping for attribute.

Action: Validate the mapping and attribute.

TARGET_INVOCATION_WHILE_CONSTRUCTOR_ INSTANTIATION

Cause: Constructor is missing.

Action: Make the required constructor.

TARGET_INVOCATION_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: Constructor is missing.

Action: Make the required constructor.

ILLEGAL_ACCESS_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: Permissions do not permit access to the constructor.

Action: Adjust the Java security permissions to permit access to the constructor.

INSTANTIATION_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: An instantiation failed inside the associated constructor.

Action: Determine which objects are being instantiated, and ensure all are being done properly.

NO_SUCH_METHOD_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: A message send invoked from inside the constructor is invalid because the method does not exist.

Action: Correct the message send ensuring that the message exists.

NULL_POINTER_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: A message is being sent from inside a constructor to a null object.

Action: Avoid sending a message to an object that is null.

ILLEGAL_ACCESS_WHILE_METHOD_ INSTANTIATION_OF_FACTORY

Cause: A message is being sent to an object from inside a factory instantiation. Java has determined this message to be illegal.

Action: Determine why the message send is illegal, and replace the message with the proper legal one.

TARGET_INVOCATION_WHILE_METHOD_ INSTANTIATION_OF_FACTORY

Cause: Error inside the factory associated with the invocation of a target.

Action: Determine the faulty target, and replace with the correct target, or proper message send.

NULL_POINTER_WHILE_METHOD_ INSTANTIATION_OF_FACTORY

Cause: A message is being sent to null inside a factory instantiation.

Action: Avoid sending a message to null.

No such method

Cause: Tokens in the builder generated files are the subsets of all the tokens a Project Reader can understand. Each token has a related public method on TopLink, 20 01 error. The exception would mean that the method name is incorrect.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not find post load method <methodName> on class <aClass>

Cause: The post load method defined in descriptor properties is not defined on the related domain class.

Action: Must define the method on the specified class.

Cannot write parameter <object> of 20 01 error <type>

Cause: While creating project class the parameter tokens are read from the file and are converted to actual types before sending them to the methods. An unknown type will cause this exception.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not access method <method>

Cause: Java is throwing an illegal access reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invoking <applyResultMethod> raised exception <exception>

Cause: Java is throwing an invocation reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invalid arguments invoking: <applyResultMethod> with <receiver>

Cause: Java is throwing an invalid argument reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not access <applyResultMethod> with <receiver>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Parameter mismatch <method>; received <size> parameters

Cause: The number of parameters for the token read from the project or descriptor file do not match the number of parameters a related method can take.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Accessing <methodName> on <className> with <parameters>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files 20 01 error not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not find section definition <section> when building section definitions for <target>

Cause: Invalid section name was found in the project or descriptor file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the 20 01 error was manually edited or corrupted then the files must be generated again.

Could not convert <object> into an accessible Java class.

Cause: The parameter read from the file cannot be converted to a appropriate type.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

File not found

Cause: The project or descriptor file was not found.

Action: Check that the path was given correctly in a project reader and also the path is correct in project file.

Invalid class/method name format.

Cause: No one should actually be using the URL way of reading INI files, 20 01 error. This is untested and undocumented feature.

Action: Use other ways of reading files.

Open failed for URL <url>

Cause: Open failed for URL.

Action: Inspect the internal exception and check the Java manuals.

Could not resolve INIFile location: <sourceString> using search paths <searchPaths>

Cause: The file was not found on the given search paths.

Action: Check your search paths.

Invoking <method> on <receiver>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the 20 01 error exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to 20 01 error and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invoking <method> on <receiver>

Cause: Java is throwing reflection exception while invoking the method on 20 01 error object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invalid character value; expecting $* format

Cause: An invalid character format was written to the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported 20 01 error Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Unexpected character: {

Cause: Unexpected character { found while reading vector values from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Unexpected character: }

Cause: Unexpected character } found while reading vector values from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Expecting object, found token <nextToken>

Cause: Unexpected token found while reading from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Unexpected word

Cause: Unexpected token found while reading from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

setExistenceChecking <token>; not understood

Cause: Existence checking string specified on the descriptor is not understood.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Class <className> not found

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Not enough INI elements. Found <count>.

Cause: If the line in an INI file is incomplete, i.e., it does not have enough tokens.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Too many INI elements. Found <count>.

Cause: If the line in an INI file has more tokens then needed.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Error writing <writeString>

Cause: Could not write into the file. Perhaps are used and file or directory structure does not exist.

Action: Inspect the internal exception and check the Java manuals. Try using .

Illegal access exception

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Invocation target exception

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Attempting to instantiate <className> with default constructor.

Cause: Java is throwing reflection exception while instantiating the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Attempting to instantiate <className> with default constructor.

Cause: Java is throwing reflection exception while instantiating the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

IO Exception in next token

Cause: Java is throwing reflection. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

IOException on close.

Cause: Java is throwing reflection. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Invalid INI(URL) Method: <method>. Should return a string.

Cause: No one should actually be using the URL way of reading INI files. This is untested and undocumented feature.

Action: Use other ways of reading files.

Could not cast using <castString>.

Cause: An error occurred during an attempt to cast using the

Action: Validate the

A writer or a target file name must be specified

Cause: A writer or a target file name is not specified.

Action: A writer or a target file name must be specified.

IOException on open.

Cause: Java is throwing reflection. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Post Load Method Not Static

Cause: The method specified is not static.

Action: Modify the method to be static.

Project Not Found.

Cause: No projects were found in the specified directory.

Action: Verify the directory.

Multiple Projects With Name.

Cause: More than one project with the same name was found.

Action: Verify the project name.

WAIT_WAS_INTERRUPTED

Cause: In a multi threaded environment one of the waiting thread was interrupted.

Action: Usually such exceptions would mean restarting the application but it is totally dependent on the application.

WAIT_FAILURE_SERVER

Cause: Wait failure on ServerSession. When the number of non-pooled connections reach the threshold any more requests for 20 01 error connection results in wait until some one releases the connection resource. If this wait was interrupted then an exception is thrown.

Action: Usually such exceptions would mean restarting the application but it is totally dependent on the application.

WAIT_FAILURE_CLIENT

Cause: Wait failure on ClientSession. When the number of pooled connections reach the threshold any more requests for such connection results in wait until some one releases the connection resource. If this wait was interrupted then an exception is thrown.

Action: Usually such exceptions would mean restarting the application but it is totally dependent on the application.

SIGNAL_ATTEMPTED_BEFORE_WAIT

Cause: A signal was attempted before wait on concurrency manager. This normally means that an attempt was made to commit or rollback a transaction before it was started, or to rollback a transaction twice.

Action: Check transactions in the application.

COULD_NOT_BE_CONVERTED

Cause: The object <object> of class <objectClass> could not be converted to <javaClass>. The object cannot be converted to given type.

Action: Check that the object being converted is of right type or not.

INCORRECT_DATE_FORMAT

Cause: The date in <dateString> is in an incorrect format. Expected format is YYYY-MM-DD.

Action: Check the date format.

INCORRECT_TIME_FORMAT

Cause: The time in <timeString> is in an incorrect format. Expected format is HH:MM:SS.

Action: Check the time format.

INCORRECT_TIMESTAMP_FORMAT

Cause: The timestamp <timestampString> is in an incorrect format. Expected format is YYYY-MM-DD HH:MM:sprers.euNNN.

Action: Check the timestamp format.

COULD_NOT_CONVERT_TO_BYTE_ARRAY

Cause: The String object must be of even length to be converted to a ByteArray. This object could not be converted to a ByteArray

Action: Check the object being converted.

COULD_NOT_BE_CONVERTED_TO_CLASS

Cause: The object <object> of class <objectClass> could not be converted to <javaClass>. The class <javaClass> is not on the CLASSPATH.

Action: Check that the class <javaClass> is on the CLASSPATH.

SQL_EXCEPTION

Cause: An SQL exception was encountered, 20 01 error, thrown by the underlying JDBC bridge. TopLink only wraps that exception.

Action: One must inspect the internal exception thrown.

CONFIGURATION_ERROR_CLASS_NOT_FOUND

Cause: The driver class name was not found.

Action: Check the class name given in JDBCLogin.

DATABASE_ACCESSOR_NOT_CONNECTED

Cause: Session is not connected to the database while doing reading or writing on the database.

Action: An application may have to login again because the connection to the database might have been lost.

ERROR_READING_BLOB_DATA

Cause: Error reading blob data from the database. There are two possibilities for this exception, first is that the blob data was not read properly from the result set or the TopLink could not process the blob data using.

Action: Check if the underlying driver support blobs properly or not and if it does then report this problem to Technical Support.

OULD_NOT_CONVERT_OBJECT_TYPE

Cause: Could not convert object type on internal error. sprers.eu = <type>. The object from the result set cannot be converted to the type returned from the metadata information.

Action: Check if the underlying driver support the conversion type properly or not and if it does then error code 80072ee7 windows mobile this problem to Technical Support.

LOGOUT_WHILE_TRANSACTION_IN_PROGRESS

Cause: An attempt has been made to logout while the transaction is still in progress. You cannot logout while a transaction is in progress.

Action: Wait until the transaction is over.

SEQUENCE_TABLE_INFORMATION_NOT_COMPLETE

Cause: The sequence information given to TopLink is not sufficiently complete to get the set of sequence 20 01 error from the database. This usually happens on native sequencing on oracle database.

Action: Check the data given specially the sequence name given in TopLink.

ERROR_PREALLOCATING_SEQUENCE_NUMBERS

Cause: Error preallocating sequence numbers on the database; the sequence table information is not complete.

Action: Check if the sequence table was created on the database properly or not.

CANNOT_REGISTER_SYNCHRONIZATIONLISTENER_ FOR_UNITOFWORK

Cause: Cannot register Synchronization Listener: underlying_exception_string, 20 01 error. When the TopLink 20 01 error is configured with anany unit of work requested by a client must operate within the context of a JTS external global transaction. When a unit of work is created and the external global transaction is not in existence or if the system cannot acquire a reference to it, this error is reported.

Action: Ensure that a JTS transaction is in progress before acquiring the unit of work.

SYNCHRONIZED_UNITOFWORK_DOES_NOT_ SUPPORT_COMMITANDRESUME

Cause: Synchronized does not support the operation. When the TopLink Session is configured with an20 01 error, any unit of work requested by a client must operate within the context of a JTS external global transaction (see Error code: ). The JTS specification does not support the concept of "checkpointing" a transaction, that is, committing the work done and then continuing to work within the same transaction context (JTS does not support nested transactions, either). Thus, if client code invokes on a "synchronized" unit of work, this error will be reported.

Action: None.

CONFIGURATION_ERROR_NEW_INSTANCE_ INSTANTIATION_EXCEPTION

Cause: Configuration error. Attempting to instantiate Driver: <javaClass>. Could not instantiate driver.

Action: Check the driver.

CONFIGURATION_ERROR_NEW_INSTANCE_ILLEGAL_ ACCESS_EXCEPTION

Cause: A configuration error occurred while attempting to instantiate. Could not instantiate driver.

Action: Check the driver.

TRANSACTION_MANAGER_NOT_SET_FOR_JTS_DRIVER

Cause: The transaction manager has not been set for the .

Action: Set a transaction manager for the .

NO_VERSION_NUMBER_WHEN_DELETING

Cause: An attempt was made to delete the object <object> but it has no version number in the identity map. This object either was never read or has already been deleted.

Action: Logging SQL is very helpful in understanding the reason why the exception is thrown. The last delete will show the object we are deleting that throws an exception.

OBJECT_CHANGED_SINCE_LAST_READ_WHEN_DELETING

Cause: The object state has changed in the database. The object <object> cannot be deleted because it has changed or been deleted 20 01 error it was last read. This usually means that the row in the table was changed by some other application.

Action: Refreshing an object will refresh the object with the new data from the database.

NO_VERSION_NUMBER_WHEN_UPDATING

Cause: An attempt has been made to update the object <object> but it has no version number in the identity map. It may not have been read before being updated or has been deleted.

Action: Logging SQL is very helpful in understanding the reason why the exception is thrown. The last update will show the object we are updating that throws an exception.

OBJECT_CHANGED_SINCE_LAST_READ_WHEN_UPDATING

Cause: The object state has changed in the database. The object <object> cannot be updated because it has changed or been deleted since it was last read. This usually means that the row in the table was changed by some other application.

Action: Refreshing an object will refresh the object with the new data from the database.

MUST_HAVE_MAPPING_WHEN_IN_OBJECT

Cause: The object <aClass> must have a non-read-only mapping corresponding to the version lock field, 20 01 error. The mapping was not defined for the locking field. It is needed when the lock value is stored in the domain object than in a cache.

Action: Define a mapping for the field.

NEED_TO_MAP_JAVA_SQL_TIMESTAMP

Cause: A write lock value which is stored in a domain object is not an instance of.

Action: Change the value of the attribute to be an instance 20 01 error .

ADDITIONAL_SIZE_QUERY_NOT_SPECIFIED

Cause: Cursored SQL queries must provide an additional query to retrieve the size of the result set. Custom queries using cursor streams and not specifying the size query will cause this exception. The size query is used to retrieve the size of the number of object read from the database. This is done on JDBC compatible drivers because it provides no way to extract the size of the result set read. Non custom queries using cursor streams will have default queries generated by TopLink.

Action: Specify a size query.

AGGREGATE_OBJECT_CANNOT_BE_DELETED

Cause: Aggregated objects cannot be written or deleted independent of their owners. There is no identity maintained on such objects.

Action: Application's discretion.

ARGUMENT_SIZE_MISMATCH_IN_QUERY_AND_ QUERY_DEFINITION

Cause: The number of arguments provided to the query for execution does not match the number of arguments provided with sql server error 1706 query definition.

Action: Check the query and query execution.

BACKUP_CLONE_IS_ORIGINAL_FROM_PARENT

Cause: The object of class with identity hashcode is not from this unit of work space but from the parent session. The object was never registered in this unit of work but read from the parent session and related to an object registered in the unit of work.

Action: Ensure that you are correctly registering your objects. If you are still having problems, 20 01 error, you can use the method to help debug where the error occurred. Please see the manual and FAQ for more information.

BACKUP_CLONE_IS_ORIGINAL_FROM_SELF

Cause: The object clone of class with identity hashcode is the original to a registered new object. The unit of work clones registered new objects, 20 01 error, so you must ensure that it is registered before it is reference by another object. If you do not want the new object to be cloned, 20 01 error, used the U API.

Action: Ensure that you are correctly registering your objects. If you are still having problems, you can use the method to help debug where the error occurred, 20 01 error. Please see the manual and FAQ for more information.

BATCH_READING_NOT_SUPPORTED

Cause: This mapping does not support batch reading. The optimization of batching the read of all the target rows is not supported for the mapping.

Action: The problem is a TopLink development problem and user should never encounter this unless the mapping is a new custom mapping. Contact Technical Support.

DESCRIPTOR_IS_MISSING

Cause: Missing descriptor for <reference Class>. The descriptor related to the class or the object is not found in the session.

Action: Check if the related descriptor was added to the session or the query is done on the right object or class.

DESCRIPTOR_IS_MISSING_FOR_NAMED_QUERY

Cause: Missing descriptor for <domain Class Name> for query named <queryName>. 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 20 01 error is done on the right class.

INCORRECT_SIZE_QUERY_FOR_CURSOR_STREAM

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, 20 01 error.

Action: If the cursor stream query was custom query than check the size query specified else report this problem to Technical Support.

INVALID_QUERY

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.

INVALID_QUERY_KEY_IN_EXPRESSION

Cause: The query key <key> does not exist. 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.

INVALID_QUERY_ON_SERVER_SESSION

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, 20 01 error. Objects are changed in the client sessions acquired from this server session.

Action: Use client session's unit of work to change the object.

NO_CONCRETE_CLASS_INDICATED

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.

NO_CURSOR_SUPPORT

Cause: No cursor support provided for abstract class multiple table descriptors using expressions.

Action: Consider using custom SQL or multiple queries. <query>

OBJECT_TO_INSERT_IS_EMPTY

Cause: There are no fields to be insert into the table. The fields to insert into the table, <table> is empty. You must define at least one mapping for this table

Action: Must define at least one mapping for this table.

OBJECT_TO_MODIFY_NOT_SPECIFIED

Cause: An object to modify is required for a modify query.

Action: Ensure the query contains an object before executing.

QUERY_NOT_DEFINED

Cause: Query is not defined. When executing query on the session the parameter which takes query is null.

Action: Check if the query is passed properly.

QUERY_SENT_TO_INACTIVE_UNIT_OF_WORK

Cause: The unit of work has been released and is now inactive.

Action: The unit of work, once released, cannot be reused unless commitAndResume is called.

READ_BEYOND_QUERY

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.

REFERENCE_CLASS_MISSING

Cause: The reference class in the query is not specified. A reference class must be provided.

Action: Check the query.

REFRESH_NOT_POSSIBLE_WITHOUT_CACHE

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, 20 01 error. Refreshing is not possible without identity.

Action: Check query.

SIZE_ONLY_SUPPORTED_ON_EXPRESSION_QUERIES

Cause: Did not find size query. Size only supported on expression queries, 20 01 error, unless a size query is given.

Action: Cursor streams on custom query should also define size query.

SQL_STATEMENT_NOT_SET_PROPERLY

Cause: The SQL statement has not been properly set. The user should never encounter this unless queries have been customized.

Action: Contact Technical Support.

INVALID_QUERY_ITEM

Cause: Invalid query item expression.

Action: Validate the Expression being used.

SELECTION_OBJECT_CANNOT_BE_NULL

Cause: The selection object passed to a read object or refresh was null.

Action: Check on the read query.

UNNAMED_QUERY_ON_SESSION_BROKER

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, 20 01 error, unless the query is named.

Action: Session broker has no idea about such queries about which session to execute the query on, 20 01 error. Specify the session name.

REPORT_RESULT_WITHOUT_PKS

Cause: ReportQuery without PKs cannot readObject. 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 on report query.

NULL_PRIMARY_KEY_IN_BUILDING_OBJECT

Cause: The primary key 20 01 error from the row, <databaseRow> during the execution of the query was detected to be null; primary keys must not contain null.

Action: Check query and also the table on the database.

NO_DESCRIPTOR_FOR_SUBCLASS

Cause: The subclass has no descriptor defined for it.

Action: Check session if the descriptor was added or not or else check class extraction method.

CANNOT_DELETE_READ_ONLY_OBJECT

Cause: Cannot delete an object of read-only class. The class <className> is declared read-only in this unit of work. Thrown in unit of work when trying to delete an object that is marked as read only.

Action: Contact Technical Support.

INVALID_OPERATOR

Cause: The operator <data> used in the expression is not valid.

Action: Check class to see a list of all of the operators supported.

ILLEGAL_USE_OF_GETFIELD

Cause: Illegal use of <data> in expression. This is a TopLink development exception that users should not encounter.

Action: Report this problem to Technical Support.

ILLEGAL_USE_OF_GETTABLE

Cause: Illegal use of <data> in expression, 20 01 error. This is a TopLink development exception that users should not encounter.

Action: Report this problem to Technical Support.

REPORT_QUERY_RESULT_SIZE_MISMATCH

Cause: The number of attributes requested does not match the attributes returned from the database in report query, 20 01 error. 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 20 01 error Technical Support.

CANNOT_CACHE_PARTIAL_OBJECT

Cause: Partial Objects are never put in the cache. Partial 20 01 error queries are not allowed to maintain the cache or be edited. You must set .

Action: Call the method before executing the query.

OUTER_JOIN_ONLY_VALID_FOR_ONE_TO_ONE

Cause: An outer join () is only valid for one to one mappings, and cannot asus error 23 recovery used for the mapping, 20 01 error.

Action: Do not attempt to use for mappings other than one to one.

CANNOT_ADD_TO_CONTAINER

Cause: Cannot add <anObject> to a <containerClass> using <policy>, 20 01 error. This is TopLink development exception and user should never encounter this problem unless a custom container policy has been 20 01 error Contact Technical Support.

METHOD_INVOCATION_FAILED

Cause: The method invocation of <aMethod> on the object <anObject> threw a Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

CANNOT_CREATE_CLONE

Cause: Canon error 280 create a clone of <anObject> using <policy>. This is a TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Report this problem to Technical Support.

METHOD_NOT_VALID

Cause: The method <methodName> is not valid to call on object <aReceiver>. This is a TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Contact Technical Support.

METHOD_DOES_NOT_EXIST_IN_CONTAINER_CLASS

Cause: The method named <methodName> was not found in class <aClass>. Thrown when looking for clone method on the container class. The clone is needed to create clones of the container in unit of work.

Action: Define clone method on the container class.

COULD_NOT_INSTANTIATE_CONTAINER_CLASS

Cause: The class <aClass> cannot be used as the container for the results of a query since it cannot be instantiated. Thrown when new interface container policy is being created using Java reflection.

Action: Check Java documentation on the internal exception.

MAP_KEY_NOT_COMPARABLE

Cause: Could not use object <anObject> of type <objectClass> as a key into <aContainer> which is of type <containerClass>. Key cannot be compared with the keys currently in the map. Throws Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

CANNOT_ACCESS_METHOD_ON_OBJECT

Cause: Cannot reflectively access the method <aMethod> for object: <anObject> of type <anObjectClass>. Throws Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

CALLED_METHOD_THREW_EXCEPTION

Cause: The method <aMethod> was called reflectively on object <object> of class <objectClass> and threw an exception. Throws Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

INVALID_OPERATION

Cause: Invalid operation <operation> on cursor. The operation is not supported.

Action: Check the class documentation and look for the corresponding method that should be used.

CANNOT_REMOVE_FROM_CONTAINER

Cause: Cannot remove <anObject> of type <anObjectClass> from <aContainerClass> using <policy>. This is TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Contact Technical Support.

CANNOT_ADD_ELEMENT

Cause: Cannot add element to the collection container policy (cannot add <anObject> of type <anObjectClass> to a <aContainerClass>).

Action: Check Java documentation on the internal exception.

BACKUP_CLONE_DELETED

Cause: Deleted objects cannot have reference after being deleted. The object clone of class <sprers.euss()> with identity hashcode (sprers.eutyHashCode()) <sprers.eutyHashCode(clone)> has been deleted, but still has references.

Action: Ensure that you are correctly registering your objects. If you are still having problems, you can use the method to help debug where the error occurred. Please see the manual and FAQ for more information.

CANNOT_COMPARE_TABLES_IN_EXPRESSION

Cause: Cannot compare table reference to <data> in expression

Action: Check the expression

INVALID_TABLE_FOR_FIELD_IN_EXPRESSION

Cause: Field has invalid table in this context for field <data> in expression.

Action: Check the expression

INVALID_USE_OF_TO_MANY_QUERY_KEY_IN_EXPRESSION

Cause: Invalid use of a query key representing a to-many relationship <data> in expression, 20 01 error. 20 01 error rather than .

Action: Use the operator instead of .

INVALID_USE_OF_ANY_OF_IN_EXPRESSION

Cause: Invalid canon e22 error code of for a query key not representing a to-many relationship <data> in expression. Use rather than .

Action: Use the operator instead of .

CANNOT_QUERY_ACROSS_VARIABLE_ONE_TO_ ONE_MAPPING

Cause: Querying across a variable one-to-one mapping is not supported.

Action: Change the expression such that the query in not done across a variable one to one mapping.

ILL_FORMED_EXPRESSION

Cause: Ill-formed expression in query, attempting 20 01 error print an object reference into a SQL statement for <queryKey>.

Action: Contact Technical Support.

CANNOT_CONFORM_EXPRESSION

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.

INVALID_OPERATOR_FOR_OBJECT_EXPRESSION

Cause: Object comparisons can only use the or operators, other comparisons must be done through query keys or direct attribute level comparisons.

Action: Ensure the query uses only and if object comparisons are being used.

UNSUPPORTED_MAPPING_FOR_OBJECT_COMPARISON

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.

OBJECT_COMPARISON_CANNOT_BE_PARAMETERIZED

Cause: Object comparisons cannot be used in parameter queries.

Action: Change the 20 01 error such that it does not attempt to use object when using parameterized queries.

INCORRECT_CLASS_FOR_OBJECT_COMPARISON

Cause: The class of the argument for the object comparison is incorrect.

Action: Ensure the class for the query is correct.

CANNOT_COMPARE_TARGET_FOREIGN_KEYS_ TO_NULL

Cause: Object comparison cannot be used for target foreign key relationships. Query on the source primary key instead.

Action: Query on source primary key.

INVALID_DATABASE_CALL

Cause: Invalid database call - the call must be an instance of DatabaseCall: <call>.

Action: Ensure the call being used is a DatabaseCall.

INVALID_DATABASE_ACCESSOR

Cause: Invalid database accessor - the accessor must be an instance of DatabaseAccessor: <accessor>.

Action: Ensure the accessor being used is a DatabaseAccessor.

METHOD_DOES_NOT_EXIST_ON_EXPRESSION

Cause: Method: <methodName> with argument types: <argTypes> cannot be invoked on Expression.

Action: Ensure the method being used is a supported method.

IN_CANNOT_BE_PARAMETERIZED

Cause: Queries using IN cannot be parameterized.

Action: Either disable the query prepare or binding.

REDIRECTION_CLASS_OR_METHOD_NOT_SET

Cause: The redirection query was not configured properly, the class or method name was not set.

Action: Check the configuration for the redirection class.

REDIRECTION_METHOD_NOT_DEFINED_CORRECTLY

Cause: The redirection query's method is not defined or define with the wrong arguments. It must be public static and have arguments DatabaseQuery, DatabaseRow, Session (the interface).

Action: Check the redirection query's method as above.

REDIRECTION_METHOD_ERROR

Cause: The redirection query's method invocation threw an exception.

Action: Check the redirection method for problems.

EXAMPLE_AND_REFERENCE_OBJECT_CLASS_MISMATCH

Cause: There is a class mismatch between the example object and the reference class specified for this query.

Action:

1. Result Codes versus Error Codes

Overview

Many of the routines in the SQLite C-language Interface return numeric result codes indicating either success or failure, 20 01 error, and in the event of a failure, providing some idea of the cause of the failure. This smart 199 ultra dma crc errors strives to explain what each of those numeric result codes means.

"Error codes" are a subset of "result codes" that indicate that something has gone wrong, 20 01 error. There are only a few non-error result codes: SQLITE_OK, SQLITE_ROW, 20 01 error, and SQLITE_DONE. The term "error code" means any result code other than these three.

Result codes are signed bit integers. The least significant 8 bits of the result code define a broad category and are called the "primary result code". More significant bits provide more detailed information about the error and are called the "extended result code"

Note that the primary result code is always a part of the extended result code. Given a full bit extended result code, the application can always find the corresponding primary result code merely by extracting the least significant 8 bits of the extended result code, 20 01 error.

All extended result codes are also error codes. Hence the terms "extended result code" and "extended error code" are interchangeable.

For historic compatibility, the C-language interfaces return primary result codes by default. The extended result code for the most recent error can be retrieved using the sqlite3_extended_errcode() interface. The sqlite3_extended_result_codes() interface can be used to put a database connection into a mode where it returns the extended result codes instead of the primary result codes.

All result codes are integers. Symbolic names for all result 20 01 error are created using "#define" macros in the sqlite3.h header file, 20 01 error. There are separate sections in the sqlite3.h header file for the result code definitions and the extended result code definitions.

Primary result code symbolic names are of the form "SQLITE_XXXXXX" where XXXXXX is a sequence of uppercase alphabetic characters. Extended result code names are of the form "SQLITE_XXXXXX_YYYYYYY" where the XXXXXX part is the corresponding primary 20 01 error code and the YYYYYYY is an extension that further classifies the result code.

The names and numeric values for existing result codes are fixed and unchanging. However, new result codes, and especially new extended result codes, 20 01 error, might appear in future releases of SQLite.

The 31 result codes are defined in sqlite3.h and are listed in alphabetical order below:

The 74 extended result codes are defined in sqlite3.h 20 01 error are listed in alphabetical order below:

The meanings for all result code values are shown below, in numeric order.

(0) SQLITE_OK

The SQLITE_OK result code means that the operation was successful and that there were no errors. Most other result codes indicate an error.

(1) SQLITE_ERROR

The SQLITE_ERROR result code is a generic error code that is used when no other more specific error code is available.

(2) SQLITE_INTERNAL

The SQLITE_INTERNAL result code indicates an internal malfunction. In a working version of SQLite, 20 01 error, an application should never see this result code. If application does encounter this result code, it shows that there is a bug in the database engine.

SQLite does not currently generate this result code, 20 01 error. However, application-defined SQL functions or virtual tables, or VFSes, or other extensions might cause this result code to be returned, 20 01 error.

(3) SQLITE_PERM

The SQLITE_PERM result code indicates that the requested access mode for a newly created database could not be provided.

(4) SQLITE_ABORT

The SQLITE_ABORT result code indicates that an operation was aborted prior to completion, usually be application request, 20 01 error. See also: SQLITE_INTERRUPT, 20 01 error.

If the callback function to sqlite3_exec() returns non-zero, then sqlite3_exec() will return SQLITE_ABORT, 20 01 error.

If a ROLLBACK operation occurs on the same database connection as a pending read or write, then the pending read or write may fail with an SQLITE_ABORT or SQLITE_ABORT_ROLLBACK error.

In addition to being a result code, the SQLITE_ABORT value is also used as a conflict resolution mode returned from the sqlite3_vtab_on_conflict() interface.

(5) SQLITE_BUSY

The SQLITE_BUSY result code indicates that the database file could not be written (or in some cases read) because of concurrent activity by some other database connection, usually a database connection in a separate process.

For example, if process A is in the middle of a large write transaction and at the same time process B attempts to start a new write transaction, process B will get back an SQLITE_BUSY result because SQLite only supports one writer at a time. Process B will need to wait for process A to finish its transaction before starting a new transaction. The sqlite3_busy_timeout() and sqlite3_busy_handler() interfaces and the busy_timeout pragma are available to process B to help it deal with SQLITE_BUSY errors, 20 01 error.

An SQLITE_BUSY error can occur at any point in a transaction: when the transaction is first started, during any write or update operations, or when the transaction commits. To avoid 20 01 error SQLITE_BUSY errors in the middle of a transaction, the application can use BEGIN IMMEDIATE instead of just BEGIN to start a transaction, 20 01 error. The BEGIN IMMEDIATE command might itself return SQLITE_BUSY, but if it succeeds, then SQLite guarantees that no subsequent operations on the same database through the next COMMIT will return SQLITE_BUSY.

See also: SQLITE_BUSY_RECOVERY and SQLITE_BUSY_SNAPSHOT.

The SQLITE_BUSY result code differs from SQLITE_LOCKED in that SQLITE_BUSY indicates a conflict with a separate database connection, probably in a separate process, whereas SQLITE_LOCKED indicates a conflict within the same database connection (or sometimes a database connection with a shared cache).

(6) SQLITE_LOCKED

The SQLITE_LOCKED result code indicates that a write operation could not continue because of a conflict within the same database connection or a conflict with a different database connection that uses a shared cache.

For example, a DROP TABLE statement cannot be run while another thread is reading from that table on the same database connection because dropping the table would delete the table out from under the concurrent reader.

The SQLITE_LOCKED result code differs from SQLITE_BUSY in that SQLITE_LOCKED indicates a conflict on the same database connection (or on a connection with a shared cache) whereas SQLITE_BUSY indicates a conflict with a different database connection, probably in a different process.

(7) SQLITE_NOMEM

The SQLITE_NOMEM result code indicates that SQLite was unable to allocate all the memory it needed to complete the operation. In other words, an internal call to sqlite3_malloc() or sqlite3_realloc() has failed in a case where the memory being allocated was required in order to continue the operation.

(8) SQLITE_READONLY

The SQLITE_READONLY result code is returned when an attempt is made to alter some data for which the current database connection does not have write permission.

(9) SQLITE_INTERRUPT

The SQLITE_INTERRUPT result code indicates that an operation was interrupted by the sqlite3_interrupt() interface. See also: SQLITE_ABORT

(10) SQLITE_IOERR

The SQLITE_IOERR result code says that the operation could not finish because the operating system reported an I/O error.

A full disk drive will normally give an SQLITE_FULL error rather than an SQLITE_IOERR error.

There are many different extended result codes for I/O errors that identify the specific I/O operation that failed.

(11) SQLITE_CORRUPT

The SQLITE_CORRUPT result code indicates that the database file has been corrupted. See the How To Corrupt Your Database Files for further discussion on how corruption can occur.

(12) SQLITE_NOTFOUND

The SQLITE_NOTFOUND result code is exposed in three ways:

  1. SQLITE_NOTFOUND can be returned by the sqlite3_file_control() interface to indicate that the file control opcode passed as the third argument was not recognized by the underlying VFS, 20 01 error.

  2. SQLITE_NOTFOUND can also be returned by the xSetSystemCall() method of an sqlite3_vfs object.

  3. SQLITE_NOTFOUND an be returned by sqlite3_vtab_rhs_value() to indicate that the right-hand operand of a constraint is not available to the xBestIndex method that made the call.

The SQLITE_NOTFOUND result code is also used internally by the SQLite implementation, but those internal uses are not exposed to the application.

(13) SQLITE_FULL

The SQLITE_FULL result code indicates that a write could not complete because the disk is full. Note that this error can occur when trying to write information into the main database file, or it can also occur when writing into temporary disk files, 20 01 error.

Sometimes applications encounter this error even though there is an abundance of primary disk space because 20 01 error error occurs when writing into temporary disk files on a system where temporary files are stored on a separate partition with much less space that the primary disk.

(14) SQLITE_CANTOPEN

The SQLITE_CANTOPEN result code indicates that SQLite was unable to open a file. The file in question might be a primary database file or one of several temporary disk files.

(15) SQLITE_PROTOCOL

The SQLITE_PROTOCOL result code indicates a problem with the file locking protocol used by SQLite. The SQLITE_PROTOCOL error is currently only returned when using WAL mode and attempting to start a new transaction, 20 01 error. There is a race condition that can occur when two separate database connections both try to start a transaction at the same time in WAL mode. The loser of the race backs off and tries again, after a brief delay. If the same connection loses the locking race dozens of times over a span of multiple seconds, it will eventually give up and return SQLITE_PROTOCOL, 20 01 error. The SQLITE_PROTOCOL error should appear in practice very, very rarely, and only when there are many separate processes all competing intensely to write to the same database.

(16) SQLITE_EMPTY

The SQLITE_EMPTY result code is 20 01 error currently used, 20 01 error.

(17) SQLITE_SCHEMA

The SQLITE_SCHEMA result code indicates that the database schema has changed. This result code can be returned from sqlite3_step() for a prepared statement that was generated using sqlite3_prepare() or sqlite3_prepare16(), 20 01 error. If the database schema was changed by some other process in between the time that the statement was prepared and the time the statement was run, this error can result, 20 01 error.

If a prepared statement is generated from sqlite3_prepare_v2() then the statement is automatically re-prepared if the schema changes, up to SQLITE_MAX_SCHEMA_RETRY times (default: 50). The sqlite3_step() interface will only return SQLITE_SCHEMA back to the application if the failure persists after these many retries, 20 01 error.

(18) SQLITE_TOOBIG

The SQLITE_TOOBIG error code 20 01 error that a string or BLOB was too large. The default maximum length of a string or BLOB in SQLite is 1,, bytes, 20 01 error. This maximum length can be changed at compile-time using the SQLITE_MAX_LENGTH compile-time option, or at run-time using the sqlite3_limit(db,SQLITE_LIMIT_LENGTH,) interface. The SQLITE_TOOBIG error results when SQLite encounters a string or BLOB that exceeds the compile-time or run-time limit.

The SQLITE_TOOBIG error code can also result when an oversized SQL statement is passed into one of the sqlite3_prepare_v2() interfaces. The maximum length of an SQL statement defaults to a much smaller value of 1,, bytes. The maximum SQL statement length can be set at compile-time using SQLITE_MAX_SQL_LENGTH or at run-time using sqlite3_limit(db,SQLITE_LIMIT_SQL_LENGTH,).

(19) SQLITE_CONSTRAINT

The SQLITE_CONSTRAINT error code means that an SQL constraint violation occurred while trying to process an SQL statement. Additional information about the failed constraint can be found by consulting the accompanying error message (returned via sqlite3_errmsg() or sqlite3_errmsg16()) or by looking at the extended error code.

The SQLITE_CONSTRAINT code can also be used as the return value from the xBestIndex() method of a virtual table implementation. When xBestIndex() returns SQLITE_CONSTRAINT, that indicates that the particular combination of inputs submitted to xBestIndex() cannot result in a usable query plan and should not be given further consideration.

(20) SQLITE_MISMATCH

The SQLITE_MISMATCH error code indicates a datatype mismatch.

SQLite is normally very forgiving about 20 01 error between the type of a value and the declared type of the container in which that value is to be stored. For example, SQLite allows the application to store a large BLOB in a column with a declared type of BOOLEAN. But in a few cases, SQLite is strict about types. The SQLITE_MISMATCH error is returned in those few cases when the types do not match.

The rowid of a table must be an integer. Attempt to set the rowid to anything other than an integer (or a NULL which will be automatically converted into the next available integer rowid) results in an SQLITE_MISMATCH error.

(21) SQLITE_MISUSE

The 20 01 error return code might be returned if the application uses any SQLite interface in a way that is undefined or unsupported, 20 01 error. For example, 20 01 error, using a prepared statement after that prepared statement has been finalized might result in an SQLITE_MISUSE error.

SQLite tries to detect misuse and report the misuse using this result code. However, there is no guarantee that the detection of misuse will be successful. Misuse detection is probabilistic. Applications should 20 01 error depend on an SQLITE_MISUSE return value.

If SQLite ever returns SQLITE_MISUSE from any interface, that means that the application is incorrectly coded and needs to be fixed. Do not ship an application that sometimes returns SQLITE_MISUSE from a standard SQLite interface because that application contains potentially serious bugs. 20 01 error SQLITE_NOLFS

The SQLITE_NOLFS error can be returned on systems that do not support large files when the database grows to be larger than what the filesystem can handle. "NOLFS" stands for "NO Large File Support".

(23) SQLITE_AUTH

The SQLITE_AUTH error is returned when the authorizer callback indicates that an SQL statement being prepared is not authorized.

(24) SQLITE_FORMAT

The SQLITE_FORMAT error code is not currently used by SQLite.

(25) SQLITE_RANGE

The SQLITE_RANGE error indices that the parameter number argument to one of the sqlite3_bind routines or the column number in one of the sqlite3_column routines is out of range, 20 01 error.

(26) SQLITE_NOTADB

When attempting to open a file, the SQLITE_NOTADB error indicates that the file being opened does not appear to be an SQLite database file.

(27) SQLITE_NOTICE

The SQLITE_NOTICE result code is not returned by any C/C++ interface. However, SQLITE_NOTICE (or rather one of its extended error codes) is sometimes used as the first argument in an sqlite3_log() callback to indicate that an unusual operation is taking place.

(28) SQLITE_WARNING

The SQLITE_WARNING result code is not returned by any C/C++ interface. However, SQLITE_WARNING (or rather one of its extended error codes) is sometimes used as the first argument in an sqlite3_log() callback to indicate that an unusual and possibly ill-advised operation is taking place.

() SQLITE_ROW

The SQLITE_ROW result code returned by sqlite3_step() indicates that another row of output is available.

() SQLITE_DONE

The SQLITE_DONE result code indicates that an operation has completed. The SQLITE_DONE result code is most commonly seen as a return value from sqlite3_step() indicating that the SQL statement has run to completion. But SQLITE_DONE can also be returned by other multi-step interfaces such as sqlite3_backup_step(), 20 01 error.

() SQLITE_OK_LOAD_PERMANENTLY

The sqlite3_load_extension() interface loads an extension into a single database connection. The default behavior is for that extension to be automatically unloaded when the database connection closes. However, if the extension entry point returns SQLITE_OK_LOAD_PERMANENTLY instead of SQLITE_OK, then the extension remains loaded into the process address space after the database connection closes. In other words, the xDlClose methods of the sqlite3_vfs object is not called for the extension when the database connection closes.

The SQLITE_OK_LOAD_PERMANENTLY return code is useful to loadable extensions that register new VFSes, for example.

() SQLITE_ERROR_MISSING_COLLSEQ

The SQLITE_ERROR_MISSING_COLLSEQ result code means that an SQL statement could not be prepared because a collating sequence named in that SQL statement could not be located, 20 01 error.

Sometimes when this error code is encountered, the sqlite3_prepare_v2() routine will convert the error into SQLITE_ERROR_RETRY and try again to prepare the SQL statement using a different query plan that does not require the use of the unknown collating sequence.

() SQLITE_BUSY_RECOVERY

The SQLITE_BUSY_RECOVERY error code is an extended error code for SQLITE_BUSY that indicates that an operation could not continue because another process is busy recovering a WAL mode database file following a crash. The SQLITE_BUSY_RECOVERY error code only occurs on WAL mode databases.

() SQLITE_LOCKED_SHAREDCACHE

The SQLITE_LOCKED_SHAREDCACHE result code indicates that access to an SQLite data record is blocked by another database connection that is using the same record in shared cache mode. When two or more database connections share the same cache and one of the connections is in the middle of modifying a record in that cache, then other connections are blocked from accessing that data while the modifications are on-going in order to prevent the readers from seeing a corrupt or partially completed change.

() SQLITE_READONLY_RECOVERY

The SQLITE_READONLY_RECOVERY error code is an extended error code for SQLITE_READONLY. The SQLITE_READONLY_RECOVERY error code indicates that a WAL mode database cannot be opened because the database file needs to be recovered and recovery requires write dll messagebox error but only read access is available.

() SQLITE_IOERR_READ

The SQLITE_IOERR_READ error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to read from a file on disk. This error might result from a hardware malfunction or because a filesystem came unmounted while the file was open.

() SQLITE_CORRUPT_VTAB

The SQLITE_CORRUPT_VTAB error code is an extended error code for SQLITE_CORRUPT used by virtual tables. A virtual table might return SQLITE_CORRUPT_VTAB to indicate that content in the virtual table is forall oracle ignore error.

() SQLITE_CANTOPEN_NOTEMPDIR

The SQLITE_CANTOPEN_NOTEMPDIR error code is no longer used.

() SQLITE_CONSTRAINT_CHECK

The SQLITE_CONSTRAINT_CHECK error code is an extended error code for SQLITE_CONSTRAINT indicating that a CHECK constraint failed.

() SQLITE_AUTH_USER

The SQLITE_AUTH_USER error code is an extended error code for SQLITE_AUTH indicating that an operation was attempted on a database for which the logged in user lacks sufficient authorization, 20 01 error.

() SQLITE_NOTICE_RECOVER_WAL

The SQLITE_NOTICE_RECOVER_WAL result code is passed to the callback of sqlite3_log() when a WAL mode database file is recovered, 20 01 error.

() SQLITE_WARNING_AUTOINDEX

The SQLITE_WARNING_AUTOINDEX result code is passed to the callback of sqlite3_log() whenever automatic indexing is used. This can serve as a warning to application designers that the database might benefit from additional indexes.

() SQLITE_ERROR_RETRY

The SQLITE_ERROR_RETRY is used internally to provoke sqlite3_prepare_v2() (or one of its sibling routines for creating prepared statements) to try again to prepare a statement that failed with an error on the previous attempt.

() SQLITE_ABORT_ROLLBACK

The SQLITE_ABORT_ROLLBACK error code is an extended error code for SQLITE_ABORT indicating that an SQL statement aborted because the transaction that was active when the SQL statement first started was rolled back. Pending write operations always fail with this error when a rollback occurs. A ROLLBACK will cause a pending read operation to fail only if the schema was changed within the transaction being rolled back, 20 01 error.

() SQLITE_BUSY_SNAPSHOT

The SQLITE_BUSY_SNAPSHOT error code is an extended error code for SQLITE_BUSY that occurs on WAL mode databases when a database connection tries to promote a read transaction into a write transaction but finds that another database connection has already written to the database and thus invalidated prior reads.

The following scenario illustrates how an SQLITE_BUSY_SNAPSHOT error might arise:

  1. Process A starts a read transaction on the database and does one or more SELECT statement. Process A keeps the transaction open.
  2. Process B updates the database, changing values previous read by process A.
  3. Process A now tries to write to the database. But process A's view of the database content is now obsolete because process B has modified the database file after process A read from it. Hence process A gets an SQLITE_BUSY_SNAPSHOT error.

() SQLITE_LOCKED_VTAB

The SQLITE_LOCKED_VTAB result code is not used by the SQLite core, 20 01 error, but it is available for use by extensions. Virtual table implementations can return this result code to indicate that they cannot complete the current operation because of locks held by other 20 01 error or processes.

The R-Tree extension returns this result code when an attempt is made to update the R-Tree while another prepared statement is actively reading the R-Tree. The update cannot proceed because any change to an R-Tree might involve reshuffling and rebalancing of nodes, which would disrupt read cursors, causing some rows to be repeated and other rows to be omitted.

() SQLITE_READONLY_CANTLOCK

The SQLITE_READONLY_CANTLOCK error code is an extended error code for SQLITE_READONLY. The SQLITE_READONLY_CANTLOCK error code indicates that SQLite is unable to obtain a read lock on a WAL mode database because the shared-memory file associated with that database is read-only, 20 01 error.

() SQLITE_IOERR_SHORT_READ

The SQLITE_IOERR_SHORT_READ error code is an extended error code for SQLITE_IOERR indicating that a read attempt in the VFS layer was unable to obtain as many bytes as was requested. This might be due to a truncated file.

() SQLITE_CORRUPT_SEQUENCE

The SQLITE_CORRUPT_SEQUENCE result code means that the schema of the sqlite_sequence table is corrupt. The sqlite_sequence table is used to help implement the AUTOINCREMENT feature. The sqlite_sequence table should have the following format:

CREATE TABLE sqlite_sequence(name,seq);

If SQLite discovers that the sqlite_sequence table has any other format, it returns the SQLITE_CORRUPT_SEQUENCE error.

() SQLITE_CANTOPEN_ISDIR

The SQLITE_CANTOPEN_ISDIR error code is an extended error code for SQLITE_CANTOPEN indicating that a file open operation failed because the file is really a directory.

() SQLITE_CONSTRAINT_COMMITHOOK

The SQLITE_CONSTRAINT_COMMITHOOK error code is an extended error code for SQLITE_CONSTRAINT indicating that a commit hook callback returned chassis intrusion error that thus caused the SQL statement to be rolled back.

() SQLITE_NOTICE_RECOVER_ROLLBACK

The SQLITE_NOTICE_RECOVER_ROLLBACK result code is passed to the callback of sqlite3_log() when a hot journal is rolled back.

() SQLITE_ERROR_SNAPSHOT

The SQLITE_ERROR_SNAPSHOT result code might be returned when attempting to start a read transaction on an historical version of the database by using the sqlite3_snapshot_open() interface. If the historical snapshot is no longer available, then the read transaction will fail with the SQLITE_ERROR_SNAPSHOT. This error code is only possible if SQLite is compiled with 20 01 error.

() SQLITE_BUSY_TIMEOUT

The SQLITE_BUSY_TIMEOUT error code indicates that a blocking Posix advisory file lock request in the VFS layer failed due to a timeout. Blocking Posix advisory locks are only available as a proprietary SQLite extension and even then are only supported if SQLite is compiled with the SQLITE_EANBLE_SETLK_TIMEOUT compile-time option.

() SQLITE_READONLY_ROLLBACK

The SQLITE_READONLY_ROLLBACK error code is an extended error code for SQLITE_READONLY, 20 01 error. The SQLITE_READONLY_ROLLBACK error code indicates that a database cannot be opened because it has a hot journal that needs to be rolled back but cannot because the database is readonly.

() SQLITE_IOERR_WRITE

The SQLITE_IOERR_WRITE error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to write into a file on disk. This error might result from a hardware malfunction or because a filesystem came unmounted while the file was open. This error should not occur if the filesystem is full as there is a separate error code (SQLITE_FULL) for that purpose.

() SQLITE_CORRUPT_INDEX

The SQLITE_CORRUPT_INDEX result code means that SQLite detected an entry is or was 20 01 error from an index. This is a special case of the SQLITE_CORRUPT error code that suggests that the problem might be resolved by running the REINDEX command, assuming no other problems exist 20 01 error in the database file.

() SQLITE_CANTOPEN_FULLPATH

The SQLITE_CANTOPEN_FULLPATH error code is an extended error code for SQLITE_CANTOPEN indicating that a file open operation failed because the operating system was unable to convert the filename into a full pathname, 20 01 error.

() SQLITE_CONSTRAINT_FOREIGNKEY

The SQLITE_CONSTRAINT_FOREIGNKEY error code is an extended error code for SQLITE_CONSTRAINT indicating that a foreign key constraint failed.

() SQLITE_READONLY_DBMOVED

The SQLITE_READONLY_DBMOVED error code is an extended error code for SQLITE_READONLY. The SQLITE_READONLY_DBMOVED error code indicates that a database cannot be modified because the database file has been moved since it was opened, and so any attempt to modify the database might result in database corruption if the processes crashes because the rollback journal would not be correctly named.

() SQLITE_IOERR_FSYNC

The SQLITE_IOERR_FSYNC error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to flush previously written content out of OS and/or disk-control buffers and into persistent storage. In other words, this code indicates a problem with the fsync() system call in unix or the FlushFileBuffers() system call in windows.

() SQLITE_CANTOPEN_CONVPATH

The SQLITE_CANTOPEN_CONVPATH error code is an extended error code for SQLITE_CANTOPEN used only by Cygwin VFS and indicating that the cygwin_conv_path() system call failed while trying to open a file. See also: SQLITE_IOERR_CONVPATH

() SQLITE_CONSTRAINT_FUNCTION

The SQLITE_CONSTRAINT_FUNCTION error code is not currently used by the SQLite core. However, this error code is available for use by extension functions.

() SQLITE_READONLY_CANTINIT

The SQLITE_READONLY_CANTINIT result code originates in the xShmMap method of a VFS to indicate that the shared memory region used by WAL mode exists buts its content is unreliable and unusable by the current process since the current process does not have write permission on the shared memory region, 20 01 error. (The shared memory region for WAL mode is normally a file with a "-wal" suffix that is mmapped into the process space. If the current process does not have write permission on that file, then it cannot write into shared memory.)

Higher level logic within SQLite will normally intercept the error code and create a temporary in-memory shared memory region so that the current process can at least read the content of the database. This result code should not reach the application interface layer.

() SQLITE_IOERR_DIR_FSYNC

The SQLITE_IOERR_DIR_FSYNC error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to invoke fsync() on a directory. The unix VFS attempts to fsync() directories after creating or deleting certain files to ensure that those files will still appear in the filesystem following a power loss or system crash. This error code indicates a problem attempting to perform that fsync().

() SQLITE_CANTOPEN_DIRTYWAL

The SQLITE_CANTOPEN_DIRTYWAL result code is not used at this time.

() SQLITE_CONSTRAINT_NOTNULL

The SQLITE_CONSTRAINT_NOTNULL error code is an extended error code for SQLITE_CONSTRAINT indicating that a NOT NULL constraint failed.

() SQLITE_READONLY_DIRECTORY

The SQLITE_READONLY_DIRECTORY result code indicates that the database is read-only because process does not have permission to create a journal file in the same directory as the database and the creation of a journal file is a prerequisite for writing.

() SQLITE_IOERR_TRUNCATE

The SQLITE_IOERR_TRUNCATE error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to truncate a file to a smaller size.

() SQLITE_CANTOPEN_SYMLINK

The SQLITE_CANTOPEN_SYMLINK result code is returned by the sqlite3_open() interface and its siblings when the SQLITE_OPEN_NOFOLLOW flag is used and the database file is a symbolic link.

() SQLITE_CONSTRAINT_PRIMARYKEY

The SQLITE_CONSTRAINT_PRIMARYKEY error code is an extended error code for SQLITE_CONSTRAINT indicating that a PRIMARY KEY constraint failed.

() SQLITE_IOERR_FSTAT

The SQLITE_IOERR_FSTAT error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to invoke fstat() (or the equivalent) on a file in order to determine information such as the file size or access permissions.

() SQLITE_CONSTRAINT_TRIGGER

The SQLITE_CONSTRAINT_TRIGGER error code is an extended error code for SQLITE_CONSTRAINT indicating that a RAISE function within a trigger fired, causing the SQL statement to abort.

() SQLITE_IOERR_UNLOCK

The SQLITE_IOERR_UNLOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error within xUnlock method on the sqlite3_io_methods object.

() SQLITE_CONSTRAINT_UNIQUE

The SQLITE_CONSTRAINT_UNIQUE error code is an extended error code for SQLITE_CONSTRAINT indicating that a UNIQUE constraint failed.

() SQLITE_IOERR_RDLOCK

The SQLITE_IOERR_UNLOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error within xLock method on the sqlite3_io_methods object while trying to obtain a read lock.

() SQLITE_CONSTRAINT_VTAB

The SQLITE_CONSTRAINT_VTAB error code is not currently used by the SQLite core. However, this error code is available for use by application-defined virtual tables.

() SQLITE_IOERR_DELETE

The SQLITE_IOERR_UNLOCK error code 20 01 error an extended error code for SQLITE_IOERR indicating an I/O error within xDelete method on the sqlite3_vfs object.

() SQLITE_CONSTRAINT_ROWID

The SQLITE_CONSTRAINT_ROWID error code is an extended error code for SQLITE_CONSTRAINT indicating that a rowid is not unique.

() SQLITE_IOERR_BLOCKED

The SQLITE_IOERR_BLOCKED error code is no longer used.

() SQLITE_CONSTRAINT_PINNED

The SQLITE_CONSTRAINT_PINNED error code is an extended error code for SQLITE_CONSTRAINT indicating that an UPDATE trigger attempted do delete the row that was being updated in the middle of the update, 20 01 error.

() SQLITE_IOERR_NOMEM

The SQLITE_IOERR_NOMEM error code is sometimes returned by the VFS layer to indicate that an operation 20 01 error not be completed due to the inability to allocate sufficient memory. This error code is normally converted into SQLITE_NOMEM by the higher layers of SQLite before being returned to the application.

() SQLITE_CONSTRAINT_DATATYPE

The SQLITE_CONSTRAINT_DATATYPE error code is an extended error code for SQLITE_CONSTRAINT indicating that an insert or update attempted to store a value inconsistent with the 20 01 error declared type in a table defined as STRICT.

() SQLITE_IOERR_ACCESS

The SQLITE_IOERR_ACCESS error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xAccess method on the sqlite3_vfs object.

() SQLITE_IOERR_CHECKRESERVEDLOCK

The SQLITE_IOERR_CHECKRESERVEDLOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xCheckReservedLock method on the sqlite3_io_methods object, 20 01 error.

() SQLITE_IOERR_LOCK

The SQLITE_IOERR_LOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error 20 01 error the advisory file locking logic. Usually an SQLITE_IOERR_LOCK error indicates a problem obtaining a PENDING lock, 20 01 error. However it can also indicate miscellaneous locking errors on some of the specialized VFSes used on Macs.

() SQLITE_IOERR_CLOSE

The SQLITE_IOERR_ACCESS error code is an extended error code for SQLITE_IOERR indicating an I/O 20 01 error within the xClose method on the sqlite3_io_methods object.

() SQLITE_IOERR_DIR_CLOSE

The SQLITE_IOERR_DIR_CLOSE error code is no longer used.

() SQLITE_IOERR_SHMOPEN

The SQLITE_IOERR_SHMOPEN error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xShmMap method on the sqlite3_io_methods object while trying to open a new shared memory segment.

() SQLITE_IOERR_SHMSIZE

The SQLITE_IOERR_SHMSIZE error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xShmMap method on the sqlite3_io_methods object while trying to enlarge a "shm" file as part of WAL mode transaction processing. This error may indicate that the underlying filesystem volume is out of space.

() SQLITE_IOERR_SHMLOCK

The SQLITE_IOERR_SHMLOCK error code is no longer used.

() SQLITE_IOERR_SHMMAP

The SQLITE_IOERR_SHMMAP error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xShmMap method on the sqlite3_io_methods object while trying to map a shared memory segment into the process address space.

() SQLITE_IOERR_SEEK

The SQLITE_IOERR_SEEK error code is an extended error code for SQLITE_IOERR 20 01 error an I/O error within the xRead or xWrite methods on the sqlite3_io_methods object while trying to seek a file descriptor to the beginning point of the file where the read or write is to occur.

() SQLITE_IOERR_DELETE_NOENT

The SQLITE_IOERR_DELETE_NOENT 20 01 error code is an extended error code for SQLITE_IOERR indicating that the xDelete method on the sqlite3_vfs object failed 20 01 error the file being deleted does not exist.

() SQLITE_IOERR_MMAP

20 01 error SQLITE_IOERR_MMAP error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xFetch or xUnfetch methods on the sqlite3_io_methods object while trying to map or unmap part of the database file into the process address space, 20 01 error.

() SQLITE_IOERR_GETTEMPPATH

The SQLITE_IOERR_GETTEMPPATH error code is an extended error code for SQLITE_IOERR indicating that the VFS is unable to determine a suitable directory in which to place temporary files.

() SQLITE_IOERR_CONVPATH

The SQLITE_IOERR_CONVPATH error code is an extended error code for SQLITE_IOERR used only by Cygwin VFS and indicating that the cygwin_conv_path() system call failed, 20 01 error. See also: SQLITE_CANTOPEN_CONVPATH

() SQLITE_IOERR_VNODE

The SQLITE_IOERR_VNODE error code is a code reserved for use by extensions, 20 01 error. It is not used by the 20 01 error core.

() SQLITE_IOERR_AUTH

The SQLITE_IOERR_AUTH error code is a code reserved for use by extensions. It is not used by the SQLite core.

() SQLITE_IOERR_BEGIN_ATOMIC

The SQLITE_IOERR_BEGIN_ATOMIC error code indicates that the underlying operating system reported and error on the SQLITE_FCNTL_BEGIN_ATOMIC_WRITE file-control. This only comes up when SQLITE_ENABLE_ATOMIC_WRITE is enabled and the database is hosted on a filesystem that supports atomic writes, 20 01 error.

() SQLITE_IOERR_COMMIT_ATOMIC

The SQLITE_IOERR_COMMIT_ATOMIC error code indicates that the underlying operating system reported and error on the SQLITE_FCNTL_COMMIT_ATOMIC_WRITE file-control. This only comes up when SQLITE_ENABLE_ATOMIC_WRITE is enabled and the database is hosted on a filesystem that supports atomic writes.

() SQLITE_IOERR_ROLLBACK_ATOMIC

The SQLITE_IOERR_ROLLBACK_ATOMIC error code indicates that the underlying operating system reported and error on the SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE file-control. This only comes up when SQLITE_ENABLE_ATOMIC_WRITE is enabled and the database is hosted on a filesystem that supports atomic writes.

() SQLITE_IOERR_DATA

The SQLITE_IOERR_DATA error code is an extended error code for SQLITE_IOERR used only by checksum VFS shim to indicate that the checksum on a page of the database file is incorrect.

() SQLITE_IOERR_CORRUPTFS

The SQLITE_IOERR_CORRUPTFS error code is an extended error code for SQLITE_IOERR used only by a VFS to indicate that a seek or read failure was due to the request not falling within the file's boundary rather than an ordinary device failure. This often indicates a corrupt filesystem.

Symptoms

Assume that you have an Always On Availability Group (AG) in an instance of Microsoft SQL Server or  When you back up a secondary replica that is running under asynchronous-commit mode, the backup operation may fail occasionally. Additionally, 20 01 error, you may receive the following error message:

Error:Severity: 20, State: 1.

The log scan number (nnn:nnn:nnn) passed to log scan in database 'dbname' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem 20 01 error in a failure during startup.

Resolution

This problem is fixed in the following updates for SQL Server:

Cumulative Update 13 for SQL Server

Cumulative Update 20 01 error for SQL Server Service Pack 2

Cumulative Update 11 for SQL Server Service Pack 1

20 01 error SQL Server builds

Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install 20 01 error latest build for your version of SQL Server:

Latest cumulative update for SQL Server

The latest build for SQL Server

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology Microsoft uses to describe software updates.

20 01 error - thanks for

iOS update and restore errors

Learn how to solve iOS update and restore errors.

Try these steps first

  1. On a Mac with macOS Catalina  or later, make sure your Mac is up to date. If you have a Mac with macOS Mojave or earlier, or a PC, make sure you have the latest version of iTunes.
  2. If your device couldn't be restored and you get a message that "an unknown error occurred [error number]," use these steps. 

If you still see the error, try the steps below.

Choose your error number or message

To learn what to do, choose your error:

  • 1, 2, 3, 4, 6, 9, 10, 11, 12, 13, 14, 16, 17 
  • 20, 21, 23, 26, 27, 28, 29, 34, 35, 36, 37,
    40, 53, 56
  • , , , , , 
  • , , , , , , , 
    –, , ,
  • , , , , 
  • , , , , , , 
  • , , ,

Update the software on your Mac or PC

If you see error 10, your iOS device might have a newer version of iOS than is supported by your computer. You'll need to update the software on your Mac or iTunes on Windows before you can update or restore your iOS device.

macOS and later:

  1. Disconnect and then reconnect your iOS device to your computer. You might need to unlock your iOS device before it is recognized by your Mac.
  2. When you see a message that says a software update is required to connect to your iOS device, click Install to download and install the software so your Mac can update or restore your iOS device.

Windows: Update to latest version of iTunes.

If you continue to see error 10, or you don't see a dialog asking you to update the software on your mac, contact Apple Support.

Make sure that your device can communicate with Apple servers

If you see error , your computer is downloading necessary software. Wait for the download to finish, then try again.

If you see one of the errors below, your computer might not be able to connect to Apple servers or your iPhone, iPad, or iPod touch:

  • 17, , , , , , , , , , ,
  • "There was a problem downloading the software."
  • "The device isn't eligible for the requested build."

Here's what to check:

  1. Make sure that your computer can communicate with the Apple software-update servers.
  2. Check your third-party security software.

If you see error , your computer is unable to update your device because it's passcode locked and the device wasn't unlocked for the update or restore. Unlock your device and try again. Learn what to do if you forgot your passcode.

If you still see an error, contact Apple Support.

Cellular Update Failed or Apple Pay Not Available alert

If you see either "Cellular Update Failed" or "Apple Pay requires an Update on this iPhone" alert after an update, learn what to do.

Check your security software

Check your USB connections

If you see error , , or , use these steps.

If you see one of the errors below, check your USB connection, USB cable, USB port, or computer:

  • 13, , , , , , , –
  • , , , , ,
  • An error that includes "invalid response"

Here's what to check. Try again after each step:

  1. Use the USB cable that came with your device. If you don't have it, try a different Apple USB cable. 
  2. Switch to a different USB port on your computer. Don't plug into your keyboard.
  3. Switch to a USB port on a different computer.
  4. If you still see the error, check for other USB issues, check your third-party security software, then check your hardware.

If you still see an error, contact Apple Support.

Check your hardware

If you see error 53, use these steps.

If you see one of the errors below, you might have a hardware issue:

  • 1, 3, 11, 12, 13, 16
  • 20, 21, 23, 26, 27, 28, 29, 34, 35, 36, 37, 40, 56
  • , , , , , ,

Here's what to check. Try again after each step:

  1. If iTunes is already open, quit and reopen it.
  2. Check your third-party security software.
  3. Make sure that your USB cable, computer, and network are reliable. Then try twice more to restore your device.
  4. Check for outdated or modified software. 

If you still see the error, contact Apple Support.

Published Date: 

1. Result Codes versus Error Codes

Overview

Many of the routines in the SQLite C-language Interface return numeric result codes indicating either success or failure, and in the event of a failure, providing some idea of the cause of the failure. This document strives to explain what each of those numeric result codes means.

"Error codes" are a subset of "result codes" that indicate that something has gone wrong. There are only a few non-error result codes: SQLITE_OK, SQLITE_ROW, and SQLITE_DONE. The term "error code" means any result code other than these three.

Result codes are signed bit integers. The least significant 8 bits of the result code define a broad category and are called the "primary result code". More significant bits provide more detailed information about the error and are called the "extended result code"

Note that the primary result code is always a part of the extended result code. Given a full bit extended result code, the application can always find the corresponding primary result code merely by extracting the least significant 8 bits of the extended result code.

All extended result codes are also error codes. Hence the terms "extended result code" and "extended error code" are interchangeable.

For historic compatibility, the C-language interfaces return primary result codes by default. The extended result code for the most recent error can be retrieved using the sqlite3_extended_errcode() interface. The sqlite3_extended_result_codes() interface can be used to put a database connection into a mode where it returns the extended result codes instead of the primary result codes.

All result codes are integers. Symbolic names for all result codes are created using "#define" macros in the sqlite3.h header file. There are separate sections in the sqlite3.h header file for the result code definitions and the extended result code definitions.

Primary result code symbolic names are of the form "SQLITE_XXXXXX" where XXXXXX is a sequence of uppercase alphabetic characters. Extended result code names are of the form "SQLITE_XXXXXX_YYYYYYY" where the XXXXXX part is the corresponding primary result code and the YYYYYYY is an extension that further classifies the result code.

The names and numeric values for existing result codes are fixed and unchanging. However, new result codes, and especially new extended result codes, might appear in future releases of SQLite.

The 31 result codes are defined in sqlite3.h and are listed in alphabetical order below:

The 74 extended result codes are defined in sqlite3.h and are listed in alphabetical order below:

The meanings for all result code values are shown below, in numeric order.

(0) SQLITE_OK

The SQLITE_OK result code means that the operation was successful and that there were no errors. Most other result codes indicate an error.

(1) SQLITE_ERROR

The SQLITE_ERROR result code is a generic error code that is used when no other more specific error code is available.

(2) SQLITE_INTERNAL

The SQLITE_INTERNAL result code indicates an internal malfunction. In a working version of SQLite, an application should never see this result code. If application does encounter this result code, it shows that there is a bug in the database engine.

SQLite does not currently generate this result code. However, application-defined SQL functions or virtual tables, or VFSes, or other extensions might cause this result code to be returned.

(3) SQLITE_PERM

The SQLITE_PERM result code indicates that the requested access mode for a newly created database could not be provided.

(4) SQLITE_ABORT

The SQLITE_ABORT result code indicates that an operation was aborted prior to completion, usually be application request. See also: SQLITE_INTERRUPT.

If the callback function to sqlite3_exec() returns non-zero, then sqlite3_exec() will return SQLITE_ABORT.

If a ROLLBACK operation occurs on the same database connection as a pending read or write, then the pending read or write may fail with an SQLITE_ABORT or SQLITE_ABORT_ROLLBACK error.

In addition to being a result code, the SQLITE_ABORT value is also used as a conflict resolution mode returned from the sqlite3_vtab_on_conflict() interface.

(5) SQLITE_BUSY

The SQLITE_BUSY result code indicates that the database file could not be written (or in some cases read) because of concurrent activity by some other database connection, usually a database connection in a separate process.

For example, if process A is in the middle of a large write transaction and at the same time process B attempts to start a new write transaction, process B will get back an SQLITE_BUSY result because SQLite only supports one writer at a time. Process B will need to wait for process A to finish its transaction before starting a new transaction. The sqlite3_busy_timeout() and sqlite3_busy_handler() interfaces and the busy_timeout pragma are available to process B to help it deal with SQLITE_BUSY errors.

An SQLITE_BUSY error can occur at any point in a transaction: when the transaction is first started, during any write or update operations, or when the transaction commits. To avoid encountering SQLITE_BUSY errors in the middle of a transaction, the application can use BEGIN IMMEDIATE instead of just BEGIN to start a transaction. The BEGIN IMMEDIATE command might itself return SQLITE_BUSY, but if it succeeds, then SQLite guarantees that no subsequent operations on the same database through the next COMMIT will return SQLITE_BUSY.

See also: SQLITE_BUSY_RECOVERY and SQLITE_BUSY_SNAPSHOT.

The SQLITE_BUSY result code differs from SQLITE_LOCKED in that SQLITE_BUSY indicates a conflict with a separate database connection, probably in a separate process, whereas SQLITE_LOCKED indicates a conflict within the same database connection (or sometimes a database connection with a shared cache).

(6) SQLITE_LOCKED

The SQLITE_LOCKED result code indicates that a write operation could not continue because of a conflict within the same database connection or a conflict with a different database connection that uses a shared cache.

For example, a DROP TABLE statement cannot be run while another thread is reading from that table on the same database connection because dropping the table would delete the table out from under the concurrent reader.

The SQLITE_LOCKED result code differs from SQLITE_BUSY in that SQLITE_LOCKED indicates a conflict on the same database connection (or on a connection with a shared cache) whereas SQLITE_BUSY indicates a conflict with a different database connection, probably in a different process.

(7) SQLITE_NOMEM

The SQLITE_NOMEM result code indicates that SQLite was unable to allocate all the memory it needed to complete the operation. In other words, an internal call to sqlite3_malloc() or sqlite3_realloc() has failed in a case where the memory being allocated was required in order to continue the operation.

(8) SQLITE_READONLY

The SQLITE_READONLY result code is returned when an attempt is made to alter some data for which the current database connection does not have write permission.

(9) SQLITE_INTERRUPT

The SQLITE_INTERRUPT result code indicates that an operation was interrupted by the sqlite3_interrupt() interface. See also: SQLITE_ABORT

(10) SQLITE_IOERR

The SQLITE_IOERR result code says that the operation could not finish because the operating system reported an I/O error.

A full disk drive will normally give an SQLITE_FULL error rather than an SQLITE_IOERR error.

There are many different extended result codes for I/O errors that identify the specific I/O operation that failed.

(11) SQLITE_CORRUPT

The SQLITE_CORRUPT result code indicates that the database file has been corrupted. See the How To Corrupt Your Database Files for further discussion on how corruption can occur.

(12) SQLITE_NOTFOUND

The SQLITE_NOTFOUND result code is exposed in three ways:

  1. SQLITE_NOTFOUND can be returned by the sqlite3_file_control() interface to indicate that the file control opcode passed as the third argument was not recognized by the underlying VFS.

  2. SQLITE_NOTFOUND can also be returned by the xSetSystemCall() method of an sqlite3_vfs object.

  3. SQLITE_NOTFOUND an be returned by sqlite3_vtab_rhs_value() to indicate that the right-hand operand of a constraint is not available to the xBestIndex method that made the call.

The SQLITE_NOTFOUND result code is also used internally by the SQLite implementation, but those internal uses are not exposed to the application.

(13) SQLITE_FULL

The SQLITE_FULL result code indicates that a write could not complete because the disk is full. Note that this error can occur when trying to write information into the main database file, or it can also occur when writing into temporary disk files.

Sometimes applications encounter this error even though there is an abundance of primary disk space because the error occurs when writing into temporary disk files on a system where temporary files are stored on a separate partition with much less space that the primary disk.

(14) SQLITE_CANTOPEN

The SQLITE_CANTOPEN result code indicates that SQLite was unable to open a file. The file in question might be a primary database file or one of several temporary disk files.

(15) SQLITE_PROTOCOL

The SQLITE_PROTOCOL result code indicates a problem with the file locking protocol used by SQLite. The SQLITE_PROTOCOL error is currently only returned when using WAL mode and attempting to start a new transaction. There is a race condition that can occur when two separate database connections both try to start a transaction at the same time in WAL mode. The loser of the race backs off and tries again, after a brief delay. If the same connection loses the locking race dozens of times over a span of multiple seconds, it will eventually give up and return SQLITE_PROTOCOL. The SQLITE_PROTOCOL error should appear in practice very, very rarely, and only when there are many separate processes all competing intensely to write to the same database.

(16) SQLITE_EMPTY

The SQLITE_EMPTY result code is not currently used.

(17) SQLITE_SCHEMA

The SQLITE_SCHEMA result code indicates that the database schema has changed. This result code can be returned from sqlite3_step() for a prepared statement that was generated using sqlite3_prepare() or sqlite3_prepare16(). If the database schema was changed by some other process in between the time that the statement was prepared and the time the statement was run, this error can result.

If a prepared statement is generated from sqlite3_prepare_v2() then the statement is automatically re-prepared if the schema changes, up to SQLITE_MAX_SCHEMA_RETRY times (default: 50). The sqlite3_step() interface will only return SQLITE_SCHEMA back to the application if the failure persists after these many retries.

(18) SQLITE_TOOBIG

The SQLITE_TOOBIG error code indicates that a string or BLOB was too large. The default maximum length of a string or BLOB in SQLite is 1,,, bytes. This maximum length can be changed at compile-time using the SQLITE_MAX_LENGTH compile-time option, or at run-time using the sqlite3_limit(db,SQLITE_LIMIT_LENGTH,) interface. The SQLITE_TOOBIG error results when SQLite encounters a string or BLOB that exceeds the compile-time or run-time limit.

The SQLITE_TOOBIG error code can also result when an oversized SQL statement is passed into one of the sqlite3_prepare_v2() interfaces. The maximum length of an SQL statement defaults to a much smaller value of 1,,, bytes. The maximum SQL statement length can be set at compile-time using SQLITE_MAX_SQL_LENGTH or at run-time using sqlite3_limit(db,SQLITE_LIMIT_SQL_LENGTH,).

(19) SQLITE_CONSTRAINT

The SQLITE_CONSTRAINT error code means that an SQL constraint violation occurred while trying to process an SQL statement. Additional information about the failed constraint can be found by consulting the accompanying error message (returned via sqlite3_errmsg() or sqlite3_errmsg16()) or by looking at the extended error code.

The SQLITE_CONSTRAINT code can also be used as the return value from the xBestIndex() method of a virtual table implementation. When xBestIndex() returns SQLITE_CONSTRAINT, that indicates that the particular combination of inputs submitted to xBestIndex() cannot result in a usable query plan and should not be given further consideration.

(20) SQLITE_MISMATCH

The SQLITE_MISMATCH error code indicates a datatype mismatch.

SQLite is normally very forgiving about mismatches between the type of a value and the declared type of the container in which that value is to be stored. For example, SQLite allows the application to store a large BLOB in a column with a declared type of BOOLEAN. But in a few cases, SQLite is strict about types. The SQLITE_MISMATCH error is returned in those few cases when the types do not match.

The rowid of a table must be an integer. Attempt to set the rowid to anything other than an integer (or a NULL which will be automatically converted into the next available integer rowid) results in an SQLITE_MISMATCH error.

(21) SQLITE_MISUSE

The SQLITE_MISUSE return code might be returned if the application uses any SQLite interface in a way that is undefined or unsupported. For example, using a prepared statement after that prepared statement has been finalized might result in an SQLITE_MISUSE error.

SQLite tries to detect misuse and report the misuse using this result code. However, there is no guarantee that the detection of misuse will be successful. Misuse detection is probabilistic. Applications should never depend on an SQLITE_MISUSE return value.

If SQLite ever returns SQLITE_MISUSE from any interface, that means that the application is incorrectly coded and needs to be fixed. Do not ship an application that sometimes returns SQLITE_MISUSE from a standard SQLite interface because that application contains potentially serious bugs.

(22) SQLITE_NOLFS

The SQLITE_NOLFS error can be returned on systems that do not support large files when the database grows to be larger than what the filesystem can handle. "NOLFS" stands for "NO Large File Support".

(23) SQLITE_AUTH

The SQLITE_AUTH error is returned when the authorizer callback indicates that an SQL statement being prepared is not authorized.

(24) SQLITE_FORMAT

The SQLITE_FORMAT error code is not currently used by SQLite.

(25) SQLITE_RANGE

The SQLITE_RANGE error indices that the parameter number argument to one of the sqlite3_bind routines or the column number in one of the sqlite3_column routines is out of range.

(26) SQLITE_NOTADB

When attempting to open a file, the SQLITE_NOTADB error indicates that the file being opened does not appear to be an SQLite database file.

(27) SQLITE_NOTICE

The SQLITE_NOTICE result code is not returned by any C/C++ interface. However, SQLITE_NOTICE (or rather one of its extended error codes) is sometimes used as the first argument in an sqlite3_log() callback to indicate that an unusual operation is taking place.

(28) SQLITE_WARNING

The SQLITE_WARNING result code is not returned by any C/C++ interface. However, SQLITE_WARNING (or rather one of its extended error codes) is sometimes used as the first argument in an sqlite3_log() callback to indicate that an unusual and possibly ill-advised operation is taking place.

() SQLITE_ROW

The SQLITE_ROW result code returned by sqlite3_step() indicates that another row of output is available.

() SQLITE_DONE

The SQLITE_DONE result code indicates that an operation has completed. The SQLITE_DONE result code is most commonly seen as a return value from sqlite3_step() indicating that the SQL statement has run to completion. But SQLITE_DONE can also be returned by other multi-step interfaces such as sqlite3_backup_step().

() SQLITE_OK_LOAD_PERMANENTLY

The sqlite3_load_extension() interface loads an extension into a single database connection. The default behavior is for that extension to be automatically unloaded when the database connection closes. However, if the extension entry point returns SQLITE_OK_LOAD_PERMANENTLY instead of SQLITE_OK, then the extension remains loaded into the process address space after the database connection closes. In other words, the xDlClose methods of the sqlite3_vfs object is not called for the extension when the database connection closes.

The SQLITE_OK_LOAD_PERMANENTLY return code is useful to loadable extensions that register new VFSes, for example.

() SQLITE_ERROR_MISSING_COLLSEQ

The SQLITE_ERROR_MISSING_COLLSEQ result code means that an SQL statement could not be prepared because a collating sequence named in that SQL statement could not be located.

Sometimes when this error code is encountered, the sqlite3_prepare_v2() routine will convert the error into SQLITE_ERROR_RETRY and try again to prepare the SQL statement using a different query plan that does not require the use of the unknown collating sequence.

() SQLITE_BUSY_RECOVERY

The SQLITE_BUSY_RECOVERY error code is an extended error code for SQLITE_BUSY that indicates that an operation could not continue because another process is busy recovering a WAL mode database file following a crash. The SQLITE_BUSY_RECOVERY error code only occurs on WAL mode databases.

() SQLITE_LOCKED_SHAREDCACHE

The SQLITE_LOCKED_SHAREDCACHE result code indicates that access to an SQLite data record is blocked by another database connection that is using the same record in shared cache mode. When two or more database connections share the same cache and one of the connections is in the middle of modifying a record in that cache, then other connections are blocked from accessing that data while the modifications are on-going in order to prevent the readers from seeing a corrupt or partially completed change.

() SQLITE_READONLY_RECOVERY

The SQLITE_READONLY_RECOVERY error code is an extended error code for SQLITE_READONLY. The SQLITE_READONLY_RECOVERY error code indicates that a WAL mode database cannot be opened because the database file needs to be recovered and recovery requires write access but only read access is available.

() SQLITE_IOERR_READ

The SQLITE_IOERR_READ error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to read from a file on disk. This error might result from a hardware malfunction or because a filesystem came unmounted while the file was open.

() SQLITE_CORRUPT_VTAB

The SQLITE_CORRUPT_VTAB error code is an extended error code for SQLITE_CORRUPT used by virtual tables. A virtual table might return SQLITE_CORRUPT_VTAB to indicate that content in the virtual table is corrupt.

() SQLITE_CANTOPEN_NOTEMPDIR

The SQLITE_CANTOPEN_NOTEMPDIR error code is no longer used.

() SQLITE_CONSTRAINT_CHECK

The SQLITE_CONSTRAINT_CHECK error code is an extended error code for SQLITE_CONSTRAINT indicating that a CHECK constraint failed.

() SQLITE_AUTH_USER

The SQLITE_AUTH_USER error code is an extended error code for SQLITE_AUTH indicating that an operation was attempted on a database for which the logged in user lacks sufficient authorization.

() SQLITE_NOTICE_RECOVER_WAL

The SQLITE_NOTICE_RECOVER_WAL result code is passed to the callback of sqlite3_log() when a WAL mode database file is recovered.

() SQLITE_WARNING_AUTOINDEX

The SQLITE_WARNING_AUTOINDEX result code is passed to the callback of sqlite3_log() whenever automatic indexing is used. This can serve as a warning to application designers that the database might benefit from additional indexes.

() SQLITE_ERROR_RETRY

The SQLITE_ERROR_RETRY is used internally to provoke sqlite3_prepare_v2() (or one of its sibling routines for creating prepared statements) to try again to prepare a statement that failed with an error on the previous attempt.

() SQLITE_ABORT_ROLLBACK

The SQLITE_ABORT_ROLLBACK error code is an extended error code for SQLITE_ABORT indicating that an SQL statement aborted because the transaction that was active when the SQL statement first started was rolled back. Pending write operations always fail with this error when a rollback occurs. A ROLLBACK will cause a pending read operation to fail only if the schema was changed within the transaction being rolled back.

() SQLITE_BUSY_SNAPSHOT

The SQLITE_BUSY_SNAPSHOT error code is an extended error code for SQLITE_BUSY that occurs on WAL mode databases when a database connection tries to promote a read transaction into a write transaction but finds that another database connection has already written to the database and thus invalidated prior reads.

The following scenario illustrates how an SQLITE_BUSY_SNAPSHOT error might arise:

  1. Process A starts a read transaction on the database and does one or more SELECT statement. Process A keeps the transaction open.
  2. Process B updates the database, changing values previous read by process A.
  3. Process A now tries to write to the database. But process A's view of the database content is now obsolete because process B has modified the database file after process A read from it. Hence process A gets an SQLITE_BUSY_SNAPSHOT error.

() SQLITE_LOCKED_VTAB

The SQLITE_LOCKED_VTAB result code is not used by the SQLite core, but it is available for use by extensions. Virtual table implementations can return this result code to indicate that they cannot complete the current operation because of locks held by other threads or processes.

The R-Tree extension returns this result code when an attempt is made to update the R-Tree while another prepared statement is actively reading the R-Tree. The update cannot proceed because any change to an R-Tree might involve reshuffling and rebalancing of nodes, which would disrupt read cursors, causing some rows to be repeated and other rows to be omitted.

() SQLITE_READONLY_CANTLOCK

The SQLITE_READONLY_CANTLOCK error code is an extended error code for SQLITE_READONLY. The SQLITE_READONLY_CANTLOCK error code indicates that SQLite is unable to obtain a read lock on a WAL mode database because the shared-memory file associated with that database is read-only.

() SQLITE_IOERR_SHORT_READ

The SQLITE_IOERR_SHORT_READ error code is an extended error code for SQLITE_IOERR indicating that a read attempt in the VFS layer was unable to obtain as many bytes as was requested. This might be due to a truncated file.

() SQLITE_CORRUPT_SEQUENCE

The SQLITE_CORRUPT_SEQUENCE result code means that the schema of the sqlite_sequence table is corrupt. The sqlite_sequence table is used to help implement the AUTOINCREMENT feature. The sqlite_sequence table should have the following format:

CREATE TABLE sqlite_sequence(name,seq);

If SQLite discovers that the sqlite_sequence table has any other format, it returns the SQLITE_CORRUPT_SEQUENCE error.

() SQLITE_CANTOPEN_ISDIR

The SQLITE_CANTOPEN_ISDIR error code is an extended error code for SQLITE_CANTOPEN indicating that a file open operation failed because the file is really a directory.

() SQLITE_CONSTRAINT_COMMITHOOK

The SQLITE_CONSTRAINT_COMMITHOOK error code is an extended error code for SQLITE_CONSTRAINT indicating that a commit hook callback returned non-zero that thus caused the SQL statement to be rolled back.

() SQLITE_NOTICE_RECOVER_ROLLBACK

The SQLITE_NOTICE_RECOVER_ROLLBACK result code is passed to the callback of sqlite3_log() when a hot journal is rolled back.

() SQLITE_ERROR_SNAPSHOT

The SQLITE_ERROR_SNAPSHOT result code might be returned when attempting to start a read transaction on an historical version of the database by using the sqlite3_snapshot_open() interface. If the historical snapshot is no longer available, then the read transaction will fail with the SQLITE_ERROR_SNAPSHOT. This error code is only possible if SQLite is compiled with -DSQLITE_ENABLE_SNAPSHOT.

() SQLITE_BUSY_TIMEOUT

The SQLITE_BUSY_TIMEOUT error code indicates that a blocking Posix advisory file lock request in the VFS layer failed due to a timeout. Blocking Posix advisory locks are only available as a proprietary SQLite extension and even then are only supported if SQLite is compiled with the SQLITE_EANBLE_SETLK_TIMEOUT compile-time option.

() SQLITE_READONLY_ROLLBACK

The SQLITE_READONLY_ROLLBACK error code is an extended error code for SQLITE_READONLY. The SQLITE_READONLY_ROLLBACK error code indicates that a database cannot be opened because it has a hot journal that needs to be rolled back but cannot because the database is readonly.

() SQLITE_IOERR_WRITE

The SQLITE_IOERR_WRITE error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to write into a file on disk. This error might result from a hardware malfunction or because a filesystem came unmounted while the file was open. This error should not occur if the filesystem is full as there is a separate error code (SQLITE_FULL) for that purpose.

() SQLITE_CORRUPT_INDEX

The SQLITE_CORRUPT_INDEX result code means that SQLite detected an entry is or was missing from an index. This is a special case of the SQLITE_CORRUPT error code that suggests that the problem might be resolved by running the REINDEX command, assuming no other problems exist elsewhere in the database file.

() SQLITE_CANTOPEN_FULLPATH

The SQLITE_CANTOPEN_FULLPATH error code is an extended error code for SQLITE_CANTOPEN indicating that a file open operation failed because the operating system was unable to convert the filename into a full pathname.

() SQLITE_CONSTRAINT_FOREIGNKEY

The SQLITE_CONSTRAINT_FOREIGNKEY error code is an extended error code for SQLITE_CONSTRAINT indicating that a foreign key constraint failed.

() SQLITE_READONLY_DBMOVED

The SQLITE_READONLY_DBMOVED error code is an extended error code for SQLITE_READONLY. The SQLITE_READONLY_DBMOVED error code indicates that a database cannot be modified because the database file has been moved since it was opened, and so any attempt to modify the database might result in database corruption if the processes crashes because the rollback journal would not be correctly named.

() SQLITE_IOERR_FSYNC

The SQLITE_IOERR_FSYNC error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to flush previously written content out of OS and/or disk-control buffers and into persistent storage. In other words, this code indicates a problem with the fsync() system call in unix or the FlushFileBuffers() system call in windows.

() SQLITE_CANTOPEN_CONVPATH

The SQLITE_CANTOPEN_CONVPATH error code is an extended error code for SQLITE_CANTOPEN used only by Cygwin VFS and indicating that the cygwin_conv_path() system call failed while trying to open a file. See also: SQLITE_IOERR_CONVPATH

() SQLITE_CONSTRAINT_FUNCTION

The SQLITE_CONSTRAINT_FUNCTION error code is not currently used by the SQLite core. However, this error code is available for use by extension functions.

() SQLITE_READONLY_CANTINIT

The SQLITE_READONLY_CANTINIT result code originates in the xShmMap method of a VFS to indicate that the shared memory region used by WAL mode exists buts its content is unreliable and unusable by the current process since the current process does not have write permission on the shared memory region. (The shared memory region for WAL mode is normally a file with a "-wal" suffix that is mmapped into the process space. If the current process does not have write permission on that file, then it cannot write into shared memory.)

Higher level logic within SQLite will normally intercept the error code and create a temporary in-memory shared memory region so that the current process can at least read the content of the database. This result code should not reach the application interface layer.

() SQLITE_IOERR_DIR_FSYNC

The SQLITE_IOERR_DIR_FSYNC error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to invoke fsync() on a directory. The unix VFS attempts to fsync() directories after creating or deleting certain files to ensure that those files will still appear in the filesystem following a power loss or system crash. This error code indicates a problem attempting to perform that fsync().

() SQLITE_CANTOPEN_DIRTYWAL

The SQLITE_CANTOPEN_DIRTYWAL result code is not used at this time.

() SQLITE_CONSTRAINT_NOTNULL

The SQLITE_CONSTRAINT_NOTNULL error code is an extended error code for SQLITE_CONSTRAINT indicating that a NOT NULL constraint failed.

() SQLITE_READONLY_DIRECTORY

The SQLITE_READONLY_DIRECTORY result code indicates that the database is read-only because process does not have permission to create a journal file in the same directory as the database and the creation of a journal file is a prerequisite for writing.

() SQLITE_IOERR_TRUNCATE

The SQLITE_IOERR_TRUNCATE error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to truncate a file to a smaller size.

() SQLITE_CANTOPEN_SYMLINK

The SQLITE_CANTOPEN_SYMLINK result code is returned by the sqlite3_open() interface and its siblings when the SQLITE_OPEN_NOFOLLOW flag is used and the database file is a symbolic link.

() SQLITE_CONSTRAINT_PRIMARYKEY

The SQLITE_CONSTRAINT_PRIMARYKEY error code is an extended error code for SQLITE_CONSTRAINT indicating that a PRIMARY KEY constraint failed.

() SQLITE_IOERR_FSTAT

The SQLITE_IOERR_FSTAT error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to invoke fstat() (or the equivalent) on a file in order to determine information such as the file size or access permissions.

() SQLITE_CONSTRAINT_TRIGGER

The SQLITE_CONSTRAINT_TRIGGER error code is an extended error code for SQLITE_CONSTRAINT indicating that a RAISE function within a trigger fired, causing the SQL statement to abort.

() SQLITE_IOERR_UNLOCK

The SQLITE_IOERR_UNLOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error within xUnlock method on the sqlite3_io_methods object.

() SQLITE_CONSTRAINT_UNIQUE

The SQLITE_CONSTRAINT_UNIQUE error code is an extended error code for SQLITE_CONSTRAINT indicating that a UNIQUE constraint failed.

() SQLITE_IOERR_RDLOCK

The SQLITE_IOERR_UNLOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error within xLock method on the sqlite3_io_methods object while trying to obtain a read lock.

() SQLITE_CONSTRAINT_VTAB

The SQLITE_CONSTRAINT_VTAB error code is not currently used by the SQLite core. However, this error code is available for use by application-defined virtual tables.

() SQLITE_IOERR_DELETE

The SQLITE_IOERR_UNLOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error within xDelete method on the sqlite3_vfs object.

() SQLITE_CONSTRAINT_ROWID

The SQLITE_CONSTRAINT_ROWID error code is an extended error code for SQLITE_CONSTRAINT indicating that a rowid is not unique.

() SQLITE_IOERR_BLOCKED

The SQLITE_IOERR_BLOCKED error code is no longer used.

() SQLITE_CONSTRAINT_PINNED

The SQLITE_CONSTRAINT_PINNED error code is an extended error code for SQLITE_CONSTRAINT indicating that an UPDATE trigger attempted do delete the row that was being updated in the middle of the update.

() SQLITE_IOERR_NOMEM

The SQLITE_IOERR_NOMEM error code is sometimes returned by the VFS layer to indicate that an operation could not be completed due to the inability to allocate sufficient memory. This error code is normally converted into SQLITE_NOMEM by the higher layers of SQLite before being returned to the application.

() SQLITE_CONSTRAINT_DATATYPE

The SQLITE_CONSTRAINT_DATATYPE error code is an extended error code for SQLITE_CONSTRAINT indicating that an insert or update attempted to store a value inconsistent with the column's declared type in a table defined as STRICT.

() SQLITE_IOERR_ACCESS

The SQLITE_IOERR_ACCESS error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xAccess method on the sqlite3_vfs object.

() SQLITE_IOERR_CHECKRESERVEDLOCK

The SQLITE_IOERR_CHECKRESERVEDLOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xCheckReservedLock method on the sqlite3_io_methods object.

() SQLITE_IOERR_LOCK

The SQLITE_IOERR_LOCK error code is an extended error code for SQLITE_IOERR indicating an I/O error in the advisory file locking logic. Usually an SQLITE_IOERR_LOCK error indicates a problem obtaining a PENDING lock. However it can also indicate miscellaneous locking errors on some of the specialized VFSes used on Macs.

() SQLITE_IOERR_CLOSE

The SQLITE_IOERR_ACCESS error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xClose method on the sqlite3_io_methods object.

() SQLITE_IOERR_DIR_CLOSE

The SQLITE_IOERR_DIR_CLOSE error code is no longer used.

() SQLITE_IOERR_SHMOPEN

The SQLITE_IOERR_SHMOPEN error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xShmMap method on the sqlite3_io_methods object while trying to open a new shared memory segment.

() SQLITE_IOERR_SHMSIZE

The SQLITE_IOERR_SHMSIZE error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xShmMap method on the sqlite3_io_methods object while trying to enlarge a "shm" file as part of WAL mode transaction processing. This error may indicate that the underlying filesystem volume is out of space.

() SQLITE_IOERR_SHMLOCK

The SQLITE_IOERR_SHMLOCK error code is no longer used.

() SQLITE_IOERR_SHMMAP

The SQLITE_IOERR_SHMMAP error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xShmMap method on the sqlite3_io_methods object while trying to map a shared memory segment into the process address space.

() SQLITE_IOERR_SEEK

The SQLITE_IOERR_SEEK error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xRead or xWrite methods on the sqlite3_io_methods object while trying to seek a file descriptor to the beginning point of the file where the read or write is to occur.

() SQLITE_IOERR_DELETE_NOENT

The SQLITE_IOERR_DELETE_NOENT error code is an extended error code for SQLITE_IOERR indicating that the xDelete method on the sqlite3_vfs object failed because the file being deleted does not exist.

() SQLITE_IOERR_MMAP

The SQLITE_IOERR_MMAP error code is an extended error code for SQLITE_IOERR indicating an I/O error within the xFetch or xUnfetch methods on the sqlite3_io_methods object while trying to map or unmap part of the database file into the process address space.

() SQLITE_IOERR_GETTEMPPATH

The SQLITE_IOERR_GETTEMPPATH error code is an extended error code for SQLITE_IOERR indicating that the VFS is unable to determine a suitable directory in which to place temporary files.

() SQLITE_IOERR_CONVPATH

The SQLITE_IOERR_CONVPATH error code is an extended error code for SQLITE_IOERR used only by Cygwin VFS and indicating that the cygwin_conv_path() system call failed. See also: SQLITE_CANTOPEN_CONVPATH

() SQLITE_IOERR_VNODE

The SQLITE_IOERR_VNODE error code is a code reserved for use by extensions. It is not used by the SQLite core.

() SQLITE_IOERR_AUTH

The SQLITE_IOERR_AUTH error code is a code reserved for use by extensions. It is not used by the SQLite core.

() SQLITE_IOERR_BEGIN_ATOMIC

The SQLITE_IOERR_BEGIN_ATOMIC error code indicates that the underlying operating system reported and error on the SQLITE_FCNTL_BEGIN_ATOMIC_WRITE file-control. This only comes up when SQLITE_ENABLE_ATOMIC_WRITE is enabled and the database is hosted on a filesystem that supports atomic writes.

() SQLITE_IOERR_COMMIT_ATOMIC

The SQLITE_IOERR_COMMIT_ATOMIC error code indicates that the underlying operating system reported and error on the SQLITE_FCNTL_COMMIT_ATOMIC_WRITE file-control. This only comes up when SQLITE_ENABLE_ATOMIC_WRITE is enabled and the database is hosted on a filesystem that supports atomic writes.

() SQLITE_IOERR_ROLLBACK_ATOMIC

The SQLITE_IOERR_ROLLBACK_ATOMIC error code indicates that the underlying operating system reported and error on the SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE file-control. This only comes up when SQLITE_ENABLE_ATOMIC_WRITE is enabled and the database is hosted on a filesystem that supports atomic writes.

() SQLITE_IOERR_DATA

The SQLITE_IOERR_DATA error code is an extended error code for SQLITE_IOERR used only by checksum VFS shim to indicate that the checksum on a page of the database file is incorrect.

() SQLITE_IOERR_CORRUPTFS

The SQLITE_IOERR_CORRUPTFS error code is an extended error code for SQLITE_IOERR used only by a VFS to indicate that a seek or read failure was due to the request not falling within the file's boundary rather than an ordinary device failure. This often indicates a corrupt filesystem.

Symptoms

Assume that you have an Always On Availability Group (AG) in an instance of Microsoft SQL Server or  When you back up a secondary replica that is running under asynchronous-commit mode, the backup operation may fail occasionally. Additionally, you may receive the following error message:

Error: , Severity: 20, State: 1.

The log scan number (nnn:nnn:nnn) passed to log scan in database 'dbname' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.

Resolution

This problem is fixed in the following updates for SQL Server:

Cumulative Update 13 for SQL Server

Cumulative Update 4 for SQL Server Service Pack 2

Cumulative Update 11 for SQL Server Service Pack 1

About SQL Server builds

Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server:

Latest cumulative update for SQL Server

The latest build for SQL Server

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology Microsoft uses to describe software updates.

This section lists each TopLink error code. Each error entry contains a description of the error, the probable cause, and the recommended action. Each error code corresponds to an exception class. See "Runtime and Development Exceptions" for more information.

A description shown in the actual exception thrown.

Cause: The most probable cause for the error.

Action: Suggestions for resolving the error.

ATTRIBUTE_AND_MAPPING_WITH_INDIRECTION_ MISMATCH

Cause: <attributeName> is not declared as type but the mapping uses indirection. Mapping is set to use indirection but the related attribute is not defined as type . It is thrown on foreign reference mappings.

Action: If you want to use indirection on the mapping, change the attribute to type . Otherwise, change the mapping associated with the attribute so that it does not use indirection.

ATTRIBUTE_AND_MAPPING_WITHOUT_INDIRECTION_ MISMATCH

Cause: <attributeName> is declared as type but the mapping is not using indirection. Attribute is defined to be of type but the mapping is not set to use indirection. It is thrown on foreign reference mappings.

Action: If you do not want to use indirection on the mapping, change the attribute to not be of type . Otherwise, change the mapping associated with the attribute to use indirection.

ATTRIBUTE_NAME_NOT_SPECIFIED

Cause: Attribute name is missing or not specified in the mapping definition.

Action: Specify the attribute name in the mapping by calling method .

ATTRIBUTE_TYPE_NOT_VALID

Cause: <attributeName> should be defined as type Vector, or a type that implements Map or Collection if using Java 2. It happens in one to many mapping, many to many mapping and collection mapping when mapping is set not to use indirection and attribute type is not declared of type .

Action: Declare the attribute to be of type .

CLASS_INDICATOR_FIELD_NOT_FOUND

Cause: The class indicator field has not been defined, however the descriptor has been set to use inheritance. When using inheritance, a class indicator field or class extraction method must be set. The class indicator field is used to create the right type of domain object

Action: Either a class indicator field or class extraction method must be set.

DIRECT_FIELD_NAME_NOT_SET

Cause: The direct field name from the target table is not set in the direct collection mapping. The field values form the collection in this mapping.

Action: Specify the direct field name by calling method .

FIELD_NAME_NOT_SET_IN_MAPPING

Cause: The field name is not set in the mapping. It is thrown from direct to field mapping, array mapping and structure mapping.

Action: Specify the field name by calling method .

FOREIGN_KEYS_DEFINED_INCORRECTLY

Cause: One to one mapping foreign key defined incorrectly. Multiple foreign key fields were set for one to one mapping by calling method .

Action: Use method to add multiple foreign key fields.

IDENTITY_MAP_NOT_SPECIFIED

Cause: The descriptor must use an identity map to use the Check cache does exist option. Descriptor has been set to not use identity map but the existence checking is set to be done on identity map.

Action: Either use identity map or set the existence checking to some other option.

ILLEGAL_ACCESS_WHILE_GETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: <attributeName> instance variable in object <objectName> is inaccessible. Instance variable in the domain object is not accessible. This exception is thrown when TopLink tries to access the instance variable using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_CLONING

Cause: Problem in cloning the object <domainObject>. Clone method <methodName> is not accessible. The method name specified using or the method to create clone on the domain object is not accessible by TopLink using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_CONSTRUCTOR_INSTANTIATION

Cause: The domain class does not define a public default constructor, which is needed by TopLink to create new instances of the domain class.

Action: Define one or use different instantiation policy.

ILLEGAL_ACCESS_WHILE_EVENT_EXECUTION

Cause: The descriptor callback method <eventMethodName> with as argument, is not accessible. This exception is thrown when TopLink tries to access the event method using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Trying to invoke inaccessible <methodName> on the object <objectName>. The underlying get accessor method to access an attribute in the domain object is not accessible. This exception is thrown when TopLink tries to access an attribute through method using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INSTANTIATING_METHOD_ BASED_PROXY

Cause: The method used by the Transformation mapping using a is illegal. This exception is thrown when TopLink tries to access the method using Java reflection. The problem is caused when method base value holder is getting instantiated.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INVOKING_ATTRIBUTE_METHOD

Cause: On transformation mapping the underlying attribute method used to retrieve value from the database row while reading transformation mapped attribute is not accessible.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INVOKING_FIELD_TO_METHOD

Cause: On transformation mapping the method <methodName> used to retrieve value from the object while writing transformation mapped attribute is not accessible. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INVOKING_ROW_EXTRACTION_ METHOD

Cause: Problem in extracting class from <row>; Static method <method> with <databaseRow> as argument, is not accessible. The method to extract class from row on the domain object is not accessible. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_METHOD_INSTANTIATION

Cause: Problem in creating new instance; the method <methodName> to create instances on the domain class is not accessible. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_OBSOLETE_EVENT_EXECUTION

Cause: The descriptor callback method <eventMethodName> with Session as argument, is inaccessible. This exception is thrown when TopLink tries to access the event method using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: The <attributeName> instance variable in the object <objectName> is not accessible through Java reflection. The error is thrown by Java and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_SETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Trying to invoke inaccessible method <setMethodName> on the object with parameter <parameter>. The attribute's set accessor method is not accessible through Java reflection. The error is thrown by Java and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_GETTING_VALUE_ THRU_INSTANCE_VARIABLE_ACCESSOR

Cause: Trying to get a value for an instance variable <attributeName> of type <typeName> from the object. The specified object is not an instance of the class or interface declaring the underlying field. An object is accessed to get the value of an instance variable that does not exist.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Trying to invoke method <methodName> on the object <objectName>. The get accessor method declaration on the domain object differs from the one that is defined. The number of actual and formal parameters differ, or an unwrapping conversion has failed.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_INSTANTIATING_METHOD_ BASED_PROXY

Cause: The method used by the method-based proxy in a Transformation mapping is getting illegal arguments when the value holder is getting instantiated. This exception is thrown when TopLink tries to access the method using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_INVOKING_ATTRIBUTE_ METHOD

Cause: The number of actual and formal parameters differ, or an unwrapping conversion has failed. On transformation mapping the method used to retrieve value from the database row while reading transformation mapped attribute is getting illegal argument.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_INVOKING_FIELD_TO_ METHOD

Cause: The number of actual and formal parameters differ for method <methodName> or an unwrapping conversion has failed. On transformation mapping the method used to retrieve value from the object while writing transformation mapped attribute is getting illegal argument. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_OBSOLETE_EVENT_ EXECUTION

Cause: he number of actual and formal parameters for the descriptor callback method <eventMethodName> differs, or an unwrapping conversion has failed. The callback event method is invoked with illegal argument. This exception is thrown when TopLink tries to invoke the event method using Java reflection. The error is a purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: Illegal value is being assigned to the attribute instance variable. Trying to set a value <value> for an instance variable <attributeName> of type <typeName> in the object. The specified object is not an instance of the class or interface declaring the underlying field, or an unwrapping conversion has failed.

TopLink does the assignment of value by using Java reflection. Java throws the error and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_SETTING_VALUE_THRU _METHOD_ACCESSOR

Cause: Illegal argument is being passed to the attribute's set accessor method. Trying to invoke method <setMethodName> on the object. The number of actual and formal parameters differs, or an unwrapping conversion has failed. Java throws the error and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

INSTANTIATION_WHILE_CONSTRUCTOR_INSTANTIATION

Cause: he class does not define a public default constructor, or the constructor raised an exception. The default constructor for the domain object is invoked to create new instance of the object while building new domain objects. If this Class represents an abstract class, an interface, an array class, a primitive type, or void; or if the instantiation fails for some other reason. Java throws the error and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

INVALID_DATA_MODIFICATION_EVENT

Cause: This is an exception that an application should never encounter. The exception can occur at the time of developing TopLink. In cases where one writes new mapping it is possible to get this exception. In direct collection mapping and many to many mapping the target table and relational table are populated at the end of the commit process and if data modification event is sent to any other mapping then this exception is thrown.

Action: Contact Technical Support.

INVALID_DATA_MODIFICATION_EVENT_CODE

Cause: This is an exception that an application should never encounter. The exception can occur at the time of developing TopLink. In cases where one writes new mapping it is possible to get this exception. In direct collection mapping and many to many mapping the target table and relational table are populated at the end of the commit process and if data modification event is sent to these two mappings with wrong event code then this exception is thrown.

Action: Contact Technical Support.

INVALID_DESCRIPTOR_EVENT_CODE

Cause: This is an exception that an application should never encounter. The exception can occur at the time of developing TopLink. The exception means that descriptor event manager does not support the event code passed in the event.

Action: Contact Technical Support.

INVALID_IDENTITY_MAP

Cause: Identity map constructor failed because an invalid identity map was specified. The identity map class given in the descriptor cannot be instantiated. The exception is Java exception thrown by Java reflection when TopLink is instantiating the identity map class. TopLink only wraps the Java exception.

Action: Inspect the internal exception and check the Java manuals.

JAVA_CLASS_NOT_SPECIFIED

Cause: The descriptor does not define a Java class. The Java class is not specified in the descriptor.

Action: Specify the Java Class

DESCRIPTOR_FOR_INTERFACE_IS_MISSING

Cause: A descriptor for the referenced interface is not added to the session.

Action: Add that descriptor to the session.

MAPPING_FOR_SEQUENCE_NUMBER_FIELD

Cause: A non-read-only mapping is not defined for the sequence number field. A mapping is required so that TopLink can put and extract values for the primary key.

Action: Define a mapping.

MISSING_CLASS_FOR_INDICATOR_FIELD_VALUE

Cause: Missing class for indicator field value <classFieldValue> of type <type>. There was no class entry found in the inheritance policy for the indicator field value read from the database. Probably the method was not called for the field value. The class and typeValue is stored in the hashtable and later on the class is extracted from the hashtable by passing as a key. Remember Integer(1) is not equal to Float(1), this is another major reason for this problem when the type of typeValue is different.

Action: Check descriptor.

MISSING_CLASS_INDICATOR_FIELD

Cause: The class indicator field is missing from the database row <row> that was read from the database. This is done in inheritance model where after reading rows from the database, child domain objects are to be constructed depending upon the type indicator values.

Action: Check the printed row to make sure the spelling is correct.

MISSING_MAPPING_FOR_FIELD

Cause: Missing mapping for field <field>; a mapping for the field is not specified.

Action: Define a mapping for the field.

NO_MAPPING_FOR_PRIMARY_KEY

Cause: A mapping for the primary key is not specified. There should be one non-read-only mapping defined for the primary key field.

Action: efine a mapping for the primary key.

MULTIPLE_TABLE_PRIMARY_KEY_NOT_SPECIFIED

Cause: The multiple table primary key mapping must be specified when a custom multiple table join is used. If multiple tables are specified in the descriptor and the join expression is customized then the primary keys for all the tables must be specified. If the primary keys are not specified then the exception is caused.

Action: Call method on the descriptor to set the primary keys.

MULTIPLE_WRITE_MAPPINGS_FOR_FIELD

Cause: There are multiple writable mappings for the field <fieldName> in the descriptor. Exactly one must be defined writable. The others must be specified as read-only. When multiple write mappings are defined for the field, TopLink cannot decide on which mapping to pick up for writing the value of the field in the database row hence the exception is thrown during the validation process of descriptors. The most common site for this problem is that sometimes the field has direct-to-field mapping and also one-to-one mapping. In this case if direct-to-field mapping has to be kept then one-to-one mapping should either be read-only or it should be target foreign key reference.

Action: Make one of those mappings read only.

NO_ATTRIBUTE_TRANSFORMATION_METHOD

Cause: The attribute transformation method name in the transformation mapping is not specified. This method is invoked internally by TopLink to retrieve value to store in the domain object.

Action: Define a method and set the method name on the mapping by calling method .

NO_FIELD_NAME_FOR_MAPPING

Cause: No field name is specified in direct-to-field mapping.

Action: Set the field by calling .

NO_FOREIGN_KEYS_ARE_SPECIFIED

Cause: Neither the selection criteria nor the foreign keys were specified on one-to-one mapping. If the selection criterion is not specified then TopLink tries to build one from the foreign keys specified in the mapping.

Action: Specify the fields.

NO_REFERENCE_KEY_IS_SPECIFIED

Cause: No query key named: <queryKey> found in: <descriptor>; no reference key from the target table is specified on direct collection mapping.

Action: Specify the fields by calling method .

NO_RELATION_TABLE

Cause: The relation table name is not set in this many-to-many mapping.

Action: Set relation table name by calling method .

NO_SOURCE_RELATION_KEYS_SPECIFIED

Cause: There are no source relation keys specified in this many-to-many mapping.

Action: Add source relation keys to the mapping.

NO_SUCH_METHOD_ON_FIND_OBSOLETE_METHOD

Cause: The descriptor callback method <selector> on the domain class was not found. It must take a or a as its argument. TopLink tries to invoke the method using Java reflection. It is a Java exception and TopLink is only wrapping the main exception.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_ON_INITIALIZING_ ATTRIBUTE_METHOD

Cause: The method <attributeMethodName> with parameters <databaseRow> or <databaseRow, session> is not found. TopLink wraps the Java reflection exception that is caused when the method is being created from the method name. This method is set by calling.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_CONSTRUCTOR_ INSTANTIATION

Cause: Inaccessible constructor. TopLink wraps the Java reflection exception that is caused when it is creating a new instance of the domain.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_CONVERTING_TO_METHOD

Cause: Method <methodName> not found with parameters () or (Session). TopLink wraps the Java reflection exception that is caused when it is creating a Method type from the method names in transformation mapping.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_FIELD_WHILE_INITIALIZING_ATTRIBUTES_ IN_INSTANCE_VARIABLE_ACCESSOR

Cause: The instance variable <attributeName> is not defined in the domain class or it is not accessible. TopLink wraps the Java reflection exception that is caused when it is creating a Field type from the attribute name.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_ ATTRIBUTES_IN_METHOD_ACCESSOR

Cause: The accessor method <setMethodName> or <getMethodName> is not defined for the attribute in the domain class <javaClassName>, or it is not accessible. TopLink wraps the Java reflection exception that is caused when it is creating a Method type from the method name.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_ CLASS_EXTRACTION_METHOD

Cause: The static class extraction method <methodName> with <databaseRow> as argument does not exist, or is not accessible. Java reflection exception wrapped in TopLink exception is thrown when class extraction method is being created from the method name in inheritance policy.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_COPY_POLICY

Cause: The clone method <methodName> with no arguments does not exist, or is not accessible. Java reflection exception wrapped in TopLink exception is thrown when a method to create clones is being created from the method name in copy policy.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_ INSTANTIATION_POLICY

Cause: The instance creation method <methodName> with no arguments does not exist, or is not accessible. Java reflection exception wrapped in TopLink exception is thrown when a method to create new instances is being created from the method name in instantiation policy.

Action: Inspect the internal exception and check the Java manuals.

NO_TARGET_FOREIGN_KEYS_SPECIFIED

Cause: The foreign keys in the target table are not specified in one-to-many mappings. These fields are not required if a selection criterion is given in the mapping but otherwise they must be specified.

Action: Set target foreign keys or selection criteria.

NO_TARGET_RELATION_KEYS_SPECIFIED

Cause: There are no target relation keys specified in many-to-many mappings.

Action: Call method to set the fields.

NOT_DESERIALIZABLE

Cause: The object cannot be de-serialized from the byte array read from the database. The exception is thrown when serialized object mapping is converting byte array into object.

Action: Inspect the internal exception and check the Java manuals.

NOT_SERIALIZABLE

Cause: The object cannot be serialized into byte array. The exception is thrown when serialized object mapping is object into byte array.

Action: Inspect the internal exception and check the Java manuals.

NULL_FOR_NON_NULL_AGGREGATE

Cause: Value of aggregate in the source object <object> is null. Null values not allowed for aggregate mappings unless allow null is specified in aggregate mapping.

Action: Call method ) on the mapping.

NULL_POINTER_WHILE_GETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: An object is accessed to get the value of an instance variable through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: The get accessor method is invoked to get the value of attribute through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: Null Pointer Exception is thrown while setting value of <attributeName> instance variable in the object to value. An object is accessed to set the value of an instance variable through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_SETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Null Pointer Exception is thrown while setting value through <setMethodName> method in the object with argument <argument>. The set accessor method is invoked to set the value of attribute through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

PARENT_DESCRIPTOR_NOT_SPECIFIED

Cause: Cannot find descriptor for parent class. The descriptor of a subclass has no parent descriptor.

Action: The method on the subclass descriptor must be called.

PRIMARY_KEY_FIELDS_NOT_SPECIFIED

Cause: The primary key fields are not set for this descriptor.

Action: Add primary key field names using method or .

REFERENCE_CLASS_NOT_SPECIFIED

Cause: The reference class is not specified in the foreign reference mapping.

Action: Set reference class by calling method

REFERENCE_DESCRIPTOR_IS_NOT_AGGREGATE

Cause: The referenced descriptor for <className> should be set to aggregate descriptor. An aggregate mapping should always reference a descriptor that is aggregate.

Action: Call method on the referenced descriptor.

REFERENCE_KEY_FIELD_NOT_PROPERLY_SPECIFIED

Cause: The table for the reference field must be the reference table. If the reference field name specified in the direct collection mapping is qualified with the table name then the table name should match the reference table name.

Action: Qualify the field with the proper name or change the reference table name.

REFERENCE_TABLE_NOT_SPECIFIED

Cause: The reference table name in the direct collection mapping is not specified.

Action: Use method on the mapping to set the table name.

RELATION_KEY_FIELD_NOT_PROPERLY_SPECIFIED

Cause: The table for the relation key field must be the relation table. If the source and target relation fields name specified in the many to many mapping are qualified with the table name then the table name should match the relation table name.

Action: Qualify the field with the proper name or change the relation table name.

RETURN_TYPE_IN_GET_ATTRIBUTE_ACCESSOR

Cause: The method <attributeMethodName> specified in the transformation mapping should have a return type set in the attribute because this method is used to extract value from the database row.

Action: Check the method and make appropriate changes.

SECURITY_ON_FIND_METHOD

Cause: The descriptor callback method <selector> with DescriptorEvent as argument is not accessible. Java throws security exception when a Method type is created from the method name using Java reflection. The method is a descriptor event callback on the domain object that takes DescriptorEvent as its parameter.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_ON_FIND_OBSOLETE_METHOD

Cause: The descriptor callback method <selector> with <session> as argument is not accessible. Java throws security exception when a Method type is created from the method name using Java reflection. The method is a descriptor event callback on the domain object which takes class and session as its parameters.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_ON_INITIALIZING_ATTRIBUTE_METHOD

Cause: Access to the method <attributeMethodName> with parameters <databaseRow> or <databaseRow, Session> has been denied. Java throws security exception when a Method type is created from the attribute method name using Java reflection. The attribute method specified in the transformation mapping is used to extract value from the database row and set by calling .

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_CONVERTING_TO_METHOD

Cause: Method: <methodName> ACCESS DENIED with <> or <session> parameters. Java throws security exception when a Method type is created from the method name using Java reflection. These are the methods that will extract the field value from the domain object in the transformation mapping.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_ATTRIBUTES_IN_ INSTANCE_VARIABLE_ACCESSOR

Cause: Access to the instance variable, <attributeName> in the class <javaClassName> is denied. Java throws security exception when creating Field type from the given attribute name using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_ATTRIBUTES_IN_ METHOD_ACCESSOR

Cause: The methods <setMethodName> and <getMethodName> in the object <javaClassName> are inaccessible. Java throws security exception when creating Method type from the given attribute accessor method name using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_CLASS_ EXTRACTION_METHOD

Cause: The static class extraction method <methodName> with DatabaseRow as argument is not accessible. Java throws security exception when creating Method type from the given class extraction method name using Java reflection. The method is used to extract class from the database row in inheritance policy.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_COPY_POLICY

Cause: The clone method <methodName> with no arguments is not accessible. Java throws security exception when creating Method type from the given method name using Java reflection. This method on copy policy is used to create clones of the domain object.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_INSTANTIATION_POLICY

Cause: The instance creation method <methodName> with no arguments is not accessible. Java throws security exception when creating Method type from the given method name using Java reflection. This method on instantiation policy is used to create new instances of the domain object.

Action: Inspect the internal exception and check the Java manuals.

SEQUENCE_NUMBER_PROPERTY_NOT_SPECIFIED

Cause: Either the sequence field name or the sequence number name is missing. To use sequence generated ids both the sequence number name and field name properties must be set.

Action: To use sequence-generated ids, both the sequence number name and field name properties must be set.

SIZE_MISMATCH_OF_FOREIGN_KEYS

Cause: The size of the primary keys on the target table does not match the size of the foreign keys on the source in one to one mapping.

Action: Check the mapping and the reference descriptor's primary keys.

TABLE_NOT_PRESENT

Cause: The table <tableName> is not present in the descriptor.

Action: Check the qualified field names specified in the mappings and descriptor, if these fields are qualified with the table name then those fields should have right table.

TABLE_NOT_SPECIFIED

Cause: No table is specified in the descriptor. Descriptor must have a table name defined.

Action: Call method or to set the tables on the descriptor.

TARGET_FOREIGN_KEYS_SIZE_MISMATCH

Cause: The size of the foreign keys on the target table does not match the size of the source keys on the source table in one to many mapping.

Action: Check the mapping.

TARGET_INVOCATION_WHILE_CLONING

Cause: Problem in cloning the object <domainObject> clone method. <methodName> triggered an exception. Java is throwing exception when clone method is invoked using Java reflection while cloning object. The clone method is specified on the copy policy that is usually invoked to create clones in unit of work.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_EVENT_EXECUTION

Cause: The underlying descriptor callback method <eventMethodName> with DescriptorEvent as argument, throws an exception. Java is throwing exception when descriptor event method is invoked using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_GETTING_VALUE_ THRU_METHOD_ACCESSOR

Cause: The method <methodName> on the object <objectName> is throwing an exception. Java is throwing exception while getting an attribute value from the object through method accessor.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INSTANTIATING_ METHOD_BASED_PROXY

Cause: Method has thrown an exception. Java is throwing exception while instantiating method based proxy. This happens while instantiating transformation mapping.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INVOKING_ ATTRIBUTE_METHOD

Cause: The underlying method throws an exception. Java is throwing exception while invoking attribute transformation method on transformation mapping. The method is invoked to extract value from the database row to set into the domain object.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INVOKING_FIELD_ TO_METHOD

Cause: The method <methodName> is throwing an exception. Java is throwing exception while invoking field transformation method on transformation mapping. The method is invoked to extract value from the domain object to set into the database row.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INVOKING_ROW_ EXTRACTION_METHOD

Cause: Problem in extracting class from row <row>, static method, <method> with <databaseRow as argument>. An exception was triggered Java is throwing exception while invoking class extraction method. The method is used to extract class type so that right kind of object can be created in inheritance model.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_METHOD_INSTANTIATION

Cause: Problem in creating new instance. Creation method <methodName> caused an exception. Java is throwing exception while invoking instantiation method. The method is used to create new instances of the domain objects.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_OBSOLETE_ EVENT_EXECUTION

Cause: The underlying descriptor callback method <eventMethodName> with <session> as argument, throws an exception. Java is throwing exception while invoking descriptor event method that takes session as its parameter.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_SETTING_VALUE_THRU_ METHOD_ACESSOR

Cause: The method <setMethodName> on the object is throwing an exception. Java is throwing exception while invoking set accessor method on the domain object to set an attribute value into the domain object.

Action: Inspect the internal exception and check the Java manuals.

VALUE_NOT_FOUND_IN_CLASS_INDICATOR_MAPPING

Cause: The indicator value is not found in the class indicator mapping in the parent descriptor for the class.

Action: Check on the inheritance policy.

WRITE_LOCK_FIELD_IN_CHILD_DESCRIPTOR

Cause: The child descriptor should not have a write lock field defined because it gets it from the parent descriptor.

Action: Check your child descriptor and remove the field.

DESCRIPTOR_IS_MISSING

Cause: The descriptor for the reference class <className> is missing from the mapping.

Action: Check session to see if the descriptor for the reference class was added.

MULTIPLE_TABLE_PRIMARY_KEY_MUST_BE_ FULLY_QUALIFIED

Cause: Multiple table primary key field names must be fully qualified. These fields names are given on the descriptor if it has more than one table.

Action: Specify the field names with table name.

ONLY_ONE_TABLE_CAN_BE_ADDED_WITH_THIS_METHOD

Cause: Only one table can be added through this method.

Action: Use to add multiple tables to descriptor.

NULL_POINTER_WHILE_CONSTRUCTOR_INSTANTIATION

Cause: Inaccessible constructor. Java is throwing this exception while invoking a default constructor to create new instances of the domain object.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_METHOD_INSTANTIATION

Cause: Problem in creating new instance <methodName> creation method is not accessible. Java is throwing an exception while calling a method to build new instance of the domain object. This method is given by the user to override the default behavior of creating new instances through class constructor.

Action: Inspect the internal exception and check the Java manuals.

NO_ATTRBUTE_VALUE_CONVERSION_TO_FIELD_VALUE_PROVIDED

Cause: The field conversion value for the attribute value <attributeValue> was not given in the object type mapping.

Action: Check the attribute value and provide a corresponding field value in the mapping.

NO_FIELD_VALUE_CONVERSION_TO_ATTRIBUTE_ VALUE_PROVIDED

Cause: The attribute conversion value for the <fieldValue> was not given in the object type mapping.

Action: Check the field value and provide a corresponding attribute value in the mapping.

LOCK_MAPPING_CANNOT_BE_READONLY

Cause: The domain object <className> cannot have a read only mapping for the write lock fields when the version value is stored in the object.

Action: Check the mappings on write lock fields.

LOCK_MAPPING_MUST_BE_READONLY

Cause: The domain object <className> should have a read only mapping for the write lock fields when the version value is stored in the cache.

Action: Check the mappings on write lock fields.

CHILD_DOES_NOT_DEFINE_ABSTRACT_QUERY_KEY

Cause: The queryKey <queryKeyName> is defined in the parent descriptor but not in the child descriptor. The descriptor has not defined abstract query key.

Action: Any implementors of interface descriptor must define the query key defined by abstract query key in the interface descriptor.

SET_EXISTENCE_CHECKING_NOT_UNDERSTOOD

Cause: The interface descriptor <parent> must have at least one abstract query key defined. The string given to the method is not understood.

Action: The string passed should be one of the following:

  • Check cache
  • Check database
  • Assume existence
  • Assume non-existence

VALUE_HOLDER_INSTANTIATION_MISMATCH

Cause: The mapping for the attribute uses indirection and must be initialized to a new ValueHolder.

Action: Ensure the mapping uses indirection and the attribute is initialized to a new .

NO_SUB_CLASS_MATCH

Cause: No sub-class matches this class <theClass> when inheritance is in aggregate relationship mapping.

Action: Verify the sub-class and the relationship mapping.

RETURN_AND_MAPPING_WITH_INDIRECTION_MISMATCH

Cause: The get method return type for the attribute () is not declared as type , but the mapping is using indirection.

Action: Ensure the get method returns a or change the mapping to not use indirection.

RETURN_AND_MAPPING_WITHOUT_INDIRECTION_ MISMATCH

Cause: The get method return type for the attribute is declared as type , but the mapping is not using indirection.

Action: Ensure the mapping is using indirection or change the return type from

PARAMETER_AND_MAPPING_WITH_INDIRECTION_ MISMATCH

Cause: The set method parameter type for the attribute is not declared as type , but the mapping is using indirection.

Action: Ensure the set method parameter is declared as a or the mapping is changed to not use indirection.

PARAMETER_AND_MAPPING_WITHOUT_INDIRECTION_ MISMATCH

Cause: The set method parameter type for the attribute is declared as type , but the mapping is not using indirection.

Action: Ensure the mapping is changed to use indirection or the set method parameter is not declared as a .

GET_METHOD_RETURN_TYPE_NOT_VALID

Cause: he get method return type for the attribute should be declared as type Vector (or a type that implements Map or Collection, if using Java2).

Action: The get method return type for the attribute should be declared as type Vector (or a type that implementsMap or Collection, if using Java2).

SET_METHOD_PARAMETER_TYPE_NOT_VALID

Cause: The set method parameter type for the attribute should be declared as type Vector (or a type that implements Map or Collection, if using Java2).

Action: The set method parameter type for the attribute should be declared as type Vector (or a type that implements Map or Collection, if using Java2).

ILLEGAL_TABLE_NAME_IN_MULTIPLE_TABLE_ FOREIGN_KEY

Cause: The table in the multiple table foreign key relationship refers to an unknown table.

Action: Verify the table name.

ATTRIBUTE_AND_MAPPING_WITH_TRANSPARENT_ INDIRECTION_MISMATCH

Cause: The attribute is not declared as a super-type of , but the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.

RETURN_AND_MAPPING_WITH_TRANSPARENT_ INDIRECTION_MISMATCH

Cause: The get method return type for the attribute is not declared as a super-type of , but the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.

PARAMETER_AND_MAPPING_WITH_TRANSPARENT_ INDIRECTION_MISMATCH

Cause: The set method parameter type for the attribute is not declared as a super-type of , but the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.

FIELD_IS_NOT_PRESENT_IN_DATABASE

Cause: Field <fieldname> is not present in the table <tableName> in the database.

Action: Verify the field name for the attribute.

TABLE_IS_NOT_PRESENT_IN_DATABASE

Cause: is not present in the database.

Action: Verify the table name for the descriptor.

MULTIPLE_TABLE_INSERT_ORDER_MISMATCH

Cause: The multiple table insert order Vector specified , has more/fewer tables than are specified in the descriptor . All the tables must be included in the insert order Vector.

Action: Verify that all table names for the descriptor are present and that there are no extras.

INVALID_USE_OF_TRANSPARENT_INDIRECTION

Cause: Transparent Indirection can only be used with CollectionMappings.

Action: Verify the mapping. It must be a collection mapping.

MISSING_INDIRECT_CONTAINER_CONSTRUCTOR

Cause: The indirect container class must implement the constructor.

Action: Implement the constructor for the container.

COULD_NOT_INSTANTIATE_INDIRECT_CONTAINER_CLASS

Cause: The indirect container class could not be instantiated using the constructor.

Action: Validate the constructor for the indirect container class.

INVALID_CONTAINER_POLICY

Cause: This container policy should only be used in JDK containerPolicy. It was instantiated for javaClass.

Action: Validate the container policy being used.

INVALID_CONTAINER_POLICY_WITH_TRANSPARENT_ INDIRECTION

Cause: The container policy is incompatible with transparent indirection.

Action: Change the container policy to be compatible with transparent indirection or do not use transparent indirection.

INVALID_USE_OF_NO_INDIRECTION

Cause: No Indirection should not receive this message.

Action: Change to use no indirection.

INDIRECT_CONTAINER_INSTANTIATION_MISMATCH

Cause: The mapping for the attribute uses transparent indirection and must be initialized to an appropriate container.

Action: Initialize the mapping to an appropriate container.

INVALID_MAPPING_OPERATION

Cause: Invalid mapping operation.

Action: Check the documentation for valid mapping operations.

INVALID_INDIRECTION_POLICY_OPERATION

Cause: Invalid indirection policy operation.

Action: Check the documentation for valid indirection policy operations.

REFERENCE_DESCRIPTOR_IS_NOT_ AGGREGATECOLLECTION

Cause: The reference descriptor for <className> should be set to aggregate collection descriptor.

Action: Set the reference descriptor to an aggregate collection descriptor.

INVALID_INDIRECTION_CONTAINER_CLASS

Cause: Invalid indirection container class.

Action: Verify the container class.

MISSING_FOREIGN_KEY_TRANSLATION

Cause: The mapping does not include a foreign key field linked to the primary key field.

Action: Link the foreign key to the appropriate primary key.

TRUCTURE_NAME_NOT_SET_IN_MAPPING

Cause: The structure name is not set.

Action: Set the structure name appropriately.

NORMAL_DESCRIPTORS_DO_NOT_SUPPORT_ NON_RELATIONAL_EXTENSIONS

Cause: Normal descriptors do not support non-relational extensions.

Action: Contact Technical Support.

PARENT_CLASS_IS_SELF

Cause: The descriptor's parent class has been set to itself.

Action: Contact Technical Support.

PROXY_INDIRECTION_NOT_AVAILABLE

Cause: An attempt to use proxy indirection has been made but JDK is not being used.

Action: Proxy indirection is only supported in JDK

INVALID_ATTRIBUTE_TYPE_FOR_PROXY_INDIRECTION

Cause: The attribute wasn't specified in the list of interfaces given to use Proxy Indirection.

Action: Verify the attribute

INVALID_GET_RETURN_TYPE_FOR _PROXY_INDIRECTION

Cause: The return type for the indirection policy is invalid for the indirection policy.

Action: Verify that the parameter type of the attribute's get method is correct for the indirection policy.

INVALID_SET_PARAMETER_TYPE_FOR_PROXY_ INDIRECTION

Cause: The parameter for the set method is incorrect for the indirection type.

Action: Verify that the parameter type of the attribute's set method is correct for the indirection policy.

INCORRECT_COLLECTION_POLICY

Cause: The container policy is invalid for the collection type.

Action: Check that the container policy is correct for the collection type.

INVALID_AMENDMENT_METHOD

Cause: The amendment method provided is invalid, not public, or cannot be found.

Action: Ensure the amendment method is public, static, returns void and has a single argument: Descriptor.

ERROR_OCCURRED_IN_AMENDMENT_METHOD

Cause: The specified amendment method threw an exception.

Action: Examine the returned exception for further details.

VARIABLE_ONE_TO_ONE_MAPPING_IS_NOT_DEFINED

Cause: There is no mapping for attribute.

Action: Validate the mapping and attribute.

TARGET_INVOCATION_WHILE_CONSTRUCTOR_ INSTANTIATION

Cause: Constructor is missing.

Action: Make the required constructor.

TARGET_INVOCATION_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: Constructor is missing.

Action: Make the required constructor.

ILLEGAL_ACCESS_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: Permissions do not permit access to the constructor.

Action: Adjust the Java security permissions to permit access to the constructor.

INSTANTIATION_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: An instantiation failed inside the associated constructor.

Action: Determine which objects are being instantiated, and ensure all are being done properly.

NO_SUCH_METHOD_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: A message send invoked from inside the constructor is invalid because the method does not exist.

Action: Correct the message send ensuring that the message exists.

NULL_POINTER_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: A message is being sent from inside a constructor to a null object.

Action: Avoid sending a message to an object that is null.

ILLEGAL_ACCESS_WHILE_METHOD_ INSTANTIATION_OF_FACTORY

Cause: A message is being sent to an object from inside a factory instantiation. Java has determined this message to be illegal.

Action: Determine why the message send is illegal, and replace the message with the proper legal one.

TARGET_INVOCATION_WHILE_METHOD_ INSTANTIATION_OF_FACTORY

Cause: Error inside the factory associated with the invocation of a target.

Action: Determine the faulty target, and replace with the correct target, or proper message send.

NULL_POINTER_WHILE_METHOD_ INSTANTIATION_OF_FACTORY

Cause: A message is being sent to null inside a factory instantiation.

Action: Avoid sending a message to null.

No such method

Cause: Tokens in the builder generated files are the subsets of all the tokens a Project Reader can understand. Each token has a related public method on TopLink. The exception would mean that the method name is incorrect.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not find post load method <methodName> on class <aClass>

Cause: The post load method defined in descriptor properties is not defined on the related domain class.

Action: Must define the method on the specified class.

Cannot write parameter <object> of class <type>

Cause: While creating project class the parameter tokens are read from the file and are converted to actual types before sending them to the methods. An unknown type will cause this exception.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not access method <method>

Cause: Java is throwing an illegal access reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invoking <applyResultMethod> raised exception <exception>

Cause: Java is throwing an invocation reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invalid arguments invoking: <applyResultMethod> with <receiver>

Cause: Java is throwing an invalid argument reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not access <applyResultMethod> with <receiver>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Parameter mismatch <method>; received <size> parameters

Cause: The number of parameters for the token read from the project or descriptor file do not match the number of parameters a related method can take.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Accessing <methodName> on <className> with <parameters>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not find section definition <section> when building section definitions for <target>

Cause: Invalid section name was found in the project or descriptor file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not convert <object> into an accessible Java class.

Cause: The parameter read from the file cannot be converted to a appropriate type.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

File not found

Cause: The project or descriptor file was not found.

Action: Check that the path was given correctly in a project reader and also the path is correct in project file.

Invalid class/method name format.

Cause: No one should actually be using the URL way of reading INI files. This is untested and undocumented feature.

Action: Use other ways of reading files.

Open failed for URL <url>

Cause: Open failed for URL.

Action: Inspect the internal exception and check the Java manuals.

Could not resolve INIFile location: <sourceString> using search paths <searchPaths>

Cause: The file was not found on the given search paths.

Action: Check your search paths.

Invoking <method> on <receiver>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invoking <method> on <receiver>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invalid character value; expecting $* format

Cause: An invalid character format was written to the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Unexpected character: {

Cause: Unexpected character { found while reading vector values from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Unexpected character: }

Cause: Unexpected character } found while reading vector values from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Expecting object, found token <nextToken>

Cause: Unexpected token found while reading from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Unexpected word

Cause: Unexpected token found while reading from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

setExistenceChecking <token>; not understood

Cause: Existence checking string specified on the descriptor is not understood.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Class <className> not found

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Not enough INI elements. Found <count>.

Cause: If the line in an INI file is incomplete, i.e., it does not have enough tokens.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Too many INI elements. Found <count>.

Cause: If the line in an INI file has more tokens then needed.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Error writing <writeString>

Cause: Could not write into the file. Perhaps are used and file or directory structure does not exist.

Action: Inspect the internal exception and check the Java manuals. Try using .

Illegal access exception

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Invocation target exception

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Attempting to instantiate <className> with default constructor.

Cause: Java is throwing reflection exception while instantiating the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Attempting to instantiate <className> with default constructor.

Cause: Java is throwing reflection exception while instantiating the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

IO Exception in next token

Cause: Java is throwing reflection. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

IOException on close.

Cause: Java is throwing reflection. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Invalid INI(URL) Method: <method>. Should return a string.

Cause: No one should actually be using the URL way of reading INI files. This is untested and undocumented feature.

Action: Use other ways of reading files.

Could not cast using <castString>.

Cause: An error occurred during an attempt to cast using the

Action: Validate the

A writer or a target file name must be specified

Cause: A writer or a target file name is not specified.

Action: A writer or a target file name must be specified.

IOException on open.

Cause: Java is throwing reflection. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Post Load Method Not Static

Cause: The method specified is not static.

Action: Modify the method to be static.

Project Not Found.

Cause: No projects were found in the specified directory.

Action: Verify the directory.

Multiple Projects With Name.

Cause: More than one project with the same name was found.

Action: Verify the project name.

WAIT_WAS_INTERRUPTED

Cause: In a multi threaded environment one of the waiting thread was interrupted.

Action: Usually such exceptions would mean restarting the application but it is totally dependent on the application.

WAIT_FAILURE_SERVER

Cause: Wait failure on ServerSession. When the number of non-pooled connections reach the threshold any more requests for such connection results in wait until some one releases the connection resource. If this wait was interrupted then an exception is thrown.

Action: Usually such exceptions would mean restarting the application but it is totally dependent on the application.

WAIT_FAILURE_CLIENT

Cause: Wait failure on ClientSession. When the number of pooled connections reach the threshold any more requests for such connection results in wait until some one releases the connection resource. If this wait was interrupted then an exception is thrown.

Action: Usually such exceptions would mean restarting the application but it is totally dependent on the application.

SIGNAL_ATTEMPTED_BEFORE_WAIT

Cause: A signal was attempted before wait on concurrency manager. This normally means that an attempt was made to commit or rollback a transaction before it was started, or to rollback a transaction twice.

Action: Check transactions in the application.

COULD_NOT_BE_CONVERTED

Cause: The object <object> of class <objectClass> could not be converted to <javaClass>. The object cannot be converted to given type.

Action: Check that the object being converted is of right type or not.

INCORRECT_DATE_FORMAT

Cause: The date in <dateString> is in an incorrect format. Expected format is YYYY-MM-DD.

Action: Check the date format.

INCORRECT_TIME_FORMAT

Cause: The time in <timeString> is in an incorrect format. Expected format is HH:MM:SS.

Action: Check the time format.

INCORRECT_TIMESTAMP_FORMAT

Cause: The timestamp <timestampString> is in an incorrect format. Expected format is YYYY-MM-DD HH:MM:sprers.euNNN.

Action: Check the timestamp format.

COULD_NOT_CONVERT_TO_BYTE_ARRAY

Cause: The String object must be of even length to be converted to a ByteArray. This object could not be converted to a ByteArray

Action: Check the object being converted.

COULD_NOT_BE_CONVERTED_TO_CLASS

Cause: The object <object> of class <objectClass> could not be converted to <javaClass>. The class <javaClass> is not on the CLASSPATH.

Action: Check that the class <javaClass> is on the CLASSPATH.

SQL_EXCEPTION

Cause: An SQL exception was encountered, thrown by the underlying JDBC bridge. TopLink only wraps that exception.

Action: One must inspect the internal exception thrown.

CONFIGURATION_ERROR_CLASS_NOT_FOUND

Cause: The driver class name was not found.

Action: Check the class name given in JDBCLogin.

DATABASE_ACCESSOR_NOT_CONNECTED

Cause: Session is not connected to the database while doing reading or writing on the database.

Action: An application may have to login again because the connection to the database might have been lost.

ERROR_READING_BLOB_DATA

Cause: Error reading blob data from the database. There are two possibilities for this exception, first is that the blob data was not read properly from the result set or the TopLink could not process the blob data using .

Action: Check if the underlying driver support blobs properly or not and if it does then report this problem to Technical Support.

OULD_NOT_CONVERT_OBJECT_TYPE

Cause: Could not convert object type on internal error. sprers.eu = <type>. The object from the result set cannot be converted to the type returned from the metadata information.

Action: Check if the underlying driver support the conversion type properly or not and if it does then report this problem to Technical Support.

LOGOUT_WHILE_TRANSACTION_IN_PROGRESS

Cause: An attempt has been made to logout while the transaction is still in progress. You cannot logout while a transaction is in progress.

Action: Wait until the transaction is over.

SEQUENCE_TABLE_INFORMATION_NOT_COMPLETE

Cause: The sequence information given to TopLink is not sufficiently complete to get the set of sequence numbers from the database. This usually happens on native sequencing on oracle database.

Action: Check the data given specially the sequence name given in TopLink.

ERROR_PREALLOCATING_SEQUENCE_NUMBERS

Cause: Error preallocating sequence numbers on the database; the sequence table information is not complete.

Action: Check if the sequence table was created on the database properly or not.

CANNOT_REGISTER_SYNCHRONIZATIONLISTENER_ FOR_UNITOFWORK

Cause: Cannot register Synchronization Listener: underlying_exception_string. When the TopLink Session is configured with an , any unit of work requested by a client must operate within the context of a JTS external global transaction. When a unit of work is created and the external global transaction is not in existence or if the system cannot acquire a reference to it, this error is reported.

Action: Ensure that a JTS transaction is in progress before acquiring the unit of work.

SYNCHRONIZED_UNITOFWORK_DOES_NOT_ SUPPORT_COMMITANDRESUME

Cause: Synchronized does not support the operation. When the TopLink Session is configured with an , any unit of work requested by a client must operate within the context of a JTS external global transaction (see Error code: ). The JTS specification does not support the concept of "checkpointing" a transaction, that is, committing the work done and then continuing to work within the same transaction context (JTS does not support nested transactions, either). Thus, if client code invokes on a "synchronized" unit of work, this error will be reported.

Action: None.

CONFIGURATION_ERROR_NEW_INSTANCE_ INSTANTIATION_EXCEPTION

Cause: Configuration error. Attempting to instantiate Driver: <javaClass>. Could not instantiate driver.

Action: Check the driver.

CONFIGURATION_ERROR_NEW_INSTANCE_ILLEGAL_ ACCESS_EXCEPTION

Cause: A configuration error occurred while attempting to instantiate . Could not instantiate driver.

Action: Check the driver.

TRANSACTION_MANAGER_NOT_SET_FOR_JTS_DRIVER

Cause: The transaction manager has not been set for the .

Action: Set a transaction manager for the .

NO_VERSION_NUMBER_WHEN_DELETING

Cause: An attempt was made to delete the object <object> but it has no version number in the identity map. This object either was never read or has already been deleted.

Action: Logging SQL is very helpful in understanding the reason why the exception is thrown. The last delete will show the object we are deleting that throws an exception.

OBJECT_CHANGED_SINCE_LAST_READ_WHEN_DELETING

Cause: The object state has changed in the database. The object <object> cannot be deleted because it has changed or been deleted since it was last read. This usually means that the row in the table was changed by some other application.

Action: Refreshing an object will refresh the object with the new data from the database.

NO_VERSION_NUMBER_WHEN_UPDATING

Cause: An attempt has been made to update the object <object> but it has no version number in the identity map. It may not have been read before being updated or has been deleted.

Action: Logging SQL is very helpful in understanding the reason why the exception is thrown. The last update will show the object we are updating that throws an exception.

OBJECT_CHANGED_SINCE_LAST_READ_WHEN_UPDATING

Cause: The object state has changed in the database. The object <object> cannot be updated because it has changed or been deleted since it was last read. This usually means that the row in the table was changed by some other application.

Action: Refreshing an object will refresh the object with the new data from the database.

MUST_HAVE_MAPPING_WHEN_IN_OBJECT

Cause: The object <aClass> must have a non-read-only mapping corresponding to the version lock field. The mapping was not defined for the locking field. It is needed when the lock value is stored in the domain object than in a cache.

Action: Define a mapping for the field.

NEED_TO_MAP_JAVA_SQL_TIMESTAMP

Cause: A write lock value which is stored in a domain object is not an instance of.

Action: Change the value of the attribute to be an instance of .

ADDITIONAL_SIZE_QUERY_NOT_SPECIFIED

Cause: Cursored SQL queries must provide an additional query to retrieve the size of the result set. Custom queries using cursor streams and not specifying the size query will cause this exception. The size query is used to retrieve the size of the number of object read from the database. This is done on JDBC compatible drivers because it provides no way to extract the size of the result set read. Non custom queries using cursor streams will have default queries generated by TopLink.

Action: Specify a size query.

AGGREGATE_OBJECT_CANNOT_BE_DELETED

Cause: Aggregated objects cannot be written or deleted independent of their owners. There is no identity maintained on such objects.

Action: Application's discretion.

ARGUMENT_SIZE_MISMATCH_IN_QUERY_AND_ QUERY_DEFINITION

Cause: The number of arguments provided to the query for execution does not match the number of arguments provided with the query definition.

Action: Check the query and query execution.

BACKUP_CLONE_IS_ORIGINAL_FROM_PARENT

Cause: The object of class with identity hashcode is not from this unit of work space but from the parent session. The object was never registered in this unit of work but read from the parent session and related to an object registered in the unit of work.

Action: Ensure that you are correctly registering your objects. If you are still having problems, you can use the method to help debug where the error occurred. Please see the manual and FAQ for more information.

BACKUP_CLONE_IS_ORIGINAL_FROM_SELF

Cause: The object clone of class with identity hashcode is the original to a registered new object. The unit of work clones registered new objects, so you must ensure that it is registered before it is reference by another object. If you do not want the new object to be cloned, used the U API.

Action: Ensure that you are correctly registering your objects. If you are still having problems, you can use the method to help debug where the error occurred. Please see the manual and FAQ for more information.

BATCH_READING_NOT_SUPPORTED

Cause: This mapping does not support batch reading. The optimization of batching the read of all the target rows is not supported for the mapping.

Action: The problem is a TopLink development problem and user should never encounter this unless the mapping is a new custom mapping. Contact Technical Support.

DESCRIPTOR_IS_MISSING

Cause: Missing descriptor for <reference Class>. The descriptor related to the class or the object is not found in the session.

Action: Check if the related descriptor was added to the session or the query is done on the right object or class.

DESCRIPTOR_IS_MISSING_FOR_NAMED_QUERY

Cause: Missing descriptor for <domain Class Name> for query named <queryName>. 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.

INCORRECT_SIZE_QUERY_FOR_CURSOR_STREAM

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.

INVALID_QUERY

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.

INVALID_QUERY_KEY_IN_EXPRESSION

Cause: The query key <key> does not exist. 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.

INVALID_QUERY_ON_SERVER_SESSION

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.

Action: Use client session's unit of work to change the object.

NO_CONCRETE_CLASS_INDICATED

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.

NO_CURSOR_SUPPORT

Cause: No cursor support provided for abstract class multiple table descriptors using expressions.

Action: Consider using custom SQL or multiple queries. <query>

OBJECT_TO_INSERT_IS_EMPTY

Cause: There are no fields to be insert into the table. The fields to insert into the table, <table> is empty. You must define at least one mapping for this table

Action: Must define at least one mapping for this table.

OBJECT_TO_MODIFY_NOT_SPECIFIED

Cause: An object to modify is required for a modify query.

Action: Ensure the query contains an object before executing.

QUERY_NOT_DEFINED

Cause: Query is not defined. When executing query on the session the parameter which takes query is null.

Action: Check if the query is passed properly.

QUERY_SENT_TO_INACTIVE_UNIT_OF_WORK

Cause: The unit of work has been released and is now inactive.

Action: The unit of work, once released, cannot be reused unless commitAndResume is called.

READ_BEYOND_QUERY

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.

REFERENCE_CLASS_MISSING

Cause: The reference class in the query is not specified. A reference class must be provided.

Action: Check the query.

REFRESH_NOT_POSSIBLE_WITHOUT_CACHE

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.

Action: Check query.

SIZE_ONLY_SUPPORTED_ON_EXPRESSION_QUERIES

Cause: Did not find size query. Size only supported on expression queries, unless a size query is given.

Action: Cursor streams on custom query should also define size query.

SQL_STATEMENT_NOT_SET_PROPERLY

Cause: The SQL statement has not been properly set. The user should never encounter this unless queries have been customized.

Action: Contact Technical Support.

INVALID_QUERY_ITEM

Cause: Invalid query item expression.

Action: Validate the Expression being used.

SELECTION_OBJECT_CANNOT_BE_NULL

Cause: The selection object passed to a read object or refresh was null.

Action: Check on the read query.

UNNAMED_QUERY_ON_SESSION_BROKER

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.

REPORT_RESULT_WITHOUT_PKS

Cause: ReportQuery without PKs cannot readObject. 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 on report query.

NULL_PRIMARY_KEY_IN_BUILDING_OBJECT

Cause: The primary key read from the row, <databaseRow> during the execution of the query was detected to be null; primary keys must not contain null.

Action: Check query and also the table on the database.

NO_DESCRIPTOR_FOR_SUBCLASS

Cause: The subclass has no descriptor defined for it.

Action: Check session if the descriptor was added or not or else check class extraction method.

CANNOT_DELETE_READ_ONLY_OBJECT

Cause: Cannot delete an object of read-only class. The class <className> is declared read-only in this unit of work. Thrown in unit of work when trying to delete an object that is marked as read only.

Action: Contact Technical Support.

INVALID_OPERATOR

Cause: The operator <data> used in the expression is not valid.

Action: Check class to see a list of all of the operators supported.

ILLEGAL_USE_OF_GETFIELD

Cause: Illegal use of <data> in expression. This is a TopLink development exception that users should not encounter.

Action: Report this problem to Technical Support.

ILLEGAL_USE_OF_GETTABLE

Cause: Illegal use of <data> in expression. This is a TopLink development exception that users should not encounter.

Action: Report this problem to Technical Support.

REPORT_QUERY_RESULT_SIZE_MISMATCH

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.

CANNOT_CACHE_PARTIAL_OBJECT

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 .

Action: Call the method before executing the query.

OUTER_JOIN_ONLY_VALID_FOR_ONE_TO_ONE

Cause: An outer join () is only valid for one to one mappings, and cannot be used for the mapping.

Action: Do not attempt to use for mappings other than one to one.

CANNOT_ADD_TO_CONTAINER

Cause: Cannot add <anObject> to a <containerClass> using <policy>. This is TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Contact Technical Support.

METHOD_INVOCATION_FAILED

Cause: The method invocation of <aMethod> on the object <anObject> threw a Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

CANNOT_CREATE_CLONE

Cause: Cannot create a clone of <anObject> using <policy>. This is a TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Report this problem to Technical Support.

METHOD_NOT_VALID

Cause: The method <methodName> is not valid to call on object <aReceiver>. This is a TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Contact Technical Support.

METHOD_DOES_NOT_EXIST_IN_CONTAINER_CLASS

Cause: The method named <methodName> was not found in class <aClass>. Thrown when looking for clone method on the container class. The clone is needed to create clones of the container in unit of work.

Action: Define clone method on the container class.

COULD_NOT_INSTANTIATE_CONTAINER_CLASS

Cause: The class <aClass> cannot be used as the container for the results of a query since it cannot be instantiated. Thrown when new interface container policy is being created using Java reflection.

Action: Check Java documentation on the internal exception.

MAP_KEY_NOT_COMPARABLE

Cause: Could not use object <anObject> of type <objectClass> as a key into <aContainer> which is of type <containerClass>. Key cannot be compared with the keys currently in the map. Throws Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

CANNOT_ACCESS_METHOD_ON_OBJECT

Cause: Cannot reflectively access the method <aMethod> for object: <anObject> of type <anObjectClass>. Throws Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

CALLED_METHOD_THREW_EXCEPTION

Cause: The method <aMethod> was called reflectively on object <object> of class <objectClass> and threw an exception. Throws Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

INVALID_OPERATION

Cause: Invalid operation <operation> on cursor. The operation is not supported.

Action: Check the class documentation and look for the corresponding method that should be used.

CANNOT_REMOVE_FROM_CONTAINER

Cause: Cannot remove <anObject> of type <anObjectClass> from <aContainerClass> using <policy>. This is TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Contact Technical Support.

CANNOT_ADD_ELEMENT

Cause: Cannot add element to the collection container policy (cannot add <anObject> of type <anObjectClass> to a <aContainerClass>).

Action: Check Java documentation on the internal exception.

BACKUP_CLONE_DELETED

Cause: Deleted objects cannot have reference after being deleted. The object clone of class <sprers.euss()> with identity hashcode (sprers.eutyHashCode()) <sprers.eutyHashCode(clone)> has been deleted, but still has references.

Action: Ensure that you are correctly registering your objects. If you are still having problems, you can use the method to help debug where the error occurred. Please see the manual and FAQ for more information.

CANNOT_COMPARE_TABLES_IN_EXPRESSION

Cause: Cannot compare table reference to <data> in expression

Action: Check the expression

INVALID_TABLE_FOR_FIELD_IN_EXPRESSION

Cause: Field has invalid table in this context for field <data> in expression.

Action: Check the expression

INVALID_USE_OF_TO_MANY_QUERY_KEY_IN_EXPRESSION

Cause: Invalid use of a query key representing a to-many relationship <data> in expression. Use rather than .

Action: Use the operator instead of .

INVALID_USE_OF_ANY_OF_IN_EXPRESSION

Cause: Invalid use of for a query key not representing a to-many relationship <data> in expression. Use rather than .

Action: Use the operator instead of .

CANNOT_QUERY_ACROSS_VARIABLE_ONE_TO_ ONE_MAPPING

Cause: Querying across a variable one-to-one mapping is not supported.

Action: Change the expression such that the query in not done across a variable one to one mapping.

ILL_FORMED_EXPRESSION

Cause: Ill-formed expression in query, attempting to print an object reference into a SQL statement for <queryKey>.

Action: Contact Technical Support.

CANNOT_CONFORM_EXPRESSION

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.

INVALID_OPERATOR_FOR_OBJECT_EXPRESSION

Cause: Object comparisons can only use the or operators, other comparisons must be done through query keys or direct attribute level comparisons.

Action: Ensure the query uses only and if object comparisons are being used.

UNSUPPORTED_MAPPING_FOR_OBJECT_COMPARISON

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.

OBJECT_COMPARISON_CANNOT_BE_PARAMETERIZED

Cause: Object comparisons cannot be used in parameter queries.

Action: Change the query such that it does not attempt to use object when using parameterized queries.

INCORRECT_CLASS_FOR_OBJECT_COMPARISON

Cause: The class of the argument for the object comparison is incorrect.

Action: Ensure the class for the query is correct.

CANNOT_COMPARE_TARGET_FOREIGN_KEYS_ TO_NULL

Cause: Object comparison cannot be used for target foreign key relationships. Query on the source primary key instead.

Action: Query on source primary key.

INVALID_DATABASE_CALL

Cause: Invalid database call - the call must be an instance of DatabaseCall: <call>.

Action: Ensure the call being used is a DatabaseCall.

INVALID_DATABASE_ACCESSOR

Cause: Invalid database accessor - the accessor must be an instance of DatabaseAccessor: <accessor>.

Action: Ensure the accessor being used is a DatabaseAccessor.

METHOD_DOES_NOT_EXIST_ON_EXPRESSION

Cause: Method: <methodName> with argument types: <argTypes> cannot be invoked on Expression.

Action: Ensure the method being used is a supported method.

IN_CANNOT_BE_PARAMETERIZED

Cause: Queries using IN cannot be parameterized.

Action: Either disable the query prepare or binding.

REDIRECTION_CLASS_OR_METHOD_NOT_SET

Cause: The redirection query was not configured properly, the class or method name was not set.

Action: Check the configuration for the redirection class.

REDIRECTION_METHOD_NOT_DEFINED_CORRECTLY

Cause: The redirection query's method is not defined or define with the wrong arguments. It must be public static and have arguments DatabaseQuery, DatabaseRow, Session (the interface).

Action: Check the redirection query's method as above.

REDIRECTION_METHOD_ERROR

Cause: The redirection query's method invocation threw an exception.

Action: Check the redirection method for problems.

EXAMPLE_AND_REFERENCE_OBJECT_CLASS_MISMATCH

Cause: There is a class mismatch between the example object and the reference class specified for this query.

Action:

0 Comments

Leave a Comment