! # $ %% $ & "

" "

"

! & / " #

$ ')+ ( *,

% # ' *-. ( + &.-, #

")

! ! & ) 2 #$ $ 6 $ ! # $ #3 #$ $ 0 # # #

$+ , 1

% -% # -- % $ -% # 7 % % 2 #2 9% #/ 0 % # #2 #2 % 2 ## # # # %

. / 0 +

0 / % 7 $ %
" G-70 Database Manager

* 4 $ 1 $ $ $ $ $

: % #8 $ $ 6 $ 4 # : 1

For Mac :

http://www.apple.com/downloads/macosx/apple/javaupdate142.html

& 6 :0 #

+ 0 % # 0

Siebel dedicated Web client
Siebel dedicated Web client connects directly to a database server for all data access, and does not store any Siebel data locally. All layers of the Siebel eBusiness Applications architecture, except for the database, reside on the users personal computer.

Siebel handheld client

Mobile devices with a Web browser and Internet service using the Palm operating system. For more information see Siebel Handheld Administration Guide for Palm OS.

Siebel wireless client

This is a wireless-enabled mobile device with a Web browser and Internet service. For more information, see Siebel Wireless Administration Guide and Siebel Sync Guide.
1.1.4 Siebel Web Server Extension (SWSE)
SWSE is a plug-in extension that runs within the Web server that enables communication between Siebel eBusiness Applications Web clients and Siebel Servers. Siebel eBusiness Applications are a family of zero-footprint, Web-based applications that you access through a standard Web browser.
These applications use several server components to service these Web clients: Web server: Client Web browsers connect to Web servers to display Siebel Web client applications. SWSE: A plug-in extension that runs within the Web server. Siebel Web Engine: The SWSE communicates with the Siebel Web Engine within the Siebel Server for access to Siebel eBusiness Applications data and logic. For information on supported hardware, operating system platforms, Web browsers, and Web servers, please refer to Siebel System Requirements and Supported Platforms.
1.1.5 Siebel Enterprise Server
The Siebel Enterprise Server is a logical grouping of the following components: Siebel Gateway Server Resonate Server Siebel Server Siebel Server Manager All the Siebel Servers in the Siebel Enterprise Server support the same group of users accessing a common database server. The Enterprise Server can be configured, managed, and monitored as a single logical group, allowing the Siebel administrator to start, stop, monitor, or set parameters for all Siebel Servers within an enterprise. You can set some Siebel Server parameters at the enterprise level, and these parameters will apply to all Siebel Servers and components operating within that enterprise; other parameters can be adjusted at the server or component level to support fine-tuning. All Siebel Servers that connect to a common database schema must be installed within the same Enterprise Server.
The Siebel Gateway Server serves as the single entry point for accessing Siebel Servers, and provides enhanced scalability, load-balancing, and high availability across the Enterprise Server. The key services that operate within the Gateway Server are the Name Server and the Connection Broker.
Name Server: This feature provides the persistent backing of Siebel Server configuration information, including definitions and assignments of component groups and components; operational parameters, and connectivity information. Any changes to the configuration are written to the Name Server. At start-up, the Siebel Server obtains its configuration information from the Name Server. The Name Server also serves as the dynamic registry for Siebel Server and component availability information. At start-up, a Siebel Server within the Enterprise Server notifies the Name Server of its availability and stores its connectivity informationsuch as network addressesin the Name Servers non-persistent (volatile) store. Enterprise components (such as the Siebel Server Manager) query the Name Server for Siebel Server availability and connectivity information. When a Siebel Server shuts down, this information is cleared from the Name Server. In a Windows environment, the Name Server runs as a Windows service. In a UNIX environment, the Name Server runs as a daemon process. A single Name Server can potentially serve several databases in an environment (such as multiple development and test environments). For purposes of mitigating dependencies and improving recover ability, you should keep the Siebel production environment separate from other Siebel environments (development or test) by using a separate Name Server. Connection Broker: This feature directs client connection requests to the least-laden Siebel Server operating the desired component, thus providing superior scalability and availability. Connection Broker is an optional service of the Gateway Server that uses the Resonate Central Dispatch product to distribute client connection requests across multiple Siebel Servers. Only dedicated Web client connections to the Siebel Application Object Manager, request processor, and request agent components (for Interactive Assignment) are distributed by Resonate Central Dispatch.

