Sunday, 29 May 2016

How to unlock a Datastage job


When a user is compiling a Datastage job,They are getting below message
This job is locked by user username.

Even if user has closed that job,this error is still coming.

OR

User aborted a running sequence in between and then getting below error while trying to compile the sequence again.

Cannot get exclusive access to executable file for job Job name-Job may be being monitored.


Solution:
1.Click on Tools and then Run Director from designer.
2.Select the job/Sequence and click on job from top and choose cleanup resources.



















3.If this option is not available or visible to you,then open Datastage administrator.
4.Select that project and go to Properties.Please check marked checkbox.











5. Now click on the clean up resource from director.
6.Now try to compile the job to see if the issue is fixed.
7.If the issue still persist,Then click the session of that user from Infosphere.
8.Click on administration.
9.Click on Session management.
10.Click on Active session and select that user and click on Disconnect.

How to remove security alerts from Datastage client window


When we are trying to login into Datastage designer from client machine getting below security Popup.When we click on Yes,It disappears and we are able to login into Datastage designer.

But we try to run multiple projects simultaneously,It is really annoying.Please follow the below steps to get ride of this Popup.It will disappear.







Solution:

Please follow below steps.

1.To view the security certificate, Click on "View Certificate".
2.Click the "Certification Path" tab, and then select the "Root Certificate".
3.Click on "View Certificate".
4.Click on "Install Certificate", and then click "Next".
5.Select "Place all certificates in the following store".
6.Click "Browse", and then select "Trusted Root Certification Authorities".
7.Click "Next", and then click "Finish" to import the certificate.
Now the security Popup will disappear.

Sunday, 20 March 2016

DataStage Job Compilation error "Failed to invoke GenRuntime using phantom process helper".

 
           

 Data Stage compilation error "Failed to invoke GenRuntime using phantom process helper. "


If you are getting below error while compiling jobs in Data Stage and error in coming in all the projects.Job are not able to execute.

Failed to invoke GenRuntime using phantom process helper. 

Cause:One of the possible cause of this error may be that tmp directory is full.Go to location
            /opt/IBM/InformationServer and check the space occupied by folder tmp

Run below command to see the space occupied.

df -k /opt/IBM/InformationServer/tmp

It command will show you total space assigned to this folder,space occupied,space available and %use.

If your issue is due to space in tmp directory,You will see %use as 100%.That means there is no space available in tmp directory and your jobs are failing.

If you try to delete some unwanted files from tmp folder,%Use may not decrease less than 100%.It means that even after deleting the files,no space is being released.

Solution:

Data Stage restart may resolve this issue.

Your tmp folder  may be filled because of the bad jobs.

A bad jobs is a job that had an issue while running and caused the temp directory to become full.
This could happen again if the same program is run.

Developer needs to fix the job to avoid this issue.

Friday, 18 March 2016

Data Stage Jobs are hanging after Upgrade/Installation

           

               Data stage jobs are hanging on new server (after upgrade)



 If you are facing below error-

After Data Stage upgrade or new installation, if your jobs are hanging during testing, hundreds of jobs run together but don’t get executed and get hanged. Jobs are taking a lot of time in execution.
This problem may be because the nproc value and max user processes variables don’t have enough values to execute the jobs.

[root@localhost# ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 127358
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 65535
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 10240
cpu time               (seconds, -t) unlimited
max user processes              (-u) 65535
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

A decent value for max user processes should be 10K.Please check above values for dsadm account or the account which is running your Data stage server.

If open files and max user processes values are less then and get it fixed by Linux team.

Nproc values are saved in /etc/security/limits.conf .

If you are upgrading on a new server,You can verify these settings on your current server also.

Sunday, 7 February 2016

DataStage configuration (WebSphere and InfoSphere)

             
                     

                  How to configure DataStage after installation


     We need to configure datastage once the installation is completed.In the previous posts,We have discussed that you need to copy contents from dsenv on your current server to your new server and some of the other configuration files.

After copying the configuration files,We need to configure datastage .Below are the steps to configure datastage.

First,we need to configure security in WebSphere.

                                  WebSphere configuration



1. Login into WebSphere admin URL  https://hostname:9043/ibm/console/login.do  with existing admin user( Which you have provided during installation ex wasadmin)

2. Click on Security---> global security.

3. Choose standalone ldap registry in the pull down window for ‘Available realm definitions’ then click configure.

    Make sure Enable administrative security is checked in administrative secuirty.
    Enable application security is checked in Application security.
          On the right side LTPA should be selected in Authentication.
   
4. Provide primary administrative user name(It should be LDAP account)

5. Choose Microsoft Active Directory in Types of LDAP server.

6. Provide Domain.corp.dom in host field and port number in port field.

7. You can keep the search time out same as default.

8. In the Bind Distinguished Name (DN)
Bind dn: cn=adminid_from_AD,ou=users,dc=corp,dc=dom

(You can check these settings in your old environment.)

9. In the Bind password,Provide the password of the above id ,which you have mentioned in DN.


10. At the top hits save.

11.   Go to Administrative group roles, hit add, change the search string to the name of the group that will be WAS admins and click add, then save(optional).

12. Click apply and then save.

After making these changes,You can see all the LDAP groups and users through IIS URL.

Now,you can login into WebSphere admin console,only with the account which you have provided in primary administrative user name.

If you want to login with some other accounts also to monitor the activities,then you need to add Monitor Roles for all Authenticated users.

1. Click on Administrative group roles under Users and Groups.

2. Click on Add.

3. In the group,Choose ALL AUTHENTICATED

4. In the Roles,Choose monitor.

5.Click on Apply.

6. Now all the users,who have access to datastage,should be able to login into WebSphere admin console with their user id.


                           InfoSphere Configuration

Credential Mapping


1) Defining default credentials


1. Open the admin console URL https://servername:9445/ibm/iis/console/.

2. Login with the user id which you gave during installation (Example wasadmin).
    You must have suite administrator authority or IBM® InfoSphere® DataStage® and IBM      InfoSphere QualityStage® administrator authority.


The default credentials are used for any users who do not have their own credential mappings. If you do not want users who do not have mapped credentials to access the server, do not add default mapping credentials.

Procedure

  1. In the IBM InfoSphere Information Server Web console, click the Administration tab.
  2. In the Navigator pane, select Domain Management > Engine Credentials.
  3. Select the InfoSphere Information Server engine for which you want to specify the default credentials.
  4. Click Open Configuration.
  5. In the User Name field, type the user name to be used by all InfoSphere Information Server users for whom a specific mapping is not defined.
  6. In the Password field, type the corresponding password. The user name and password that you provide must be a valid user name and password for the operating system where the engine tier components are installed.
  7. Confirm the password.
  8. Click Save and Close.

2.) Configuring your credentials

 you can map the credentials for your own user account.

Steps
  1. In the  Information Server Web console, click the Administration tab.
  2. In the Navigation pane, select Domain Management > Engine Credentials.
  3. Select the InfoSphere Information Server engine that you want to configure.
  4. Click Open My Credentials.
  5. Type the user name and password that you want to use to connect to the IBM InfoSphere Information Server engine. The user name and password that you provide must be a valid user name and password for the operating system where the engine tier components are installed.
  6. Click Save and Close.
3.) Grant role to DataStage users/Groups

Steps

  1. Grant the required suite and suite component roles to the user in the Web console.
  2. Using a role that has administrative privileges, log in to the IBM InfoSphere Information Server Web console.
  3. Select the Administration tab.
  4. In the Navigation pane, select Users and Groups > Users.
  5. Select the user that you want to grant access to and click Open User.
  6. In the Roles pane, assign the following roles to the user.
  7. Suite User
  8. Required for all users in order to log in to any of the suite components.
  9. DataStage and QualityStage User
  10. Required for any user in order log in to any of the InfoSphere DataStage and InfoSphere QualityStage product modules.
  11. DataStage and QualityStage Administrator
  12. Optional. Grants full access to all projects and the administrative capability of InfoSphere DataStage and InfoSphere QualityStage.

Note: Same way ,you can assign riles to groups also.It is better to assign roles to groups instead of assigning to individual users.

If you want to add any other user as administrator who is not part of any group,Then you need to assign administrator role to that user individuals.