Phantom Warnings ODBC
Moderators: chulett, rschirm, roy
Phantom Warnings ODBC
We are getting Phantom Warnings in our Job Logs, when connecting to SQL Server using ODBC. The same jobs work fine on other servers, and were working fine a few days ago. Anybody come across this before?. I have tried using ODBC tracing but it all looks normal.
e.g.
Item #: 65
Event ID: 64
Timestamp: 2006-07-26 09:07:15
Type: Warning
User Name: dvmri
Message: DataStage Job 428 Phantom 4826
Warning:
[DataDirect][ODBC SQL Server Driver][SQL Server]
DataStage Phantom Finished
Item #: 66
Event ID: 65
Timestamp: 2006-07-26 09:07:15
Type: Warning
User Name: dvmri
Message: DataStage Job 428 Phantom 19346
Warning:
[DataDirect][ODBC SQL Server Driver][SQL Server]
Warning:
[DataDirect][ODBC SQL Server Driver][SQL Server]
Warning:
[DataDirect][ODBC SQL Server Driver][SQL Server]
DataStage Phantom Finished
e.g.
Item #: 65
Event ID: 64
Timestamp: 2006-07-26 09:07:15
Type: Warning
User Name: dvmri
Message: DataStage Job 428 Phantom 4826
Warning:
[DataDirect][ODBC SQL Server Driver][SQL Server]
DataStage Phantom Finished
Item #: 66
Event ID: 65
Timestamp: 2006-07-26 09:07:15
Type: Warning
User Name: dvmri
Message: DataStage Job 428 Phantom 19346
Warning:
[DataDirect][ODBC SQL Server Driver][SQL Server]
Warning:
[DataDirect][ODBC SQL Server Driver][SQL Server]
Warning:
[DataDirect][ODBC SQL Server Driver][SQL Server]
DataStage Phantom Finished
-
- Participant
- Posts: 94
- Joined: Wed May 08, 2002 8:44 am
- Location: Germany
- Contact:
Re: Phantom Warnings ODBC
Identify the entries in the project phantom directory &PH& (timestamp) and see if you can get some more information from there.
Klaus
Klaus
loveojha2
I tried a reset too but I just get a repeat of the same messages.
What I am trying to do is have our jobs run without any warnings. The project is on a production box and will go live in a couple of weeks. The way we have the sequences setup is to abort when they see warnings.
I don't want to go through all our sequence links and change them to allow warnings. Then you wouldn't know whether a warning has been generated for this reason or another more serious issue.
Alan
I tried a reset too but I just get a repeat of the same messages.
What I am trying to do is have our jobs run without any warnings. The project is on a production box and will go live in a couple of weeks. The way we have the sequences setup is to abort when they see warnings.
I don't want to go through all our sequence links and change them to allow warnings. Then you wouldn't know whether a warning has been generated for this reason or another more serious issue.
Alan
My question was more on the particular job that is having issue,What I am trying to do is have our jobs run without any warnings.
What is it having (the design)?
Are you having any thing parameterized, is there any chance that you are having a parameter value difference (between the servers)?
Success consists of getting up just one more time than you fall.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Any time SQL Server generates an informational message, DataStage logs it as a warning, because it regards receiving messages from the database or ODBC driver as "unusual". Unfortunately you can not change this behaviour in DataStage. Is there an environment variable you can set so that SQL Server does not generate informational messages ?
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.
Resolved!
The solution was:-
1) Take an export of the Jobs, Routines and Transform code, but without any executables.
2) Then re-import and perform a re-compile of everything.
Don't ask me why this has fixed it but it has!
Thanks for all your responses
Alan
1) Take an export of the Jobs, Routines and Transform code, but without any executables.
2) Then re-import and perform a re-compile of everything.
Don't ask me why this has fixed it but it has!
Thanks for all your responses
Alan
This happened because may parameter get binded with the executablesDon't ask me why this has fixed it but it has!
And if you execute them directly (without a fresh compile), instead of taking the current value in place of $PROJDEF, they take whatever was already binded
Experts please clear my doubt.
Success consists of getting up just one more time than you fall.