DB2: Installing Update U475375_xxxx /FP3sa
IBM provides extensive documentation as part of each DB2 Update. One document lists all APARS included in the update. The Overview of FixPak has detailed information about the update along with installation instructions and post-update actions. Important: After applying the DB2 FP3sa patch for DB2 7.1, do NOT start either the DB2 instance or the Administration server without performing instance updates. Failure to apply the updates will keep the instances from starting. Review the installation steps in Table 4-5. The process would be the same for AIX and Solaris. If only the DB2 client code is installed, there will be no instance update steps.
Table 4-5 Patch update steps
Sequence 9 Userid db2inst1 db2inst1, db2as root root root root root db2inst1 db2inst1, db2as delta, install /opt/IBMdb2/V7.1/instance /opt/IBMdb2/V7.1/instance /opt/IBMdb2/V7.1/instance /opt/IBMdb2/V7.1/instance Directory Action db2stop db2admin stop installallpatch db2ilist db2iupdt dasilist dasiupdt db2start db2admin start
Use the command line to apply the DB2 patch and update all instances. See Example 4-1.
Example 4-1 Applying the DB2 patch
# su - db2inst1 Sun Microsystems Inc. SunOS 5.8 Generic February 2000 $ db2stop SQL1064N DB2STOP processing was successful. $ db2admin stop SQL4407W The DB2 Administration Server was stopped successfully. $ exit
# ls APAR.txt FixpakReadme.txt delta_install siebel_4577_fp32.tar # cd delta* # ls 172037-000 172037-014 172037-028 172037-042 172037-056 172037-001 172037-015 172037-029 172037-043 172037-057 172037-002 172037-016 172037-030 172037-044 172037-058 172037-003 172037-017 172037-031 172037-045 172037-059 172037-004 172037-018 172037-032 172037-046 172037-060 172037-005 172037-019 172037-033 172037-047 172037-061 172037-006 172037-020 172037-034 172037-048 172037-062 172037-007 172037-021 172037-035 172037-049 172037-063 172037-008 172037-022 172037-036 172037-050 172037-064 172037-009 172037-023 172037-037 172037-051 172037-065 172037-010 172037-024 172037-038 172037-052 172037-066 172037-011 172037-025 172037-039 172037-053 172037-067 172037-012 172037-026 172037-040 172037-054 backoutallpatch 172037-013 172037-027 172037-041 172037-055 installallpatch #./installallpatch INFO: Do NOT interrupt while installing patch 172037-000. Installation of <db2adt71> was successful. INFO: Do NOT interrupt while installing patch 172037-001. Installation of <db2adts71> was successful. INFO: Do NOT interrupt while installing patch 172037-002. Installation of <db2cdb71> was successful. INFO: Do NOT interrupt while installing patch 172037-003. ( continues )

This operation will create in the database the tables, views, packages, procedures, and triggers. Also, the database is seeded with initial data. Launch the Database Server Configuration Utility by selecting the following (see Table 5-8): Start -> Programs -> Siebel Enterprise Server 7.0.2 -> Configure DB Server
Table 5-8 Database components installation responses
Installation screen Siebel Enterprise Parameters Siebel Enterprise Parameters Installation and Configuration Parameters Siebel Database Service Options Siebel Database Service Options Siebel Database Service Options Siebel Language Option Siebel Language Option Installation and Configuration Parameters Installation variable Gateway Server Address Enterprise Server Name Siebel Server Directory Siebel Database Directory Siebel Database Operation Siebel User/Role Creation Selection or string entered gw siebel_es C:\sea702\siebsrvr C:\sea702\dbsrvr Install Database Grantusr has been run by DBA to create Siebel user and roles Install Siebel Database IBM DB2 UDB v7.1 SiebSrvr_siebel_es
Select Installation Operation RDBMS Platform ODBC Data Source Name
Installation screen Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters
Installation variable Database User Name Database Password Database Password (confirm) Database Table Owner Database Table Owner Password Database Table Owner Password (confirm) Database Server OS Index Table Space Name 4K Table Space Name 16K Table Space Name 32K Table Space Name
Selection or string entered sadmin sadmin sadmin siebel siebel siebel Windows tbs_idx tbs_4k tbs_16k tbs_32K
This installation creates a number of log files in the sea702\Siebrvr\log subdirectory such as UpgWiz.log. You need to review the logs for any errors. Note: A number of Siebel log files are increments on each run of the installation. For, example the file UpgWiz.log would be renamed to UpgWiz_01.log and a new UpdWiz.log would be created on an additional installation.

