Action: Change the view definition to include all necessary alternate key attributes. 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. This executes a SQL statement like select a. 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. 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. 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.
This error normally carries a detail exception from database which will give further information about the database failure. This is not supported. 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.
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. Action: Check the detail IO exception and make necessary correction.
Action: Examine the XML file and make sure that the element tag is one of the recognized ones. Action: Check to see if the XML document has gone through a proper migration process. If not, migrate the application.
Action: When running with MDS, make sure that the metadata store supports the delete operation. Check the detail exception. 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. Action: Review your code that builds the view def. Make sure that entity references do not have a recursion in it.
For a view link usage entry, both a source and destination should be defined. Action: Modify the class that is using the pool to check the pool size before adding a new connection to the pool. 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.
Action: Increase the maximum pool size in order to accommodate 2x the maximum expected active request size. There might be a datatype mismatch between the attributes of the view object and columns in the SQL for it. Action: This exception carries the most up to date def object.
Resolve the differences and retry write. Action: An existing definition object's MDS key should not be null. Contact Oracle Support Services. Action: Retry creating the document. Action: Resolve this metadata merge conflict. Struct attributes. 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.
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: Master end in an association must return a single row. Action: Do not try to edit this property. Instead, consider deleting and creating the def object.
However, either the major version number or the minor version number do match between the original def object and the def object found on the tip of the MDS repository. This means another user has modified and saved the def object between the time when this client loaded the original def object.
Action: Reload the def object to refresh to the tip and request edit. Action: Another user may have removed the document. Refresh def object cache. This means that another user made structural changes to the def object and it may not be refreshed with the latest def object.
Action: The def object cache should be refreshed to the tip of the repos. 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. Action: Cannot modify the value of the association attribute as it is marked readonly. Action: Fix the attribute value so that it passes the custom validation rule. Action: Fix the failing entity values and revalidate the view object. Action: Do not modify a readonly attribute value.
Action: Fix the failing entities and then re-validate this application module. 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. Action: Fix the failing entities or attributes as found in the details of this exception.
Action: Modify the updatable setting of the view attribute. Not available in 3. 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. Action: Fix the attribute value so that it validates against the failing rule. Action: Fix the cause for failure in the custom validation method for this attribute.
Action: Fix the cause for failure in the custom validator method for this attribute. Action: Provide non-null values for mandatory attributes. This occurs only in the case when there is a composition association between the master and detail entities. Action: Fix the attribute kind information in the xml-metadata definition for attributes in this view object.
Action: Set at least one attribute as the primary key for this entity type, so that entities of this type can be uniquely identified. Action: Convert the argument to a proper Java type, such that it is an instance of the Java type that this attribute expects. This exception could also be thrown if the getter is not a public Java method.
Action: Do not throw any exception other than sub-classes of JboException from any business logic code in the getter method for an attribute. Also verify that the getter method is a public Java method. This exception could also be thrown if the setter is not a public Java method. Action: Do not throw any exception other than sub-classes of JboException from any business logic code in the setter method for an attribute.
Also verify that the setter method is a public Java method. There could be conversion errors between the return type from JDBC for the attribute and its Java type. Fix any conversion errors or domain exceptions that are in the details of this exception. The details can also contain DeferredAttrValidationExceptions which needs to be fixed as well.
Action: Verify the details for JboExceptions and fix those errors at the row level. This exception should not be seen outside of the framework. Action: Verify the details for JboExceptions and fix those attributes with null values.
Action: Change the updatable setting of the variable. 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. 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. Action: Provide a non-null value for one of these attributes. Action: Session definition full name must start with one of the sessiondef packages.
Action: Before setting the transaction level flag, make sure the validator class implements oracle. Action: Fix the attribute kind information in the xml-metadata definition for attributes in this entity or view object. Action: Please provide a value that does not begin with a wildcard character. Action: Site definition full name must start with one of the sitedef packages. 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. This could happen if a reference to the ViewRow is held by some business logic while the containing view object was removed. Action: Either provide a typemap that maps the selected columns in the query or leave out the erring column-type from the query.
Action: Review the query implementation. 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. Action: Choose a different mode to update the row like correction mode. Action: Change the start or end effective date. Action: Switch to Update mode. Action: Switch to a different mode or navigate to a row where previous rows exist.
Action: Navigate to the first sequenced row. 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.
It may have wrong information or structure. Action: Check the resource definition and the request content. The cause also can be the opposite scenario. Action: Check the resource path and the operation that was used in the request. Action: Check the request content. Action: Check the request content and the resource path. Action: Check the http method, the URL and the verb that are being used.
Action: Check the detail exception to determine the root cause of the problem. Action: Explicitly specify the jdbc url that should be used for creating the internal connection by setting the oracle. However, the class specified could not be located or loaded. Action: Make sure that the name specified for jbo. The class name should be fully qualified with the package name. A special keyword None represents no persistent collection manager, i. Action: Make sure that the database connection URL is correct.
The detail to this exception will give further information on the problem. Action: Check to make sure that the connection has appropriate authority to create a table. Action: Look at the details of this exception for further information on the problem and how to address it.
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.
For the Oracle persistent manager, the SQL statement used for this would be 'select sysdate from dual'. 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.
An exception might have been thrown during serialization. An exception might have been thrown during deserialization. Action: Enable by-id access by calling PCollection. The id must be greater than 0. Action: Give a valid id. In particular, a node which was thought to be passivated was found to be active. In particular, the root node of the persistent collection is no good. It is either 1 null , 2 has younger or older sibling, or 3 has a parent node.
None of these should apply to the root node. 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 it is under 50MB, change it, restart your database, and try your connection again. You may not have compiled your classes Compile your business component classes and try again.
Cause: When business components are running inside JServer, only one root application module may be created. This is because JServer already provides one transaction context. Action: It is illegal to attempt to create multiple root transactions when running inside JServer. 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. 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. Cause: While traversing the parenthood chain for application modules, a child application module was found with no container parent application module. Action: If this application has added custom business component classes, it may be that the application code is attempting to access a child application module before it is fully initialized.
If this is not the case, this error probably represents some internal error in Business Components for Java framework, in which case contact Business Components for Java Technical Support. Cause: A business component is found without a container parent application module. Action: If this application has added custom business component classes, it may be that the application code is attempting to access a business component before it is fully initialized.
Cause: Attempting to load metadata objects failed. It may have unexpected data or the XML data may be corrupt. Action: 1. Make sure that the file is present. If the file system support case insensitive file names e. For a. Check the JPX file to make sure that the valid tag is in there. This error is reported if the base XML file is not found.
When loading the XML file for a package JboPackage tag , this error is reported if some unexpected error occurs while loading a containee. In all of the above cases, a more descriptive message may be printed on Diagnostic.
If you are not seeing Diagnostic messages, you can run your application with Diagnostic turned on, as in "java -Djbo. Cause: Some XML parsing exception oracle. XMLParseException was thrown. If you are not seeing diagnostic messages, you can run your application with diagnostic turned on, as in "java -Djbo.
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.
Cause: An attempt was made to set the base definition of another definition object, e. However, A already extends B. Setting a recursive circular subclassing relationship among definition objects is illegal. Action: Review your subclassing hierarchy of your definition objects and correct errors. Action: Check the content of the XML file for the view definition.
Make sure that the value for that element is valid. Make sure that the value for the element is a positive integer. Cause: The maximum fetch size specified in the view definition XML file is not valid. Cause: A problem is found in resolving a view link definition or an association. In case of a view link, this error may be caused by the fact that the source or destination view object cannot found. Or, if the view link ends have attribute names, this error may indicate that the named attributes cannot be found.
Similarly, for an association, this error indicates that either source or destination entity object or attributes involved in the association cannot be found. Cause: This error occurs if the application uses meta object serialization files. It indicates that after the. 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. Cause: Attribute definition found in XML file is invalid.
It is missing SQLType value. Cause: The view link definition in the XML file is missing either the source or destination view link end. Action: Normally, the meta object name is a dot-separated name of the meta object. For an entity object named Emp in package1. 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. Cause: You cannot set customer query calling setQuery on a view object if it is the detail view object in a master detail view link.
Cause: An entity association definition in an XML file is invalid. In particular, this error means that either of the two association ends "AssociationEnd" elements in the XML file are missing "Attributes", which lists source or destination attributes. Cause: An attempt was made to post a row with no attribute set. Action: Set some attributes on the row before attempting to insert it into the database. 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. 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.
A possible cause for this is that the DTD file is missing oracle. Cause: Custom class could not be found and loaded. The custom class may be for a component e. 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.
Action: Either change the Updateable flag for the View Attribute or do not attempt to update readonly attributes. Cause: Attempting to validate entities and attributes failed during validation of buffered attributes in Deferred Validation mode.
Not available in 3. 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. 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.
Cause: The custom method validator attached to an entity returned false , indicating a failure in the validation for that entity. Cause: The custom method validator attached to an attribute returned false indicating a failure in validation for that attribute in the custom method. 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. Action: Fix the attribute kind information in the xml-metadata definition for attributes in this view object.
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.
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.
Cause: An unexpected exception occurred in set Attribute method. This exception could also be thrown if the getter is not a public Java method. Action: Do not throw any exception other than sub-classes of JboException from any business logic code in the getter method for an attribute.
Also verify that the getter method is a public Java method. This exception could also be thrown if the setter is not a public Java method. Action: Do not throw any exception other than sub-classes of JboException from any business logic code in the setter method for an attribute. Also verify that the setter method is a public Java method. 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. Fix any conversion errors or domain exceptions that are in the details of this exception. The details can also contain DeferredAttrValidationExceptions which needs to be fixed as well. Cause: An unexpected exception occurred during a setter method for an attribute. This exception should not be seen outside of the framework.
Cause: An unexpected exception occurred during validating attributes of a row for mandatory fields. 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.
This could happen if a reference to the ViewRow is held by some business logic while the containing view object was removed. Cause: Failed to execute a 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. Cause: When using global transactions you cannot use the transactional datasoource for acquiring the internal connection. Action: Explicitly specify the jdbc url that should be used for creating the internal connection by setting the oracle.
Cause: The client specified a custom persistent collection through the jbo. However, the class specified could not be located or loaded. Action: Make sure that the name specified for jbo. The class name should be fully qualified with the package name. A special keyword None represents no persistent collection manager, i. 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. Cause: An error occurred while creating "persistent collection control table. Action: Check to make sure that the connection has appropriate authority to create a table. 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. Cause: An error occurred while trying to lock the persistent collection control row. This error is thrown in two situations:. 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.
Cause: An unexpected error occurred while attempting to update the persistent collection control row. Cause: An error occurred while attempting to create a database table to store persistent collection material. Cause: An unexpected error occurred while attempting to commit persistent collection changes. Cause: An error occurred while attempting to create an index on a database table that stores persistent collection material.
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: 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. Cause: An error occurred while attempting to query for the next id from a pers coll table.
Cause: An error occurred while attempting to create add a key column on a database table that stores persistent collection material. Cause: An error occurred while attempting to create a database table to store key info for persistent collection material. Cause: An unexpected error occurred while passivating objects into the persistent store. An exception may have been thrown during serialization. Cause: An unexpected error occurred while activating objects from the persistent store. An exception may have been thrown during deserialization.
Cause: An unexpected error occurred while inserting a passivation row into the persistent store table. Cause: An unexpected error occurred while updating a passivation row in the persistent store table. Cause: An unexpected error occurred while deleting a passivation row from the persistent store table. Cause: An unexpected error occurred while retrieving a passivation row from the persistent store table. 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.
Cause: The client attempted to retrieve a row by an id, but the id value is invalid. The id must be greater than 0. 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. Cause: An unexpected error occurred while deleting all passivation rows from the persistent store table. In particular, the root node of the persistent collection is no good.
It is either 1 null , 2 has younger or older sibling, or 3 has a parent node. None of these should apply to the root node. 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. 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: 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.
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 ResourcePool. Cause: A client request was timed out while waiting for a resource to be returned to the resource pool. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more.
Asked 10 years ago. Active 10 years ago. Viewed 2k times.
0コメント