Validation Exceptions (7001 – 7147)

ValidationException is a development exception that is raised when an incorrect state is detected or an API is used incorrectly.

Format

EXCEPTION [TOPLINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

Example 13-7 Validation Exception

EXCEPTION [TOPLINK – 7008]: oracle.toplink.exceptions.ValidationException
EXCEPTION DESCRIPTION: The Java type javaClass is not a valid database type. The Java type of the field to be written to the database has no corresponding type on the database.

7001: LOGIN_BEFORE_ALLOCATING_CLIENT_SESSIONS: Cause: You attempted to allocate client sessions before logging into the server.; Action: Ensure you have called login method on your server session or database session. This error also appears in multi threaded environments as a result of concurrency issues. Check that all your threads are synchronized.

7002: POOL_NAME_DOES_NOT_EXIST: Cause: The pool name used while acquiring client session from the server session does not exist.; Action: Verify the pool name given while acquiring client session and all the existing pools on the server session.

7003: MAX_SIZE_LESS_THAN_MIN_SIZE: Cause: The maximum number of connections in a connection pool should be more than the minimum number of connections.; Action: Check addConnectionPool(String poolName, JDBCLogin login, int minNumberOfConnections, int maxNumberOfConnections) method on the server session.

7004: POOLS_MUST_BE_CONFIGURED_BEFORE_LOGIN: Cause: Pools must all be added before login on the server session has been done. Once logged in, you cannot add pools.; Action: Check addConnectionPool(String poolName, JDBCLogin login, int minNumberOfConnections, int maxNumberOfConnections) on server session. This method should be called before logging in on the server session.

7008: JAVA_TYPE_IS_NOT_A_VALID_DATABASE_TYPE: Cause: The Java type javaClass is not a valid database type. The Java type of the field to be written to the database has no corresponding type on the database.; Action: Check the table or stored procedure definition.

7009: MISSING_DESCRIPTOR: Cause: The descriptor className is not found in the session.; Action: Ensure that the related descriptor to the class was properly registered with the session.

7010: START_INDEX_OUT_OF_RANGE: Cause: This is a TopLink development exception and users should never encounter this problem. It happens when a copy of a vector is created with a start and end index.; Action: Report this problem to Oracle Support Services.

7011: STOP_INDEX_OUT_OF_RANGE: Cause: This is a TopLink development exception and users should never encounter this problem. It happens when a copy of a vector is created with a start and end index.; Action: Report this problem to Oracle Support Services.

7012: FATAL_ERROR_OCCURRED: Cause: This is a TopLink development exception and users should never encounter this problem. It happens when test cases are executed.; Action: Report this problem to Oracle Support Services. This error commonly occurs if you attempt to call the commit method on an invalid (or previously committed) unit of work.
If cannotCommitUOWAgain method of ValidationException appears in the stack trace, verify that the commit method was called on valid UnitOfWork instances.

7013: NO_PROPERTIES_FILE_FOUND: Cause: The toplink.properties file cannot be found on the system classpath.; Action: Ensure that there is a toplink.properties file located on the system classpath.

7017: CHILD_DESCRIPTORS_DO_NOT_HAVE_IDENTITY_MAP: Cause: An identity map is added to the child descriptor. A child descriptor shares its parent's identity map.; Action: Check the child descriptor and remove the identity map from it.

7018: FILE_ERROR: Cause: The user should never encounter this problem. It happens when test cases are executed.; Action: Contact Oracle Support Services.

7023: INCORRECT_LOGIN_INSTANCE_PROVIDED: Cause: The login instance provided to the login method is incorrect. A JDBCLogin must be provided.; Action: Use a JDBCLogin.

7024: INVALID_MERGE_POLICY: Cause: This is a TopLink development exception and users should never encounter it.; Action: Contact Oracle Support Services.

7025: ONLY_FIELDS_ARE_VALID_KEYS_FOR_ DATABASE_ROWS: Cause: The key on the database row is not either of type String or of type DatabaseField.; Action: Contact Oracle Support Services.

7027: SEQUENCE_SETUP_INCORRECTLY: Cause: The sequence sequenceName is set up incorrectly, increment does not match pre-allocation size.; Action: Contact Oracle Support Services.

7028: WRITE_OBJECT_NOT_ALLOWED_IN_UNIT_OF_WORK: Cause: A writeObject() method is not allowed in a UnitOfWork.; Action: Ensure that a writeObject() method is not in the UnitOfWork.

7030: CANNOT_SET_READ_POOL_SIZE_AFTER_LOGIN: Cause: TopLink is unable to set read pool size after the server session has already been logged in.; Action: The size should be set before login.

7031: CANNOT_ADD_DESCRIPTORS_TO_SESSION_BROKER: Cause: TopLink cannot add descriptors to a session broker.; Action: Descriptors are added to the sessions contained in the session broker.

7032: NO_SESSION_REGISTERED_FOR_CLASS: Cause: The descriptor related to the domain class domainClass was not found in any of the sessions registered in the session broker.; Action: Check the sessions.

7033: NO_SESSION_REGISTERED_FOR_NAME: Cause: The session with the given name sessionName is not registered in the session broker.; Action: Check the session broker.

7038: LOG_IO_ERROR: Cause: Error while logging message to session's log.; Action: Check the internal exception.

7039: CANNOT_REMOVE_FROM_READ_ONLY_CLASSES_ IN_NESTED_UNIT_OF_WORK: Cause: TopLink is unable to remove from the set of read-only classes in a nested unit of work. A nested unit of work's set of read-only classes must be equal to or be a superset of its parent's set of read-only classes.; Action: Contact Oracle Support Services.

7040: CANNOT_MODIFY_READ_ONLY_CLASSES_SET_ AFTER_USING_UNIT_OF_WORK: Cause: TopLink is unable to change the set of read-only classes in a unit of work after that unit of work has been used. Changes to the read-only set must be made when acquiring the unit of work or immediately after.; Action: Contact Oracle Support Services.

7042: PLATFORM_CLASS_NOT_FOUND: Cause: The platform class className was not found and a reflection exception is raised.; Action: Check the internal exception.

7043: NO_TABLES_TO_CREATE: Cause: A project does not have any tables to create on the database.; Action: Validate the project and tables you are attempting to create.

7044: ILLEGAL_CONTAINER_CLASS: Cause: The container class specified className cannot be used as the container because it does not implement the Collection or Map interfaces.; Action: Implement either the Collection or Map interfaces in the container class.

7047: CONTAINER_POLICY_DOES_NOT_USE_KEYS: Cause: Invalid Map class was specified for the container policy. The container specified (of Class aPolicyContainerClass) does not require keys. You tried to use methodName.; Action: Use map class that implements the Map interface.

7048: METHOD_NOT_DECLARED_IN_ITEM_CLASS: Cause: The key method on the map container policy is not defined. The instance method <methodName> does not exist in the reference class <className> and therefore cannot be used to create a key in a map. A map container policy represents how to handle an indexed collection of objects. Usually the key is the primary key of the objects stored, so the policy needs to know the name of the primary key get method, to extract it from each object using reflection. For instance a user might call policy.setKeyMethodName("getId").; Action: Check the second parameter of the useMapClass method of DatabaseQuery.

7051: MISSING_MAPPING: Cause: Missing the attribute attributeName for descriptor descriptor called from source. This is a TopLink development exception and a user should never encounter it.; Action: Contact Oracle Support Services.

7052: ILLEGAL_USE_OF_MAP_IN_DIRECTCOLLECTION: Cause: The method useMapClass was called on a DirectCollectionMapping. It is invalid to call the useMapClass method on a DirectCollectionMapping. TopLink cannot instantiate Java attributes mapped using a DirectCollectionMapping with a map. The useMapClass method is supported for OneToManyMappings and ManyToManyMappings. The Java 2 Collection interface is supported using the useCollectionClass method.; Action: Use the useCollectionClass method. Do not call the useMapClass method on DirectCollectionMapping.

7053: CANNOT_RELEASE_NON_CLIENTSESSION: Cause: TopLink is unable to release a session that is not a client session. Only client sessions can be released.; Action: Modify the code to ensure the client session is not released.

7054: CANNOT_ACQUIRE_CLIENTSESSION_FROM_SESSION: Cause: TopLink is unable to acquire a session that is not a client session. Client sessions can be acquired only from server sessions.; Action: Modify the code to ensure an acquire session is attempted only from server sessions.

7055: OPTIMISTIC_LOCKING_NOT_SUPPORTED: Cause: Optimistic locking is not supported with stored procedure generation.; Action: Do not use OptimisticLocking with stored procedure generation.

7056: WRONG_OBJECT_REGISTERED: Cause: The wrong object was registered into the unit of work. It should be the object from the parent cache.; Action: Ensure that the object is from the parent cache.

7058: INVALID_CONNECTOR: Cause: The connector selected is invalid and must be of type DefaultConnector.; Action: Ensure that the connector is of type DefaultConnector.

7059: INVALID_DATA_SOURCE_NAME: Cause: Invalid data source name: name.; Action: Verify the data source name.

7060: CANNOT_ACQUIRE_DATA_SOURCE

Cause: TopLink is unable to acquire the data source name or an error has occurred in setting up the data source.

Action: Verify the data source name. Check the nested SQL exception to determine the cause of the error. Typical problems include:

The connection pool was not configured in your config.xml file.
The driver is not on the classpath.
The user or password is incorrect.
The database server URL or driver name is not properly specified.

7061: JTS_EXCEPTION_RAISED: Cause: An exception occurred within the Java Transaction Service (JTS).; Action: Examine the JTS exception and see the JTS documentation.

7062: FIELD_LEVEL_LOCKING_NOTSUPPORTED_ OUTSIDE_A_UNIT_OF_WORK: Cause: FieldLevelLocking is not supported outside a unit of work. In order to use field-level locking, a unit of work must be used for all write operations.; Action: Use a unit of work for writing.

7063: EJB_CONTAINER_EXCEPTION_RAISED: Cause: An exception occurred within the EJB container.; Action: Examine the EJB exception and see the JTS documentation.

7064: EJB_PRIMARY_KEY_REFLECTION_EXCEPTION: Cause: An exception occurred in the reflective EJB bean primary key extraction.; Action: Ensure that your primary key object is defined correctly.

7065: EJB_CANNOT_LOAD_REMOTE_CLASS: Cause: The remote class for the bean cannot be loaded or found, for the bean.; Action: Ensure that the correct class loader is set correctly.

7066: EJB_MUST_BE_IN_TRANSACTION: Cause: TopLink is unable to create or remove beans unless a JTS transaction is present, bean=bean.; Action: Ensure that the JTS transaction is present.

7068: EJB_INVALID_PROJECT_CLASS: Cause: The platform class platformName was not found for the projectName using the default class loader.; Action: Validate the project and platform.

7069: PROJECT_AMENDMENT_EXCEPTION_OCCURED: Cause: An exception occurred while looking up or invoking the project amendment method, amendmentMethod on the class amendmentClass.; Action: Validate the amendment method and class.

7070: EJB_TOPLINK_PROPERTIES_NOT_FOUND: Cause: A toplink.properties resource bundle must be located on the classpath in a TopLink directory.; Action: Validate the classpath and the location of the TopLink resource bundle.

7071: CANT_HAVE_UNBOUND_IN_OUTPUT_ARGUMENTS: Cause: You cannot use input or output parameters without using binding.; Action: Use binding on the StoredProcedureCall.

7072: EJB_INVALID_PLATFORM_CLASS: Cause: SessionManager failed to load the class identified by the value associated with properties platform-class or external-transaction-controller-class during initialization when it loads the TopLink session common properties from the TopLink global properties file (sessions.xml for non-EJB applications or toplink-ejb-jar.xml for EJB applications).; Action: Ensure that your TopLink global properties file is correctly configured. Pay particular attention to the platform-class and external-transaction-controller-class properties.

7073: ORACLE_OBJECT_TYPE_NOT_DEFINED: Cause: The Oracle object type with type name typeName is not defined.; Action: Ensure that the Oracle object type is defined.

7074: ORACLE_OBJECT_TYPE_NAME_NOT_DEFINED: Cause: The Oracle object type typeName is not defined.; Action: Ensure that the Oracle object type is defined.

7075: ORACLE_VARRAY_MAXIMIM_SIZE_NOT_DEFINED: Cause: The Oracle VARRAY type typeName maximum size is not defined.; Action: Verify the maximum size for the Oracle VARRAY.

7076: DESCRIPTOR_MUST_NOT_BE_INITIALIZED: Cause: When generating the project class, the descriptors must not be initialized.; Action: Ensure that the descriptors are not initialized before generating the project class.

7077: EJB_INVALID_FINDER_ON_HOME: Cause: The home interface toString method specified during creation of BMPWrapperPolicy does not contain a correct findByPrimaryKey method. A findByPrimaryKey method must exist that takes the PrimaryKey class for this bean.; Action: Ensure that a findByPrimaryKey method exists and is correct.

7078: EJB_NO_SUCH_SESSION_SPECIFIED_IN_PROPERTIES: Cause: The sessionName specified on the deployment descriptor does not match any session specified in the toplink.properties file.; Action: Contact Oracle Support Services.

7079: EJB_DESCRIPTOR_NOT_FOUND_IN_SESSION: Cause: The descriptor was not found in the session.; Action: Check the project being used for this session.

7080: EJB_FINDER_EXCEPTION: Cause: A FinderException is raised when attempting to load an object from the class with the primary key.; Action: Contact Oracle Support Services.

7081: CANNOT_REGISTER_AGGREGATE_OBJECT_IN_ UNIT_OF_ WORK: Cause: The aggregate object cannot be directly registered in the unit of work. It must be associated with the source (owner) object.; Action: Contact Oracle Support Services.

7082: MULTIPLE_PROJECTS_SPECIFIED_IN_PROPERTIES: Cause: The toplink.properties file specified multiple project files for the server. Only one project file can be specified.; Action: Specify either projectClass, projectFile, or xmlProjectFile.

7083: NO_PROJECT_SPECIFIED_IN_PROPERTIES: Cause: The toplink.properties file does not include any information on the TopLink project to use for the server. One project file must be specified.; Action: Specify either projectClass, projectFile, or xmlProjectFile.

7084: INVALID_FILE_TYPE: Cause: The specified file is not a valid type for reading. ProjectReader must be given the deployed XML project file.; Action: Contact Oracle Support Services.

7085: SUB_SESSION_NOT_DEFINED_FOR_BROKER: Cause: Unable to create an instance of the external transaction controller specified in the properties file.; Action: Contact Oracle Support Services.

7086: EJB_INVALID_SESSION_TYPE_CLASS: Cause: The session manager cannot load the class corresponding to the session's type class name.; Action: Ensure that the class name of the session's type is fully qualified in the sessions.xml file or toplink.properties file.

7087: EJB_SESSION_TYPE_CLASS_NOT_FOUND: Cause: The session manager cannot load the class corresponding to the session's type class name.; Action: Ensure that the class name of the session's type is fully qualified in the sessions.xml file or toplink.properties file.

7088: CANNOT_CREATE_EXTERNAL_TRANSACTION_ CONTROLLER: Cause: The session manager cannot load the class corresponding to the external transaction controller's class name.; Action: Ensure that the class name of the external transaction controller is valid and fully qualified in the sessions.xml file or toplink.properties file.

7089: SESSION_AMENDMENT_EXCEPTION_OCCURED: Cause: The session manager cannot load the class corresponding to the amendment class name, or it cannot load the method on the amendment class corresponding to the amendment method name.; Action: Ensure that the class name of the amendment class is fully qualified, and the amendment method exists in the amendment class in the sessions.xml file or toplink.properties file.

7091: SET_LISTENER_CLASSES_EXCEPTION: Cause: TopLink is unable to create the listener class that implements SessionEventListener for the internal use of SessionXMLProject.; Action: Contact Oracle Support Services.

7092: EXISTING_QUERY_TYPE_CONFLICT: Cause: TopLink has detected a conflict between a custom query with the same name and arguments to a session.; Action: Ensure that no query is added to the session more than once or change the query name so that the query can be distinguished from others.

7093: QUERY_ARGUMENT_TYPE_NOT_FOUND: Cause: TopLink is unable to create an instance of the query argument type.; Action: Ensure that the argument type is a fully qualified class name and the argument class is included in the classpath environment.

7094: ERROR_IN_SESSION_XML: Cause: The sessions.xml or toplink.properties files cannot be loaded.; Action: Ensure that the path to either of the files exists on the classpath environment.

7095: NO_SESSIONS_XML_FOUND: Cause: The sessions.xml or toplink.properties files cannot be loaded.; Action: Ensure that the path to either of the files exists on the classpath environment. The sessions.xml should be included in the root of the deployed JAR file. When using a WAR file, the sessions.xml file should be located in the WEB-INF\classes directory. When using EJB 3.0, TopLink automatically loads the ejb3-toplink-sessions.xml file.

7096: CANNOT_COMMIT_UOW_AGAIN: Cause: TopLink cannot invoke commit method on an inactive unit of work that was committed or released.; Action: Ensure you invoke commit method on a new unit of work or invoke commitAndResume method so that the unit of work can be reused. For more information about the commitAndResume method, see Oracle TopLink API Reference.

7097: OPERATION_NOT_SUPPORTED: Cause: TopLink cannot invoke a nonsupport operation on an object.; Action: Do not use the operation indicated in the stack trace.

7099: PROJECT_XML_NOT_FOUND: Cause: The file name specified for the XML-based project is incorrect.; Action: Verify the name and location of the file.

7101: NO_TOPLINK_EJB_JAR_XML_FOUND: Cause: The toplink-ejb-jar.xml file was not found.; Action: Ensure that the file is on your classpath.

7102: NULL_CACHE_KEY_FOUND_ON_REMOVAL: Cause: Encountered a null value for a cache key while attempting to remove an object from the identity map. The most likely cause of this situation is that the object has already been garbage-collected and therefore does not exist within the identity map.; Action: Ignore. The removeFromIdentityMap method of the Session is intended to allow garbage collection, which has already been done.

7103: NULL_UNDERLYING_VALUEHOLDER_VALUE: Cause: A null reference was encountered while attempting to invoke a method on an object that uses proxy indirection.; Action: Please check that this object is not null before invoking its methods.

7104: INVALID_SEQUENCING_LOGIN: Cause: A separate connection(s) for sequencing was requested but the sequencing login uses the external transaction controller.; Action: Either provide a sequencing login that does not use an external transaction controller or do not use separate connection(s) for sequencing.

7105: INVALID_ENCRYPTION_CLASS: Cause: Error encountered while converting encryption class.; Action: Ensure the encryption class name is correctly specified in the sessions.xml file and that the encryption class specified is available on the classpath. A common reason for this exception is the usage of JDK 1.3 and earlier versions. The TopLink JCE encryption mechanism requires JDK 1.4 and higher (or JDK 1.3 configured with the JCE plug-in) to function properly.

7106: ERROR_ENCRYPTING_PASSWORD: Cause: Error encountered during password string encryption.; Action: An error is raised while trying to encrypt the password string. A common reason for this exception is the usage of JDK 1.3 and earlier versions. The TopLink JCE encryption mechanism requires JDK 1.4 and higher (or JDK 1.3 configured with the JCE plug-in) to function properly.

7107: ERROR_DECRYPTING_PASSWORD: Cause: Error encountered during password string decryption.; Action: An exception was raised while trying to decrypt the password string. A common reason for this exception is the usage of JDK 1.3 and earlier versions. The TopLink JCE encryption mechanism requires JDK 1.4 and higher (or JDK 1.3 configured with the JCE plug-in) to function properly.

7108: NOT_SUPPORTED_FOR_DATASOURCE: Cause: This operation is not supported for non-relational platforms.; Action: Do not use this operation on the current platform, or use a relational database platform.

7109: PROJECT_LOGIN_IS_NULL: Cause: The login in the project used to create the session is null. The login used for the project must be a valid login.; Action: No login was specified for the TopLink project. A valid login must be included on any TopLink project. Login information can be added using TopLink Workbench or using Java code.

7110: HISTORICAL_SESSION_ONLY_SUPPORTED_ON_ORACLE: Cause: At present HistoricalSession only works with Oracle 9R2 or later databases, as it uses the Oracle database Flashback feature.; Action: Generic History Support (see oracle.toplink.history.HistoryPolicy) works for any database. If a HistoryPolicy is incorrectly set, TopLink may be defaulting to using flashback instead. An AsOfSCNClause is implicitly flashback only.

7111: CANNOT_ACQUIRE_HISTORICAL_SESSION: Cause: You may not acquire a HistoricalSession from a unit of work, another HistoricalSession, a ServerSession, or a ServerSessionBroker. You may acquire one from a regular session, a ClientSession, or a ClientSessionBroker.; Action: To recover objects, read the objects in both a HistoricalSession and UnitOfWork, and call mergeCloneWithReferences(historicalObject) method on the UnitOfWork.

7112: FEATURE_NOT_SUPPORTED_IN_JDK_VERSION: Cause: You have specified that TopLink use a feature, but this feature is not available in the current JDK version.; Action: You must use the version of the JDK that supports this feature.

7113: PLATFORM_DOES_NOT_SUPPORT_CALL_WITH_RETURNING: Cause: Platform does not support call with returning.; Action: Set stored procedures with output parameters in setInsertQuery, setInsertCall, setUpdateQuery, or setUpdateCall methods of the DescriptorQueryManager.

7114: ISOLATED_DATA_NOT_SUPPORTED_IN_CLIENTSESSIONBROKER: Cause: Isolated data is not currently supported within a ClientSessionBroker. Session contains descriptors representing isolated data.; Action: Ensure that isolated data is not used.

7115: CLIENT_SESSION_CANNOT_USE_EXCLUSIVE_CONNECTION: Cause: An ExclusiveConnection cannot be used for ClientSession reads without isolated data.; Action: You must update the ConnectionPolicy used, to remove ExclusiveConnection configuration or the project to set certain data to be exclusive.

7116: INVALID_METHOD_ARGUMENTS: Cause: Invalid arguments are used in the method.; Action: Refer to the public API of the calling method and use valid values for the arguments.

7117: MULTIPLE_CURSORS_NOT_SUPPORTED: Cause: There is an attempt to use more than one cursor in a SQLCall.; Action: TopLink currently supports only one cursor per call.

7118: WRONG_USAGE_OF_SET_CUSTOM_SQL_ARGUMENT_TYPE_METOD: Cause: The setCustomSQLArgumentType method was invoked on SQLCall, but this method does not use custom SQL.; Action: Don't call this method on SQLCall that doesn't use custom SQL.

7119: CANNOT_TRANSLATE_UNPREPARED_CALL: Cause: Unprepared SQLCall attempted translation.; Action: SQLCall must be prepared before translation.

7120: CANNOT_SET_CURSOR_FOR_PARAMETER_TYPE_OTHER_THAN_OUT: Cause: Parameter in SQLCall cannot be used as a cursor, because it is has parameter type other than OUT.; Action: Parameter used as a cursor must have parameter type OUT.

7121: PLATFORM_DOES_NOT_SUPPORT_STORED_FUNCTIONS: Cause: Platform does not support stored functions.; Action: Do not define stored functions on this platform.

7122: EXCLUSIVE_CONNECTION_NO_LONGER_AVAILABLE: Cause: The exclusive connection associated with the session is unavailable for the query on the object.; Action: Isolated objects with indirection read through an ExclusiveIsolatedClientSession must not have indirection triggered after the ExclusiveIsolatedClientSession has been released. Re-read the objects through the current ExclusiveIsolatedClientSession.

7123: UNIT_OF_WORK_IN_TRANSACTION_COMMIT_PENDING: Cause: A successful writeChanges operation has been called on this UnitOfWork. As the commit process has been started but not yet finalized, the only supported operations now are commit, commitAndResume, release, any non-object level query, or SQLCall execution. The operation is not allowed at this time.; Action: Execute one of the supported operations to continue.

7124: UNIT_OF_WORK_AFTER_WRITE_CHANGES_FAILED: Cause: An unsuccessful writeChanges operation has been called on this UnitOfWork. Given the possibility that partial changes have been written to the data store but not rolled back (if inside external transaction), the only supported operations now are release, global transaction rollback, any non-object level query or SQLCall execution.; Action: Determine the cause of the original failure and retry in a new UnitOfWork.

7125: INACTIVE_UNIT_OF_WORK: Cause: Once the UnitOfWork has been committed and/or released, no further operation should be performed on it.; Action: Acquire a new UnitOfWork, or use the commitAndResume method instead of commit method in the future.

7126: CANNOT_WRITE_CHANGES_ON_NESTED_UNIT_OF_WORK: Cause: The writeChanges method cannot be called on a NestedUnitOfWork. A nested UnitOfWork never writes changes directly to the data store, only the parent UnitOfWork does.; Action: Call the commit method instead, and then the writeChanges method on the parent UnitOfWork.

7127: CANNOT_WRITE_CHANGES_TWICE: Cause: You can only writes changes to the data store once.; Action: You must either roll back the transaction, or call the commit method on this UnitOfWork and start a new one.

7128: ALREADY_LOGGED_IN: Cause: Session is already logged in.; Action: Do not try to login again.

7129: INVALID_NULL_METHOD_ARGUMENTS: Cause: The method's arguments cannot have a null value.; Action: Ensure that the method's arguments do not have a null value.

7130: NESTED_UOW_NOT_SUPPORTED_FOR_ATTRIBUTE_TRACKING: Cause: Nested UnitOfWork is not supported for attribute change tracking.; Action: Do not use a nested UnitOfWork with attribute change tracking.

7131: WRONG_COLLECTION_CHANGE_EVENT_TYPE: Cause: The collection change event is the wrong type. The collection change event type has to be added or removed.; Action: Ensure that the collection change event type used is defined in CollectionChangeEvent.

7132: WRONG_CHANGE_EVENT: Cause: Wrong event class. Only PropertyChangeEvent and CollectionChangeEvent classes are supported.; Action: Ensure that the event class is either PropertyChangeEvent or CollectionChangeEvent.

7133: OLD_COMMIT_NOT_SUPPORTED_FOR_ATTRIBUTE_TRACKING: Cause: Old commit is not supported for attribute change tracking.; Action: Do not try to use attribute change tracking with an old commit.

7134: SERVER_PLATFORM_IS_READ_ONLY_AFTER_LOGIN

Cause: The server platform is read only after login.

Action: Changes to the server platform must be made before login. You must either:

CMP: Define a class that implements oracle.toplink.ejb.cmp.DeploymentCustomization, and customize its public String beforeLoginCustomization(Session session) class to change your server platform. Consult the documentation for defining a customization class in your orion-ejb-jar.xml file.
Non-CMP/POJO: Define a subclass of oracle.toplink.sessions.SessionEventAdapter, and override the public void preLogin(SessionEvent event) method to change your server platform. The session is contained in the event. Consult the documentation for sessions.xml and using SessionEventAdapter.

7135: CANNOT_COMMIT_AND_RESUME_UOW_WITH_UPDATE_ALL_QUERIES: Cause: You cannot commit and resume a UnitOfWork containing an UpdateAllQuery.; Action: You must either commit and continue in a new UnitOfWork, or do not use UpdateAllQuery.

7136: NESTED_UOW_NOT_SUPPORTED_FOR_UPDATE_ALL_QUERY: Cause: Nested UnitOfWork is not supported for an update all query.; Action: Do not use a nested UnitOfWork for an UpdateAllQuery.

7137: UNFETCHED_ATTRIBUTE_NOT_EDITABLE: Cause: The object is partially fetched (using fetch group), the unfetched attribute is not editable.; Action: Do not edit the unfetched attribute, or explicitly fetch the attribute before editing it.

7138: OBJECT_NEED_IMPL_TRACKER_FOR_FETCH_GROUP_USAGE: Cause: The object must implement FetchGroupTracker in order to use fetch group.; Action: The domain call must implement FetchGroupTracker in order to use fetch group.

7139: UPDATE_ALL_QUERIES_NOT_SUPPORTED_WITH_OTHER_WRITES: Cause: Update all queries cannot be issued within a UnitOfWork containing other write operations.; Action: Do not use UpdateAllQuery within a UnitOfWork containing other write operations.

7140: WRONG_SEQUENCE_TYP: Cause: Sequence type does not have method.; Action: Do not call this method on this type of sequence.

7144: PLATFORM_DOES_NOT_SUPPORT_SEQUENCE: Cause: Platform does not support sequence.; Action: Do not use this sequence type on this platform.

7145: SEQUENCE_CANNOT_BE_CONNECTED_TO_TWO_PLATFORMS: Cause: Two attempts have been made to connect to sequence, but it is already connected to one. Likely the two sessions share the DatasourcePlatform object.; Action: Ensure that the sequence is used by a single session only.

7146: QUERY_SEQUENCE_DOES_NOT_HAVE_SELECT_QUERY: Cause: QuerySequence does not have select query.; Action: Ensure that the sequence has a select query.

7147: CREATE_PLATFORM_DEFAULT_SEQUENCE_UNDEFINED: Cause: Platform cannot create platform default sequence - it doesn't override the createPlatformDefaultSequence method.; Action: You must either override the createPlatformDefaultSequence method on the platform or explicitly set default sequence by calling setDefaultSequence on DatasourceLogin.