Configuring DB Import

This step is done to populate the repository table in the database with application objects. Regardless of the number of business applications you are using, only a single import is required. Launch the Database Server Configuration Utility by selecting the following (see Table 5-9): Start -> Program -> Siebel Enterprise Server 7.0.2 -> Configure DB Server.
Table 5-9 Repository installation responses
Installation screen Siebel Enterprise Parameters Siebel Enterprise Parameters Installation and Configuration Parameters Installation and Configuration Parameters Siebel Database Server Options Import Repository Option Import Repository Parameters Import Repository Parameters Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters Installation variable Gateway Server Address Enterprise Server Name Siebel Server Directory Siebel Database Directory Siebel Database Operation Select Repository Operation Import Selection RDBMS Platform ODBC Data Source Name Database User Name Database Password Database Password (confirm) Database Table Owner Selection or string entered gw siebel_es C:\sea702\siebsrvr C:\sea702\dbsrvr Import/Export Repository Import Repository Import Standard Siebel Repository IBM DB2 UDB v7.1 siebel sadmin sadmin sadmin siebel
Installation screen Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters Installation and Configuration Parameters
Installation variable Database Table Owner Password Database Table Owner Password (confirm) Import Repository Name Repository File Name
Selection or string entered siebel siebel Siebel Repository C:\sea702\dbsrv\common\ mstrep.dat
Tip: When you have finished entering responses, you will be presented with a message asking to start the process. Click OK. A screen will appear that indicates the steps which will be taken. It will have a spinning globe in the upper left corner. You need to click OK again to start the actual process. This installation creates a number of log files in the sea702\Siebrvr\log subdirectory such as UpgWiz.log. You need to review the logs for any errors.

6.2 Operating system considerations
This section focuses on monitoring operating system resources for performance problems. We review the various system resources that should be monitored, the tools that may be used to do so, and provide broad guidelines for achieving good performance. Jobs are scheduled at predefined intervals to collect system performance statistics and transform them into insert statements. The system performance statistics are then inserted into special user-defined tables (non-Siebel tables). These special user-defined tables are ultimately used for trend analysis. They provide a pretty good overall picture of your system resource utilization over a period of time.
6.2.1 System resources and bottlenecks
System resource utilization/bottlenecks can be classified into four types: CPU utilization: A system is considered CPU bound when the total utilization (user + system) is greater than 80%. A good rule of thumb is to keep the average CPU usage the below 80%, so that it has spare capacity to handle short bursts of unpredictable demand While monitoring CPU, short intervals (1 to 3 seconds) of 100% CPU busy can be ignored. The focus should be on the long-term, since average CPU utilization is an issue. Memory and paging: The following thresholds should be monitored: Paging space is considered low when greater than 70% of paging space is active. Paging is considered bound when: Paging volume %busy is greater than 30% of the I/O. Paging logical volume-to-paging volume activity is greater than 40%.
Disk and I/O: The following thresholds should be monitored: A disk is I/O-bound when CPU %iowait is greater than 40%. A disk is I/O-bound when it is regularly more than 45% busy. Process problems: The following process monitoring should be observed: Monitor processes that appear to be getting unusually high amounts of CPU. While monitoring processes, ignore short bursts (1 to 3 seconds) of 100% CPU busy, and focus on the long term average CPU utilization.
6.2.2 Monitoring system resources on AIX
In this section we describe tools for monitoring system resources on AIX.

Tools available in AIX

The following tools are available in AIX to monitor system resources. Performance ToolKit/6000 (also known as PTX or xmperf):
Chapter 6. Performance management
This is an excellent X-Window graphical performance monitoring tool. It can show historical data and is good for trend analysis of all system resources. This is an optional AIX component. Online Monitor (nmon): This is a freely available and useful tool. It provides a snapshot of AIX statistics. It is available to IBM and IBM Business Partners via PartnerInfo and is located at:

This list of tables depends on the functional modules that you purchased from Siebel, and also on your customizations for your Siebel implementation.
6.3.5 Parallelism considerations
The main objective of parallelism is to minimize the I/O wait by spreading the database across multiple disks. This can be achieved by: Using multiple tablespaces for frequently accessed tables and placing them on different devices Distributing large tables on multiple-containers across multiple-disks Using separate tablespaces for indexes and tables Using dedicated tablespace for large and frequently accessed tables. A DB2 registry parameter, DB2_PARALLEL_IO, turns on parallel I/O (when necessary) for tablespaces with even one container. This is under the assumption that the container is on RAID disks and therefore can sustain parallel I/Os. The DB2_PARALLEL_IO registry variable should be set to specify the tablespaces (either all, or a specific one) that have containers on RAID devices. Note: It is important to set this on before the tablespace is created.
If you just want to turn on parallel I/O for tablespaces 1, 2, 5 and 7, then you run the commands:
$ db2set DB2_PARALLEL_IO = 1, 2, 5, 7 $ db2stop $ db2start
If you want to turn on parallel I/O for all the tablespaces, you use the commands:
$ db2set DB2_PARALLEL_IO = * $ db2stop $ db2start
After setting the registry variable, DB2 must be stopped (db2stop), and then restarted (db2start) for the changes to take effect. Important: Note that if RAID disk subsystems are utilized for tablespace containers, then the DB2 registry parameter DB2_STRIPED_CONTAINERS should be set to ON before the table spaces are created, so that the container tag page is actually an extent and not a single page. This is done by the commands:
$ db2set DB2_STRIPED_CONTAINERS = ON $ db2stop $db2start

6.3.6 DB2 log placement

We recommend that you allocate the DB2 log files on physical disks that do not have high I/O activity. For instance, avoid putting the logs on the same disk as the operating system or high volume databases. This will allow for efficient logging activity with a minimum of overhead (such as waiting for I/O). You can track the number of I/Os related to database logging by using a database system monitor. You can change the log path to different disks by using Configure. from the Control Center menu, or by running the following command:
db2 update db cfg for <DB_NAME> using newlogpath <new directory>
Consider having more primary logs than the default setting of 10:
db2 update db cfg for <DB_NAME> using logprimary <new logfile number>
Primary log files are preallocated, while secondary log files are created if primary logs are not sufficient. Therefore, you will reduce the overhead of creating secondary logs during high DB2 activity if you have sufficient primary logs. Notice that the maximum number of logs (primary and secondary) is 128. Since DB2 V7 has increased log file size from 4GB to 32 GB.

Bufferpool hit ratio

A measure of the effectiveness of the bufferpool is the bufferpool hit ratio. The more data found in the bufferpool, the better it is for performance, since this avoids unnecessary I/O operations. The bufferpool hit ratio should be as high as possible. This is determined through an iterative process wherein you increase the number of buffers and measure the buffer pool hit ratio until there is no further improvement in the ratio. You can measure the bufferpool hit ratio (and many other parameters) with the DB2 Performance Monitor (available from the Control Center), or the SNAPSHOT command from the command line:
$ db2 get snapshot for bufferpools on <DB_Name>
This is calculated as follows:
1 (data + index) physical pages read __________________________________ (data + index) logical pages read
The four parameters can be obtained by issuing the db2 get snapshot. command as shown above.

Bufferpool size

DB2 does not use all of its memory just for bufferpools. Bufferpool space is allocated from the same shared memory segment as the lock list, database heap, and utility heap (determined by configuration parameters locklist, dbheap, and util_heap_sz, respectively). Because of this, you should try to get as optimal a size as possible for your bufferpool through the iterative process outlined earlier. If your tables are too big to fit into bufferpools, try at least to put indexes with heavy hit ratios in separate bufferpools. Note: Using multiple bufferpools requires deep db2 skills to optimize the performance.
IBM DB2 Universal Database Administration Guide: Performance Version 7, provides more information on this subject.
If your usage of EIM processing is high, you may consider having separate bufferpools for EIM tables. You will limit the impact of EIM processing on online users by flushing the bufferpools of EIM processes. Note: There is a compromise here: EIM is not always running and then when its not running the memory allocated to EIM is wasted.
Shared memory considerations on UNIX
On a UNIX-based system, the database shared memory (database global memory) that can be allocated is constrained due to addressing schemes in which shared memory segments start at specific addresses. The database shared memory is memory that are allocated during the first connect to the database.

$ $ > $ db2 update monitor switches using statement on db2 "create event monitor statemon for statements write to file '/siebeldump/db2dump' manualstart" set event monitor statemon state 1
Once this is done, you need to run your siebel applications from the Siebel client. Note you usually have enough data for analysis after running for 2 to 3 minutes.
$ set event monitor statemon state 0 $ db2evmon -db siebel -evm statemon > statemon_read $ db2 drop event monitor statemon
You can also use the graphical tools in Event Monitor and Event Analyzer available in the Control Center for the same purpose.
You can identify the poorly performing SQL statement from the file statemon_read.

