Guru Of Geeks

DataStage Error:   Job xxx is being accessed by another user    Take below steps to get rid of locks in datastage -- In web console check active sessions and if job is listed disconnect session. To view all active sessions: In the Web console, click the Administration tab. In the Navigation pane, select Session Management > Active Sessions The Active Sessions pane shows the users that are currently connected to the server.

The ssh client PuTTY can be configured to maintain a connection and not time out due to inactivity.   To set up a new connection with "keep alives" to maintain your connection follow the steps below: Open the PuTTy application and navigate to the  Options  panel. Select Connection In the field  Sending null packets to keep session active  change the default value from  0 to 1800  (30 minutes) Check the  Enable TCP keepalives (SO_KEEPALIVE option)  check box. Note:  This option may not be available in older versions of the PuTTY client. Select  Session  from the left hand menu. In the  Host Name (or IP Address)  field enter the  destination hostname , for example vayu.nci.org.au In the  Saved Sessions  box enter a name for the session, for example vayu. Select  Save Any new sessions will now use these modified connection options.  

When attempting to open a job log in Director, user gets the following error message: Error selecting from log file RT_LOG### Error was: Unable to open DICT 'RT_LOG###'. This is because the D_RT_LOG file is missing from the projects directory.

Data Sets sometimes take up too much disk space. This technote describes how to obtain information about datasets and how to delete them.  

    While attempting to compile job,  “failed to invoke GenRunTime using Phantom process helper” RC:      /tmp space might be full            Job status is incorrect            Format problems with projects uvodbc.config file

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