<h2 id="just-install">Just Install?</h2>
<p>So, I figured I would write a new post specifically for installing the latest DB2 Express-C on OpenSuSE as I had a bit of difficulty.</p>
<p>Ultimately, the path to success includes just following along the normal install (e.g. what I have automated below, changing yum and RH package names to zypper and SuSE package names) with 1 exception:</p>
<ul>
<li>db2prereqcheck</li>
</ul>
<h2 id="db2prereqcheck">db2prereqcheck</h2>
<p>Running db2prereqcheck will always crash.  Attempting to debug expc/db2/linuxadm64/bin/db2prereqcheck_exe shows that it is trying to compare a minimum version for SuSE, passing &quot;42.2 &quot; into atoi and then crashing in ____strtoll_l_internal.</p>
<p>After tring to get it work by chaning values in /etc/os-release and /etc/SuSE-release, I just gave up and commented out the call to db2prereqcheck_exe in expc/db2/linuxadm64/bin/db2prereqcheck.</p>
<p>And, that&#39;s it!  Enjoy DB2, and make sure to follow my <a href="http://craigstjean.com/2016/03/db2profile-and-zsh/">db2profile and zsh</a> post if you use zsh!</p>


DB2 Express-C 11.1 on OpenSuSE 42.2 Leap

<p><img src="/Fotolia_70774541_XS.jpg" alt=""></p>
<p><em>Yea yea, I&#39;m on a DB2 blog kick tonight. I&#39;ve been a fan of DB2 for a long time and it&#39;s about time I posted some of this!</em></p>
<h2 id="whats-the-goal">What&#39;s the goal?</h2>
<p>Simple:</p>
<ul>
<li>install DB2 (rootless)</li>
<li>configure it</li>
<li>configure fault monitors</li>
<li>setup autostart</li>
</ul>
<p>That&#39;s it!</p>
<h2 id="what-do-i-need">What do I need?</h2>
<p>This particular script assumes CentOS 7.  To test it out, you can create a quick CentOS 7 VM, or spin up a droplet on DigitalOcean if you wish.</p>
<p><strong>Note</strong>: make <em>sure</em> you have your host properly defined in /etc/hosts</p>
<p>Oh, and you should probably download DB2 Express-C while you&#39;re at it.</p>
<h2 id="just-get-on-with-it">Just get on with it!</h2>
<p><strong>Fine!</strong></p>
<script src="https://gist.github.com/craigstjean/c003384ab9d751842aba.js"></script>

