There are a couple of topics that mention this error, but no one seems to answer the question, "Why does DataStage generate the following SQL Statement?".
SELECT DISTINCT "Computer", "SoftwareProduct", "DataStore" FROM MetaStage_Loc_Info
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'MetaStage_Loc_Info'.
It seems to be an unnecessary overhead. Does anyone know what triggers DataStage to make this call, and whether or not there is a way to tell it not to?
Thanks in advance,
Heather
Invalid object name 'MetaStage_Loc_Info'
Moderators: chulett, rschirm, roy
Invalid object name 'MetaStage_Loc_Info'
what a man is contributes much more to his happiness than what he has, or how he is regarded by others.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The job is running in MetaStage proxy mode, and DataStage is attempting to determine information from MetaStage about the job in question (the same information is also stored in DataStage - it is seeking to compare the two).
What I suspect is happening is that your job was created in an earlier version, and the token "MetaStage_Loc_Info" was correct then but "they" have since changed it.
Check with your support provider.
What I suspect is happening is that your job was created in an earlier version, and the token "MetaStage_Loc_Info" was correct then but "they" have since changed it.
Check with your support provider.
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.
-
- Premium Member
- Posts: 15
- Joined: Wed Feb 20, 2008 3:33 pm