The runLocally() of the operator fail

[Ultramundane]

Getting the error:

SS_V1406EDD_Extract,0: The runLocally() of the operator failed.

When I specify an incoming parameter named FilePrefix as:
FilePrefix="TEST."

However, when I specify a different value it works.
Example:
FilePrefix="TEST.ASCENTL."
works without any issues.

The full filename in the target stage is:
#FilePath#/Seq/#FilePrefix#V1406E.PROFCST

The design is
ODBC ==> Transformer ==> Seq File

Note: In both cases I made sure that the target file didn't already exist!

Thanks.

[Ultramundane]

More testing results. The algorithm of failure.

IF [ your jobname is PAndP01_020_V1406E_PROFCST ]
AND IF [ your login name is not pearsona ]
AND IF [ A PERIOD IS IN THE FIFTH AND LAST CHARACTER POSITION USED FOR FILE NAMES ]
DO FAIL
ELSE SUCCEED

[Ultramundane]

I was able to find smaller algorithm.

Code: Select all

IF [ your jobname is PAndP01_020_V1406E_PROFCST ]
  AND IF [ your login name is not pearsona ]
    AND IF [ FilePrefix parameter is 5 characters long ]
      DO FAIL
ELSE SUCCEED

[ray.wurlod]

Less than or equal to 5, or only equal to 5 ?
Is persona the user ID who originally created (first saved/imported) this job?

You certainly find the weird ones!

[chulett]

Probably need another patch.

[Ultramundane]

Less than or equal to 5, or only equal to 5 ?
Is persona the user ID who originally created (first saved/imported) this job?

You certainly find the weird ones! ...

The job fails when the FilePrefix is equal to any 5 characters and the rest of the conditions.

persona was the user who created the job in development and the job is failing in system test. The job was migrated using version control. The job was checked in and pushed out using the dsadm login.

In function test anyone can execute the job with any FilePrefix. Function test and System test are on the same server and Datastage instance. They are just in different projects.

[Ultramundane]

I can the run job in function test without problems. I removed the job from system test and re-migrated and the job still exhibits same characteristics. I migrated the job to a different system test project and the job worked. Seems to be something wrong with the project?

[ray.wurlod]

If it were a specific file prefix I'd agree but, as it's not, that might be a bit of a long bow to draw.

[Ultramundane]

Argh...

I set to true the following to get more info:
APT_DUMP_SCORE
APT_PM_SHOW_PIDS
APT_STARTUP_STATUS
OSH_DUMP
OSH_ECHO
OSH_EXPLAIN
OSH_PRINT_SCHEMAS

The problem does not occur! I turned back to false. The problem occurs.

[ray.wurlod]

Doo doo doo doo doo doo doo doo (Twilight Zone theme)...

Planning to experiment with which of the environment variables switches the problem off? That may help to narrow down the cause, curiously.

[Ultramundane]

Agreed. I had tried and found that changing the current status of any environment variable that is used for either reporting or px results in the job running successfully.

[Ultramundane]

Getting stranger.

The default value of the FilePrefix parameter is 5 characters long. If I change the default to something that is say 17 characters long, I can now run the job with a FilePrefix that is 5 characters long. However, running the job with a FilePrefix that is 17 characters long (including not specifying and using the default value) results in the job failing.

Thus:

Code: Select all

IF [ project name is SMds01 ]
  AND IF [ job name is PAndP01_020_V1406E_PROFCST ]
    AND IF [ login name is not pearsona ]
      AND IF [ FilePrefix is length of default value ]
        AND IF [ no reporting or px variables modified ]
          DO FAIL
ELSE 
  SUCCEED

[Ultramundane]

Appears to be tied to the length of the name of the job in that particular project. That is, if I rename the job to something shorter it works without problems. If I rename to something longer it works. If I rename to something the same length it still is quirky.

Code: Select all

IF [ project name is SMds01 ]
  AND IF [ job name is 26 characters ]
    AND IF [ login name is not pearsona ]
      AND IF [ FilePrefix is length of default value ]
        AND IF [ no reporting or px variables modified ]
          DO FAIL
ELSE
  SUCCEED

[Ultramundane]

IBM cannot find the problem in their code. They want to close the case because changing any environment allows the job to work. They call this a fix. I call it workaround. I would like to have it fixed. They of course disagree because they don't know what to do or how to actually fix the issue.

[DSguru2B]

One of my collegues brought a smiliar issue to my attention. It was server though. It had about 10 stages and long link names and stage names. The job name was pretty long too. One of the hashed file stages was ending abnormally. After trying different things without avail, i just make a copy of the job and renamed it to 'abc'. It ran like a charm. I did not report this to support. I kinda figured I was hitting a limit somewhere.