Oracle ADF 100个例外 Business Components Error Messages(错误提示！)

Oracle ADF Business Components Error Messages The prefix "JBO-" signifies that the following messages were generated by Oracle ADF Business Components. All messages are listed in order by the message code number. 
Each error message contains an error number, an exception type, a cause, and an action. In some cases there may be multiple causes and/or actions. 
JBO-25000: UnknownSQLTypeException 
Cause: SQLType name passed to NullValue constructor is invalid. 
Action: Provide a valid SQLType name. See oracle.jbo.server.OracleTypeMapEntries for a list of valid SQLType names. Names are like "VARCHAR", "CHAR", "NUMBER", etc. 
JBO-25001: NameClashException 
Cause: A business component of this name already exists in the application module. 
Action: Provide a different name for the business component. If you provide a null value or null string for the name, the framework will create a unique name within the scope of the application module. 
JBO-25002: NoDefException 
Cause: No business component definition found with the given name in the project classpath. 
Action: Provide a correct name for the business component definition. If the definition is not in the classpath, you must include it there. Names are of the format myProjectPackage.BusinessPackage.BusinessComponent. This error can also occur if there is a case conflict, as when the database expects "DEPTNO" and receives "Deptno" instead. 
JBO-25003: NoObjException 
Cause: No business component object found with the given name in the application module. 
Action: Provide a different name for the business component object or create a new business component with the given name. 
JBO-25004: InvalidDefNameException 
Cause: An attempt has been made to associate a definition name with a type for which it is not valid. 
Action: The name should be a valid Java identifier with no spaces or punctuation. Names are of the format myProjectPackage.BusinessPackage.BusinessComponent 
JBO-25005: InvalidObjNameException 
Cause: An attempt has been made to associate a business component name with an object for which it is not valid. 
Action: The name should be a valid Java identifier with no spaces or punctuation. Names are of the format myProjectPackage.BusinessPackage.BusinessComponent 
JBO-25006: InvalidParamException 
Cause: The parameters passed to a business component method are invalid. 
Action: See the Javadoc for the method that throws this exception. Expand the call-stack for the correct parameters. E.g., DBTransactionImpl.executeCommand() throws this exception when command parameter is null or an empty String. 
JBO-25007: InvalidOperException 
Cause: Resetting row validation for a default RowIterator of a view object or a RowSet is not permitted. 
Action: Reset the RowValidation flag for the RowSet or view object. This will create another iterator for the RowSet or view object to navigate to another row without validating. 
JBO-25008: InvalidOperException 
Cause: An attempt has been made to remove a view object that is participating in a view link. 
Action: Remove the view link before removing the view object. 
JBO-25009: oracle.jbo.domain.DataCreationException 
Cause: A domain object could not be created with the given value. Either a domain constructor that accepts the given value does not exist, or there is no conversion method in the domain object for the given value type, or the domain's constructor threw an unexpected exception.

This exception may be thrown if an Oracle Object is specified with a default value where no string constructor or on the Oracle Object is present. 
Action: Confirm that the value being passed is valid with respect to the domain-type being created. E.g., passing a String value like "One" to the oracle.jbo.domain.Number constructor will throw this exception. 
For Oracle Objects with default values, you must create a string constructor on the Oracle Object and provide a default value that initializes the object type attributes. 
JBO-25010: oracle.jbo.domain.DomainValidationException 
Cause: Validation failed with the given value in a domain constructor. This exception is thrown in the validate() method of a domain type. 
Action: Provide a valid value for the domain type. 
JBO-25011: InvalidOperException 
Cause: An attempt has been made to invoke an invalid navigation method for a forward-only view object or RowSet. 
Action: Either remove the forward-only setting for the view object or RowSet, or do not invoke navigation methods other than next() on the forward-only view object or RowSet. 
JBO-25012: InvalidOperException 
Cause: The client has attempted to locate view rows that has the given entity row as the primary entity row. However, it has been discovered that the entity row's entity definition does not match the entity definition of the view object's primary entity object base. 
Action: The entity row used to locate view rows must be based on the same entity definition. 
JBO-25013: TooManyObject**ception 
Cause: Attempting to add a new entity to the cache with the primary key the same as an existing entity. This exception is thrown when uniquing a newly fetched/created entity with the cached set of entities. 
Action: The primary key value may not be unique for this entity-type. Fix by adding more attributes to the Key definition for this entity type, so that each row for this entity is uniquely identifiable. Or fix the primary key value so that this entity has a unique key identifier. 
JBO-25014: RowInconsistentException 
Cause: The database value does not match the cached value for this entity object. This could happen when another user or operation has committed modifications to the same entity-row in the database. This exception can also be thrown if the equals() method on one of the domain-type attributes in the entity fails. 
Action: Choose from the following options: 
　

