Hi All.
I am able to remove datasets usings orchadmin command.
but we have a situation where dataset files are removed but the child descriptor files in node1 node2 still existing .
so to remove these descriptor files by using orchadmin we do not have datasets .
so please let me know what is the best to remove datasets.
removing descriptor files when datasets do not exist
Moderators: chulett, rschirm, roy
Please try using search before posting. These are called orphaned datasets and are not trivial to fix. A very good post on the process was written by Arndt and it is covered in a FAQ: viewtopic.php?t=107450
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
Not sure why but clicking the link tells me
Can you please post the text here?
Sorry, but only users granted special access can read topics in this forum.
![Sad :(](./images/smilies/icon_sad.gif)
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Descriptor files are not "in node1 node2".
There is only one descriptor file per Data Set; the descriptor file has a name with a ".ds" suffix.
The data files in the directories nominated as resource disk in the configuration file are known as "segment files".
So please advise whether it is the descriptor file or the segment files that have been deleted, so that cogent advice may be provided.
There is only one descriptor file per Data Set; the descriptor file has a name with a ".ds" suffix.
The data files in the directories nominated as resource disk in the configuration file are known as "segment files".
So please advise whether it is the descriptor file or the segment files that have been deleted, so that cogent advice may be provided.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.