6.5.3 Analyzing the SQL

After you identify the poorly performing SQL statements, the following approach may be used to test and optimize the SQL statements: Create the Explain table by executing EXPLAIN.DDL in the sqllib\misc directory (you only need to do this once for your database).

$ db2 -tvf explain.dll

The Explain statement is useful when you want to gather Explain information for a dynamic SQL statement. It can be invoked either from the command line, the control center, or from an application program.
$ db2 explain all with snapshot for Your SQL statement
This command populates a number of Explain tables including the snapshot columns of the Explain_statement table. You can use the Visual Explain or other command (db2exfmt, db2expln, or dynexpln). The results file will include the SQL you entered and the optimized SQL suggested by DB2, for example:
$ db2exfmt -d [DB_NAME] -o [Output fil]
6.5.4 The Index Advisor utility
The Index Advisor utility can be used in cases when poorly performing SQL statement has been identified. Use Smart Guide to determine the appropriate indexes required to improve the performance of the SQL statement
6.6 Capacity planning considerations
Capacity planning is the ability to predict and estimate the growth of system resources such that you can put in place some planning and budgeting to cater for future growth. (In this context, we mean resource requirements in the next two to five years.) Factors that affect growth are: Implementation of new applications into the production environment Rolling out the application in phases to different departments Rolling out new features in phases to the user community Unexpected growth of tables Changes in user expectation and uses for the applications Many other possibilities

db2 list tablespaces show detail
Increase the number of ODBC statement handles. DB2 UDB can quickly run out of ODBC statement handles, depending on the number of business objects your enterprise uses. Because it is difficult to know how many business objects your users actually use, you should increase this number automatically each time you install or upgrade the DB2 UDB client, or when rebinding database utilities. We recommend that you increase the number of CLI packages to six by rebinding the CLI packages, using the special DB2 CLIPKG bind option.
Upgrading the DB2 UDB instance
After upgrading DB2 UDB, upgrade the DB2 UDB instance. To upgrade the instance run the following command on the database server to upgrade to the current version of your RDBMS software:

db2updv7 -d DB_NAME

For more detailed information about tablespaces and bufferpools, please refer the DB2 manuals and Siebel Upgrade guide for Microsoft Windows.
Preparing the Siebel Database
Prepare the Siebel Database as follows: Determine tablespace page size requirements. Create DB2 temporary tablespaces. Increase 4K and 16K tablespaces and bufferpools. Create 16-K and 32-K tablespaces and bufferpools. For the purpose of creating tablespaces and bufferpools, use the scripts provided in Appendix C, Database setup scripts on Windows on page 225.
Updating the file system directory
In previous releases, the file system had a flat structure with one directory. The Release 7.0 file system contains subdirectories. During the upgrade of the production environment, Siebel Anywhere looks for certain files in the file system subdirectories, but these files only exist in the root file system directory. Therefore, you need to create the appropriate subdirectories in your previous installation directory structure, and then copy the required files from the root file system directory to the new subdirectories.
Here is how to make the file attachments accessible by Siebel eBusiness Applications: In the existing file system structure, create an \att subdirectory if it does not already exist; for example, \\ siebfile\att, where siebfile is your root file system directory. Copy all files located under the \\ siebfile directory to the \\ siebfile\att directory so that all file attachments will be accessible by Siebel eBusiness Applications. Verify that files have copied correctly to the \\ siebfile\att directory. After this has been verified, clean up the file system.

ConnectString = siebel.TCPIP.NONE.none://192.168.27.188:2320/siebel/SalesPalmObjMgr/ EnableExtServiceOnly = TRUE [/salesce] ConnectString = siebel.TCPIP.NONE.none://192.168.27.188:2320/siebel/SalesCEObjMgr/ EnableExtServiceOnly = TRUE
Impact of Central Dispatch on the eapps.cfg file The section for [/eservice] from the eapps.cfg file is repeated below.
If Central Dispatch is not used for load balancing (does not apply to our case), then connection strings within the eapps.cfg file are modified to show the location of the gateway server [192.168.27.151] and the Siebel server name [ibm152].
[/eservice] AnonUserName = sadmin AnonPassword = sadmin ConnectString = siebel.TCPIP.NONE.none://192.168.27.151:2320/siebel/eServiceObjMgr/ibm152 StartCommand = SWECmd=GotoView&SWEView=Home+Page+View+(eService)
Where 192.168.27.151 represents the gateway server and ibm152 represents the single Siebel Application Server.

