Error while creating new jobs in DataStage

If you face the error error similar to below can occur when trying to save a newly created job:

Error On CREATE.FILE command
Creating file "RT_CONFIG4817 as type 30, mkdbfile: connot create file
RT_CONFIG4817. Unable to create operating system file "RT_CONFIG4817"

Unlocking XMETA locks from jobs

How can I unlock an XMETA locked job?

The job cannot be exported and when attempting to open the job, the following error appears:

Unable to open the Job
The Job 'TestJob' is locked by user 'dsadm'
(SessionID '8F1B0326-4F7E-45A8-B8EC-EAA8C4780528')

Do you want to continue and open a read-only view of the Job?

This issue arises when a lock still remains in XMETA for the corresponding job. Information Server will lock the job to ensure that there is no indeterminancy regarding the editing and saving of a job.
The most common causes of this is when a user has closed a client window unexpectedly (e.g. Force Terminate).

Error - mongod shell doesn't start, /data/db doesn't exsist

Error - mongod shell doesn't start, /data/db doesn't exsist


If you face this error while starting MongoDB (mongod), most probably there are 2 reasons for this -

a.  /data/db is not exist at all
b. mongod process don't have access on /data/db

Solution :-

The default db path for mongodb is /data/db/.
So when you run:

"Current Informix Installation Detected" message during installation

I am sharing this IBM tip on Cognos here again as it helped my from a big trouble :-) , Thought for a worth sharing ......

Cause

1. A separate, standalone version of Informix is installed on the host (or leftovers are found in the Windows registry)

2. IBM Cognos Express has been installed and reinstalled and the Informix registry entries were not removed properly.

3. The Windows user "informix" is present on the host because Informix had been installed on the system in the past.

DataStage Error - Cannot authenticate user

When you attempt to start one of the InfoSphere DataStage and QualityStage Administrator clients, the following message is displayed:

Failed to authenticate
the current user against the selected Domain:  Invalid user name (username)
or password.

 

There are several possible causes of this problem.

• The user name is invalid.
• The password is invalid or has expired.
• The user has no suite user role.
• Credential mapping is required, but has not been defined for this user.
• The user has no DataStage role or has the incorrect DataStage role.

DataStage Error - Client logins fail with Error: 39125

DataStage client logins fail with error: 39125: the directory you are connecting to either is not a uv account or does not exist.

This error usually indicates that one of the 6 files required to make a UniVerse account is missing from the directory of the DataStage project which has the problem or that the user does not have permission to access these files. Those 6 files/directories are:

DataStage Warning - When deleting data set previous delete attempt not complete

main_program: When deleting data set /full_Path_of_dataset.ds, previous delete attempt not complete; removing /full_Path_of_dataset.ds.being_deleted in order to proceed.


Solution -

This error usually comes when a previous run of respective job got aborted and the auto cleanup process hasn't been completed properly.

DataStage Error - irreconcilable constraints on the number of partitions

Fatal Error: There are irreconcilable constraints on the number of partitions of an operator: parallel <stage name>. The number of partitions is already constrained to 1, but an eSame partitioned input virtual dataset produced by parallel {natural=MOD_Nulls, synthetic="modify(0)"} has 2. 


This Error is simply Data Partitioning Error, The Stage mentioned in Error is not getting the Partition as defined for it. This is usually happen in SAME partitioning.

DataStage job fails with code=-14 [Timed out while waiting for an event]

DataStage job fails with code=-14 [Timed out while waiting for an event] - this generally happens when jobs are called from sequencers 

 

Solution :

Follow steps 1-3 in resolving this error.
1) DSWaitStartup - environment variable -
When multiple instances of a job are run from a sequence, and one or more of the job instances are set to reset, the sequence might report a status=99 or -14. This can occur because the controlling sequence did not give the job instances enough time to reset before polling its status. The start up time for a job reset must be increased. The environment variable DSWaitResetStartup can be used for this purpose.

(The maximum value that can be set for DSWaitResetStartup is the value of DSWaitStartup (default is 60). For example, if a value of 120 is required for DSWaitResetStartup, then ensure that DSWaitStartup is also set to a minimum of 120.)

