Download Content Manager 8.3

Content Manager Upgrade
from 8.3.11 to 8.4.2.3
[Type the document subtitle]
Uzma Khan
2/26/2013
Page 1 of 60
Table of Contents
Deployment Architecture ............................................................................................................................. 2
Softwares Versions ....................................................................................................................................... 3
Upgrade Existing DBs , ICMNLSDB and RMDB .............................................................................................. 4
Prepare SVR83DB2 for upgrade ................................................................................................................ 4
Applying 8.3 Fixpacks ............................................................................................................................ 4
Check ICMNLSDB , RMDB for upagrde .................................................................................................. 5
Upgrade/installation of Library Server on SVR83DB2 .............................................................................. 7
Prepare SVR84LS and SVR84RM ................................................................................................................. 14
Data Migration from Content Manager SVR83DB2 to SVR84LS and SVR84RM ......................................... 15
Installation of Library Server on SVR84LS ................................................................................................... 17
Installation of Resource Manager DB on SVR84RM................................................................................... 25
Installation of Resource Manager Application (SVR84RMAPP) ................................................................ 30
Installation verification on Windows®.............................................................................................. 53
Upgrading to the IBM DB2 Driver for JDBC and SQLJ (required) ................................................................ 54
Upgrading your Resource manager application............................................................................ 56
Binding bind files after installing fix packs ............................................................................................ 58
Page 2 of 60
Deployment Architecture
Content Manager 8.3
SAN
SVR83RMAPP
SVR83DB2
Content Manager 8.4
SAN
SVR84RMAPP
SVR84LS
SVR84RM
Page 3 of 60
Softwares Versions
SNO Server
Name
Replace
Older
Server If Version
applicable
1.
SVR84RM
SVR83DB2
Newer
/Change version/Change
DB2 Enterprise
Server 8.2.9
DB2 Enterprise
Server 9.7.3
Content Manager
8.3.11
CM 8.4.2.3 –
Resource manager
Database
DB2 Enterprise
Server 8.2.9
DB2 Enterprise
Server 9.7.3
DB : RMDB
2.
SVR84LS
DB :
ICMNLSDB
CM 8.4.2.3Library Server
Database
3.
SVR83RMAPP SVR84RMAPP
Resource
Manager
Application :
ICMRM
Webshere
Application Server
5.1.1
Webshere
Application
Server 7.0.0.13
DB2 Run time Client
8.1.11
DB2 Data Run
time Client
9.7.3
Content Manager
8.3.11
Content
Manager
(ICMRM)
8.4.2.3
Page 4 of 60
Upgrade Existing DBs , ICMNLSDB and RMDB
Prepare SVR83DB2 for upgrade
Applying 8.3 Fixpacks
1. Install CM 8.3 fix pack 3a from (update_win_8.3.00.350.ZIP) after mapping the network
drive
2. Install CM 8.3 fix pack 11 from (update_win_8.3.00.950.zip) after mapping the network
drive
3. Restart the computer(SVR83DB2)
4. Install Db2 8.1.11 Fix Pack 18 from (FP18_WR21443_ESE) after mapping the network drive
5. Apply post –installation from readme.txt of fixpack for each database installed on that
server.
 db2updv8 –d icmnlsdb
 db2updv8 –d rmdb
 Run the db2 command line processor
