Lotus Nut

During an installation of  Quickr Services for Websphere Portal, I ran into the follow error when uploading content from the Connectors:

"RepositoryException: Error while calling a function createItems of PLS data manager."

I discovered that there isn't much out there when searching for this. After some further investigation, we discovered that a mount point was getting full. Since we were installing this on Linux, I made sure that all of my mount points looked alright - per the Quickr InfoCenter:

• /: 1.5 GB or more (root directory)
• /opt: 4 GB or more. The default directory to install Lotus Quickr on Linux is /opt, which you could change to any directory you like later. By default, /opt is under / file system in default. If you choose to install Lotus Quickr under /usr, 5 GB or more is recommended.
• /home: 700 MB or more (home directory)
• /tmp: 600 MB or more. Run the following command to ensure that you have appropriate permissions in the /tmp directory: ls -ld /tmp. The result should look like the following: drwxrwxrwt 34 root root 4096 date_stamp time_stamp/tmp.

The box was setup with /local mounted to a hefty internal disk array, so we used /local in place of /opt for the directory where we would install Quickr. This is where everything from the installation should go, right? Wrong.

Our /home path was only 2GB and it filled up rather quickly. When performing the installation, a "quikradm" account is created. This is the owner of the DB2 information, and all of the DB2 data will reside in the home path for this user account! Since Quickr is only supported on RHEL4 currently, we couldn't resize that mount point on the fly. So after a quick reboot and resizing of the /home path (to 3GB), we were able to get up and running. At that point, we went through the process of using the db2relocatedb command to move the DB2 information over to the /local path.

So, how do you prevent this? I haven't tested this, but I imagine that by first creating the db2 user account with the proper home directory that the installation will see the existing account (and therefore install the DB2 data into that home path!).