Having Errors When Connecting to MSSQL DB

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
DS_SUPPORT
Premium Member
Premium Member
Posts: 232
Joined: Fri Aug 04, 2006 1:20 am
Location: Bangalore

Having Errors When Connecting to MSSQL DB

Post by DS_SUPPORT »

We have a simple job with some 2 hashed File lookups. Our Job design is

Code: Select all

                 LKP1 LKP2
                  |      |
                  V      V
DRS --- IPC--TRANSFORMER --- IPC--DRS
We are using DRS stage, because customers can configure it to run on any database. When testing this job, it is running perfectly when oracle is used as Source and target.

But it is failing when MSSQL Server is used as source and target, we are getting the error like

Code: Select all

DataStage Job 741 Phantom 4936
Program "DSP.Close": Line 94, Exception raised in GCI subroutine:
Access violation.
Attempting to Cleanup after ABORT was raised in stage JOBNAME..TransformerName
Program "DSD.INTClose": Line 141, Unable to open the operating system file "DSD_BP.O/%".
[ENOENT] No such file or directory
Program "DSD.INTClose": Line 141, Unable to load file "".
Program "DSD.INTClose": Line 141, Unable to load subroutine.
I tried searching another posts with similar issue, but could not find the solution. And i did have a look on the line 94 in DSP.Close

Code: Select all

00089 002CC : 0F8 move           "DSTAGE_RUN_E_0243"  => _T0006 
00089 002D2 : 0F8 move           "Error %1 in $DSP.Abort"  => _T0007 
00089 002D8 : 196 subr           "*DataStage*DSR_LOADSTRING" _T0006 _T0007 GCI.RESULT  => ERROR 
00090 002E6 : 0C2 jump           004A2: 
00091 002EC : 0C2 jump           00344: 
00092 002F4 : 2DE testfw         1 00344: 
00093 002FC : 0F8 move           0  => GCI.RESULT 
00094 00302 : 01E call           "$DSP.Close" HANDLE GCI.RESULT 
00095 0030C : 106 ne             GCI.RESULT 0  => $R26 
00095 00314 : 2DE testfw         $R26 0033C: 
00096 0031C : 0F8 move           "DSTAGE_RUN_E_0244"  => _T0008 
00096 00322 : 0F8 move           "Error %1 in $DSP.Close"  => _T0009 
00096 00328 : 196 subr           "*DataStage*DSR_LOADSTRING" _T0008 _T0009 GCI.RESULT  => ERROR 
00097 00336 : 0C2 jump           004A2: 
00098 0033C : 0C2 jump           00344: 
00100 00344 : 0F8 move           0  => GCI.RESULT 
00101 0034A : 01E call           "$DS.ANYCLOSE" HANDLE GCI.RESULT 
But it is calling $DSP.Close, so i dont know how to proceed after this.

We are wondering why this error is coming when connecting to SQL Server DB alone and that too it is occuring only for some jobs and not for all jobs. Can someone suggest, how to proceed with this?
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

No idea, but have you tried to determine what the jobs that fail have in common? Perhaps looks at the datatypes being selected or the nature of the sql being run and see if there's any common element, when it has this kind of field it doesn't work and when there is no field of this type it works?
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

DSD_BP.O/% is not a valid pathname, yet this is where the failure is occurring - DataStage is presumably trying to load one of the routines in the DSD_BP.O directory, but somehow has identified a catalog name of "%".

I think this one needs to go to your official 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.
Post Reply