Fault Type 11

cfuller · Post by **cfuller** » Tue Jun 10, 2008 4:32 pm

Hi all

I'm in the process of upgrading from v7.1.r1 to v8.0.1a, and am having trouble with a couple of jobs. The jobs are very simple but I keep getting the same issue -

DataStage Job 586 Phantom 12518
Abnormal termination of DataStage.
Fault type is 11. Layer type is BASIC run machine.
Fault occurred in BASIC program DSP.Open at address 574.

Job design -

DRS Stage (connecting to Oracle) --> Transform --> HashFile

I have a number of jobs doing similar things, which all seem to work OK, just a couple seem to fail with the same error. I have been talking to IBM but still no joy.

I have also tried a couple of other things -

1) Rebuilt job from scratch, rather than use imported job from 7.1 export
2) Swapped hash file for Flat file - same result
3) Swapped DRS stage for OCI stage - same result

These jobs were originally part of a sequencer that was running about 5 or 6 job concurrently, but I can recreate the error by running the job independently.

If anyone has ideas of what to try next, please let me know.

ArndW · Post by **ArndW** » Wed Jun 11, 2008 1:38 am

This would seem to point to the error occuring in the TRANSform stage. Both your changes and link to DSP.Open reflect that.
Address 574 in the program (assuming you have the same release 8.0.1 that I do) is a call to "$DSP.Open" routine that has been cataloged in memory.

Assuming you had no installation issues, do the transform stages have anything in common that differentiates them from jobs that work? Perhaps call up user-written routines?

cfuller · Post by **cfuller** » Wed Jun 11, 2008 5:22 pm

Hi Arnd

No custom routines, just a very basic job to read data from a number of Oracle tables, using generated SQL, and writing to the hash file. Three columns read, 3 columns written to file with the same Metadata on both sides. The only difference I can see is that the column names are altered on the output side.

chulett · Post by **chulett** » Wed Jun 11, 2008 7:08 pm

Ok, let me ask this. What version of the Oracle client do you have installed on your DataStage server? When I've had Oracle related issues like this, my Fault Type was 10, not 11, but perhaps it is still an issue here.

I see your database version is 10gR2, I'm specifically wondering about the client you are using to access it. I'm assuming the DRS stage is set to Oracle and not something like ODBC instead, yes?

cfuller · Post by **cfuller** » Wed Jun 11, 2008 9:55 pm

Hi Craig

Client is 10gr2 for AIX, installed on DataStage server.

When using the DRS stage the connection type was Oracle, not ODBC. I got the same issue with OCI stage.

Still working with IBM also, so if I get a satisfactory response from them I will advise.

chulett · Post by **chulett** » Wed Jun 11, 2008 10:02 pm

Do you know the specific client version? For example, 9iR2 could be:

9.2.0.1
9.2.0.5
9.2.0.8

Etc. Support should have asked the same question, I would think. Anywho, let us know if you have any luck.

cfuller · Post by **cfuller** » Wed Jun 11, 2008 10:44 pm

Oracle version - 10.2.0.1.0

cfuller · Post by **cfuller** » Wed Jun 11, 2008 11:07 pm

Oracle version - 10.2.0.1.0

cfuller · Post by **cfuller** » Thu Jun 12, 2008 6:42 pm

IBM have managed to recreate this issue in their environment

, so hopefully I have found a bug that a patch can correct. I will let you all know what happens.

cfuller · Post by **cfuller** » Thu Jun 12, 2008 7:15 pm

IBM advise that they think the issue is one that was created in v7.5.2, and relates to when a FROM clause is > 76 characters. It seems the error has reappeared in v8.0. They are working on the patch, and will release it ASAP.

As a work around I will start changing my job designs to do the joins within Transform stages, rather than using complex queries with the DRS / OCI stage, or look at reducing the FROM some other way.

cfuller · Post by **cfuller** » Thu Jun 12, 2008 11:59 pm

IBM have given me a workaround for this...within DRS stage use ODBC as connector rather than Oracle. As this is parameterised in most of my jobs this is a simple workaround that I can live with till the patch becomes available.

cfuller · Post by **cfuller** » Mon Jun 30, 2008 5:51 pm

Just received the patch to fix the DRS stage, Apar number JR29532. Applied patch and retested my code successfully, so if anyone else is using DRS stage with from clauses greater than 75 characters, then talk to IBM and get this patch. They have also produced a similar one for the OCI stage.

:D

cfuller · Post by **cfuller** » Mon Jun 30, 2008 5:53 pm

Just received the patch to fix the DRS stage, Apar number JR29532. Applied patch and retested my code successfully, so if anyone else is using DRS stage with from clauses greater than 75 characters, then talk to IBM and get this patch. They have also produced a similar one for the OCI stage.

:D

chulett · Post by **chulett** » Mon Jun 30, 2008 6:49 pm

So this patch is specific to 8.x yes?

cfuller · Post by **cfuller** » Mon Jun 30, 2008 7:52 pm

Hi Craig

Yes...8.0.1a

Readme.txt file is as follows -

PATCH REPORT FOR APAR:JR29532
PRODUCT: Information Server
VERSION: 8.0.1.1
PATCH NAME:patch_JR29532

COMPONENT: Server

PROBLEM REPORTED/Implementation Details:
OracleOCI Stage and DRS Stage with DBMS Type = Oracle will SEGV
when SQL FROM clause character length is greater than 77.

CAUSE OF PROBLEM:

FIX SUMMARY:

USER INTERFACE FIX:
None

PRE-REQUISITE PATCHES REQUIRED:

COMPETING PATCHES:
None

OBSOLETED PATCHES:
None

EXPECTED RESULTS OF PATCH:

SYSTEM REQUIREMENTS (OS LEVEL, COMPILER VERSION):
This patch is supported on:
Platform(s) : AIX
IS Release(s) : 8.0.1.1

PATCHED FILES:
The following files contain the fixes for this ecase:

<IS-Install-Path>/Server/DSComponents/bin/drs.so
<IS-Install-Path>/Server/DSComponents/bin/drsenu.so
<IS-Install-Path>/Server/DSComponents/bin/drsoci.so

where <IS-Install-Path> is the install directory

TARGET DIRECTORY:
The following directories are where the patched files will be copied:

<IS-Install-Path>/Server/DSComponents/bin/

where <IS-Install-Path> is the install directory

(version 2.6a)