B.2 SWSE log file

The log file, eapps.cfg, generated during the installation of the extension is listed here. The file is located in the log directory of the SWSE installation directory:
00002011 2002-01-23 15:00:10 0000-00-00 00:00:00 -001 001f siebel c:\sea703\SWEApp\log\ss020123.log 7.0.3 [14010] LANG_INDEPENDENT GenericLog GenericLog 0 2002-01-23 15:00:10 #Software: Siebel Web Engine (SWE) ISAPI extension #Version: 7.0.3 #Date: 2002-01-23 15:00:10 GenericLog GenericLog 0 2002-01-23 15:00:10 [2052] INFO Successfully initialized extension state (22 applications). GenericLog GenericLog 0 2002-01-23 15:00:10 [1700] INFO Initialized application "/eservice/" (URI "/eservice/"). GenericLog GenericLog 0 2002-01-23 15:00:10 [SWSE] Anon pool has 0 of 0 sessions available GenericLog GenericLog 0 2002-01-23 15:00:10 [SWSE] Starting new anon session 2052: [SWSE]

1700: [SWSE]

[1700] DETAILS
GenericLog GenericLog 0 2002-01-23 15:00:10 [1700] DETAILS [SWSE] User : sadmin Attempting to open a session.
GenericLog GenericLog 0 2002-01-23 15:00:11 [1700] DETAILS 1700: [SWSE] User : sadmin Open Session : siebel.TCPIP.NONE.none://192.168.27.188:2320/siebel/eServiceObjMgr/!2.21c8. 143f.386c3ac0 succeeded in 0.7943 seconds. GenericLog GenericLog 0 2002-01-23 15:00:11 [1700] DETAILS [SWSE] New anon session (!2.21c8.143f.386c3ac0) started GenericLog GenericLog 0 2002-01-23 15:00:11 [1700] DETAILS [SWSE] Checked out anon session: !2.21c8.143f.386c3ac0. GenericLog GenericLog 0 2002-01-23 15:00:48 [1700] DETAILS [SWSE] User : sadmin Attempting to open a session. 1700:
GenericLog GenericLog 0 2002-01-23 15:00:49 [1700] DETAILS 1700: [SWSE] User : sadmin Open Session : siebel.TCPIP.NONE.none://192.168.27.188:2320/siebel/eServiceObjMgr/!2.21c8. 1440.386c3ae6 succeeded in 0.3046 seconds. GenericLog GenericLog 0 2002-01-23 15:00:49 [1700] DETAILS [SWSE] Checked in anon session: !2.21c8.143f.386c3ac0 1700:

db2 -tvf set_bufferpools.sql
set_bufferpools.sql script to set the bufferpools
-- This CLP file was created using DB2LOOK Version 6.0 -- Timestamp: Mon Nov 27 10:58:-- Database Name: SIEBEL -- Database Manager Version: DB2/NT Version 6.1.0 -- Database CodepagF: 1252 --# --# Connect to database first --# Use: db2 -tvf CONNECT TO SIEBEL; ------------------------------------- DDL Statements for BUFFERPOOLS ------------------------------------ALTER BUFFERPOOL CREATE BUFFERPOOL CREATE BUFFERPOOL CREATE BUFFERPOOL COMMIT WORK; CONNECT RESET; TERMINATE; "IBMDEFAULTBP" "BUF4K" "BUF16K" "BUF32K" SIZE SIZE SIZE SIZE 6000 ; 6000 PAGESIZE 4096 NOT EXTENDED STORAGE; 1500 PAGESIZE 16384 NOT EXTENDED STORAGE; 1000 PAGESIZE 32768 NOT EXTENDED STORAGE;

E.5 Create DB2 log files

The following create_logs.sql script is used to create a db2 log file folder for migration.
create_logs.sql.sql script to create log file folder
--# --# --# Use db2 -tvf UPDATE UPDATE UPDATE UPDATE DB DB DB DB CFG CFG CFG CFG FOR FOR FOR FOR SIEBEL SIEBEL SIEBEL SIEBEL USING USING USING USING NEWLOGPATH D:\DB2LOGS\ ; MAXAPPLS 3000 ; AVG_APPLS 10 ; MAXFILOP 500 ;
-- Create 32 mg log file UPDATE DB CFG FOR SIEBEL USING LOGFILSIZ 8000 ; UPDATE DB CFG FOR SIEBEL USING LOGPRIMARY 25 ; -- Secondary Logs should be around 100 on a production system. UPDATE DB CFG FOR SIEBEL USING LOGPRIMARY 100 ; UPDATE DB CFG FOR SIEBEL USING SOFTMAX 80 ;

