IBM DB2 Runtime Client - DB2COPY1

Version: 9
Views: 2.2k  |  Created: 09/12/2009

Average Rating: 0
DB2 Runtime Client - DB2COPY1 has 3 inventory records, 1 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (3)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 0 / 5 (Not Rated) based on 0 ratings
Most Commonly Reported Deployment Method
Not Determined
or cancel
122
Note
We just recently had to create a new package to deploy IBM's Db2 v9.1 run time client. In doing so we came across a problem with how IBM handles running the installation process via the system account for SCCM.

Setup.exe hands off the installation process to WININST.exe which is provided by IBM in the source files. WININST.EXE does a check for the My documents folder under the user profile. If you want to run this setup in user context then you will not have a problem. Running it as the system account(administrative) is a problem. WININST.EXE is looking for a My Documents folder under C:\Document and Settings\Local Service\ . On a standard Windows XP Pro build the My Documents folder does not exist in that location. The installation process wants to create a folder called DB2LOG in the My Documents folder under the user profile. It does this even if you have stipulated a different location of the installation log in your command line. When WININST.EXE checks for the My Documents folder and is not found it stops the installation.

As you may have surmised we needed to manually create a My Documents folder in the location above and our installation was successful at that point. We opened a Support ticket with IBM and sent them logs and a description of the issue with how we resolved it. hopefully they will make necessary changes in the future.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
121
Note

I would also like to add that running the msi for the client in any mode other than full resulted in the msi not installing at all(it would start installing then die off). When I looked into the msi I came across numerous custom actions that were not set to ignore the error code, thus these are what caused it to stop installing. All I did at the end of the day was repackage it. You'll also have to include the temporary folder and files it creates when it is launched by another client(say Cognos). These files and folders are created under c:\Program Files\IBM\SQLLIB\DB2.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
3
Note

The issue noted above isn't so much that the CAs check for a return code, rather it's that the UI sequence contains CAs which don't appear in EI at all (and vice-versa). I'll try and remember to post the list once I've completed my transform.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (3)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

DB2 Runtime Client - DB2COPY1

Version

9.1.700.855

Contact

Customer Support Department

Comments

IBM DB2 V[VersionString]

Uninstall String

MsiExec.exe /I{4A54CF0D-EE0D-48CB-8C96-69C720FD16C6} MsiExec.exe /I{4A54CF0D-EE0D-48CB-8C96-69C720FD16C7}

Questions & Answers (1)

Questions & Answers related to IBM DB2 Runtime Client - DB2COPY1

1
ANSWERS

Blogs (0)

Blog posts related to IBM DB2 Runtime Client - DB2COPY1

Reviews (0)

Reviews related to IBM DB2 Runtime Client - DB2COPY1