Verify that another user or operation has not modified the same row in the database. If this entity has attributes of a domain type verify that the equals() method on these domains do not fail when comparing the existing cached value with the newly fetched value.
For any attributes/columns that are updated by the database, modify the entity attribute definition by selecting Refresh after update on the Attribute Settings page of the Entity Object Wizard.
Use view.executeQuery() frequently, especially after any operations that result in data being changed.
JBO-25015: InvalidOperException 
Cause: Attempting to execute a query for a view object or RowSet after closing or removing the view object or RowSet. 
Action: Verify that the view object or RowSet is not removed or closed. 
JBO-25016: ReadOnlyViewObjectException 
Cause: Attempting to modify data for a view object which is declared to be read only. This includes creating a new row for this view object, removing a Row, or modifying attributes of a ViewRow for this view object. 
Action: Create a view object with ReadOnly flag set to false to modify the data. 
JBO-25017: RowCreateException 
Cause: An unexpected exception occurred while creating a new entity instance. 
Action: The entity may not have a public default constructor. Fix the cause for InstantiationException or IllegalAcces**ception that appears in the details of this exception. 
JBO-25018: RowCreateException 
Cause: An unexpected exception occurred while creating a new ViewRow instance. 
Action: The ViewRow may not have a public default constructor. Fix the cause for InstantiationException or IllegalAcces**ception that appears in the details of this exception. 
JBO-25019: RowNotFoundException 
Cause: Attempting to lock a non-existing row in the database. This could occur when the cache has an entity which was subsequently deleted from the database by another user or operation. 
Action: Remove the current entity from the entity-cache by calling remove(). Or re-synchronize the cache with the database, by rolling-back the current transaction or by committing the existing set of changes and then dropping the entity-cache. 
JBO-25020: RowNotFoundException 
Cause: Attempting to find a referenced entity in the ViewRow failed due to a changed foreign-key value. 
Action: Provide a valid foreign-key value or remove the current one. 
JBO-25021: oracle.jbo.domain.DataCreationException 
Cause: A domain object could not be created with the given value. Either a domain-constructor that accepts the given value does not exist, or there is no conversion method in the domain object for the given value type, or the domain's constructor threw an unexpected exception. 
Action: Confirm that the value being passed is valid with respect to the domain-type being created. E.g., passing a String value like "One" to oracle.jbo.domain.Number constructor will throw this exception. 
JBO-25022: ViewLinkAlreadyExist**ception 
Cause: Attempting to set the Master RowSet for this RowSet more than once. 
Action: Do not invoke setMasterRowSetIterator more than once on a RowSet. 
JBO-25023: oracle.jbo.domain.GenericDomainException 
Cause: An expected domain exception occurred. 
Action: Contact Oracle ADF Business Components Technical Support. 
JBO-25024: JboException 
Cause: Attempting to use an obsolete TypeMap constructor. 
Action: Verify that the TypeMaps in use for this version of framework is compatible. See example TypeMaps in oracle.jbo.server.OracleTypeMapEntries 
JBO-25025: ReadXMLException 
Cause: An error occurred during reading the XML data for a view object. This exception may contain other ReadXMLExceptions. 
Action: Fix the contained Row- or Attribute-level exceptions in the details for this exception. 
JBO-25026: RowReadXMLException 
Cause: An error occurred during reading the XML data for a ViewRow. This exception may contain other ReadXMLExceptions for contained RowSets or Attributes. 
Action: Fix the RowSet- or Attribute-level exceptions in the details for this exception. 
JBO-25027: AttributeReadXMLException 
Cause: An error occurred during reading the XML data for an attribute of a ViewRow. This exception may contain other JboExceptions thrown from the set method for this attribute. 
Action: Fix the JboException in the details for this exception. 
JBO-25028: oracle.jbo.domain.DataCreationException 
Cause: A domain object could not be created with the given value. Either a domain-constructor that accepts the given value does not exist, or there is no conversion method in the domain object for the given value type, or the domain's constructor threw an unexpected exception. 
Action: Confirm that the value being passed, is valid with respect to the domain-type being created. E.g., passing a String value like "One" to oracle.jbo.domain.Number constructor will throw this exception. 
JBO-25029: oracle.jbo.domain.DataCreationException 
Cause: The named data class (may be a domain) could not be found. 
Action: Make sure that the data class is accessible from the CLASSPATH and is a valid data class. 
JBO-25030: InvalidOwnerException 
Cause: This entity is a detail in a composition association and no container entity could be found. This could occur for the following reasons: 

