Text |
Error text not available. |
Text |
NSD model has no domain reference. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB online services and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Input is an unqualified non existing ERE for multiple domain. |
Explanation |
This error should only occur in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
"OR" expected in domain/value specification. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Illegal input: model is singular. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Missing built-in ID. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Illegal input after "," in dom/value spec. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
"DDE" is not allowed here as domain specification. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
AX-node expected. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Unexpected end of text in Search Buffer. |
Explanation |
A direct call or a FIND NATIVE was issued with a syntax error in the Search Buffer. |
Action |
Check program and correct error. |
Text |
Illegal recursion in error handler. |
Explanation |
The Entire DB nucleus detected an unexpected situation that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB, terminate your Natural session and start a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Attribute sublist of model not found. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
User or DLOGON library not found. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Illegal format specified for descriptive attribute. |
Explanation |
For each descriptive attribute only specific formats are allowed. This error may occur in the case of an erroneous definition of descriptive attributes or if an illegal format has been specified in the format buffer for a direct call. |
Action |
Contact your Entire DB administrator. |
Text |
Bad response code from built-in (ext) routine. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
New occurrence stored is not in buffer. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Not even 1 page obtained (contradiction). |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Page ISN not in core when bit says it should be. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
AX-node for relation group has not been found. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Tried to delete DLOGON library or user. |
Explanation |
It is not allowed to delete the current DLOGON library or user. |
Action |
DLOGON for GLOBAL-LIBRARY or another user. Retry to delete library or user. |
Text |
Missing component sublist. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Occurrence has no reference for PENDING CHANGE RECORDS. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Reference to non-existing ERE found in a DV node (EXPORT). |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Number of nodes on top level sublist = 0. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
More than 1 sublist attached. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
"RECURSIVELY" not allowed in attribute-list. |
Explanation |
A direct call or a FIND NATIVE was issued with a syntax error in the Search Buffer. |
Action |
Check program and correct error. |
Text |
Illegal connector in attr/comp sublist (not "OR" OR ","). |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Only one attribute allowed to be specified for occurrence. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Illegal input in DELETE clause of UPDATE command. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Attribute options not allowed in domain/value spec. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Domain element is not a valid ERE name. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Category qualification is illegal for a category. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Non existing ERE entered as category qualification. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Illegal category qualification. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Internal error: reference to modify not found. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Category delete rejected, because occurrences involved. |
Explanation |
A category delete is rejected, because of one of the following: 1) The category to be deleted is an ER-category for which occurrences exist. 2) An ER-category for which non dummy occurrences exist becomes invalid, for example because it has the category to be deleted as attribute. For more details, see Entire DB documentation. |
Action |
Delete the occurrences involved before deleting the category. |
Text |
Category update was rejected, because occurrences are involved. |
Explanation |
Category updates are rejected, if: 1) An entity category becomes invalid for non dummy occurrences, for example, because you add a non existing attribute to an entity category or a group category. 2) The category update requires that occurrences would have to be adapted, for example, if an attribute is deleted (exception: non inverted descriptive attributes may always be deleted). For more details, see Entire DB documentation. |
Action |
1) Define attribute categories before using them as attributes. 2) Delete the occurrences involved before updating the categories. |
Text |
Missing sublist. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Missing attribute sublist in model. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Relation elements of a relationship cannot be updated. |
Explanation |
The relation elements are defined when the relationship is stored, and it is not allowed to update them. |
Action |
Delete relationship and store new relationship. |
Text |
Tried to change primary name of an occurrence of an entity category defined with the "STORE NAMES" option. |
Explanation |
It is not allowed to change the primary name of an occurrence of an entity category defined with the "STORE NAMES" option, because this option causes the primary name of a referenced occurrence to be stored in the referencing ERE to optimize the access to the linkage attributes, and, therefore, all EREs referencing the referenced ERE would have to be updated. |
Action |
Delete entity and store new entity with the new name or contact your Entire DB administrator to reorganize your Entire DB database. |
Text |
Illegal "DELETE" body. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Updated higher level cat. becomes invalid: Subcategories. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Attr/Comp/Domain element to add already exists in category. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Illegal modification type. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Not implemented: Subcat for multiple version category. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |