In Datastage 8.5, There is Xmeta in Database and the Repository (DS_JOBS / DS_JOBOBJECTS etc) in hashed files also.
Locks can be still cleared using DS.TOOLS. And aswell using Datastage Admin Webconsole.
May I know why is there two different places the metadata is been maintained?
Or what is maitained in Xmeta and what is in OS hashed file repository?
I understand that there is some extra feature such as DS_AUDIT and more reporting feature is avaialble in XMeta.
Anything else?
Xmeta vs Hashed files
Moderators: chulett, rschirm, roy
I think the goal is to eliminate all the hashed files and only use XMETA. I am guessing that took longer than expected or there were performance issues. So they are eliminating slowly and duplicating data because XMETA is supported across multiple product lines.
Only IBM knows for sure why it is this way.
Only IBM knows for sure why it is this way.
Mamu Kim
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The local repository (which you have called "hashed files" and which was originally built on the UniVerse RDBMS) is the original, and continues to be used primarily for design-time operations so that you don't commit anything to XMETA until you are ready to. For performance reasons you can also specify local job logging.
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It's always connected (via services) to XMETA. Your Information Server roles and DataStage credentials are stored in XMETA - you could not log in were they not there.
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.