DSXchange

I have a primary execution sequencer that is set as multi instance, but since moving to version 8 I have noticed that the invocation id is not always 'taking', i.e. I run a job and set the invocation id in the run dialog box, but it doesn't always seems to set correctly. I haven't noticed any partic...

Thanks Ray...worked exactly as described.

Hi all I'm upgrading from v7 to v8, and am getting the following warning message when testing one of my match jobs - Server:DPLAPP1 Project:POLNEW Job No:571 Job name:MatchSubmissionLocality Invocation: Event Number:136 Event type:Warning User:dsadm Timestamp:24/07/2008 9:20:06 AM Message Id:IIS-DSE...

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 ch...

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 ch...

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

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

Try 'INDEX', syntax Index (string, substring, instance). So your code would look like - The designer manual should be able to give you more examples.

Hi Jim I found this issue too when importing a number of jobs from a v7 export into a v8 project, although there did not seem to be any correlation between the jobs imported and the jobs that the compiler could not get exclusive access to. To overcome the problem I had to clear the locks on the jobs...

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.

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 with...

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.

Oracle version - 10.2.0.1.0

Oracle version - 10.2.0.1.0

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.