o db2 terminate
o db2 CONNECT TO <dbname>
o db2 BIND c:\ibm\sqllib\BND\@db2ubind.lst BLOCKING ALL GRANT PUBLIC
ACTION ADD
o db2 BIND c:\ibm\sqllib\BND\db2schema.bnd BLOCKING ALL GRANT PUBLIC
sqlerror continue
o db2 terminate
6. Restart the server
Page 5 of 60
Check ICMNLSDB , RMDB for upagrde
SVR83DB2 from where you need to migrate DATA
Copy db2ckupgrade.exe and db2dbmig.txt from the same path \DB2 Enterprise 9.7 for limited use
CM\DB2 Enterprise Edition\ESE\image\db2\Windows\utilities to D:\IBM\SQLLIB\BIN On SVR83DB2 (
THE machine from where you need to migrate data (ICMNLSDB , RMDB) )
1. Run Command Line Processor on SVR83DB2 machine
Rum commands as under
2.
Terminate
3. C:\IBM\SQLLIB\BIN>db2ckupgrade rmdb -l db2ckupgarde.log -u rmadmin -p
rmadmin
db2ckupgrade was unsuccessful. Please look at logfile for more details.
Check the db2ckupgarde.log file on the same directory
If error appears
SQL1015N The database is in an inconsistent state. SQLSTATE=55025
Than do the following
C:\IBM\SQLLIB\BIN>db2
db2 => list applications
If applications exits than
db2 => force applications all
DB20000I The FORCE APPLICATION command completed successfully.
DB21024I This command is asynchronous and may not be effective immediately.
db2 => terminate
DB20000I The TERMINATE command completed successfully.
Page 6 of 60
C:\IBM\SQLLIB\BIN>db2ckupgrade rmdb -l db2ckupgarde.log -u rmadmin -p rmadmin
db2ckupgrade was successful. Database(s) can be upgraded.
ICMNLSDB
C:\IBM\SQLLIB\BIN> db2ckupgrade icmnlsdb -l db2ckupgarde.log -u icmadmin -p icmadmin
db2ckupgrade was unsuccessful. Please look at logfile for more details.
Error 1 : SQL1015N The database is in an inconsistent state. SQLSTATE=55025
Repeat the above steps.
Error 2 :
SQL1249N "The DATALINK data type is not supported. "DB2EXT.GETDATALINKCONTENT" must
be dropped or altered to avoid using the DATALINK data type.
Execute following command from db2 prompt
db2
db2
db2
db2
DROP
DROP
DROP
DROP
SPECIFIC
SPECIFIC
SPECIFIC
SPECIFIC
FUNCTION
FUNCTION
FUNCTION
FUNCTION
DB2EXT.DATALINKCONTENT1
DB2EXT.DATALINKCONTENT2
DB2EXT.DATALINKCONTENT4
DB2EXT.DATALINKCONTENT3
Run the command until it gets successful.
Page 7 of 60
Upgrade/installation of Library Server on SVR83DB2
1. Take the snapshot of existing machine
2. Run the installer of CM 8.4.2 from extracting CZL7JML.ZIP after mapping network drive For
backing up existing database it took approximately 2 and half hour so be patient to
complete the installation. (Note: Depending upon the Data, For our production it took 4
hours with 1 TB data.)
3. Install fixpack after extracting update_win_8.4.02.300.ZIP , if its remote drive than map network
drive.
4. Run the configuration, if It doesn’t start automatically than from command prompt type
config_CM to run the configuration wizard.
Change the host name to full domain name e.g. SVR83DB2.abc.com.pk
Page 8 of 60
Page 9 of 60
Page 10 of 60
Page 11 of 60
Page 12 of 60
Press next to start the configuration
Page 13 of 60
Page 14 of 60
Prepare SVR84LS and SVR84RM
1.
2.
3.
4.
5.
Prepare two servers SVR84LS and SVR84RM with 32 bit windows
Create icmadmin on SVR84LS and rmadmin on SVR84RM
Add above mentioned users in Administrators user group
Logged in on both servers with above mentioned users
Map Network drive
Extract Db2 from DB2_ESE_97_Win_x86.zip file into \ DB2 Enterprise 9.7 for limited use CM\DB2
Enterprise Edition\ESE\image and map the Network drive
Run Setup from above mapped drive (with all default setting on path D:\ without any space in
path ) db2 enterprise edition restricted use for CM on both machines.
Map another Network drive for FixPack 3a after extracting v9.7fp3a_nt32_server .ZIP into Fix
Packs\Fix Pack 3a\v9.7fp3a_nt32_server\SERVER
Run Setup and Choose work with existing for DB2 Enterprise Server and rest all default settings.
After installation:
6.
7.
8.
9.
10.
Create Standard empty database named ICMNLSDB on SVR84LS and RMDb on SVR84RM
Install Net Search Extender as mentioned in “NET Search Extender Installation “
Shut down machines
Take the snapshot for both machines
Power On both machines
Page 15 of 60
Data Migration from Content Manager SVR83DB2 to
SVR84LS and SVR84RM
Note : Save the content of the base table of the DB2EXT.DBDEFAULTS view before you perform the
database migration by running the following statements:
db2 "CREATE TABLE DBDEFAULTSCOPY LIKE DB2EXT.TDBDEFAULTS";
db2 "INSERT INTO DBDEFAULTSCOPY SELECT * FROM DB2EXT.TDBDEFAULTS";
1. After the installation mentioned above “Upgrade/installation of Library Server on SVR83DB2”
Take full Offline backup with data of ICMNLSBD and RMDB on SVR83DB2 machine
a. BACKUP DATABASE RMDB TO "C:\TEST" WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1
WITHOUT PROMPTING;
b. BACKUP DATABASE ICMNLSDB TO "C:\TEST" WITH 2 BUFFERS BUFFER 1024
PARALLELISM 1 WITHOUT PROMPTING;
2. Copy database RMDB and index directories on SVR84RM and ICMNLSDB and index
directories on SVR84LS from C:\Test .
3. Restore database ICMNLSDB on SVR84LS and RMDB on SVR84RM with the following
commands
a. RESTORE DATABASE ICMNLSDB FROM "C:\Backup Databases\" TO "D:” WITHOUT
PROMPTING;
b. RESTORE DATABASE RMDB FROM "C:\Backup Databases\" TO "D:” WITHOUT
PROMPTING;
If Error appears than see the db2diag.log file if error
ADM0501C A stack overflow exception has occurred. The DB2 instance has
terminated abnormally. To remedy this problem, you may increase the default
stack size for db2syscs.exe using the db2hdr utility as follows: db2hdr
\sqllib\bin\db2syscs.exe /s:<stackreserve>[,<stackcommit>] Note that increasing
the default stack size will consume virtual memory space and may reduce the
maximum number of concurrent connections. Contact IBM Support for further
assistance
Than do the following
4. Go to D:\ibm\sqllib\MISC on command prompt {On both machines}
a. D:\IBM\SQLLIB\MISC>db2hdr d:\ibm\sqllib\bin\db2sysc.exe
Creation Time: Sun May 16 00:01:43 2010
Created to run on a I386 class machine
Page 16 of 60
Characteristics
Image is an EXE
Image has its Relocation Information removed
Image is Large Address space capable
Minium OS level is 4.0
Image must be loaded at 00400000
Stack Reserved/Committed is 256K[262144],16K[16384]
b. db2 => force applications all
DB20000I The FORCE APPLICATION command completed successfully.
DB21024I This command is asynchronous and may not be effective immediately.
c. db2 => db2stop
DB20000I The DB2STOP command completed successfully.
d. D:\IBM\SQLLIB\MISC>db2hdr d:\ibm\sqllib\bin\db2sysc.exe /s:600
Stack Reserved/Committed is 600K[614400],16K[16384]
d:\ibm\sqllib\bin\db2sysc.exe updated successfully
e. D:\IBM\SQLLIB\MISC>db2hdr d:\ibm\sqllib\bin\db2sysc.exe
Creation Time: Sun May 16 00:01:43 2010
Created to run on a I386 class machine
Characteristics
Image is an EXE
Image has its Relocation Information removed
Image is Large Address space capable
Minium OS level is 4.0
Image must be loaded at 00400000
Stack Reserved/Committed is 600K[614400],16K[16384]
D:\IBM\SQLLIB\MISC>db2start
11/24/2010 15:41:21 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
5. Restore database ICMNLSDB on SVR84LS and RMDB on SVR84RM with the following
commands
a. RESTORE DATABASE ICMNLSDB FROM "C:\test\" TO "D:” WITHOUT PROMPTING;
b. RESTORE DATABASE RMDB FROM "C:\test\" TO "D:” WITHOUT PROMPTING;
6. db2 => db2stop
DB20000I The DB2STOP command completed successfully.
7. Run Command D:\IBM\SQLLIB\MISC>db2hdr d:\ibm\sqllib\bin\db2sysc.exe /s:256
8. db2 => db2start
11/24/2010 15:41:21 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
9.
10.
Page 17 of 60
Installation of Library Server DB on SVR84LS
11. Run the installer of CM 8.4.2 after extracting CZL7JML.ZIP and after mapping network
drive for ONLY LS on SVR84LS
12. Install update after extracting update_win_8.4.02.300 and if Network drive than after mapping.
13. Check and verify all path values in table ICMSTSYSCONTROL in ICMNLSDB and changed to
new path location as per new system.
14. Run the only LS configuration, if It doesn’t start automatically than from command prompt
type config_CM to run the configuration wizard, Select all values presented on below
pasted screens .
Page 18 of 60
Page 19 of 60
Page 20 of 60
Page 21 of 60
Page 22 of 60
Page 23 of 60
Page 24 of 60
Page 25 of 60
Installation of Resource Manager DB on SVR84RM
1. Run the installer of CM 8.4.2 from \Content Manager 8.4.2\CZL7JML after mapping
network drive for ONLY RMDB on SVR84RM
2. Install update after extracting update_win_8.4.02.300 and if Network drive than after mapping.
3. Run the only RMDB configuration, if It doesn’t start automatically than from command prompt
type config_CM to run the configuration wizard, Select all values presented on below
pasted screens
4. Click Next for next four screens by choosing default values, verify that all paths and
working directly paths are correct
Page 26 of 60
Page 27 of 60
Page 28 of 60
Click NEXT for next screen
Page 29 of 60
Now
5. Rrestart the server SVR84RM and SVR84LS
Page 30 of 60
Installation of Resource Manager Application
(SVR84RMAPP)
We are prepare the new Resource Manager Application server without touching
or upgrading the existing server SVR83RMAPP
1.
2.
3.
4.
5.
6.
7.
8.
9.
Install WAS 7.0 after extracting the Part No C1G0QML.ZIP and if its on network drive than after
mapping
Install update after extracting the Part No C1G0RML.ZIP and if its on network drive than after
mapping
Install update installed after mapping the network path \WAS 7.0\C1G0RML , run Launchpad and
select update installer.
Install WAS 7 Fix Pack 13
Install db2 runtiem client \\Content Manager 8.4.2\DB2 Enterprise 9.7 for limited use CM\RTCL and if
it’s on network drive than after mapping ,
Install fix pack 3a from dataserver run time client from \DB2 9.7\Fix Packs\Fix Pack
3a\v9.7fp3a_nt32_rtcl_EN.exe and if it’s on network drive than after mapping ,
Install CM 8.4.02 and if it’s on network drive than after mapping
Install FixPack update from update_win_8.4.02.300 and if it’s on network drive than after mapping ,
Catalog SVR84RM and SVR84LS abd ICMNLSDB and RMDB by running following commands
Save these commands in bat file in D:\ibm\SQLLIB\BIN directory and run from there
@echo Starting Database Mgr... >> CatalogDB.log
setlocal
rem #################################
rem # fill in with appropriate values for <common_ip_address>. Remember to check with the
rem # instructor for the ip of the <common> machine.
rem # Also, make sure that the userid/password combination is correct. For these labs,
rem # it should be db2admin/was1edu.
rem ################################
db2 -z CreateDB.log catalog tcpip node SVR84RM remote SVR84RM server 50000
db2 -z CreateDB.log catalog tcpip node SVR84LS remote SVR84LS server 50000
Page 31 of 60
db2 -z CreateDB.log catalog db icmnlsdb as icmnlsdb at node SVR84LS
db2 -z CreateDB.log connect to icmnlsdb user icmadmin using icmadmin
db2 -z CreateDB.log connect reset
db2 -z CreateDB.log catalog db rmdb as rmdb at node SVR84RM
db2 -z CreateDB.log connect to rmdb user rmadmin using rmadmin
db2 -z CreateDB.log connect reset
10. Shut down the machine
11. Take snapshot
12. Run the cm configuration from command prompt config_CM
Page 32 of 60
Click NEXT for next 4-5 screen after verifying paths for DB2 and application server .
Page 33 of 60
Page 34 of 60
Page 35 of 60
Page 36 of 60
Page 37 of 60
Page 38 of 60
Page 39 of 60
Page 40 of 60
Page 41 of 60
Page 42 of 60
Page 43 of 60
Page 44 of 60
Page 45 of 60
Page 46 of 60
Page 47 of 60
Click Next for next screen.
Page 48 of 60
13. Start icmrm application after logged into was administration console
14. Logged into system administration client and than click RMDB
If following error “Internal server Error” appears, see log file in websphere logs and see the text below
to solve the issue
Problem(Abstract)
[6/29/06 13:38:56:670 EDT] 00000050 J2CUtilityCla E J2CA0036E:
An
exception occurred while invoking method setDataSourceProperties
on
com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used
by resource SiBuss DB2_CF : com.ibm.ws.exception.WsException:
DSRA0023E: The DataSource implementation class
"COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource" could not be
found.
Cause
The cause of the problem is that the WebSphere Application Server Java™
virtual machine (JVM) could not find the JDBC JAR file, in this example the
DB2 JAR, in its classpath that contains the implementation class. The most
likely cause is that the classpath of the JDBC Provider configuration has used
a WebSphere Application Server variable, for example,
Page 49 of 60
DB2_JDBC_DRIVER_PATH, but the variable has not been set for the
corresponding WebSphere Application Server.
Resolving the problem
Set DB2_JDBC_DRIVER_PATH = d:\ibm\sqllib\java for allscopes
Check the database provider and data source configuration to see if the
WebSphere Application Server JDBC driver path system variable is used in
the classpath in the JDBC Provider and ensure the variable is set for the
correct scope. That is, if the JDBC provider is defined at the node scope, the
JDBC driver path system variable must be defined at the node scope.
For example, if the J2CA0036E and DSRA0023E are logged in the application
server's SystemOut.log, then check the JDBC Provider's configuration to
Application Server's DB2_JDBC_DRIVER_PATH variable (if it is used in the
JDBC Provider configuration) and confirm that variable points to the correct
location of the driver. Also, confirm that the userID that is used to run the
Java process has the correct permission to use the driver.
Similarly, if the J2CA0036E and DSRA0023E are logged in the Deployment
Manager's (DMgr's) SystemOut.log file, then check the JDBC Provider
configuration for the node and cell scopes. Check the JDBC Provider's
configuration to see if the variable is used and confirm that variable points to
the correct location for the driver (from Administrative Console Resources
> WebSphere Variables) and confirm the use
If error appears
“DGL5162A: System Managed Storage (SMS) request to resource manager failed: 'ICM9753:
Resource manager administrative logon or credential refresh required.'”
After you successfully upgrade to DB2 Content Manager V8.4 or later, you
have a problem accessing resource managers in the DB2 Content Manager
system administration client. Error message ICM9753 is shown in a client
window. When you check definitions in the resource manager access table, it
shows that column ACC_USERNAME is defined as CHAR(32).
Symptom
After you successfully upgrade to DB2 Content Manager V8.4 or later, you
have problems accessing resource managers in the DB2 Content Manager
system administration client. The following error message is shown when
you try to log on:
DGL5162A: System Managed Storage (SMS) request to
resource manager failed: 'ICM9753: Resource manager
administrative logon or credential refresh required
When you check definitions in the resource manager RMACCESS table, it
shows that column ACC_USERNAME is defined as CHAR(32). It should be
VARCHAR(32) instead.
Diagnosing the problem
The ACC_UserName column in the resource manager RMACCESS table is
defined as CHAR(32) instead of VARCHAR(32).
Resolving the problem
To fix the problem, change and re-create the RMACCESS table. Contact your
database administrator before you alter the table definition. Ensure that you
Page 50 of 60
back up your database before you proceed with these changes:
For a DB2 database:
The following are sample steps to alter the table definition in DB2:
1. Stop the resource manager application server.
{If we already run CM 8.4.2 on RMDB than its already converted to
VARCHAR(32), than change rmadmin for acc_userid =0 and icmadmin
for acc_userid=1 }
2. Connect to rmdb using rmadmin.
3. Run the command
db2look -d rmdb -e -tw rmaccess -i rmadmin -w password -o
db2look.sql
, then save the file.
This command exports the RMACCESS table definition to the
db2look.sql file and edits the file to set the ACC_USERNAME
definition from CHAR(32) to VARCHAR(32),
4. Run the command db2 export to <filename> of ixf
select * from rmaccess.
This command exports the data entry in the RMACCESS table to the
given file name.
5. Drop the RMACCESS table.
6. Create the table by running db2 -t -f db2look.sql.
7. Import the data back into the table by running the following
command, where filename is the file that you specified in Step 4:
db2 import from <filename> of ixf insert into
RMACCESS.
8. Run the command db2 describe table
rmadmin.rmaccess to verify that the
ACC_USERNAME column changed to VARCHAR(32).
9. Run the command db2 select hex(acc_username) from
rmadmin.rmaccess.
This command shows the user names in hexadecimal format. You should not
see any trailing blank spaces, which show up as hex 20 at the end of the
user IDs. If there are trailing spaces, run the following command to reset the
value of the ACC_USERNAME column so that it trims off the trailing space
characters.
select hex(acc_username) , acc_userid from rmadmin.rmaccess
db2 update rmadmin.rmaccess set acc_username='<your
username>' where acc_userid=<for each acc_userid in the
Page 51 of 60
table>
update rmadmin.rmaccess
where acc_userid=0
set acc_username='rmadmin'
update rmadmin.rmaccess
where acc_userid=1
set acc_username='icmadmin'
update rmadmin.rmaccess set acc_password='rmadmin' where
acc_userid = 0
update rmadmin.rmaccess set acc_password='icmadmin' where
acc_userid = 1
if Resource manager still does not connected than do the
following
connect to <LS DB>
select hex(substr(encryptionkey,9,24)) as key from icmstsyscontrol
connect to <RM DB>
select Hex(substr(acc_public_key,1,24)) as key from rmaccess where
acc_userid=1
Compare keys of LS and RM and if they are different
connect to <RM DB>
update rmaccess set acc_public_key=x?LS key string? where acc_userid=1
10. Start the resource manager application server again.
MUST Do this step before
proceeding further
11. Copy lbosdata from SVR83RMAPP machine to SVR84RMAPP and map
the SAN disks same as mapped earlier.
12. Now check from CM client for documents searching and retrieval.
Here Upgrade is done…Below are the references you might need during
the said upgrade.
Page 52 of 60
NET Search Extender Installation
1. IF NSE is on network drive than Map network drive on both machines
\DB2 9.7\Fix Packs\Fix Pack 3a\NSE\windows\install
2. Run setup from path NSE\image\windows\install \, choose db2copy1 and user name and
password db2admin\******* on both machines
3. Open db2 command window and type as under
4. db2extmdb icmnlsdb
5.
Text search only: When you migrate your DB2 Universal Database Net Search Extender database,
do not remove the old db2v8 directory. Make sure to rebind the library server database. Otherwise,
you might receive the error: DGL5056A: Text search was attempted on a
database that is not enabled for text search.
db2rbind icmnlsdb -l C:\logfile.txt all -u icmadmin -p password
db2rbind rmdb -l C:\logfile.txt all -u rmadmin -p password
6.
Recommendation: Create an index on the RMOBJECTS table to improve the background
performance:
Option
Description
DB2
Universal
Database
Enter the command: CREATE INDEX IDX_OBJ_REFDATE ON RMOBJECTS
(OBJ_REFERENCEDDATE, OBJ_STATUS, OBJ_STAGEDVOLUMEID); RUNSTATS ON
TABLE schema name.RMOBJECTS WITH DISTRIBUTION AND DETAILED INDEXES
ALL;
7. Clean up the DB2EXT.DBDEFAULTS view after completion of the database migration by
running the following statements:
db2 "DELETE FROM (SELECT ROW_NUMBER() OVER
(PARTITION BY NAME) AS COUNT FROM DB2EXT.TDBDEFAULTS) WHERE COUNT > 1";
db2 "UPDATE DB2EXT.TDBDEFAULTS T1 SET T1.VALUE = (SELECT S1.VALUE FROM
DBDEFAULTSCOPY S1
WHERE T1.NAME = S1.NAME AND T1.VALUE <> S1.VALUE FETCH FIRST 1 ROWS ONLY)
WHERE T1.NAME IN (SELECT DISTINCT S2.NAME FROM DBDEFAULTSCOPY S2,
DB2EXT.TDBDEFAULTS T2
WHERE T2.NAME <> 'VERSION' AND T2.NAME = S2.NAME AND T2.VALUE <> S2.VALUE)";
Both statements might return a warning like "SQL0100W No row was found for FETCH,
UPDATE or DELETE". In these cases, you can regard the execution as successful.
Page 53 of 60
Installation verification on Windows®
Complete the following steps to verify that Net Search Extender is correctly installed.

