Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11g Release 2 (11.1.2.3.0)

Part Number E22506-03
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

10 JBO-24000 to JBO-80008

JBO-24000: no JAAS Context. Permission information is not available.
Cause: An error occurred while initializing the Java Authentication and Authorization Service (JAAS).
Action: Make sure that the JAAS configuration is correct.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-24001: Role {0} is not found.
Cause: An error occurred while retrieving the role.
Action: Make sure that the role information is correct.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-24002: User {0} is not found.
Cause: An error occurred while retrieving the user.
Action: Make sure that the user information is correct.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-24003: Attribute {2} in entity {1} is not updatable.
Cause: An attempt was made to update the attribute, but the user did not have permission or the attribute was not updatable.
Action: Make sure that the user permission and updatable setting for the attribute are correct.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-24004: Rows cannot be removed from entity {0}.
Cause: An attempt was made to remove the row, but the user did not have permission or the entity was read-only.
Action: Make sure that the user permission and read-only setting for the entity are correct.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-24005: Rows cannot be created in entity {0}.
Cause: An attempt was made to create a row, but the user did not have permission or the entity was read-only.
Action: Make sure that the user permission and read-only setting for the entity are correct.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-24006: The entity already has permission defined.
Cause: The entity already has permission defined.
Action: Modify permission def is not allowed.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-24007: Unable to get system property {0} when security manager is enable.
Cause: The property is not defined.
Action: Get property value is not allowed.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25000: SQL type {0} is invalid.
Cause: An attempt was made to generate a null value for a domain with an invalid SQL type.
Action: Provide a valid SQL type name for the domain. Examples include VARCHAR, CHAR and NUMBER. See oracle.jbo.server.OracleTypeMapEntries for a full list.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25001: Object {1} of type {0} already exists.
Cause: An attempt was made to load a business component with the same name and type as another business component already loaded by the application module.
Action: Provide a different name for the business component. If a null value or null string is provided for the name, the framework will create a unique name within the scope of the application module.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25002: Definition {1} of type {0} is not found.
Cause: A definition object with the given name could not be found.
Action: Provide a correct name for the business component definition (using the format 'packagename.objectname') and ensure that the definition is available on the classpath. This error can also occur if there is a case conflict, as when the database expects 'DEPTNO' and receives 'Deptno' instead.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25003: Object {1} of type {0} is not found.
Cause: A business component object with the given name could not be found in the application module.
Action: Provide a different name for the business component object or create a new business component with the given name.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25004: Definition name {1} of type {0} is invalid.
Cause: An attempt has been made to load an invalid definition name or associate a definition name with a type for which it is not valid.
Action: Ensure that the name is a valid Java identifier with no spaces or punctuation, and conforms to the format 'packagename.objectname'.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25005: Object name {1} of type {0} is invalid.
Cause: An attempt has been made to associate a business component name with an object for which it is not valid.
Action: Ensure that the name is a valid Java identifier with no spaces or punctuation, and conforms to the format 'packagename.objectname'.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25006: Value {2} passed as parameter {1} to method {0} is invalid: {3}.
Cause: An attempt was made to invoke a business components method with an invalid parameter value.
Action: Pass a correct value for the parameter. To determine the allowed values for a given parameter, check the Javadoc for the method that throws this exception. For example, Javadoc indicates that the 'DBTransactionImpl.executeCommand' method throws this exception when the 'command' parameter is empty.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25007: The validation flag cannot be reset for a default iterator.
Cause: An attempt was made to reset the row validation flag for the default iterator of a rowset or view object.
Action: Reset the row validation flag for the rowset or view object instead. This will create a secondary iterator to allow the rowset or viewobject to navigate to another row without validating.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25008: Object {0} cannot be removed because it is referenced by object {1}.
Cause: An attempt was made to remove a view object that is participating in a view link.
Action: Remove the view link before removing the view object.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25009: Cannot create an object of type:{0} from type:{2} with value:{1}
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 constructor threw an unexpected exception.
Action: Ensure that the value being passed is valid with respect to the domain type being created. For example, passing the string value 'one' to the 'oracle.jbo.domain.Number' constructor will throw this exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25010: A validation failure has occurred while creating a domain with value {0}.
Cause: Validation failed with the given value in a domain constructor. This exception is thrown in the domain type 'validate()' method.
Action: Provide a valid value for the domain type.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25011: Rowset {0} is forward only.
Cause: An attempt was made to invoke an invalid navigation method on 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25012: View object {0} does not have entity {1} as its primary base.
Cause: The client attempted to locate a view row that has the given entity row as its primary entity row. However, the entity row's entity definition does not match the entity definition of the view object's primary entity object base.
Action: Ensure that the entity row used to locate view rows is based on the same entity definition as the view object's primary entity object base.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25013: Too many objects match the primary key {0}.
Cause: An attempt was made to add a newly fetched or created entity to the cache, but the new entity has the same primary key as an existing entity. The primary key must be unique for this entity type.
Action: Add more attributes to the key definition for the 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25014: Another user has changed the row with primary key {0}.
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: 1. 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 <code>equals()</code> method on these domains do not fail when comparing the existing cached value with the newly fetched value. 2. 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. 3. Use 'view.executeQuery()' frequently, especially after any operations that result in data being changed.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25015: Query collection {0} is closed.
Cause: An attempt was made to execute a query or access a row from a closed or removed view object or rowset.
Action: Verify that the view object or rowset is not removed or closed.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25016: View object {0} is read-only.
Cause: An attempt was made 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 view row for this view object.
Action: Create a view object with the read-only flag set to 'false' in order to modify data.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25017: New entity row of type {0} cannot be created.
Cause: An unexpected exception occurred while creating a new entity instance.
Action: Ensure that the entity has a public default constructor. Fix the cause of the InstantiationException or IllegalAccessException that appears in the details of this exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25018: New view row of type {0} cannot be created.
Cause: An unexpected exception occurred while creating a new view row instance.
Action: Ensure that the view row has a public default constructor. Fix the cause of the InstantiationException or IllegalAccessException that appears in the details of this exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25019: Entity row with key {1} is not found in {0}.
Cause: An attempt was made to lock a nonexistent 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, 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25020: View row with key {1} is not found in {0}.
Cause: An attempt to find a referenced entity in the view row failed due to a changed foreign key value.
Action: Provide a valid foreign key value or remove the current one.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25021: Domain object type {0} cannot be created.
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 constructor threw an unexpected exception.
Action: Ensure that the value being passed is valid with respect to the domain type being created. For example, passing the string value 'one' to the 'oracle.jbo.domain.Number' constructor will throw this exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25022: A view link {0} already exists between source view object {1} and destination view object {2}.
Cause: An attempt was made to set the master rowset for this rowset more than once.
Action: Do not invoke 'setMasterRowSetIterator' more than once on a rowset.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25023: Operation {0} on domain value {1} of class {2} cannot be performed.
Cause: An unexpected domain exception occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25024: Method {0} is obsolete.
Cause: An attempt was made to use an obsolete type map constructor.
Action: Verify that the type map is compatible with this version of the framework. See example type maps in 'oracle.jbo.server.OracleTypeMapEntries'.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25025: Rowset with XML tag {0} cannot be loaded.
Cause: An error occurred while reading the XML data for a view object. This exception might contain other ReadXMLExceptions.
Action: Fix the contained row-level or attribute-level exceptions in the details for this exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25026: Row {1} with XML tag {0} cannot be loaded.
Cause: An error occurred while reading the XML data for a view row. This exception might contain other ReadXMLExceptions for contained rowsets or attributes.
Action: Fix the rowset-level or attribute-level exceptions in the details for this exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25027: Attribute {1} at index {2} with XML tag {0} cannot be loaded.
Cause: An error occurred while reading the XML data for an attribute of a view row. This exception might contain other JboExceptions thrown from the set method for this attribute.
Action: Fix the JboException in the details for this exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25028: Domain object type {0} cannot be created: {1}.
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 constructor threw an unexpected exception.
Action: Ensure that the value being passed is valid with respect to the domain type being created. For example, passing the string value 'one' to the 'oracle.jbo.domain.Number' constructor will throw this exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25029: Domain class {0} is not found.
Cause: The named data class (typically a domain) could not be found.
Action: Ensure that the data class is accessible from the CLASSPATH and is a valid data class.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25030: Detail entity {0} with row key {1} cannot find or invalidate its owning entity.
Cause: No container entity was found for a detail entity in a composition association. This could occur if a nonexistent master key value was passed in during creation of a new detail entity instance, or if the foreign key value of this entity was modified so that it no longer matched any master entity.
Action: Pass a valid foreign key value to the 'create' method or 'setAttribute' method so that an appropriate master row is found for this entity.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25031: View row for view object {0} is missing entity row for {1}.
Cause: The client 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 could be null if the foreign key linking the primary entity to the secondary entity object is null.
Action: Do not try to access attributes of missing entity rows in this situation.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25032: Passivation to target store {1} is unsuccessful.
Cause: A failure occurred while trying to passivate the application module or transaction state.
Action: Resolve the detail exception raised by the passivation target store (Database, File or Memory).

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25033: Activating state with id {0} from target store {1} is unsuccessful.
Cause: A failure occurred while trying to activate the application module or transaction state.
Action: Resolve the detail exception raised by the passivation target store (Database, File or Memory) and ensure that the state snapshot ID exists in the target store.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25034: Row with handle {1} is not found in rowset {0}.
Cause: The client attempted to locate a row with a stale row handle. This error might 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 might receive a new query collection. Thus, this error might occur 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 might 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 the row handle is not stale. One approach is to find the row again using its primary key before attempting to act on the row.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25035: The application module passivation store is invalid.
Cause: An application attempted to change an application module's passivation store after it had been initialized. The passivation store (Database, File or Memory) can 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 framework.
Action: Check the client application logic for invocations of ApplicationModuleImpl.setStoreForPassiveState which are invoked after the application module passivation store has been initialized.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25036: An invalid object operation was invoked on type {0} with name {1}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25037: Detail row set {0} is missing a master row set iterator for view link {1}, master view object {2}.
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 was removed through a call to removeMasterRowSetIterator() and has not been replaced with an appropriate one.
Action: Call setMasterRowSetIterator() to provide a valid master row set iterator.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25038: Value {2} passed as parameter {1} to method {0} is invalid.
Cause: An attempt was made to invoke a business components method with an invalid parameter value.
Action: Refer to the documentation of error message JBO-25006 (EXC_INVALID_PARAMETER) for more information. The difference between this error message and EXC_INVALID_PARAMETER is that this version does not include an explanation. In general, Oracle recommends using JBO-25006 instead of JBO-25038.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25039: No current row in row set iterator {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25040: Row should be locked before getting an output stream from an attribute.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25041: Type map cannot convert data from {1} to {0} with operation {2}.
Cause: The TypeFactory class asked the TypeMapEntries class to convert data, but the TypeMapEntries class did not know how to perform the conversion. This is typically an issue with the TypeMapEntries implementation.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25042: Row of trans post listener handle {0} not found in list.
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 to the row in database. This fails for whatever reason (this exception's detail might have further information). 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25043: Extraneous key {0} of index {1} (in key-value array) passed to findByKey for view object {2}.
Cause: Extraneous key passed in to findByKey(). For example, suppose the View Object expects no more than a two-part key, but the key passed into findByKey is a three-part key. Then, this exception will be thrown.
Action: Provide a valid key.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25044: Application state snapshot is based on an older version of the application definition metadata.
Cause: An attempt was made to activate application module or transaction state based on an older metadata definition into an application module with a later metadata definition.
Action: Ensure that snapshots used for state activation were generated from the currently running version of the application definition metadata.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25045: Row set iterator {0} has detected an implicit synchronization attempt.
Cause: An attempt was made to implicitly synchronize an iterator in a 3-tier running environment. When the application module synchronization mode is set to SYNC_BATCH, iterator synchronization must be done explicitly.
Action: Remove code that attempts to synchronize the iterator implicitly.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25046: Requested row not available in row set iterator {0}.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25047: Attempt to make call to server detected for application module {0}.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25048: Operation {0} is invalid for a working set object.
Cause: This operation is invalid for this working set object. It might be because the operation doesn't make sense in batch mode, or because the batch communication mode (WSApplicationModuleImpl.getBatchCommMode()) does not allow this operation.
Action: Remove code/operation that calls the named method of set the batch communication mode to allow this operation.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25049: Entity {0} cannot be set to batch mode because a key attribute is marked as refresh-on-insert or refresh-on-update.
Cause: An attempt was made to set batch mode on an entity that has a primary key marked as refresh-on-insert or refresh-on-update.
Action: Remove the refresh-on-insert or refresh-on-update setting of the primary key attribute.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25050: Batch mode post operation failed. See Exception details for a list of failures.
Cause: Posting entities in batch mode failed with a set of exceptions
Action: Fix the cause for each of the exceptions in the details array.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25051: Row of range index {1} is not found in RowSetIterator {0}.
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 might 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 might 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 the 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25052: View object {0} with no key attributes cannot be activated.
Cause: A view object with no key attributes was configured to passivate one or more of its transient attributes. However, a view object without key attributes cannot participate in state passivation.
Action: Define one or more key attributes for this view object.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25053: Cannot navigate with unposted rows in a RangePaging RowSet.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25054: Cannot locate the specified stack snapshot id: {0}
Cause: An attempt has been made to activate a stack snapshot that does not exist. The specified snapshot might already have been activated or the stack might already have been cleared by a previous rollback/commit.
Action: Ensure that stack snapshot ids are maintained by the application across transaction boundaries.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25055: Snapshot {0} cannot be removed.
Cause: An attempt was made to remove a persistent snapshot that is referenced by the snapshot stack.
Action: Clear the snapshot stack before attempting to remove the referenced snapshot.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25056: Cannot call removeFromCollection() or removeAndRetain() on an Entity row: Entity name {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25057: Entity row update operation did not find matching row: Entity name {0}, key {1}
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 might have modified the row and committed the changes.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25058: Definition {1} of type {0} is not found in {2}.
Cause: No business component definition found with the given name in the project classpath.
Action: Provide a correct name for the business component definition and ensure the definition is available on the classpath. Names are of the format <code>myProjectPackage.BusinessPackage.BusinessComponent</code>. This error can also occur if there is a case conflict, as when the database expects 'DEPTNO' and receives 'Deptno' instead.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25059: View Object {0} has ManageRowsByKey turned on, but its key definition is empty
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25060: Unexpected error encountered while trying to retrieve the next row from JDBC ResultSet for collection {0}
Cause: An unexpected exception was thrown while retrieving the next row from JDBC ResultSet.
Action: Take a look at the detail exception for further information and fix underlying problems.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25061: Cannot enable passivation for internal ViewObjects and rowsets.
Cause: ViewRowSetImpl.setPassivationEnabled called for internal rowset
Action: Create a datamodel ViewObject instance and use rowsets from that ViewObject to make them passivation enabled.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25062: Cannot find a matching detail ViewObject. Link definition: {0}, master row set iterator {1}.
Cause: An attempt was made to create detail rowset. However, no matching detail view object could be found.
Action: Ensure that a matching view object is present before attempting to create a detail rowset.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25063: Operation {0} cannot be performed because the working set object is not bound.
Cause: This operation is invalid for this working set object because the working set object is not bound to actual implementation object.
Action: This action must be performed after the working set object is bound.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25064: Variable {1} in RowSet {0} is not a where-clause parameter. It is of kind {2}.
Cause: A call was made to define or set a named where-clause parameter value. However, the named variable's 'kind' is not 'where'. That is, the variable is not a where-clause parameter.
Action: Make sure that the variable name is correct and that the named variable is a where-clause parameter.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25065: Named where-clause parameter {0} does not belong to ViewObject {1}. It belongs to an object of type {2}.
Cause: An attempt was made to remove a named where-clause parameter. However, this where-clause parameter is owned by neither the RowSet nor the ViewObject. Therefore, the parameter cannot be removed.
Action: It is illegal to try to remove a named where-clause parameter that does not belong to either the RowSet or the ViewObject.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25066: View Object {0} is based on an Entity built from Row Set. For such a View Object, cannot include QUERY_MODE_SCAN_DATABASE_TABLES in its query mode.
Cause: An attempt was made to include QUERY_MODE_SCAN_DATABASE_TABLES in the View Object's query mode (through a call to setQueryMode()). However, this View Object can perform query only through Entity Object. Hence, QUERY_MODE_SCAN_DATABASE_TABLES is inappropriate.
Action: The View Object is probably based on an Entity, which in turn is based on a RowSet (EntityDefOverRowSet). It is illegal to use QUERY_MODE_SCAN_DATABASE_TABLES for a View Object built on top of an Entity which is built over a Row Set. Do not include QUERY_MODE_SCAN_DATABASE_TABLES in the setQueryMode() invocation.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25067: Entity {0} has a subclass EO {1} and no discriminator. Therefore this base Entity cannot be used to create an Entity Row.
Cause: An attempt was made to create a new instance of an Entity Row. However, this Entity Definition has a subclass Entity Definition with no discriminator. That is, this Entity Definition should really be abstract.
Action: Typically in this situation, the base class should not instantiate any row. Use the subclass Entity to create the row

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25068: Entity {0} has a base EO {1} with no discriminator, but base EO has rows in its cache. Cannot populate both caches.
Cause: An attempt was made to create a new instance of an Entity Row. However, this Entity Definition is a subclass Entity Definition with no discriminator, and a base EO has a row already instantiated. A conflict exists because nothing discriminates this Entity from the base Entity.
Action: Typically in this situation, the base class should not instantiate any row. Use the subclass Entity to create the row

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25069: Row definition {0} has two sibling subclasses defs, {1} and {2}, but no discriminator to distinguish them.
Cause: Two sibling subclasses of a Row Definition are found, but the Row Definition has no discriminator. This condition is disallowed because when a row is either retrieved or created, the framework cannot determine the correct row class. That is, the hierarchy forks withouth a discriminator. The only situation whether subclassing is allowed without discriminator is when the tree is straight lined and only one of the classes in the hierarchy line is used to instantiate rows.
Action: Either define discriminator attributes, or do not create siblings in the row class hierarchy.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25070: Where-clause param variable {0} needs ordinal index array.
Cause: This view object of entity is using Oracle number style binding (:1, :2, ... binding, not named binding) or JDBC style (? binding). A variable of where-clause-param kind is found, but the extended int array that designates where the value should be bound is missing.
Action: When defining a variable for where-clause param in conjunction with a binding style which is not Oracle named binding, specify an int array that designates where the value should be bound.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25071: Applying List binding {1} with given set of values leads to multiple matching rows for a row of type:{0}, key {2}
Cause: ListBinding results in more than one matching row for the given set of mapping values. Only one matching row is expected.
Action: Provide a new set of mapping values that will end up in a single matching row or adjust the StructureDef metadata to allow defaulting to the first matching row.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25072: Applying List binding {1} with given set of values leads to no matching row for a row of type :{0}, key {2}
Cause: ListBinding failed to find any matching row for the given set of mapping values.
Action: Provide a new set of mapping values that will end up in a single matching row or adjust the StructureDef metadata to allow defaulting to the first matching row.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25073: Definition {1} of type {0} is hidden
Cause: Def object is hidden. An attempt was made to access a hidden def object.
Action: This particular operation is disallowed on a hidden def object. Avoid this operation.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25074: Definition {1} of type {0} is hidden in {2}, operation: {3}
Cause: Def object is hidden. An attempt was made to access a hidden def object in the specified container object.
Action: This particular operation is disallowed on a hidden def object. Avoid this operation.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25075: Definition {0} of type {1} is read-only. Cannot modify it
Cause: Attempting to modify or save data for a def object which is read-only.
Action: If the def object is shared, do not attempt to modify anything. If the def object is session scoped, do not modify it if there are running instances of that definition. If the def object is session scoped and is not being used by any running instance, mark it editable before modifying it.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25076: Expression validator does not allow setting a value to source attribute:{0}.
Cause: Expression validator does not allow direct assignment of a value to an attribute. This is to avoid possible cycle of assignments/validations.
Action: Remove direct assignments. If assignment is necessary, verify there is no cycle, and then use constructs like 'source.MyVar = ..'.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25077: Name {0} not found in the given object: {1}.
Cause: An invalid name was passed in an expression.
Action: Fix the expression by passing in a correct name for a property.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25078: Key attribute {1} for {0} not populated
Cause: While building the where-clause statement for an entity row operation (e.g., fault-in, delete, or update), the named key attribute value is not populated.
Action: This entity row operation requires the key attributes to be populated. Make sure that all key attributes have values in them.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25079: The list of discriminator attributes for subclass {0} is different from that of the base {1}
Cause: In a subclass hierarchy of RowDefs, found a subclass RowDef whose discr attr list has more attrs than the base class. It is disallowed for a subclass to change discr attr list in the subclass hierarchy.
Action: Make sure that subclass RowDefs have the same set of discr attributes as the base class.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25080: Definition name: {0} does not match the file in which it is loaded from: {1}
Cause: An attempt has been made to load a definition metadata file named differently from the name or id of the top level xml element in the file.
Action: The name should be a valid Java identifier with no spaces or punctuation. The name or id of the top level xml element in the file should match the file name.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25081: The new fetch size {0} passed into setFetchSize() for a view object {2} is invalid. It is smaller than the old value {1}.
Cause: The fetch size passed into <code>ViewObjectImpl.setFetchSize()</code> is smaller than the previous value. Fetch size of a view object cannot decrease.
Action: Specify a value which is bigger than the current value.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25082: Cannot change the access mode for the row set {0} because either the VO has more than one RS or the RS has more than one iterator.
Cause: An attempt has been made to change the row set's access mode from scrollable/forward-only to range-paging or vice versa. This is allowed only if the VO has one or no row set. Or, an attempt has been made to set the row set's access mode to forward-only, but this is allowed only if the row set has one or no iterator.
Action: Close other row sets or iterators before changing the access mode.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25083: Cannot create a secondary iterator on row set {0} because the access mode is forward-only or range-paging
Cause: An attempt has been made to create a new row set iterator on a row set whose access mode is either forward-only or range-paging.
Action: Creation of secondary row set iterator is allowed if the row set's access mode is scrollable.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25084: Cannot call last() on row set {0} because the access mode uses range-paging
Cause: An attempt has been made to jump to the last row on a row set whose access mode uses range-paging.
Action: Replace 'last' with 'setRangeStart' for the range-paging based access mode.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25085: The value being set for attribute {0} does not match the value derived from list binding {1}
Cause: An attribute value being set does not match the attribute value derived from a list binding. This typically happens in the following situations. First, suppose the user sets values for Deptno from 10 to 20 and Dname from ABC to DEF. If a list binding is triggered by Deptno and if it sets Dname to XYZ, the result is an inconsistent state where DEF does not match XYZ. In this situation, this exception is thrown. Second, suppose there is an EmpDept view object with Emp and Dept entity bases. Suppose Dept is reference and read-only and there is a list binding on Dept.Dname whose derived attribute is Emp.Deptno. If the user selects a new Dept through the dept name, a new Dept entity row is brought in (because a new Emp.Deptno is chosen). After this, the framework checks to make sure that the Dname coming from the new entity row matches the original selection from the list bindng. If they do not match, this exception is thrown.
Action: Make sure the list binding definition and attribute set values end up in a consistent result (i.e., the derived values from the list binding match the row's attribute values).

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25086: Operation {1} cannot be performed until definition {0} is resolved.
Cause: An attempt was made to use a def object before resolving it. The def object must be resolved first.
Action: Make sure resolveDefObject() is called before this operation.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25087: Cannot call getRowCount() on row set {0} because the access mode uses range-paging
Cause: An attempt has been made to get the row count of a row set whose access mode uses range-paging.
Action: Replace getRowCount() with getEstimatedRowCount() for range-paging based access mode.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25088: Persdef {0} has no static definition set
Cause: An attempt was made to perform an operation on a persdef that requires the static definition object, but the persdef has no static definition.
Action: Set the static definition object before attempting the operation.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25089: View object {0} attempted to fetch rows beyond the row limit
Cause: The view object attempted to fetch rows beyond a global row limit.
Action: If in a search region narrow down the results by providing more search criteria otherwise contact your system administrator.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25090: Attribute value {3} leads to duplicate keys for this entity type {1}.
Cause: An attempt was made to set an attribute value that leads to addition of a newly fetched or created entity to the cache, but tut this value makes the entity key same as another existing entity. The primary key must be unique for this entity type.
Action: Add more attributes to the key definition for the entity type, so that each row for this entity is uniquely identifiable. Or fix the key value so that this entity has a unique key identifier.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25091: View object {0} has no primary entity
Cause: An attempt was made to get the primary post state of a view row that has no entity usages.
Action: Only call this method on a view row with one or more entity usages

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25092: Programmatically accessible view object definition {0} is not found.
Cause: An attempt has been made to find a view definition using a short name and no corresponding custom or standard object can be found.
Action: Use a shortname that corresponds to the name of a custom object in a registered custom object base package or elsethe name of a standard object that has been registered to be programmatically accessible.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25093: Attribute {0} is being modified, while it is being validated causing an infinite loop.
Cause: An attempt was made within an expression or validation rule to update an attribute while that attribute is being validated.
Action: Remove the call to set the erring attribute value

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25150: The method {1} on class {0} is not permitted.
Cause: An attempt was made within an untrusted expression to call a method not on the list of allowed methods.
Action: Add the method to the list of allowed methods in adf-config.xml

Level: 1

Type: ERROR

Impact: Security

JBO-25151: Accessing the {1} property on class {0} is not permitted.
Cause: An attempt was made within an untrusted expression to access a property not allowed by methods on the list.
Action: Add the get and set methods corresponding to the property to the list of allowed methods in adf-config.xml

Level: 1

Type: ERROR

Impact: Security

JBO-25152: Calling the constructor for class {0} is not permitted.
Cause: An attempt was made within an untrusted expression to call a constructor not on the list of allowed constructors.
Action: Add the constructor to the list of allowed constructors in adf-config.xml.

Level: 1

Type: ERROR

Impact: Security

JBO-25153: Calling the {1} method on class {0} is not permitted.
Cause: An attempt was made within an untrusted expression to call a constructor not on the list of allowed constructors.
Action: Use an alternate method.

Level: 1

Type: ERROR

Impact: Security

JBO-25154: Calling the {1} function is not permitted.
Cause: An attempt was made within an untrusted expression to call a method which is on the list of blacklisted methods on scripts.
Action: Rename the method, or call it from a trusted context.

Level: 1

Type: ERROR

Impact: Security

JBO-25155: Defining an additional method is not permitted.
Cause: An attempt was made within an untrusted expression to define an additional method.
Action: Create the same logic without the use of an embedded method, or mark the script as trusted.

Level: 1

Type: ERROR

Impact: Security

JBO-25156: Defining an additional class is not permitted.
Cause: An attempt was made within an untrusted expression to define an additional class.
Action: Create the same logic without the use of an embedded class, or mark the script as trusted.

Level: 1

Type: ERROR

Impact: Security

JBO-25157: Calling the {1} method on class {0} is not permitted when used in a static context.
Cause: An attempt was made within an untrusted expression to call a method which is blacklisted when used in a static context.
Action: Instead use the method on an instance of the class.

Level: 1

Type: ERROR

Impact: Security

JBO-25158: Accessing the {1} property is not permitted.
Cause: An attempt was made within an untrusted expression to use a property on the list of blacklisted properties.
Action: Instead access the property with an allowed method.

Level: 1

Type: ERROR

Impact: Security

JBO-25159: Accessing the {1} property, when used in a static context on class {0}, is not permitted.
Cause: An attempt was made within an untrusted expression to use a property in a static context on the list of blacklisted properties.
Action: Instead access the property with an allowed method, or use in an instance context.

Level: 1

Type: ERROR

Impact: Security

JBO-25160: Defining a method pointer is not permitted.
Cause: An attempt was made within an untrusted expression to define a method pointer.
Action: Create the same logic without the use of a method pointer, or mark the script as trusted.

Level: 1

Type: ERROR

Impact: Security

JBO-25161: Calling the {1} function is not permitted.
Cause: An attempt was made within an untrusted expression to call a method which is not allowed on scripts.
Action: Rename the method, or call it from a trusted context.

Level: 1

Type: ERROR

Impact: Security

JBO-25162: Using the Java field operator (.@) is not permitted.
Cause: An attempt was made within an untrusted expression to directly access a Java field via '.@'.
Action: Create the same logic without the use of the '.@' operator, or mark the script as trusted.

Level: 1

Type: ERROR

Impact: Security

JBO-25170: Expression timed out.
Cause: An untrusted expression exceeded the maximum time allotted for a run.
Action: Break the task up into multiple tasks, increase the timeout value, or mark the script as trusted.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25171: Expression exceeded the maximum number of new view instances ({0}).
Cause: An untrusted expression exceeded an allowed use of resources.
Action: Change your expression to use fewer resources.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25180: Exception in expression "{0}": {2}
Cause: An exception has occurred within a Transient Expression.
Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25181: Exception in expression "{0}" recalc expression {1} : {2}
Cause: An exception has occurred within a Recalc Expression.
Action: Examine the details to find the root cause, and modify the Expression to avoid the root exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25182: Exception in expression "{0}" validation rule {1} : {2}
Cause: An exception has occurred within a Validation Rule expression.
Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25183: Exception in expression "{0}" trigger {1} : {2}
Cause: An exception has occurred within a Trigger expression.
Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25184: Exception in expression "{0}" object function {1} : {2}
Cause: An exception has occurred within an Object Fucntion.
Action: Examine the details to find the root cause, and modify the function to avoid the root exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25185: Exception in expression "{0}" global function {1} : {2}
Cause: An exception has occurred within an Object Fucntion.
Action: Examine the details to find the root cause, and modify the function to avoid the root exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25186: Exception in expression "{0}" of unknown type {1} : {2}
Cause: An exception has occurred within an expression of unknown type.
Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25200: Application module is not connected to a database.
Cause: The application module is not connected to the database.
Action: Provide a valid set of connection credentials to connect to a database.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25201: A database connection already exists.
Cause: An attempt was made to reestablish a database connection.
Action: Disconnect the current database connection before trying to reestablish the JDBC connection.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25221: Method {0} not supported
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. <code>setAttribute()</code> in <code>oracle.jbo.Key</code> class is not implemented and will throw this exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25222: Unable to create application module.
Cause: The application module was typically not created for one of the following reasons: 1. Business components deployed in local mode were not found on the classpath. 2. Unresolved classes existed on the server. 3. Java2 permissions were not granted. 4. Java pool size was too small.
Action: Depending on the cause, chose from the following actions: If business components are deployed in local mode, they might not be on the classpath. <br>If this is the cause of the error, the exception will usually be followed by a different exception, JBO-25002: NoDefException. If this occurs, try the following: Make a library for the business components. Add the library to the client's project properties. Include the library on the 'libraries' page when creating a deployment profile for the client (whether the client was a web application or a command-line application). Copy the library with the client to the target platform (whether the client was a web application or a command-line application). Include all the copied files (including the library) when setting the classpath on the target platform. There might be unresolved classes on the server. Try the following procedure to resolve any unresolved classes on the database. In the System Navigator, right-click the JDBC connection used to deploy the Business Components project. Choose Invoke SQLPlus from the context menu. Copy and paste the following SQLPlus script into the SQLPlus window. set termout off set echo off set heading off set pages 999 set linesize 2000 set feedback off select 'alter java class "'|| replace(dbms_java.longname(object_name),'/','.')||'" resolve;' from user_objects where object_type='JAVA CLASS' and status = 'INVALID' spool C:\temp\resolve.sql / spool off set echo on set termout on @C:\temp\resolve.sql There might be missing Java2 permissions. If this is the cause of the error, there will be permissions errors in the database trace file. To correct the problem, see the help topic 'Granting Permissions on a Business Components EJB' for information on granting Java2 permissions. Note: The location of the database trace file varies from installation to installation, but in a default Windows NT installation, the file will be in the directory ORACLE_HOME\admin\orcl\ udump and will have the form orclnnnn.trc. The Java pool size might be too small Business Components for Java deployed as EJBs work best with a Java pool size of at least 50MB. Edit the init.ora file and check the <code>java_pool_size</code> parameter. If it is under 50MB, change it, restart the database, and try the connection again.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25223: Cannot create multiple root application modules.
Cause: When business components are running inside JServer, only one root application module can 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25224: Could not disconnect and retain application module state because database state exists for current connection.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25226: Application module definition {0} contains recursive AM reference.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25227: Recursive view links found. Master-detail chain: {0}.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25228: Unable to register a database change notification request for {0} view object
Cause: The View Object that has auto refresh turned on failed to register an Oracle database change notification request.
Action: Ensure that the database user is granted CHANGE NOTIFICATION privilege. Look at the exception details for further troubleshooting.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25229: Unable to unregister a database change notification request for {0} view object
Cause: The View Object that has auto refresh turned on failed to unregister an Oracle database change notification request.
Action: Look at the exception details for further troubleshooting.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25230: XML document {0} has no stream to save
Cause: An attempt was made to save XML document, but the document has not been persisted (most likely saveXMLContents() is called without a call to writeXMLContents()).
Action: Call writeXMLContents() first.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25301: Application module {0} is not a root app module but has no parent
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, the application code might be 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 framework, in which case contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25302: Component object {0} has no parent
Cause: A business component is found without a container (parent) application module.
Action: If this application has added custom business component classes, the application code might be 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 the framework, in which case contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25303: Cannot clear entity cache {0} because it has modified rows
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25306: Design-time attribute {0} of type {1} could not be persisted
Cause: Could not persist a design-time attribute into the XML file.
Action: Identify the offending design-time attribute and contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25307: XML file not open
Cause: XML file is not open.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25308: The primary key of an existing entity bean cannot be modified for entity facade {0}.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-25309: The primary key of an entity bean cannot be null for entity facade {0}.
Cause: The primary key of an entity bean is null. This is disallowed by EJB.
Action: Set the primary key to be not null.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26000: A Generic exception occurred during loading Customizations.
Cause: Metadata objects failed to load due to unexpected or corrupt data in the XML file.
Action: Verify that the XML metadata for various components is valid.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26001: XML File not found for the Container {0}
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 supports 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 might 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 contained object. In all of the above cases, a more descriptive message might be printed on Diagnostic. To see these messages, run the application with Diagnostic turned on, as in 'java -Djbo.debugoutput=console ...', to see Diagnostic messages.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26002: Error Parsing the XML file "{0}".
Cause: Some XML parsing exception (<code>oracle.xml.parser.v2.XMLParseException</code>) was thrown.
Action: The XMLParseException information is output to Diagnostic. To see diagnostic messages, run the application with diagnostic turned on, for example 'java -Djbo.debugoutput=console ...'

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26003: Mismatch in the attribute indices declared in Java versus the indices in the definition for entity {0}.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26004: A recursive base definition is found while attempting to set the base definition of {0} to {1}.
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 the subclassing hierarchy of the definition objects and correct errors.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26005: FetchMode must be either FETCH_AS_NEEDED, FETCH_ALL or FETCH_DEFAULT. View object {0}
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'

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26006: FetchSize must be a positive integer. View object {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26007: MaxFetchSize should be MAX_FETCH_UNLIMITED, MAX_FETCH_DEFAULT or integer. View object {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26008: Could not resolve reference to "{0}".
Cause: A problem is found in resolving a view link definition or an association. In case of a view link, this error might 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 might 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26009: Serialized file "{0}" is invalid. The root object is not a Business Component object.
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 was deserialized, the top level object returned from deserialization was not an instance of oracle.jbo.server.xml.JboElementImpl.
Action: Repair the corrupt .ser file.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26010: Invalid Entity Attribute Name "{1}" specified for the View Attribute "{0}"
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26011: SQLType not specified for the View Attribute "{0}"
Cause: Attribute definition found in XML file is invalid. It is missing SQLType value.
Action: Correct the error in the XML file.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26012: Invalid View Link Definition "{0}". View Link must have two ViewLinkDefEnds.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26013: Naming Exception occurred while looking up the object "{0}".
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 <code>package1.example.Emp</code>. 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26015: View object {0} does not include a discriminator column {2} of entity base {1}.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26016: Cannot set user query to view "{0}" because it is a destination in a view link
Cause: An attempt was made to call 'setQuery()' on a detail view object in a master detail view link.
Action: Do not call setQuery() if the view object is a detail.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26017: Association or view link definition {0} has an invalid attribute list.
Cause: The association or view link definition has a missing or invalid attribute list.
Action: Correct the error(s) in the XML file.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26018: Entity {0} cannot be posted to the database because it has no attributes set.
Cause: An attempt was made to post a row with no attribute set. Some databases (Oracle Database in particular) 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26019: Attempting to remove a parent entity without removing all children entities
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 via an association and removing all of them.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26020: Attempting to insert row with no matching EO base
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26021: NullPointerException while parsing XML file "{0}". Perhaps missing DTD file?
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26022: Custom class {0} cannot be found.
Cause: A custom class could not be found and loaded. The custom class might be for a component (for example, view object), a definition (for example, view definition), or a row (for example, view row or entity row).
Action: Make sure that the named class is reachable from the CLASSPATH. The detail exception (if present) provides more specific reasons why the attempt to locate and load the custom class failed.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26023: Custom class {0} is not assignable to {1}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26024: An error occurred while creating InitialContext
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: When 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);

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26025: An error occurred while trying to get System properties
Cause: An error occurred while trying to get System properties. Specifically, System.getProperties() call failed.
Action: When 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');

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26026: An error occurred while loading properties from a properties file {0}
Cause: An error occurred while trying to get load properties.
Action: Check to see if the named properties file contains valid Java properties.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26027: Unable to find resource. {0}
Cause: Unable to find a resource
Action: Check to see if the resource exists and the framework code has adequate permissions to load the resource.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26028: View object {0} does not include a primary key attribute {2} of entity base {1}.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26029: Could not find and load the type map class {0}
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 might 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 provide more specific reasons why the attempt to locate and load the custom class failed.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26030: Failed to lock the record, another user holds the lock.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26031: Association end {0} of assoc {1} invalid for entity base {2} in view object {3}.
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 association. For such a view definition, the framework 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 association end to perform join.
Action: Most commonly, this is caused by incorrect information in the view object XML file. Make sure that the association end for the named entity usage is not pointing at the wrong end of association.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26032: Operation {0} is invalid for a ViewCriteria or ViewCriteriaRow.
Cause: The attempted operation is invalid for a ViewCriteria or ViewCriteriaRow.
Action: Remove code that attempts this operation.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26033: Cannot find Application Data Model with name :{0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26034: Cannot find Configuration with name :{0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26035: Secondary entity usage {0} is missing parts of association description.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26036: The configuration of meta object {0} causes recursive substitution.
Cause: An attempt was made to set up meta object substitution that leads to recursion. For example, consider a substitution where C substitutes B, and B substitutes A, and A substitutes C. This results in a recursive substitution and will cause this error.
Action: Review the meta object substitution and correct errors.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26037: Cannot find matching EO from discriminator columns for view object {0}, entity base {1}, discr value {2}.
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 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 discriminator column values match one and only one entity object.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26038: Cannot find an entity usage for entity {1} in view link definition {0}, view link end {2}.
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 source and destination are not switched with those of the entity association.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26039: View object {0} does not include an alternate key attribute {2} of entity base {1}, entity key {3}.
Cause: A view definition does not include an alternate key attribute of an entity base. When a view object uses an entity as one of its entity bases, and when it defines a view object level alternate key using one of the entity alternate keys, it must map the entity attributes that make up the alternate key.
Action: Change the view definition to include all necessary alternate key attributes.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26040: Failed to post entity {1} to database during "{0}" : SQL Statement "{2}".
Cause: Some database error occurred while posting (writing) an entity to the database in JDBC batch mode. 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26041: Failed to post data to database during "{0}": SQL Statement "{1}".
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26042: Failed to generate REF and OID on entity {0}.
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(table-name, a.oid) ... Somehow, this statement is failing.
Action: Ensure that : The Oracle database version is correct. The table in question is 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26043: REF and OID not supported by this SQLBuilder on entity {0}.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26044: Error while getting estimated row count for view object {0}, statement {1}.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26045: Failed to generate PK-Based REF on entity {0}.
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: Ensure that: The Oracle database version is correct. The table in question is an object table. The object table uses 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26046: PK-Based REF not supported by this SQLBuilder on entity {0}.
Cause: An attempt was made to generate Oracle o8 object ref from a non-Oracle database SQLBuilder. This is not supported.
Action: Make sure that the correct SQLFlavor (i.e., SQLBuilder) is being used for the application and switch to the right one.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26047: LOCK_OPTUPDATE mode update operation missing change indicator value: Entity {0}, key {1}.
Cause: An attempt was made to update a row in LOCK_OPTUPDATE mode and the change indicator attribute value is not present.
Action: Look at the attribute mapping of the View Object that read in this Entity row and make sure that the View Object includes the change indicator attribute. The LOCK_OPTUPDATE mode requires the value to be present.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26048: Constraint "{2}" is violated during post operation "{0}" using SQL statement "{1}".
Cause: A constraint violation occurred in the database while posting (writing) an entity to the database. This error carries a detail exception from the database which will give further information about the database failure.
Action: Fix the cause for the constraint violation. Look at the details of the exception and address the database problem.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26049: An error occurred during loading definition {0}.
Cause: Metadata objects failed to load due to unexpected or corrupt data in the XML file.
Action: Verify that the XML metadata for various components is valid.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26050: An error occurred while writing personalization definition {0}.
Cause: An I/O error occurred while writing personalization definition.
Action: Check the detail I/O exception and make necessary correction.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26051: Unrecognized XML element tag {1} found in meta object {0}.
Cause: The element tag of the XML file is not recognized.
Action: Examine the XML file and make sure that the element tag is one of the recognized ones.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26053: Invalid association or view link definition "{0}". Invalid unbound attribute list.
Cause: An association or view link definition end has an invalid unbound attribute list. This error is raised if the unbound attribute is not one of the association/view link end attributes.
Action: Correct the error(s) in the XML file.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26054: Invalid version number for {0}. Require {1} or greater, but found {2}.
Cause: The XML document is either missing the version number or has a version number which is lower than the required version number.
Action: Check to see if the XML document has gone through a proper migration process. If not, migrate the application.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26055: Failed to delete XML document {0}.
Cause: An attempt was made to delete an XML document from disk, but this operation failed.
Action: When running with MDS, make sure that the metadata store supports the delete operation. Check the detail exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26056: Multiple occurrences of XML element {1} found in {0}. Only one expected.
Cause: Multiple occurrences of an element were found in the XML document when only one was expected.
Action: Examine the XML document and see which element shows up mutiple times. If the issue looks like a problem in the framework's persistence code, report it.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26057: Recursive entity references found in view def {0}. Entity refs: {1}
Cause: An attempt was made to create a view definition whose entity references have a cycle in it. For example, a view definition contains two entity references E and F, where E's source reference is F, and F's is E.
Action: Review your code that builds the view def. Make sure that entity references do not have a recursion in it.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26058: Cannot define view link {0} in application module {1}. The view object {2} is in application module {3} and the view link''s application module is not a child of the view object''s application module.
Cause: An attempt was made to establish a data model view link in an application module, but either the master or the detail view object is in an AM which is not the same AM as the view link's, or is not a parent of the view link's AM.
Action: When creating a data model VL, the VL's AM must be the same as the VO's, or must be a child (nested) AM of the VO (for both master and detail).

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26059: Invalid View Link Usage "{0}". Either the source "{1}" or the destination "{2}" is not defined.
Cause: The ViewLink Usage is not correctly defined.
Action: Specify both source and destination for the ViewLink Usage.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26060: Error while registering JDBC driver.
Cause: A SQLException occurred while trying to register a JDBC driver.
Action: Fix the underlying SQLException.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26061: Error while opening JDBC connection.
Cause: A SQLException occurred while trying to open a JDBC connection.
Action: Fix the underlying SQLException.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26062: Error while closing JDBC connection.
Cause: A SQLException occurred while trying to close a JDBC connection.
Action: Fix the underlying SQLException.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26064: Error while closing JDBC statement.
Cause: A SQLException occurred while trying to close a JDBC connection.
Action: Fix the underlying SQLException.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26065: Error during commit.
Cause: A SQLException occurred during the commit phase of this transaction.
Action: Fix the underlying SQLException.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26066: Error during rollback.
Cause: A SQLException occurred during the rollback phase of this transaction.
Action: Fix the underlying SQLException.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26067: Failed to add JDBC connection to the connection pool, connection pool is full.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26068: Failed to return JDBC connection to the connection pool, connection does not belong to the pool.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26069: Client request was timed out while waiting for a connection to be returned to the connection pool.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26070: Column definition retrieval from JDBC failed on view object {0}.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26071: Access mode {1} is invalid. View object {0}
Cause: The access 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 'AccessMode'. Make sure that the value for that element is valid.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26072: Another user changed the document {0}.
Cause: The client requested to write metaobject, but the metaobject document was updated by another user.
Action: This exception carries the most up to date def object. Resolve the differences and retry write.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26073: Document {0} has no MDS key.
Cause: The client requested to write metaobject, but the metaobject's MDS key is null and so we cannot perform the consistency check.
Action: An existing definition object's MDS key should not be null. Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26074: MDS detected another user changed the document {0} since the mutable MO was obtained.
Cause: The client requested to write metaobject, but the metaobject document was updated by another user. The difference between this error and <code>EXC_PERS_DOC_INCONSISTENT</code> is that this error is detected by MDS between <code>getMutableMO()</code> and <code>flushChanges()</code>. <code>EXC_PERS_DOC_INCONSISTENT</code> is raised by an MOKey check.
Action: This exception carries the most up to date def object. Resolve the differences and retry write.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26075: Document {0} exists. Another user just created the same doc.
Cause: The client requested to create a new document. While creating and flushing the MDS MO, MDS threw a document-exists-exception, which means that another user just created the same document.
Action: Retry creating the document.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26076: Merge for definition {0} failed for elem {1}. Inserted elem [{2} -> {3}] was deleted by another user.
Cause: During object merge, found a metadata element which was marked for insertion by the current user, but was deleted by another transaction committed or published by another user.
Action: Resolve this metadata merge conflict.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26077: Merge for definition {0} failed for elem {1}. Updated elem [{2} -> {3}] was deleted by another user.
Cause: During object merge, found a metadata element which was marked for update by the current user, but was deleted by another transaction committed or published by another user.
Action: Resolve this metadata merge conflict.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26078: Merge for definition {0} failed for elem {1}. Inserted elem [{2} -> {3}] was inserted by another user.
Cause: During object merge, found a metadata element which was marked for insertion by the current user, but was inserted by another transaction committed or published by another user.
Action: Resolve this metadata merge conflict.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26079: Merge for definition {0} failed for elem {1}. Updated elem [{2} -> {3}] was updated by another user.
Cause: During object merge, found a metadata element which was marked for update by the current user, but was updated by another transaction committed or published by another user.
Action: Resolve this metadata merge conflict.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26080: Error while selecting entity for {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26081: Error while getting datum for attribute {1} in {0}
Cause: A SQLException occurred when converting data from JDBC to <code>oracle.jbo.domain.Struct</code> attributes.
Action: Fix the conversion errors as suggested in SQLException.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26083: Comparison operator {0} has a string code for its description, but the message bundle class cannot be found.
Cause: A comparison operator was specified with string code, but the message bundle class could not be loaded. When specifying a string code for translatable operator description, the framework first checks to see if the operator specification includes a message bundle class name. If so, it attempts to find the string in that message bundle. If not, then the framework tries to find the string in the owning object's (either view object or entity object) message bundle. If both fail, this error is raised.
Action: Make sure that the comparison operator specification is correct in the XML file.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26084: Invalid association definition "{0}". Association must have two AssociationEnds.
Cause: The association definition in the XML file is missing either the source or destination association end. For an association XML file, two elements named AssociationEnd should be found.
Action: Correct the error in the XML file.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26085: Missing association name in EO-exists validator {0} of {1}.
Cause: The EO-exists validator is missing the association name in its definition.
Action: Correct the error in the XML file.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26086: Association attributes do not match the destination EO''s primary keys in EO-exists validator {0} of {1}.
Cause: The EO-exists validator's source side attribute list does not match the desination EO's primary keys. For example, suppose there is a PurchaseOrder EO which includes an EO-exists validator to Customer EO. PurchaseOrder EO is using association CustToPurch to validate. In this case, the association attribute list on the PurchaseOrder side match with Customer's PK exactly (order does not matter--they must equal as sets).
Action: Correct the error in the XML file.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26087: The master end accessor {0} of composition assoc {1} has an invalid attribute kind: {2}.
Cause: The composition association's master end has attribute kind of RowSetIterator (cardinality -1 or > 1), i.e., it returns an iterator, rather than a row.
Action: Master end in an association must return a single row. Thus, the attribute kind must be Row (cardinality = 1).

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26100: An error occurred after commit was performed.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26101: An error occurred after posting was performed.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-26102: An error occurred after rollback was performed.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27001: Association attribute {2} included in {0} {1} is not updatable
Cause: This association attribute is marked readonly.
Action: Cannot modify the value of the association attribute as it is marked readonly.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27002: Entity validation with key {1} failed in entity object {0}
Cause: A custom validation rule failed to validate an attribute value.
Action: Fix the attribute value so that it passes the custom validation rule.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27003: Validation of rows in view object {0} failed
Cause: Modified or new entities in this view object failed to validate.
Action: Fix the failing entity values and revalidate the view object.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27004: Attribute set for {2} in entity {1} failed
Cause: Attempting to modify a read-only entity-attribute.
Action: Do not modify a read-only attribute value.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27005: Validation of rows in application module {0} failed
Cause: Modified or new entities within this application module or nested application module failed to validate.
Action: Fix the failing entities and then revalidate this application module.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27006: Validation failed because attribute {2} is not found in {0} {1}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27007: Validation of a view row in view object {0} failed
Cause: Attempting to validate a ViewRow failed.
Action: Fix the failing entities or attributes as found in the details of this exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27008: Attribute {2} in view object {1} cannot be set.
Cause: An attempt was made to modify a view row attribute that is read-only.
Action: Modify the updatable setting of the view attribute.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27009: Batch set of attributes in view object {1} failed
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27010: Attribute set with value {3} for {2} in {1} has invalid precision/scale
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27011: Attribute set with value {3} for {2} in {1} failed
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27012: Row validation method {2} failed for row with key {1} in {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27013: Attribute set validation method {4} failed for attribute {2} in {1}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27014: Attribute {2} in {1} is required.
Cause: The attribute value cannot be null as it has been marked mandatory.
Action: Provide non-null values for mandatory attributes.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27015: {0} contained entity/s still invalid
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

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27016: Invalid attribute kind for column {0}.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27017: The primary key for Entity {0} could not be determined.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27018: Attribute set with value {3} for {2} in {1} failed because of type mismatch
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27019: The get method for attribute "{2}" in {1} cannot be resolved.
Cause: An unexpected exception occurred in the getAttribute 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 subclasses 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27020: The set method for attribute "{2}" in {1} cannot be resolved.
Cause: An unexpected exception occurred in the setAttribute 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 subclasses 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27021: Failed to load custom data type value at index {0} with java object of type {1} due to {2}.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27022: Failed to load value at index {0} with java object of type {1} due to {2}.
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27023: Failed to validate all rows in a transaction.
Cause: An unexpected exception occurred during validating changes in a transaction.
Action: Verify the details for DeferredRowValidationException and fix those errors.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27024: Failed to validate a row with key {1} in {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27025: Failed to validate attribute {2} with value {3}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27026: Set method threw an exception found in the details of this exception.
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

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27027: Missing mandatory attributes for a row with key {1} of type {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27028: Variable {2} in manager {1} is not updatable.
Cause: An attempt was made to set the value of a variable that is not updatable.
Action: Change the updatable setting of the variable.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27029: Key definitions in definition {1} cannot be modified after it is resolved.
Cause: An attempt was made to modify the key definition after the definition is resolved (resolveDefObject()).
Action: It is illegal to modify key definitions after the definition is resolved. If key definitions are to be modified, it should be done before.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27030: An entity row without a primary key cannot be locked.
Cause: An attempt was made to lock an entity row with key which is not the primary key.
Action: For locking an entity row, only the primary key can be used (and not an alternate key). Do not use a non-primary key for locking.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27031: At least one of the following attributes {2} in {1} is required.
Cause: At least one of the list attributes must be not null.
Action: Provide a non-null value for one of these attributes.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27032: Session definition full name must start with {0}
Cause: The specified session definition full name is invalid.
Action: Session definition full name must start with the package name, 'sessiondef'. Make sure that the full name starts with it.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27033: Validator {0} cannot be designated transaction level because it does not implement JboTransValidatorInterface
Cause: An attempt was made to set a validator to transaction level validator, but the validator does not implement oracle.jbo.rules.JboTransValidatorInterface.
Action: Before setting the transaction level flag, make sure the validator class implements oracle.jbo.rules.JboTransValidatorInterface.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27034: Invalid kind for attribute {0} from the corresponding superclass attribute.
Cause: Attribute kind is different between an entity or view object and the corresponding superclass.
Action: Fix the attribute kind information in the xml-metadata definition for attributes in this entity or view object.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27035: Attribute {2} is required.
Cause: The attribute value cannot be null as it has been marked mandatory.
Action: Provide non-null values for mandatory attributes.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27036: At least one of the following attributes {2} is required.
Cause: At least one of the list attributes must be not null.
Action: Provide a non-null value for one of these attributes.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27037: Please provide a value that does not begin with a wildcard character for attribute {2}.
Cause: The attribute value may not begin with a wildcard character.
Action: Please provide a value that does not begin with a wildcard character.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27101: Attempt to access dead entity in {0}, key={1}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27102: Attempt to access dead view row of persistent id {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27120: SQL error during query execution. Statement: {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27121: SQL error during statement execution. Statement: {0}
Cause: Failed to execute a SQL statement.
Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27122: SQL error during statement preparation. Statement: {0}
Cause: Failed to prepare a JDBC PreparedStatement.
Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27123: SQL error during call statement preparation. Statement: {0}
Cause: Failed to prepare a JDBC CallableStatement.
Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27124: SQL error during empty statement creation
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27125: Cannot find matching type-map entries for all columns in a dynamic ViewObject-query
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27126: Long running query "{0}" has been canceled.
Cause: The view object's query timeout was reached or the user requested cancellation of a long query.
Action: Review the query implementation.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27127: The effective date operation for Entity {0} will introduce gaps or overlaps. key={1}
Cause: Effective date constraint violation while creating or updating a row. The operation will cause gaps or overlaps in the effective date timeline
Action: Change the start or end effective date if it is a new row. If it is an update choose a different mode.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27128: The effective date update operation for Entity {0} failed because an existing row has the effective start date that matches the effective date. key={1}
Cause: Effective date row update with UPDATE mode is disallowed because the start effective date of an existing row matches the effective date.
Action: Choose a different mode to update the row like correction mode.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27129: The effective date row for Entity {0} has end date less than start date, key={1}
Cause: Effective end date is greater than the start date.
Action: Change the start or end effective date.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27130: Current mode {0} is not supported in Multiple Changes Per Day.
Cause: Current mode is not supported in Multiple Changes Per Day.
Action: Switch to Update Change Insert mode.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27131: Current mode {0} is supported only in Multiple Changes Per Day.
Cause: Current mode is not supported in Multiple Changes Per Day.
Action: Switch to Update Change Insert mode.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27132: Current operation cannot be performed in {0} mode because no future rows exist. key={1}
Cause: Current operation cannot be performed when no future rows exist.
Action: Switch to Update mode.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27133: Current operation cannot be performed in {0} mode because no previous rows exist. key={1}
Cause: Current operation cannot be performed when no previous rows exist.
Action: Switch to a different mode or navigate to a row where previous rows exist.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27134: Current Multiple Changes Per Day operation can be performed only on first sequenced row. key={0}
Cause: Current Multiple Changes Per Day operation can be performed only on first sequenced row.
Action: Navigate to first sequenced row.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27200: JNDI failure. Unable to lookup {0} at context {1}
Cause: JNDI lookup failed. It can be caused by an incorrect data source name, particularly for the internal connection, or an internal error.
Action: Check the internal data source name to see if it is valid. If the error is not caused by the internal connection problem, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27201: Error suspending current transaction
Cause: An error occurred while suspending a global transaction for JTA pcoll manager.
Action: Check the detail exception to determine the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27202: Error resuming current transaction
Cause: An error occurred while resuming a global transaction for JTA pcoll manager.
Action: Check the detail exception to determine the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27203: Cannot use the default connection for persistence with global transactions.
Cause: While using global transactions, an attempt was made to use the transactional data source 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

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27500: The resource was not found.
Cause: The resource was not found
Action: Check the resource definition and the URL

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27501: The action was not found. Action name: "{0}"
Cause: The action was not found in the resource/resource collection
Action: Check the resource definition and the request content

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27502: Cannot generate content.
Cause: The content generation was not enabled in the request
Action: The request need to provide a Writer/OutputStream. For HTTP clients, the "Accept" header must be configured correctly

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27503: Invalid Resource Type.
Cause: The request is trying to execute an operation in resource collection that is only available for a specific resource. The cause also can be the opposite scenario.
Action: Check the resource path and the operation that was used in the request.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27504: The request content does not represent an action or it has an invalid structure.
Cause: The request content does not represent an action or it has an invalid structure.
Action: Check the request content.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27505: The request content doesn't match the specified resource
Cause: The request content doesn't match the specified resource.
Action: Check the request content and the resource path.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27506: The informed query string could not be processed.
Cause: The query string could not be proccessed. It may have wrong information or structure.
Action: Check the content/structure of the query string.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-27507: The user is not authorized to execute this operation
Cause: The user doesn't have access to the requested operation.
Action: Check the if the requested operation was granted to the user.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28000: PersistManager class {0} not found
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28001: Cannot connect to database
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28002: Could not create persistence control table {0}
Cause: An error occurred while creating the 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28003: Could not delete row in control table for table {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28004: Could not lock row in control table for table {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28005: Could not update row in control table for table {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28006: Could not create persistence table {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28007: Could not commit while working on persistence table {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28008: Could not create an index {0} on table {1} for persistent collection
Cause: An error occurred while attempting to create an index 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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28009: Error while getting current time from database
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28010: Error while getting next sequence value for {0} from database
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28011: Error while querying for the next id from column {1} of table {0}, collection id {2}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28012: Could not add key column {0} to table {1}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28013: Could not create key info table {0}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28020: Passivation error on collection {0}, collection id {1}, persistent id {2}
Cause: An unexpected error occurred while passivating objects into the persistent store. An exception might have been thrown during serialization.
Action: Look at the details of this exception for further information on the problem and how to address it.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28021: Activation error on collection {0}, collection id {1}, persistent id {2}
Cause: An unexpected error occurred while activating objects from the persistent store. An exception might have been thrown during deserialization.
Action: Look at the details of this exception for further information on the problem and how to address it.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28030: Could not insert row into table {0}, collection id {1}, persistent id {2}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28031: Could not update row into table {0}, collection id {1}, persistent id {2}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28032: Could not delete row from table {0}, collection id {1}, persistent id {2}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28033: Could not retrieve row from table {0}, collection id {1}, persistent id {2}
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28034: Retrieval by id not supported for collection {0}, collection id {1}. Call enableAccessById()
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28035: Persistent id {1} is invalid for a collection {0}, collection id {1}. It should be > 0
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.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28036: Object of id {2} is already active in its parent {3} in a persistent collection {0}, collection id {1}
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 Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28037: Object of id {2} not found in its parent {3} in a persistent collection {0}, collection id {1}
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 found in a node is missing.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28038: Could not delete all rows for collection of id {1} from table {0}
Cause: An unexpected error occurred while deleting all passivation rows from the persistent store table.
Action: Look at the details of this exception for further information on the problem and how to address it.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28039: Root node for collection {0} is invalid, collection id {1}, persistent id {2}
Cause: While attempting to activate an object of a given id, an internal integrity problem was found. In particular, the root node of the persistent collection is no good. It is either (1) <code>null</code>, (2) has younger or older sibling, or (3) has a parent node. None of these should apply to the root node.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28040: Could not retrieve ids of rows whose key id is {1} and hash is {2} from table {0}
Cause: An unexpected error occurred while retrieving an array of persistent ids of rows from the persistent store table of given key hash code at the given key index.
Action: Look at the details of this exception for further information on the problem and how to address it.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28041: Update found multiple rows or no matching row. Persistence table {0}, collection id {1}, persistent id {2}
Cause: The system tried to update a row in the persistence store table, but it found either no row or more than one matching row.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28100: The resource pool, {0}, failed to create a pooled resource instance.
Cause: Either the JDBC connection pool or the application pool were unable to create a new pooled JDBC connection or application module.
Action: If the exception details indicate that an exception occurred while creating a JDBC connection then check the JDBC connection description to ensure that it references a valid, live database instance. If the exception details indicate that an exception occurred while creating an application module then check the application module configuration to ensure that it references a valid, live application server and application application module class.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28101: An application attempted to set a pooled resource that might be in use as available.
Cause: The application attempted to mark a pooled resource which has already been available in the resource pool as available.
Action: Remove the application logic that invokes {@link oracle.jbo.pool.ResourcePool#setAvailable(Object)}, or move the application logic such that it occurs only once before the resource is made available.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28102: A request was timed out while waiting for a resource to be returned to the resource pool, {0}.
Cause: A client request timed out while waiting for a resource to be returned to the resource pool.
Action: Increase the maximum resource pool size in order to accommodate the maximum expected active request size. If the exception details indicate that the exception was thrown while waiting for an application module in the application pool then the maximum pool size can be increased with the property, jbo.ampool.maxpoolsize. If the exception details indicate that the exception was thrown while waiting for a JDBC connection in the JDBC connection pool then the maximum pool size can be increased with the property, jbo.maxpoolsize.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28103: A pool operation was specified for a pooled resource that does not belong to the resource pool.
Cause: A pool request was made for a resource that does not belong to the pool.
Action: Ensure that the pool request is accessing the same pool instance that was used to acquire the resource instance.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28200: Validation threshold limit reached. Invalid Entities still in cache
Cause: Invalid entities still found in the validation list of the transaction after attempting to validate all invalid entities for the VALIDATION_THRESHOLD 10 times (by default).
Action: Fix any logic that invalidates entity instances in the validation cycle (perhaps in overridden validateEntity() methods) such that all entities are valid before the VALIDATION_THRESHOLD limit is reached.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28201: Post threshold limit reached. Some entities yet to be posted.
Cause: There are invalid entities or entities in the post list of the transaction after trying to post all changes for the POST_THRESHOLD 10 times (by default).
Action: Fix any logic that places entities in the transaction's list of entities to be validated or posted in the post cycle, such that all entities get posted before the POST_THRESHOLD is reached.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28202: Entities invalidated in beforeCommit(). Need to revalidate and post.
Cause: Invalid entity instances found in the transaction in the beforeCommit phase.
Action: Fix any business logic that invalidates entity instances in postChanges() such that there are no more invalid entities after all changes are posted during the commit cycle.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28203: The updated row cannot be refreshed because its key values are unset or modified by database triggers.
Cause: The row could not be refreshed after update because the value of its primary or unique key was not set or unknown.
Action: Ensure values are set for at least one primary or unique key that can be used to fetch the row that is being updated. If that is not possible, use a custom SQLBuilder with doRefreshSQL() defined to refresh the row.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28204: Too many objects match the alternate key {0} for entity {1}, key {2}.
Cause: Attempting to add a new entity to the cache with alternate key that is same as an existing entity. This exception is thrown when uniquing a newly fetched/created entity with the cached set of entities.
Action: Fix the named alternative value of the row. Or, the alternate key definition might have to be augmented with additional attributes.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-28205: Validator {0} needs a row from iterator {1} to perform its validation, but did not find any row. Validation fails for row with key {2}.
Cause: A validator needs a row to perform validation, but the view object could not find any matching row.
Action: Since the necessary row is not found, the validation failed. Check to ensure that it is not an application error that cause no row to be found.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29000: Unexpected exception caught: {0}, msg={1}
Cause: If an unexpected exception occurs during a framework operation, this exception is thrown, with the unexpected exception included in the details of this exception.
Action: Fix the cause for the exception in the details for this JboException.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29001: Type mismatch. Expected {0}. Actual {0}
Cause: During creation of application module in the EJB deployment mode, the object returned by the EJB home is not an instance of oracle.jbo.common.remote.ejb.RemoteApplicationModule.
Action: This usually means that the wrong EJB home is being invoked to create a remote application module. Fix it to point to the correct home.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29004: Server-side configuration for creating the pool not specified.
Cause: A configuration was not specified for the remote ApplicationModule usage.
Action: Use the design time to specify a configuration for the remote ApplicationModule usage.

Level: 1

Type: ERROR

Impact: Configuration

JBO-29100: Attribute {0} is not selected
Cause: Def object is not selected. An attempt was made to access a nonselected def object.
Action: This particular operation is disallowed on a nonselected def object. Avoid this operation.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29101: Attribute {0} is not selected in {1}, operation: {2}
Cause: Def object is not selected. An attempt was made to access a nonselected def object in the specified container object.
Action: This particular operation is disallowed on a nonselected def object. Avoid this operation.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29102: The S_ROW_ID table is unable to generate a new row ID.
Cause: No more row IDs were available in the database's configured row ID range.
Action: Contact the system administrator. The row ID table in the database needs to be refreshed with a new row ID range.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29103: Internal error: {0} cannot be null
Cause: This is an internal exception. The specified argument cannot be NULL.
Action: Contact the System Administrator. The specified argument cannot be NULL.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29104: Unable to create RowId generator application Module. Add the RowIdAM application module in the AM Usage for the current application.
Cause: The RowIdAM application module is not a shared application module of the current application module.
Action: Add the RowIdAM application module in the AM Usage for the current application or contact the System Administrator.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29105: Attributes referenced in view criteria {0}.{1} with property AppliedIfJoinSatisfied do not map to the same entity usage.
Cause: The attributes used in the View Criteria do not map to the same entity usage.
Action: Make sure the attributes used in the View Criteria all map to the same entity usage if AppliedIfJoinSatisfied is set to true.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29106: Attributes referenced in view criteria {0}.{1} with property AppliedIfJoinSatisfied map to the primary entity usage.
Cause: The attributes used in the View Criteria cannot map to the primary entity usage.
Action: Make sure the attributes used in the View Criteria all map to a non-primary entity usage if AppliedIfJoinSatisfied is set to true.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29107: View criteria {0}.{1} with property AppliedIfJoinSatisfied must be used with an entity-based view object.
Cause: The view criteria cannot be used with a non-entity based view object
Action: The view criteria can only be used with an entity-based view object if AppliedIfJoinSatisfied is set to true.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29108: The value specified for the property {0} in the rowidam.properties file is invalid.
Cause: Invalid value specified in the rowidam.properties file. The values cannot be <= 0.
Action: Update the properties to specify accepted values. The property values should be > 0.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29109: The value specified for column {0} in the S_ROW_ID table is invalid.
Cause: One or more column values in S_ROW_ID table are invalid.
Action: Update the S_ROW_ID table with accepted values. The column values should be greater than zero.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29110: Unable to cast the class type specified for RowId comparison to GeneratorSequenceImpl or BigDecimal.
Cause: Invalid value specified for comparison.
Action: The value to be compared with the RowId should be of type BigDecimal or any other type that can converted to BigDecimal.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29111: View criteria {0} is a union VC and contains an invalid element of type {1} at index {2}
Cause: This view crieria is marked for union query but contains a view criteria element which is neither a ViewCriteria nor ViewCriteriaUsage.
Action: A union view criteria can only contain ViewCriteria or ViewCriteriaUsage. Correct the view criteria definition.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29112: The time zone ''{0}'' defined in adf-config.xml or TimeZone.getDefault().getID() does not exist in your Oracle database table V$TIMEZONE_NAMES. Please set an available time zone in your TZ environment variable or user.timezone Java system property.
Cause: The time zone could not be set as the value defined in adf-config.xml or TimeZone.getDefault().getID() does not exist in Oracle database table V$TIMEZONE_NAMES.
Action: Set an existing time zone defined in your Oracle database table V$TIMEZONE_NAMES in TZ environment variable or user.timezone Java system property.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29113: Encountered database recoverable exception. Please retry your request.
Cause: Encountered database recoverable exception.
Action: Retry your request after performing some recovery steps such asacquiring a new connection.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29114: ADF context is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is {1}
Cause: An error message cannot be constructed because ADF context is not setup on the thread.
Action: Use the error code and the stack trace to diagnose the root cause.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29115: Unable to get the error message due to error {1}. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is {2}
Cause: An error occured while constructing a display message for an underlying exception.
Action: Use the error code and the stack trace to diagnose the root cause.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29116: Data modification not allowed for readonly transaction.
Cause: An attempt was made to modify object in readonly transaction.
Action: Use view object in non read-only transaction for modification.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-29117: Transaction security access type {0} does not allow application module {1} security access type {2}.
Cause: An attempt was made to activate application module with different transaction security access type.
Action: Use transaction with same or no security access type.

Level: 1

Type: ERROR

Impact: Security

JBO-29118: Viewobject {0} cannot be created in application with readonly access.
Cause: An attempt to create view object in an application module with unsecured view object.
Action: Create updateable view object in application module that do not contain unsecured view object.

Level: 1

Type: ERROR

Impact: Security

JBO-29119: Unsecured viewobject {0} cannot be created in non readonly access application module.
Cause: An attempt to create unsecured view object in an application module with updateable view object.
Action: Create unsecured view object in application module that do not contain unpdateable view object.

Level: 1

Type: ERROR

Impact: Security

JBO-30000: Application module pool {0} has already been created.
Cause: The application attempted to create an application pool with the same name as an existing application pool.
Action: Correct the application logic that is creating an application pool. Validate that a pool with the given name has not already been registered with the pool manager.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30001: Cookie {0} is invalid.
Cause: Deprecated.
Action: N/A

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30002: The pool signature for the cookie is invalid.
Cause: Deprecated.
Action: N/A

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30003: Application pool {0} fails to check out an application module due to the following exception:
Cause: The pool failed to create an application module instance during checkout. Typically this exception occurs when the pool has been configured with an invalid application module name, EJB server, etc. or when an invalid JDBC username, password, URL, or datasource name has been specified.
Action: See the exception details for more information regarding the failure. Correct the application's configuration properties appropriately.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30004: An application module that was not checked out was checked into the pool, {0}
Cause: The application attempted to check in an application module that was not checked out from the pool.
Action: Remove redundant releaseApplicationModule() invocations from the application logic.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30005: A pool operation was specified for an application module instance that was not created by that pool.
Cause: The application attempted to invoke an application pool method with an application module that was not created by that application pool instance.
Action: Correct the application logic. Use the session cookie that was used to acquire the application module instance to acquire a reference to the application pool that created that application module instance.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30006: The cookie for session {0} and application {1} is not a valid handle for application pool, {2}. The cookie cannot be used to access this pool instance.
Cause: The application attempted to access the application pool with a session cookie that is not registered with that application pool.
Action: Correct the application logic. The application should not reference the application pool directly. Use the session cookie interface for all application pool interaction.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30009: A thread attempted to set as 'available' an application module that could already be in use. An application module's availability cannot be changed from outside of the pool once it has been made available.
Cause: The application attempted to modify the availability status of an application module that is already in active pool use.
Action: Remove the application logic that is updating the application module availability status.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30010: The cookie for session {0} and application {1} cannot be replicated with an active cookie instance.
Cause: The web server attempted to replicate a session cookie with an existing, active cookie.
Action: Internal exception. Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30011: A null session cookie application id, session id, or application pool reference ({0}, {1}, {2}) was specified during cookie construction. The cookie could not be constructed.
Cause: The application attempted to create a session cookie with an invalid set of cookie parameters.
Action: Correct the application logic that creates the session cookie. Verify that the cookie session id, application id, and application pool reference are all not null.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30012: A cookie for session {0} and application {1} has already been registered with application pool {2}. The cookie must be removed first.
Cause: The application attempted to create a session cookie in an application pool that already contains that session cookie.
Action: Correct the application logic that creates the session cookie. Remove the existing session cookie before creating a new one in that pool.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30013: The cookie environment for session {0} and application {1} cannot be reset after the cookie has become active.
Cause: The application attempted to change the session cookie environment after the session cookie became active.
Action: Correct the application logic that sets the session cookie environment. Move all logic that changes the session cookie such that it occurs before the session cookie becomes active. A session cookie is active after it is first used to acquire an application module.

Level: 1

Type: ERROR

Impact: Configuration

JBO-30014: The cookie for session {0} and application {1} cannot be removed from the application pool while it has an application module checked out.
Cause: Correct the application logic that sets the session cookie environment. Move all logic that changes the session cookie such that it occurs before the session cookie becomes active. A session cookie is active after it is first used to acquire an application module.
Action: Correct the application logic that removes the session cookie from the application pool. Be sure to invoke SessionCookie.releaseApplicationModule() before invoking ApplicationPool.removeCookie(SessionCookie).

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30015: The cookie for session {0} and application {1} cannot be serialized while in use.
Cause: The application attempted to serialize a session cookie while that cookie had an application module instance checked out or which the cookie was locked by a client request thread.
Action: Correct the serialization logic such that the session cookie is serialized after the session cookie application module has been released to the application pool and after all client requests have released their cookie locks.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30016: The request thread for session {0} and application {1} was timed out while waiting for an available application module in the pool, {2}.
Cause: The application request thread timed out while waiting for an available appliation module instance in the pool.
Action: Prevent wait timeouts by increasing the maximum pool size.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30017: The cookie for session {0} and application {1} cannot be reset while an ApplicationModule is reserved.
Cause: ApplicationModuleRef.resetState() was invoked while the ApplicationModuleRef was referencing a reserved ApplicationModule instance.
Action: Release the ApplicationModule with ApplicationModuleRef.releaseApplicationModule(true, boolean) before invoking resetState.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30018: The cookie configuration does not match the specified configuration. applicationId: {0}, sessionId: {1}, cookieConfig: {2}, specifiedConfig: {3}.
Cause: oracle.jbo.http.HttpContainer.findSessionCookie was invoked with a configName which was different than the configuration that was used to create the specified SessionCookie.
Action: Use a distinct applicationId to identify the cookie for each distinct Configuration.

Level: 1

Type: ERROR

Impact: Configuration

JBO-30019: An unavailable cookie state is detected while attempting to use a cookie from application {0}, session {1}.
Cause: An application pool method was invoked for a cookie that was not currently available. A cookie can be in an unavailable state if another thread is currently updating the cookie. For example, consider the following scenario: 1. cookie 1 releases an ApplicationModule with the managed state option 2. cookie 2 targets that ApplicationModule for recycling 3. Before cookie 2 has passivated the ApplicationModule state for cookie 1, cookie 1 requests another ApplicationModule In this instance the ApplicationPool could throw an unavailable exception. Note that most of the occurrences of this exception should be handled by the pooling framework.
Action: Report the exception to Oracle Support Services. Attempt the invalid operation again.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-30020: An invalid SessionCookie release mode was specified. applicationId: {0}, sessionId: {1}.
Cause: oracle.jbo.common.ampool.SessionCookie.releaseApplicationModule was invoked with an unsupported releaseMode.
Action: Invoke releaseApplicationModule(int) with a valid releaseMode attribute. Valid releaseModes include: SessionCookie.SHARED_MANAGED_RELEASE_MODE SessionCookie.SHARED_UNMANAGED_RELEASE_MODE SessionCookie.RESERVED_MANAGED_RELEASE_MODE SessionCookie.RESERVED_UNMANAGED_RELEASE_MODE

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33000: Configuration file {0} is not found.
Cause: The requested configuration file could not be found.
Action: Provide a correct name for the configuration file. Or, make sure that the named configuration file can be found in one of the accessible paths.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33001: Configuration file {0} is not found in the classpath.
Cause: The requested configuration file could not be found in the class paths.
Action: Make sure that the named configuration file can be located in one of the class paths.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33003: Connection name {0} is not defined.
Cause: The specified connection could not be found. Or an error occurred during processing of the specified connection.
Action: Make sure that the connection name is correct.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33004: Configuration file cannot be parsed.
Cause: An error occurred while parsing configuration file.
Action: Check to make sure that the configuration file is a valid XML file. See the detail exception for further information.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33005: Configuration {0} is not found.
Cause: The named configuration parameter was not found in the configuration.
Action: The system expects to find the named configuration parameter, but could not. Check the configuration content to make sure that it contains the named configuration parameter.

Level: 1

Type: ERROR

Impact: Configuration

JBO-33006: Data source {0} is not supported.
Cause: This error message indicates that the underlying SQLBuilder does not support datasource.
Action: For this SQLBuilder, do not use datasource.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33007: Data source {0} is not found.
Cause: The specified datasource could not be found.
Action: Make sure that the datasource name is correct. See the detail exception for further info.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33020: Current time is not available from SQL statement "{0}".
Cause: An error occurred while getting the current time from the database.
Action: If there is a detail exception, it will give further information about what went wrong. If no detail exception was provided, that means the SQL statement to get the current time returned no result (no row). Check the SQL statement for correctness.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33021: User {0} cannot be authenticated.
Cause: An error occurred while authenticating the user.
Action: Make sure that the user authentication information is correct.

Level: 1

Type: ERROR

Impact: Security

JBO-33022: Thread {0} has timed out while waiting to acquire a lock.
Cause: A thread timed out while waiting for a resource that was protected with an 'oracle.jbo.common.Lock'.
Action: Verify that all threads that have acquired a lock have properly released that lock in a 'finally' code block.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33023: Thread {0} is attempting to release a session cookie lock that it did not acquire.
Cause: The application attempted to release a {@link oracle.jbo.common.Lock} that it did not hold.
Action: Internal exception. Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33024: Graph nodes cannot be sorted due to a cycle in the graph.
Cause: A cycle was detected in the dependency graph.
Action: Check the edges in the graph and remove any cycles.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33025: Failed to release application module {0}. Cookie handle not found.
Cause: Failed to release application module due to missing cookie handle.
Action: Invoke the correct, counterpart releaseAM method.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33026: Value must be between {MinVal} and {MaxVal}
Cause: Input values failed the range validator test.
Action: Provide values that are within the range validator paramters.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33027: Value must be greater than {MinVal}
Cause: Input values failed the minimum validator test.
Action: Provide values that are greater than the minimum.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33028: Value must be less than {MaxVal}
Cause: Input values failed the maximum validator test.
Action: Provide values that are less than the maximum.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33029: Value must have exactly {MinLength} characters
Cause: Input values must be longer than minimum length.
Action: Provide values that are longer than the minimum length.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33030: Value can have at most {MaxLength} characters
Cause: Input values exceeded maximum length length.
Action: Provide values that are less than or equal to maximum length.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33031: Value must have at least {MinLength} and at most {MaxLength} characters
Cause: Value must have at least (minLen) and at most (maxLen) characters.
Action: Provide values that are between minimum and maximum length.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-33032: Value must have exactly {MaxLength} characters
Cause: alue must be exactly (maxLen) characters.
Action: Provide values that is exactly the maximum length.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34000: Definition class name missing in XML file of type {0}
Cause: Name of the definition Java class missing in the JClient XML file.
Action: Every metaobject in JClient must have name of the definition object's Java class in the XML file. Correct the error by regenerating XML file in the design time.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34001: Iterator binding {0} is not of the expected class {1}
Cause: The iterator binding is of the wrong Java class. Some controls expect to work with a JUIterRowBinding, while others with JUIterRangeBinding. This error indicates that the supplied iterator binding is not of the expected class.
Action: If the error is caused by some client code that supplies an iterator binding, correct the code to supply an iterator binding of the correct class. If the error is caused by framework code, contact Oracle Support Services with the stack trace.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34002: The application obj has already been set for form binding {0}. Cannot do it again
Cause: The form binding has already been registered with an application (JUApplication) object. It is illegal to try to set the form binding's application object again.
Action: This error typically means a program error. Contact Oracle Support Services with the stack trace.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34003: No iterators bound with the given name :{0}
Cause: No iterator binding found with the given name.
Action: Fix the iterator binding name before attempting to change the iterator associated with it.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34004: No matching row found for entered or selected item in the LOV iterator for a list-binding.
Cause: No matching row found for a selected value in a List binding.
Action: Enter/Select a valid item from the list so that the matching row in the LOV iterator can be found.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34005: Exceptions occurred in synchronizing updates from this application. Click Details to see the complete list.
Cause: Exceptions occurred in synchronizing data from the client Application into the Business Components tier.
Action: Fix the exceptions displayed in the details list and then reapply the changes.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34006: Method that creates the iterator for this object returns null.
Cause: Collection to which this iterator is bound returns null.
Action: Fix the return value so that a valid collection is available for this iterator to bind to.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34007: A value is not passed for mandatory parameter {0}.
Cause: Mandatory Parameter was not set by the calling code either programmatically or by overriding it in a nested container usecase.
Action: Set the mandatory parameter value

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34008: Final parameter {0} cannot be modified.
Cause: Mandatory Parameter was not set by the calling code either programmatically or by overriding it in a nested container usecase.
Action: Set the mandatory parameter value

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34009: ListBinding definition :{0} not found.
Cause: Server side ListBinding could not be found with the given usage name.
Action: Fix the server side ListBinding usage name in List binding metadata

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34010: The "{0}" descriptor appears in the application classpath more than once: - {1} - {2}
Cause: The cpx classpath name has already been found at a different source in the classpath. It is illegal to have the same relative cpx name in the classpath more than once.
Action: Refactor one of the indicated URLs in the message so it appears under a different relative package in the classpath.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34011: Validator expression {0} did not result in a valid object for bindingContainer:{1}
Cause: Expression for custom validator does not resolve into a valid object that as a public method of name validateBindingContainer and that takes the bindingContainer as the only parameter.
Action: Provide a different expression or fix the expression so that an object whose class has a method with following signature: public validateBindingContainer(DCBindingContainer ctr)

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34012: Attempting to register a Swing binding factory when Faces version is already installed.
Cause: Faces binding factory is already installed for ADF Model bindings. Attempt to install a Swing version will break the application due to binding class incompatibilities.
Action: Remove or replace references to juimodel in namespace attributes, in pagedef xml files in the application with: http://xmlns.oracle.com/adfm/uimodel.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34013: Enter a nonempty string and a string not equal to '%' in the list:{0} to filter the list of values.
Cause: Empty string or % was entered to filter list datsource for a list binding.
Action: Enter any other string to filter by in the list component bound to this list binding.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-34014: No matching child node found for row with key:{0} under parent node:{1}
Cause: No matching node in the current range of rows found for a row retrieved from the backend collection.
Action: Scroll the backend collection to the appropriate range where a node for this row will be found. If row keys are for rows outside of current range of rows in the RowIterator, use alternate client apis to access the row data avoiding calls into this node binding.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-36000: An unexpected expression token is found.
Cause: Unexpected token found.
Action: Found an unexpected expression token. Make sure that the words are spelled correctly and that the expression makes sense.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-36001: Mismatching parentheses are found.
Cause: Mismatching parentheses.
Action: Examine the expression and ensure that open parentheses match up with closing parentheses.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-36002: The method call specification is invalid. "," or ")" is expected.
Cause: Invalid method call. After a method parameter, ',' or ')' is expected, but neither was found.
Action: Examine the expression and correct method invocation.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-36003: An expression token is not found.
Cause: Expecting a token. The expression string was terminated unexpectedly.
Action: Examine the expression and ensure that the expression does not end unexpectedly.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-36004: Mismatching square brackets are found. An invalid array index is specified.
Cause: Mismatching square brackets.
Action: Examine the expression and ensure that open square brackets (for array index) match up with closing brackets.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-36005: Variable {0} is not found.
Cause: Variable not found.
Action: Examine the expression and ensure that the variable name is correct.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-36006: cannot convert {0} into {1}
Cause: Cannot convert data.
Action: Cannot convert data from one class to another. Examine the expression and ensure that the data assignment does not cause incompatible conversion of data.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-36007: Binary operation {0} is invalid for strings.
Cause: An attempt was made to invoke an invalid binary operation on two strings.
Action: Examine the operation ID and correct the expression so that the invalid binary operation is not attempted on strings. The expression runtime only recognizes addition as a valid binary operation between two strings.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-36008: The AND separator for a BETWEEN operator cannot be found. Token {0} is found instead.
Cause: A BETWEEN operator was found but no AND for the two comparison expressions.
Action: Take a look at the expression string. The correct syntax for BETWEEN is 'testVal BETWEEN value1 AND value2'. The expression parser could not find the AND keyword. Correct the expression.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-55001: A value of type {1} cannot be set to a value of type {0}.
Cause: Unexpected type was provided to Variant utility.
Action: Provide an expected type as reported in the exception.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-55002: Variant type {0} is invalid.
Cause: The data-type passed to the Variant utility from a Validation rule is invalid. This could be due to a corrupt XML-metadata definition in the component's XML file.
Action: Fix the component XML for the offending validation rule.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-55003: Variant name {0} is invalid.
Cause: The name of the variant type passed to the Variant utility from a Validation rule is invalid. This could be due to a corrupt XML meta data definition in the component's XML file.
Action: Fix the component XML for the offending validation rule.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56001: Row value is missing for data object {0}.
Cause: The Row Value for a SDOValueStore is null.
Action: Should not use SDOValueStore with a NULL row value.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56002: Operation {0} on object {1} is not supported.
Cause: An attempt was made to invoke an invalid service operation.
Action: Ensure that this service operation is defined at design time.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56003: Nonpersistent attribute {0} cannot be used in a database mode view criteria.
Cause: A nonpersistent attribute is used for DB ViewCriteriaItem.
Action: Make sure the attribute is persistent.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56004: Non-ViewLink accessor attribute {0} cannot be used for a view criteria item that has nested view criteria.
Cause: A non-ViewLink accessor is used for DB ViewCriteriaItem that has nested ViewCriteria.
Action: Make sure the attribute is a ViewLink accessor.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56005: SDO type is not found for ViewObject {0} with namespace {1} and name {2}.
Cause: SDO Type is not found for a ViewObject.
Action: Make sure the viewobject is SDO enabled.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56006: ComplexType or DataType SDO property {0} has conflict values {1} vs. {2} for attribute {3}.
Cause: Conflict input values for ComplexType non-value properties.
Action: Make sure the payload has the same values for the same ComplexType non-value properties.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56007: ViewObject not found for sdo dataobject {0} from base viewobject {1}.
Cause: Can't find corresponding ViewObject for one SDO Type.
Action: Make sure passing valid SDODataObject that maps to valid ViewObject.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56008: Mapped value for name {0} not found in viewobject {1} attribute {2}.
Cause: Can't find mapped value for one given name.
Action: Add neccessary name/value to PropertySet.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56009: Mapped name for value {0} not found in viewobject {1} attribute {2}.
Cause: Can't find mapped value for one given value.
Action: Add neccessary name/value to PropertySet.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56010: Comparision Operation {0} is invalid for ViewCriteriaItem of attribute {1}.
Cause: The attempted operation is invalid for a ViewCriteriaItem.
Action: Change the input value of this operation.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56101: Nonpersistent attribute {0} cannot be sorted upon.
Cause: A nonpersistent attribute is used for DB SortCriteria.
Action: Make sure the attribute is persistent.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56102: Dependencies specified for view attribute {0} conflict with dependencies specified on the underlying entity attribute.
Cause: View attribute dependencies conflict with the entity attribute dependencies.
Action: Ensure that the dependencies are not specified on both the view and entity attribute.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56103: View object {0} is not prepared.
Cause: This is the exception that gets thrown by ViewObjectImpl when attempting an operation on a declarative view object on which prepareVOForQuery has not been called, such as findByAltKey (bug 7455860) or createAndInitRow (bug 7504211).
Action: Call ViewObjectImpl.prepareVOForQuery before calling findByAltKey or createAndInitRow for the first time.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-56104: Entity {0} cannot be set to batch mode because it has streaming attribute types (e.g., Blob, Clob).
Cause: An attempt was made to set batch mode on an entity that has streaming attribute types (e.g., Blob, Clob).
Action: Remove BatchThreshold value from this entity's metadata.

Level: 1

Type: ERROR

Impact: Programmatic

JBO-80000: Connection is already open.
Cause: An open operation was attempted on a URL connection that is already open and in a active state.
Action: Ensure that a close operation has been called before invoking the open operation on the connection.

Level: 1

Type: ERROR

Impact: Other

JBO-80001: Connection is not open.
Cause: An interaction with the URL was attempted without opening the connection.
Action: Ensure that the connection has been opened and is active before starting an interaction with the URL.

Level: 1

Type: ERROR

Impact: Other

JBO-80002: Connection description cannot be created.
Cause: There was an internal error creating the metadata fragment for the URLConnection.
Action: Verify if the details necessary to create a new URL connection are provided.

Level: 1

Type: ERROR

Impact: Other

JBO-80003: Operation is invalid. Connection is already released to the pool.
Cause: An operation was attempted on a connection that had already been released to the pool.
Action: Obtain a new active reference to the connection from the connections context.

Level: 1

Type: ERROR

Impact: Other

JBO-80004: Authentication provider "{0}" cannot be initialized.
Cause: Either the metadata describing the authentication provider was corrupted or the class registered in the metadata for the authentication could not be loaded.
Action: Ensure that the class is available in the class path of the application. Contact Oracle Support Services if the corrupt metadata cannot be recovered.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

JBO-80005: The connection cannot be created. Connection metadata is invalid.
Cause: The connection metadata in the repository has been corrupted possibly due to an external edit.
Action: Contact Oracle Support Services to recover the corrupted metadata.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

JBO-80006: The connection instance cannot be created. Resource endpoint is not provided.
Cause: A URLConnection could not be created as the URI / URL to the resource endpoint was not supplied.
Action: Provide a valid URL / URI to create the connection.

Level: 1

Type: ERROR

Impact: Other

JBO-80007: The connection fails to open. Resource endpoint "{0}" does not exist.
Cause: The URL resource could not be accessed after the connection was created. If the connection describes an HTTP URL resource outside a firewall, the proxy settings might not have been correctly configured to access the URL.
Action: Ensure that the URL is active and can be accessed. If the connection describes an HTTP URL outside a firewall, verify that the correct proxy settings are configured.

Level: 1

Type: ERROR

Impact: Other

JBO-80008: Proxy is not supported for file connection protocol.
Cause: An attempt was made to configure proxy information for a file connection protocol.
Action: Proxy configuration is not supported for a file connection protocol. Remove any proxy configuration done for this connection.

Level: 1

Type: ERROR

Impact: Other