E.6 Redirected restore

The following loaddb_siebel.sql script is used to restore the backup of database of siebel 6.2.1 on windows NT using DB2 6.1 with fixpak 8. This is redirected restore procedure. The value 20011214162920 is the timestamp generated by the system when the backup
is taken. This value may change accordingly on different systems.
loaddb_siebel.sql script for redirected restore before Siebel Repository name is changed
-- without prior restore database siebel user db2admin using db2admin from s:/ taken at 20011214162920 into siebel newlogpath d:/db2logs with 4 buffers buffer 1024 redirect parallelism 4 without rolling forward

\ \ \ \ \ \ \ \

E.7 Tablespace mapping
The following siebel_map.sql script is used to set the tablespace mapping on the db2 database on the production system.
siebel_map.sql script to run DDL statements for bufferpools
-- DDL Statements for TABLESPACES --------------------------------------# Create the DB2 Database ala Dennis set tablespace containers for 2 using (PATH 'D:\DB2DATA\USERSPACE1.db2') ; -- EXTENTSIZE 24 PREFETCHSIZE 48 OVERHEAD 18.70 TRANSFERRATE 1.01 \ -- CATALOG TABLESPACE MANAGED BY SYSTEM USING set tablespace containers for 0 using (PATH 'D:\DB2DATA\catalog.db2') ; -- EXTENTSIZE 8 PREFETCHSIZE 8 OVERHEAD 18.60 TRANSFERRATE 1.00 \ -- TEMPORARY TABLESPACE MANAGED BY SYSTEM USING set tablespace containers for 1 using (PATH 'D:\DB2DATA\temporary.db2') ; -- EXTENTSIZE 32 PREFETCHSIZE 32 OVERHEAD 18.60 TRANSFERRATE 1.00 \ -- WITH "Siebel Database SIEBEL" -- CREATE TEMPORARY TABLESPACE TEMP32K IN NODEGROUP IBMTEMPGROUP PAGESIZE 32768 MANAGED BY SYSTEM set tablespace containers for 3 using (PATH 'D:\DB2DATA\temp32k1.db2') ; -- CREATE TEMPORARY TABLESPACE TEMP16K IN NODEGROUP IBMTEMPGROUP PAGESIZE 16384 MANAGED BY SYSTEM set tablespace containers for 4 using (PATH 'D:\DB2DATA\temp16k1.db2') ; -- CREATE TEMPORARY TABLESPACE TEMP4K IN NODEGROUP IBMTEMPGROUP PAGESIZE 4096 MANAGED BY SYSTEM set tablespace containers for 5 using (PATH 'D:\DB2DATA\temp4k1.db2') ; -- CREATE REGULAR TABLESPACE TBS_4K IN NODEGROUP IBMDEFAULTGROUP PAGESIZE 4096 MANAGED BY DATABASE set tablespace containers for 6 using (FILE 'D:\DB2DATA\tbs_4K_01.dat'512000, -- CREATE REGULAR TABLESPACE TBS_16K IN NODEGROUP IBMDEFAULTGROUP PAGESIZE 16384 MANAGED BY DATABASE set tablespace containers for 7 using (FILE 'D:\DB2DATA\tbs_16k_01.dat'64000, -- CREATE LONG TABLESPACE TBS_4KL IN NODEGROUP IBMDEFAULTGROUP PAGESIZE 4096 MANAGED BY DATABASE set tablespace containers for 8 using (FILE 'D:\DB2DATA\tbs_4kL_01.dat'256000, -- CREATE REGULAR TABLESPACE TBS_IDX IN NODEGROUP IBMDEFAULTGROUP PAGESIZE 4096 MANAGED BY DATABASE set tablespace containers for 9 using (FILE 'D:\DB2INDEX\tbs_idx_01.dat'512000, -- CREATE REGULAR TABLESPACE TBS_32K IN NODEGROUP IBMDEFAULTGROUP PAGESIZE 32768 MANAGED BY DATABASE set tablespace containers for 10 using (FILE 'D:\DB2DATA\tbs_32k_01.db2'24000,