<p>Ok, so a few points:</p>
<ul>
<li>The script is a combination of <a href="https://twitter.com/angoca">@angoca</a>&#39;s work on getting DB2 into Docker (<a href="https://github.com/angoca/db2-docker">https://github.com/angoca/db2-docker</a>), and some of my own additions (like enabling the fault monitor).</li>
<li>The script must be run as root (which it will validate in lines 3-7)</li>
<li>The script will validate that you defined your hostname in /etc/hosts (lines 9-14)</li>
<li>This will be a rootless install, and the instance owner will be db2inst1</li>
<li>For testing, I like to make myself an instance owner (probably not best practice, but in the context of a development environment I&#39;m fine with it) (line 23)</li>
<li>Lines 25-40 ensure needed packages are installed</li>
<li>Line 46 <em>actually installs DB2</em></li>
<li>Lines 49-52 make some tweaks to the configuration (e.g. port, OS authentication, etc.)</li>
<li>Line 57 configures DB2 with our tweaks, and also enables TCP communication to the database</li>
<li>Lines 60-84 configure auto-start and the fault monitors</li>
<li>Lines 88-94 do some cleanup, then prompt to reboot</li>
</ul>
<h2 id="what-do-i-do-next">What do I do next?</h2>
<p>With DB2 installed, all of my database user setup, database creation, table creation, etc. are all automated.  Maybe in another post I&#39;ll explain that.</p>
<p>Oh, and if you are using zsh, see my post on getting <code>db2profile</code> to work with zsh at <a href="http://www.craigstjean.com/2016/03/db2profile-and-zsh/">http://www.craigstjean.com/2016/03/db2profile-and-zsh/</a></p>
<p><em>Are you a DBA and did I do something wrong?  Let me know!  I&#39;ll get it fixed so I don&#39;t direct someone the wrong way</em></p>


Automated DB2 Installations with Fault Monitors!

<p><img src="/Fotolia_52415534_XS.jpg" alt=""></p>
<h2 id="what">What?</h2>
<p>To leverage DB2 commands from a *nix environment, you typically append the following to your shell profile script:</p>
<pre><code class="language-shell">. /path/to/db2/sqllib/db2profile
</code></pre>
<p><em>But</em>, if you try that in zsh, you get the lovely errors:</p>
<pre><code>zsh: awk: command not found...
AddRemoveString:12: command not found: awk
zsh: sed: command not found...
AddRemoveString:14: command not found: sed
zsh: sed: command not found...
AddRemoveString:18: command not found: sed
zsh: awk: command not found...
AddRemoveString:12: command not found: awk
zsh: sed: command not found...
AddRemoveString:14: command not found: sed
zsh: sed: command not found...
AddRemoveString:18: command not found: sed
zsh: awk: command not found...
AddRemoveString:12: command not found: awk
zsh: sed: command not found...
AddRemoveString:14: command not found: sed
zsh: sed: command not found...
AddRemoveString:18: command not found: sed
zsh: awk: command not found...
AddRemoveString:12: command not found: awk
zsh: sed: command not found...
AddRemoveString:14: command not found: sed
</code></pre>
<p><strong>And worse</strong>, you completely lost everything in <code>$PATH</code>.  Due to differences between the Bourne shell and the Z shell, the <code>AddRemoveString</code> function in <code>db2profile</code> splits your path variables in a way it can&#39;t recombine.</p>
<h2 id="so-how-can-i-fix-it">So how can I fix it?</h2>
<p>Luckily, there&#39;s an easy fix I&#39;ve come up with.  First, I copy <code>db2profile</code> to <code>db2profile.zsh</code>, then towards the bottom of <code>AddRemoveString</code> I add a line that replaces the newlines in the path variable with the correct delimiter:</p>
<p>In the end, it looks like this:</p>
<pre><code class="language-shell">AddRemoveString()
{
    if [ $# -ne 3 ]; then
       return 0
    fi
    var=$1        #The enviornment variable to be processed
    addrm_str=$2  #The new path to be used
    action=$3     #Action: a -&gt; add, r -&gt; remove
    if [ &quot;X${action?}&quot; != &quot;Xa&quot; -a &quot;X${action?}&quot; != &quot;Xr&quot; ]; then
        return 0  # return without doing anything
    fi
    awkval=&#39;$1 != &quot;&#39;${addrm_str?}&#39;&quot;{print $0}&#39;
    newval=`eval echo \\${$var:-&quot;&quot;} | awk &#39;{for (i=1; i&lt;= NF; ++i) \
          if( $i != VAR &amp;&amp; length($i) &gt; 0 ) print $i&quot;:&quot;}&#39; FS=&quot;:&quot; VAR=${addrm_str?}`
    newval=`echo ${newval?} | sed &#39;s/\: /\:/g&#39;`
    if [ &quot;X${action?}&quot; = &quot;Xa&quot; ]; then
        newval=${newval?}&quot;${addrm_str?}&quot;
    else
        newval=`echo ${newval?} | sed &#39;s/:$//&#39;`
    fi
+   newval=`echo ${newval?} | tr &#39;\n&#39; &#39;:&#39;`
    eval $var=\&quot;${newval?}\&quot;
    unset var addrm_str awkval newval
}
</code></pre>
<p>That line marked with a <code>+</code> is the line added (make sure to remove the <code>+</code> if you copy/paste).</p>
<p>Then, just update your <code>.zshrc</code> with:</p>
<pre><code class="language-shell">. /path/to/db2/sqllib/db2profile.zsh
</code></pre>
<p><strong>That&#39;s it!</strong></p>


Craig St. Jean

Craig St. Jean

Father, programmer, constant learner, @outsystems MVP, @pluralsight author

Chief Technology Architect