Reasons Claims and Flushes can Fail

Running Global Projects

Using Extracts with Global Projects : Reasons Claims and Flushes can Fail

Reasons Claims and Flushes can Fail

Claims and flushes may fail for valid reasons. If a flush has failed (e.g. due to a name clash), all subsequent flushes will stall (Previous flush failed) until the failed flush has been reset.

Claims are treated as failing unless all elements have been claimed. Thus if 10 claims have succeeded and 1 has failed, the Claim command is treated as having failed. The Extract Control form in DESIGN, DRAFT and other modules contains more detailed reporting.

Here is a list of some common symptoms and the underlying causes:


Symptom	Cause
Unable to savework. Perhaps you have been Expunged	Daemon has been expunged. Modifications to database (other than updates) will fail.
Flush may have overtaken another flush. Previous flush could not be found	In this case, the Flush will stall for a retry.
Previous flush failed	Subsequent flushes will fail until failed flush has been reset.
Unable to claim <item> because element is already claimed by <extract or user> from Extract <no>	Valid failure ‑ another extract or user has it claimed
Unable to claim <item> from parent extract <no> because element is modified in a later session.	EXTRACT REFRESH is required, to bring the child extract’s view of the parent up to date
Nothing to claim locally ‑ all claims failed in owning extract	Cannot claim to child extract, because failed to claim anything from its parent
You cannot claim <item> without doing an extract claim from the parent extract	The item has not been claimed into the extract before the User has claimed it. This is only applicable to Explicit dBs.
Unable to claim <item> from parent extract <no> as element has been deleted in a later session	The item has been deleted in the parent, and the child extract has not been brought up to date yet.
Element reference <item> is invalid or has been deleted	The reference number of <item> cannot be found in the database, it is an invalid reference number.
Element <item> has been modified, so cannot be released. Savework must be done first	The item must be saved the database before an extract operation can be undertaken on it.
Element <item> has been deleted by another User	The item you are trying to Claim has been deleted by another user.
Name clash on <item>. Please rename	The name of the item that has just been created already exists.
Cannot flush/abandon <item> as old and new owners must both be in the list, or neither in the list	The parent of the owner has been changed. Both the old and the new owners need to be flushed/issued/abandoned at the same time, and the list currently only contains one or the other.
Cannot flush/abandon <item> without its owner	The item is either new or moved to a another item. Both need to be flushed/issued/abandoned at the same time.
Cannot flush/abandon <item> without its members	The member list of item has changed in some way. The item needs to be flushed/issued/abandoned with its members.
Cannot abandon/release <item>. Element is claimed out by a user (maybe yourself) or to an extract	The item is claimed by a User (possible the user doing the EXTRACT ABANDON/RELEASE) or to a child extract.
Element <item> kerror <no>	Internal error. Please contact AVEVA support desk for more information.
Dabacon error <NUMBER> for DB <item>	Internal error. Please contact AVEVA support desk for more information.

1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.