Non partitioned environment:
a. Set up the sample text indexes as follows:
i. Call db2cmd to open a DB2® command window.
ii. Change to sqllib\samples\extenders\db2ext
iii. From the DB2 command window, call nsesample.bat yourdb. Note that this
command creates the database if it does not already exist.
iv. Check the generated output file nsesample.log in the current directory.
b. Call the following sample queries to execute in the DB2 command window:
v. Connect to your database using db2 connect to yourdb
vi. Execute the sample queries using db2 -tvf search
vii. Check the results of the queries contained in the script. Note that every query
should return one or more hits.
If there are no errors in the nsesample.log file and all the queries are working, Net Search Extender is
successfully installed
Backing up and restoring text indexes
You must stop the Net Search Extender services prior to backing up or restoring enabled databases and text
indexes.

To back up enabled databases and text indexes created by Net Search Extender:
c. Find out which indexes Net Search Extender has created and where they are stored. Call
a select statement on the db2ext.textindexes view:
d. db2 => connect to icmnlsdb user icmadmin using icmadmin
e. db2 "select indschema, indname, indexdirectory from db2ext.textindexes" on machine
ABC
f. Ensure that no index update is running, and then stop Net Search Extender services.
Issue the following command:
terminate
db2text stop
g. After backing up the database, back up the index directories and subdirectories.
From C:\ TextSearchIndex, C:\ TextSearchIndexWD and C:\IBM\SQLLIB\db2ext\indexes
h. Restart Net Search Extender services. Issue the following command:
db2text start

