Oracle Messages 'Cause and Action'
Note that only error messages with cause and actions go in .msg/.msb files; other information messages stay in the resources of the components concerned and are displayed with a standard AfxMessageBox call, rather than using the full rmum error stack.
CDA-00001,1, "Repository has not been initialized"
Cause : Before opening an activity and making operation calls, the API
must be initialized within the database connection.
Action : Execute the CDAPI initialize procedure to initialize the API and
establish a context Container - see the Oracle Repository
Meta-Model and API Help for procedure details
CDA-00002,1, "Repository internal error in ciilok.get_new_range: Lock request failed."
Cause : An attempt to request a database lock was not successful.
Action : Disconnect from the database, reconnect, and then begin with a call
to 'cdapi.initialize()'.
CDA-00003,0, "API internal error in ciilok.get_new_range: Unable to allocate reference value range from CI_REFERENCE_RANGES"
Cause : All reference ranges are currently in use.
Action : Issue a call to 'cdapi.initialize()' from another database
connection to allocate more API reference ranges. This call causes
an implicit commit and so, if the current API database connection
is engaged in an activity, the call must be made from a database
connection other than the current one.
To avoid this in the future, increase the number of available
ranges, or increase the range size.
CDA-00004,0, "API internal error in %0!s: Duplicate data found in SDD_ELEMENTS/SDD_STRUCTURE_ELEMENTS"
Cause : The repository instance appears to have become corrupt. Duplicate
elements have been detected.
Action : Run a corruption detection utility on your repository instance to
determine which elements are in violation of uniqueness constraints.
CDA-00005,1, "API initialization error: SYS.DUAL table has multiple rows and should have only one"
Cause : More than one row was detected in the SYS.DUAL table.
Action : Reset the SYS.DUAL table to have a single row, with value 'X' in
its only column.
CDA-00006,1, "API initialization error: The API has already been initialized."
Cause : An attempt was made to run 'cdapi.initialize()' twice in a database
connection.
Action : 'cdapi.initialize()' must be called only once in a database
connection.
CDA-00007,1, "API message instantiation error: no message text found for %0!s-%1!s."
Cause : No message was found in the table 'RM$NLS_MESSAGES' for the given
Facility and Code.
Action : Make sure that this table was populated with data during API
installation.
CDA-00008,0, "Lock failed. Record has been locked by another user."
Cause : An exclusive database lock has been taken out on this record by
another user or session.
Action : Save outstanding work in other sessions and try again.
CDA-00009,1, "Could not lock the utility in exclusive mode."
Cause : A request was made to lock this utility in single user mode.
The request has timed out because someone else is running this
utility. Some of the utilities have to be run in exclusive
single mode.
Action : Try again later or see Enterprise Manager for who is running the
utility. Restarting the database will remove all locks.
CDA-00010,1, "System error locking the utility in exclusive mode."
Cause : Lock failed.
Action : This is an internal program error and should not normally be
issued. Note any further information/messages etc. and refer to
system/computer administrator before retrying. Restarting the
database might help. If problem persists then refer to Oracle
support.
CDA-00011,0, "Failed to lock Application System %0!s Version %1!s in exclusive mode."
Cause : Lock failed.
Action : This is an internal program error and should not normally be issued.
Note any further information/messages etc. and refer to system/
computer administrator before retrying. Restarting the database
may help. If the problem persists then refer to Oracle Support.
CDA-00012,0, "Unable to lock Application System %0!s Version %1!s in exclusive mode."
Cause : A request was made to take an exclusive lock on this Application
System. The request has timed out because another user is accessing
the Application System or another session is already holding an
exclusive lock on this Application System.
Action : Try again later. If the problem persists use Enterprise Manager
or ask your DBA to determine who is preventing you from obtaining
an exclusive lock on this Application System. Ending the session
holding the lock will remove the lock. Alternatively restarting the
database will remove all locks.
CDA-00013,0, "System error releasing user defined lock. Lock ID %0!s"
Cause : The utility was unable to remove an exclusive lock on an
Application System.
Action : End your session to remove any outstanding Application Locks you
may be holding. If the problem persists refer to your database
administrator.
/
/ 00100 .. 00199 Delete processing errors
/
CDA-00100,1, "%0!s: Cannot delete -- %1!s is connected to other application systems"
Cause : The specified element could not be deleted because it is referenced
by other application systems.
Action : Disconnect the element from all application systems other than the
owning application system before attempting to drop it.
CDA-00101,1, "%0!s: Cannot delete -- %1!s exist that reference this %2!s"
Cause : The specified element could not be deleted because it is referenced
by elements that cannot be cascade deleted.
Action : Drop the connected elements, or disconnect them from the specified
element, before reissuing the operation. If you are using a
diagramming tool, the connected elements may not be visible
and a consolidate operation may be required.
CDA-00102,1, "%0!s: Cannot delete -- %1!s of this %2!s exist"
Cause : The specified element cannot be deleted because it is referenced
by elements that cannot be cascade deleted.
Action : Drop the referenced elements, or dissociate them, before reissuing
the specified operation.
CDA-00103,0, "%0!s: This synonym is defined against %1!s and cannot be updated"
Cause : Synonyms defined against entities cannot be updated or deleted
directly.
Action : Update the entity to change its Name, Plural or Short Name.
CDA-00104,0, "%0!s: This synonym is defined against %1!s and cannot be deleted"
Cause : Synonyms defined against entities cannot be updated or deleted
directly.
Action : Update the entity to change its Name, Plural or Short Name.
CDA-00105,0, "%0!s '%1!s': An attempt was made to provide a value for an ineligible property of this Copy function"
Cause : Copy functions are limited to holding basic information only,
relying on the Master function to hold the detailed information
about the function. Valid properties in a Copy function are its
Short Definition, Sequence In Parent, Parent Reference,
Common Function Reference and Function Label.
Action : Resubmit the operation, but withhold values for all but the
restricted list of properties.
CDA-00106,1, "%0!s: Cannot be deleted. Referred to by non-analysis event classifier."
Cause : An interface classifier cannot be deleted if it is referred to by
an event classifier which has Analysis_Type_Flag set to 'N'.
Action : Remove the reference to the interface classifier or set the
Analysis_Type_Flag to 'Y'.
CDA-00107,1, "%0!s: Cannot be deleted. Referred to as top level of a business object."
Cause : This element cannot be deleted because it is
referred to by a business object.
Action : Remove the reference to this element from
the business object.
CDA-00108,1, "%0!s: Cannot delete a method which references an external generic class."
Cause : Cannot delete a method which references a generic
class that has its External_Flag property set to 'Y'.
Action : To be able to delete the method the External_Flag property
of the referenced generic class must be set to 'N'. Otherwise
remove the reference to the generic class.
CDA-00109,1, "--%0!s: Cannot be deleted. Referred to by a refining association."
Cause : This association cannot be deleted when it is referred to by
a refining association.
Action : Remove the reference to the association in the
property Association_Reference of the other association.
CDA-00110,1, "--%0!s: Cannot be deleted. Refers to an external generic class."
Cause : A general attribute cannot be deleted if it
refers to a generic class with External_Flag property set
to 'Y'.
Action : If you want delete the general attribute you must first set
the External_Flag property on the referenced generic class to 'N'.
CDA-00111,1, "%0!s: An Event Classifier cannot be deleted if generated by an Object State"
Cause : An Event Classifier that was generated as a result of an
Object State (i.e. it has a reference to an Object State in
its Object_State_Reference property) cannot be deleted.
Action : If you want to delete this Event Classifier you must first remove
the reference to the Object State in the property
Object_State_Reference.
/
/ 00200 .. 00299 Share messages
/
CDA-00200,0, "'%0!s' is not a valid element type to share among application systems"
Cause : Elements of the specified type cannot be shared among application
systems.
Action : Check the documentation to determine which element types are
shareable across application systems.
CDA-00201,0, "User requires SHARE privilege on the Application system to which shared elements are being reconnected."
Cause : Users must have SHARE privilege on the Application System to
which shared elements are being reconnected.
Action : Request SHARE privileges from your Repository Administrator.
CDA-00202,1, "Cannot share non-shareable element '%0!s'"
Cause : Certain elements are sub-types of Non-Shareable Element (see
Element documentation) and they may not be shared.
Action : This element may not be shared. Creating a copy (or in the case
of functions, a common function) is permitted, however.
CDA-00203,1, "Cannot share container '%!s'"
Cause : Containers cannot be shared.
Action : This element may not be shared. Creating a copy is permitted though.
/
/ 00500 .. 00599 Data formatting errors
/
CDA-00500,0, "%0!s: Invalid format type <%1!s>"
Cause : The specified format type is not valid.
Action : Refer to the format type rules in the Designer Meta-model and
API documentation.
CDA-00501,0, "%0!s: Unusual format type <%1!s>"
Cause : The specified format type is considered unusual, though it is valid.
Action : No action need be taken. This is an informational message only.
CDA-00502,0, "%0!s: Maximum Length must be provided for this format type <%1!s>"
Cause : The specified format type requires a Maximum Length.
Action : Update the specified element, providing a Maximum Length value.
CDA-00503,0, "%0!s: Length is invalid for this format type <%1!s> -- it has been reset to null"
Cause : The specified format type cannot be length constrained.
Action : The system automatically nullified the length constraint. No
action need be taken by the user.
CDA-00504,0, "%0!s: Maximum Length is not meaningful for this format type <%1!s>"
Cause : The specified format type cannot be length constrained.
Action : Refer to the format type rules in the Designer Meta-model and
API documentation.
CDA-00505,0, "%0!s: Maximum Length <%1!s> is larger than the allowed limit for this format type <%2!s>"
Cause : The supplied Maximum Length exceeds the limit for this format type.
Action : Refer to the format type rules in the Designer Meta-model and
API documentation.
CDA-00506,0, "%0!s: Maximum Length must be at least 1 for this format type <%1!s>"
Cause : The Maximum Length for this format type must have a positive integer
value.
Action : Refer to the format type rules in the Designer Meta-model and
API documentation.
CDA-00507,0, "%0!s: Precision is mandatory for this format type <%1!s>"
Cause : The specified format type must be constrained by a Precision.
Action : Update the specified element, providing a Precision value with
this format type.
CDA-00508,0, "%0!s: Precision cannot be specified for this format type <%1!s> -- it has been reset to null"
Cause : The specified format type can have no Precision.
Action : The system automatically nullified the Precision property value.
No action need be taken by the user.
CDA-00509,0, "%0!s: Precision places are not meaningful for this format type <%1!s>"
Cause : The specified format type cannot be precision constrained.
Action : No action need be taken. This is an informational message only.
CDA-00510,1, "%0!s: Precision is out of range for this format <%1!s>"
Cause : The Precision value must be within the range specified by the
Oracle SQL language documentation.
Action : Refer to the format type rules in the Oracle SQL language
documentation.
CDA-00511,0, "%0!s: %1!s must not contain whitespace characters"
Cause : Use of blank spaces is not allowed in this property.
Action : Use underscores instead of spaces in the property.
CDA-00512,0, "%0!s: Datatype, Maximum Length and Scale are inconsistent with the specified Denormalized Summary Function"
Cause : When the Denormalized Summary Function is 'COUNT', Datatype must
be numeric, Maximum Length must be greater than or equal to 5, and
Scale must be 0.
Action : Make the element values consistent.
CDA-00513,0, "%0!s: The Datatype of this column (%1!s) is not consistent with the Datatype of its denormalized column (%2!s)"
Cause : Datatype values of denormalized columns must be consistent
according to the specified Denormalized Summary Function.
Action : Refer to the format type rules in the Designer Meta-model and
API documentation.
CDA-00514,0, "%0!s: Maximum Length must not be specified when the Datatype is 'DATE'"
Cause : When an item is specified as being of the Datatype 'DATE'
the MAXIMUM_ LENGTH property must be null.
Action : If Datatype is 'DATE' ensure that the MAXIMUM_LENGTH property
is not given a value.
/
/ 00700 .. 00799 ??>
/
CDA-00700,0, "%0!s: Too many references provided"
Cause : Too many reference values were provided in an arc relationship.
Action : Provide a reference for only one relationship in the arc.
CDA-00701,0, "%0!s: Event is maintained internally and cannot be updated"
Cause : An attempt was made to update an Event that is maintained
internally by the system.
Action : This operation was automatically rolled back. No action need be
taken by the user. This is an informational message only.
CDA-00702,0, "%0!s: Mismatch between %1!s referenced by the two ends of this relationship or association"
Cause : The specified relationship end or association role does not match
the one at the other end. Either the two ends do not reference the
same entities or object types consistently, or they do not reference
each other.
Action : Delete both relationship ends or association roles and re-create
them.
CDA-00703,0, "Cannot delete application systems through CDAPI; use the Repository Object Navigator"
Cause : An attempt was made to delete an application system version through
the API. This operation must be performed through the Repository
Object Navigator.
Action : Use the Repository Object Navigator to drop a version of an
application system.
CDA-00704,0, "%0!s: Maximum Sequence In Parent number (999) reached during auto-generation -- using a non-maximum value"
Cause : When generating a value for Sequence In Parent, the maximum value
(999) was reached. A non-maximum value was used instead.
Action : No action need be taken. This is an informational message only.
CDA-00705,0, "%0!s: Maximum number of root functions (999) has been exceeded -- cannot create"
Cause : The limit on the number of root functions has been exceeded in the
context application system.
Action : Either delete a root function in the context application system,
or make one subordinate to another function.
CDA-00706,0, "%0!s: Maximum number of child functions (999) has been exceeded for parent %1!s -- cannot create"
Cause : The limit on the number of child functions for the specified parent
has been exceeded.
Action : Either delete a sibling function or move one elsewhere in the
function hierarchy.
/
/ 00810 .. 00819 UE Text Type Messages
/
CDA-00810,0, "Invalid Text Type '%0!s'"
Cause : An invalid Text Type was typed.
Action : Refer to the list of valid values specified for this property in
the documentation.
CDA-00811,0, "Text Type '%0!s' already exists"
Cause : This text type already exists - it cannot be assigned to a
new Text Type.
Action : Choose another value for Text Type.
CDA-00812,0, "Unknown Text Type '%0!s'"
Cause : An unknown Text Type was supplied.
Action : Refer to the list of valid values specified for this property in
the documentation.
CDA-00813,0, "Operation denied: Text Type '%0!s' is not a user-extended text type"
Cause : The Text Type value supplied was not a user-extended text type.
Action : Refer to the list of valid values specified for this property in
the documentation.
CDA-00814,0, "Operation denied: Text Type '%0!s' is published"
Cause : The Text Type value supplied is a published text type.
Action : Refer to the list of valid values specified for this property in
the documentation.
CDA-00815,0, "Operation denied: Text Type '%0!s' is not published"
Cause : The Text Type value supplied is an unpublished text type.
Action : None - text type is already unpublished.
CDA-00816,1, "Usage exists for Text Type %0!s - Cannot unpublish"
Cause : Can only carry out an unpublish operation on a user extended
text type with no text usages.
Action : Ensure that this text type is not used by any element types
before unpublishing.
/
/ 00820 .. 00829 UE Text Type Usage Messages
/
CDA-00820,0, "Text Type '%0!s' for the text usage does not exist"
Cause : The Text Type specified for the text usage does not exist.
Action : Refer to the list of valid values specified for the property in
the documentation.
CDA-00821,0, "The Element Type ID %0!s specified for the text usage does not exist"
Cause : The Element Type ID specified for the text usage does not exist.
Action : Refer to the list of valid values specified for the property in
the documentation.
CDA-00822,0, "Text usage already exists: Text Type = '%0!s', Element Type ID = '%1!s'"
Cause : The text usage identified by the specified Text Type and Element
Type ID already exists.
Action : Specify a combination of values to identify a new text usage.
CDA-00823,0, "Unknown text type usage: Text Type = '%0!s', Element Type ID = %1!s"
Cause : The specified Text Type and Element Type ID do not identify a known
text usage.
Action : Specify a combination of values to identify a known text usage.
CDA-00824,0, "Operation denied: Not an extended Text Type usage"
Cause : The specified usage is not an extended Text Type usage.
Action : Specify an extended Text Type usage.
CDA-00825,0, "Operation denied: Text Type usage is published"
Cause : The operation was called with the ID of a user-defined
element type which is published, and this operation
requires that the element type is not published.
Action : Specify the ID of an unpublished user-defined
element type or unpublish this element type.
CDA-00826,0, "Text Type '%0!s' is not published"
Cause : The operation was called with the ID of a user-defined
element type which is not published, and this operation
requires that the element type is published.
Action : Specify the ID of a published user-defined
element type or publish this element type.
CDA-00827,0, "Operation denied: Text Type usage is not published - Cannot unpublish"
Cause : Can only carry out an unpublish operation on a published
user extended text usage.
Action : None - this text type usage is already unpublished.
CDA-00828,0, "Instances of Text Usage '%0!s' currently exist - Cannot unpublish"
Cause : Can only carry out an unpublish operation on a user extended
text usage with no instances.
Action : Delete the instances of this text usage before unpublishing.
/
/ 00830 .. 00839 UE Element Type Messages
/
CDA-00830,0, "Invalid Extended Element Short Name '%0!s' (should be E1 through E499)"
Cause : SHORT_NAME is mandatory and must begin with E
and be followed by a number between 1 an 499.
Action : Pick a SHORT_NAME that follows the above rule.
CDA-00831,0, "Short Name must be specified for an Extended Element Type"
Cause : SHORT_NAME is mandatory and has not been specified.
Action : Specify SHORT_NAME.
CDA-00832,0, "An Element Type with Short Name '%0!s' already exists"
Cause : SHORT_NAME must be unique across the Repository.
Action : Specify a unique SHORT_NAME.
CDA-00833,0, "Name must be specified for an Extended Element Type"
Cause : NAME is mandatory and has not been specified.
Action : Specify NAME.
CDA-00834,0, "An Element Type with Name '%0!s' already exists"
Cause : NAME must be unique across the Repository.
Action : Specify a unique NAME.
CDA-00835,0, "Plural Name must be specified for an Extended Element Type"
Cause : PLURAL_NAME is mandatory and has not been specified.
Action : Specify PLURAL_NAME.
CDA-00836,0, "An Element Type with Plural Name '%0!s' already exists"
Cause : PLURAL_NAME must be unique across the Repository.
Action : Specify a unique PLURAL_NAME.
CDA-00837,0, "Element Type %0!s does not exist"
Cause : The operation was called with the ID of an unknown
(or non-existent) element type.
Action : Specify the ID of a user-defined element type
(not instance).
CDA-00838,0, "Element Type '%0!s' is not a user-extendible type"
Cause : The operation was called with the ID of an element
type which is not user-defined.
Action : Specify the ID of a user-defined element type (e.g. E64).
CDA-00839,0, "Element Type '%0!s' is published"
Cause : The operation was called with the ID of a user-defined
element type which is published, and this operation
requires that the element type is not published.
Action : Specify the ID of an unpublished user-defined
element type or unpublish this element type.
/
/ 00840 .. 00859 UE Association Type Messages
/
CDA-00840,0, "Invalid Extended Association Short Name '%0!s' (should be A1 through A499)"
Cause : SHORT_NAME is mandatory and must begin with A
and be followed by a number between 1 an 499.
Action : Pick a SHORT_NAME that follows the above rule.
CDA-00841,0, "Short Name must be specified for an Extended Association Type"
Cause : SHORT_NAME is mandatory and has not been specified.
Action : Specify SHORT_NAME.
CDA-00842,0, "An Association Type with Short Name '%0!s' already exists"
Cause : SHORT_NAME must be unique across the Repository.
Action : Specify a unique SHORT_NAME.
CDA-00843,0, "Name must be specified for an Extended Association Type"
Cause : NAME is mandatory and has not been specified.
Action : Specify NAME.
CDA-00844,0, "An Association Type with Name '%0!s' already exists"
Cause : NAME must be unique across the Repository.
Action : Specify a unique NAME.
CDA-00845,0, "Plural Name must be specified for an Extended Association Type"
Cause : PLURAL_NAME is mandatory and has not been specified.
Action : Specify PLURAL_NAME.
CDA-00846,0, "An Association Type with Plural Name '%0!s' already exists"
Cause : PLURAL_NAME must be unique across the Repository.
Action : Specify a unique PLURAL_NAME.
CDA-00847,0, "Association Type %0!s does not exist"
Cause : The operation was called with the ID of an unknown
(or non-existent) association type.
Action : Specify the ID of a user-defined association type
(not instance).
CDA-00848,0, "Association Type '%0!s' is not a user-extendible type"
Cause : The operation was called with the ID of an association
type which is not user-defined.
Action : Specify the ID of a user-defined association type (e.g. A64).
CDA-00849,0, "Association Type '%0!s' is published"
Cause : The operation was called with the ID of a user-defined
association type which is published, and this operation
requires that the association type is not published.
Action : Specify the ID of an unpublished user-defined
association type or unpublish this association type.
CDA-00850,0, "Invalid Part Of reference %0!s"
Cause : PART_OF_REFERENCE must refer to a Primary Access Control
element type or one of a limited number of Secondary Access
Control element types.
Action : Refer to the Repository Administration Utility 'Maintain User
Extensions' section for the full list of valid PART_OF element
types.
CDA-00851,0, "Invalid Part Of Degree '%0!s' (should be NULL, '1' or 'M')"
Cause : PART_OF_DEGREE has valid values NULL, '1' or 'M'.
Action : Set one of the valid values.
CDA-00852,0, "Invalid Use Of reference %0!s"
Cause : USE_OF_REFERENCE must refer to a Primary Access Control
element type or one of a limited number of Secondary Access
Control element types.
Action : Refer to the Repository Administration Utility 'Maintain User
Extensions' section for the full list of valid USE_OF element
types.
CDA-00853,0, "Invalid Use Of Degree '%0!s' (should be NULL, '1', or 'M')"
Cause : USE_OF_DEGREE has valid values NULL, '1' or 'M'.
Action : Set one of the valid values.
CDA-00854,0, "Data exists for Association Type %0!s - Cannot unpublish"
Cause : Can only carry out an unpublish operation on a user extended
association type with no instance data.
Action : Delete all instance data of this association type before
unpublishing.
CDA-00855,0, "Text Type %0!s refers to Association Type %1!s - Cannot unpublish"
Cause : Can only carry out an unpublish operation on a user extended
association type with no text usages.
Action : Delete (or unpublish?) all text usages of this element type
unpublishing.
CDA-00856,0, "Association Type '%0!s' is not published - Cannot unpublish"
Cause : Can only carry out an unpublish operation on a published
user extended association type.
Action : None - this element type is already unpublished.
CDA-00857,0, "Association Type '%0!s' is not a User Type - Cannot remap"
Cause : Can only carry out a remap operation on a User Defined
Association Type, not a System Association Type.
Action : Remap another Association Type.
/
/ 00860 .. 00869 UE Property messages
/
CDA-00860,0, "Specified property '%0!s' does not exist"
Cause : The operation was called with the ID of an unknown
(or non-existent) property.
Action : Specify the ID of a user-defined property.
CDA-00861,0, "Property '%0!s' is not a user-extendible property"
Cause : The operation was called with the ID of a property
which is not user-defined.
Action : Specify the ID of a user-defined property
(e.g. USER_DEFINED_PROPERTY_1).
CDA-00862,0, "Property '%0!s' is published"
Cause : The operation was called with the ID of a user-defined
property which is published, and this operation
requires that the property is not published.
Action : Specify the ID of an unpublished user-defined
property or unpublish this property.
CDA-00863,0, "Property Displayed Name must be specified"
Cause : DISPLAY_NAME is mandatory and has not been specified.
Action : Specify DISPLAY_NAME.
CDA-00864,0, "Unknown Datatype '%1!s' for property '%0!s'"
Cause : DISPLAY_DATATYPE must be either 'CHAR','NUMBER' or 'DATE'
Action : Set a valid value for DISPLAY_DATATYPE.
CDA-00865,0, "Invalid Length '%2!s' specified for property '%0!s' Datatype '%1!s'"
Cause : DISPLAY_LENGTH must be set and be between 0 and 240 inclusive.
Action : Set a valid value for DISPLAY_LENGTH.
CDA-00866,0, "Invalid Precision '%2!s' specified for property '%0!s' Datatype '%1!s'"
Cause : DISPLAY_PRECISION must not be set for CHAR and DATE datatypes and
for NUMBER datatypes may be null or between 1 and 38.
Action : Set a valid value for DISPLAY_PRECISION.
CDA-00867,1, "Invalid Scale '%2!s' specified for property '%0!s' Datatype '%1!s'"
Cause : DISPLAY_SCALE must not be set for CHAR and DATE datatypes and
for NUMBER datatypes may be null or between 0 and DISPLAY_PRECISION.
Action : Set a valid value for DISPLAY_SCALE.
CDA-00868,0, "Invalid Mandatory flag '%0!s'; expected 'Y' or 'N'"
Cause : IS_MANDATORY must be 'Y' or 'N'.
Action : Set a valid value for IS_MANDATORY.
CDA-00869,0, "Data exists for Property %0!s - Cannot unpublish"
Cause : Can only carry out an unpublish operation on a user extended
property, when all the instance data is null.
Action : Nullify all instance data of this Property before
unpublishing.
/
/ 00870 .. 00880 UE Publish and remap messages
/
CDA-00870,0, "Data exists for Element Type %0!s - Cannot unpublish"
Cause : Can only carry out an unpublish operation on a user extended
element type with no instance data.
Action : Delete all instance data of this element type before
unpublishing.
CDA-00871,0, "Association Type %0!s refers to Element Type %1!s - Cannot unpublish"
Cause : Can only carry out an unpublish operation on a user extended
element type with no associations.
Action : Delete (or unpublish?) this association before unpublishing.
CDA-00872,0, "Text Type %0!s refers to Element Type %1!s - Cannot unpublish"
Cause : Can only carry out an unpublish operation on a user extended
element type with no text usages.
Action : Delete (or unpublish?) all text usages of this element type before
unpublishing.
CDA-00873,0, "Element Type '%0!s' is not published - Cannot unpublish"
Cause : Can only carry out an unpublish operation on a published
user extended element type.
Action : None - this element type is already unpublished.
CDA-00874,0, "Property '%0!s' is not published - Cannot unpublish"
Cause : Can only carry out an unpublish operation on a published
user extended property.
Action : None - this property is already unpublished.
CDA-00875,0, "Element Type '%0!s' is not a User Type - Cannot remap"
Cause : Can only carry out a remap operation on a User Defined
Element Type, not a System Element Type.
Action : Remap another Element Type.
CDA-00876,0, "Property '%0!s' is not extended - Cannot be source of a remap"
Cause : Can only carry out a remap operation from a user extended
Property.
Action : Remap from another Property.
CDA-00877,0, "Property '%0!s' is extended - Cannot be target of a remap"
Cause : Can only carry out a remap operation to a Property which is
not extended.
Action : Remap to a different Property.
CDA-00878,0, "Cannot remap as Properties '%0!s' and '%1!s' are in different Element Types"
Cause : The source and target Properties for a remap operation must belong
to the same Element Type.
Action : Choose Properties in the same Element Type.
/
/ 00900 .. 00999 UE Runtime errors
/
CDA-00901,0, "Unknown element type ID %0!s"
Cause : The operation was called with the ID of an unknown
(or non-existent) element type.
Action : Specify the ID of a user-defined element type
(not instance).
CDA-00902,0, "Unknown association type ID %0!s"
Cause : The operation was called with the ID of an unknown
(or non-existent) association type.
Action : Specify the ID of a user-defined association type
(not instance).
CDA-00903,0, "Internal error: Association type %0!s missing from CIUE_ASSOCIATION_TYPES"
Cause : Internal error - should not occur
Action : Contact Oracle support
CDA-00904,0, "PART OF end of association wrong: Expected type '%0!s', found type '%1!s'"
Cause : The element type at the end of the PART_OF_REFERENCE property
is of the wrong element type.
Action : Set PART_OF_REFERENCE to refer to an element of the
expected element type.
CDA-00905,0, "PART OF end of association wrong: Element %0!s does not exist"
Cause : No element exists with the ID specified in PART_OF_REFERENCE.
Action : Set PART_OF_REFERENCE to refer to an element of the
expected element type.
CDA-00906,0, "USE OF end of association wrong: Expected type '%0!s', found type '%1!s'"
Cause : The element type at the end of the USE_OF_REFERENCE property
is of the wrong element type.
Action : Set USE_OF_REFERENCE to refer to an element of the
expected element type.
CDA-00907,0, "USE OF end of association wrong: Element %0!s does not exist"
Cause : No element exists with the ID specified in USE_OF_REFERENCE.
Action : Set USE_OF_REFERENCE to refer to an element of the
expected element type.
CDA-00908,0, "Equivalent association between specified %0!s and %1!s already exists"
Cause : An association of this type already exists between these two
elements.
Action : Change PART_OF_REFERENCE, USE_OF_REFERENCE or the association type.
CDA-00909,0, "An PART OF association already exists to the specified '%0!s'"
Cause : The PART OF end of this association is defined as being
'one and only one' (i.e. it has PART_OF_DEGREE = 1),
and an association of this type already exists to the element
referred to in PART_OF_REFERENCE.
Action : Change the PART_OF_REFERENCE to refer to another element
of the same type or modify the definition of this user-defined
association.
CDA-00910,0, "A USE OF association already exists to the specified '%0!s'"
Cause : The USE OF end of this association is defined as being
'one and only one' (ie. it has USE_OF_DEGREE = 1),
and an association of this type already exists to the
element referred to in USE_OF_REFERENCE.
Action : Change the USE_OF_REFERENCE to refer to another element of
the same type or modify the definition of this user-defined
association.
CDA-00921,0, "Property '%0!s' cannot be set because it is not published"
Cause : The user-defined property specified has not been published so may
not be updated or inserted.
Action : Publish the property in the Repository Administration Utility.
CDA-00922,0, "Property '%0!s' is not updateable"
Cause : The user-defined property specified has been defined as
'not updateable'.
Action : Alter the property definition in the Repository
Administration Utility.
CDA-00923,0, "Property '%0!s' is mandatory (and NULL specified)"
Cause : The user-defined property specified has been defined as
mandatory and a null value has been set.
Action : Alter the property definition in the Repository
Administration Utility.
CDA-00924,0, "Property '%0!s' length %1!s is longer than maximum allowed (%2!s)"
Cause : The user-defined property specified has a maximum length specified
that is smaller than the data value being set.
Action : Set a shorter value for this property or alter the
property definition in the Repository Administration Utility.
CDA-00925,0, "Invalid date value '%1!s' specified for property '%0!s'"
Cause : The internal DATE format is 'YYYYMMDDHHMISS', and the value does
not confirm to this.
Action : Set a DATE value that confirms to this rule.
CDA-00926,0, "Invalid number '%1!s' specified for property '%0!s'"
Cause : The value specified is not a valid number.
Action : Set a valid number.
CDA-00927,1, "Number '%1!s' value for property '%0!s' is too big (-%2!s < value < %2!s)"
Cause : The value specified is too large for the precision and scale
defined for this property.
Action : Set a smaller value for this property or alter the
property definition in the Repository Administration Utility.
/
/ 01000 .. 01999 Fatal errors during pre-process
/
CDA-01000,1, "%0!s: Average Length (%1!s) is greater than Maximum Length (%2!s)"
Cause : The Average Length must be less than or equal to the Maximum Length.
Action : Update the element and provide consistent Average Length and
Maximum Length values.
CDA-01001,0, "%0!s: The Start Value (%1!s) must be between Minimum Value (%2!s) and Maximum Value (%3!s)"
Cause : The Start Value is outside the range implied by the Minimum Value
and Maximum Value.
Action : Specify a Start Value that is consistent with the Minimum Value and
Maximum Value.
CDA-01002,0, "%0!s: Initial Transaction (%1!s) exceeds Maximum Transaction (%2!s)"
Cause : The Initial Transaction must be less than or equal to the Maximum
Transaction.
Action : Update the element and provide consistent Initial Transaction and
Maximum Transaction values.
CDA-01003,1, "%0!s : Name %1!s is not a valid ORACLE object name."
Cause : The rules for naming are as follows:
1) Object name must begin with an alphabetical character (A-Z).
2) Object name can only contain characters: A-Z, 0-9, $, # and _.
3) Enclose name in double quotes to include other characters.
4) Object Name cannot be that of an ORACLE reserved word
except in the case of Database Roles where the following
reserved words are allowed; CONNECT, DBA, RESOURCE
and PUBLIC.
Action : Ensure ORACLE object name does not include any
illegal characters or formatting.
CDA-01004,1, "%0!s: Average Attribute Length (%1!s) is greater than Maximum Attribute Length (%2!s)"
Cause : The Average Attribute Length must be less than or equal to the
Maximum Attribute Length.
Action : Update the element and provide consistent Average Attribute Length
and Maximum Attribute Length values.
CDA-01005,1, "%0!s: Average Column Length (%1!s) is greater than Maximum Column Length (%2!s)"
Cause : The Average Column Length must be less than or equal to the
Maximum Column Length.
Action : Update the element and provide consistent Average Column Length and
Maximum Column Length values.
CDA-01006,1, "%0!s: Super-type %1!s is itself a sub-type of a domain"
Cause : An invalid loop was found in a domain hierarchy. A domain cannot
be an ancestor of one of its descendants.
Action : Reset one of the super-type references to remove the inconsistency.
CDA-01007,1, "%0!s: Initial Volume (%1!s) exceeds Maximum Volume (%2!s)"
Cause : The Initial Volume must be less than or equal to the Maximum Volume.
Action : Update the element and provide consistent Initial Volume and
Maximum Volume values.
CDA-01008,1, "%0!s: Average Volume (%1!s) exceeds Maximum Volume (%2!s)"
Cause : The Average Volume must be less than or equal to the Maximum Volume.
Action : Update the element and provide consistent Average Volume and
Maximum Volume values.
CDA-01009,1, "Attribute Value for %0!s: Low Value (%1!s) exceeds High Value (%2!s)"
Cause : The Low Value must be less than or equal to the High Value.
Action : Update the element and provide consistent Low Value and High Value
values.
CDA-01010,1, "%0!s: Specified super-type %1!s must be owned by the context application system"
Cause : In order to specify a super-type for an element, both the element
and its super-type must be owned by the context application system.
Action : Change the context application system or connect the specified
element to the current context application system.
CDA-01011,1, "%0!s: Referenced %1!s is not part of %2!s"
Cause : An attempt was made to include an Attribute in a Unique Identifier
Entry that is not part of the Entity against which the Unique
Identifier is specified.
Action : Include only those Attributes and Relationships that are specified
against the Entity that is constrained by the Unique Identifier
Entry.
CDA-01012,1, "%0!s: Referenced %1!s is not connected to %2!s"
Cause : An attempt was made to include a Relationship End in a Unique
Identifier Entry that is not part of the Entity against which the
Unique Identifier is specified.
Action : Include only those Attributes and Relationships that are specified
against the Entity that is constrained by the Unique Identifier
Entry.
CDA-01013,0, "%0!s: %1!s is not of 'ONE AND ONLY ONE' Degree"
Cause : Relationships in a Unique Identifier should generally be of Degree
ONE AND ONLY ONE. This message is simply to alert the user of a
possible modeling error.
Action : It is recommended that the Relationship be updated to be of Degree
ONE AND ONLY ONE, though violation of this rule will not prevent
an activity from being closed successfully.
CDA-01014,1, "%0!s: Cannot change the From Relationship End Reference when the relationship end is part of a UID"
Cause : A Relationship End that is part of a Unique Identifier Entry for
an Entity cannot be transferred to another Entity.
Action : Remove the Relationship End from the Unique Identifier of the
entity.
CDA-01015,1, "%0!s: Cannot change the From Relationship End Reference when the relationship end is in an arc"
Cause : A relationship end that is part of an arc cannot be transferred
to another entity without removing it from the arc.
Action : Nullify the Arc Number property on the relationship end when
transferring the relationship.
CDA-01016,0, "%0!s: Minimum Value (%1!s) exceeds Maximum Value (%2!s)"
Cause : The Minimum Value must be less than or equal to the Maximum Value.
Action : Update the specified element and provide consistent Minimum Value
and Maximum Value values.
CDA-01017,1, "%0!s: Minimum Volume (%1!s) exceeds Maximum Volume (%2!s)"
Cause : The Minimum Volume must be less than or equal to the Maximum Volume.
Action : Update the specified element and provide consistent Minimum Volume
and Maximum Volume values.
CDA-01018,1, "%0!s: Average Volume (%1!s) exceeds Maximum Volume (%2!s)"
Cause : The Average Volume must be less than or equal to the Maximum Volume.
Action : Update the specified element and provide consistent Average Volume
and Maximum Volume values.
CDA-01019,1, "Function Attribute Usage: mismatch in usage flags between %0!s and %1!s for %2!s"
Cause : A mismatch has been detected between the usage flags in a Function
Attribute Usage element and the corresponding Function Entity Usage
element.
Action : Refer to the documentation for rules regarding usage flags.
CDA-01020,1, "%0!s: An Entity Reference must be supplied for CHANGE events"
Cause : When CHANGE events are performed, they must be performed on
entities.
Action : Provide an Entity Reference when specifying an event of type
CHANGE.
CDA-01021,0, "Event trigger for %0!s and %1!s: Either an Event triggers a Function or a Function triggers an Event"
Cause : If the triggering reference is a function, the triggered reference
must be an event. If the triggering reference is an event, the
triggered reference must be a function.
Action : Provide an Event Reference and a Function Reference.
CDA-01022,0, "%0!s: A domain cannot be its own super-type"
Cause : A Supertype Reference specified against a domain appears already
to be a sub-type of that domain; this violates the hierarchy.
Action : Reset the Supertype Reference property either of the super-type or
of the sub-type, to avoid the violation.
CDA-01023,0, "%0!s: Minimum Extents (%1!s) exceeds Maximum Extents (%2!s)"
Cause : The Minimum Extents must be less than or equal to the Maximum
Extents for storage parameter definitions.
Action : Enter consistent values for Minimum Extents and Maximum Extents.
CDA-01024,1, "%0!s: %1!s is already a child of %2!s. It may only be in one TYPE BODY"
Cause : A PLSQL Module that is a child of a TYPE BODY PLSQL Module is
specific to that Type Body and it is not be possible
to reuse it elsewhere (i.e. via a Module Network, as a child
of another Type Body or of a Procedure etc).
Action : Do not associate this PLSQL Module with this TYPE BODY
PLSQL Module.
CDA-01025,1, "%0!s: %1!s already exists for %2!s. Only one TYPE BODY is permitted"
Cause : Only one TYPE BODY PL/SQL Module is permitted for an
Oracle Object Type, and one exists for this Oracle Object
Type already.
Action : Delete the other TYPE BODY PL/SQL Module, or choose a different
value for PLSQL_MODULE_TYPE.
CDA-01026,0, "%0!s: Maximum length of Journal table names is 27 characters"
Cause : The name of a journal table, for logging the activities on a table,
must not exceed 27 characters in length.
Action : Shorten the table name to 27 characters.
CDA-01027,0, "%0!s: Sum of Percent Free and Percent Used exceeds 100"
Cause : The parameters PCTFREE and PCTUSED sum to over 100.
Action : Enter consistent values for the PCTFREE and PCTUSED parameters.
CDA-01028,0, "%0!s: Referenced %1!s is not connected to the context application system"
Cause : The element referred must be connected to the context application
system.
Action : Either share the referenced element into the context application
system or specify a reference to another element.
element.
CDA-01029,1, "%0!s: Document Attachments are not valid for this element type"
Cause : Documents may only be attached to Primary Access Control
elements (PACs) and some simple Secondary Access Control
elements (SACs).
Action : Attach this document to another element type.
CDA-01030,1, "An implementation for this database object already exists in the schema"
Cause : Each schema may contain only one implementation for each
database object. The schema you are attempting to copy
to already contains an implementation for the database
object implemented by the item you are copying.
Action : Either delete the database object implementation that
is already present in the schema, or use a different
schema for the implementation you are attempting to
copy.
CDA-01031,1, "%0!s: MODULE_LEVEL Module Components must not be within a window"
Cause : Module level components are used by the reports
generator to summarize data on items in other module
components in the module.
Since the reports generator views a window as a report
it is invalid for the module level module component to be
in one window and the summarized module component
in a different window.
Action : Set the window property on the module component
inclusion to NULL and repeat the operation.
CDA-01032,0, "%0!s: Table has more than 12 triggers with create status = 'Y'"
Cause : For Versions 7.0.X of the Oracle database, there can be only one
database trigger of a particular execute time, event and trigger
level per table. The maximum possible number of triggers is
therefore 2x3x2 = 12. Versions 7.1.X have no such constraint.
Action : Warning only: No action must be taken
CDA-01033,0, "%0!s: Trigger of this event, level and execute time already exists"
Cause : Versions 7.0.X of the Oracle database cannot implement more than
one database trigger of a particular execution time, event and
trigger level per table; e.g. only one PRE-INSERT ROW level trigger
per table. Versions 7.1.X can cope with more than one, but the
order in which the database triggers are fired is indeterminate.
Action : Warning only: No action must be taken
CDA-01034,1, "%0!s: Cannot delete -- There is a corresponding Activity_Usage hierarchy"
Cause : The specified element could not be deleted because there
exists at least one Activity_Usage with a reference to another
Activity_Usage and the Activity_Definitions referred to by
these parent-child Activity_Usages form the Parent_Activity_Usage
and Child_Activity_Usage of this element.
Action : Break the association with the corresponding Activity_Usage
hierarchy before reissuing the operation.
CDA-01035,1, "%0!s: Invalid Trigger EXECUTION_TIME (%1!s)"
Cause : An invalid EXECUTION_TIME has been chosen for this trigger.
Action : For details of valid values for EXECUTION_TIMEs and contexts
see the Designer Model documentation.
CDA-01036,1, "%0!s: Invalid Trigger TRIGGER_LEVEL (%1!s)"
Cause : An invalid TRIGGER_LEVEL has been chosen for this trigger.
Action : For details of valid TRIGGER_LEVELs and their contexts, see the
Designer Model documentation.
CDA-01037,1, "%0!s: Classifier must be abstract if it has Overridable Methods"
Cause : This Classifier must have its Abstract property set to
'Yes' when it has at least one Method that has its Overridable
property set to 'MUST'.
Action : Make sure that the Abstract property for this Classifier
is set to 'Yes'.
CDA-01038,1, "%0!s : %1!s cannot be inserted, base table usage already exists."
Cause : A table usage already exists for this module component with the
usage type of Base.
Action : If this is a table usage of another usage type other than Base,
ensure the correct type is selected in the Property Palette.
CDA-01039,1, "%0!s: Can only be Abstract if all of its Methods are Overridable."
Cause : The Abstract Flag for a Classifier cannot be set to 'Yes' if
any of its methods have their Overridable property set to
'CANNOT'
Action : Make sure the Abstract Flag for this Classifier
is not set to 'Yes'.
CDA-01040,1, "%0!s: PL/SQL Module defined as Trigger from %1!s must have type of Trg-Logic"
Cause : The PL/SQL Module was defined as a Trigger from a Table and must
have type of Trg-Logic.
Action : Keep the type value as Trg-Logic.
CDA-01041,1, "%0!s: Multiple modifiable entity object attributes amongst supertypes."
Cause : Only one entity object attribute in an entity object and its
supertypes can have Modification_Flag = 'Y'.
Action : Set the Modification_Flag to 'N' on either this element or one of
the supertypes of the referenced entity objects.
CDA-01042,1, "%0!s: PL/SQL definition referenced from Trigger. Cannot change type. "
Cause : This definition is referenced by a trigger and therefore the type of
module can only be of Trg-Logic.
Action : Ensure type is kept as Trg-Logic.
CDA-01043,0, "%0!s: Sum of PERCENT_FREE and PERCENT_USED exceeds 100"
Cause : The algorithm used is:
(nvl(PERCENT_FREE,10) + nvl(PERCENT_USED,40)) <= 100
Action : Set PERCENT_FREE and PERCENT_USED so that the above
rule is fulfilled.
CDA-01044,1, "%0!s : No base table usage defined on parent %1!s"
Cause : An attempt was made to create a Base Table Usage
on a Subcomponent where no Base Table Usage
has been defined on the parent Module Component
of the Subcomponent. Base Table Usages can only
be defined for Subcomponents if a Base Table Usage
has been defined for the parent Module Component.
Action : Ensure a corresponding Base Table Usage
exists on the parent Module Component before
attempting to create one on the Subcomponent.
CDA-01045,1, "%0!s : Base Table Usage of %1!s conflicts with usage of %2!s defined on %!3s"
Cause : The Base Table Usage specified for this Subcomponent
is for a different table to the Base Table Usage on the
parent Module Component. The Base Table Usage
of a Subcomponent must match the Base Table
Usage defined for its parent Module Component.
Action : Create a Base Table Usage for the
same table as the Base Table Usage
on the parent Module Component.
CDA-01046,1, "Specified Table Partition %0!s is on different table to Index Storage %1!s"
Cause : An attempt was made to create a Local Index Partition
against a Table Partition for a different table to the Index
Storage the Index Partition is for. Local Index Partitions
must be defined against Table Partitions of the same table
as the Index Storage they partition.
Action : Specify a Table Partition from the
same table as the Index Storage.
CDA-01047,1, "%0!s: Date Document Changed (%1!s) earlier than Date Document Created (%2!s)"
Cause : The Date Document Changed value must be later than or the
same as the Date Document Created value.
Action : Update the element and provide consistent Date Document Created and
Date Document Changed values.
CDA-01049,0, "%0!s: Invalid Function Return type (%1!s)"
Cause : The datatype of the return value has been set to one
which is not valid.
Action : For details on valid datatypes, see the API and Model Reference
Guide, which you can access from the Start menu.
CDA-01051,0, "%0!s: Generators may truncate this title to 15 characters"
Cause : The SHORT_NAME property value exceeds 15 characters and
this may be truncated to 15 characters when generated.
Action : Warning only: no action need be taken.
CDA-01056,0, "%0!s: Only Tables, Views and Snapshots can have constraints"
Cause : Attempting to attach a primary, unique or foreign key or check
constraint to a Record. Only Tables, Views and Snapshots can
have such constraints.
Action : Ensure that the Record does not have any constraints attached.
CDA-01057,0, "%0!s: Specified Exception Table does not exist"
Cause : The Exception Table specified does not exist within the
context of this application.
Action : This is a Warning Message so no action is needed.
CDA-01058,1, "%0!s: Trigger can only reference PL/SQL definition of type Trg-Logic."
Cause : A trigger can only reference a PL/SQL definition that as been
created with type value of Trg-Logic.
Action : Either choose to reference a PL/SQL definition of type Trg-Logic or
leave PL/SQL definition field blank and a new one will be created
automatically.
CDA-01059,0, "%0!s: A primary key constraint already exists for this table"
Cause : A table can have only one primary key constraint.
Action : Delete or update the existing primary key constraint, or add a
unique key constraint.
CDA-01061,0, "%0!s: Arc cannot be mandatory if an arc number is not specified"
Cause : It is not meaningful to specify that the constraint is in a
mandatory arc, if the arc number is not set.
Action : Specify the ARC_NUMBER or set the ARC_MANDATORY property to 'N'.
CDA-01062,0, "%0!s: Constraints implemented on the server cannot perform this deletion"
Cause : Constraints implemented on the server can either cascade on
delete or restrict delete.
Action : Specify either that the constraint is implemented on the client
only, or that deletes are either cascaded or restricted.
CDA-01063,0, "%0!s: Constraints implemented on the server cannot perform this update"
Cause : Constraints implemented on the server prohibit the update of the
source column. Any other action can be performed by client-side
code only.
Action : Specify either that the constraint is implemented on the client
only, or that updates are restricted.
CDA-01064,0, "%0!s: Only Tables, Views and Snapshots can be referenced"
Cause : Only Tables, Views and Snapshots can be referenced by the Foreign
Table reference.
Action : Ensure that any Foreign Key references are not made to objects
other than Tables, Views or Snapshots.
CDA-01068,0, "%0!s: A primary key and a unique key have been defined the same"
Cause : No unique constraint can have the same key components as the
primary key.
Action : Change the key components of one of the keys.
CDA-01071,0, "%0!s: Column must be in the same table as the constraint"
Cause : The specified Column does not exist in the same Table as the
constraint.
Action : Ensure that a Column usage is within the same Table as the
constraint usage.
CDA-01072,0, "%0!s: Null Columns in a mandatory Key"
Cause : Only mandatory (NOT NULL) Columns should appear in Unique
Constraints or Foreign Key Constraints, when MANDATORY_FLAG
= 'Y'.
Action : Make this Column mandatory or do not make it part of the
Primary Key for this Table.
CDA-01073,0, "%0!s: Join column (FOREIGN_COLUMN_REFERENCE) does not exist in the join table"
Cause : FOREIGN_COLUMN_REFERENCE must refer to a Column in the same Table
that the Constraint joins to.
Action : Choose a Column that is in the same Table that the Constraint
joins to.
CDA-01074,0, "%0!s: Join column is not part of the primary key"
Cause : The join column should be part of the primary key for its table.
Action : Modify the key for the join table, or choose another column.
CDA-01075,0, "%0!s: Column is defined as NOT NULL but appears in an arc"
Cause : Columns that appear in arcs should allow NULLs.
Action : Ensure the Mandatory property for this column is not checked
i.e. that it can contain a NULL value.
CDA-01076,0, "%0!s: Column is defined as NOT NULL but cascade rule nullifies"
Cause : The cascade delete or update rule for this constraint is to nullify
the foreign key, but this key contains a NOT NULL column.
Action : Change the key components or change the cascade delete or cascade
update rule.
CDA-01077,0, "%0!s: Column and join column do not have identical descriptions"
Cause : The Datatype, Average Length and Maximum Length of both the
parent column and the join column should be identical.
Action : Modify one or other of the column definitions, or document the
reason for the difference.
CDA-01078,0, "%0!s: A foreign column can be referred to only once per constraint"
Cause : Columns must be unique within a constraint.
Action : Remove the duplicate reference to the column.
CDA-01079,0, "Term exists as a synonym or entity, possibly in another application"
Cause : Terms must be unique. They must not duplicate any entity names
or synonyms that are visible from the context application system.
Action : Ensure that the term does not exist as a name or synonym for
another term or entity within the current or connected application
systems.
CDA-01080,0, "Reference already exists for this module"
Cause : A change history is uniquely identified by its module and change
reference number.
Action : Enter a different reference, or rename the existing change history
to have the same change reference.
CDA-01081,0, "%0!s: Previous change not transferred back to production directory"
Cause : A new change history cannot be entered until all previous change
histories are transferred back for use, e.g. Live or System Test.
Action : Ensure that all existing change history entries for this module
have 'date transferred' set.
CDA-01082,0, "%0!s: Module is not yet complete or passed testing"
Cause : A module should not be subject to change history until it is
complete.
Action : Set the 'module complete' flag.
CDA-01083,0, "%0!s: Super-module is used in another application"
Cause : The calling module is shared into another application system.
Action : This is a warning message and no action is required.
CDA-01085,1, "%0!s: Column usage is updateable but table usage is not updateable."
Cause : A Column of this Table has been set so that it can be updated
but the Table has not been set to allow updates and insertions.
Action : If the module can change the value of a column, update the module
table usage update flag or insert flag as appropriate.
CDA-01086,1, "%0!s: Column usage is nullable but table usage is not insertable/updateable"
Cause : The Column usage for a module has been set so that values can
be set to NULL but the Table usage that the Column is attached to
has not had its UPDATE_FLAG set to Yes.
Action : Either set the Column usage UPDATE_FLAG to N if you wish
no updating to be allowed or change the Table usage
UPDATE_FLAG to Y if you wish the column to be updated
to a NULL value.
CDA-01087,0, "%0!s: Column usage is selectable but table usage is not selectable"
Cause : A Column usage has been set so that values can be queried but
the Table usage to which it is attached has not been set for
queries.
Action : Either set the Table Usage to allow queries on the Column
or set the Column Usage to not allow queries (SELECT_FLAG
= 'N')
CDA-01089,0, "%0!s: Update flag conflicts with one or more foreign key constraints"
Cause : UPDATE_FLAG is 'Y' but the Column is in a non-transferable
Foreign Key Constraint.
Action : Set UPDATE_FLAG to 'N' or update the Foreign Key Constraint this
Column is in so that FK_TRANSFERABLE = 'Y'.
CDA-01090,0, "%0!s: Update flag conflicts with one or more primary key constraints"
Cause : The UPDATE_FLAG has been set for a primary key constraint;
Primary Keys must be NOT NULL and cannot be updated.
Action : Ensure the UPDATE_FLAG for columns that are Primary Keys is
set to No for updates allowed.
CDA-01091,0, "%0!s: Update flag conflicts with one or more unique key constraints"
Cause : The UPDATE_FLAG has been set to yes for one or more Unique Key
constraints; Unique Keys must be NOT NULL and unique and are
generally system generated. They cannot be updated.
Action : Ensure that the UPDATE_FLAG for columns that are Unique Keys
is set to No for updates allowed.
CDA-01099,1, "%0!s : Multiple inheritance of value types not permitted."
Cause : More than one generalization association has been made for
this value type. Value types can only inherit from a single other
value type.
Action : Ensure that this value type has only one generalization association
to another value type.
CDA-01100,0, "%0!s: May not set the primary Actor Usage to be non-primary"
Cause : Of the Actor Usages which refer to the same Activity Usage, one
and only one Actor Usage must have its PRIMARY_FLAG = 'Y'.
Action : If you wish to make another Actor Usage the primary for this
Activity Usage, set its PRIMARY_FLAG to 'Y' and CDAPI will set the
current PRIMARY_FLAG to 'N'.
CDA-01101,1, "A relationship with End Names %0!s and %1!s already exists between %2!s and %3!s"
Cause : A relationship with the same names between the same respective
entities has been detected.
Action : Rename one of the relationship ends to avoid the uniqueness
conflict.
CDA-01102,1, "%0!s: Entities %1!s and %2!s must both be connected to the context application system"
Cause : Each entity must either be shared or owned directly by the context
application system.
Action : Connect the entity in violation by sharing it with the context
application system.
CDA-01103,0, "Relation selection for %0!s: Cannot associate a view/snapshot with itself"
Cause : An association has been attempted between this view/snapshot
and itself. A view or snapshot cannot be based on itself.
Action : Ensure the View or Snapshot is based on another Table, View or
Snapshot.
CDA-01104,0, "%0!s: MTI_REFERENCE (Link To) must be defined for a non BASE Detailed Table Usage"
Cause : If USAGE_TYPE is neither 'BASE' nor null, then MTI_REFERENCE
(Link To) must be set.
Action : Set the MTI_REFERENCE (Link To) to the required
Detailed Table Usage, or set USAGE_TYPE to 'BASE' or null.
CDA-01105,0, "Unique identifier entry %0!s: Attribute Or Relation property must be either A[ttribute] or R[elationship End]"
Cause : The Attribute Or Relation property must be provided in order to
create a unique identifier entry.
Action : Provide a value of A or R.
CDA-01106,0, "Unique identifier entry: %0!s %1!s already exists in UID for entity %2!s"
Cause : A uniqueness constraint violation was detected that caused
processing of this unique identifier entry to halt. Continuation
would have led to a SQL unique index constraint violation.
Action : Since the element is already part of the unique identifier entry,
no action need be taken.
CDA-01107,1, "%0!s: No SHARE access privileges on application system that owns Common Function %1!s"
Cause : The specified common function is not owned by the context
application system, and the user does not have SHARE privileges on
the remote application system in order to share the common
function.
Action : Obtain SHARE privileges on the remote application system.
CDA-01108,1, "%0!s: Parent Function %1!s must be owned by context application system"
Cause : A function hierarchy must be contained within an application system.
Action : Specify a reference to a function that is owned by the context
application system.
CDA-01109,1, "%0!s: Cannot be both a Master function and a Copy function"
Cause : The specified function is both a Copy function (i.e. it refers to a
Common Function) and a Master function (i.e. other functions refer
to this function as a Common Function).
Action : Update the Copy functions to reference a different Master function,
or ensure that this function does not refer to a Common Function.
CDA-01110,1, "%0!s: A function cannot refer to the same function as both Master and Parent"
Cause : A Common Function that is a Child Function refers to its own Parent
as its Master Function.
Action : Update the function with references to a different Common Function
and/or a different Parent Function.
CDA-01111,1, "%0!s: A Function cannot be its own Parent"
Cause : A violation in the function hierarchy was detected.
Action : Update the function to refer to a different Parent.
CDA-01112,1, "%0!s: A function cannot be its own Common function"
Cause : A violation in the function hierarchy was detected.
Action : Update the function to refer to a different Common Function.
CDA-01113,1, "%0!s: Cannot be both a Parent Function and a Copy Function"
Cause : An attempt has been made either to make an existing Copy Function a
Parent Function, or to make an existing Parent Function a Copy
Function.
Action : Ensure consistent cross-referencing to avoid these violations to
the hierarchy. A Master Function can be a Parent Function.
CDA-01114,1, "%0!s: Master %1!s cannot be an ancestor of this function"
Cause : A violation in the function hierarchy was detected.
Action : Update the function to refer to a different Common Function.
CDA-01115,1, "%0!s: Parent %1!s is a descendant of this Function"
Cause : A violation in the function hierarchy was detected.
Action : Update the function to refer to a different Parent Function.
CDA-01124,1, "%0!s: Foreign Constraint and linked Table Usage must be to the same table"
Cause : If both MTI_REFERENCE and CONSTRAINT_REFERENCE are set
then EITHER:
TABLE_REFERENCE must equal
CONSTRAINT_REFERENCE.TABLE_REFERENCE
and MTI_REFERENCE.TABLE_REFERENCE must equal
CONSTRAINT_REFERENCE.FOREIGN_TABLE_REFERENCE
OR
TABLE_REFERENCE must equal
CONSTRAINT_REFERENCE.FOREIGN_TABLE_REFERENCE
and MTI_REFERENCE.TABLE_REFERENCE must equal
CONSTRAINT_REFERENCE.TABLE_REFERENCE
Action : Set CONSTRAINT_REFERENCE and MTI_REFERENCE so that the
above rules are fulfilled, or leave one of them null.
CDA-01126,1, "%0!s: The Foreign Constraint join is the wrong way round for a LOOKUP usage"
Cause : If USAGE_TYPE = LOOKUP and both MTI_REFERENCE and
CONSTRAINT_REFERENCE are set
then EITHER:
TABLE_REFERENCE must equal
CONSTRAINT_REFERENCE.FOREIGN_TABLE_REFERENCE
and MTI_REFERENCE.TABLE_REFERENCE must equal
CONSTRAINT_REFERENCE.TABLE_REFERENCE
OR
TABLE_REFERENCE must not equal
CONSTRAINT_REFERENCE.TABLE_REFERENCE
OR
MTI_REFERENCE.TABLE_REFERENCE must not equal
CONSTRAINT_REFERENCE.FOREIGN_TABLE_REFERENCE
Action : Set CONSTRAINT_REFERENCE and MTI_REFERENCE so that the
above rules are fulfilled, or leave one of them null,
or do not set USAGE_TYPE to LOOKUP.
CDA-01129,0, "%0!s: Cannot have an Outer Join on a SUBQRY foreign key link"
Cause : OUTER_JOIN_FLAG = 'Y' is not allowed if USAGE_TYPE is 'SUBQUERY'.
Action : Set USAGE_TYPE or OUTER_JOIN_FLAG to one of their other values.
See the API documentation for Module Detail Table Usages for
the effects of different values of USAGE_TYPE.
CDA-01134,0, "%0!s: Case-independent Name is not unique in module"
Cause : Program Data Name is not case-sensitive. Although it can be
expressed in mixed case, its uniqueness cannot depend on
case-sensitivity.
Action : Change the Name of the Program Data, or define it for a different
module.
CDA-01135,0, "%0!s: If VALUE_DATATYPE is null, VALUE_LENGTH and VALUE_SCALE must be null"
Cause : If VALUE_DATATYPE is not being set to describe the program datum,
then it is not valid to set VALUE_LENGTH or VALUE_SCALE.
Action : Either set VALUE_LENGTH and VALUE_SCALE to null, or
specify VALUE_DATATYPE (and set references to Domain, Oracle Type,
Datastructure and Column to null).
CDA-01136,1, "%0!s: Type not = EXCEPTION"
Cause : If the DATA_CONSTRUCT_TYPE is 'EXCEPTION', it is not valid to set
VALUE_DATATYPE or to refer to a Domain or to a Datastructure or to
an Oracle Type or to a Table or to a Column.
Action : Set DATA_CONSTRUCT_TYPE to another value, or set VALUE_DATATYPE and
references to Domain, Datastructure, Oracle Type, Column and Table
all to null.
CDA-01137,0, "%0!s: Type not = EXCEPTION"
Cause : If the DATA_CONSTRUCT_TYPE is not 'EXCEPTION', then you must
set VALUE_DATATYPE or a reference to a Domain, a Datastructure, a
Column, a Table or an Oracle Type.
Action : Set DATA_CONSTRUCT_TYPE to another value, or set VALUE_DATATYPE
or one of the references to Domain, Datastructure, Column, Table or
Oracle Type.
CDA-01138,0, "%0!s: No Datatype named %1!s exists"
Cause : This is a warning to draw your attention to the
fact that the Datatype specified is not one of the
standard ones.
Action : Warning, so action need not be taken.
CDA-01139,0, "%0!s: Scope can only be public for PL/SQL modules of Type PACKAGE"
Cause : It is not valid to create a Program Datum with Scope = 'PUBLIC'
when the context Module is not Module Type = 'PACKAGE', but it is
written in the Language 'PL/SQL'.
Action : Ensure that the Scope and Module Type values are consistent.
CDA-01151,1, "%0!s: Cannot set UPDATE_FLAG - the Column is in a non-updateable Constraint"
Cause : This column appears in a Constraint (Primary, Unique or Foreign)
that is either not updateable or not transferable, but this module
is attempting to update this column.
Action : Ensure the UPDATE_FLAG is not set for this Column usage or
it is not in a non-updateable Constraint.
CDA-01158,0, "%0!s: If Datatype is null, Length, Scale and Default Value must all be null"
Cause : If Datatype is not being set to describe the program datum, then it
is not valid to set Length, Scale or Default Value.
Action : Either set Length, Scale and Default Value to null or specify a
Datatype (and set references to Domain and Datastructure to null).
CDA-01159,0, "%0!s: Set either Datatype or a reference to Domain, Datastructure, Column, Table or Oracle Type"
Cause : Either a Datatype must be set, or a reference to Domain or to
Datastructure or to Column or to Table or to Oracle Type.
Action : Ensure that Datatype is set as a reference to Domain or to
Datastructure or to Column or to Table or to Oracle Type.
CDA-01160,1, "%0!s: Must link to a Usage that is within the same Module Component"
Cause : MTI_REFERENCE (Link To) must refer to a Module Detailed
Table Usage (MTI) that is within the same
Module Component as the current one.
Action : Leave MTI_REFERENCE (Link To) as null, or set it
to a Module Detail Table Usage which is within
the same Module Component as this one.
CDA-01163,0, "%0!s: Invalid Datastructure type (%1!s)"
Cause : An invalid type for this Datastructure has been chosen.
Action : For details of valid types for Datastructures see the Designer
Model documentation.
CDA-01164,0, "%0!s: Specified module is the wrong type"
Cause : This Datastructure has been defined against a module of the wrong
type. Datastructures can be used with modules of type PROCEDURE,
PACKAGE, FUNCTION or TRG-LOGIC only.
Action : Ensure that the Datastructure is assigned to the right PL/SQL
module. If it is, ensure that the TYPE property of the PL/SQL
module is valid.
CDA-01165,1, "%0!s: PL/SQL Tables can contain only one item"
Cause : A Datastructure Item already exists for this Datastructure. As this
Datastructure is of TYPE 'PL/SQL Table' further Datastructure Items
cannot be added.
Action : Ensure that the Datastructure that this Item is attached to
is set to the right TYPE. If this is PL/SQL Table then ensure
only one Datastructure Item exists.
CDA-01173,1, "%0!s: PLSQL_MODULE_REFERENCE must refer to either a PACKAGE or a PROCEDURE"
Cause : If PLSQL_MODULE_REFERENCE is set it must refer to
a PL/SQL Module which has PLSQL_MODULE_TYPE
= 'PACKAGE' or 'PROCEDURE'.
Action : Refer to a different PL/SQL Module, a different element
or change the PL/SQL Module to be a Package or Procedure.
CDA-01174,1, "%0!s: CURSOR_REFERENCE must refer to a PL/SQL Module of type CURSOR"
Cause : If CURSOR_REFERENCE is set it must refer to
a PL/SQL Module which has PLSQL_MODULE_TYPE
= 'CURSOR'.
Action : Refer to a different PL/SQL Module, a different element
or change the PL/SQL Module to be a Cursor.
CDA-01175,0, "%0!s: One and only one source of a datatype should be set"
Cause : The datatype is evaluated from one of many sources.
One of the following must be set: Datatype or references to Cursor,
Domain, Column, Datastructure2, Program Datum, Table Definition or
Oracle Type.
Action : Ensure that the Datatype has only one source.
CDA-01176,0, "%0!s: PL/SQL tables can contain only one item"
Cause : PL/SQL tables may have only one column. This datastructure
is of type 'TABLE' and has more than one datastructure item.
Action : Either do not attempt to place this Item on this
Datastructure, or delete the other Item first.
CDA-01178,0, "%0!s: Both Package and Cursor must be set to define a cursor"
Cause : In the Repository, a cursor can be defined in more than one package
or procedure via the module network. The pair need to be referenced
to resolve the cursor to be used.
Action : Ensure that both Package and Procedure are referenced.
CDA-01180,1, "%0!s: Datatype must be set if either LENGTH or DEFAULT_VALUE is set"
Cause : One or more of the properties LENGTH or DEFAULT_VALUE or
DECIMAL_PLACES has been set without a Datatype being referenced.
Action : If either LENGTH or DEFAULT_VALUE or DECIMAL_PLACES properties
are populated then DATATYPE property must be set.
CDA-01184,0, "%0!s: A business unit cannot be its own parent"
Cause : A violation in the business unit hierarchy was detected.
Action : Update the business unit to refer to a different Parent.
CDA-01185,0, "%0!s: Only set one of ITEM_REFERENCE, MODULE_ARGUMENT_REFERENCE, VALUE"
Cause : One and only one of the following properties must be set:
ITEM_REFERENCE, MODULE_ARGUMENT_REFERENCE, VALUE
Action : Set only one of these properties.
CDA-01186,0, "%0!s: CALLED_ARGUMENT_REFERENCE.MODULE_REFERENCE must equal MODULE_NETWORK_REFERENCE.CHILD_MODULE_REFERENCE"
Cause : The CALLED_ARGUMENT_REFERENCE must refer to a Module Argument
belonging to the called Module of the Module Network (as
identified by MODULE_NETWORK_REFERENCE.
Action : Either set CALLED_ARGUMENT_REFERENCE to refer to a different
Module Argument, or set MODULE_NETWORK_REFERENCE to refer to a
different Module Network, so that the values conform to the
above rule.
CDA-01187,0, "%0!s: The DATATYPE of the called Module Argument must match what is passed in"
Cause : The DATATYPE of the CALLED_ARGUMENT_REFERENCE must match the
DATATYPE of the ITEM_REFERENCE.DATATYPE or the
MODULE_ARGUMENT_REFERENCE.DATATYPE or the VALUE.
Note API cannot verify the datatype of VALUE.
Action : Alter the DATATYPE.
CDA-01188,0, "%0!s: Passed Values are valid for General Modules only."
Cause : The Passed Value must be passed via a Module Network such that
its CHILD_MODULE_REFERENCE and PARENT_MODULE_REFERENCE refer to
General Modules, not PL/SQL Modules or Java Modules.
Action : Set the MODULE_NETWORK_REFERENCE to a Module Network with its
CHILD_MODULE_REFERENCE and PARENT_MODULE_REFERENCE set to
General Modules.
CDA-01189,1, "%0!s: Cannot be the value for an Item in the context of a SQL Query Set"
Cause : If ITEM_REFERENCE is set then ITEM_REFERENCE.ITEM_FOR must equal
'MCO'.
Action : Set ITEM_REFERENCE to an Item within a Module Component.
CDA-01190,0, "%0!s: Item must belong to a Module Component that is included in the calling Module"
Cause : If ITEM_REFERENCE is set then the Item must belong to a Module
Component that is included in the calling Module in the Module
Network. (MODULE_NETWORK_REFERENCE.PARENT_MODULE_REFERENCE)
Action : Make the Passed Value refer to a different MODULE_NETWORK_REFERENCE
or a different ITEM_REFERENCE, MODULE_ARGUMENT_REFERENCE or VALUE.
CDA-01191,0, "%0!s: Cannot delete this Module Component Inclusion as %1!s depends on it"
Cause : This Module Component Inclusion cannot be deleted as it links
a Module Component which is the context of an Item with the
value passed via a Passed Value, and a Module that calls that
Passed Value.
Action : Delete the Passed Value by hand.
CDA-01192,0, "%0!s: The Module Argument must belong to the calling Module in the Module Network"
Cause : When the Passed Value is the value of a Module Argument it must be
within the calling Module, that is the parent Module of the
Module Network.
Action : Make the Passed Value refer to a different MODULE_NETWORK_REFERENCE
or a different ITEM_REFERENCE, MODULE_ARGUMENT_REFERENCE or VALUE.
CDA-01193,1, "%0!s: Parent reference cannot be same as child."
Cause : This object's parent value is referencing itself.
Action : Ensure that the parent field references another of this object
type or leave blank.
CDA-01194,1, "%0!s : Definition cannot be switched from object to relational and vice versa"
Cause : TABLE and VIEWS can be either object or relational. An object
TABLE or VIEW references an Oracle Object Type and this is set
in the Object Type property field or left blank when the TABLE
or view is relational. This is set on insertion of a new VIEW or
TABLE and cannot be updated.
Action : The reference to an Oracle Object Type cannot be updated.
If this has to be changed the TABLE or VIEW must be deleted
and recreated in the correct state.
CDA-01195,1, "%0!s : Object View or Table Definitions cannot have Columns."
Cause : A Column cannot be part of a View Definition or a Table
Definition that references an Oracle Object Type.
Action : Ensure that the Object View or Table does not have any Columns.
CDA-01196,1, "%0!s : When Unlimited flag is set Maximum extents must be null."
Cause : Caused when a value is attached to the max extents property
when unlimited? property is set to Yes.
Action : Leave max extents as null or change unlimited? to No.
CDA-01201,0, "%0!s: A Maximum Value must exist if the value for Cycle is 'Y' and the Increment Value positive"
Cause : If the CYCLE property in a Sequence Implementation is set to Y
and the INCREMENT value is positive then the MAXIMUM value
must also be set.
Action : Ensure that the MAXIMUM value is set.
CDA-01202,0, "%0!s: Increment Value cannot be zero"
Cause : INCREMENT property as been set to zero for this Sequence
Implementation.
Action : Set the INCREMENT property to a positive or negative number.
CDA-01203,0, "%0!s: Increment Value (%1!s) must not be greater than the sequence range"
Cause : The INCREMENT value exceeds the MAXIMUM value.
Action : Ensure that the INCREMENT value is a sensible level with regard
to the MAXIMUM set.
CDA-01204,0, "%0!s: When Cycle is 'Y', the Cache Value must not be more than one cycle"
Cause : If caching and cycling are used, CACHE must be less than
(CIEL(MAXVALUE - MINVALUE)) / ABS(INCREMENT).
See Oracle Server SQL Reference.
Action : Change the values of CACHE, CYCLE, MAXVALUE, MINVALUE
or INCREMENT so that the rule outlined in the CAUSE is obeyed.
CDA-01205,1, "%0!s: DEGREE (%1!s) must be null when PARALLEL is null"
Cause : If PARALLEL is not set, then DEGREE must not be set either.
Action : Set PARALLEL to a value or set DEGREE to null.
CDA-01206,0, "%0!s: Specified %1!s does not exist <%2!s>"
Cause : The reference property to the specified Type has been
populated with either the ID of an object of a different
Type, or a non-existent ID.
Action : Populate the specified reference property with an ID of
an element of the correct Type, or if it is an optional
property, set it to null.
CDA-01208,0, "%0!s: Reference to foreign table does not match reference to joined key table"
Cause : This foreign key constraint refers to a unique key or to a primary
key. The foreign table referred to in the foreign key constraint
must be the same as the table referred to in the unique or primary
key constraint.
Action : Ensure that the foreign table referred to in the foreign key
constraint is the same as the table referred to in the unique
or primary key constraint.
CDA-01209,0, "%0!s: Foreign key constraints in an arc must be optional"
Cause : The MANDATORY property for a foreign key that is part of
an arc has been set to Y. Foreign keys in Arcs must be
optional because they may reference another TABLE or another
foreign key in the arc may reference another TABLE.
Action : Ensure all foreign keys in an arc have MANDATORY set to N.
CDA-01210,0, "%0!s: BASE_COLUMN_REFERENCE must be null for a Table or Record Column"
Cause : BASE_COLUMN_REFERENCE has been set for a Table or Record.
Only Views and Snapshots can refer to a base column.
Action : Ensure that BASE_COLUMN_REFERENCE is null.
CDA-01211,0, "%0!s: PREFERENCE_NAME %1!s does not exist for PRODUCT_FLAVOR %2!s"
Cause : The combination of PREFERENCE_NAME and PRODUCT_FLAVOR must be
valid. The combination must be found in the system table
CDI_DFLT_USER_PREF_USAGES; columns DUP_SNAME and P_SNAME
respectively.
Action : Change the value of PREFERENCE_NAME or PRODUCT_FLAVOR.
CDA-01212,1, "%0!s Minimum Cardinality (%1!s) exceeds Maximum Cardinality (%2!s)"
Cause : The Minimum Cardinality exceeds the Maximum Cardinality.
Action : Change either the Maximum Cardinality or the Maximum Cardinality
of the Relationship end. A null value for Maximum Cardinality
means infinity.
CDA-01213,1, "%0!s: The properties All Databases and Database can't both be set"
Cause : A specific database has been defined as well as all databases.
This is not allowed.
Action : Specify either All Databases or a Database or neither.
CDA-01301,0, "%0!s: Property %1!s must not be NULL"
Cause : A violation of a property optionality constraint was detected.
Action : Provide a value for this property.
CDA-01302,0, "%0!s: Invalid value for property %1!s"
Cause : An invalid value was supplied for the specified property.
Action : Refer to the list of valid values for this property in the
documentation.
CDA-01304,0, "%0!s: Arc %1!s violation"
Cause : This element contains an arc on a set of relationships to other
elements. A value must be provided for only one of the relationships
in this arc, and either zero or more than one of these relationships
were set.
Action : Refer to the Element Type Definition documentation
for this element to determine which relationships
are part of the arc as identified by number in the
error message.
CDA-01305,0, "%0!s: UID %1!s uniqueness violation"
Cause : A uniqueness constraint violation was detected for this element.
Action : Refer to the documentation for the uniqueness constraint rules for
this element. The number after 'UID' refers to which uniqueness
constraint is violated if there are more than one.
CDA-01306,0, "%0!s: Mandatory Flag disallows a nullify action on update or delete"
Cause : Making a Foreign Key Constraint mandatory means that when the
'source' row is deleted or any of the columns' values are updated,
then the only valid cascade actions are to Cascade,
Restrict or Default.
Action : Make the Foreign Key Constraint optional or make both the
Cascade Delete and Cascade Update flags either 'C', 'R' or 'D'.
CDA-01307,0, "%0!s: Language name must be the same as the associated source file"
Cause : Class Code Locations and Class Set Code Locations are
located in Source Files. If the Source File has an
associated Language it must be the same as the
LANGUAGE_NAME property of the Class Code Location
and Class Set Code Location.
Action : Either change the associated Source File so that it has no
Language or make the Source File's Language the same as
the LANGUAGE_NAME in the associated Class Code Locations and
Class Set Code Locations.
CDA-01308,0, "%0!s: HASHKEYS must be an integer >= 2"
Cause : The property HASHKEYS must be an integer and its minimum
value is 2.
Action : Alter the value of HASHKEYS.
CDA-01309,0, "%0!s: Language_Name <%1!s> and Code_Section_Type <%2!s> not found in table cdi_code_section_types"
Cause : Each Class Code Location must refer to one and only one row in
the table cdi_code_section_types.
Action : The combination of properties Language_Name and Code_Section_Type
for this Class Code Location must match a combination of the
columns Language_Name and Type_Name in cdi_code_section_types.
CDA-01310,0, "%0!s: Language_Name <%1!s> and Class_Set_Code_Type <%2!s> not found in table cdi_class_set_code_types"
Cause : Each Class Set Code Location must refer to one and only one row in
the table cdi_class_set_code_types.
Action : The combination of properties Language_Name and Class_Set_Code_Type
for this Class Set Code Location must match a combination of the
columns Language_Name and Type_Name in cdi_class_set_code_types.
CDA-01311,0, "%0!s: Full Pathname <%1!s> clashes with <%2!s> in <%3!s>"
Cause : The FULL_PATHNAME of a file must be unique across all types of file
(Database, Record and Source), which are shared into the context
application system.
Action : Set the FULL_PATHNAME to a unique value or to null.
CDA-01312,0, "%0!s: Class Code Location must mirror an existing Set Member Item"
Cause : The values of the properties SOURCE_FILE_REFERENCE and
GENERATOR_CLASS_SET_REFERENCE should be the same as an instance
of a Set Member Item's ELEMENT_REFERENCE and
USER_DEFINED_SET_REFERENCE.
Action : Either insert a Set Member Item with the appropriate values
or select different values for the Class Code Location.
CDA-01313,0, "%0!s: Class Set Code Location must mirror an existing Set Member Item"
Cause : The values of the properties SOURCE_FILE_REFERENCE and
GENERATOR_CLASS_SET_REFERENCE should be the same as an instance
of a Set Member Item's ELEMENT_REFERENCE and
USER_DEFINED_SET_REFERENCE.
Action : Either insert a Set Member Item with the appropriate values
or select different values for the Class Set Code Location.
CDA-01314,0, "%0!s: Cannot associate %1!s with more than one Generator Class Set"
Cause : A Source File may only be associated with one and
only one Generator Class Set.
Action : Remove the association between this Source File and Generator
Class Set before creating the new association.
CDA-01315,1, "%0!s: Module of PLSQL_MODULE_TYPE %1!s cannot have a return type."
Cause : Only modules of type FUNCTION and CURSOR can have a return type.
Action : Set return type to null for this plsql_module_type.
CDA-01316,1, "%0!s: Cache value cannot be 1"
Cause : Valid CACHE VALUES for a SEQUENCE are null, 0 or >= 2. On
generation a NULL value will result in the target database's default
(often 20); a value of 0 will result in the NOCACHE option being
set.
Action : Change the CACHE VALUE to null, 0 or >= 2.
CDA-01317,1, "%0!s: Default value must be entered if null values are not permitted"
Cause : Default value must be entered if Optional? is set to False.
Action : Enter default value
CDA-01318,1, " %0!s: ALIAS %1!s already exists."
Cause : The ALIAS already exists for a Table, View or Snapshot in the
current Container.
Action : Choose another value for ALIAS.
CDA-01319,0, "%0!s: Cannot grant Reference privilege on table to a Role."
Cause : REFERENCE_FLAG may only be 'Y' for a Table when the
grant is made to a User, not a Role.
Action : Set REFERENCE_FLAG to 'N' or grant to a User, or
grant to another Object Implementation, e.g. a View.
CDA-01320,0, "%0!s: Select at least one privilege."
Cause : At least one privilege must be selected for the object.
Action : Set at least one privilege to 'Y'.
CDA-01321,0, "%0!s: Function Entity Usages cannot be created for a copy function."
Cause : Copy (Slave) Functions may not be modified so
Function Entity Usages cannot be created.
Action : Add the Function Entity Usages to the Master Function.
CDA-01322,0, "%0!s: A PUBLIC Role cannot be a %1!s."
Cause : A PUBLIC Role cannot be specified for a Child or Parent Role
reference.
Action : Specify another Role as Child or Parent Role.
CDA-01323,1, "%0!s: %1!s already exists for %2!s database."
Cause : Roles and User NAMEs must be unique within the Database.
Action : Choose another NAME for this Role or Group.
CDA-01324,0, "%0!s: Cannot update or delete a PUBLIC Role."
Cause : A PUBLIC Role cannot be updated or deleted.
Action : Delete the database to delete PUBLIC Role.
CDA-01325,1, "%0!s: A generateable language %1!s cannot be deleted."
Cause : Languages with GENERATABLE_FLAG = 'Y' may not be deleted.
Action : Do not attempt to delete this Language.
CDA-01326,0, "%0!s: The associated Module Detail Table Usage does not exist for the Column %1!s"
Cause : A Detail Table Usage does not exist for the Table to which the
Column belongs.
Action : Create a Detail Table Usage for the Table to which the Column
belongs.
CDA-01327,0, "%0!s: Module of PLSQL_MODULE_TYPE %1!s must have a return type"
Cause : FUNCTIONs must have a return type
Action : Set a valid return type
CDA-01328,1, "%0!s: The NAME or LANGUAGE_TYPE for generateable languages cannot be changed"
Cause : NAME or LANGUAGE_TYPE of a Language that can be
generated from Designer cannot be updated.
Action : Do not attempt to update the NAME or LANGUAGE_TYPE
of this Language.
CDA-01329,0, "%0!s: Primary Key Constraint cannot be defined on an optional Column %1!s."
Cause : Only mandatory (NOT NULL) Columns are valid in a Primary Key.
Action : Make this Column mandatory or do not make it part of the
Primary Key for this Table.
CDA-01330,1, "%0!s: Cannot define an Index for a Hash Cluster."
Cause : Hash Clusters (CLUSTER_TYPE = 'HCL')
may not have Cluster Indexes.
Action : Change the Cluster's CLUSTER_TYPE or do not
attempt to associate a Cluster Index with this Cluster.
CDA-01331,0, " %0!s: Property HASHKEYS and HASH_IS cannot be defined for index cluster."
Cause : Property HASHKEYS and HASH_IS should be null for index cluster.
Action : Set HASHKEYS and HASH_IS to null.
CDA-01332,0, "%0!s: Table Partitions are only valid for Oracle8 databases"
Cause : Table Partitions may only be associated with Table Implementations
which are in the schema of a Database User on an Oracle Database
with DB_VERSION = 8.
Action : Set the owning Database to version 8.
CDA-01333,0, "%0!s: A Break Group may not have a Parent Group"
Cause : An Item Group with BREAK_GROUP_FLAG = 'Y' may not have
ITEM_GROUP_REFERENCE set.
Action : Don't make this Item Group a Break Group, or do not give it a
parent Item Group.
CDA-01334,0, "%0!s: A Chart Group may not have a Parent Group"
Cause : An Item Group with CHART_CATEGORY set may not have
ITEM_GROUP_REFERENCE set.
Action : Don't make this Item Group a Chart Group, or do not give it a
parent Item Group.
CDA-01335,0, "%0!s: Local Index Partitions must be for LOCAL Index Storage"
Cause : The Local Index Partition must be a partition of an
Index Storage element with INDEX_STORAGE_TYPE = 'LOCAL'
Action : Set the INDEX_STORAGE_TYPE to 'LOCAL' or associate a
Global Index Partition to the Index Storage element.
CDA-01336,0, "%0!s: Global Index Partitions must be for GLOBAL Index Storage"
Cause : The Global Index Partition must be a partition of an
Index Storage element with INDEX_STORAGE_TYPE = 'GLOBAL'
Action : Set the INDEX_STORAGE_TYPE to 'GLOBAL' or associate a
Local Index Partition to the Index Storage element.
CDA-01337,0, "%0!s: Partition Key Entries must be for GLOBAL Index Storage"
Cause : The Partition Key Entry must be in the partition key of
an Index Storage element with INDEX_STORAGE_TYPE = 'GLOBAL'
Action : Set the INDEX_STORAGE_TYPE to 'GLOBAL'
CDA-01338,0, "%0!s: RELATION_SELECTION_REFERENCE must be null for a Table or Record"
Cause : Only Columns for Views and Snapshots can refer to a Relation
Selection.
Action : Leave the property null. Choose a Column of a View or Snapshot.
CDA-01339,0, "%0!s: DATATYPE, MAXIMUM_LENGTH and DECIMAL_PLACES must match the Cluster Column's"
Cause : If CLUSTER_COLUMN_REFERENCE is set, then the Column's DATATYPE,
PRECISION and SCALE must match the Cluster Column's.
MAXIMUM_LENGTH and DECIMAL_PLACES must match the Cluster
Column's DATATYPE, LENGTH and SCALE.
Action : Alter the Column's DATATYPE, MAXIMUM_LENGTH or DECIMAL_PLACES or set
CLUSTER_COLUMN_REFERENCE to null.
CDA-01340,0, "%0!s: Module Component FLAGs should not be set when the BASE Usage FLAGs are not set"
Cause : If this Data Bound Item is for a BASE Module Detail Table Usage
then the SELECT_FLAG or the UPDATE_FLAG should not be set to 'Y'
if the associated Module Component's SELECT_FLAG or UPDATE_FLAG
are set to 'N'.
Action : Update the SELECT_FLAG or UPDATE_FLAG or the associated
Module Component's SELECT_FLAG or UPDATE_FLAG. This is only a
identical.
Warning so action need not be taken.
CDA-01341,0, "%0!s: Module Component must not be MODULE_LEVEL"
Cause : The associated Module Component must have its MODULE_LEVEL_FLAG
set to 'N'.
Action : Associate this Module Detail Table Usage with another Module
Component or set the MODULE_LEVEL_FLAG to 'N'.
CDA-01342,0, "%0!s: The Database User and the Role must be in the same Database"
Cause : In order for a Role to be granted to a User, they
both must be in the same Database.
Action : Associate the User with a different Role which is in the same
Database as the User.
CDA-01343,0, "%0!s: Cannot grant the PUBLIC role to a User"
Cause : The PUBLIC Role is not a real Role and cannot be granted to a
User.
Action : Grant a different Role to this User.
CDA-01344,0, "%0!s: %1!s is in %2!s but the Object is in %3!s"
Cause : The User or Role which is being granted privileges is in a
different database than the User which owns the Database Object.
Action : Grant privileges to a User or Role in the Database that
contains the User which owns the Database Object
(or in the case of Directory, grant privileges to a User or Role
in the Database which owns the Directory).
CDA-01345,0, "%0!s: Cannot delete -- Module Program Data exist which refer to Program Data owned by this Module"
Cause : The specified element could not be deleted because it owns
Program Data which is referenced by another Module, i.e. a
Module Program Datum links Program Data owned by this Module
to another Module.
Action : Ensure that all Program Data owned by this Module is
not referenced by any other Module.
CDA-01346,0, "%0!s: A General Module may not have language PL/SQL"
Cause : There are two types of Module: PL/SQL Module, which has an
implied Language of PL/SQL, and has all the associations and
properties particular to PL/SQL Modules; and General Modules
for all other Languages.
Action : Give the General Module a different Language or create a
PL/SQL Module.
CDA-01347,0, "%0!s: May not grant from a PUBLIC Role to another Role"
Cause : When creating a Role Grant, GRANTOR_ROLE_REFERENCE
may not refer to the Role with NAME = 'PUBLIC'.
Action : Refer to a different Role.
CDA-01348,0, "%0!s: Uniqueness conflict with %1!s"
Cause : See the documentation for the Uniqueness Constraint of
this element type. There are a number of element types which
share this namespace.
Action : Choose another NAME for this object.
CDA-01349,0, "%0!s: Uniqueness conflict with %1!s"
Cause : See the documentation for the Uniqueness Constraint of
this element type. There are a number of element types which
share this namespace.
Action : Choose a different associated element.
CDA-01350,0, "%0!s: Module Component Inclusion references must be different"
Cause : MCN_REFERENCE_FROM must not equal MCN_REFERENCE_TO.
Action : Refer to different Module Component Inclusions.
CDA-01351,0, "%0!s: Associated Module Detail Table Usages must not be within SQL Query Sets"
Cause : The Module Detail Table Usages referenced by
TABLE_USAGE_REFERENCE_TO and TABLE_USAGE_REFERENCE_FROM must
both be directly within Module Components, not SQL Query Sets.
Action : Associate the Key Based Link with Module Detail Table Usages
which are within Module Components.
CDA-01352,0, "%0!s: Module Component From Detail Table Usage must match From Module Component Inclusion"
Cause : TABLE_USAGE_REFERENCE_FROM.MODULE_COMPONENT_REFERENCE must equal
MCN_REFERENCE_FROM.MODULE_COMPONENT_REFERENCE.
Action : Make sure the 'from' Module Detail Table Usage and the 'from'
Module Component Inclusion are for the same Module Component.
CDA-01353,0, "%0!s: Module Component To Detail Table Usage must match To Module Component Inclusion"
Cause : TABLE_USAGE_REFERENCE_TO.MODULE_COMPONENT_REFERENCE must equal
MCN_REFERENCE_TO.MODULE_COMPONENT_REFERENCE.
Action : Make sure the 'to' Module Detail Table Usage and the 'to'
Module Component Inclusion are for the same Module Component.
CDA-01354,0, "%0!s: Foreign Key Constraint must be based on the same Table as the 'From' or 'To' Module Detail Table Usage"
Cause : If the Key Based Link is based on a Foreign Key Constraint, then
FOREIGN_KEY_REFERENCE.TABLE_REFERENCE must equal
TABLE_USAGE_REFERENCE_FROM.TABLE_REFERENCE or
TABLE_USAGE_REFERENCE_TO.TABLE_REFERENCE.
Action : Associate the Key Based Link with a different Foreign Key
Constraint or a different Module Detail Table Usage.
CDA-01355,0, "%0!s: Foreign Key Constraint must refer to the same Table as the 'From' or 'To' Module Detail Table Usage"
Cause : If the Key Based Link is based on a Foreign Key Constraint, then
FOREIGN_KEY_REFERENCE.FOREIGN_TABLE_REFERENCE must equal
TABLE_USAGE_REFERENCE_TO.TABLE_REFERENCE or
TABLE_USAGE_REFERENCE_FROM.TABLE_REFERENCE.
Action : Associate the Key Based Link with a different Foreign Key
Constraint or a different Module Detail Table Usage.
CDA-01356,0, "%0!s: Primary Key Constraint must be for the same Table as the 'From' and 'To' Module Detail Table Usage"
Cause : If the Key Based Link is based on a Primary Key Constraint, then
PRIMARY_KEY_REFERENCE.TABLE_REFERENCE must equal
TABLE_USAGE_REFERENCE_FROM.TABLE_REFERENCE and
TABLE_USAGE_REFERENCE_TO.TABLE_REFERENCE.
Action : Associate the Key Based Link with a different Primary Key
Constraint or a different Module Detail Table Usage.
CDA-01357,0, "%0!s: Unable to create unique Name for Type %1!s. Base Name = %2!s"
Cause : The simple algorithm used to create unique Names has failed. It
acts by adding a number to the end of the Name until it is
unique or grows to be longer than the property maximum length.
Action : Choose a shorter or maybe completely different Name.
CDA-01358,0, "%0!s: No other Module Component Inclusion may have the same MODULE_COMPONENT_REFERENCE"
Cause : If MODULE_COMPONENT_REFERENCE.MODULE_COMPONENT_TYPE = 'SPECIFIC'
then no more other Module Component may have the same
MODULE_COMPONENT_REFERENCE.
Action : Refer to another Module Component.
CDA-01359,0, "%0!s: Cannot delete if Module Component is MODULE_LEVEL"
Cause : A Module Component or Module Component Inclusion cannot be deleted
if MODULE_LEVEL_FLAG = 'Y'.
GENERAL_MODULE_REFERENCE.LANGUAGE_REFERENCE
'SupportsModuleLevelComponent'.
Action : Delete the General Module directly.
CDA-01360,0, "%0!s: Shared COMMON Module Components cannot become SPECIFIC"
Cause : This Module Component is shared into another Application System.
Action : Unshare this Module Component before making it SPECIFIC.
CDA-01361,0, "%0!s: REUSABLE Module Components must be included in only one Module before becoming SPECIFIC"
Cause : Before changing a Module Component from REUSABLE to SPECIFIC it
must be included in at most one General Module via
a Module Component Inclusion.
Action : Delete Module Component Inclusions that associate this REUSABLE
Module Component with General Modules.
CDA-01362,0, "%0!s: MODULE_LEVEL Module Components must be in a valid Language"
Cause : If MODULE_LEVEL_FLAG = 'Y' then LANGUAGE_REFERENCE must refer to
a Language with the property 'SupportsModuleLevelComponent'.
Action : Refer to another Language or set MODULE_LEVEL_FLAG to 'N'
CDA-01363,0, "%0!s: This MODULE_LEVEL Module Component is in the same Module as %1!s"
Cause : If MODULE_LEVEL_FLAG = 'Y' GENERAL_MODULE_REFERENCE must be unique
There is a maximum
of one MODULE_LEVEL Module Component per General Module. Another
Module Component with MODULE_LEVEL_FLAG = 'Y' already exists.
Action : Set the MODULE_LEVEL_FLAG to 'N', associate this Component with
another Module, or modify the existing Module Level Component
for this Module.
CDA-01364,0, "%0!s: Only SPECIFIC Module Components may be MODULE_LEVEL"
Cause : If MODULE_LEVEL_FLAG = 'Y' then MODULE_COMPONENT_TYPE
must be 'SPECIFIC'.
Action : Set MODULE_LEVEL_FLAG to 'N' or MODULE_COMPONENT_TYPE to
'REUSABLE'.
CDA-01365,0, "%0!s: REUSABLE Module Components must not set GENERAL_MODULE_REFERENCE"
Cause : If MODULE_COMPONENT_TYPE = 'REUSABLE' then GENERAL_MODULE_REFERENCE
must be null.
Action : Set GENERAL_MODULE_REFERENCE to null or set MODULE_COMPONENT_TYPE to
'SPECIFIC', but not both.
CDA-01366,0, "%0!s: SPECIFIC Module Components must set GENERAL_MODULE_REFERENCE"
Cause : If MODULE_COMPONENT_TYPE = 'SPECIFIC' then
GENERAL_MODULE_REFERENCE must not be null.
Action : Set MODULE_COMPONENT_TYPE to 'REUSABLE' or set
GENERAL_MODULE_REFERENCE but not both.
CDA-01367,0, "%0!s: Language must not be 'PL/SQL'"
Cause : Module Components are only included in General Modules, not
PL/SQL Modules.
Action : Put the Module Component in another Language.
CDA-01368,0, "%0!s: Cannot be included in a Module without a Language"
Cause : Module Components can only be associated to Modules with a
specified Language, i.e. GENERAL_MODULE_REFERENCE.LANGUAGE_REFERENCE
must not be null.
Action : Associate this Module Component with a General Module which has a
specified Language.
CDA-01369,0, "%0!s: MTI_REFERENCE (Link To) must not be defined for a BASE Detailed Table Usage"
Cause : If USAGE_TYPE is either 'BASE' or null, then MTI_REFERENCE
(Link To) must be null.
Action : Set the MTI_REFERENCE (Link To) to null or set USAGE_TYPE to
another value.
CDA-01370,0, "%0!s: Upper limit Column (FOREIGN_COLUMN_REFERENCE2) does not exist in the join Table"
Cause : FOREIGN_COLUMN_REFERENCE2 must refer to a Column in the same Table
that the Constraint joins to.
Action : Choose a Column that is in the same Table that the Constraint
joins to.
CDA-01371,0, "%0!s: Module Component Inclusion or Window must belong to the General Module"
Cause : If GENERAL_MODULE_REFERENCE is set then
MCN_REFERENCE.GENERAL_MODULE_REFERENCE or
WINDOW_REFERENCE.GENERAL_MODULE_REFERENCE must equal
GENERAL_MODULE_REFERENCE.
Action : Assign the Navigation Action Item to a different General Module
or a different Window or Module Component Inclusion.
CDA-01372,1, "%0!s: Only valid in Oracle Databases above version 6"
Cause : A PL/SQL Mod Implementation must be in the schema of a
Database User on an Oracle Database and the DB_VERSION
must be greater than 6, i.e.
DATABASE_USER_REFERENCE.DATABASE_REFERENCE.DATABASE_TYPE =
'ORC' and
DATABASE_USER_REFERENCE.DATABASE_REFERENCE.DB_VERSION > 6.
Action : Associate this PL/SQL Mod Implementation with another Database User
or associate the Database User with an Oracle Database V7 or
above.
CDA-01373,0, "%0!s: %1!s already refers to %2!s"
Cause : Each Foreign Key Constraint may have one and only one Relation
Index. That is there may be no other Relation Indexes with the
same FOREIGN_KEY_REFERENCE.
Action : Set FOREIGN_KEY_REFERENCE to null or refer to another
Foreign Key Constraint.
CDA-01374,0, "%0!s: Snapshot Refresh Group is in %1!s but Snapshot is in %2!s"
Cause : If the Snapshot Implementation is a member in a Snapshot Refresh
Group, then the Database User which is the schema for the Snapshot
Implementation must be in the same Database as the Snapshot
Refresh Group, i.e. SNAPSHOT_GROUP_REFERENCE.ORACLE_DATABASE_
_REFERENCE must equal DATABASE_USER_REFERENCE.DATABASE_REFERENCE.
Action : Don't put the Snapshot Implementation in a Snapshot Refresh Group,
put it in another Snapshot Refresh Group, or put it in a different
Database User.
CDA-01375,0, "%0!s: Snapshot is Simple and %1!s is based on more than one Table"
Cause : FAST Snapshots may only be based on one Table. It is not
permitted to set a Snapshot Implementation's REFRESH_TYPE
to 'FAST' if it is based on a Snapshot Definition that is
derived from more than one Table. Similarly it is not permitted
to make a Snapshot Definition to be derived from more than one
Table if even one of its Implementations has REFRESH_TYPE = 'FAST'.
FAST or Updateable Snapshots must be Simple; that is
they may be based on only one Table.
It is not permitted to set a Snapshot Implementation's
REFRESH_TYPE to 'FAST' or a Snapshot Definition's UPDATABLE_FLAG
to 'Y' if the Snapshot Definition is derived from
more than one Table. Similarly it is not permitted
to derive a Snapshot Definition from more than one
Table if it has UPDATABLE_FLAG = 'Y' or even one of its
Implementations has REFRESH_TYPE = 'FAST'.
Action : Set the Snapshot Implementation's REFRESH_TYPE to a value
other than 'FAST', or set the Snapshot Definition's UPDATABLE_FLAG
to 'N'.
CDA-01376,0, "%0!s: Snapshot is Simple and %1!s is not based on a Table."
Cause : FAST Snapshots may only be based on one Table (not Views or other
Snapshots). It is not permitted to set a Snapshot Implementation's
REFRESH_TYPE to 'FAST' if it is based on a
Snapshot Definition that is derived from a View, Snapshot or
Record. Similarly it is not permitted
to make a Snapshot Definition to be derived from a View, Snapshot
or Record if even one of its Implementations
has REFRESH_TYPE = 'FAST'.
FAST or Updateable Snapshots must be Simple; that is
they may only be based on one Table (not Views or other
Snapshots). It is not permitted to set a Snapshot Implementation's
REFRESH_TYPE to 'FAST' or a Snapshot Definition's UPDATABLE_FLAG
to 'Y' if the Snapshot Definition is derived from a View, Snapshot
or Record. Similarly it is not permitted to derive a Snapshot
Definition from a View, Snapshot or Record if
it has UPDATABLE_FLAG = 'Y' or even one of its Implementations has
REFRESH_TYPE = 'FAST'.
Action : Set the Snapshot Implementation's REFRESH_TYPE to a value other
than 'FAST', or set the Snapshot Definition's UPDATABLE_FLAG to
'N'.
CDA-01377,0, "%0!s: Only Views and Snapshots can be derived from Relation Selections"
Cause : Record and Table Definitions may not be derived from
Relation Selections. Only View and Snapshot Definitions may be
derived, i.e. VIEW_REFERENCE.TABLE_TYPE must be in ('SNP','VW').
Action : Refer VIEW_REFERENCE to a Snapshot or View.
CDA-01378,0, "%0!s: Cannot be based on a MODULE_LEVEL Module Component"
Cause : A SQL Query Set must not be in a set operation with a Module
Component that has MODULE_LEVEL_FLAG = 'Y'.
Action : Associate the SQL Query Set with another Module Component.
CDA-01379,0, "%0!s: Cannot be based on a Module Component with DATASOURCE_TYPE = 'TABLE'"
Cause : A SQL Query Set must not be in a set operation with a Module
Component that has DATASOURCE_TYPE = 'TABLE'.
Action : Associate the SQL Query Set with another Module Component or
set the DATASOURCE_TYPE to another value.
CDA-01381,0, "%0!s: Column must be within referenced Table"
Cause : If COLUMN_REFERENCE is set then COLUMN_REFERENCE.TABLE_REFERENCE
must equal TABLE_REFERENCE.
Action : Choose a Column in the referenced Table
CDA-01382,0, "%0!s: Replication Group is in a different Database to the Database User"
Cause : If the View or Table Implementation is in a Replication Group then
it must be in the same Database as the Database User, i.e.
REPLICATION_GROUP_REFERENCE.DATABASE_REFERENCE must equal
DATABASE_USER_REFERENCE.DATABASE_REFERENCE.
Action : Either leave the REPLICATION_GROUP_REFERENCE null, or refer to a
different Replication Group or Database User.
CDA-01383,0, "%0!s: Tablespace is in a different Database to the Database User"
Cause : The Tablespace must be part of the same Database that owns the
Database User, i.e.
DATABASE_USER_REFERENCE.DATABASE_REFERENCE must equal
TABLESPACE_REFERENCE.DATABASE_REFERENCE.
Action : Choose a different Database User or Tablespace.
CDA-01384,0, "%0!s: MODULE_LEVEL Module Components may not be of TYPE 'SQL EXPRESSION' or 'SQL AGGREGATE'"
Cause : If MODULE_COMPONENT_REFERENCE.MODULE_LEVEL_FLAG = 'Y' then
UNBOUND_TYPE must not be in ('SQL EXPRESSION','SQL AGGREGATE').
Action : Set UNBOUND_TYPE to a different value or put the Unbound Item in
a non-MODULE_LEVEL Module Component.
CDA-01385,0, "%0!s: Insert and Update not permitted for non-CUSTOM Unbound Items"
Cause : If UNBOUND_TYPE != 'CUSTOM' then INSERT_FLAG must be 'N' and
UPDATE_FLAG must be 'N'.
Action : Set UNBOUND_TYPE to another value or set INSERT_FLAG and
UPDATE_FLAG to 'Y'.
CDA-01386,0, "%0!s: Can only set RELATION_SELECTION_REFERENCE if BASE_COLUMN_REFERENCE is set"
Cause : BASE_COLUMN_REFERENCE must be set before
RELATION_SELECTION_REFERENCE may be set.
RELATION_SELECTION_REFERENCE need only be set if
the View or Snapshot is based on one table twice)
Action : Either leave RELATION_SELECTION_REFERENCE as null or
set BASE_COLUMN_REFERENCENCE.
CDA-01389,0, "%0!s: Window must be in same General Module as Module Component Inclusion"
Cause : If WINDOW_REFERENCE is set then
WINDOW_REFERENCE.GENERAL_MODULE_REFERENCE
must equal GENERAL_MODULE_REFERENCE.
Action : Either do not set WINDOW_REFERENCE, or set it to the ID of a
Window in the same General Module as this
Module Component Inclusion.
CDA-01390,0, "%0!s: Module Network must be both from and to a General Module"
Cause : If a Navigation Action Item is for navigation to a Module Network,
then both the PARENT_MODULE_REFERENCE and the CHILD_MODULE_REFERENCE
must refer to General Modules, not PL/SQL Modules.
Action : Either refer to a different Module Network, or update this
Module Network so that conforms to the above rule.
CDA-01391,0, "%0!s: A Primary Unique Identifier already exists for this Entity"
Cause : Only one Unique Identifier for each Entity may have
PRIMARY_UID_FLAG set to 'Y'.
Action : Set PRIMARY_UID_FLAG to 'N' for this or all other Unique Identifiers
for this Entity.
CDA-01392,0, "%0!s: The Role or User must be in the same Database as the Database Object"
Cause : (ROLE_REFERENCE or DATABASE_USER_REFERENCE).DATABASE_REFERENCE
must equal (PLSQL_MODULE_REFERENCE, SEQUENCE_REFERENCE,
SNAPSHOT_REFERENCE, TABLE_REFERENCE or
VIEW_REFERENCE).DATABASE_USER_REFERENCE.DATABASE_REFERENCE
Action : Select another Role or User, or another Database Object.
CDA-01393,0, "%0!s: Cannot update or delete built in Value Types"
Cause : A number of Value Types are classed as 'built in' (property
DATATYPE is set) and these may not be updated or deleted.
Action : Do not update or delete built in Value Types.
CDA-01394,1, "%0!s: It is not possible to recursively generalize or specialize"
Cause : Generalization Associations may not set the SUPERTYPE_REFERENCE
to the same Type as the SUBTYPE_REFERENCE.
Action : Set the SUPERTYPE_REFERNCE and the SUBTYPE_REFERENCE to
different values.
CDA-01395,1, "%0!s: May not generalize or specialize different Types"
Cause : The two Abstract Types involved in a Generalization Association
must either both be Value Types or both be Object Types,
but not a mixture of the two.
Action : Set different values for SUPERTYPE_REFERENCE and SUBTYPE_REFERENCE.
CDA-01396,0, "%0!s: '%1!s..%2!s' is not a valid permutation"
Cause : The full list of valid permutations of MINIMUM_CARDINALITY and
MAXIMUM_CARDINALITY is:
0..1, 0..n, 0..*, 1..1, 1..n, 1..*, n..n, n..*
Action : Set MINIMUM_CARDINALITY and MAXIMUM_CARDINALITY so that the
above rule holds.
CDA-01397,0, "%0!s: Only one role in a pair can have AGGREGATION != \"NONE\""
Cause : At least one of the ends of the Association Role pair must have
AGGREGATION = 'NONE'.
Action : Set AGGREGATION = 'NONE' for one of the ends of the
Association.
CDA-01398,0, "%0!s: %1!s and %2!s : A Type Operation may not be part of an Arc Constraint"
Cause : Only Type Attributes and Association Roles may be part of an
Arc Constraint.
Action : Either refer to a Uniqueness Constraint or an Other Constraint,
alternatively refer to a Type Attribute or an Association Role.
CDA-01399,0, "%0!s: VERB_NAME cannot be set at both ends of a pair of Association Roles"
Cause : VERB_NAME may only be set on one end of an Association Role pair.
Action : Set VERB_NAME to null on one Association Role.
CDA-01400,0, "%0!s: If ORDERED_SET_FLAG is 'Y', then MAXIMUM_CARDINALITY must be > 1"
Cause : ORDERED_SET_FLAG may only be set at the 'many' end of an
Association Role.
Action : Set ORDERED_SET_FLAG to 'N', or MAXIMUM_CARDINALITY to a value
greater than 1, or '*'(null).
CDA-01401,0, "%0!s: If ABSTRACT_TYPE_REFERENCE ('return_type') is set, then RETURN_VALUE_FLAG must = 'Y'"
Cause : While RETURN_VALUE_FLAG may be set if ABSTRACT_TYPE_REFERENCE
is not set (indicating that this Operation will return a value
that is unspecified as yet), once a return_type is specified
RETURN_VALUE_FLAG must be set to 'Y'.
Action : Set RETURN_VALUE_FLAG to 'Y', or set ABSTRACT_TYPE_REFERENCE
to null.
CDA-01402,0, "%0!s: Either VALUE or IDENTIFIER (or both) must be set"
Cause : Both VALUE or IDENTIFIER may be set, but one MUST be set.
Action : Set either VALUE or IDENTIFIER or both.
CDA-01403,0, "%0!s: If HIGH_VALUE is set, VALUE must be set"
Cause : VALUE must be set if HIGH_VALUE is set.
Action : Either leave HIGH_VALUE null, or set VALUE.
CDA-01404,0, "%0!s: SOURCE_LEVEL and TARGET_LEVEL must be different"
Cause : The Transformation must be between different levels.
Action : Set SOURCE_LEVEL and TARGET_LEVEL to different values.
CDA-01405,0, "%0!s: If DEFAULT_VALUE is set then OVERRIDE_DEFAULT_FLAG must be set to 'Y'"
Cause : Setting DEFAULT_VALUE overrides any inherited value, so must be set
Action : Set OVERRIDE_DEFAULT_FLAG to 'Y'.
CDA-01406,1, "%0!s: SCOPE_TABLE_REFERENCE may only be set if OBJECT_TYPE_INCLUSION = 'REF'"
Cause : A column can only be scoped by a table if the
OBJECT_TYPE_INCLUSION property is set to 'REF' ('Reference').
Action : Leave SCOPE_TABLE_REFERENCE as null, or set OBJECT_TYPE_INCLUSION
to 'REF'.
CDA-01407,1, "%0!s: Object Columns must have OBJECT_TYPE_INCLUSION set"
Cause : OBJECT_TYPE_INCLUSION must be set for Object Columns. Object
Columns have ORACLE_TYPE_REFERENCE set.
Action : Set OBJECT_TYPE_INCLUSION, or leave ORACLE_TYPE_REFERENCE null.
CDA-01408,0, "%0!s: Object Columns may not have DATATYPE, MAXIMUM_LENGTH or DECIMAL_PLACES set"
Cause : This Column has ORACLE_TYPE_REFERENCE set and
therefore must not set DATATYPE, MAXIMUM_LENGTH and
DECIMAL_PLACES.
Action : Set DATATYPE, MAXIMUM_LENGTH and DECIMAL_PLACES all to null.
CDA-01409,0, "%0!s: Object Columns must not be in Records"
Cause : This Column has ORACLE_TYPE_REFERENCE set and therefore may
not be a component in a Record.
Action : Set ORACLE_TYPE_REFERENCE to null, or place it in a Table,
Snapshot or View.
CDA-01411,0, "%0!s: Scalar Columns must not have OBJECT_TYPE_INCLUSION set"
Cause : This Column has ORACLE_TYPE_REFERENCE set to null and
therefore must not have OBJECT_TYPE_INCLUSION set.
Action : Set OBJECT_TYPE_INCLUSION to null.
CDA-01412,0, "%0!s: Scalar Columns must not have OBJECT_TYPE_INCLUSION set"
Cause : This Column has COLUMN_OR_ATTRIBUTE_TYPE = 'SCALAR' and
therefore must not have OBJECT_TYPE_INCLUSION set.
Action : Set OBJECT_TYPE_INCLUSION to null.
CDA-01414,0, "%0!s: CACHE_FLAG and LOGGING_FLAG may not both be set to 'Y'"
Cause : Either CACHE_FLAG or LOGGING_FLAG or neither may be set, but not
both.
Action : Set either CACHE_FLAG or LOGGING_FLAG or make them both null.
CDA-01415,0, "%0!s: Column must be SCALAR"
Cause : The discriminator Column must have ORACLE_TYPE_REFERENCE
set to null.
Action : Remove this Column as a discriminator Column.
CDA-01416,0, "%0!s: CLUSTER_REFERENCE may not be set for Implicit Index Storages"
Cause : Implicit Index Storage may not be set for a
Cluster Implementation.
Action : Use this Implicit Index Storage for a Snapshot
or a Table.
CDA-01417,0, "%0!s: RETURN_TYPE and ORACLE_TYPE_REFERENCE may not both be set"
Cause : Only one of these two properties may be set.
Action : Set either RETURN_TYPE or ORACLE_TYPE_REFERENCE (or neither).
CDA-01418,1, "%0!s: SCALAR... and OBJECT... properties are mutually exclusive"
Cause : If COLLECTION_OF = 'SCALAR' then SCALAR_DATATYPE must be set
(plus SCALAR_MAXIMUM_LENGTH and SCALAR_DECIMAL_PLACES
if appropriate) while ORACLE_OBJECT_TYPE_REFERENCE must not
be set.
If COLLECTION_OF = 'OBJECT' then SCALAR_DATATYPE must be null
while ORACLE_OBJECT_TYPE_REFERENCE must be set.
Action : Set the properties so the rules outlined in the Cause are met.
CDA-01419,1, "%0!s: VARRAY COLLECTION_TYPES only must set VARRAY_LIMIT"
Cause : VARRAY_LIMIT must be set if COLLECTION_TYPE = 'VARRAY'.
VARRAY_LIMIT must not be set if COLLECTION_TYPE = 'NESTED TABLE'.
Action : Either leave VARRAY_LIMIT null and set COLLECTION_TYPE =
'NESTED TABLE' or set VARRAY_LIMIT and set COLLECTION_TYPE =
'VARRAY'.
CDA-01420,0, "%0!s: TYPE BODY Modules must have ORACLE_OBJECT_TYPE_REFERENCE set, and no other PL/SQL Modules may"
Cause : ORACLE_OBJECT_TYPE_REFERENCE must be set if
PLSQL_MODULE_TYPE is 'TYPE BODY'.
ORACLE_OBJECT_TYPE_REFERENCE must not be set if
PLSQL_MODULE_TYPE is not 'TYPE BODY'.
Action : Either set PLSQL_MODULE_TYPE to 'TYPE BODY' and
set ORACLE_OBJECT_TYPE_REFERENCE; or set PLSQL_MODULE_TYPE
to another value, and leave ORACLE_OBJECT_TYPE_REFERENCE null.
CDA-01421,0, "%0!s: May not make a Valid Value for a System Value Type"
Cause : Some of the basic Value Types are created automatically and
may not have any Valid Values set for them. They all have
SYSTEM_ELEMENT_FLAG set to 'Y'.
Action : Do not associate a Valid Value with this Value Type.
CDA-01422,0, "%0!s: An Item Group may not refer to itself"
Cause : ITEM_GROUP_REFERENCE may not refer to itself.
Action : Set ITEM_GROUP_REFERENCE to null or to refer to another Item Group.
CDA-01423,1, "%0!s: A Module Detail Table Usage may not refer to itself."
Cause : MTI_REFERENCE may not refer to itself.
Action : Set MTI_REFERENCE to null or to another Module Detail Table Usage.
CDA-01424,1, "%0!s: Cannot update system organization unit."
Cause : The system organization unit is provided in the default
workarea and folder, and cannot be modified.
Action : Do not attempt to update this organization unit.
CDA-01425,1, "%0!s: Cannot delete system organization unit."
Cause : The system organization unit is provided in the default
workarea and folder, and cannot be deleted.
Action : Do not attempt to delete this organization unit.
CDA-01426,1, "%0!s: ORGANIZATION_UNIT_REFERENCE must be set."
Cause : All organization units must have this property
ORGANIZATION_UNIT_REFERENCE set to
their parent organization unit. Only the system
organization unit has no parent.
Action : Set ORGANIZATION_UNIT_REFERENCE to the parent
organization unit.
CDA-01427,1, "%0!s: Cannot delete organization units with children."
Cause : Other organization units make reference to this
organization unit via ORGANIZATION_UNIT_REFERENCE.
Action : Delete the child organization units before deleting
this one, or use the 'Force Delete' command.
CDA-01428,1, "%0!s : loop detected involving %1!s."
Cause : This transition has resulted in a loop involving the
specified element, i.e. it is possible to trace a series of
transitions so the element is its own source or target.
Action : Change the source or target properties of this transition so that
a loop does not occur.
CDA-01429,1, "%0!s : %1!s is FINAL and cannot be the source of a transition"
Cause : Pseudostates of TYPE 'FINAL' cannot be referred to by the
SOURCE_PSEUDOSTATE_REFERENCE property of a transition.
Action : Either set the Pseudostate's TYPE to another value or choose a
different element to be the source of this transition.
CDA-01430,1, "%0!s : %1!s is INITIAL and cannot be the target of a transition."
Cause : Pseudostates of TYPE 'INITIAL' cannot be referred to by the
SOURCE_PSEUDOSTATE_REFERENCE property of a transition.
Action : Either set the Pseudostate's TYPE to another value or choose a
different element to be the target of this transition.
CDA-01431,1, "%0!s : Source %1!s may not have OBJECT_STATE_REFERENCE set."
Cause : Event Classifiers which have their OBJECT_STATE_REFERENCE
property set may not be the source or target of a
Transition.
Action : Change the Transition so that SOURCE_EVENT_REFERENCE refers to
a valid element, or update the source Event Classifier's
OBJECT_STATE_REFERENCE property to null.
CDA-01432,0, "%0!s : Target %1!s may not have OBJECT_STATE_REFERENCE set"
Cause : Event Classifiers which have their OBJECT_STATE_REFERENCE
property set may not be the target or target of a
Transition.
Action : Change the Transition so that TARGET_EVENT_REFERENCE refers to
a valid element, or update the target Event Classifier's
OBJECT_STATE_REFERENCE property to null.
CDA-01433,1, "%0!s : Invalid transition between source %1!s and target %2!s."
Cause : The source and target elements specified may not be joined
by a transition even if there are intermediate pseudostates.
Action : See the documentation for the transition element type for
details of valid and invalid source and target element types.
Change the transition so that its source elements and its
target elements comply (even via pseudostates).
CDA-01434,1, "%0!s : %1!s is the target of %2!s transitions so cannot be source to more than one transition"
Cause : A pseudostate cannot be the source of many transitions
and the target of many transitions. This pseudostate is
the target of multiple transitions already, therefore it
cannot be the source of a second transition.
Action : Either remove some of the transitions going
to the pseudostate so it is the target of
only one, or change this transition so its
source is another element, or add a new,
intermediate, pseudostate.
CDA-01435,1, "%0!s : %1!s is the source of %2!s transitions so cannot be target to more than one transition"
Cause : A pseudostate cannot be the target of many transitions
and the source of many transitions. This pseudostate is
the source of multiple transitions already and therefore
cannot be the target of a second transition.
Action : Either remove some of the transitions going from the
pseudostate so it is the source of only one, or change
this transition so its target is another element, or
add a new, intermediate, pseudostate.
CDA-01436,1, "%0!s : Source and Target are for %1!s."
Cause : A Transition cannot form a 'pig's ear' on a Pseudostate,
i.e. a Transition cannot be the source and target of the same
Pseudostate.
Action : Set SOURCE_PSEUDOSTATE_REFERENCE or TARGET_PSEUDOSTATE_REFERENCE
to different values.
CDA-01438,0, "%0!s: Cannot have more than two View Link End Usages in %1!s"
Cause : Each View Link Usage may have a maximum of two View Link End Usages.
The View Link Usage referred to by this View Link End Usage already
has two.
Action : Associate this View Link End Usage with another View Link Usage
or delete an existing View Link End Usage from this
View Link Usage.
CDA-01439,1, "Table with refrential integrity constraints cannot be made Global temporary."
Cause : The Global Temporary flag has been set to a value other than
"PERMANENT" for a table containing Foreign keys.
Action : Change the value of the Global Temporary flag to "PERMANENT" or
remove the Foreign Keys from the table.
/
/ 02000 .. 02999 Constraint violations
/
CDA-02000,1, "%0!s: Uniqueness conflict in %1!s with %2!s."
Cause : A uniqueness violation was detected. An element already exists in
the specified container with the same identifying
properties. Typically this will be NAME, but check with the CDAPI
documentation for the specified element type for more details.
SHORT_NAME, ALIAS and PLURAL_NAME may be identifying properties.
Action : Rename the element in violation, or otherwise change its identifying
properties so that it avoids the uniqueness conflict.
CDA-02001,1, "%0!s: %1!s conflicts with another synonym in %2!s."
Cause : A synonym by this name already exists in the specified application
system.
Action : Change the property of the entity for which the synonym is being
created (i.e., Name, Short Name or Plural) to avoid the uniqueness
conflict.
CDA-02002,1, "%0!s: Invalid value <%1!s> for property %2!s."
Cause : An invalid value was supplied for the specified property.
Action : Refer to the documentation for a list of valid values for this
property.
CDA-02003,1, "%0!s: Property %1!s (%2!s) may not be negative"
Cause : An attempt was made to enter a negative value into this property.
Action : Enter a non-negative value.
CDA-02004,0, "%0!s: Invalid Datatype value (%1!s)"
Cause : An invalid Datatype was supplied.
Action : Refer to the list of valid values specified for this property in
the documentation.
CDA-02005,0, "%0!s: Value for property %1!s (%2!s) is not in the recommended list"
Cause : The recommended list contains the frequently used values
for this property.
Action : Warning only. No action need be taken. The recommended list
can be found in the documentation.
CDA-02006,0, "%0!s: Invalid Unit Of Frequency value (%1!s)"
Cause : An invalid Unit Of Frequency was supplied.
Action : Refer to the list of valid values specified for this property in
the documentation.
CDA-02007,0, "%0!s: Invalid Frequency Unit value (%1!s)"
Cause : An invalid Frequency Unit was supplied.
Action : Refer to the list of valid values specified for this property in
the documentation.
CDA-02008,1, "%0!s: LANGUAGE must not be NULL as Module Components exist in this Module"
Cause : Module Components can only be associated to Modules with a
specified Language.
i.e. GENERAL_MODULE_REFERENCE.LANGUAGE_REFERENCE
must not be NULL.
Action : Give this Module a Language.
CDA-02009,0, "%0!s: Invalid Response Needed value (%1!s)"
Cause : An invalid Response Needed value was supplied.
Action : Refer to the list of valid values specified for this property in
the documentation.
CDA-02010,1, "%0!s: Invalid response required value (%1!s)."
Cause : An invalid response required was supplied.
Action : Refer to the documentation for a list
of valid values for this property.
CDA-02011,1, "%0!s: Modules with Language = Common Library must have GENERAL_MODULE_TYPE = LIBRARY"
Cause : Either GENERAL_MODULE_TYPE was set to a type other than LIBRARY when
the LANGUAGE was set to Common Library, or LANGUAGE was set
to Common Library when GENERAL_MODULE_TYPE was not set to LIBRARY.
Action : Either set GENERAL_MODULE_TYPE to LIBRARY if the LANGUAGE is set to
Common Library, or set LANGUAGE to a Language other than
Common Library if the GENERAL_MODULE_TYPE is not LIBRARY.
CDA-02012,0, "%0!s: Invalid Time value (%1!s)"
Cause : An invalid Time was supplied.
Action : Refer to the list of valid values specified for this property in
the documentation.
CDA-02013,0, "%0!s: Invalid Attribute Precision value (%1!s)"
Cause : An invalid Attribute Precision was supplied.
Action : Refer to the list of valid values specified for this property in
the documentation.
CDA-02014,0, "%0!s: Invalid Datastore Type (%1!s)"
Cause : An invalid Datastore Type was supplied.
Action : Refer to the list of valid values specified for this property in
the documentation.
CDA-02015,1, "%0!s: Columns in Views may not be clustered"
Cause : A View Column was added to a Cluster Column.
Action : Remove the View Column from the Cluster Column.
CDA-02016,1, "%0!s: Check Constraints in Views can only have Validate In = CLIENT"
Cause : The Validate In (IMPLEMENTATION_LEVEL) property was set to
a value other than CLIENT.
Action : Set the Validate In (IMPLEMENTATION_LEVEL) property to
CLIENT for the View. Or place a similar Check Constraint
against the base Table.
CDA-02017,1, "%0!s: Cannot create Unique Key for index only Table"
Cause : Attempting to attach a unique key constraint to an index only table.
Action : Ensure the index only table does not have a unique key attached.
Alternatively set the INDEX_ONLY_FLAG on the table to 'N'.
CDA-02018,1, "%0!s: Can't set NULLIFY_FLAG when the Column is in a Primary Key Constraint."
Cause : Attempting to set NULLIFY_FLAG for Column in Primary Key Constraint.
Action : Ensure the NULLIFY_FLAG is not set for a Column in a
Primary Key Constraint when the Module Detail Table Usage is 'BASE'.
CDA-02019,1, "Event Classifier Name %0!s cannot be updated. "
Cause : An attempt was made to update the name of this Event Classifier
where the object state reference is set.
Event classifiers which have been generated as a result of an
object state cannot have their name updated.
Action : Repeat the operation without attempting to update
the name of the Event Classifier.
CDA-02020,0, "%0!s: Uniqueness conflict with %1!s in %2!s"
Cause : See the Uniqueness Constraint for this element in the user
documentation.
Action : Rename the new element or modify the new associations such that
the documented uniqueness constraint is not violated.
CDA-02021,1, "%0!s: Activity implemented by Method Rule Usage must reference same Rule."
Cause : Method Rule Usages of call type PRE-CONDITION :
If the method, which is the subject of the method rule usage,
implements an activity then that activity's
precondition rule must be the same rule as that being used
to create the method rule usage.
Method Rule Usages of call type POST-CONDITION :
If the method, which is the subject of the method rule usage,
implements an activity then that activity's
postcondition rule must be the same rule as that being used
to create the method rule usage.
Action : Method Rule Usages of call type PRE-CONDITION :
Ensure the activity's pre-condition rule is the same rule
for which the method rule usage is being created.
Method Rule Usages of call type POST-CONDITION :
Ensure the activity's post-condition rule is the same rule
for which the method rule usage is being created.
CDA-02022,0, "%0!s: Either source or destination must be a function"
Cause : A dataflow must connect a function to another element.
Action : Provide a reference to a function for either the source or the
destination.
CDA-02023,0, "%0!s: The source object must not be the same as the destination object"
Cause : The elements at each end of a dataflow must be different.
Action : Update the dataflow, specifying distinct source and destination
elements.
CDA-02024,0, "%0!s: Source Function %1!s and destination Function %2!s do not share the same parent"
Cause : If both the source and the destination of the dataflow are
functions, then they must both be either root functions or children
the same parent.
Action : Update the dataflow to refer to source and destination functions
that are both either root functions or sibling functions.
CDA-02025,0, "%0!s: Multiple indexes map to %1!s within context %2!s"
Cause : Each Cluster may have only one Index and this Cluster
already has one.
Action : Do not attempt to add extra Indexes to this Cluster.
CDA-02026,1, "Method Rule Usage of call type %0!s already exists for this method %1!s"
Cause : There can only be one method rule usage with call type
set to pre-condition for each method referenced in a
method rule usage.
There can only be one method rule usage with call type
set to post-condition for each method referenced in a
method rule usage.
Action : Correct the data by specifying either a different call type or
a different method for this method rule usage.
CDA-02027,1, "%0!s: Activity level cannot be updated"
Cause : You cannot update the level of an activity if :-
The activity is a parent activity in an activity decomposition
OR
The activity is a child activity in an activity decomposition
and the parent activity has a level of SYSTEM
OR
The activity is a child activity in an activity decomposition
and it has siblings, i.e. there exist other activity
decompositions with the same parent as this child activity.
Action : Either:-
Remove any activity decompositions which are
causing this update to fail and repeat the operation.
Or
Do not attempt to update the level property of this activity.
CDA-02028,0, "%0!s: Source function %1!s must not be a Copy function"
Cause : Functions contained in dataflows must not be Copy functions (i.e.
they must not refer to a Common function).
Action : Either update the specified source function to remove the reference
to the Common function, or update the dataflow to refer to a
different source function.
CDA-02029,0, "%0!s: Destination function %1!s must not be a Copy function"
Cause : Functions contained in dataflows must not be copy functions (i.e.
they must not refer to a Common function).
Action : Either update the specified destination function to remove the
reference to a Common function, or update the dataflow to refer to
a different destination function.
CDA-02030,0, "%0!s: Source %1!s must be connected to the context application system"
Cause : Both the source and the destination elements of a dataflow must be
connected to the context application system.
Action : Connect the specified source element to the context application
system.
CDA-02031,0, "%0!s: Destination %1!s must be connected to the context application system"
Cause : Both the source and the destination elements of a dataflow must be
connected to the context application system.
Action : Connect the specified destination element to the context application
system.
CDA-02032,1, "%0!s: Parent and child activity references must not be the same."
Cause : An ACTIVITY_DECOMP cannot refer to a single ACTIVITY_DEFINITION
by both PARENT_ACTIVITY_REFERENCE and CHILD_ACTIVITY_REFERENCE.
Action : Ensure that the PARENT_ACTIVITY_REFERENCE and the
CHILD_ACTIVITY_REFERENCE for this ACTIVITY_USAGE refer
to different ACTIVITY_DEFINITIONS.
CDA-02033,1, "%0!s: ORACLE6 databases may not have snapshots, PL/SQL Modules or Cursors"
Cause : Version 6 ORACLE databases may not have associated Snapshots
or PL/SQL Modules of type Package, Procedure, or Cursor.
Action : Change the DB_VERSION of the Oracle Database.
CDA-02034,1, "%0!s: May not be its own parent"
Cause : An Activity_Usage may not refer to itself with
Activity_Usage_Reference
Action : Ensure that Activity_Usage_Reference for this
Activity_Usage does not reference itself or is set
to null.
CDA-02035,0, "%0!s: Uniqueness conflict with %1!s in %2!s"
Cause : See the Uniqueness Constraint for this element in the user
documentation.
Action : Rename the new element or modify the new associations such that
the documented uniqueness constraint is not violated.
CDA-02036,1, "%0!s: The primary file: %1!s must be a BLOB."
Cause : The primary file referenced by the Icon_File_Reference value
for this classifier must have a property of 'BLOB' for its
KIND column.
Action : Make sure that the referenced icon file has a KIND
value of 'BLOB'.
CDA-02037,1, "%0!s: Generate flag cannot be set to 'Y' when analysis flag is 'Y'."
Cause : The Generate_Class_Flag for this association has been set to 'Y'
when the Analysis_Type_Flag is set to 'Y'.
Action : Change the settings of the Generate_Class_Flag and/or the
Analysis_Type_Flag so that they are not both set to 'Y'.
CDA-02038,1, "%0!s: An association must have at least two association ends."
Cause : A reference to an association has been updated or deleted such
that there will be less than two association ends referring to that
association, or an association has been created with
less than two association ends referring to it.
Action : Ensure that there are at least two association ends that
refer to this association.
CDA-02039,1, "%0!s: An association with an association classifier must be analysis only."
Cause : An association which references either an entity object
or a generic class currently has its ANALYSIS_TYPE_FLAG set to 'N'.
Action : Either change the ANALYSIS_TYPE_FLAG for this association
to 'Y' or remove the references to the classifier (either
entity object or generic class).
CDA-02040,1, "%0!s: An n-array association must be set to analysis only."
Cause : The ANALYSIS_TYPE_FLAG is set to 'N' on an association that
has more than two association ends.
Action : Change the ANALYSIS_TYPE_FLAG on the association to 'Y'.
CDA-02041,1, "%0!s: A many to many association must be set to analysis only."
Cause : The ANALYSIS_TYPE_FLAG for a many to many association is set to 'N'.
The many to many relationship is indicated by the two ends of the
binary association having MAXIMUM_MULTIPLICITY values other than
0 or 1.
Action : Set the ANALYSIS_FLAG for this association to 'Y'.
CDA-02042,0, "%0!s: Sequences cannot have Insert, Update, Delete, Index or Reference privileges"
Cause : Only Select, Grant and Alter (and All) privileges can be granted for
Sequences.
Action : Do not set any other FLAGs to 'Y'.
CDA-02043,0, "%0!s: Snapshots cannot have Insert, Update, Delete, Index, Alter or Reference privileges"
Cause : Only Select and Grant (and All) privileges can be granted for
Snapshots.
Action : Do not set any other FLAGs to 'Y'.
CDA-02044,0, "%0!s: Views cannot have Index, Alter or Reference privileges"
Cause : Only Select, Insert, Update, Delete and Grant (and All) privileges
can be granted for Views.
Action : Do not set any other FLAGs to 'Y'.
CDA-02045,1, "%0!s: %1!s is only valid when persistent flag is set."
Cause : Either DEFAULT_COLUMN_DATATYPE or
DEFAULT_COLUMN_NAME has been set when the
object is not persistent.
Action : Make sure the persistent flag is set to 'N' or that the
values for those properties are set to NULL.
CDA-02046,1, "%0!s: Persistent entity object attribute has no valid classifier reference."
Cause : A persistent Entity Object Attribute does not have a
reference to either a primitive Generic Class or an
Attribute Domain.
Action : Either set the PERSISTENT_FLAG for this element to 'N' or
make sure this element refers to a primitive Generic Class
or an Attribute Domain via the CLASSIFIER_REFERENCE property.
CDA-02047,0, "User-Defined Set is Locked or Checked Out"
Cause : The User Defined Set referred to is either Checked Out or Locked.
.
Action : Unlock or Check In the User Defined Set before performing any
operations on it.
CDA-02048,1, "No access rights for this operation"
Cause : The user does not have the necessary privileges
on either the source or target application system
to permit this operation.
Action : Refer to the on-line help for details of the required
privileges for the operation being attempted.
Ask the application owner to grant the necessary
privileges then repeat the operation.
CDA-02049,0, "Unable to unlock the Set; it is locked by another user"
Cause : An attempt was made to unlock a user
defined set which was locked by a different
user.
Action : Check that the correct user defined set was specified.
It is not possible to unlock a set locked by another user.
The other user must release the lock before this operation
can be performed.
CDA-02050,0, "Set is not locked"
Cause : An attempt was made to unlock a user defined
set which is not locked. This may have happened during
a check in operation.
Action : Check that the correct user defined set has been specified.
If this is the result of a check in operation ensure that the
target is a locked checked out source set. If necessary, relock the
source set and then repeat the operation.
CDA-02051,0, "Set members are locked by another set"
Cause : An attempt was made to lock a user defined set
containing elements already locked in a different set.
An object may exist in many user defined sets but it
can only be locked in one of these sets.
Action : Check that the set members are not already contained
in another locked user defined set. It will be necessary to
unlock these sets before this operation can be completed
successfully. It is not advisable to manually unlock a user defined
set marked as checked out. The set should be checked
back in which will automatically release the lock.
CDA-02052,0, "Unable to delete a locked Set; unlock the Set before deletion"
Cause : A locked set may not be deleted.
Action : Unlock the set before attempting to delete it.
CDA-02053,1, "%0!s: FILE_SCOPE must equal 'MAIN'."
Cause : The FILE_SCOPE value for this Entity or View Object is set to
a value other than 'MAIN'.
Action : Set the FILE_SCOPE value to 'MAIN'.
CDA-02054,0, "Created from Database Trigger - %0!s"
Cause : Information Only
Action : Information Only
CDA-02055,0, "%0!s: The application system referred to is not the context application system"
Cause : For PUBLIC system privileges, there must be a reference to the
context application system.
Action : Transfer the system privilege to another application system or
change the context application system to the one that owns this
system privilege.
CDA-02056,1, "%0!s: Cannot be persistent if the owning entity object is not persistent."
Cause : The PERSISTENT_FLAG property for this entity
object attribute is not set to 'N' when its owning
entity object's PERSISTENT_FLAG is set to 'N'.
Action : Set the PERSISTENT_FLAG for this entity object attribute to 'N'.
CDA-02057,0, "%0!s: Index and foreign key constraint must be for the same Relation Definition"
Cause : The table referred to by this Index is not the same as the table
referred to on the foreign key constraint that is referred to as
the foreign key for the Index.
Action : Update the reference to the foreign key. (The other properties are
not updateable.)
CDA-02058,0, "%0!s: Database Type is 'ORACLE', but it is defined in an ANSI Database"
Cause : The Table or View has a Database Type of 'ORACLE', but it is
associated with an ANSI Database.
Action : Either change the Database Type to 'ANSI' or 'ANY', or set the
reference to null or the ID of an Oracle Database.
CDA-02059,1, "%0!s: A frozen attribute cannot be updateable."
Cause : An attribute must have its UPDATEABLE_FLAG set to
'N' if its CHANGE_RESTRICTION property is set
to 'FROZEN'.
Action : Set the UPDATEABLE_FLAG to 'N'.
CDA-02060,0, "%0!s: These cannot be defined against a version 6 ORACLE Database"
Cause : Version 6 of the ORACLE database does not support
Datastructure Items. This Datastructure Item is for a
Table Definition which is in turn implemented on a version 6 oracle
database.
Action : Associate this Datastructure Item with another Table (or none at
all), or change the Database that the Table is implemented upon.
CDA-02061,1, "%0!s: Persistent Entity Object Attrs cannot have Attribute Derivation Rules."
Cause : If the Persistent Flag is set to 'Y' then there can be no
Attribute Derivation Rules that reference this element.
Action : Set the Persistent Flag to 'N' or remove any
Attribute Derivation Rule references or elements.
CDA-02062,1, "%0!s: %1!s only valid when pseudo column flag is not set."
Cause : Either the DEFAULT_COLUMN_DATATYPE or the
DEFAULT_Db_OBJECT_NAME have been set when the
Pseudo Column Flag is set to 'N'.
Action : Make sure the DEFAULT_COLUMN_DATATYPE and
DEFAULT_Db_OBJECT_NAME are set to Null otherwise set
the pseudo column flag to 'Y'.
CDA-02063,0, "%0!s: Parent %1!s is a descendent of this %0!s"
Cause : The parent is also a descendent of this element. This is not
allowed in this hierarchy.
Action : Change the parent so that it is not a sibling of the current
element.
CDA-02064,0, "%0!s: Sequence Number for Snapshot and View columns is mandatory and must be unique"
Cause : Columns in Views and Snapshots must have the Sequence Number set.
This number must be unique for all columns in this View or
Snapshot.
Action : Specify a unique Sequence Number
CDA-02065,0, "A %0!s may only be modified via the diagrammers"
Cause : Update, Insert and Delete operations on Diagrams, Diagram Segments,
and Diagram Element Usages
may only be performed by diagrammers and not via the API.
Action : Do not attempt this action using the API - use one of the
diagrammers.
CDA-02066,0, "%0!s: %1!s cannot be a parent Application System as it is not empty"
Cause : Application Systems may become parents only when they do not
own or share any Elements (except Languages).
Action : Either choose another Application System to be the parent, or
delete any owned Elements and disconnect any shared Elements.
CDA-02067,0, "%0!s: %1!s cannot be a parent Application System as it has a parent itself"
Cause : Only one level of Application System hierarchy is permitted.
Action : Either choose another empty Application System to be the parent,
or nullify the Parent Reference of the intended parent
Application System.
CDA-02068,0, "%0!s: Cannot have a parent Application System as it is a parent itself"
Cause : Only one level of Application System hierarchy is permitted.
Action : Nullify the Parent Reference of the child Application Systems
CDA-02069,0, "%0!s: %1!s is in %2!s, but %3!s is in %4!s"
Cause : When a Column appears in an Index, it must be defined against the
same Table as the Index.
Action : Choose another Column or another Index.
CDA-02070,0, "%0!s: Uniqueness conflict with %1!s"
Cause : NAME (case sensitive) must be unique across all Type Attributes
and Type Operations in the same Object Type.
Action : Give the Type Attribute a NAME which does not clash.
CDA-02071,0, "%0!s: Uniqueness conflict with %1!s"
Cause : NAME (case sensitive) must be unique across all Type Attributes
in the same Object Type.
Action : Give the Type Operation a NAME which does not clash.
CDA-02072,0, "%0!s: Uniqueness conflict with %1!s"
Cause : Valid Values must have a unique SEQUENCE_NUMBER, IDENTIFIER
and VALUE within Value Type. Nulls are permitted.
Action : Set the Valid Value's SEQUENCE_NUMBER, IDENTIFIER and VALUE
so that they do not clash with the referenced Valid Value.
CDA-02073,1, "%0!s: An entity object mapped to a column cannot have pseudo flag set."
Cause : The Pseudo_Column_Flag is set to 'Y' when a mapping
exists between this entity object and a column.
Action :
CDA-02074,1, "%0!s: Cannot reference itself as a CLASSIFIER_REFERENCE"
Cause : The CLASSIFIER_REFERENCE for this element has been set to
the IRID of itself.
Action : Change the value of the CLASSIFIER_REFERENCE property so
that it does not equal the IRID of this element.
CDA-02075,1, "%0!s: The main Classifier for a file cannot reference a Primary Class"
Cause : If the File Scope property for this Classifier is set to 'Main'
then the Primary Class reference for this element must
be NULL.
Action : If the File Scope is set to 'Main' then make sure the
Primary Class property is NULL.
CDA-02076,1, "%0!s: Interface cannot be used by an interface."
Cause : An interface usage cannot link two INTERFACE_CLASSIFIERS.
Action : Make sure that the classifier referenced by the
CLASSIFIER_REFERENCE property of this INTERFACE_USAGE
element is not an INTERFACE_CLASSIFIER element.
CDA-02077,1, "%0!s: A method cannot be both static and overridable."
Cause : The combination of property values STATIC_FLAG = 'Y'
and OVERRIDABLE = 'MUST' is illegal.
Action : Either change the STATIC_FLAG property value to 'N' or
the OVERRIDABLE property value so it does not equal 'MUST'.
CDA-02078,1, "%0!s: Overridden method must be overridable and must not be private."
Cause : The method that is referenced by OVERRIDING_METHOD_REFERENCE
cannot have its overridable property set to 'CANNOT' or its
visibility property set to 'PRIVATE'.
Action : Make sure that the method referenced by the
OVERRIDING_METHOD_REFERENCE does not have its
overridable property set to 'CANNOT' or its visibility
property set to 'PRIVATE'.
CDA-02079,1, "%0!s: Illegal constructor method constraint."
Cause : A method is considered to be a constructor when its name is
the same as the CLASS_NAME of the classifier it is defined inside.
A constructor is subject to the following constraints:
The RETURN_CLASSIFIER_REFERENCE and RETURN_TYPE_SCALAR properties
must be set to NULL. The STATIC_FLAG property must be
'N' and the overridable property cannot be 'MUST'.
Action : Make sure that the RETURN_CLASSIFIER_REFERENCE
and the RETURN_TYPE_SCALAR properties are set
to NULL Also ensure the STATIC_FLAG property is set to
'N' and the overridable property is set to 'MUST'.
CDA-02080,1, "%0!s: Non constructor method settings incorrect."
Cause : A method is considered to be a constructor when its name is
equal to the CLASS_NAME of the classifier it is defined inside.
When this happens the CONSTRUCTOR_FLAG property should be set to
'Y' and the RETURN_TYPE_DEFINED_BY property should equal 'NONE'.
Action : Make sure that the CONSTRUCTOR_FLAG property is set to the correct
value according to whether this is a constructor method or not. If
this method is a constructor make sure that the
RETURN_TYPE_DEFINED_BY property is set to 'NONE'
CDA-02081,1, "%0!s: Mapping to %1!s: prevents change to property %2!s."
Cause : The specified property for this element cannot be changed if
there is a mapping to the element.
Action : Remove the mapping associated with the element.
CDA-02082,1, "%0!s: Pseudo Column status prevents setting of property: %1!s."
Cause : When the property Pseudo Column Flag is set to 'Y' then the property
cannot be set.
Action : In order to set the property the Pseudo Column Flag must be set
to 'N'.
CDA-02083,1, "%0!s: A name clash has occurred with : %1!s."
Cause : The name (case sensitive) for an entity object attribute must be
unique across all other entity object attributes, the association
ends that refer to the same entity object as this entity object
attribute and all methods that refer to the same entity object as
this entity object attribute.
Action : Change the Name of either this entity object attribute or the
%1!s that it clashes with.
CDA-02084,1, "%0!s: Primitive Flag cannot be updated if generic class is a sub-type."
Cause : If this generic class is the sub-type of another classifier then
its Primitive_Flag property cannot be updated. The element is a
sub-type when there is a Classifier_Generalization with
Subtype_Reference to this element.
Action : Do not update the Primitive_Flag.
CDA-02085,1, "%0!s: No properties can be updated on an external class"
Cause : No properties can be updated on an external class as
indicated by the External_Flag property being set to 'Y'
(Or on Methods or General Attributes for an External Class)
Action : To be able to set properties set the External_Flag to 'N'. In the
case of a General Attribute set the External_Flag on the parent
Generic_Class
CDA-02086,1, "%0!s: The method's internal name must be unique."
Cause : A clash has occurred between the INTERNAL_NAME property
and an existing method of the same internal name. Internal
names have to be unique across all methods.
Action : Change the internal name of the method so that it is
unique.
CDA-02087,1, "%0!s: A name clash has occurred with : %1!s."
Cause : The name (case sensitive) for a method may not be the same
as any attribute (CLASSIFIER_ATTRIBUTE or its subtypes) or the
other ends of the association in the classifier that the method
references.
Action : Change the name so that it does not clash with another
element in the namespace for the Method element type.
CDA-02088,1, "%0!s: Interface classifier method not overridable."
Cause : If a method is for an interface classifier then it must be
overridable.
Action : If a method is for an interface classifier then make sure that
the overridable property for that method is set to 'MUST'.
CDA-02089,1, "%0!s: Overridable property must not be set to 'CANNOT'."
Cause : A method cannot be set as overridable if the parent class is
an interface classifier or if the overridable property on the
parent classifier is set to 'CANNOT'.
Action : When a parent classifier is set to overridable and it is
not an interface classifier then you can set the method
to overridable.
A method in an interface classifier can never have
its overridable property set to 'CANNOT'.
CDA-02090,1, "%0!s: Visibility of overridden method cannot be less than overriding method."
Cause : The Visibility of an overridden method cannot be less than the
visibility of the overriding method which is referenced by the
Overriding_Method_Reference. The order of visibility, from
least to most is:
1. Private
2. Protected
3. Package
4. Public.
Action : Change the visibility of either this or the overriding method so
that the visibility of the overridden method is no less than the
visibility of the methods which override it.
CDA-02091,1, "%0!s: An overriding method must be in one of the super-types."
Cause : The overriding method of this method must be in a
super-type of the classifier referenced by this method.
Action : Make sure that the overriding Method for this Method
referenced by the property Overriding_Method_Reference
is a Method in one of the super-types of the Classifier for this
Method referenced by the property Classifier_Reference.
CDA-02092,1, "%0!s: Method and activity definition refs. to named rule must match -%1!s:"
Cause : When a method which implements an activity definition
also references a named rule with a call type of %1!s,
then the activity definition must also reference the
named rule with its %1!s_RULE_REFERENCE.
Action : Try to make sure that the condition described in the cause
information holds true. The reference properties for the elements
are as follows:
Method for implementing an activity definition:
Method referenced via Activity_Definition.Method_Reference.
Method references a Named Rule:
A Method_Rule_Usage with Method_Reference and
Named_Rule_Usage values set with the Call_Type
property set to %1!s.
Activity Definition referencing the same Named Rule:
Activity_Definition.(Pre or Post)_Rule_Reference.
CDA-02093,1, "%0!s: Cannot create a method for an external class."
Cause : A method cannot be created when it is for an external
class as indicated if its parent generic class has its
External Flag set to 'Y'.
Action : Either do not create the method, or change the
External_Flag property of the parent generic
class to 'N'.
CDA-02094,1, "%0!s: Cannot be INITIAL if element is a target pseudostate for a transition."
Cause : A pseudostate cannot have its type property set to
'INITIAL' if it is referenced as the target pseudostate
by a transition.
Action : Do not set the type property to 'INITIAL'.
CDA-02095,1, "%0!s: Cannot be FINAL if element is a Source Pseudostate for a Transition"
Cause : A Pseudostate cannot have its TYPE property set to
'FINAL' if it is referenced as the Source Pseudostate
for a Transition.
Action : Do not set the TYPE property to 'FINAL'
CDA-02096,1, "%0!s: Default value is mandatory for an attribute in an interface classifier"
Cause : When a general attribute has an interface classifier parent then
the Default_Value property for that attribute is mandatory i.e. a
value must be set.
Action : Set a value for the default value property for this
general attribute.
CDA-02097,1, "%0!s: Static Flag property must equal 'Y' for Interface Classifier attribute"
Cause : When a General Attribute is for an Interface Classifier
then Static_Flag property must equal 'Y'.
Action : When a General Attribute is owned by an Interface
Classifier make sure that the Static_Flag property
equals 'Y'.
CDA-02098,1, "%0!s: Attribute property Decimal_Places must match Domain property"
Cause : For a general attribute to refer to an attribute domain with its
classifier_reference property then the Decimal_Places property
in the general attribute must have the same value as the
Decimal_Places property in the parent attribute domain.
Action : For a general attribute to refer to an attribute domain with its
classifier_reference property make sure the Decimal_Places property
in the general attribute has the same value as the
Decimal_Places property in the parent attribute domain.
CDA-02099,1, "%0!s: Association End and Event Subscription must have same ownership"
Cause : The association end referenced by the ASSOCIATION_END
property for this subscription detail must be owned by the same
Entity Object that owns the event subscription referenced by the
EVENT_SUBSCRIPTION_REFERENCE property.
Action : Make sure that the association end referenced by the
ASSOCIATION_END property for this subscription detail
is owned by the same Entity Object that owns the
event subscription referenced by the
EVENT_SUBSCRIPTION_REFERENCE property.
CDA-02100,1, "%0!s: Owning classifier for attribute and method must be the same"
Cause : The owning classifier of the classifier attribute that this element
is mapped from must be the owning classifier, or any of its
supertypes, of the method referenced by the event raiser reference.
Action : Make sure that the owning classifier of the classifier attribute
that this element is mapped from is the owning classifier, or any
of its supertypes, of the method referenced by the event raiser
reference.
CDA-02101,1, "%0!s: A General Attribute cannot be created for an external Generic Class"
Cause : A General Attribute that has an external Generic Class as its
parent Classifier cannot be inserted.
Action : Ensure that the parent Classifier for this Attribute does not have
its External_Flag property set to 'Y'.
CDA-02102,1, "%0!s: A Generated Event Classifier cannot be Transition source or target"
Cause : When an Event Classifier is generated as a result of an
Object State i.e. the Object_State_Reference for the Event
Classifier refers to an Object State then it cannot be either
the Source_Event_Reference or the
Target_Event_Reference for a Transition.
Action : To allow the Event Classifier to be either the
Source_Event_Reference or the
Target_Event_Reference for a Transition the
Object_State_Reference property must be set to NULL.
CDA-02103,1, "%0!s: Generic Class base datatype for an Attribute Domain must be Primitive"
Cause : The Generic Class that is the base datatype for an Attribute Domain,
i.e. is referenced by the property Generic_Class_Reference, must
have its Primitive_Flag property set to 'Y'.
Action : Make sure the Primitive_Flag property for the Generic_Class
referenced by Generic_Class_Reference is set to 'Y'.
CDA-02104,1, "%0!s: Only one Interface for a Business Object can be Primary"
Cause : Only one Business Object Interface for a Business Object can
have its Primary_Flag property set to 'Y'.
Action : Make sure that only one of the Business Object Interfaces that
refer to the same Business Object with the property
Business_Object_Reference has its Primitive_Flag set to 'Y'.
CDA-02105,1, "%0!s: A derived Attribute Domain must inherit Generic Class and Base Scalar"
Cause : An Attribute Domain that is derived from another Attribute Domain
must have the same values as its supertype for the properties
Generic_Class_Reference and Base_Scalar_Datatype.
Action : For an Attribute Domain that is derived from another Attribute
Domain the properties Generic_Class_Reference and
Base_Scalar_Datatype should already be set to match those
of the supertype so do not try to change them.
CDA-02106,1, "%0!s: Object State reference for an Event Classifier cannot be transferred"
Cause : The value of the Object_State_Reference for an Event Classifier
cannot be changed to reference a different Object State. The
Event Classifier is generated as a result of that Object State and
the association cannot be changed.
Action : Make sure that the value for the Object_State_Reference remains
unchanged.
CDA-02107,1, "%0!s: Only one Event Handler for an Event Subscription can be Primary"
Cause : Only one Event Handler for an Event Subscription can
have its Primary_Flag property set to 'Y'.
Action : Make sure that the other Event Handlers that refer to the
same Event Subscription with the property
Event_Subscription_Reference have their Primary_Flag
property set to 'N'
CDA-02108,1, "%0!s: Event cannot be a publication/subscription by an Event Classifier"
Cause : An Event Publication or Event Subscription cannot link
an Event Classifier published by another Event Classifier.
The Classifier_Reference of the Event Publication or
Event subscription must refer to a Classifier other than an Event
Classifier.
Action : Make sure that the Classifier_Reference property of this
Event Publication or Event Subscription does not refer
to an Event Classifier.
CDA-02109,1, "%0!s: The Event this is the publication/subscription of must not be Analysis"
Cause : The Event Classifier that this Event Publication or
Event Subscription is the publication/subscription
for must have its Analysis_Type_Flag set to 'N'
Action : Make sure that the Event Classifier that this Event Publication
is the publication for has its Analysis_Type_Flag set to 'N'
CDA-02110,1, "%0!s: The name for this element must be unique"
Cause : The name for this element must be unique across all elements
of the same type in the owning object.
Action : Ensure that the Name property for this element is not the same as
any other elements of the same type in the owning object.
CDA-02111,1, "%0!s: Only one Uniqueness rule can be transformed to the primary key"
Cause : No more than one Uniqueness Rule in an owning Classifier can
be flagged as the designated primary key.
Action : Make sure that for all the Uniqueness Rules for a Classifier
only one of them has its Designated_Primary_Key_Property
flag set to 'Y'.
CDA-02112,1, "%0!s: A subtype and its supertype must be the same element type"
Cause : A subtype and a supertype that are referenced by a Classifier
Generalization must be the same type of Classifier element.
Action : Make sure that the elements that are referenced by the properties
Subtype Reference and Supertype Reference of this Classifier
Generalization are the same type of Classifier element.
CDA-02113,1, "%0!s: Classifier Spec Group Classifier reference must match this supertype"
Cause : The Classifier referenced by the Classifier Spec Group for
this Classifier Generalization should be the same
element as the Supertype reference for this Classifier
Generalization.
Action : Make sure that the Classifier Spec Group Classifier
Reference and the Supertype Reference for this
Classifier Generalization point to the same element.
CDA-02114,1, "%0!s: Attribute Domain - too many supertypes"
Cause : An Attribute Domain can only have one supertype.
Action : Make sure that an Attribute Domain is the
subtype in only one Classifier Generalization.
CDA-02115,1, "%0!s: Cannot be a root if Classifier is referred to as a supertype"
Cause : The Root Flag property for a Classifier must be set to
'No' if a Classifier Generalization refers to that Classifier
with its Supertype Reference property.
Action : Make sure that that the Root Flag property is set to
'No'.
CDA-02116,1, "%0!s: Cannot be a leaf if Classifier is referred to as a subtype"
Cause : The Leaf Flag property for a Classifier must be set to
'No' if a Classifier Generalization refers to that Classifier
with its Supertype Reference property.
Action : Make sure that the Leaf Flag property for this Classifier
is set to 'No'.
CDA-02117,1, "%0!s: An element that is a supertype cannot be a Leaf"
Cause : A element that is referred to by the Supertype_Reference
of a Generalization cannot have its Leaf_Flag
property set to 'Yes'
Action : Make sure that an element that is referred to by the
Supertype_Reference of a Generalization does
not have its Leaf_Flag property set to 'Yes'
CDA-02118,1, "%0!s: A subtype element cannot be a root"
Cause : An element that is referred to by the Subtype_Reference
of a Generalization cannot have its Root_Flag
property set to 'Yes'
Action : Make sure that an element that is referred to by the
Subtype_Reference of a Generalization does
not have its Root_Flag property set to 'Yes'
CDA-02119,1, "%0!s: A Classifier Spec Group cannot be owned by an Attribute Domain"
Cause : A Classifier Spec Group cannot refer to an Attribute
Domain with its Classifier_Reference property.
Action : Make sure the Classifier_Reference property of the
Classifier Spec Group does not refer to an Attribute
Domain.
CDA-02120,1, "%0!s: Classifier Spec Group cannot be owned by a Primitive Generic Class"
Cause : A Classifier Spec Group cannot refer to a Generic Class
which has its Primitive_Flag property set to 'Yes'.
Action : Make sure the Classifier_Reference property of the
Classifier Spec Group does not refer to a Generic Class
which has its Primitive_Flag property set to 'Yes'.
CDA-02121,1, "%0!s: Classifier for qualified Association End must match Attribute Class"
Cause : A Classifier that owns the Classifier Attribute (Generic or Entity
Object Attribute) referred to by a Role Qualification must be the
same Classifier referred to by the Association End that the same
Role Qualification refers to (via an Association).
Action : Make sure that the Role Qualification can reference the same
Classifier via Classifier Attribute as it can via Association End
and Association
CDA-02122,1, "%0!s: The uniqueness constraint for this element type has been broken"
Cause : The combination of (Method_reference, Event_Subscription_Reference
or Subscription_Detail_Reference) must be unique AND (
Method_Reference, Sequence) must be unique.
Action : Make sure that the combination of
(Method_reference, Event_Subscription_Reference
or Subscription_Detail_Reference) is unique AND (
Method_Reference, Sequence) is unique.
CDA-02123,1, "%0!s: The uniqueness constraint for this element type has been broken"
Cause : The combination of (Subtype_Reference, Supertype_Reference)
must be unique. And the combination of
(Sequence, Supertype_Reference) must be unique.
Action : Make sure the combination of
(Subtype_Reference, Supertype_Reference)
is unique. And the combination of
(Sequence, Supertype_Reference) is unique.
CDA-02124,1, "%0!s: Recursive generalization or specialization is not allowed"
Cause : There cannot exist a generalization of a supertype element
for a generalization which is the same as the subtype
element for that generalization. Similarly there
cannot exist a specialization of a subtype element for a
generalization which is the same as the supertype
element for that generalization.
Action : Make sure that supertypes for a generalization
do not include the subtype element for that
generalization and that the subtypes for that
generalization do not include the supertype element.
CDA-02125,1, "%0!s: Classifier constraint for rule usage broken"
Cause : When there is a usage of a specific attribute, association end or
method in an integrity or attribute derivation rule as described
by a Member Component then the attribute, association end
or method must be in the same classifier or any of its
supertypes as the integrity or attribute derivation rule.
Action : Make sure that the attribute, association end or method
is in the same classifier or its supertypes as the integrity
or attribute derivation rule for this member component.
CDA-02126,1, "%0!s: Constraint for component attribute or association end in rule broken"
Cause : When a component attribute or association end is in a rule as
described by a data component element then the classifier for
that attribute or association end must be the same as the
classifier or its supertypes for the classifier rule for that
data component.
Action : Make sure the attribute or association end for this
data component is in the same classifier or any of its
supertypes as the classifier rule (arc or uniqueness).
CDA-02127,1, "%0!s: Attribute Derivation Rule cannot be for general attribute of interface"
Cause : An attribute derivation rule cannot be for a general
attribute of an interface classifier
Action : Make sure that the CLASSIFIER_ATTRIBUTE reference for
this attribute derivation does not point to a general attribute
which is owned by an interface classifier.
CDA-02128,1, "%0!s: Attributes/ass'n ends may not be duplicated across Uniqueness rules"
Cause : A uniqueness rule may not contain the same attributes/
association ends as any other uniqueness rule via a
data component element for the same context Classifier
Action : Ensure that the context classifier for the uniqueness rule
does not have another uniqueness rule referring to it that
via a data component contains any of the same attributes
or association ends
CDA-02129,1, "%0!s: Attributes/ass'n ends may not be duplicated across arc rules"
Cause : An Arc rule may not contain the same attributes/
association ends as any other arc rule via a data
component element for the same context classifier
Action : Ensure that the context classifier for the arc rule does not
have another arc rule referring to it that via a data
component contains any of the same attributes or
association ends
CDA-02130,1, "%0!s: A primary key uniqueness rule may not contain optional atts/ass'n ends"
Cause : When a uniqueness rule is designated primary key then
it may not contain via a data component any optional
attributes or association ends, i.e. an attribute or
association end that has a MINIMUM_MULTIPLICITY of
'0'
Action : Make sure that any attributes/association ends that are
contained by a primary key uniqueness rule via a data
component are not optional
CDA-02131,1, "%0!s: A pseudo column attribute may not be an association key implementation"
Cause : An entity object attribute cannot be flagged as a pseudo column
and at the same time be flagged as an association key
implementation.
Action : Make sure that the value (YES, NO) for the Pseudo Column
property is different from the value given to the Association
Key Implementation property for this entity object attribute .
CDA-02132,1, "-%0!s: A persistent attribute may not be an association key implementation"
Cause : A persistent entity object attribute cannot be an association
key implementation.
Action : Make sure the value given for the Persistent property is
different from the value given for the Association Key
Implementation property.
CDA-02133,1, "%0!s: Attribute that implements an association should have flag set"
Cause : An entity object attribute that implements an association (i.e. is
referenced by a join component) must have its Association Key
Implementation property set to 'Yes' (Y).
Action : Make sure that the Association Key Implementation property
for an entity object attribute that implements an association is
set to 'Yes'.
CDA-02134,1, "%0!s: Event attribute reference must refer to an event classifier attribute"
Cause : The general attribute referenced by the
CLASSIFIER_ATTRIBUTE_REFERENCE must be for
an event classifier.
Action : Make sure the general attribute referenced is for
an event classifier.
CDA-02135,1, "%0!s: Corresponding event publication must exist"
Cause : A corresponding event publication must exist which links
the same event classifier and entity object classifier that are
linked by this BC4J event attribute mapping via a general
attribute and an entity object attribute respectively.
Action : Make sure that an event publication exists between
the event classifier and the entity object classifier.
CDA-02136,1, "%0!s: The owning validator must share the same generic class"
Cause : The General Attribute that is referred to by
the General Attribute property must be owned by the
same generic class that is referred to by the Validator
for this validator value.
Action : Make sure that the owning generic classifier is the same
for the Validator and the General Attribute for this validator
value.
CDA-02137,1, "%0!s: Name must be unique in all Tags for the supertypes of the stereotype"
Cause : The name for a tag must not equal the name of any tags that
refer to a supertype of the stereotype that this tag refers to.
Action : Make sure that the name for this tag is unique not only
in the tags that refer to the same stereotype but also
all the supertypes of that stereotype
CDA-02138,1, "%0!s: Name must be unique in NLS attributes for stereotype baseclass"
Cause : The name must not be the same as the NLS name of any
attribute of the stereotype base class.
Action : Make sure the name is not the same as any of the NLS
names of any of the attributes of the stereotype base class.
CDA-02139,1, "%0!s: An element may not be a specialization of itself"
Cause : An element may not be both the supertype and the
subtype of a generalization.
Action : Make sure that the SUPERTYPE_REFERENCE and the
SUBTYPE_REFERENCE properties for a generalization
do not refer to the same element.
CDA-02140,1, "%0!s: The association end must be one of a pair of association ends"
Cause : The association end referred to by a join component must be
part of an association with two association ends.
Action : Make sure that the association end referred to by a join component
is part of an association with two association ends.
CDA-02141,1, "%0!s: Association end and entity attribute must have same entity object"
Cause : The other association end in the association that is referred to
by the association end for this join component should refer to
the same entity object as the entity attribute referred to by
EO_ATTRIBUTE_TO_REFERENCE.
Action : Make sure the other association end in the association that
is referred to by the association end for this join component
refers to the same entity object as the entity attribute referred to
by EO_ATTRIBUTE_TO_REFERENCE.
CDA-02142,1, "%0!s: The other association end must be persistent"
Cause : The other association end in the association for
this join component must have its persistent flag
set to 'Yes'.
Action : Make sure the other association end in the association for
this join component has it's persistent flag
set to 'Yes'.
CDA-02143,1, "%0!s: The other association end must not have any join components"
Cause : The other association end to the association from the
association end for this join component must not itself
be referred to by any join components.
Action : Make sure the other association end to the association from the
association end for this join component is not itself
referred to by any join components
CDA-02144,1, "%0!s: From entity attribute and association end must have same Entity Object"
Cause : The from entity attribute and the association end that are
referenced by a join component must each refer to the
same entity object.
Action : Make sure that the from entity attribute
(EO_ATTRIBUTE_FROM_REFERENCE) and the
association end that are referenced by a join
component each refer to the same entity object.
CDA-02145,1, "%0!s: All referenced elements must be persistent"
Cause : Both the entity attributes and the association end referenced
by a join component must have their persistent flags set to 'Yes'.
Action : Make sure that both the entity attributes and the
association end referenced by a join component
have their persistent flags set to 'Yes'.
CDA-02146,1, "%0!s: Classifier must be same for Integrity Rule and classifier attribute"
Cause : The classifier attribute referenced by the
CLASSIFIER_ATTRIBUTE_REFERENCE must be owned by
the owning classifier of the integrity rule.
Action : Make sure the classifier attribute referenced by the
CLASSIFIER_ATTRIBUTE_REFERENCE is owned by
the owning classifier of the integrity rule.
CDA-02147,1, "%0!s: Attribute must be owned by an entity, generic class or interface"
Cause : The classifier attribute referenced by the
CLASSIFIER_ATTRIBUTE_REFERENCE must be
owned by either an entity, a generic class or an interface.
Action : Make sure that classifier attribute referenced by the
CLASSIFIER_ATTRIBUTE_REFERENCE is
owned by either an entity, a generic class or an interface.
CDA-02148,1, "%0!s: Passed value cannot be set when mapped from an event raiser"
Cause : When this context mapping is a mapping from an event raiser
then the passed value must be NULL. Likewise if the passed
value is not NULL then the event raiser from reference must be
NULL.
Action : Make sure that either the passed value property is not NULL
or the event raiser from reference property is not NULL. If either
one of these properties is set to a non NULL value then the other
must be set to NULL.
CDA-02149,1, "%0!s: Interface usage must be linked via interface usage to association end"
Cause : The interface that this role specification references must be linked
via an interface usage to the generic class or entity object that
is referenced by the association end for this element
Action : Make sure that he interface that this role specification
references is linked via an interface usage to the generic
class or entity object that is referenced by the
association end for this element
CDA-02150,1, "--%0!s: Primitive Generic Class - too many supertypes"
Cause : A Generic Class that is primitive can only have
one supertype.
Action : Make sure that a primitive Generic Class
is the subtype in only one Classifier Generalization.
CDA-02151,1, "%0!s: Owning classifier for other association end and method must be same"
Cause : The association end that this element is mapped from must be
the other end of an association from the classifier, or any of its
supertypes, of the method referenced by the event raiser
reference property.
Action : Make sure that the association end that this element is mapped
from is the other end of an association from the classifier,
or any of its supertypes, of the method referenced by the event
raiser reference property.
CDA-02152,1, "%0!s: Owning event classifier for classifier attribute must be type CALL"
Cause : The owning event classifier of the general attribute referenced
by classifier attribute reference must have type = CALL.
Action : Make sure the owning event classifier of the general attribute
referenced by classifier attribute reference has type = CALL.
CDA-02153,1, "%0!s: Must be same owning method for method parameter and event raiser"
Cause : The owning method of the method parameter this element is
mapped from must be the method referenced by the event
raiser reference.
Action : Make sure the owning method of the method parameter this element is
mapped from the method referenced by the event
raiser reference.
CDA-02154,1, "%0!s: Event classifier must be type CALL"
Cause : The event classifier referenced by the event raiser reference
must be type = CALL.
Action : Make sure the event classifier referenced by the event raiser
reference type = CALL.
CDA-02155,1, "%0!s: Owning classifier for classifier attribute must be event classifier "
Cause : The owning classifier for the classifier attribute that this element
is mapped from must be an event classifier.
Action : Make sure that the owning classifier for the classifier attribute
that this element is mapped from in an event classifier.
CDA-02156,1, "%0!s: Both event raisers must refer to the same method"
Cause : The method reference for the event raiser that this element
is mapped from must be the same as the method reference
for the event raiser reference that it is mapped to.
Action : Make sure that the method reference for the event raiser that
this element is mapped from must be the same as the method
reference for the event raiser reference that it is mapped to.
CDA-02157,1, "%0!s: An application module cannot be nested within itself."
Cause : A usage cannot be created where the parent and child
application modules are the same.
Action : Specify different parent and child application modules
and repeat the operation.
CDA-02158,1, "%0!s: Association end usage must be on a different Entity Object Usage. "
Cause : Association End Usages come in pairs, one for each end of an
association.
These two ends must be on different Entity Object Usages.
Action : Make sure each association end usage in a pair
references a different entity object usage.
CDA-02159,1, "%0!s: View Usages are in different Application Modules."
Cause : For this view link end usage its view usage and
its view link usage must within the same application
module.
Action : Select a view usage and a view link usage within
the same application module and attempt to recreate
the view link end usage.
CDA-02160,1, "%0!s: The view object of the view link end and view usage must be the same."
Cause : The view usage and the view link end referenced
by this view link end usage must be based on the
same view object.
Action : Reference a view usage and a view link end
based on the same view object and then
recreate the view link end usage.
CDA-02161,1, "%0!s: View link of the view link end and view link usage must be the same."
Cause : The view link usage and the view link end referenced
by this view link end usage must be based on the
same view link.
Action : Reference a view link usage and a view link end
based on the same view link and then
recreate the view link end usage.
CDA-02162,1, "%0!s: A view link must have exactly two view link ends"
Cause : Both view link ends must be created in the same transaction.
A view link must have exactly two view link ends. one
being the master and the other the detail.
Action : This message should only arise when using the API
directly. The client tools should always create view
link ends in pairs.
Repeat the operation, creating both view link ends
in the same transaction.
CDA-02163,1, "%0!s: The name must not equal the NLS name of any repository element"
Cause : The name must not equal the NLS name of any repository element.
Action : Ensure that the name is different from the NLS name of all
repository elements.
CDA-02164,1, "%0!s: The Base Class must be the short name of an element type."
Cause : The BASE_CLASS property for this element must be the short name
of a repository element type.
Action : Ensure that the BASE_CLASS property for this element is the short
name of a repository element type.
CDA-02165,1, "%0!s: Name must be unique in all sub and supertypes of the stereotype"
Cause : The Name must be unique in all the subtypes and supertypes
for this stereotype.
Action : Ensure that the Name is unique in all the subtypes and
supertypes for this stereotype.
CDA-02166,1, "%0!s: The name of a Package must be unique in Classifiers and Associations"
Cause : The name of a Package (case sensitive) must be unique in
any Classifier class names and Association names in the
package.
Action : Make sure the name of a Package (case sensitive) is
unique in any Classifier class names and Association names in the
package.
CDA-02167,1, "%0!s: The Name must be unique within a single Use Case"
Cause : The Name of an extension point must be unique
within a single Use Case.
Action : Make sure the Name of an extension point is unique
within a single Use Case
CDA-02168,1, "%0!s: IS PRIMARY property may not be manually set to 'No'."
Cause : The IS PRIMARY property on a Use Case Actor Usage cannot
manually be set to 'No'. This is only changed to 'No' by the
API when another Use Case Actor Usage for the same Use
Case has its IS PRIMARY property set to 'Yes'.
Action : To have the IS PRIMARY property set to 'No' another Use Case
Actor Usage for the same Use Case must have its IS PRIMARY
property set to 'Yes'.
CDA-02169,1, "%0!s: Element referred to by Element Rule Usage cannot be a UML Rule"
Cause : The element referred to by the ELEMENT property of
an Element Rule Usage may not be of type UML Rule.
Action : Make sure that the element referred to by the ELEMENT
property of an Element Rule Usage is not a UML Rule.
CDA-02170,1, "%0!s: MAXIMUM_ must be greater than or equal to the MINIMUM_MULTIPLICITY"
Cause : The MAXIMUM_MULTIPLICITY value must be
greater than or equal to the MINIMUM_MULTIPLICITY value.
Action : Make sure that the MAXIMUM_MULTIPLICITY value
is '*' or greater than or equal
to the MINIMUM_MULTIPLICITY value.
CDA-02171,1, "%0!s: Interface Classifier Method name clash."
Cause : If a Method belongs to an Interface Classifier then
the name of the method must not be the
same as the Interface Classifier name.
Action : If a Method belongs to an Interface Classifier then
make sure that the name of the method is not the
same as the Interface Classifier name.
CDA-02172,1, "%0!s: Visibility property must be 'PUBLIC' in Interface Classifier attribute"
Cause : When a General Attribute is owned by an
Interface Classifier then the Visibility property of the
General Attribute should equal 'PUBLIC'.
Action : When a General Attribute is owned by an
Interface Classifier make sure that the Visibility
property of the General Attribute equals 'PUBLIC'.
CDA-02173,1, "%0!s: Change_Restriction must equal 'FROZEN' for Interface attribute"
Cause : When a General Attribute is owned by an Interface
Classifier make sure that the Change_Restriction
property equals 'FROZEN'.
Action : When a General Attribute is owned by an Interface
Classifier make sure that the Change_Restriction
property equals 'FROZEN'.
CDA-02174,1, "%0!s: Retrievable_Flag must equal 'N' for Interface attribute"
Cause : When a General Attribute is owned by an Interface
Classifier the Retrievable_Flag property must equal
'N'.
Action : When a General Attribute is owned by an Interface
Classifier make sure the Retrievable_Flag property equals
'N'.
CDA-02175,1, "%0!s: Updatable_Flag must equal 'N' for Interface attribute "
Cause : When a General Attribute is owned by an Interface
Classifier the property Updatable_Flag must equal 'N'.
Action : When a General Attribute is owned by an Interface
Classifier make sure the Updatable_Flag property equals
'N'.
CDA-02176,1, "%0!s: Decimal_Places must be NULL for Interface attribute "
Cause : When a General Attribute is owned by an Interface
Classifier the property Decimal_Places must be NULL.
Action : When a General Attribute is owned by an Interface
Classifier make sure the property Decimal_Places is NULL.
CDA-02177,1, "%0!s: Maximum_Length must be NULL for Interface attribute "
Cause : When a General Attribute is owned by an Interface
Classifier the property maximum_length must be NULL.
Action : When a General Attribute is owned by an Interface
Classifier make sure the property maximum_length is NULL.
CDA-02178,1, "%0!s: Prompt must be NULL for Interface attribute "
Cause : When a General Attribute is owned by an Interface
Classifier the property Prompt must be NULL.
Action : When a General Attribute is owned by an Interface
Classifier make sure the property Prompt is NULL.
CDA-02179,1, "%0!s: Minimum_Multiplicity must equal '1' for Interface attribute "
Cause : When a General Attribute is owned by an Interface
Classifier the property Minimum_Multiplicity must equal '1'.
Action : When a General Attribute is owned by an Interface
Classifier make sure the property Minimum_Multiplicity
equals '1'.
CDA-02180,1, "%0!s: Attribute property Default_Value must match Domain property"
Cause : For a general attribute to refer to an attribute domain with its
classifier_reference property then the Default_Value property
in the general attribute must have the same value as the same
Default_Value property in the parent attribute domain.
Action : For a general attribute to refer to an attribute domain with its
classifier_reference property make sure the Default_Value
property in the general attribute has the same value as the
same Default_Value property in the parent attribute domain.
CDA-02181,1, "%0!s: Attribute property Maximum_Length must match Domain property"
Cause : For a general attribute to refer to an attribute domain with its
classifier_reference property then the Maximum_Length property
in the general attribute must have the same value as the same
Maximum_Length property in the parent attribute domain.
Action : For a general attribute to refer to an attribute domain with its
classifier_reference property make sure the Maximum_Length
property in the general attribute has the same value as the same
Maximum_Length property in the parent attribute domain.
CDA-02182,1, "%0!s: Attribute property Retrievable_Flag must match Domain property"
Cause : For a general attribute to refer to an attribute domain with its
classifier_reference property then the Retrievable_Flag property
in the general attribute must have the same value as the
Queryable_Flag property in the parent attribute domain.
Action : For a general attribute to refer to an attribute domain with its
classifier_reference property make sure the Retrievable_Flag
property in the general attribute has the same value as the
Queryable_Flag property in the parent attribute domain.
CDA-02183,1, "%0!s: Attribute property Updatable_Flag must match Domain property"
Cause : For a general attribute to refer to an attribute domain with its
classifier_reference property then the Updatable_Flag property
in the general attribute must have the same value as the same
Updatable_Flag property in the parent attribute domain.
Action : For a general attribute to refer to an attribute domain with its
classifier_reference property make sure the Updatable_Flag
property in the general attribute has the same value as the
Updatable_Flag property in the parent attribute domain.
CDA-02184,1, "%0!s: The maximum length of NAME is 24 "
Cause : Name length exceeded.
Action : Make sure that NAME is 24 or fewer characters in length.
CDA-02185,1, "%0!s: Property ORACLE TYPE may only reference an Oracle Object Type"
Cause : The property ORACLE TYPE may only reference
an Oracle Object Type.
Action : Make sure that the property ORACLE TYPE only
references an Oracle Object Type.
CDA-02186,1, "%0!s: A Queue Table Implementation must exist for the Database User"
Cause : The Database User referenced by the property
QUEUE_TABLE_DBU_REFERENCE must also be
referenced by a Queue Table Implementation with the
property DATABASE_USER_REFERENCE.
Action : Make sure that the Database User referenced by
the property QUEUE_TABLE_DBU_REFERENCE is
also referenced by a Queue Table Implementation with the
property DATABASE_USER_REFERENCE.
CDA-02187,1, "%0!s: Only a Subsytem Package can be represented by a Classifier"
Cause : Only if a Package has its TYPE property set to 'SUBSYSTEM'
can it be represented by a Classifier via CLASSIFIER_REFERENCE.
Action : In order to set a reference to a Classifier
make sure the TYPE property is set to 'SUBSYSTEM'.
CDA-02188,1, "%0!s: The name of a Package cannot be 'Package'"
Cause : The name of a Package cannot equal 'Package' in any
combination of letter case.
Action : Make sure the name of a Package does not equal
'Package' in any combination of letter case.
CDA-02189,1, "A circularity exists in %0!s Generalization network to element IRID: %1!s"
Cause : A circularity exists in, or will be introduced into, the
Generalization network identified in the Message line
of this error message. The IRID of the element referenced
in the circularity is also given.
Action : If the circularity is introduced by an Insertion or
Update to a Generalization element then this action is not
allowed and will have to be undone.
CDA-02190,1, "%0!s: A Package cannot own Application Systems, Folders or Projects."
Cause : Application Systems, Folders or Projects cannot be added as
a child of a Package.
Action : Make sure that Application Systems, Folders or Projects are not
added as children of a Package.
CDA-02191,0, "%0!s: MAXIMUM_MULTIPLICITY must be either '*' or a number > 0"
Cause : The valid values for MAXIMUM_MULTIPLICITY are '*' or a positive
integer.
Action : Set MAXIMUM_MULTIPLICITY so it conforms to the above rule.
CDA-02192,0, "%0!s: MINIMUM_MULTIPLICITY must a number >= 0"
Cause : MINIMUM_MULTIPLICITY must not be a negative number.
Action : Set MINIMUM_MULTIPLICITY to be either 0 or a positive number.
CDA-02193,0, "%0!s: Uniqueness clash with %1!s"
Cause : The NAME of a View Object Attribute shares the same namespace as
the SQL_ALIAS of all Entity Object Usages within the same
View Object.
Action : Ensure that within the same View Object all View Object Attribute
NAMEs and Entity Object Usage SQL_ALIASs are unique.
CDA-02194,0, "%0!s: Interface Classifier must have a Rich Interface"
Cause : If an Association End is a role in an Interface Classifer then
the Interface Classifier must have RICH_TEXT_INTERFACE = 'Y'.
Action : Update the Interface Classifier so RICH_TEXT_INTERFACE = 'Y' or
make the Association End a role in another type of Classifier.
CDA-02195,0, "%0!s: If MAXIMUM_MULTIPLICITY < 2 then ORDERED_FLAG must = 'N'"
Cause : The ORDERED_FLAG must be set if MAXIMUM_MULTIPLICITY = 1.
Action : Either increase MAXIMUM_MULTIPLICITY or set ORDERED_FLAG = 'Y'.
CDA-02196,0, "%0!s: Only one end of a binary Association may be an aggregation"
Cause : Only one Association End of a binary Association may have
AGGREGATION = 'STRONG' or 'WEAK'. The other end must set
AGGREGATION to 'NONE'.
Action : Ensure that one of the Association Ends has AGGREGATION set to
'NONE'.
CDA-02197,0, "%0!s: Aggregation is not permitted in a N-ary Association"
Cause : In an N-ary Association (one with more than 2 Association Ends),
all the Association Ends must set AGGREGATION to 'NONE'.
Action : Ensure that all Association Ends in this Association have
AGGREGATION set to 'NONE'.
CDA-02198,0, "%0!s: %1!s may only be a role in one 'STRONG' Association End"
Cause : More than one Association End with AGGREGATION = 'STRONG' refer to
one Classifier.
Action : Update one or more Associations Ends so that either AGGREGATION
!= 'STRONG' or they refer to other Classifiers.
CDA-02199,0, "%0!s: An Association Class may only play a role in a binary Association"
Cause : An Association Class is an Entity Object or Generic Class which is
referenced by an Association via its ENTITY_OBJECT_REFERENCE or
GENERIC_CLASS_REFERENCE properties. An Association with exactly two
Association Ends is a binary Association. Only an Association End
that is part of a binary Association may refer to an Association
Class.
Action : Either modify the Association End so that it refers to a Classifer
which is not an Association Class, or remove one or more of the
Association Ends that make up this Association so that it is a
binary Association.
CDA-02200,0, "%0!s: An Association Class may only be associated to a related Classifier"
Cause : An Association Class is an Entity Object or Generic Class which is
referenced by an Association via its ENTITY_OBJECT_REFERENCE or
GENERIC_CLASS_REFERENCE properties. An Association with exactly two
Association Ends is a binary Association. If one Association End in
a binary Association references an Association Class, the other
Association End must reference one of the Classifiers that plays
a role in the Association that has that Association Class.
Action : Either modify one Association End so that it refers to a Classifer
which is not an Association Class, or modify the other Association
End so that it refers to a Classifer that plays a role in the
Association which has the Association Class.
CDA-02201,0, "%0!s: UNIQUENESS_RULE_REFERENCE is only valid in binary Associations"
Cause : A binary Association is one with exactly two Association Ends.
UNIQUENESS_RULE_REFERENCE may only be set on an Association End
which is within a binary Association.
Action : Either leave UNIQUENESS_RULE_REFERENCE null or remove Association
Ends from this Association.
CDA-02202,0, "%0!s: Uniqueness Rule must be one owned by %1!s"
Cause : When an Association End references a Uniqueness Rule (via
UNIQUENESS_RULE_REFERENCE), that Uniqueness Rule must be owned by
the same Classifier that plays a role in the other Association End
of this binary Association.
Action : Either leave UNIQUENESS_RULE_REFERENCE null, or reference a
Uniqueness Rule that is owned by the correct Classifier, or update
the other Association End so that it refers to the correct
Classifier.
CDA-02203,0, "%0!s: Uniqueness Rule may only be specified on one end of an Association"
Cause : Only one Association End in a binary Association may set
UNIQUENESS_RULE_REFERENCE.
Action : Set UNIQUENESS_RULE_REFERENCE to null on one of the Association
Ends.
CDA-02204,0, "%0!s: NAME uniqueness clash with %1!s"
Cause : The NAME may be null, but if it is not null then it must be not be
the same as the NAME of any Attribute or Method in the Classifier
at the other end(s) of the Association.
Action : Change the NAME of the Association End - NULL is valid.
CDA-02205,0, "%0!s : %1!s cannot own Containers which are not Packages"
Cause : Packages may not own Application Systems, Folders or Projects.
Action : Either create a Package within this Package or set the context
Container to be an Application System, Folder or Project, or NULL
for a root Container.
CDA-02206,0, "%0!s: Uniqueness clash with %1!s"
Cause : The ROLE_NAME of an Application Module Usage shares
the same namespace as the NAME of all the View Object Usages, and
the NAMEs of all the View Link Usages in the owning Application
Module. This test is case insensitive.
Action : Ensure that within the same Application Module all View Object
Usage and View Link Usage NAMEs and all Application Module Usage
ROLE_NAMEs are unique, regardless of case.
CDA-02207,0, "%0!s: Loop detected. Parent and Child references cause a loop"
Cause : Inserting this element causes a recursive definition or a loop
which is not permitted.
Action : Choose a different value for the parent or child reference.
CDA-02208,0, "%0!s: %1!s cannot own objects"
Cause : Project Containers cannot own objects or elements. They can only
be shared in.
Action : Insert (or move) this object into a different type of
Container (Folder, Package or Application System).
CDA-02209,0, "%0!s: A Use Case may not be a specialization of itself"
Cause : Properties SUPERTYPE_REFERENCE and SUBTYPE_REFERENCE may not
have the same values.
Action : Set SUPERTYPE_REFERENCE and SUBTYPE_REFERENCE to different values.
CDA-02210,0, "%0!s : Cannot delete the owning Folder Member for this object"
Cause : An element cannot be unshared from its owning container, i.e.
the folder member with OWNERSHIP_FLAG = 'Y' cannot be deleted
without deleting the element itself.
Action : If you no longer want this element in this container, either
delete the element or move it to another container.
CDA-02211,0, "%0!s: Module Component Links may not be to or from a Subcomponent"
Cause : A Module Component Link (Key Based Link or Custom Link) may not
be from or to a Module Component Inclusion that is the usage of a
Subcomponent.
Action : Ensure that the MCN_REFERENCE_FROM and MCN_REFERENCE_TO properties
both refer to Module Component Inclusions which have their
MODULE_COMPONENT_REFERENCE properties set.
CDA-02212,0, "%0!s: Unbound Item's END_TAB stop value must be higher than START_TAB stop."
Cause : User has set the END_TAB property on the unbound item
to be greater than the START_TAB value.
Action : Set the END_TAB value to be higher than
that of the START_TAB value.
CDA-02213,0, "%0!s: Index Storage Usage Table must match table index is being created on."
Cause : The user has attempted to set a User Index Storage Usage
that is based on a different Table Definition against the
index.
Action : Create or use User Object Index Storage based
on this table.
CDA-02214,1, "Data Persistence can be set only to one of PERMANENT, SESSION or TRANSACTION"
Cause : The Data Persistence property has been set to an invalid value.
Action : Set the value of Data Persistence Property to one of PERMANENT,
SESSION or TRANSACTION.
CDA-02215,1, "Gobal Temporary tables cannot be clustered."
Cause : The cluster property for Global Temporary table has been set.
Action : Unset the cluster property of the table.
CDA-02216,1, "Gobal Temporary tables cannot be index organized."
Cause : The Index Organized property of the Global Temporary table has been
set to yes.
Action : Change the Index Organized property to No.
CDA-02217,1, "Gobal Temporary tables cannot contain referential integrity constraints."
Cause : A foreign key has been added to a Global Temporary Table.
Action : Change the value of the Data Persistence property to "PERMANENT" or
remove the foreign keys from the table.
CDA-02218,1, "Only Permanent tables can be referenced in a Foreign Key definition."
Cause : A Global Temporary table has been referenced in a Foreign Key
definition.
Action : Remove the reference to the Global Temporary Table from the Foreign
Key definition.
/
/ 03000 .. 03499 Constraint violation warnings
/
CDA-03002,1, "%0!s: Specified super-type %1!s is currently a sub-type of %0!s"
Cause : A violation in the entity hierarchy was detected.
Action : Update the entity to refer to a different super-type.
CDA-03004,1, "%0!s: The referenced %1!s does not exist"
Cause : The element for which the synonym is created does not exist.
Action : Update the synonym to refer to a valid element.
CDA-03005,1, "%0!s: A Short Definition must be provided"
Cause : A Short Definition must be provided when there is no reference to a
Common function.
Action : Update the function, either to provide a valid Short Definition or
to nullify the reference to a Common function.
/
/ 03500 .. 03599 Structure element fatal errors
/
CDA-03500,0, "%0!s: Invalid %1!s reference <%2!s>"
Cause : An invalid reference property was detected.
Action : Update the specified element, providing a valid reference value
for the indicated property.
CDA-03501,0, "%0!s <%1!s>: An association already exists between %2!s and %3!s"
Cause : A uniqueness constraint violation was detected when associating
two elements that are already associated.
Action : The association already exists, and so no action need be taken.
CDA-03502,0, "%0!s <%1!s>: An association already exists between triggering %2!s and triggered %3!s"
Cause : A uniqueness constraint violation was detected when associating
two elements that are already associated.
Action : The association already exists, and so no action need be taken.
CDA-03504,0, "%0!s<%1!s>: Does not exist"
Cause : The ID specified either does not exist or is
for an element of the wrong type.
Action : Either specify the ID of an element of the correct
element type, or call the correct function for
this ID.
/
/ 04000 .. 04099 General messages
/
CDA-04000,1, "%0!s: %1!s is not mandatory"
Cause : It is recommended that only mandatory Attributes be included in
Unique Identifier Entries.
Action : This is a modeling suggestion only. To avoid this warning, make
all Attributes mandatory (non-optional) when they are included in a
Unique Identifier Entry.
CDA-04001,1, "%0!s: %1!s is in an arc"
Cause : The specified Relationship is included in an arc. It is recommended
that such Relationships be excluded from Unique Identifier Entries,
or that all Relationships in the arc be included in the Unique
Identifier Entry.
Action : This message is intended only to alert the user to a possible
modeling error.
CDA-04002,1, "%0!s: The generated plural was too long; defaulting to entity name"
Cause : When generating the plural for an entity name, the standard
algorithm produced a plural that exceeded 40 characters, so the
plural name defaulted to the entity name.
Action : No action need be taken. This is an informational message only.
CDA-04003,0, "%0!s: Name has been truncated to 12 characters"
Cause : Application system names must be 12 characters or less, because the
final two characters are used for system purposes. The name was
truncated to 12 characters.
Action : No action need be taken. This is an informational message only.
CDA-04004,0, "%0!s: Changes in format characteristics have caused this attribute to be dissociated from %1!s"
Cause : An attribute associated with a domain was updated, and new format
characteristics were supplied that conflict with those of the
domain. As a result, the attribute was dissociated from the domain
(i.e. the reference to the domain was reset to NULL).
Action : No action need be taken. This is an informational message only.
/
/ 06000 .. 06199 Access control violations
/
CDA-06000,0, "Access control violation: %0!s not found or no rights on this application system"
Cause : Either the Application System specified does not exist, or the
current user has not been granted access to it.
Action : Check the Application System, and if correct contact the
Repository owner to grant access to your user.
CDA-06001,1, "Access control violation: reference value not provided for validation"
Cause : This is an internal message and should not normally be issued.
When calculating access control privileges for an operation on
a particular element, the ID of the element was not supplied.
Action : Check all reference property values and resubmit the operation
request.
CDA-06002,1, "Access control violation: %0!s with reference %1!s not found in any application system"
Cause : During access control checks, it was detected that a reference
property supplied for an element does not correspond to an element
in the Repository instance.
Action : Ensure that all reference properties provided in the property list
are references to valid elements.
CDA-06003,1, "Access control violation: Element %0!s with reference %1!s is unexpected element type"
Cause : Access control checks detected that a supplied reference property
corresponded to an element of a type different from that expected.
Action : Ensure that all reference properties provided in the property list
are references to valid elements.
CDA-06004,1, "Access control violation: %0!s is not owned by context %1!s"
Cause : An access control violation was detected. Operations cannot be
performed on elements that are not owned by the context application
system.
Action : Reset the context application system to be the application system
that owns the element in question, and then reissue the operation
request.
CDA-06005,1, "Access control violation: %0!s operations are not allowed in the context application system %1!s"
Cause : An access control violation was detected. The user does not have
privileges to perform the indicated operation in the context
application system.
Action : Obtain privileges to perform the indicated operation and reissue
the operation request.
CDA-06006,1, "Access control violation: Application system %0!s version %1!s not found"
Cause : Either the specified version of this application system does not
exist in this Repository instance, or the user has no privileges to
perform operations in it.
Action : Obtain the necessary privileges on this application system, or
correct the application system name and/or version, if these are
invalid.
CDA-06007,1, "Access control violation: Application system %0!s not found or no access rights on this application system"
Cause : Either the specified application system does not exist in this
Repository instance, or the user has no privileges to perform
operations in it.
Action : Obtain the necessary privileges on this application system, or
correct the application system name, if it is invalid.
CDA-06008,1, "Access control violation: %0!s is a parent Application and cannot be modified"
Cause : Operations cannot be performed on elements in parent application
systems at this time.
Action : Establish the context application system to be a childless
application system.
CDA-06009,1, "Access control violation: Primary access control element not provided on %0!s of %1!s"
Cause : An operation that was performed on an element required that access
privileges be checked for its parent. The reference for the parent
of the element was not provided in the property list, and so no
access checks could be performed.
Action : Check that all reference properties provided in the property list
are references to valid elements.
CDA-06010,1, "Access control violation: User has no read access for this application"
Cause : Operations could not be performed on this application system because
the user has no read privileges on it.
Action : Obtain the necessary privileges on this context application system
through the Repository Administrator or establish a different
application system to be the context application system.
CDA-06011,1, "Access control violation: Changes cannot be made to a frozen application"
Cause : Changes are not allowed to frozen application systems.
Action : Unfreeze the application system before attempting to perform
operations on its elements.
CDA-06012,1, "Access control violation: %0!s: Neither entity %1!s nor %2!s is owned by the context application system"
Cause : At least one of the entities that are connected by a relationship
must be owned by the context application system.
Action : Reset the context application system to be the owner of at least
one of the entities and reissue the operation request.
CDA-06013,1, "Access control violation: This operation requires ADMIN privileges on the application system"
Cause : The current user does not have the ADMIN privilege to this
Application System, which is required for this operation.
Action : Obtain ADMIN privilege for this Application System from
the Repository owner.
CDA-06014,1, "Access control violation: Renaming an application system requires ADMIN privileges on all versions"
Cause : To rename a versioned Application System, the user must
have ADMIN privilege on all versions of the Application
System. The current user does not have this privilege for
at least one version.
Action : Obtain ADMIN privilege for all versions of this Application System
from the Repository owner.
CDA-06015,0, "Access control violation: Application system name %0!s already exists"
Cause : An attempt was made to rename an application system to a name
that is already used by an existing application system. This
application system may be owned by another user.
Action : Application system names must be unique within the repository
instance.
CDA-06016,0, "Access control violation: %0!s not a valid Repository user"
Cause : An attempt was made to transfer ownership of a application system
to a user that has not been registered as a valid repository
user.
Action : This error will only occur if a user has access 'canceled' while
the operation was performed. Reselect a valid user and retry.
CDA-06017,1, "Access control violation: Only the application system owner can transfer ownership"
Cause : Only the owner of an application system may transfer ownership
Action : Retry operation as the application system owner
CDA-06018,0, "copy: Uniqueness checks failed on new element"
Cause : An attempt was made to copy an element that would result in a name
clash within the application system.
Action : Specify a new name or short name in the copy dialogue.
CDA-06019,0, "Element has been deleted by another user"
Cause : An element being processed has been deleted before the operation
could complete.
Action : Re-query elements and retry the operation
CDA-06020,0, "copy: A new `Name` must be specified for this element-type"
Cause : When the source and destination application systems of copy are
the same , a new element name must be specified.
Action : Enter a new Name for the element in the copy dialogue
CDA-06021,0, "copy: A new `Short Name` must be specified for this element-type"
Cause : When the source and destination application systems of copy are the
same , a new element short name must be specified.
Action : Enter a new Short Name for the element in the copy dialogue
CDA-06022,1, "%0!s: The Name is not unique within application system"
Cause : The specified name was not unique
Action : Specify a unique name and repeat the operation.
CDA-06023,0, "%0!s: The Short Name is not unique within application system"
Cause : The specified name was not unique
Action : Specify a unique name and repeat the operation.
CDA-06024,0, "%0!s: Another database object exists with this name"
Cause : Database object must be unique in an application system
Action : Repeat the operation specifying a unique name for the
database object.
CDA-06025,0, "Unable to share %0!s type %1!s; share failed"
Cause : The share operation failed for the this element
Action : The share operation usually fails because of name uniqueness
constraints. The name conflicts have to be resolved before the
operation is repeated.
CDA-06026,0, "Unable to share %0!s type %1!s (non-shareable element); share failed"
Cause : An attempt was made to share a non-shareable element
Action : This error should not normally occur
CDA-06027,0, "User requires SHARE privileges on the owning application system of %0!s type %1!s; share failed"
Cause : Users must have SHARE privileges on the owning application
system to share an element from that application.
Action : Request SHARE privileges from your Repository Administrator
CDA-06028,1, "Cannot unshare - Element is referenced from %0!s - %1!s"
Cause : An attempt to unshare a element has failed because references
to that element within the application system exist.
Action : Remove references before unsharing
CDA-06029,0, "Unshare failed for %0!s - %1!s"
Cause : Unshare failed. Causes are listed separately.
Action : See individual Actions.
CDA-06030,0, "Unshare operation failed"
Cause : Unshare of a set of elements has failed.
Action : The entire operation is rollback, so remedy the cause and
retry operation
CDA-06031,0, "Unable to transfer %0!s type %1!s (non-transferable element); transfer failed"
Cause : An attempt has been made to transfer a non-transferable element
Action : Elements of this type cannot be transferred.
CDA-06032,0, "Function is used (%0!s - %1!s)"
Cause : Transferring a function with usages
Action : A function cannot be transferred to another application system if
the function or any of its children has usages with entities,
business units, modules or dataflows.
CDA-06033,0, "Receiving application system contains function/child (%0!s)"
Cause : The application system that is to receive the function, or function
hierarchy, already contains a function with the same label as one of
the functions that you are trying to transfer.
Action : Resolve the duplicate name and retry.
CDA-06034,0, "Source or destination of Dataflow (%0!s)"
Cause : The specified dataflow exists between the function being
transferred and either an external or datastore object.
As functions are not shareable it is not possible to maintain
this relationship across application systems.
Action : Either delete the dataflow before transferring the function or
transfer the related external or datastore at the same time.
In the latter case, there could be further references which would
also need to be resolved.
CDA-06035,0, "Entity/sub-types not shared by the application system"
Cause : This message is not used in the current release.
Action :
CDA-06036,0, "Must specify a new name for an element that is already shared into the application system"
Cause : An attempt was made to copy or share an element
into an application system where the name is already
in use.
Action : Specify a new name for the element and repeat the
operation.
CDA-06037,0, "Cannot copy elements of type %0!s"
Cause : An attempt was made to copy and element which is
not allowed to be copied.
Action : Refer to the on-line help to determine which
elements can be copied. Repeat the
operation specifying a valid element to copy.
CDA-06038,0, "A valid application system must be specified"
Cause : An attempt was made to share, copy or
transfer an element without specifying the
target application system.
Action : Repeat the operation specifying a valid target
application system to which the user has the appropriate
access rights.
If necessary, refer to the on-line help for further details
on the access rights required to perform the operation.
CDA-06039,0, "Only the owner of an application system can grant access to it"
Cause : An attempt was made to grant access rights
to an application system by a user who does not have
the correct privileges.
Only users with administrator privilege or users who own an
application system can grant further access rights on that
application system.
Action : Ask the application owner to grant administrator
privileges to the user performing the operation.
Repeat the operation using a valid repository user who
has been granted the correct privileges.
CDA-06040,0, "Access rights for the user and application system already exist"
Cause : The specified user already has these access rights on
the target application system.
Action : Ensure the correct user was specified.
Repeat the operation specifying the correct user to
whom access rights are to be granted.
CDA-06041,0, "Cannot remove the access rights for the owner of the application system"
Cause : An attempt was made to remove all access rights
from the application owner.
Action : Transfer ownership of the application system to a new owner.
Then repeat the operation to remove the access
rights to the application system for the user who is
no longer the application owner.
CDA-06042,0, "Access right values that are mandatory have not been set"
Cause : The following access right values are mandatory and must be set :-
Select, Update, Insert, Delete, Share and Admin privileges
Target application system
User being granted the privilege, user granting the privilege.
Action : Ensure all mandatory properties are being set and
repeat the operation.
CDA-06043,0, "Access right values have been set incorrectly"
Cause : This message is no longer used.
Action :
CDA-06044,0, "Insufficient privileges to remove the application system"
Cause : Delete privilege is required to delete an application
system.
Action : Ask the application owner to grant the delete privilege
to the user attempting to perform the Application Delete operation.
Then, repeat the operation.
CDA-06045,0, "Not all the application systems within the hierarchy have been specified"
Cause : All application systems in an application system
hierarchy must be deleted together.
Action : Repeat the operation selecting the entire application hierarchy.
CDA-06046,0, "Elements have been shared by application systems that are not being removed"
Cause : It is not possible to delete an application system which
owns elements shared to other application systems not
also marked for delete.
Action : Either unshare the elements or copy the elements in to the
application systems not being deleted.
CDA-06047,0, "Not all the application systems within the version group have been specified"
Cause : This error message is no longer used.
Action :
CDA-06048,0, "Could not lock the Repository tables in exclusive mode"
Cause : This error message is no longer used.
Action :
CDA-06049,0, "Elements within application systems being removed are currently checked out"
Cause : The application system to be deleted contains elements which
are checked out to a working application system.
Action : This is a warning message.
Pressing the OK button will delete the application
system and it will not be possible to check in the
elements from the working application system.
CDA-06050,0, "The commit mode is invalid"
Cause : An invalid commit mode has been specified when
performing this operation.
Valid commit modes when deleting an application system
are either committing after each application system or one
commit at the end of the entire operation.
Valid commit modes when copying an application system
are normal mode, table mode and run mode.
Refer to the online help for further details of the various
commit modes.
Action : Repeat the operation specifying a valid commit mode.
CDA-06051,0, "A Repository user already exists for this Oracle user"
Cause :
Action :
CDA-06052,0, "The Repository username is not unique"
Cause :
Action :
CDA-06053,1, "Application name specified exceeds the maximum length allowed."
Cause : An application name has been specified which is longer
than 14 characters.
Action : Repeat the operation specifying a new application name
which is 14 characters or less.
CDA-06054,0, "The Oracle user does not exist"
Cause :
Action :
CDA-06055,0, "The application system does not exist"
Cause :
Action :
CDA-06056,0, "The user type is invalid"
Cause :
Action :
CDA-06057,0, "The access privilege is invalid"
Cause :
Action :
CDA-06058,0, "The database type is invalid"
Cause :
Action :
CDA-06059,0, "Access to the application system has not been given"
Cause :
Action :
CDA-06060,0, "Cannot remove the Repository user that owns the Repository tables"
Cause :
Action :
CDA-06061,1, "The restore process had to create a unique name for application system %0!s"
Cause : After a successful restore of an application
system the restore process found duplicate
application system names had been created.
This could have occurred if another user
was running restore simultaneously and chose
the same application system name.
The restore process has had to rename the
application system to remove the duplicate.
Action : This is a warning message.
No errors have occurred but you
may want to rename the restored application.
CDA-06062,1, "Access control violation: Changes cannot be made. Application is invalid."
Cause : Application is not complete or has become corrupt.
Action : Application is no longer valid and should be deleted.
CDA-06063,0, "Mandatory values have not been set"
Cause : This error message is no longer used.
Action :
CDA-06064,0, "No Manager access privileges: Cannot create or modify application systems"
Cause : In order to Create, Update, Delete or Select from an
Application System the user must have Manager privilege.
Action : Obtain Manager privilege for this user from the
Repository owner.
CDA-06065,0, "User %0!s does not have access privileges to the repository"
Cause : You either typed in the wrong database user or you have not been
given access to the repository.
Action : Contact your repository manager and get them to give you access
to the repository.
CDA-06066,0, "Unable to share %0!s type %1!s. Elements may not be shared between different versions of the same application system"
Cause : Sharing an element between different versions of the same
application system
Action : Elements can only be copied between different versions of the
same application system
CDA-06067,1, "Unable to ascertain access rights on this element (%0!s) %1!s"
Cause : Force delete could not verify access on this element
Action : Use the normal 'delete' operation. This element may not be force
deleted.
CDA-06068,0, "Access control violation: %0!s is not shared into %1!s"
Cause : An access control violation was detected. Operations cannot be
performed or references made to elements that are not owned
or shared into the context application system.
Action : Share the element into the current application system and then
reissue the operation request.
CDA-06069,0, "User Defined Set %0!s is already checked-out to a Working Application. Repeat operation to confirm"
Cause : An attempt was made to check-out a 'Source Set' from a User Defined
Set that has already been checked-out or is a Working Set.
The check-out process would overwrite the existing version flags
if the operation was to continue.
Action : Repeat operation to confirm.
CDA-06070,0, "Error %0!s"
Cause : It was not possible to create all the tables and indexes necessary
for the Archive and Restore processes.
Action : Examine the error stack for further details of the Oracle error
which has occurred and consult your Database Administrator.
CDA-06071,0, "Failed to execute %0!s"
Cause : It was not possible to truncate one or more tables necessary for the
Archive and Restore processes.
Action : Examine the error stack for further details of the Oracle error
which has occurred and consult your Database Administrator.
CDA-06072,0, "Failed to execute %0!s"
Cause : It was not possible to drop all the tables and indexes necessary for
the Archive and Restore processes.
Action : Examine the error stack for further details of the Oracle error
which has occurred and consult your Database Administrator.
CDA-06073,0, "No applications exist for this transaction."
Cause : No applications were selected for the Archive/Restore process being
requested.
Action : Repeat the operation selecting the applications you wish to Archive/
Restore.
CDA-06074,0, "Invalid transaction reference."
Cause : The transaction reference which has been passed to the Archive/
Restore process is invalid.
Action : Repeat the process highlighting those applications you wish to be
Archived or Restored.
CDA-06075,0, "Not all members of the Archive Group have been selected. Application: %0!s Group: %1!s has not been selected."
Cause : When attempting to Restore an application group all members of the
application group must be selected.
Action : Repeat the operation selecting all members of the Application group
for restore.
CDA-06076,0, "Application %0!s was archived from Repository Version %1!s. The current Repository Version is %2!s."
Cause : It is not possible to Restore an application which was archived in
an earlier release of Designer without first performing an
upgrade of the tables used by the Restore process.
Action : Upgrade the tables used by the Restore process and repeat the
operation.
CDA-06077,0, "One or more applications failed to Restore."
Cause : It was not possible to restore all the applications selected for
restore.
Action : Examine the error stack for further details of the applications
which failed to restore.
Correct the errors and repeat the operation.
CDA-06078,0, "The new name %0!s given for Application %1!s already exists in the repository."
Cause : An application has been given a new name which already exists in the
repository.
Action : Repeat the operation specifying a new name for the application which
does not already exist in the repository.
CDA-06079,0, "%0!s: This element is locked, shared or read only and cannot be altered."
Cause : This element or its parent has its LOCKED_FLAG set to 'L', 'R' or
'S' indicating that it is Locked, Read-Only or Shared.
This element cannot be deleted or updated while it is locked.
Action : Unlock or Check-in the locked set, or Unshare it.
CDA-06080,0, "Application System %0!s has got a %1!s User Defined Set %2!s."
Cause : There is a locked User Defined Set in the Application System
which is checked out.
Action : Continuing will override the locked status of the User
Defined Set. Otherwise this operation will halt.
CDA-06081,0, "Invalid Repository versions"
Cause : Tried to copy an Application system from one repository to another
with different version numbers.
Action : Copy to another repository with the same version number or upgrade
repository or use Archive/Restore.
CDA-06082,0, "Elements have been shared from application systems that are not being copied"
Cause : One or more application systems have shared elements from
applications systems that are not being copied.
Action : To copy application system between repository with shared elements
you have to select the owning application system as well.
Select applications systems and try again.
CDA-06083,1, "Access control violation: Changes cannot be made to a locked application"
Cause : Changes are not allowed to locked application systems.
Action : Unlock the application system before attempting to perform
operations on its elements.
CDA-06084,1, "Unable to transfer entity %0!s. Entity is a subtype of another entity."
Cause : The entity could not be transferred to a different application
because it is a subtype of another entity.
Action : Either transfer the supertype of this entity, (all its subtypes will
also be transferred), or nullify the supertype property of this
entity, and repeat the transfer operation.
CDA-06085,1, "Cannot copy: invalid reference to %! : %!. Please change copy rules."
Cause : Could not copy element as the action would result in an
invalid reference to another repository object.
Action : Amend the copy rules to include the element
pointed to by the invalid reference.
CDA-06086,1, "Unable to identify type body for Oracle Object Type %0!s"
Cause : An attempt was made to transfer an Oracle Object Type
but the transfer utility could not identify the type body
applicable to the Oracle Object Type.
Action : Use the RON to examine the Oracle Object Type and ensure it has
a valid type body. Repeat the transfer operation.
CDA-06087,1, "Access control violation: %0!s with reference %1!s not found in work area"
Cause : During access control checks, it was detected that a reference
property supplied for an element does not correspond to an element
in the work area.
Action : Include the missing element in the work area
CDA-06088,1, "Owning folder not found for element type %0!s , name: %1!s "
Cause : Access control violation.
In order to determine the access rights of the specified element
the owning folder must be contained within the work area views.
Action : Include the owning folder in the work area
CDA-06089,1, "%0!s: Unable to lock Primary Access File %1!s referenced by %2!s "
Cause : When locking this element type an attempt is
made to lock all primary access files
referenced by each file usage on the owning classifier.
The lock failed because the Primary Access File
is not contained in the context workarea.
Action : Modify the context workarea to include the Primary Access File
and repeat the operation.
CDA-06097,0, "Invalid Version number"
Cause : The new VERSION number must be an integer between 2 and 999, and
must be greater than the latest VERSION number.
Action : Enter a valid VERSION number.
CDA-06098,0, "Unable to determine the Repository Owner"
Cause : The utility which takes out Application Exclusive locks needs to
determine the owner of your repository. The utility was unable to
do so.
Action : Repeat the operation. If the problems persists contact your
Repository Administrator.
CDA-06099,0, "%0!s : CONTAINER_REFERENCE must be set unless moving a Container to be top level"
Cause : When calling move_pac(..), CONTAINER_REFERENCE must be set to a
valid target Container, except when the element to be moved is
a Container which is to be made a top level container.
Action : Specify the target Container where this PAC is to be moved to, or
specify a Container in PAC_IRID.
CDA-06100,0, "%0!s: Project Containers cannot own objects"
Cause : Objects cannot be inserted into or moved into Projects. Only
Folders, Application Systems and Packages may own objects.
Action : Insert or move your object into another type of Container.
CDA-06101,0, "%0!s: Cannot copy a Container into itself"
Cause : Cannot copy a container element (application system, folder,
package or project) into itself.
Action : Select another container element to be the owner of this
container, or set the context container to be null to make a copy
of this container a root container.
CDA-06102,0, "%0!s : Cannot share an element into a container of which it is already a mem"
Cause : An element type cannot be shared into a container (application
system, folder, package or project) to which it is linked via
a folder member, whether by ownership or a previous share.
Action : Do not try to share this Element Type into this Folder.
CDA-06103,1, "%0!s: Only primary access elements (PACs) may be moved"
Cause : Secondary access elements (SACs) or intersection elements may
not be moved to another container.
Action : Either move this element's parent PAC element to another container
or copy this element to another PAC.
CDA-06104,0, "Cannot move element %0!s - target container %1!s is within same hierarchy"
Cause : Attempting to move an element to
become a child of one of its own
sub-elements
Action : Move element to a destination
outside its own hierarchy
CDA-06105,0, "Cannot move : %0!s into itself"
Cause : Source element and target element
are the same. Cannot move
element into itself.
Action : Move element to another
destination
/
/ 07000 .. 07099 Unknown
/
CDA-07000,1, "%0!s is a checked out set. Repeat operation to unlock set."
Cause : An attempt was made to unlock a set which is currently
checked out to a working application system. Unlocking
this set will reset the status of the set and all its members
from 'CHECKED OUT' and 'LOCKED' to 'UNLOCKED'.
It will not then be possible to run the checkin operation
on this set to accept the changes from the working
application system.
Action : Repeat the operation to override this warning message
and successfully UNLOCK the set.
CDA-07003,0, "Unable to CheckIn User Defined Set %0!s The members of this User Defined Set are not checked out."
Cause : Attempting to CheckIn to a user defined set which contains set
members which have not been checked out.
Action : Checkout the set from the Source Application before proceeding
with the CheckIn operation.