Datastage Server 7.5.1A migration issue to 7.5.3

[sunayan_pal]

HI I recently upgrade the Datastage server fronm 7.5.1A to 7.5.3 .
everything work fine except the following .
while i am using the DRS stage to connect to the database ( SQL server 2000)

Project:tmnt_uat(prxetl1)
Job name:jbPjS_I06_CLR_Dept
Event #:69
Timestamp:30/06/2008 13:58:37
Event type:Fatal
User: dsadm
Message:
main_program: Fatal Error: Fatal: Shared library (drsenu.so) failed to load: errno = (8), system message = (rtld: 0712-001 Symbol DSPIMallocStageName was referenced
from module /home/dsadm/Ascential/DataStage/DSEngine/lib/drsenu.so(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol DSCRegisterPassive was referenced
from module /home/dsadm/Ascential/DataStage/DSEngine/lib/drsenu.so(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol ds_writelog was referenced
from module /home/dsadm/Ascential/DataStage/DSEngine/lib/drsenu.so(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol DSCLoadResourceEx was referenced
from module /home/dsadm/Ascential/DataStage/DSEngine/lib/drsenu.so(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol DSCDeclareProperty was referenced
from module /home/dsadm/Ascential/DataStage/DSEngine/lib/drsenu.so(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol DSCPropDefaultFromStr was referenced
from module /home/dsadm/Ascential/DataStage/DSEngine/lib/drsenu.so(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol DSCUVValueMark was referenced
from module /home/dsadm/Ascential/DataStage/DSEngine/lib/drsenu.so(), but a runtime definition
of the symbol was not found.
Additional errors occurred but are not reported.)

Could you please provide me the solution.

[sunayan_pal]

hi all ,
it get resolved by doing a few change in the operator config file

[ray.wurlod]

Please be more specific about what those changes were and, in particular, which of them wrought the fix!

[sunayan_pal]

hi All ,

Got one more error while using the DRS stage.
not sure why it is happening.

APT_CombinedOperatorController,0: Fatal Error: Fatal: [DataDirect][ODBC lib] Function sequence error
SQLNumResultCols: Error retrieveing columns in the result set
Plug-in stage property (WHERE_CLAUSE) is not defined for Input Links

node_node1: combination of 3 operators [odSchedule_Data; APT_TransformOperatorImplV0S133_jbHRP_I02_UPD_00_BkupTable_xFMT in xFMT; odSchedule_Data_Bkup], partition 0 of 1, processID 376,904 on node1, player 1 terminated unexpectedly.

Any clue how to resolve

[ray.wurlod]

Please disable operator combination so that you can learn which operator is throwing the error.

[ray.wurlod]

*Topic Relocated- Content Editor*

[sunayan_pal]

Could you please let me know HOw to disable the operator combination.

I guess at the base level DRS stage is using the Generic ODBc to connect to the target database.
SO it may be a problem with ODBC connection.

This job was very well working in 7.5.1.A but failed in 7.5.3.

[ray.wurlod]

Bring environment variable APT_DISABLE_COMBINATION into your job as a job parameter and, when you run the job, set it to True.

[sunayan_pal]

Hi Ray,

I run it with the Enviornment variable

I got the following error:

drsCLR_UKCUSTOM_CUSTOM_DRIVERS,0: Failure during execution of operator logic.

drsCLR_UKCUSTOM_CUSTOM_DRIVERS,0: Fatal Error: Fatal: The 0 column(s) defined on this link do not match the 0 column result set generated by the SQL statement: %3.
Plug-in stage property (WHERE_CLAUSE) is not defined for Input Links

node_node1: operator [drsCLR_UKCUSTOM_CUSTOM_DRIVERS], partition 0 of 1, processID 733,290 on node1, player 3 terminated unexpectedly.

main_program: Unexpected exit status 1

main_program: Step execution finished with status = FAILED.

[sunayan_pal]

the stage used is a DRS stage

the SQL used in that Stage is as followed:

INSERT INTO UKCUSTOM_CUSTOM_DRIVERS (CUSTOMID) VALUES (?)


Before sQL Statement:

DELETE FROM UKCUSTOM_CUSTOM_DRIVERS WHERE CUSTOMID <> '';

there is no After command used.

[ray.wurlod]

You have no columns defined on the input link.

But you have one parameter marker in the SQL.

This is not a correct combination, which is what the error message is telling you.

[sunayan_pal]

You have no columns defined on the input link.

But you have one parameter marker in the SQL.

This is not a correct combination, which is what the error message is telling you. ...

Hi Ray,

the same piece of code was working fine in the version 7.5.1a but not in 7.5.3

i had contact to IBM . they had intimated that a patch need to be insstalled for this.

[ray.wurlod]

You were relying on something that did not work properly, and has now been fixed. The patch will un-fix it, so that previous behaviour can resume. A better solution would be to get the logic of the job design correct.

[sunayan_pal]

Hi ,
Initially the job logic was DRS at the target side and was unable to execute the before and after SQL.

Since it was a staging table and the only objective was to truncate / delete as per the business area.

now i use it in the source end and use the logic.

while reading the data from the table a where clause with condition 1=0
and then an after SQL doing the same ( truncate / delete ) the table.

this is an alternative of the job design.

[sunayan_pal]

the following are the files which need the treatment to make the DRS stage operational.

drsenu.so
drsjpn.so
drsodbc.so
drs.so
libdsplugin.so
liborpheus.so

After adding this files the DRS stage even at Target Stage is Working.