View previous topic :: View next topic
|
Author |
Message |
satinspace
New User
Joined: 28 Sep 2005 Posts: 3
|
|
|
|
Hi all,
I am encountering an error status 0226 while executing an ERASE statement. The record which is being erased is present in the database and it is obtained making it current before executing the ERASE. The OBTAIN statement was successful but I am getting an 0226 error for the ERASE. Below is the ERASE statement used in the code.
ERASE <Record name> PERMANENT MEMBERS
Please provide me any possible reasons for this error. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello and welcome to the forum,
I don't "do" idms, but does this not point to the problem (the bold is mine)?
Quote: |
26 Either no duplicates exist for the named record or the record name or SPF index entry cannot be found. |
|
|
Back to top |
|
|
Uday Kumar R
New User
Joined: 07 Nov 2007 Posts: 27 Location: Mumbai
|
|
|
|
Hi,
Probably an broken chain issue. Try to use the command
Erase <Record name> members all
Please let me know if i am wrong. |
|
Back to top |
|
|
satinspace
New User
Joined: 28 Sep 2005 Posts: 3
|
|
|
|
Hi Uday,
Thanks for the reply. Can you explain more about the broken chain issue you were talking about?.. |
|
Back to top |
|
|
sudharsan.soundararajan Warnings : 1 New User
Joined: 15 Oct 2008 Posts: 17 Location: Chennai
|
|
|
|
Hi All,
I too want to Know about the BROKEN-CHAIN.
Satinspace,
Is this abort coming for the first record itself or when trying a series of data.
Please forgive me if i am wrong. |
|
Back to top |
|
|
Uday Kumar R
New User
Joined: 07 Nov 2007 Posts: 27 Location: Mumbai
|
|
|
|
Hi Santosh and Sudarsan,
I am not aware in details the reason behind why the issue exactly happens. As per my knowledge - A bad db key has get extracted from a record's , while it was moving in the record set.
Another version is say suppose when a update job running in local mode and after completeion of this job all the areas to be recovered once completion of the run unit, if they are not recovered properly then issue may happens.
One more version is if a retreval job try to retreive a record while an update job using the same record for updating purpose, at that time there is possibly of loosing the currency it is also called as Broken chain.
Usually if this happens in any job, we hold for a couple of minutes and run the job from abending step which executes properly in the next run.
Please let me know if i am going wrong.
Regards,
Uday |
|
Back to top |
|
|
satinspace
New User
Joined: 28 Sep 2005 Posts: 3
|
|
|
|
Thanks everyone for your help.
This issue has been resolved finally. The record which I was trying to erase was a part of a set which was corrupted. This was discovered by our DBA. This corruption was patched out using the IDMSPFIX (fix page) utility. Then the record was successfully erased from DB. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Good to hear it is now working - thank you for letting us know
d |
|
Back to top |
|
|
|