The How-to install Insight 1.0.1 on Redhat using DB2
I apologize for the length of this post but if you have experienced the frustration of trying to install 1.0.1, you will appreciate it in the end.
This assumes you have already worked out the various install failures due to dependencies on various libraries likely not to be installed on your Redhat (or Centos) system. Be prepared to do some trial and error here. You can resolve most of the dependencies via a close review of all the documentation but you will likely find a couple failed installs will identify some additional dependencies. I could take a look at my install log - maybe - if you need to know the various libraries you are likely to require.
You will quickly discover the automated install fails after transferring a few gb with a error indicating the star views script failed. The documentation is not helpful. Actually, I didn't find anything that was helpful. The suggested standard approach which to be employed would be to install the databases manually. This will not work either and simply leads to more frustration.
After a lot of trial and error (30+ installs) - I identified the star views was not the problem despite the various error messages and logs which target it. It fails because the riasset ddl fails. In addition, several other ddl files (riba, rischk) fail as well. All of these run prior to the star views ddl file.
After a lot more investigation, I discovered these scripts as well as others were edited before the build was released and in so doing, their native mime type was changed and their formatting prevented db2 from executing them as proper commands. After spending a bit of time removing the formatting, I found the scripts could be executed. There are, however, hundreds of lines to edit and in attempting to find an easier way, I discovered the true issue and an easy approach to solving it.
Open the files in Notepad++. You will notice these files are encoded in DOS/WINDOWS ANSI when they should be Unix encoded. Use Notepad to switch the files to Unix encoding and save them. You now have scripts which will result in a successful install. One of the scripts however is missing a COMMIT command at the end, you will need to add this as well.
The following ddl's need to be modified - createRIASSET, createRIBA, and createRISCHK. Note the createRIASSET file is missing the COMMIT; command at the end of the file.
Additionally, two SQL scripts are also encoded improperly; (1) the initRIASSET.sql file and (2) the initRISCHK file. Make sure to fix these as well or another failed install (after the successful create of the database and tables) will be the result.
How do you get these files? Start the install and monitor the Insight install directory/datawarehouse/dw/work_spc/ddl folder. Shortly after the program indicates it is installing websphere - early in the actual installation - you will find the ddl and script directories (also under work_spc) get populated. As soon as they do, copy the necessary files from these directories onto your desktop somewhere. When the install fails, it removes these files so if you wait too long, you get to repeat this process.
Modify the files using Notepad++ (or whatever tool you find convenient to encode them as Unix files.) Once you have done so, check their properties and make sure they haven't been marked executable as well.
Run your install again (make sure you delete the existing ridw database and the Rational Insight install folder) monitoring the appropriate folder as directed above. As soon as it is populated, copy the ddl files into the ddl folder and scripts folder under work_spc. Also note there are ddl and script folders located a directory up from the work_spc folder as well; overwrite these files too.
The install will complete as expected and Insight will actually work when the install completes.
Rational: I will submit a defect as well. Where? Should I specify it against the build or ... also, the documentation should mention the install will indicate success if a user fails to delete the bad database prior to a reinstallation but leaves the system in an unusable state and the reason why isn't immediately identifiable - unless you have performed 30+ installs.
This assumes you have already worked out the various install failures due to dependencies on various libraries likely not to be installed on your Redhat (or Centos) system. Be prepared to do some trial and error here. You can resolve most of the dependencies via a close review of all the documentation but you will likely find a couple failed installs will identify some additional dependencies. I could take a look at my install log - maybe - if you need to know the various libraries you are likely to require.
You will quickly discover the automated install fails after transferring a few gb with a error indicating the star views script failed. The documentation is not helpful. Actually, I didn't find anything that was helpful. The suggested standard approach which to be employed would be to install the databases manually. This will not work either and simply leads to more frustration.
After a lot of trial and error (30+ installs) - I identified the star views was not the problem despite the various error messages and logs which target it. It fails because the riasset ddl fails. In addition, several other ddl files (riba, rischk) fail as well. All of these run prior to the star views ddl file.
After a lot more investigation, I discovered these scripts as well as others were edited before the build was released and in so doing, their native mime type was changed and their formatting prevented db2 from executing them as proper commands. After spending a bit of time removing the formatting, I found the scripts could be executed. There are, however, hundreds of lines to edit and in attempting to find an easier way, I discovered the true issue and an easy approach to solving it.
Open the files in Notepad++. You will notice these files are encoded in DOS/WINDOWS ANSI when they should be Unix encoded. Use Notepad to switch the files to Unix encoding and save them. You now have scripts which will result in a successful install. One of the scripts however is missing a COMMIT command at the end, you will need to add this as well.
The following ddl's need to be modified - createRIASSET, createRIBA, and createRISCHK. Note the createRIASSET file is missing the COMMIT; command at the end of the file.
Additionally, two SQL scripts are also encoded improperly; (1) the initRIASSET.sql file and (2) the initRISCHK file. Make sure to fix these as well or another failed install (after the successful create of the database and tables) will be the result.
How do you get these files? Start the install and monitor the Insight install directory/datawarehouse/dw/work_spc/ddl folder. Shortly after the program indicates it is installing websphere - early in the actual installation - you will find the ddl and script directories (also under work_spc) get populated. As soon as they do, copy the necessary files from these directories onto your desktop somewhere. When the install fails, it removes these files so if you wait too long, you get to repeat this process.
Modify the files using Notepad++ (or whatever tool you find convenient to encode them as Unix files.) Once you have done so, check their properties and make sure they haven't been marked executable as well.
Run your install again (make sure you delete the existing ridw database and the Rational Insight install folder) monitoring the appropriate folder as directed above. As soon as it is populated, copy the ddl files into the ddl folder and scripts folder under work_spc. Also note there are ddl and script folders located a directory up from the work_spc folder as well; overwrite these files too.
The install will complete as expected and Insight will actually work when the install completes.
Rational: I will submit a defect as well. Where? Should I specify it against the build or ... also, the documentation should mention the install will indicate success if a user fails to delete the bad database prior to a reinstallation but leaves the system in an unusable state and the reason why isn't immediately identifiable - unless you have performed 30+ installs.
4 answers
Hi Robert,
I'm very sorry to hear that you've had so much trouble installing Rational Insight 1.0.1 on a RedHat system. Although it's of little consolation at this point, the Insight quality assurance and development teams did test the installation on RedHat 5 thoroughly and did not encounter this issue. We'll need more information about your specific environment, such as specific version of RedHat, 32 or 64 bit OS, DB2 edition and version, and as specific installation steps as your can provide, in order to work on reproducing the issue.
You can file a new defect against the Data Warehouse component at the following URL
http://jazz.net/jazz02/web/projects/Rational%20Insight#action=com.ibm.team.workitem.newWorkItem&ts=1296225676000
Please cc me on your new defect and I'll ensure that the Insight quality assurance teams are notified and can review your case.
A few pointers for anyone else who may hit a similar issue:
1. Selecting a manual installation of the database will place the database scripts on the system but will not execute them. This should allow you to proceed with your work around.
2. You can tell the installer to pause on error rather than rolling back all of the changes immediately. This should allow you to copy what you need from the installation directory. To enable pause on error follow the instructions at
https://jazz.net/wiki/bin/view/Main/InsightFAQ#PauseOnInstallFail
I'm very sorry to hear that you've had so much trouble installing Rational Insight 1.0.1 on a RedHat system. Although it's of little consolation at this point, the Insight quality assurance and development teams did test the installation on RedHat 5 thoroughly and did not encounter this issue. We'll need more information about your specific environment, such as specific version of RedHat, 32 or 64 bit OS, DB2 edition and version, and as specific installation steps as your can provide, in order to work on reproducing the issue.
You can file a new defect against the Data Warehouse component at the following URL
http://jazz.net/jazz02/web/projects/Rational%20Insight#action=com.ibm.team.workitem.newWorkItem&ts=1296225676000
Please cc me on your new defect and I'll ensure that the Insight quality assurance teams are notified and can review your case.
A few pointers for anyone else who may hit a similar issue:
1. Selecting a manual installation of the database will place the database scripts on the system but will not execute them. This should allow you to proceed with your work around.
2. You can tell the installer to pause on error rather than rolling back all of the changes immediately. This should allow you to copy what you need from the installation directory. To enable pause on error follow the instructions at
https://jazz.net/wiki/bin/view/Main/InsightFAQ#PauseOnInstallFail
Hi Lawrence,
Don't worry. I like the challenges which is why I am frequently in the various beta programs. I have actually done each of the things you mentioned (good points for others) but I wanted an automatic install because I wanted to verify the automatic install would configure all linkages, parameters, etc.
This is pretty much a plain Jane install and utilizes an architecture hosted internally except it is the enterprise version of db2 rather than the express c.
Redhat 5.5 32 bit version. DB2 9.7.2 (express C). Install db2. Default id's and ports. Run Insight 1.0.1 install. Accept defaults.
It should be a simple matter for you guys to pull the various ddl files and note some are unix encoded and those that don't work are windows encoded. I simply pulled the files from your install and attempted to run them through the db2 command editor, when it balked, I knew where to concentrate my efforts.
I will file the defect and cc you on it.
Don't worry. I like the challenges which is why I am frequently in the various beta programs. I have actually done each of the things you mentioned (good points for others) but I wanted an automatic install because I wanted to verify the automatic install would configure all linkages, parameters, etc.
This is pretty much a plain Jane install and utilizes an architecture hosted internally except it is the enterprise version of db2 rather than the express c.
Redhat 5.5 32 bit version. DB2 9.7.2 (express C). Install db2. Default id's and ports. Run Insight 1.0.1 install. Accept defaults.
It should be a simple matter for you guys to pull the various ddl files and note some are unix encoded and those that don't work are windows encoded. I simply pulled the files from your install and attempted to run them through the db2 command editor, when it balked, I knew where to concentrate my efforts.
I will file the defect and cc you on it.
Hi Robert,
I'm very sorry to hear that you've had so much trouble installing Rational Insight 1.0.1 on a RedHat system. Although it's of little consolation at this point, the Insight quality assurance and development teams did test the installation on RedHat 5 thoroughly and did not encounter this issue. We'll need more information about your specific environment, such as specific version of RedHat, 32 or 64 bit OS, DB2 edition and version, and as specific installation steps as your can provide, in order to work on reproducing the issue.
Hi Lawrence,
Don't worry. I like the challenges which is why I am frequently in the various beta programs. I have actually done each of the things you mentioned (good points for others) but I wanted an automatic install because I wanted to verify the automatic install would configure all linkages, parameters, etc.
This is pretty much a plain Jane install and utilizes an architecture hosted internally except it is the enterprise version of db2 rather than the express c.
Redhat 5.5 32 bit version. DB2 9.7.2 (express C). Install db2. Default id's and ports. Run Insight 1.0.1 install. Accept defaults.
It should be a simple matter for you guys to pull the various ddl files and note some are unix encoded and those that don't work are windows encoded. I simply pulled the files from your install and attempted to run them through the db2 command editor, when it balked, I knew where to concentrate my efforts.
I will file the defect and cc you on it.
Hi Robert,
I'm very sorry to hear that you've had so much trouble installing Rational Insight 1.0.1 on a RedHat system. Although it's of little consolation at this point, the Insight quality assurance and development teams did test the installation on RedHat 5 thoroughly and did not encounter this issue. We'll need more information about your specific environment, such as specific version of RedHat, 32 or 64 bit OS, DB2 edition and version, and as specific installation steps as your can provide, in order to work on reproducing the issue.
This is a valid defect, I don't know why it was not caught or under what specific conditions it fails, the issue will be addressed in the next ifix.
Hi Lawrence,
Don't worry. I like the challenges which is why I am frequently in the various beta programs. I have actually done each of the things you mentioned (good points for others) but I wanted an automatic install because I wanted to verify the automatic install would configure all linkages, parameters, etc.
This is pretty much a plain Jane install and utilizes an architecture hosted internally except it is the enterprise version of db2 rather than the express c.
Redhat 5.5 32 bit version. DB2 9.7.2 (express C). Install db2. Default id's and ports. Run Insight 1.0.1 install. Accept defaults.
It should be a simple matter for you guys to pull the various ddl files and note some are unix encoded and those that don't work are windows encoded. I simply pulled the files from your install and attempted to run them through the db2 command editor, when it balked, I knew where to concentrate my efforts.
I will file the defect and cc you on it.
Hi Robert,
I'm very sorry to hear that you've had so much trouble installing Rational Insight 1.0.1 on a RedHat system. Although it's of little consolation at this point, the Insight quality assurance and development teams did test the installation on RedHat 5 thoroughly and did not encounter this issue. We'll need more information about your specific environment, such as specific version of RedHat, 32 or 64 bit OS, DB2 edition and version, and as specific installation steps as your can provide, in order to work on reproducing the issue.
This is a valid defect, I don't know why it was not caught or under what specific conditions it fails, the issue will be addressed in the next ifix.
As a simple workaround, issue a dos2unix against the .ddl and .sal files causing an issue.