Creating a new entity instance by passing a non-existing master key value.
Updating the foreign-key value in this entity and there is no master entity with that foreign-key value. This could happen in a composition association if the detail rows are created before the master.
Action: Provide a valid foreign-key value to the create() method or setAttribute() method so that an appropriate master row is found for this entity. For composition associations, you need to have the FK field populated first, so you should create the children of compositions using a detail VO instance, as that will auto-populate the FK field. 
JBO-25031: RowNotFoundException 
Cause: The client has attempted to access an attribute of a view which is mapped to an entity row, but the corresponding entity row is null. If the view object consists of multiple entity object bases and if the secondary entity object bases are reference-only, the entity rows may be null if the foreign key linking the primary entity to the secondary entity object is null. 
Action: In such a situation, the user is not allowed to access attributes of missing entity rows. 
JBO-25032: JboSerializationException 
Cause: Failure trying to make the application module state or transaction state passive. 
Action: The passivation target store (Database, File or Memory) may have reported an exception. See the details of this exception for errors from the target store. 
JBO-25033: JboSerializationException 
Cause: Trying to activate the application module state or transaction state failed. 
Action: The passivation target store (Database, File or Memory) may have reported an exception. See the details of this exception for errors from the target store. The given ID (in case of activation) may be invalid/not found. 
JBO-25034: RowNotFoundException 
Cause: The client has attempted to locate a row with a stale row handle. This error may be raised if the client tries to take a row out of one query collection and use its handle to find a row in another query collection. Note that if the client calls executeQuery on a RowSet, it may receive a new query collection. Thus, you may get this error if the client retrieves a row from a RowSet, takes its row handle, calls executeQuery(), and then tries to locate the row using the saved handle. 
This exception may also be raised if a row reference is used across transaction boundaries and the row handle has become stale and hence the corresponding row cannot be found. 
Action: Make sure that your row handle is not stale. Perhaps, find the row again using its primary key before attempting to act on the row. 
JBO-25035: JboException 
Cause: An application attempted to change an application module's passivation store after it had been initialized. 
Action:The passivation store (Database, File or Memory) may only be initialized once. If the customer application logic has not specified a passivation store when the serialization framework is invoked, the passivation store is initialized by the Oracle ADF framework. Check the client application logic for invocations of ApplicationModuleImpl.setStoreForPassiveState which are invoked after the application module passivation store has been initialized. 
JBO-25036: InvalidObjAcces**ception 
Cause: An application invoked an object operation that is not supported in the object's current state. 
Action: Remove the invalid operation invocation or provide exception handling logic. 
JBO-25037: NoObjException 
Cause: This row set is a detail in a master-detail relationship, but it is missing a master row set iterator. Most likely, this occurred because a master row set iterator is removed through a call to removeMasterRowSetIterator() and has not be replaced with an appropriate one. 
Action: Call setMasterRowSetIterator() to provide a valid master row set iterator. 
JBO-25038: InvalidParamException 
Cause: The parameters passed to a business component method are invalid. 
Action: Refer to error message for EXC_INVALID_PARAMETER (JBO-25006) for info. Difference between this error msg and EXC_INVALID_PARAMETER is that this one does not include a reason. In general, we recommend using EXC_INVALID_PARAMETER instead of EXC_INVALID_PARAM_NO_EXPL_GIVEN. 
JBO-25039: RowNotFoundException 
Cause: The client attempted to work with the current row of a row set iterator, but the iterator has no current row. 
Action: Position the iterator to the correct row and perform the operation. 
JBO-25040: JboException 
Cause: The row containing a large object was not locked before attempting to call a method on the large object that could potentially change the data of the object. 
Action: Lock the row before attempting to get an output stream or write into a large object domain instance. 
JBO-25041: oracle.jbo.domain.DataCreationException 
Cause: TypeFactory determined it needs to ask the TypeMapEntries class to ask to convert data, but the TypeMapEntries did not know how to perform the conversion. 
Action: This usual means problems in TypeMapEntries implementation. Contact BC4J Technical Support. 
JBO-25042: RowNotFoundException 
Cause: Entity row of the given handle is not found in transaction post listener list. 
Most likely cause of this error is as follows: the user requests certain operation. The operation tries to get access the row in database. This fails for whatever reason (this exception's detail may have further info). The system tries to fix the problem at the entity level. It looks for the entity row in the transaction post listener list. The specified row is not found. 
Action: Look at the details and see if the cause can be determined from them. Check to see if concurrent updates to database could have caused the problem. 
JBO-25043: InvalidParamException 
Cause: Extraneous key passed in to findByKey(). For example, suppose the View Object may expect no more than a two-part key, but the key passed into findByKey is a three-part key. Then, this exception will thrown. 
Action: Provide a valid key. 
JBO-25044: DefinitionChangedException 
Cause: Trying to activate the application module state or transaction with an older version of metadata into an application module with a later metadata definition of the Business Components. 
Action: A newer version of the application definitions objects is now running and trying to activate an Application state which was passivated with an earlier version. ** 
JBO-25045: InvalidOperException 
Cause: An attempt to synchronize iterator implicitly is detected in 3 tier running environment. When ApplicationModule synchronization mode is SYNC_BATCH, iterator synchronization should only be done explictly. 
Action: Remove code/operation that attempts to synchronize iterator implicitly. 
JBO-25046: RowNotAvailableException 
Cause: This exception is thrown when running in 3 tier SYNC_BATCH mode. The user requested a row, but that row is not available in the cache. 
Action: Make appropriate API calls to bring the required row into cache. Then, try to get the row again. 
JBO-25047: InvalidOperException 
Cause: An attempt to make a call to server detected for an operation that is supposed to work only with client cache. 
Action: Remove code/operation that attempts to call server. 
JBO-25048: InvalidOperException 
Cause: This operation is invalid for a working set View Object. 
Action: Remove code/operation that calls the named method. 
JBO-25049: InvalidOperException 
Cause: Attempting to set an batch mode for an entity that has a primary key marked as Refresh-on-insert. 
Action: Do not set this entity type into batch mode.
JBO-25050: BatchDMLException 
Cause: Posting entities in batch mode failed with a set of exceptions 
Action: Fix the cause for each of the exception in the details array. 
JBO-25051: RowNotFoundException 
Cause: The client has attempted to locate a row with a range index, but the Row Set Iterator's range does not have a row at the index. 
It may be that the range index is too big (>= the range size), or that the range is at the bottom and the range index is beyond the last row of the Row Set. 
Or, the Row Set may have been reset because of operations like rollback and clear-cache. Hence, the range is empty and no row is found 
Action: Make sure that your Row Set Iterator is open and has rows in its range. Also, make sure that the range index falls between the first and the last row of the range. 
JBO-25052: JboException 
Cause: A ViewObject with no key attributes has transient passivatable attributes. This type of ViewObject cannot participate in passivation/activation. 
Action: Set one or more attributes as key attributes for this ViewObject 
JBO-25053: InvalidOperException 
Cause: An attempt has been made to navigate a rowset in Range Paging mode when the rowset has inserted/removed rows. 
Action: Post this transaction before navigating. 
JBO-25054: JboException 
Cause: An attempt has been made to activate a stack snapshot which does not exist. The specified snapshot may already have been activated or the stack may already have been cleared by a previous rollback/commit. 
Action: Ensure that stack snapshot ids are maintained by the application across transaction boundaries. ** 
JBO-25055: JboException 
Cause: An attempt has been made to remove a persistent snapshot which is referenced by the snapshot stack. 
Action: Clear the snapshot stack before attempting to remove the the referenced snapshot. ** 
JBO-25056: InvalidOperException 
Cause: An attempt has been made to call removeFromCollection() on an Entity row. It is illegal to call removeFromCollection() on an Entity row. 
Action: Remove code that calls removeFromCollection() on an Entity row. 
JBO-25057: RowNotFoundException 
Cause: In LOCK_OPTUPDATE locking mode, an attempt was made to update an Entity row. The update operation failed to update any row. 
Action: Another user may have modified the row and committed the changes. 
JBO-25058: NoDefException 
Cause: No business component definition found with the given name in the project classpath. 
Action: Provide a correct name for the business component definition. If the definition is not in the classpath, you must include it there. Names are of the format myProjectPackage.BusinessPackage.BusinessComponent. This error can also occur if there is a case conflict, as when the database expects "DEPTNO" and receives "Deptno" instead. 
JBO-25059: InvalidOperException 
Cause: This View Object is not Entity based, and its ManageRowsByKey flag is true. Yet, its key definition is empty. Restated, the user has asked for the View rows to be managed by keys, but the key definition is empty (which would produce empty keys for all rows). 
Action: In order to manage EO-less View Object by key, a meaningful (non-empty) key definition must be supplied. 
JBO-25060: RowNotFoundException 
Cause: An unexpected exception was thrown when we tried to retrieve the next row from JDBC ResultSet. 
Action: Take a look at the detail exception for further information and fix underlying problems. 
JBO-25061: InvalidOperException 
Cause: ViewRowSetImpl.setPassivationEnabled called for internal rowset 
Action: Create a datamodel ViewObject instance and use rowsets from that ViewObject to make them passivation enabled. 
JBO-25062: NoObjException 
Cause: An attempt was made to create detail RowSet. However, no matching detail ViewObject could be found. 
Action: You can create a detail RowSet only if a matching ViewObject is present. Make sure that an appropriate ViewObject is there before calling to create a detail RowSet. 
　
JBO-25200: NotConnectedException 
Cause: The application module is not connected to the database. 
Action: Provide a valid set of connection credentials to connect to a database. 
JBO-25201: AlreadyConnectedException 
Cause: Trying to re-establish a database connection. 
Action: Disconnect the current database connection before trying to re-establish the JDBC connection. 
　
JBO-25221: JboException 
Cause: Attempting to call a method that is either not implemented or not supported. 
Action: This method is not available on the called object. E.g. setAttribute() in oracle.jbo.Key class is not implemented and will throw this exception. 
JBO-25222: ApplicationModuleCreateException 
Cause: If your business components are deployed in local mode, they may not be on the classpath. 
Action: If this is the cause of the error, the exception will usually be followed by a different exception, JBO-25002: NoDefException. If this occurs, make sure you've done all of the following: 

Made a library for your business components.
Added a library to your client's project properties.
Included the library on the "libraries" page when you created a deployment profile for your client (whether your client was a web application or a command-line application).
Copied the library with your client to the target platform (whether your client was a web application or a command-line application).
Included all the files you copied (including the library) when you set the classpath on the target platform.
JBO-25223: ApplicationModuleCreateException 
Cause: When business components are running inside JServer, only one root application module may be created. This is because JServer (already) provides one transaction context. 
Action: It is illegal to attempt to create multiple root transactions when running inside JServer. 
JBO-25224: JboException 
Cause: Trying to retain the application module state during a transaction disconnect failed. 
Action: The disconnect and retain application module state target requires that no database state exist before the transaction connection is closed. Examples of database state include open database cursors in non-forward only view objects, database locks, and uncommitted database changes. The client should clean up this state by fetching or resetting any open view objects and committing any uncommitted changes. 
JBO-25226: ApplicationModuleCreateException 
Cause: This application module definition contains recursive references to child application modules. For example, if application module definition appMod1 contains a child application module of appMod2, and appMod2 contains appMod1, this error will be raised. 
Action: Remove recursive application module definition references. 
JBO-25227: InvalidOperException 
Cause: The user has attempted to create a view link (in an application module) that will result in a recursive loop of view links. The error message should show a chain of recursive master-detail relationships. 
Action: If a static view link is causing the recursion, remove the view link from the application module. If a dynamic view link is causing the recursion, remove the code that creates the recursive view link. 
JBO-25301: InvalidOwnerException 
Cause: While traversing the parenthood chain for application modules, a child application module was found with no container (parent) application module. 
Action: If this application has added custom business component classes, it may be that the application code is attempting to access a child application module before it is fully initialized. If this is not the case, this error probably represents some internal error in the Oracle ADF Business Components Technology, in which case contact JDeveloper Technical Support. 
JBO-25302: InvalidOwnerException 
Cause: A business component is found without a container (parent) application module. 
Action: If this application has added custom business component classes, it may be that the application code is attempting to access a business component before it is fully initialized. If this is not the case, this error probably represents some internal error in Oracle ADF Business Components technology, in which case contact JDeveloper Technical Support. 
JBO-25303: InvalidOperException 
Cause: A dirty entity cache cannot be cleared. The client asked to clear an entity cache but some rows in the entity cache have been modified. An entity cache with modified rows cannot be cleared. 
Action: Do not attempt to clear an entity cache with modified rows in it. 
JBO-25306: JTPersistenceException 
Cause: Could not persist a design-time attribute into the XML file. 
Action: Identify the offending design-time attribute and contact JDeveloper Technical Support. 
JBO-25307: JTPersistenceException 
Cause: XML file is not open. 
Action: Contact JDeveloper Technical Support with how you ran into the problem. JBO-25308: InvalidOperException 
Cause: An attempt was made to modify the primary key of an existing entity bean. This is disallowed by EJB. 
Action: Do not modify primary key of an old (not-new) entity bean. 
JBO-25309: InvalidOperException 
Cause: The primary key of an entity bean is null. This is disallowed by EJB. 
Action: Set the primary key to be not null. 
JBO-26000: JboException 
Cause: Attempting to load metadata objects failed. It may have unexpected data or the XML data may be corrupt. 
Action: Verify that the XML metadata for various components is valid. 
JBO-26001: NoXMLFileException 
Cause: Could not open the named XML file for reading. 
Action: Try the following: 

Make sure that the file is present. In particular, if the file is to be found in a Zip/JAR file, make sure that the Zip/JAR file is included in the CLASSPATH.
This error is also reported if the name of the XML file does not match the object Name specified in the XML file. If the file system support case insensitive file names (e.g., Windows NT), make sure that the file name matches the object Name in the XML file in case-sensitive fashion.
For a JPX file, this error is reported if the JPX file is missing the JboProject XML tag. Check the JPX file to make sure that the valid tag is in there.
One XML file may be extending another XML file (specified by the Extends element in this XML file). This error is reported if the base XML file is not found.
When loading the XML file for a package (JboPackage tag), this error is reported if some unexpected error occurs while loading a containee.
In all of the above cases, a more descriptive message may be printed on Diagnostic. If you are not seeing Diagnostic messages, you can run your application with Diagnostic turned on, as in "java -Djbo.debugoutput=console ...", to see diagnostic messages, or or "java -Djbo.debugoutput=file ..." to output messages to a file. 
JBO-26002: PersistenceException 
Cause: Some XML parsing exception ( oracle.xml.parser.v2.XMLParseException) was thrown. 
Action: The XMLParseException information is output to Diagnostic. If you are not seeing diagnostic messages, you can run your application with diagnostic turned on, as in "java -Djbo.debugoutput=console ...", to see diagnostic messages, or "java -Djbo.debugoutput=file ..." to output messages to a file. 
JBO-26003: PersistenceException 
Cause: An error occurred while loading entity object definitions. An attribute index in the Java class for this entity has a mismatch with the index in the definition, or an attribute index is missing in the Java class. 
Action: Ensure that the indices of attributes in the definition for this entity match the indices defined in the Java class for this entity. 
JBO-26004: InvalidOperException 
Cause: An attempt was made to set the base definition of another definition object, e.g., setting B's base definition to A (i.e., B Extends A). However, A already extends B. Setting a recursive (circular) subclassing relationship among definition objects is illegal. 
Action: Review your subclassing hierarchy of your definition objects and correct errors. 
JBO-26005: PersistenceException 
Cause: The fetch mode specified in the view definition XML file is not valid. 
Action: Check the content of the XML file for the view definition. Look for an XML element named "FetchMode". Make sure that the value for that element is valid. Valid values are: "FETCH_AS_NEEDED", "FETCH_ALL", and "FETCH_DEFAULT".
JBO-26006: PersistenceException 
Cause: The fetch size specified in the view definition XML file is not valid. 
Action: Check the content of the XML file for the view definition. Look for an XML element named "FetchSize". Make sure that the value for the element is a positive integer. 
JBO-26007: PersistenceException 
Cause: The maximum fetch size specified in the view definition XML file is not valid. 
Action: Check the content of the XML file for the view definition. Look for an XML element named "MaxFetchSize". Make sure that the value for the element is a non-negative integer, or "MAX_FETCH_UNLIMITED", or "MAX_FETCH_DEFAULT". A MaxFetchSize of 0 is the same as MAX_FETCH_UNLIMITED. 
JBO-26008: PersistenceException 
Cause: A problem is found in resolving a view link definition or an association. In case of a view link, this error may be caused by the fact that the source or destination view object cannot found. Or, if the view link ends have attribute names, this error may indicate that the named attributes cannot be found. Similarly, for an association, this error indicates that either source or destination entity object or attributes involved in the association cannot be found. 
Action: Make sure the XML definition for the view link/association has correct view object/entity object/attribute names. 
JBO-26009: PersistenceException 
Cause: This error occurs if the application uses meta object serialization files (.ser files) instead of XML files. It indicates that after the .ser file is deserialized, the top level object returned from deserialization is not an instance of oracle.jbo.server.xml.JboElementImpl. 
Action: This probably means that the .ser file is corrupt. 
JBO-26010: PersistenceException 
Cause: Entity attribute name in the view definition XML file is invalid or is not found. 
Action: Make sure that the entity name is valid. Also, check to make sure that the named attribute does exist in the entity object. The entity object is identified by the EntityUsage element. 
JBO-26011: PersistenceException 
Cause: Attribute definition found in XML file is invalid. It is missing SQLType value. 
Action: Correct the error in the XML file. 
JBO-26012: PersistenceException 
Cause: The view link definition in the XML file is missing either the source or destination view link end. For a view link XML file, two elements named ViewLinkDefEnd should be found. 
Action: Correct the error in the XML file. 
JBO-26013: PersistenceException 
Cause: Meta object name passed for lookup is invalid. 
Action: Normally, the meta object name is a dot-separated name of the meta object. For an entity object named Emp in package1.example, the correct name would be package1.example.Emp . To correct, locate where the invalid name is coming from (could be meta object names mentioned in an XML file, or the name of the project, etc.) and change the name to a valid one. 
　
JBO-26015: PersistenceException 
Cause: A view definition does not include a discriminator column of an entity base. If an entity base has discriminator columns, it must include all of them in the view object's attribute mapping. 
Action: Change the view definition to include discriminator column attributes. 
JBO-26016: InvalidOperException 
Cause: You cannot set customer query (calling setQuery()) on a view object if it is the detail view object in a master detail view link. 
Action: Do not call setQuery() if the view object is a detail. 
JBO-26017: PersistenceException 
Cause: An association definition in an XML file is invalid. In particular, this error means that either of the two association ends ("AssociationEnd" elements in the XML file) are missing "Attributes", which lists source or destination attributes. 
Action: Correct the error(s) in the XML file. 
JBO-26018: InvalidOperException 
Cause: An attempt was made to post a row with no attribute set. Some databases (in particular Oracle) do not allow an INSERT statement with no VALUE specified. 
Action: Set some attributes on the row before attempting to insert it into the database. 
JBO-26019: JboException 
Cause: Attempting to remove a master which has detail entities. In the case of a composition, a master cannot be removed if it has details. 
Action: Remove all the details of this master by accessing the details through an association and removing all of them. 
JBO-26020: InvalidOperException 
Cause: The application code tried to take a row from one row set (or view object) and insert it into another row set (view object). In response, the framework will make a "copy" of the row in the new row set. This new row will share references to the underlying entity objects. However, if the source and destination row sets do not share any entity object bases at all, this operation will fail as it does not find any entity rows to share. 
Action: When attempting to take a row from one row set and insert into another, make sure that they share at least one entity object base. 
JBO-26021: PersistenceException 
Cause: A NullPointerException was thrown while parsing an XML file. A possible cause for this is that the DTD file is missing ( oracle.jbo.dtd.jbo*.dtd). 
Action: Make sure the appropriate DTD file is present. 
JBO-26022: CustomClassNotFoundException 
Cause: Custom class could not be found and loaded. The custom class may be for a component (e.g., view object), a definition (e.g., view definition), or a row (e.g., view row, entity row). 
Action: Make sure that the named class is reachable from the CLASSPATH. The detail exception (if present) will give you more specific reasons why the attempt to locate and load the custom class failed. 
JBO-26023: CustomClassNotFoundException 
Cause: Custom class was found and loaded, but it is invalid in that it is not assignable to a framework (super) class. 
Action: Make sure that the custom class subclasses the appropriate framework (super) class. 
JBO-26024: PersistenceException 
Cause: An error occurred while creating initial context. This error usually carries a detail exception which will give further information on the cause of the error. 
Action: If your application is running inside JServer, make sure that the database user (schema) has the setContextClassLoader permission. To grant this, the database system administrator can invoke the following PL/SQL procedure: 
EXEC DBMS_JAVA.GRANT_PERMISSION('&&1', 'SYS:java.lang.RuntimePermission', 'setContextClassLoader', null); 
JBO-26025: PersistenceException 
Cause: An error occurred while trying to get System properties. Specifically, System.getProperties() call failed. 
Action: If your application is running inside JServer, make sure that the database user (schema) has the proper property permission. To grant this, database system can invoke the following PL/SQL procedure: 
EXEC DBMS_JAVA.GRANT_PERMISSION('&&1', 'SYS:java.util.PropertyPermission', '*', 'read'); 
JBO-26026: PersistenceException 
Cause: An error occurred while trying to get load properties. 
Action: Check to see if the named properties file contains valid Java properties. 
JBO-26027: RowCreateException 
Cause: While initializing a view row, the system found an entity object base with discriminator column attributes. However, the discriminator column values coming from the view row do not match any of the entity objects (the entity for the entity object base or any of its extended entities). 
Action: Make sure that the view row's discriminator column values match one and only one entity object. 
JBO-26028: PersistenceException 
Cause: A view definition does not include a primary key attribute of an entity base. When a view object uses an entity as one of its entity bases, it must include all primary key attributes of the underlying entity object. 
Action: Change the view definition to include all primary key attributes. 
JBO-26029: CustomClassNotFoundException 
Cause: Custom type map class could not be found and loaded. 
Action: Make sure that the named class is reachable from the CLASSPATH. If jbo.TypeMapEntries property is specified, make sure that the property value is correct. Also, though unlikely, this may be caused by an improper implementation of SQLBuilder where it is returning an incorrect value for type map class name. 
The detail exception (if present) will give you more specific reasons why the attempt to locate and load the custom class failed. 
　
JBO-26030: AlreadyLockedException 
Cause: This row has already been locked by another user or transaction. 
Action: Try locking the row again and the operation should succeed after the other user or transaction has released the lock. 
JBO-26031: PersistenceException
Cause: Problem in secondary entity base definition in view definition. The named entity base is supposed to use the named entity association end to join it with another entity base, but, when resolved with the association definition, the association end does not resolve to the same entity. For example, suppose one builds a view object with Dept and Emp. Emp is supposed to join with Dept using the EmpEnd of the DeptEmp assocation. For such a view definition, BC4J verifies that EmpEnd indeed is from Emp entity. If EmpEnd was from another entity, say Person (or Dept), it would not be correct to use that assocation end to perform join. 
Action: Most commonly, this is caused by incorrect information in the view object's XML file. Make sure that the 'AssociationEnd' for the named 'EntityUsage' is not pointing at the wrong (the other) end of assocation. 
JBO-26032: InvalidOperException
Cause: The attempted operation is invalid for a ViewCriteria or ViewCriteriaRow. 
Action: Remove code that attempts this operation. 
JBO-26033: JboException 
Cause: Cannot find application definition of the given name
Action: Fix the application definition name or make the appropriate .cpx file available in the classpath.
JBO-26034: JboException
Cause: Cannot find configuration information in the application definition file
Action: Fix the Configuration name or make the appropriate .cpx file available in the classpath.
JBO-26035: PersistenceException 
Cause: A view definition is found with an entity usage definition where the secondary entity usage's association description is incomplete.
Action: Examine the view object's XML file. A secondary entity usage's association description should have the following elements: 'Association', 'AssociationEnd', and 'SourceUsage'. Check to see if any of these are missing.
JBO-26036: InvalidOperException
Cause: An attempt was made to set up meta object subtitution that leads to recursion. For example, suppose you set up substitution where C substitutes B, and B substitutes A, and A subsititutes C. This results in a recursive substitution and will cause this error.
Action: Review your meta object substitution and correct errors.
JBO-26037: RowCreateException
Cause: While creating a new View row, the system found an entity object base with discriminator column attributes. However, the discriminator column values coming from the View row does not match any of the entity objects (the entity for the entity object base or any of its extended entities).
Action: Make sure that the View row's discriminator column values match one and only one entity object.
JBO-26038: PersistenceException
Cause: The view link definition is based on an entity association. One of its ends specifies the named entity definition, but the view definition for that view link end does not have an entity usage for that entity definition. 
Action: Correct the error in the view link definition (XML file). In particular, check to see if the view link's source and destination are not switched with those of the entity association.
JBO-26041: DMLException 
Cause: Some database error occurred while posting (writing) an entity to the database. This error normally carries a detail exception from the database which will give further information about the database failure. 
Action: Look at the details of the exception and address the database problem. 
JBO-26042: DMLException 
Cause: A database failure occurred while trying to generate an object ID (OID) and object reference (REF). When a new row is created on an entity which maps to an Oracle object table, an OID and REF for the new row are generated. This executes a SQL statement like select a.oid, make_ref(, a.oid) ... Somehow, this statement is failing. 
Action: Check the following: 

Are you using the right version of Oracle database?
Is the table in question an object table?
This error normally carries a detail exception from the database, which will give further information about the database failure. Take a look at the detail exception and address the database problem. JBO-26043: DMLException 
Cause: An attempt was made to generate an object ID (OID) and/or a reference (REF) on a database system that does not support Oracle objects. 
Action: Do not try to create OID or REF on a database system that does not support Oracle objects. 
JBO-26044: DMLException 
Cause: The application tried to get an estimated row count (getEstimatedRowCount()) on a row set. While building the appropriate query statement, executing it, and retrieving the estimated count, an error occurred. This error is accompanied by the SQL statement that caused the error. Also, it normally carries a detail exception from database, which will give further information about the database failure. 
Action: Take a look at the SQL statement and the detail exception and address the database problem. 
JBO-26045: DMLException 
Cause: A database error occurred while trying to generate an object ID (OID) from the primary key. This operation is valid only if the table in question is an object table and if the table specifies that the reference (REF) is PK based. 
Action: Check the following: 

Are you using the right version of Oracle database?
Is the table in question an object table?
Does this object table use a PK-based REF?
This error normally carries a detail exception from database which will give further information about the database failure. Take a look at the detail exception and address the database problem. 　
JBO-26060: DMLException 
Cause: A SQLException occurred while trying to register a JDBC driver. 
Action: Fix the underlying SQLException. 
JBO-26061: DMLException 
Cause: A SQLException occurred while trying to open a JDBC connection. 
Action: Fix the underlying SQLException. 
JBO-26062: DMLException 
Cause: A SQLException occurred while trying to close a JDBC connection. 
Action: Fix the underlying SQLException. 
JBO-26064: DMLException 
Cause: A SQLException occurred while trying to close a JDBC connection. 
Action: Fix the underlying SQLException. 
JBO-26065: DMLException 
Cause: A SQLException occurred during the commit phase of this transaction. 
Action: Fix the underlying SQLException. 
JBO-26066: DMLException 
Cause: A SQLException occurred during the rollback phase of this transaction. 
Action: Fix the underlying SQLException. 
JBO-26067: JboException 
Cause: An exception occurred while adding a JDBC connection to a pool that was already full. 
Action: Modify the class that is using the pool to check the pool size before adding a new connection to the pool. 
JBO-26068: JboException 
Cause: The user attempted to return a connection to a pool that was not responsible for managing that connection. 
Action: Modify the class that is using the pool to ensure that the connection belongs to the pool before returning the connection to the pool. 
JBO-26069: JboException 
Cause: A client request was timed out while waiting for a connection to be returned to the pool. 
Action: Increase the maximum pool size in order to accommodate 2x the maximum expected active request size. 
JBO-26070: DMLException 
Cause: A SQLException occurred while setting up metadata JDBC statement. 
Action: Fix the underlying SQLException. There might be a datatype mismatch between the attributes of the view object and columns in the SQL for it.
JBO-26080: DMLException 
Cause: An unexpected exception occurred while executing the SQL to fetch data for an entity instance or lock it. 
Action: Fix the cause for the SQLException in the details of this exception. 
JBO-26081: SQLDatumException 
Cause: A SQLException occurred when converting data from JDBC to oracle.jbo.domain.Struct attributes. 
Action: Fix the conversion errors as suggested in SQLException. 
JBO-26100: AfterCommitException 
Cause: An exception occurred in the afterCommit notification phase of the transaction. 
Action: Verify the exception in the details of this exception. Fix the failing afterCommit() overridden methods in the entities or transient TransactionListener objects registered with the transaction to listen into the commit/rollback cycle. 
JBO-26101: AfterPostException 
Cause: An exception occurred in the afterPost phase of the transaction. 
Action: Verify the exception in the details of this exception. Fix the failing afterPost() overridden methods in the entities or transient TransactionPostListener objects registered with the transaction to listen into the post cycle. 
JBO-26102: AfterRollbackException 
Cause: An exception occurred in afterRollback notification phase of the transaction. 
Action: Verify the exception in the details of this exception. Fix the failing afterRollback() overridden methods in the entities or transient TransactionListener objects registered with the transaction to listen into the commit/rollback cycle. 
JBO-27001: ReadOnlyAttrException 
Cause: This association attribute is marked readonly. 
Action: Cannot modify the value of the association attribute as it is marked readonly. 
JBO-27002: AttrSetValException 
Cause: A custom validation rule failed to validate an attribute value. 
Action: Fix the attribute value so that it passes the custom validation rule. 
JBO-27003: ValidationException 
Cause: Modified or new entities in this view object failed to validate. 
Action: Fix the failing entity values and revalidate the view object. 
JBO-27004: ReadOnlyAttrException 
Cause: Attempting to modify a read-only entity-attribute. 
Action: Do not modify a readonly attribute value. 
JBO-27005: ValidationException 
Cause: Modified or new entities within this application module or nested application module failed to validate. 
Action: Fix the failing entities and then re-validate this application module. 
JBO-27006: AttrValException 
Cause: An attribute cannot be found by the given name during validation. 
Action: Entity metadata could be corrupt as there is an attribute which is to be validated but no definition could be found for that attribute in the metadata. 
JBO-27007: ValidationException 
Cause: Attempting to validate a ViewRow failed. 
Action: Fix the failing entities or attributes as found in the details of this exception. 
JBO-27008: ReadOnlyAttrException 
Cause: Attempting to modify a ViewRow attribute that is readonly 
Action: Either change the Updateable flag for the View Attribute or do not attempt to update readonly attributes. 
JBO-27009: ValidationException 
Cause: Attempting to validate entities and attributes failed during validation of buffered attributes in Deferred Validation mode. (Not available in 3.x) 
Action: Fix the failure cases. 
JBO-27010: ValidatonException 
Cause: For strings, the length of the string value provided for an attribute is more than the max-length this attribute expects. For Numeric values, the length of the value (in string form) is more than what the attribute expects. 
Action: Fix the attribute value with respect to the precision and scale information for the failing attribute.
JBO-27011: AttrSetValException 
Cause: A validation rule for an attribute failed either due to an unexpected exception in validating the attribute with that rule, or due to failure in evaluating the NOT operation on the rule. 
Action: Fix the attribute value so that it validates against the failing rule. 
JBO-27012: ValidationException 
Cause: The custom method validator attached to an entity returned false, indicating a failure in the validation for that entity. 
Action: Fix the cause for failure in the custom validation method for this attribute. 
JBO-27013: ValidationException 
Cause: The custom method validator attached to an attribute returned false indicating a failure in validation for that attribute in the custom method. 
Action: Fix the cause for failure in the custom validator method for this attribute. 
JBO-27014: AttrValException 
Cause: The attribute value cannot be null as it has been marked mandatory. 
Action: Provide non-null values for mandatory attributes. 
JBO-27015: ValidationException 
Cause: In validating a master, some child entities were found that could not be validated. This occurs only in the case when there is a composition association between the master and detail entities. 
Action: Fix the attribute values in the child entities so that they are valid when the child entities are validated by the master 
JBO-27016: InvalidAttrKindException 
Cause: An unexpected attribute kind found in the definition for a view object. 
Action: Fix the attribute kind information in the xml-metadata definition for attributes in this view object. 
JBO-27017: KeyNotFoundException 
Cause: While loading the metadata definition for this entity, there was no attribute marked as the primary key. 
Action: Set at least one attribute as the primary key for this entity type, so that entities of this type can be uniquely identified. 
JBO-27018: AttrSetValException 
Cause: The type of attribute value provided as an argument to the set() method for this attribute is not an instance of the Java type that this attribute expects. 
Action: Convert the argument to a proper Java type, such that it is an instance of the Java type that this attribute expects. 
JBO-27019: AttrGetValException 
Cause: An unexpected exception occurred in set Attribute method. Getter methods should throw a subclass of JboException so that custom exception messages are thrown/shown to the caller. This exception could also be thrown if the getter is not a public Java method. 
Action: Do not throw any exception other than sub-classes of JboException from any business logic code in the getter method for an attribute. Also verify that the getter method is a public Java method. 
JBO-27020: AttrSetValException 
Cause: An unexpected exception occurred in set Attribute method. Setter methods should throw a subclass of JboException so that custom exception messages are thrown/shown to the caller. This exception could also be thrown if the setter is not a public Java method. 
Action: Do not throw any exception other than sub-classes of JboException from any business logic code in the setter method for an attribute. Also verify that the setter method is a public Java method. 
JBO-27021: AttributeLoadException 
Cause: An unexpected exception occurred during fetching values from a JDBC result set into an attribute for a row object. There could be conversion errors between the return type from JDBC for the attribute and its Java type. 
Action: Verify that the JDBC-SQL type and Java type for the attribute are compatible. Fix any conversion errors or domain exceptions that are in the details of this exception. 
JBO-27022: AttributeLoadException 
Cause: An unexpected exception occurred during fetching values from a JDBC result set into an attribute for a row object. There could be conversion errors between the return type from JDBC for the attribute and its Java type. 
Action: Verify that the JDBC-SQL type and Java type for the attribute are compatible. Fix any conversion errors or domain exceptions that are in the details of this exception. 
JBO-27023: DeferredTxnValidationException 
Cause: An unexpected exception occurred during validating changes in a transaction. 
Action: Verify the details for DeferredRowValidationException and fix those errors. 
JBO-27024: DeferredRowValidationException 
Cause: An unexpected exception occurred during validating a row. 
Action: Verify the details for DeferredRowValidationException and fix those errors at the row level. The details can also contain DeferredAttrValidationExceptions which needs to be fixed as well. 
JBO-27025: DeferredAttrValidationException 
Cause: An unexpected exception occurred during validating an attribute of a row. 
Action: Verify the details for JboExceptions and fix those errors at the row level. 
JBO-27026: AttrSetValException 
Cause: An unexpected exception occurred during a setter method for an attribute. This exception should not be seen outside of the framework. 
Action: Verify the details for JboExceptions and fix those errors 
JBO-27027: DeferredAttrValidationException 
Cause: An unexpected exception occurred during validating attributes of a row for mandatory fields. 
Action: Verify the details for JboExceptions and fix those attributes with null values. 
　
JBO-27101: DeadEntityAcces**ception 
Cause: Trying to refer to an invalid/obsolete entity. This could occur if some business logic has held on to an entity reference which was removed and the transaction has been posted or committed. It could also occur if a reference entity has been removed from the cache and any ViewRow is attempting to access it. 
Action: Use findByPrimaryKey to find a valid entity of the desired key instead of holding on to a reference to an entity instance. 
JBO-27102: DeadViewRowAcces**ception 
Cause: Trying to access a ViewRow which is part of an obsolete/invalid collection. This could happen if a reference to the ViewRow is held by some business logic while the containing view object was removed. 
Action: Find the referenced ViewRow either by re-querying or using findByKey methods to get a valid reference to the ViewRow. 
JBO-27120: SQLStmtException 
Cause: Failed to execute a query. This could occur when trying to execute a query for a SQLValue domain class or a Sequence domain. 
Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception. 
JBO-27121: SQLStmtException 
Cause: Failed to execute a SQL statement. 
Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception. 
JBO-27122: SQLStmtException 
Cause: Failed to prepare a JDBC PreparedStatement. 
Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception. 
JBO-27123: SQLStmtException 
Cause: Failed to prepare a JDBC CallableStatement. 
Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception. 
JBO-27124: SQLStmtException 
Cause: Failed to create a JDBC Statement object with the given set of parameters. 
Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception. 
JBO-27125: JboException 
Cause: Failed to find a java type for a column-type in the given dynamic ViewObject query. 
Action: Either provide a typemap that maps the selected columns in the query or leave out the erring column-type from the query. 
　
　
　
JBO-27203: JboException 
Cause: When using global transactions you cannot use the transactional datasoource for acquiring the internal connection. Action: Explicitly specify the jdbc url that should be used for creating the internal connection by setting the oracle.jbo.common.PropertyConstants.INTERNAL_CONNECTION_PARAMS property 
JBO-28000: PCollException 
Cause: The client specified a custom persistent collection through the jbo.pcoll.mgr property. However, the class specified could not be located or loaded. 
Action: Make sure that the name specified for jbo.pcoll.mgr is for a valid class name. The class name should be fully qualified with the package name. A special keyword None represents no persistent collection manager, i.e., no spilling to disk will occur. 
JBO-28001: PCollException 
Cause: An error occurred while attempting to get a JDBC connection for persistent collection management. 
Action: Make sure that the database connection URL is correct. The detail to this exception will give further information on the problem. 
JBO-28002: PCollException 
Cause: An error occurred while creating "persistent collection control table." Normally, the control table's name is PCOLL_CONTROL. 
Action: Check to make sure that the connection has appropriate authority to create a table. The detail to this exception will give further information on the problem. 
JBO-28003: PCollException 
Cause: An unexpected error occurred while attempting to delete the persistent collection control row. 
Action: Look at the details of this exception for further information on the problem and how to address it. 
JBO-28004: PCollException 
Cause: An error occurred while trying to lock the persistent collection control row. This error is thrown in two situations: 

An unexpected database error occurred while attempting to lock the row.
After the persistent collection manager committed changes to database, it tried to lock the control row. Between the time of commit and lock attempt, another user somehow managed to lock the row and not release it within a set time. In this case, the detail will be null .
Action: In the first case, see the details of this exception for further information on the database problem. In the second case, make sure that no other user locks the control rows outside the Business Components framework. 
JBO-28005: PCollException 
Cause: An unexpected error occurred while attempting to update the persistent collection control row. 
Action: Look at the details of this exception for further information on the problem and how to address it. 
JBO-28006: PCollException 
Cause: An error occurred while attempting to create a database table to store persistent collection material. 
Action: Look at the details of this exception for further information on the problem and how to address it. 
JBO-28007: PCollException 
Cause: An unexpected error occurred while attempting to commit persistent collection changes. 
Action: Look at the details of this exception for further information on the problem and how to address it. 
　
JBO-28009: PCollException 
Cause: An unexpected error occurred while attempting to get the system date from the database. For the Oracle persistent manager, the SQL statement used for this would be "select sysdate from dual". 
Action: Look at the details of this exception for further information on the problem and how to address it. 
JBO-28010: PCollException 
Cause: An error occurred while attempting to get the next value of a database sequence. 
Action: Make sure that the sequence object exists in the database. Also look at the details of this exception for further information on the problem and how to address it. 
JBO-28011: PCollException 
Cause: An error occurred while attempting to query for the next id from a pers coll table. 
Action: Look at the details of this exception for further information on the problem and how to address it. 
JBO-28012: PCollException 
Cause: An error occurred while attempting to create add a key column on a database table that stores persistent collection material. 
Action: Look at the details of this exception for further information on the problem and how to address it. 
JBO-28013: PCollException 
Cause: An error occurred while attempting to create a database table to store key info for persistent collection material. 
Action: Look at the details of this exception for further information on the problem and how to address it. 
　
JBO-28020: PCollException 
Cause: An unexpected error occurred while passivating objects into the persistent store. An exception may have been thrown during serialization. 
Action: Look at the details of this exception for further information on the problem and how to address it. 
JBO-28021: PCollException 
Cause: An unexpected error occurred while activating objects from the persistent store. An exception may have been thrown during deserialization. 
Action: Look at the details of this exception for further information on the problem and how to address it. 
JBO-28030: PCollException 
Cause: An unexpected error occurred while inserting a passivation row into the persistent store table. 
Action: Look at the details of this exception for further information on the problem and how to address it. 
JBO-28031: PCollException 
Cause: An unexpected error occurred while updating a passivation row in the persistent store table. 
Action: Look at the details of this exception for further information on the problem and how to address it. 
JBO-28032: PCollException 
Cause: An unexpected error occurred while deleting a passivation row from the persistent store table. 
Action: Look at the details of this exception for further information on the problem and how to address it. 
JBO-28033: PCollException 
Cause: An unexpected error occurred while retrieving a passivation row from the persistent store table. 
Action: Look at the details of this exception for further information on the problem and how to address it. 
JBO-28034: PCollException 
Cause: The client attempted to retrieve a row in a persistent collection by an id, but the by-id access is not enabled on the persistent collection. 
Action: Enable by-id access by calling PCollection.enableIdAccess. 
JBO-28035: PCollException 
Cause: The client attempted to retrieve a row by an id, but the id value is invalid. The id must be greater than 0. 
Action: Give a valid id. 
JBO-28036: PCollException 
Cause: While attempting to activate an object of a given id, an internal integrity problem was found. In particular, a node which was thought to be passivated was found to be active. 
Action: Contact JDeveloper Technical Support with how you ran into the problem. 
JBO-28037: PCollException 
Cause: While attempting to activate an object of a given id, an internal integrity problem was found. In particular, a child node/element expected to be