Thursday, 14 August 2014

Here we go again - ERROR: Installation of IBM Cognos Business Intelligence has failed.

So, hopefully, this is the last post I'll ever write about this issue, following: -


Foiled Again - Installation of IBM Cognos Business Intelligence has failed. Return code : 1 

I had the same problem as before e.g. during the installation of IBM Business Monitor 8.0.1.2 on AIX 7.1: -

imcl -input installBAM8012.rsp -acceptLicense

I saw: -

ERROR: Error during "install" phase:

  ERROR:   Installation of IBM Cognos Business Intelligence has failed.

Return code : 1


Initially, I thought the problem was with the out-of-the-box AIX tar command, so I updated my .profile to ensure that the AIX Toolbox version of tar was picked up in the path ( /home/wasadmin/bin ) ahead of the system-wide path ( /usr/bin ).

However, this made no difference :-(

I then checked disk space utilisation.

For a previous PoC environment ( also AIX 7.1 ), the directory in which Cognos is installed: -

/opt/IBM/WebSphere/AppServer/cognos

is 3.27 GB in size.

When I checked this environment, I found that /opt/IBM/WebSphere was only 5 GB in size.

Therefore, I assumed that WAS + Cognos was almost certainly exceeding 5 GB.

Before

Filesystem    GB blocks      Free %Used    Iused %Iused Mounted on

...
/dev/fslv01        5.00      4.91    2%        4     1% /opt/ibm/WebSphere
...
 

After installation fails
 
Filesystem    GB blocks      Free %Used    Iused %Iused Mounted on
 
...
/dev/fslv01        5.00      3.13   38%    20879     3% /opt/ibm/WebSphere
...
 

After increase from 5 to 15 GB *AND* successful installation of BAM
 
Filesystem    GB blocks      Free %Used    Iused %Iused Mounted on

...
/dev/fslv01       15.00      9.76   35%   144857     6% /opt/ibm/WebSphere
...

In conclusion, ensure that you've got > 10 GB allocated to the file-system into which the WAS, BAM and Cognos binaries are going to be installed .....

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...