Page 1 of 1
Phantom Warnings ODBC
Posted: Wed Jul 26, 2006 4:29 am
by AlanP
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
Re: Phantom Warnings ODBC
Posted: Wed Jul 26, 2006 4:37 am
by Klaus Schaefer
Identify the entries in the project phantom directory &PH& (timestamp) and see if you can get some more information from there.
Klaus
Posted: Wed Jul 26, 2006 4:48 am
by AlanP
Klaus
Thanks for the suggestion but I have checked in there already. The phantom ids in the files in there don't correspond to the ones appearing in the logs anyway.
Regards
Alan
Posted: Wed Jul 26, 2006 4:51 am
by loveojha2
Do a reset through the director and see if it gives any thing extra.
What are you trying to do?
Posted: Wed Jul 26, 2006 5:02 am
by AlanP
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
Posted: Wed Jul 26, 2006 5:08 am
by loveojha2
What I am trying to do is have our jobs run without any warnings.
My question was more on the particular job that is having issue,
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)?
Posted: Wed Jul 26, 2006 4:49 pm
by ray.wurlod
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 ?
Resolved!
Posted: Thu Jul 27, 2006 3:41 am
by AlanP
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
Posted: Thu Jul 27, 2006 7:06 am
by loveojha2
Don't ask me why this has fixed it but it has!
This happened because may parameter get binded with the executables
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.
Posted: Thu Jul 27, 2006 7:13 pm
by kumar_s
You could have just recompiled, with export-import.
Posted: Mon Jul 31, 2006 8:33 am
by AlanP
kumar_s
I tried that but it didn't clear the problem. By deleting the jobs, then re-importing, you force DS to use new RT_BP### and RT_BP###.O directories where ### is a new Job number.