Skip Headers
Oracle® Application Server TopLink Mapping Workbench User's Guide
10g Release 2 (10.1.2)
Part No. B15900-01
  Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

Error Messages

The following errors messages (listed in alphabetical order) may appear in the status bar of the OracleAS TopLink Mapping Workbench and OracleAS TopLink Sessions Editor. Each message includes a description of the action that caused the error and the recommended resolution. Use the Project Status report (see "Generating the Project Status Report" on page 2-4) to display all error messages in a project.

1-1 mappings for EJB 2.0 CMP descriptors must use ValueHolder indirection.
Cause: You created a mapping without indirection.
Action: When creating a one-to-one mapping for EJB descriptors in projects with 2.0 CMP persistence, you must select the ValueHolder indirection option on the mapping's General tab.
1-M and M-M mappings for EJB 2.0 CMP descriptors must use transparent indirection.
Cause: You created a mapping without indirection.
Action: When creating a one-to-many or a many-to-many mapping for projects with 2.0 CMP persistence, you must select the Transparent indirection option on the mapping's General tab.
A field/method pair is incomplete in the [mapping name] mapping.
Cause: You created a transformation mapping, but did not specify a complete field/pair method
Action: Complete the Object > Field Method for each database field on the mapping's General tab.
A key pair has not been completely specified for a reference.
Cause: You created a table reference without a key pair.
Action: You must specify a foreign key reference for the database table. Use the database table's Reference tab to add a key pair.
A locking policy is specified, but the lock field is not specified.
Cause: You selected a locking policy, but did not specify a field for optimistic locking.
Action: Specify the locking Field on the Locking tab.
Aggregate fields are not specified.
Cause: You created an aggregate mapping without specifying specific fields.
Action: For aggregate mappings, each Field Description on the Fields tab must contain a unique Field.
Aggregate mapping fields must be unique.
Cause: You created an aggregate mapping without specifying unique fields.
Action: For aggregate mappings, each Field Description on the Fields tab must contain a unique Field.
An aggregate shared by multiple source descriptors cannot have one-to-many or many-to-many mappings.
Cause: You attempted to create multiple one-to-many and many-to-many, or one-to-one mappings in which the target is the aggregate.
Action: Aggregate descriptors that are shared by multiple source descriptors cannot have mappings that contain a target object that references the descriptor.
An ejb-jar.xml file needs to be specified.
Cause: For a 2.0 CMP persistence project, you must specify an ejb-jar.xml file.
Action: Specify the location of the ejb-jar.xml file on the project's General Properties tab.
Attribute is typed as a ValueHolderInterface, but the mapping does not use Value Holder Indirection.
Cause: You did not specify indirection or transparent indirection for the mapping.
Action: If the class attribute is of type ValueHolderInterface, you must use value holder indirection for the mapping.
Attribute is typed as a ValueHolderInterface, but the mapping does not use Indirection.
Cause: For one-to-one and transformation mappings, you did not use indirection.
Action: If the class attribute is of type ValueHolderInterface, you must use indirection for the mapping.
Cannot Use Joining because the source and target (reference) descriptors are the same type.
Cause: You selected the Use Joining option on a one-to-one mapping in which the source and reference descriptors are the same.
Action: Either unselect the Use Joining option or select a difference Reference Descriptor on the One-to-One Mapping General tab.
Classes cannot reference an aggregate target with one-to-one, one-to-many, or many-to-many mappings.
Cause: You tried to select an aggregate descriptor as a reference.
Action: You cannot select an aggregate descriptor as the Reference Descriptor for a one-to-one, one-to-many, or many-to-many mapping.
EJB Class information is not compatible with project persistence type.
Cause: You entered EJB incorrect EJB information.
Action: Ensure that the information you entered on the EJB descriptor's EJB Info tab is incorrect, based on the project's persistence type (as specified on the project's General Properties tab).
If the mapping uses indirection, then the attribute must be a ValueHolderInterface.
Cause: Persistent classes that use indirection must replace the relationship attributes with a value holder (an instance of a class that implements the ValueHolderInterface, such as ValueHolder).
Action: On the attribute's General mapping tab, select the Use Indirection option and specify ValueHolder type.
[descriptor name] is not an implementor of the [descriptor name] interface, so it cannot have an indicator value.
Cause: You included a descriptor on the Variable One-to-One Class Indicator Info tab that is an implementor.
Action: Unselect the descriptor on the Variable One-to-One Class Indicator Info tab or add the descriptor to the Implementor tab.
Mapping references write lock field, but is not read-only.
Cause: You specified a locking policy for a descriptor, but one of the attribute mappings is not read-only.
Action: Select the Read Only option on the mapping's General tab.
Mapping uses Indirection, but its associated attribute is not a ValueHolderInterface.
Cause: You attempted to use Indirection for a one-to-one mapping.
Action: If you select the Use Indirection option for a one-to-one mapping with transparent indirection, the associated class attribute must be ValueHolderInterface.
Mapping uses Value Holder Indirection but its associated attribute is not a ValueHolderInterface.
Cause: You selected indirection without a ValueHolderInterface.
Action: If you select the Use Indirection (ValueHolder) option for a one-to-many, many-to-many, or direct collection mapping, the associated class attribute must be ValueHolderInterface.
Mappings for EJB 2.0 CMP descriptors that use Value Holder Indirection must not use method accessing.
Cause: You cannot use method accessing on mappings for EJB 2.0 CMP descriptors that use ValueHolder Indirection.
Action: Because EJB attributes are code-generated, reference mappings should not be set to use method access. The attributes are code-generated to be of type ValueHolder but the abstract methods are defined to return the local interface type of the related bean.
Method accessors have not been selected.
Cause: You selected to Use Method Accessing for a mapping but did not select a method.
Action: You must select a Get and Set method on the mapping's General tab.
More than one writable many-to-many mapping cannot use the same relation table.
Cause: A project cannot have more than one writable many-to-many mapping using the same relation table.
Action: You must either make sure only one of the mappings is writable or choose a different table for each many-to-many mapping.
Multi-table reference should be defined from the base table [table name] to the derived table.
Cause: This descriptor has Inheritance and Multi-Table advanced properties defined on it.
Action: The multi-table relationship that is defined between the base class's table and this derived class's table must be defined from base to derived.
NCharacter, NString, and NClob database types are currently only supported on the Oracle9 platform.
Cause: You attempted to map a database type that is not supported by your database.
Action: The database type for a type conversion mapping or direct-to-field mapping can be NCharacter, NString, or NCLOB only if you are using an Oracle9 database.
No attribute is associated with the mapping named [mapping name].
Cause: The specified mapping does not have an associated class attribute.
Action: Either refresh the class or remove the mapping.
No calss indicator value should be defined for the abstract class [class name].
Cause:
Action:
No class in inheritance tree is marked as root.
Cause: The inheritance hierarchy must contain one root descriptor.
Action: Select the Is Root Descriptor option on the Inheritance tab.
No class indicator field is selected for this root class.
Cause: You selected the Use Class Indicator Dictionary option for the root descriptor in the inheritance hierarchy, but did not specify an indicator value for the root and its children.
Action: Use the Indicator Type drop-down list on the Inheritance tab for the root class.
No class indicator field should be defined for the abstract class [class].
Cause: Abstract classes should not be included or contain an Indicator Value on a descriptor's Inheritance tab.
Action: Either remove the Include option for the class on the Inheritance tab, or remove the abstract modifier option on the descriptor's Class Info – Class tab.
No collection type is selected.
Cause: For collection mappings, you must select a collection type.
Action: Select a collection type on the mapping's Collection tab.
No database field is selected.
Cause: You created a direct-to-field or type conversion mapping without selecting a database field.
Action: For attributes with direct-to-field mappings, you must specify a Database Field on the mapping's General tab. For attributes with type conversion mappings, you must specify a Database Field on the mapping's General tab.
No database type is selected.
Cause: For type conversion and object type mappings, you must select a database type.
Action: Select a Database Type on the mapping's General properties tab.
No direct field is specified.
Cause: For direct collection mappings, you must specify the direct collection information.
Action: Select a Target Table and Direct Field that the direct collection specifies.
No field/method pairs defined for the [mapping name] mapping.
Cause: You created a transformation mapping, but did not specify an Object --> Field Method.
Action: You must specify at least one field/method pair, unless the mapping is Read Only.
No indicator field is selected.
Cause: You created a variable one-to-one mapping, but did not specify a database field in which to store indicator values.
Action: Select the Class Indicator Field on the Class Indicator Info tab.
No indicator values are specified.
Cause: You created a variable one-to-one mapping, but did not specify indicator values for each object type.
Action: Select the Indicator Type on the Class Indicator Info tab.
No method specified for transforming a database row into this attribute.
Cause: You created a transformation mapping, but did not specify the transformation method.
Action: Select a Database Row -> Object Method on the mapping's General tab.

If you are creating a write-only mapping, you can ignore this warning.

No null value type has been selected.
Cause: You selected to Use Default Value When Database Field is Null for a mapping, but did not specify the value.
Action: Specify a default Type and/or Value on the mapping's General tab.

This message may also appear after using the Package Rename tool when upgrading an older OracleAS TopLink Mapping Workbench project.

No object type is selected.
Cause: You created an object type mapping, but did not select the type.
Action: Select the Object Type and Database Type on the mapping's General tab.
No object-type mappings have been specified.
Cause: You created an object type mapping, but did not create n object-to-database mapping.
Action: Specify at least one mapping (Database Value and Object Value) on the mapping's General tab.
No primary key(s) specified in [table name] table.
Cause: You must specify a primary key for each database table. When importing tables from a database into the OracleAS TopLink Mapping Workbench, the primary key information will be retained only if the JDBC driver supports the getPrimaryKeys() method.
Action: Ensure that a primary key is specified for each descriptor on the Descriptor Info tab.
Not all query key associations have foreign key fields specified.
Cause: You created a query key association without a foreign key.
Action: You must specify a foreign key field for each query key association on the Query Key Associations tab for variable one-to-one mapping.
No query key associations have been defined.
Cause: You created a variable one-to-one mapping, but did not define a key pair.
Action: Create or select a key pair on the mapping's Query Key Association tab.
No reference descriptor is selected.
Cause: You created a mapping, but did not specify the reference descriptor
Action: You must select a Reference Descriptor for each relationship mapping on the mapping's General tab.
No relation table is selected.
Cause: You created a many-to-many mapping, but did not specify a relation table. The relation table represents the relationship between the primary keys of the source table and target table.
Action: Select or create a Relation Table on the mapping's General tab.
No sequence field name is selected.
Cause: You selected Use Sequencing on a descriptor's Descriptor Info tab but did not specify the sequence information.
Action: Specify a Name, Table, and Field.
No sequence name is selected.
Cause: You selected Use Sequencing on a descriptor's Descriptor Info tab but did not specify the sequence information.
Action: Specify a Name, Table, and Field.
No source reference is selected.
Cause: You created a many-to-many mapping, but did not select (or create) a source table reference on the mapping's Source Reference tab.
Action: The source table reference must contain a Source field (from the mapping's relation table) and a Target field (from one of the descriptor's associated tables).
No table reference is selected.
Cause: You create a relationship mapping, but did not specify a reference table.
Action: Select (or create) a table reference for each relationship mapping on the mapping's Table Reference tab.
No target reference is selected.
Cause: You created a many-to-many mapping, but did not select (or crate) a target table reference on the mappings Target Reference tab.
Action: The source table reference must contain a Source field (from the mapping's relation table) and a Target field (from one of the descriptor's associated tables).
Object values do not match the specified attribute or object type.
Cause: For object-type mappings, you entered an Object Value that does not match the Object Type, as specified on the mapping's General tab. For example, you specified an integer type, but entered a value of A.
Action: Ensure that the Object Value matches the Object Type.
One or more field types have not been specified.
Cause: You created a field with a missing or invalid Type.
Action: You must specify the Type for each database field on the Field tab.
One of the descriptors in this package is incomplete.
Cause: One (or more) of the descriptors in a package contains errors. The OracleAS TopLink Mapping Workbench places an error icon beside the incorrect package.
Action: Expand the package to display its descriptors.
One of the packages is incomplete.
Cause: One (or more) of the packages in your project contains errors. The OracleAS TopLink Mapping Workbench places an error icon beside the incorrect project.
Action: Expand the project to display its packages.
One of the tables is incomplete.
Cause: One (or more) of the database tables in your project contains errors. The OracleAS TopLink Mapping Workbench places an error icon beside the incorrect table.
Action: Expand the database object to display its tables.
Primary keys do not match across associated tables and no reference(s) specified in multi-table policy info.
Cause: You attempted to associate multiple tables via primary key.
Action: Primary key field names must match across associated tables, or references must be defined from the primary table to each secondary table.
Primary keys(s) do not match parent's primary key(s).
Cause: In an inheritance hierarchy, the child's primary key(s) must match the root's primary key(s).
Action: Ensure that each child's Primary Key on the Descriptor Info tab matches the parent's primary key.
[descriptor name] references [reference descriptor name], which is not active.
Cause: You tried to select an inactive descriptor as a Reference Descriptor on the mapping's General tab.
Action: Either select a new Reference Descriptor, or make the descriptor active.
Root class does not include an indicator mapping for this descriptor.
Cause: The root class in the inheritance hierarchy is set to use the class indicator dictionary. The dictionary does not contain an indicator value for this child class.
Action: Select an Indicator Type on the Inheritance tab of the root class that includes the child types.
Some mappings are incomplete.
Cause: One (or more) of the attributes of a descriptor contains mapping errors. The OracleAS TopLink Mapping Workbench places an error icon beside the incorrect attribute(s).
Action: Expand the descriptor to display its mappings.
The Collection class is a Map, but the key method is not selected.
Cause: You created a direct collection mapping that uses a map class, but did not specify the key method.
Action: Select the Key Method on the mappings Collection Options tab.
The inheritance hierarchy originating in this descriptor cannot contain both aggregate and nonaggregate child descriptors.
Cause: Aggregate and class descriptors cannot be in the same inheritance hierarchy.
Action: Ensure that the inheritance hierarchy contains either aggregate or nonaggregate children – but not both.
The following mappings "Use Joining" and are mapped to the same reference descriptor: [mapping name]
Cause: You have multiple one-to-one mappings to the same descriptor, that use joining.
Action: Unselect the Use Joining option on the One-to-One Mapping General tab for all but one mapping.
The [access method type] method for this mapping's method accessing field is no longer visible to this descriptor.
Cause: You changed the class hierarchy within the project, causing the method access type (get or set) to no longer be visible to the class.
Action: Ensure that the selected method is visible to the class.
The method specified for the copy policy on this descriptor is no longer a visible member of this class.
Cause: You changed the class hierarchy within the project, causing the copy policy to no longer be visible to the class.
Action: Ensure that the selected copy policy is visible to the class.
The database type for the mapping does not match the database type of the database field.
Cause: You selected a Database Type for an Object Type mapping that differs from the type in the database.
Action: Select the Database Type on the mapping's General tab that matches the actual type in the database.
The database is incomplete.
Cause: The databases in a project contains errors. The OracleAS TopLink Mapping Workbench places an error icon beside the database.
Action: Expand the database to display its tables.
The event policy's [method type] method is no longer a visible member of this descriptor's associated class.
Cause: You changed the class hierarchy within the project, causing the method to no longer be visible to the class.
Action: Ensure that the selected method is visible to the class.
The expression [line number] on query [query name] is invalid.
Cause: One of the arguments in the query expression is missing or invalid.
Action: Edit the query and ensure that all query keys and parameters have been specified.
The following fields have multiple writable mappings: [field name].
Cause: Multiple mappings cannot write to the save database field.
Action: Each database field must have a single, writable mapping.
The following Query Keys do not have associated database fields:
Cause: The database field(s) for the query key(s) listed have been removed from the associated table.
Action: If you want to use these query key(s), then you must specify a database field(s) for them.
The following primary key fields have no writable mappings: [field name].
Cause: Each primary key field must have a writable mapping.
Action: Ensure that the primary key field mappings are not read only.
The following primary key fields are unmapped: [field name].
Cause: Each primary key field must have a writable mapping.
Action: Ensure that the primary key(s) are mapped.
The method specified for the copy policy on this descriptor is no longer a visible member of this class.
Cause: You changed the class hierarchy within the project, causing the copy policy to no longer be visible to the class.
Action: Ensure that the copy policy is visible to the class.
The method specified for the inheritance policy's class extraction method on this descriptor is no longer a visible member of this class.
Cause: You changed the class hierarchy within the project, causing the inheritance policy to no longer be visible to the class.
Action: Ensure that the inheritance policy is visible to the class.
The multi-table reference should not be defined on the database.
Cause: When using multi-tables with differently named primary keys, you must set a reference from the TOP table to the BOTTOM table. This reference must not be an actual constraint on the database.
Action: Select the table in which this is defined, and deselect the On Database option.
The parent and children of an aggregate descriptor must also be aggregates.
Cause: You created an inheritance hierarchy for an aggregate descriptor.
Action: If an aggregate descriptor is in an inheritance policy hierarchy, then all descriptors in the hierarchy must be aggregates.
The reference [table reference] does not have any field associations.
Cause: You selected a table reference for a mapping, but did not add a key pair.
Action: You must specify source and target key pairs for the reference.
The reference must have at least one field association.
Cause: You selected a table reference for a relationship mapping, but did not define a source and target field key pair.
Action: For variable one-to-one mappings, you must define a query key pair (in the source descriptor's tables) to use for the common query key.
The selected parent descriptor for this descriptor's inheritance policy does not have an associated inheritance policy.
Cause: You selected a Parent Descriptor for a descriptor's inheritance policy that does not have an inheritance policy.
Action: Parent Descriptors must have a valid inheritance policy.
The source reference does not contain any field associations.
Cause: You created a many-to-many mapping, but did not define a source and target reference for the source reference.
Action: You must define a table reference and the appropriate key pairs for each source reference.
The source reference must be specified.
Cause: You created a many-to-many mapping, but did not define a source table reference.
Action: Select or create a table reference on the mapping's Source tab.
The target reference does not contain any field associations.
Cause: You created a many-to-many mapping, but did not define a source and target reference for the target reference.
Action: You must define a table reference and the appropriate key pairs for each target reference.
The target reference must be specified.
Cause: You created a many-to-many mapping, but did not define a target table reference.
Action: On the mapping's Target tab, define a target table reference.
There is no database associated with the query key [query key name].
Cause: You did not associated the specified query key with a database table.
Action: You must select a database Name and Table on the Query Keys tab.
This class is a subclass of a final class.
Cause: If you select the Final option on the descriptor's Class Info, Class tab for a class, then the class cannot contain subclasses.
Action:
This root class has no class indicator mappings for its hierarchy.
Cause: You created an inheritance policy with the Use Class Indicator Dictionary option but did not specify the indicator values for all subclasses.
Action: Specify the indicator values for all subclasses on the descriptor's Inheritance tab.

Note:

OracleAS TopLink displays a list of each subclass and indicator value if you have identified the subclasses' parent descriptor.

"Use factory" is specified for the Instantiation policy, but all required information is not specified.
Cause: You selected the Use Factory option on the descriptor's Instantiation Policy tab, but did not specify the Factory Class, Factory Method, or Instantiation Method fields.
Action: Complete the Factory Class, Factory Method, or Instantiation Method fields on the descriptor's Instantiation tab.
"Use method" is selected for the Instantiation policy, but no method is selected.
Cause: You selected the Use Method option on the descriptor's Instantiation Policy tab, but did not specify the field.
Action: Select the Method on the descriptor's Instantiation tab.
Writable mappings defined for the class indicator field [field name].
Cause: The class indicator field should not contain any writable mappings.
Action: Select a Use Class Indicator Field on the descriptor's Inheritance tab that does not contain any writable mappings.