DataStage error upon login: DSR.ADMIN: Failed to add user to UV_USERS file

When user first logs in, they get following error message:
DSR.ADMIN: Failed to add user to UV_USERS file.
ACCESS DENIED: INTERNAL SQL ERROR FAILED TO REGISTER THIS USER FOR SQL.

DataStage Error : Loop final value not numeric - cannot execute it

Generally, you will face this Error when you are getting values from a file or Unix commands and using that value in Loop ( either transformer loop or sequencer loop ).

Solution : 

 

Datastage Common Errors and Solutions

1.     While running ./NodeAgents.sh start command... getting the following error: “LoggingAgent.sh process stopped unexpectedly”

SOL:   needs to kill LoggingAgentSocketImpl

              Ps –ef |  grep  LoggingAgentSocketImpl   (OR)

              PS –ef |               grep Agent  (to check the process id of the above)

2.     Warning: A sequential operator cannot preserve the partitioning of input data set on input port 0

SOL:    Clear the preserve partition flag before Sequential file stages.

Error : Datastage Job Aborts with "The record is too big to fit in a block"

To fix this error you need to increase the block size to accommodate the record size:

1. Log into Designer and open the job.

2. Open the job properties--> parameters-->add environment variable and select: 
   APT_DEFAULT_TRANSPORT_BLOCK_SIZE

ETL Job Design Standards - 1

When using an off-the-shelf ETL tool, principles for software development do not change: we want our code to be reusable, robust, flexible, and manageable. To assist in the development, a set of best practices should be created for the implementation to follow. Failure to implement these practices usually result in problems further down the track, such as a higher cost of future development, increased time spent on administration tasks, and problems with reliability.

Although these standards are listed as taking place in ETL Physical Design, it is ideal that they be done before the prototype if possible. Once they are established once, they should be able to be re-used for future increments and only need to be reviewed. 

Listed below are some standard best practice categories that should be identified on a typical project. 

Failure to connect to DataStage services tier: invalid port

When you attempt to start one of the DataStage clients, the following message is displayed:

Failed to authenticate
the current user against the selected Domain:  Could not connect to
server [servername] on port [portnumber].

DataStage compile error 65280; Couldn't change directory to /tmp

Error when trying to compile parallel (PX) jobs in a project.

The compilation errors include the following:

Subprocess command failed with exit status 65280.
Output from subprocess: Couldn't change directory to /tmp : No such file or directory

Error 39202 when logging into IBM DataStage

DataStage Client programs (Designer, Manager, Director) experience a connection failure, and the message displayed to the user is:

Failed to connect to host: xxxxx, project: UV
(Internal Error (39202))

Unable to open jobs with error "Unable to open the Job Unable to load RID"

Unable to open jobs with error "Unable to open the Job Unable to load RID - c2e76d84.43058877.7e01af4f.cd92bbcd-2ebc-4cb3.833e.37a962373ef7"

Also in SystemOut.log file, it has the following:
[8/25/10 21:21:46:475 UTC] 000000b1 SystemOut O 2010-08-25 21:21:46,475 ERROR ojb.OjbPersistentEObjectPersistence - java.lang.OutOfMemoryError

When datastage file system becomes full, RT_LOGxxx files can become corrupted. Here is a manual procedure to recreate them

When many datastage jobs are running for long time, the RT_LOGxxx files can become very big. If the log files are not regularly purged, in some cases, a file system full on the datastage file system can occur. If the corruption of datastage system files is restricted to the RT_LOGxxx files, a procedure to delete and recreate the RT_LOGxxx files can be attempted in order to recover from the corruption.

Selecting DataStage job log results in error: Error Selecting from log file RT_LOG

When trying to view a job log in DataStage Director, an error similar to the following is received:

Error selecting from log file RT_LOGnn
Command was: SSELECT RT_LOGnn WITH @ID LIKE '1NON' COUNT.SU
Error was: Internal data error. File <path_to>/RT_LOGnn/<filename>':
Computed blink of 0xnnnn does not match expected blink of 0xnnnn! Detected within group starting at address 0xnnnnnn!
The error message received indicates that the log file for the job is corrupted.