Text |
MULTIPLE VERSIONS + LIBRARY INDEPENDENT: mutually exclus. |
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 |
"MULTIPLE VERSIONS" only allowed for entity cat. and rel. |
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 |
Attempt to delete the only domain element of a domain cat. |
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 |
Conflicting null suppression options. |
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 |
Invalid category table. |
Explanation |
EXPORT/IMPORT requires a valid category table. |
Action |
Rerun the export/import jobs with a Natural system containing the valid category table. |
Text |
Conflicting "UNLOAD" options. |
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 |
Premature end of workfile found when importing. |
Explanation |
Either a workfile is being used which has been generated by an export program that did not end properly, or the import program has read records using READ WORKFILE, which should have been read by an IMPORT statement, or an IMPORT has been executed, even though END OF WORKFILE has already been reached. |
Action |
Check workfile and export/import programs. Rerun export job or correct error in export or import programs. |
Text |
Category "LIBRARY" is not defined in new dict. |
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 record type found in workfile. |
Explanation |
A record which would have had to be read with READ WORKFILE was not read. |
Action |
Check program and correct error. |
Text |
END OF FILE encountered when reading WF-HEADER. |
Explanation |
Either a workfile is being used which has been generated by an export program that did not end properly, or the import program has read records using READ WORKFILE, which should have been read by an IMPORT statement, or an IMPORT has been executed, even though END OF WORKFILE has already been reached. |
Action |
Check workfile and export/import programs. Rerun export job or correct error in export or import programs. |
Text |
"ATTRIBUTES" 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 |
Category sublist encountered for a group attr. |
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 |
ERE entered is not a sub-category to the attribute. |
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 |
Importing references to categories not implemented. |
Explanation |
An ERE to be imported references a category. Such references cannot be loaded at this time. |
Action |
Define attributes which reference categories with "NO LOAD/UNLOAD" option or write an export/import programs without using the EXPORT and IMPORT statements. |
Text |
Contradiction: Domain ISN exists, but no ERE ISN. |
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 |
Bad names entry found in names record. |
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 |
Contradiction: "Old" ERE exists but not category. |
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 "taken over" doesn"t exist. |
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 category qualifier for non existing ERE. |
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 relation element. |
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 |
Sublist specification for non existing ERE. |
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 |
Sublist entered for domain does not match model. |
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 node encountered in model domain 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 parent anchor in top level Sublist stack entry. |
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 |
Only references to occurrences are allowed. |
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 |
Sublist stack overflow. |
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 |
Unexpected node. |
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 contains extension record. |
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 |
Extension record to be deleted locked. |
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 |
AD 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 |
Attempted to set primary name to blank. |
Explanation |
Each entity must have a primary name which is not blank. |
Action |
Check program and correct error. |
Text |
Missing AMONG clause for relation. |
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 |
In a STORE/UPDATE statement an ISN has been specified for a linkage attribute, but an ERE with this ISN does not exist. |
Explanation |
Either an invalid number has been used, or the ERE to be referenced has been deleted. |
Action |
Check whether ERE to be referenced is still existing. If yes, check program and correct error. |
Text |
No name/relation-element specified for ERE to be stored. |
Explanation |
Each entity must have a primary name and each relationship must have at least one relation element. |
Action |
Check program and correct error. |
Text |
ISN spec. for linkage attribute is ISN of a version record. |
Explanation |
In a STORE/UPDATE statement, the ISN specified for a linkage attribute is the ISN of a version record. Probably *ISN of a "FIND VERSIONS" statement has been specified. |
Action |
Check program and correct error. |
Text |
Directory name hasn"t been found when it should have been. |
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 |
ISN of ERE to be processed is version ISN. |
Explanation |
Probably the statement where the error occured is contained in a FIND VERSIONS loop. The statement is only allowed for the current version of an ERE. |
Action |
Check program and correct error. |
Text |
User written built-in routine has not been linked. |
Explanation |
A user-defined built-in routine has been used. This built-in routine has not been linked to Natural. |
Action |
Contact your Entire DB administrator. |
Text |
Duplicate names error. |
Explanation |
Names must be unique within a library cluster for an entity category. For a relationship category, the combination of relation elements must be unique within a library cluster. |
Action |
If you tried to store a new ERE: update the existing one. If you tried to rename an ERE, choose a unique name. |
Text |
Illegal attribute ISN specified for stuffing. |
Explanation |
The Entire DB nucleus detected an unexpected situation, which probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB, terminate the Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Work area overflow. |
Explanation |
Overflow of internal work area in Entire DB nucleus occurred. |
Action |
Contact Software AG Entire DB maintenance staff. |
Text |
Overflow of work area for command ID management. |
Explanation |
There are too many active sets. |
Action |
Release sets no longer needed. Retry. |
Text |
Illegal continuation after "ERE". |
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 |
NSD DV-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 |
Report number expected: number between 0 and 32. |
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 |
Need to change code in routine due to MAX#RELS <> 10. |
Explanation |
The Entire DB nucleus detected an unexpected situation which probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB, terminate the Natural session and start a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |