Datastage InfoSphere Information Server patch installation instructions on AIX Box

About patches

Patches for IBM InfoSphere Information Server Version 8.1 consist of two files.

Table 2. Patch component file names and descriptions

Patch component	Description
README.txt	Contains important information specific to the patch.
*.ispkg	Patch package installed with the Update Installer.

Update Installer

Patches are installed with the Update Installer that is part of the IBM InfoSphere Information Server installation. Updates to the Update Installer are made available separately.

Before you install a patch, follow these steps to ensure that you are using the latest version of the Update Installer:

1. From the command line run the following command:
   • Windows: C:\IBM\InformationServer\Updates\bin\VersionInfo.bat
   • Linux, UNIX: /opt/IBM/InformationServer/Updates/bin/VersionInfo.sh
   For example, the following Update Installer version information is displayed for Version 8.1.0.160:

   IBM Information Server Update Installer Version 8.1.0.160

2. Ensure that the version number returned by the VersionInfo script is the same version as the latest Update Installer

Using console mode installation on Linux and UNIX operating systems

Follow these steps to install a patch on Linux or UNIX operating systems:

1. Log in as the root user.
2. If your installation includes , source the dsenv file. In the command prompt window, type the following command:

   . /opt/IBM/InformationServer/Server/DSEngine/dsenv

3. If you are installing a patch on IBM AIX:
   1. Unset LDR_CNTRL after sourcing dsenv to avoid adversely impacting the amount of available memory in IBM WebSphere Application Server. Type the following command:

      unset LDR_CNTRL

   2. On the services tier, use only the JRE for WebSphere Application Server. By default, the JRE is located in the /opt/IBM/WebSphere/AppServer/java directory. Type the following command:

      /opt/IBM/WebSphere/AppServer/java/bin/java -jar updater.jar other arguments

      Note: If your topology contains a computer dedicated to the engine tier, when installing on the engine tier, use the JRE from the InfoSphere Information Server Version 8.1 Fix Pack 1 package. Alternatively, you can make a copy of the JRE located in the opt/IBM/InformationServer/ASBNode/lib directory.
4. Type the following command in the /opt/IBM/InformationServer/Updates/bin directory to install a patch:

   ./InstallUpdate.sh -console

   Alternatively, you can specify all the command line parameters and values to avoid interactive installation prompts. Type the following command to install a patch:

   ./InstallUpdate.sh –p patch_JR000000_type_os.ispkg -user admin -password AdminPassword -wasadmin wasadmin -waspassword WebSpherePassword –console

Uninstalling a patch
Not all patches can be uninstalled. The README.txt file included with each patch indicates whether the patch can be uninstalled. Only the last patch installed can be uninstalled. To uninstall a patch that is not the last installed patch, you must first uninstall the latest installed patch and then uninstall all later patches. Installing a patch that cannot be uninstalled prevents all previously installed patches from being uninstalled because patches must be uninstalled in reverse order of their installation. To determine which patches have been installed, locate the Version.xml file:
Windows: C:\IBM\InformationServer\Version.xml
Linux, UNIX: /opt/IBM/InformationServer/Version.xml
In the Version.xml file, the entry for the last patch installed is at the end of the history section and is similar to the following example:
...
<History>
...
    <Sequence description="Description of the patch" id="1" installLocation="" 
lastUpdateDate="Thu Feb 14 13:13:52 EST 2008" patch="patch_JR000000" 
rollback="/opt/IBM/InformationServer/Updates/patch_JR000000" 
status="Success" version=""/>
</History>
...
You must use the Update Installer in console mode when you uninstall patches.


Uninstalling on Linux and UNIX operating systems
Follow these steps to uninstall the latest patch installed on Linux or UNIX operating systems:
Log in as the root user.
If your installation includes , source the dsenv file. In the command prompt window, type the following command:
. /opt/IBM/InformationServer/Server/DSEngine/dsenv
If you are installing a patch on IBM AIX, unset LDR_CNTRL after sourcing dsenv to avoid adversely impacting the amount of available memory in IBM WebSphere Application Server. Type the following command: 
unset LDR_CNTRL
Type the following command in the /opt/IBM/InformationServer/Updates/bin directory to uninstall the latest installed patch:
./InstallUpdate.sh -rollback patch_JR000000
 
Patch installation log files
Viewing the log files that are created during installation is useful when you are troubleshooting installation problems. During the installation and uninstallation process, the log file is simultaneously updated in the following directories:
Microsoft® Windows: 
C:\IBM\InformationServer\logs
C:\IBM\InformationServer\Updates\PatchName
Linux, UNIX: 
/opt/IBM/InformationServer/logs
/opt/IBM/InformationServer/Updates/PatchName
After a successful installation, the log file is named ISInstall.YYYY.MM.DD.HH.MM.SS.log where YYYY.MM.DD.HH.MM.SS is the date and time that the installation was started.
After an unsuccessful installation, the ISInstall.YYYY.MM.DD.HH.MM.SS.log file is included in the InformationServer/logs directory, and all logs that are used for troubleshooting are included in the InformationServer/isdump-operating_system-YYYY.MM.DD.HH.MM.SS.zip file.

Before doing the patch installation the application should be stopped and started
as shown below.

---> stopDatastage_all.sh
#!/bin/sh
#
echo "Setting environment..."
. /opt/IBM/InformationServer/Server/DSEngine/dsenv
echo "Stopping DataStage agents..."
/opt/IBM/InformationServer/ASBNode/bin/NodeAgents.sh stop
sleep 10
#
echo "Stopping DataStage Engine"
/opt/IBM/InformationServer/Server/DSEngine/bin/uv -admin -stop
sleep 10
#
echo "Stopping WAS..."
/opt/IBM/InformationServer/ASBServer/bin/MetadataServer.sh stop
#DataStage listener
#su - dsadm "-c /opt/IBM/InformationServer/Server/DSSAPbin/dsidocd.rc stop"
sleep 10
#
echo "Stopping DB2"
#DB2
su - db2inst1 -c "db2 force application all"
sleep 2
su - db2inst1 -c "db2 force application all"
su - db2inst1 -c db2stop
sleep 5
su - db2inst1 -c db2stop force


 





---> startDatastage_all.sh
#!/bin/sh
#DB2 kaynnistys
#
su - db2inst1 -c db2start
sleep 5
#Was kaynnistys
/opt/IBM/InformationServer/ASBServer/bin/MetadataServer.sh run
sleep 15
# Datastage Moottorin kaynnistys
/opt/IBM/InformationServer/Server/DSEngine/bin/uv -admin -start
sleep 10
#ASBAgentin kaynnistys
/opt/IBM/InformationServer/ASBNode/bin/NodeAgents.sh start
#Datastage listener
#su - dsadm "-c /opt/IBM/InformationServer/Server/DSSAPbin/dsidocd.rc start"