set_ODBC_siebel_7_only.cmd script for setting up ODBC client handles
REM -REM -- Increase the Number of ODBC Client Statement Handles to 6 REM -db2 connect to siebel d: cd "d:\program files\sqllib\bnd" REM -db2 bind @db2cli.lst blocking all grant public clipkg 6 REM -db2 terminate

Appendix F.

Migrating DB2 data from one DB2 platform to another
In this appendix we describe techniques for migrating DB2 data from one DB2 platform to another. In the case of migration from another RDBMS to DB2, we suggest that you use EIM. When you move data between DB2s on different platforms, use the db2move and db2look tools. This is true only for initial migration. For all further updates of Siebel data, use EIM. See Chapter 8, Enterprise Integration Manager (EIM) on page 171 for details about EIM.
F.1 Moving DB2 databases between platforms
We describe how to copy database objects (for example, tables, tablespaces) between DB2 on the same or a different operating system. For this purpose you can use db2move (database movement) and db2look (DB2 statistics and DDL extraction) tools. Procedures described in the following sections are applicable to different versions of DB2 on operating systems where DB2 UDB for UNIX, Windows, and OS/2 are available.
F.1.1 Moving database objects: examples
In this section we describe some examples of moving database objects using DB2 tools.
DB2MOVE EXPORT, DB2MOVE IMPORT
If you only need to copy tables between two DB2s, or if you want to import tables into a new database (the other option is to load), follow the steps described below. This approach is usable if your tables are not already created. Import is generally slower than load, so consider using db2move load, described in the next section. 1. Logon to the platform from which you want to export tables as a user, with the required authorization for export. 2. Use the db2move tool to export all tables and their contents:
db2move <database-alias> export
To export a subset of tables, use the options described in DB2 UDB Command Reference, SC09-2844. You will get the following files generated by EXPORT: tabnnn.ixf The exported PC/IXF file of a specific table that is needed for creation of tables. db2move.lst The list of all files can be used as input to the db2move IMPORT or LOAD action. tabnnn.msg files The export message file of the corresponding table. export.out The summarized result of the export action.
tabnnnc.yyy The exported LOB files of a specific table when your tables contain LOBs. system.msg The message file containing system messages when your table contains LOBs. 3. Transfer db2move.lst and all tabnnn.ixf files (also tabnnnc.yyy, if your tables contain LOBs) to your target server by using, for example, FTP. You do not need to copy tabnnn.msg files, because they include only messages produced by export. 4. Logon to the target operating system as a user, with the required authorization for import. 5. Create a new database:

create db <database-alias>
6. Use db2move to import tables into an existing database:
db2move <database-alias> import
DB2MOVE EXPORT, DB2LOOK, DB2MOVE LOAD
If you need to load the contents of the tables into a database, or if you want to copy objects other than just tables, you have to use db2look and db2move. In order to use the db2move load command, the target tables must already exist. Use this approach if you have a larger amount of data, since load is faster than import. For creating tables and other database objects, use the output created from db2look. 1. Logon as a user, with the required authorization for export. 2. As in the previous example, use db2move to export all tables and their contents:
3. Use db2look to get DDL statements for creation of all required objects:
db2look -d <database-alias> -a -e -l -x -o <outfile-name>
You should have the information about all objects created by all users in the outfile: DDL statement for database objects such as tables, views, automatic summary tables, indexes, triggers, user defined functions, etc. Authorization DDL (GRANT statement, for example) DDL statements for user-defined tablespaces, user-defined bufferpools, and user-defined nodegroups
Appendix F. Migrating DB2 data from one DB2 platform to another
4. Transfer <file name>.sql, db2move.lst, and all tabnnn.ixf files (as well as tabnnnc.yyy, if your tables contain LOBs) to your target operating system by using, for example, FTP. Be careful to upload the <file name>.sql file in text mode, not binary mode. You do not need to copy tabnnn.msg files, because they include only messages produced by export. 5. Logon onto the target operating system as a user, with the required authorization for load. 6. Create a new database:
7. Edit <outfile-name>.sql and correct the CONNECT TO <database name> statement to match your new database name. 8. Run the <outfile-name>.sql file containing DDL to create all database objects. The file is created by db2look (see step 3):
db2 -tvf <outfile-name>.sql
9. Use db2move to load tables into an existing database: