DSXchange

I created scripts that undeploy and deploy the ISD applications using the command line. Scheduled scripts using crontab.

This belongs in a DataStage forum.

You could start by reading all the available product documentation.

typo = typing mistake

If one character is wrong or missing, it will cause an error.

You may have a typo in your tnsname.ora file on the DataStage server or a typo in the stage properties. Double check your job logs that all parameters resolved correctly and double check your stage properties for typos.

Have you already tried searching the forums here and the IBM support portal?

Have you tried applying Microsoft Windows updates and rebooting?

I don't know what the cause could be. Hopefully someone else does.

I hit a similar problem once after installing the client onto an unsupported version of Windows 7 (I think it was Home Edition). Check that your client tier operating system is supported for that release.

Compare the environment variables between the dev and prod jobs. Maybe they're not setup correctly on prod.

It seems like if you could force a divide by zero situation in the source stage, then the job should abort. Could you add a dummy column to the query and define it as a calcuation, such as some constant number divided by "SELECT COUNT(*) FROM SOURCE_TABLE"?

Is it possible that 167 records were updated in the source table between the two job runs?

This was accepted as a requirement for a future release. Check with IBM about the status of this APAR.

JR37119: PROVIDE A WAY FOR USERS WITH THE ROLE "DATASTAGE OPERATOR" TO HA VE A "READ-ONLY" DIRECTOR (Last updated 2010-07-06).

rkashyap wrote:As per IBM, this seems to be a known issue. For 9.1.2 APAR number is JR49794. Engineering is looking into this.

No results found for JR49794. (as of today)

I found JR44926 related to looping sending cached input records to output link without regard for constraints.

The convert function will convert from a list of characters to a list of corresponding characters, one character at a time, rather than from one character to a string of many.

The XML stage documentation does warn about logging affecting performance.

Enable logging
Enter Yes to enable logging and set the log level to Warning. By default, logging is not enabled. Enabling logging affects performance.

I think it's not available in DataStage Director but is available in the DataStage Operations Console. Here is a quote from the new features web page of the 8.7 information center: InfoSphere Information Server includes a new role called Operations Viewer. This role is restricted to use only the Ope...