Proceed with Caution

An Instructive Tale About the Installation of SAP Sybase IQ

The aim of this document is to share the story of the installation of a complex software application and the steps taken to troubleshoot issues when they arise.

Overview

The implementation of a fast database is an essential part of everyday life for an organisation with diverse Business Intelligence and Analytics requirements, particularly in the realm of ‘train-of-thought’ querying. According to International Data Group, “Unstructured data is growing at a rate of 62 percent per year. When coupled with increased use of analytics, companies are finding new ways to maximize insights for things such as employee hiring and engagement, customer experience and product development and delivery. In fact, organizations want to find cheaper, faster and better ways for those insights to be delivered where they’re needed most. That means that organizations need to focus on how to effectively manage and store data in a smart way.” This journal will show the steps taken when installing the product and methods of troubleshooting when things don’t turn out quite as planned.

Columnar Databases

A columnar database is a database management system (DBMS) that stores data in columns instead of rows. The goal of a columnar database is to efficiently write and read data to and from hard disk storage in order to speed up the time it takes to return a query.

SAP Sybase IQ

Wikipedia states that “SAP IQ (also known as SAP Sybase IQ and Sybase IQ) is a column-based, petabyte scale, relational database software system used for business intelligence, data warehousing, and data marts. Produced by Sybase Inc., now an SAP company, its primary function is to analyse large amounts of data in a low-cost, highly available environment. SAP IQ is often credited with pioneering the commercialization of column-store technology.”

Installing SAP Sybase IQ for the first time After downloading the Express Edition (which has a limit of 5GB storage) from the SAP IQ web site, http://global.sap.com/campaign/ne/sybase/iq_16_free_trial_download/index.epx, and having a quick scan of the Installation Guide, Getting Started Guide and Release Notes, the install was started by right clicking on the ‘Setup.exe’ and choosing ‘Run as Administrator’. This was done on a Windows Server 2012 Standard machine with 16GB of RAM and 2 CPU’s running 2.54Ghz. The initial screen in Figure 1 sets the scene.

Figure 1

Then, SAP IQ identifies four Microsoft Visual C++ redistributables it needs to install. The installation proceeds with these tasks before showing the screen in Figure 3.

Figure 2

For this step, I chose to install into the default installation directory shown in Figure 3. Figure 3

In Figure 4 there is the customary, but indispensable warning message that you will overwrite any previous installations should you choose to continue. I continued. Figure 4

And next came the commonplace ‘Typical’ or ‘Custom’ screen. I chose the default of ‘Typical’.

Figure 5

For evaluation purposes, I chose to select the ‘Evaluate’ option. This means I will not have to provide a license key during the installation process.

Figure 6

And yes, we all have to agree to the terms of the license. Figure 7

The archetypal ‘Summary’ screen shown in Figure 8 before the ‘interesting’ part of the installation begins. Figure 8

After ‘Install’ is selected, the first event in the procedure is to install a java runtime environment. Figure 9

And here it stayed for a long while. Meanwhile, unbeknown and lurking in the background was an error message that only revealed itself when ‘Alt-Tab’ was pressed. Figure 10 – The visual representation of the error message

Figure 11 – The actual error message

This is what SAP has to say on the subject. https://scn.sap.com/thread/3545864 More details are shown in Figure 12 after clicking ‘Details’. Figure 12

The image in Figure 13 is taken from the Installation Guide. This is typically the first place I look when encountering unexpected installation behaviour.

Figure 13

Figure 14 shows a search of the entire C: drive. It should show where the log file resides. Back to more research. Figure 14

The Installation Guide shows that a file called IQ_Suite.log is generated. But on my installation, this file does not yet exist. I believe it will become available when the application terminates. However, after a period of time, the installation still proceeds. A surfeit of errors appears. I allow this to proceed as I want to see the outcome. Figure 15

Figure 16

Figure 17

Figure 18

At this point, the installation stops again. SAP has also encountered this error before. Figure 19 shows the attempted allocation of port 9999 to an RMI Service.

Figure 19

This time I cancel the installation and remove SAP Sybase IQ from Programs and Features. I also manually remove any folders that the application hasn’t cleaned up. Finally, I run CCleaner from Piriform, to cleanse the hard disk and Registry. In Figure 20 I start the installation again. I considered that if SAP Sybase IQ was trying to install a java runtime environment (JRE), and I already had the latest java installed, there may be a conflict. So if I removed java first, there should be no obstruction and the new JRE should install, and the remainder of SAP Sybase IQ would proceed to successful completion. I chose a more manageable installation folder this time round.

Figure 20

The message in Figure 21 appeared because I chose a sub folder of ‘Program Files’ and as this has a space in the folder name, the application terminated immediately. Figure 21

Figure 22 shows the start of the third attempt at installing SAP Sybase IQ, this time with a supported folder structure.

Figure 22

Unfortunately, the same error occurred. When researching, it was noted that having an old version of java on your machine might contribute to the error.

Figure 23

So by re-installing a completely fresh copy of java, I reconvened with my fourth attempt at installing SAP Sybase IQ. But as Figure 24 shows, I ended up un-installing again due to the same errors as before. Figure 24

Returning to the beginning again, I sought out any information that I might have missed. And sure enough, when I read the list of supported platforms, the small print gave up the details. In Figure 25 I could see that a Windows Server 2012 R2 platform was supported. I was installing on Windows Server 2012 Standard. Figure 25

I did not give up. My attention was focussed on the 64 bit Windows 7 SP1 machine I had available to me. Not an ideal platform to install a columnar database application on, but supported nonetheless. This time, SAP Sybase IQ appeared to install the JRE successfully and continue without error until the end. Almost. On the very last screen, you know, the one with the ‘Done’ button on it, I was informed that the installation had failed. I had successfully assigned the four default port numbers, 2638, 8282, 8283 and 9999. Using the command line to invoke a netstat –a command, I could see the port numbers that were listening or established. And now, at the very end after clicking ‘Done’, I was given the treasured log file, the IQ_Suite.log. Images of the Grand National horse race were exhibited in my mind. The horse that had led the race from start to finish, only to fall at the last fence. Nigel Mansell in the 1991 Canadian Formula 1 Grand Prix on the last lap, waving at the crowd, assured of winning, only to run out of petrol and be overtaken by the remainder of the entrants. Software installation can have this mildly disappointing effect on you. I looked at the log file, and I have to say, that if Carlsberg wrote software, this would probably be the best installation log in the world. I easily detected where the problem occurred. Figure 26 shows the extent of the problem and the next steps to take.

Figure 26

I looked in the lang.log file and located the ‘Summary’ section near the beginning. Figure 27 shows the outcome.

Figure 27

Oh well, I did look at the detail of the lang.log file and there were no other errors. I guess I’ll have to don the deerstalker hat for a while longer!! It also means that there will be a ‘Part Deux’ to this journal. Written by Steve Chapman, Senior BI Consultant, DSCallards 24th November 2015 www.thebusinessobjectspeople.com