CRNT-23667 - Updated for DB2 v9.7

git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@55470 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b

1 files changed, 47 insertions, 14 deletions

diff --git a/org.eclipse.stardust.docs.deployment/html/audittraildatabasesetup/db2.html b/org.eclipse.stardust.docs.deployment/html/audittraildatabasesetup/db2.html
index 0b4e582..c788eac 100644
--- a/org.eclipse.stardust.docs.deployment/html/audittraildatabasesetup/db2.html
+++ b/org.eclipse.stardust.docs.deployment/html/audittraildatabasesetup/db2.html
@@ -32,14 +32,50 @@ Version 9.1. DB2 can be downloaded from the following <a
 Download Website</a>.</p>

 <p>After downloading DB2, install DB2 onto the database server. The server

 installation directory is referred to as <tt>%DB2_HOME%</tt>.</p>

-<h3>Setting Up A DB2 Server</h3>

+<h2>Setting Up A DB2 Server</h2>
 <p>The following tasks must be performed to setup the DB2 server, database

 directories, buffer pools and security.</p>

-<p>@productname@ databases must run in read-committed mode. If the transaction

-isolation level is set to another mode, please change it. As part of the DB2

-installation there is an initialization file called <tt>db2cli.ini</tt>. To set

-the isolation level to <tt>READ_COMMITTED</tt>, add the following entry:</p>

-<pre>TxnIsolation = SQL_TXN_READ_COMMITTED</pre>

+<h3>Setting Transaction Isolation Level</h3>
+<p>Following table shows the DB2 UDB(Universal DataBase) equivalent to the ANSI SQL Isolation Level:</p>
+
+<table>
+	<tr>
+	<th>ANSI SQL Isolation Level</th>
+	<th>DB2 UDB Equivalent</th>
+	</tr>
+	<tr>
+	<td>SERIALIZABLE</td>
+	<td>Repeatable Read (RR)</td>
+	</tr>
+	<tr>
+	<td>REPEATABLE READ</td>
+	<td>Read stability(RS)</td>
+	</tr>
+	<tr>
+	<td>READ COMMITTED (default)</td>
+	<td>Cursor Stability (CS)</td>
+	</tr>
+	<tr>
+	<td>READ UNCOMMITTED</td>
+	<td>Uncommitted Read (UR)</td>
+	</tr>
+	
+
+</table>
+<p>To determine the isolation level in DB2, execute the following query:
+<pre>
+SELECT ISOLATION FROM SYSCAT.PACKAGES;
+
+</pre>
+
+<p>@productname@ databases must run in read-committed mode. So if the 
+ISOLATION value is CS, then you can proceed further. 
+Otherwise, execute the following query to change the ISOLATION level to CS.
+<pre>
+SET TRANSACTION ISOLATION LEVEL READ COMMITTED;
+
+</pre>
+
 <h3>Database Creation</h3>

 <p>A separate @productname@ database partition for the default DB2 instance has

 to be created. To perform this, use the DB2 command line processor and execute

@@ -86,7 +122,7 @@ allocated. In this example, system managed is used.</p>
 <pre class="CodeStandAlone">db2 =&gt; CREATE SYSTEM TEMPORARY TABLESPACE CARNOT_TEMP_TS PAGESIZE 8 K MANAGED BY SYSTEM USING ('C:/database/db2/CarnotTempTS') BUFFERPOOL CARNOTBUFFERPOOL</pre>

 <p>Note: These examples show tablespaces on a Windows platform, replace with

 the correct directory syntax in a Unix environment.</p>

-<h3>Setting Up DB2 to Work with JDBC 2.0</h3>

+<!-- <h3>Setting Up DB2 to Work with JDBC 2.0</h3>
 <p>Before version 8 of DB2, by default the database is configured to work

 with JDBC 1.1. To use JDBC 2.0, perform the following steps:</p>

 <ul>

@@ -94,7 +130,7 @@ with JDBC 1.1. To use JDBC 2.0, perform the following steps:</p>
     <li>Open a command prompt in <tt>&lt;%DB2_HOME%&gt;/java12</tt>.</li>

     <li>Set the BB2PATH variable to your <tt>&lt;%DB2_HOME%&gt;</tt>.</li>

     <li>Execute <tt>usejdbc2.bat</tt>.</li>

-</ul>

+</ul> -->
 <h3>Schema and Tables Generation</h3>

 <p>In DB2, the database users are actually system users i.e., given any

 platform windows/unix, the account you used to log in to the system will be used

@@ -114,7 +150,7 @@ provided with @productname@. <br>
 <br>

 Execute the System Console with the following arguments:</p>

 <pre>

-sysconsole -v -r COM.ibm.db2.jdbc.app.DB2Driver -dbtype DB2 -dbschema <i>&lt;dbschema&gt;</i> -l jdbc:db2://<i>&lt;host&gt;</i>:<i>&lt;port&gt;</i>/<i>&lt;schema&gt;</i> -d <i>&lt;user&gt;</i> -s <i>&lt;password&gt;</i> createschema

+sysconsole -v -r com.ibm.db2.jcc.DB2Driver -dbtype DB2 -dbschema <i>&lt;dbschema&gt;</i> -l jdbc:db2://<i>&lt;host&gt;</i>:<i>&lt;port&gt;</i>/<i>&lt;schema&gt;</i> -d <i>&lt;user&gt;</i> -s <i>&lt;password&gt;</i> createschema
 </pre>

 <p>The following is displayed after the command is invoked:</p>

 <pre>

@@ -126,17 +162,14 @@ Create @productname@ schema:
 Database type   : DB2

 Database URL    : jdbc:db2://<i>&lt;host&gt;</i>:<i>&lt;port&gt;</i>/<i>&lt;schema&gt;</i>

 Database user   : <i>&lt;user&gt;</i>

-Database driver : COM.ibm.db2.jdbc.app.DB2Driver

+Database driver : com.ibm.db2.jcc.DB2Driver
 

 Do you want to proceed? (Y/N):

 </pre>

 <p>Answer Y to proceed. The following is displayed after successful creation

 of the audit trail database schema.</p>

 <pre>Schema created.</pre>

-<p>Please note that you must use <tt>COM.ibm.db2.jdbc.net.DB2Driver</tt>

-instead of <tt>COM.ibm.db2.jdbc.app.DB2Driver</tt> if you want to generate the

-schema on a database residing on a remote machine. Additionally, you have to

-start the DB2 JDBC Applet Server service on the database server.</p>

+
 <h3>Alternative Schema Setup</h3>

 <p>If you do not have the ability to directly create the database schema

 because of privileges within your database environment or desire to create a