To restore the enabled databases and text indexes created by Net Search Extender:
i. Stop Net Search Extender. Issue the following command:
Page 54 of 60
db2text stop
j. Restore the backup copies of the index directories to the same path as before.
k. Restart Net Search Extender. Issue the command:
db2text start
If index directories Path is different on Target machine:
D:\IBM\SQLLIB\db2ext>db2text alter index ICMUU01665001001 for text index directo
ry "D:\IBM\SQLLIB\db2ext\indexes" work directory "D:\IBM\SQLLIB\db2ext\indexes"
connect to icmnlsdb user icmadmin using icmadmin
for every index found in select indschema, indname, indexdirectory from
db2ext.textindexes
NOTE: D:\IBM\SQLLIB\db2ext\indexes is a new directory
Flush the package cache after fixing index errors:

db2 flush package cache dynamic
That’s All.
Upgrading to the IBM DB2 Driver for JDBC and SQLJ
(required)
Page 55 of 60
By using type 4 mode in the JDBC driver, you can remove the DB2® Content Manager Version
8.4.2 Java™ dependency on a DB2 run-time client.
Prerequisites
Preparing DB2 Information Integrator for Content Version 8.3 configuration for upgrade
DB2 Content Manager Version 8.4.2 only supports the IBM® DB2 Driver for JDBC and SQLJ
(com.ibm.db2.jcc.DB2Driver). Previously, DB2 Content Manager Version 8.3 supported only
the DB2 JDBC Type 2 Driver (com.ibm.db2.jdbc.app.DB2Driver). Applications that use the
DB2 Content Manager API must only load a supported version of the DB2 Driver for JDBC and
SQLJ. In many cases, this automatically happens on upgrade. However, in some cases you must
change the application or its deployment environment so that a supported driver is used. For
example, if an application does not use cmbenv81 to set the CLASSPATH variable, then you
must revise the application in the following ways:
1. Update the application's CLASSPATH to include the correct JAR files. Version 8.4.2 comes with a
DB2 Driver for JDBC and SQLJ, located in IBMCMROOT/lib: db2jcc.jar, db2jcc_license_cu.jar,
and db2jcc_license_cisuz.jar. The old Version 8.3 db2Java.zip file can be removed from the
CLASSPATH.
2. If the application reference any classes that are specific to the old type 2 JDBC driver, then
change the application to use the generic JDBC classes instead of the specific DB2 classes. For
example, if the application caught the exception COM.ibm.db2.jdbc.DB2Exception, then
java.sql.SQLException should be used instead.
3. Recommendation: Run in type 4 mode to avoid the need to install and maintain the DB2 runtime client. Because the database catalog is not used in type 4 mode, additional information is
needed to create a type 4 connection. This includes the remote database name, the database
server's host name, and the database server's port. In Version 8.3, these three values were
stored in cmbicmsrvs.ini when creating a new server connection. However, these were optional
settings during configuration in Version 8.3.
The exact fields in cmbicmsrvs.ini are:
ICMREMOTEDB=icmnlsdb
ICMHOSTNAME=cmserver.svl.ibm.com
ICMPORT=50000
Note that the ICMSERVER field in the INI file is still the server name that is passed in when
connecting to a server. This matches the Version 8.3 behavior. However, in Version 8.3 the
ICMSERVER name was required to be the locally cataloged database alias. If type 4 mode is used
in Version 8.4.2, then the ICMSERVER name does not need to be a local database alias.
4. Optional: After the client is configured to use a type 4 connection and the correct JAR files, you
can remove the DB2 run-time client from the client machine.
Page 56 of 60
Alternatively, you can stay in type 2 mode if you upgrade the DB2 run-time client to Version 9
Fix Pack 3 or later, and use the db2jcc.jar of the DB2Runtime instead of the db2jcc.jar that
comes with DB2 Content Manager. The DB2 V8 run-time client does not support Java Version
Upgrading your Resource manager application
Because the Version 8.3 and Version 8.4.2 resource manager applications require different version of the
WebSphere® Application Server, you cannot upgrade the resource manager application from Version 8.3 to
Version 8.4.2. Instead, you must install and configure a brand-new Version 8.4.2 resource manager application
into WebSphere Application Server Version 6.1.
Important: For Version 8.4.2, the icmrm application is deployed on application server server1 instead of on
icmrm.
After the DB2® Content Manager Version 8.4.2 upgrade, you can choose to run the installation and
configuration wizards for the resource manager application. Make sure to complete the following steps:
1.
In the WebSphere Application Server administration console, shut down your DB2 Content Manager
Version 8.3 applications (resource manager and eClient).
2.
Install the resource manager application.
3.
In the configuration wizard, fill in the fields to configure the resource manager application.
4.
Option
Description
If you replaced your WebSphere
Application Server with Version 6.1
Recommendation: Reuse the exact same Resource manager Web
application name (for example, icmrm), HTTP port (for example, 80 or
9080), and HTTPS port (for example, 443 or 9443) that you used in the
Version 8.3 resource manager application.
If you are running WebSphere
Application Server Version 6.1 on a
separate system from the previous
version
Recommendation: Reuse the exact same Resource manager Web
application name (for example, icmrm), HTTP port (for example, 80 or
9080), and HTTPS port (for example, 443 or 9443) that you used in the
Version 8.3 resource manager application.
If you are running WebSphere
Application Server Version 6.1
concurrently with another version on
the same system
Because two resource managers cannot use the same Web application name
or ports, you must specify different values for the Resource manager Web
application name, HTTP port, and HTTPS port.
If you changed any of your Resource manager Web application name, HTTP port, or HTTPS
port values for Version 8.4.2, then make sure to eliminate any pending text indexes that used the
original port number. Otherwise, the library server will no longer be able to communicate with the
resource manager.
a.
Find pending text index items by entering the following SQL command:
db2 "select indname, logviewname, from db2ext.textindexes
where functionname like 'ICMFETCH%'"
Page 57 of 60
Example output:
INDNAME
LOGVIEWNAME
----------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------ICMUU01008001TIE
LOGIX341718
ICMUU01010001TIE
LOGIX004118
ICMUU01012001TIE
LOGIX260519
b.
For each logviewname, count the pending text rows by entering the following SQL command:
db2 "select count(*) from db2ext.LOGIX341718"
where LOGIX341718 represents each logviewname.
Example output:
1
----------0
1 record(s) selected.
c.
For each row found, update the text index on each index name corresponding to that
logviewname.
db2text update index icmadmin.ICMUU01008001TIE for text
connect to icmnlsdb user icmadmin using password
d.
Repeat the steps until you removed all pending text rows.
5.
Undeploy and uninstall the DB2 Content Manager Version 8.3 resource manager application from the
WebSphere Application Server administration console.
6.
For multiple resource managers only: Manually update values in each resource manager database
to avoid an Error writing to server log message.
a.
b.
In the system administration client, expand Resource Managers.
For each resource manager, list the Server Definitions and update the properties of its peers
to reflect their new deployment information in WebSphere Application Server Version 6.1. The
hostname, port number, and path might have changed.
Page 58 of 60
Note that in Version 8.4.2, the resource manager application log now defaults to one consolidated spot:
WAS_HOME/profiles/profileName/logs/server1/SystemOut.logprofileName. To view
it, use the log viewer in the WebSphere Application Server administration console.
Your Version 8.3 log configuration settings will not carry over. You can modify the Version 8.4.2 log
configuration settings (such as tracing level or file location) from the system administration client.
DB2 Version 9 for Linux, UNIX, and Windows
Binding bind files after installing fix packs
After a fix pack is installed, you must bind the database utilities (IMPORT, EXPORT, REORG, the Command
Line Processor) and the DB2® CLI bind files. Different subsets of bind files need to be bound for DB2 Database
for Linux®, UNIX®, and Windows® and host or iSeries™ database servers.
Ensure that you have the necessary authority to perform the BIND command.
Note: The Runtime Client cannot be used to bind the database utilities and DB2 CLI bind files. Perform the
BIND commands from a DB2 Client (or other DB2 database product) that is running on the same operating
system and the same DB2 version and fix pack level as the Runtime Client.
To bind the bind files:
1.
If you installed the fix pack on DB2 database products that have existing databases, perform the
following commands once for each database:
2.
3.
4.
5.
6.
db2 terminate
db2 CONNECT TO dbname
db2 BIND path\db2schema.bnd BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE
db2 BIND path\@db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
db2 BIND path\@db2cli.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
db2 terminate
where dbname represents the name of a database to which the files should be bound, and where path
is the full path name of the directory where the bind files are located, such as INSTHOME\sqllib\bnd
where INSTHOME represents the home directory of the DB2 instance. db2ubind.lst and db2cli.lst
contain lists of required bind files used by DB2 database products. Packages that are already bound
will return an SQL0719N error. This is expected.
7.
Optional: If you installed the fix pack on DB2 database products that have existing databases, rebind
the packages by running the REBIND or db2rbind command.
After you install a fix pack, some packages are marked as invalid. Packages marked as invalid are
implicitly rebound the first time an application uses them. To eliminate this overhead and to ensure that
the rebind is successful, manually rebind all packages. For example, issue the db2rbind command:
db2rbind dbname -l logfile all
where dbname represents the name of a database whose packages are to be revalidated, and where
logfile is the name of the file to be used for recording errors during the package revalidation procedure.
Page 59 of 60
8.
If you installed the fix pack on DB2 database products that have existing spatial-enabled databases,
perform the following commands once for each database:
9. db2 terminate
10. db2 CONNECT TO dbname
11. db2 BIND path\BND\@db2gse.lst
db2 terminate
where dbname represents the name of a database to which the files should be bound, and where path
is the full path name of the directory where the bind files are located, such as INSTHOME\sqllib\bnd
where INSTHOME represents the home directory of the DB2 instance. db2gse.lst contains the names
of the bind files for the stored procedures that DB2 Spatial Extender provides.
12. If you installed the fix pack on DB2 database products that have existing federated databases, you
must perform the following commands once for each database:
13.
14.
15.
16.
db2 terminate
db2 CONNECT TO dbname
db2 BIND path\db2dsproc.bnd BLOCKING ALL GRANT PUBLIC
db2 BIND path\db2dsproc.bnd BLOCKING ALL GRANT PUBLIC
db2 terminate
where dbname represents the name of the federated database, and path represents the full path name
of the directory where the bind files are located, such as INSTHOME\sqllib\bnd where INSTHOME
represents the home directory of the DB2 instance.
17. If you connect to DB2 databases on host or iSeries servers, perform the following actions:
o For DB2 databases on z/OS® or OS/390®:
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
db2 terminate
db2 CONNECT TO dbname
db2 BIND path\@ddcsmvs.lst BLOCKING ALL SQLERROR CONTINUE GRANT
PUBLIC ACTION ADD
db2 terminate
For DB2 databases on VM:
db2 terminate
db2 CONNECT TO dbname
db2 BIND path\@ddcsvm.lst BLOCKING ALL SQLERROR CONTINUE GRANT
PUBLIC ACTION ADD
db2 terminate
For DB2 databases on VSE:
db2 terminate
db2 CONNECT TO dbname
db2 BIND path\@ddcsvse.lst BLOCKING ALL SQLERROR CONTINUE GRANT
PUBLIC ACTION ADD
db2 terminate
For DB2 databases on iSeries:
db2 terminate
db2 CONNECT TO dbname
db2 BIND path\@ddcs400.lst BLOCKING ALL SQLERROR CONTINUE GRANT
PUBLIC ACTION ADD
db2 terminate
18. where dbname represents the name of a host or iSeries database to which the files should be bound,
and where path is the full path name of the directory where the bind files are located, such as
INSTHOME\sqllib\bnd where INSTHOME represents the home directory of the DB2 instance.
19. If you connect to databases that are running on different operating systems (Linux, UNIX or Windows)
or at different DB2 versions or service levels, bind the database utilities and DB2 CLI bind files against
those databases.
Page 60 of 60
Note:
o
The actions required are the same irrespective of whether you connect to a database on
another DB2 database system or in another DB2 copy on the same machine.
o If you have installed the fix pack in multiple locations, perform the actions once from each
unique combination of operating system and DB2 version or service level.
Perform the following actions:
db2 terminate
db2 CONNECT TO dbname
db2 BIND path\@db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
db2 BIND path\@db2cli.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
db2 terminate
where dbname represents the name of a database to which the files should be bound, and where path
is the full path name of the directory where the bind files are located, such as INSTHOME\sqllib\bnd
where INSTHOME represents the home directory of the instance where you are issuing the
commands. db2ubind.lst and db2cli.lst contain lists of required bind files used by DB2 database
products. Packages that are already bound will return an SQL0719N error. This is expected.
Related concepts
Binding applications and utilities (DB2 Connect)
Types of clients - DB2 Runtime Client and DB2 Client
Related reference
DB2 CLI bind files and package names
Host databases
Task topic
( Feedback )
Last updated 2008-05-09
http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.uprun.doc/doc/t0024970.htm