TDMS 4.0 "Data Selection Start for All Tables Step" ST22 Problem!!

[former_member205643]

Hello Everybody,

We have in the process of a TDMS 4.0 Project.

Our source system is ECC60 SR3, Database version is DB2 9.5.0.2 Fix pack 2

At the source system we have stucked by an ST22 short dump caused by TDMS step Data Selection Start for All Tables.

ST22 error simply covers a DB2 SQL Dump called

How to correct the error     Database error text........: "SQL0901N The SQL statement failed because of a      non-severe system error. Subsequent SQL statements can be processed. (Reason      "sqlnp_initlex [300]:rc( 0) ".) SQLSTATE=58004"     Internal call code.........: "[RSQL/101//1CN/CTXSAPR0140 ]"     Please check the entries in the system log (Transaction SM21).

At the images you can see the TDMS step details are added also

The error details are at the attached files.

Addition we have analyzed the OSS NOTE 1160813 - DB6: Accessing a table returns SQL0901N  and have implemented it already

Could you please help us to solve this problem?

Kind Regards Kerem Tarhan

dev_w21_09_57_25.txt.zip

Shortdump_09_57_25.txt.zip

db2_diag_log_09_57_25.txt.zip

[rajesh_kumar2]

Hi Kerem,

The short dump suggests the issue could be with DB2 optimizer hints .

If You are  on SP02 of DMIS_CNT , then you should implement the note 1685583.

If you are already on higher SP, then this could actually be the issue with DB2.

Please do let us know if implementing the DB2 FIX patch corrected your issue.

Thanks,

Rajesh

[bxiv]

Looking at your dev_w21 I see the following:

RFC Error RFCIO_ERROR_SYSERROR

I dont think that correlates to your TDMS error time, but it might be worth verifying if the RFCs stayed in an operational state.

What SP for TDMS are you on?

Do you have all the notes implemented from the TDMS composite note? http://service.sap.com/sap/support/notes/1713981

[former_member205643]

Hello Billy,

Yes, our RFC's working and we have implemented the related notes.

As it can be seen from the images just the  3 files of about 18000 files have this error. rest of this processed correctly.

By he way we have found that this problem may be solved by a DB2 FIX PATCH implementation. We are analyzing it now.

Regards

Kerem