MAJOR

=================
Configuation

Memory

Logs

LOGPRIMARY 20 # development # 100 for production

LOGSECOND 0
LOGFILSZ 1310720 # in 4KB pages 5GB
LOGBUFSZ
NEWLOGPATH .../origlog ?
MIRRLOGPATH .../mirrlog ?
SOFTMAX ?
BLK_LOG_DSK_FUL YES : cause hang NO: rolls back transaction, DB can crash
MAX_LOG = 0 # percentage of log space 1 transaction can
use, 0 is unlimited
NUM_LOG_SPAN = LOGPRIMARY-2

LOGARCHMETH1=OFF Circular Logging

=disk:.../saparch/archives ? 500 for Dev, 2 TB for Production

Archives

Install logs created

/db2/CL1/log_dir/NODE0000/LOGSTREAM0000

iostat -alDt

Monitoring
O/S
/var/log/syslog.out
adquery user te100204
db_vmstat
iostat
DB2

JFS2 inline log - inline logging 10% of the JFS - 2GB in size

go with it.

business copy
snapshot

commvault snap protect ?

size of dynamic memory components

cache hit rate http://www.dbatodba.com/db2/how-to-do/how-to-calculate-bphr-

pchr-and-cchr
Get status of the monitor switches
db2 get database manager monitor switches
 Turn the buffer monitor monitor on
db2 update dbm cfg using DFT_MON_BUFPOOL ON
After updating these parameters wait for two to three hours and proceed to get
the snapshot
of the required databases in that particular instances using the following
command
db2 get snapshot for database on <db name>
After getting snapshot switch off the monitor switches using following command
db2 update dbm cfg using DFT_MON_BUFPOOL Off
There are three hit ratio�s to be calculated from the snapshot of the
databases. Use values of parameters taken in snapshot of database above.
1. Buffer Pool Hit Ratio (BPHR)
2. Package Cache Hit Ratio (PCHR)
3. Catalog Cache Hit Ratio (CCHR)

Backup/Restore
DR
Cloning

C++ Compiler

Nodes
=====================
CL.6 sap.524
MWB mwb001
CS6 sap0559
LC6 sap0558

LRS lrs0101(prod)
lrs0501(ha or d/r)

Issues
===================

Exceed ( Secure Shell )

temp directories
249600.00 38.43 1% 1% /db2/CL1/sapdatatemp1
249600.00 38.43 1% 1% /db2/CL1/sapdatatemp2
249600.00 38.43 1% 1% /db2/CL1/sapdatatemp3
249600.00 38.43 1% 1% /db2/CL1/sapdatatemp4

/db2/{$SID}/sa/logs
/scripts
/bin

Peformance of

db2diag -l error, severe

db2support <output directory> -d <database name> -g -c -s -f
db6_update_db.sh -d <dbsid> -enable_roles
db2set
dscdb6up
db2mtrk - memory tracker

sap0505:db2cl1> db2mtrk -h
Usage: db2mtrk -i | -d | -a | -p [-m | -w] [-v] [-r interval [count]] [-h]

-i Display instance level memory usage

-d Display database level memory usage
-a Display application level memory usage
-p Display agent private memory usage
-m Display maximum usage information
-w Display watermark usage information
-v Display verbose memory usage information
-r Run in repeat mode
interval Amount of seconds to wait between reports
count Number of reports to generate before quitting
-h Display this help screen

/usr/sap/<SAPSID>/SYS/global/dscdb6.conf

DB2 CLP

Note 101809 - DB6: Supported Fix Packs IBM DB2 for Linux,UNIX and Windows

http://service.sap.com/PAM

PR2 is NetWeaver 7.01 (NW EhP1) SP7 with ECC EhP4 SP 8 until August 1

questions
=========

ksh support
Centrify support

Monitor
=========
Memory utilization
tablespaces and/or UFS for sapdata

AUTO_REORG

ISOLATION LEVEL <*****************************************

As of IBM DB2 Version 9.7, you can configure DB2 to use the new currently
committed (CC) semantics for queries with isolation level CS. With currently
committed semantics, readers do not wait for writers to release row locks. Instead,

readers see data that is based on the currently committed version; that is, the
version of the row prior to the start of the write operation. As of DB2 Version
10.1 the use of currently committed semantics is recommended.
To be able to use currently committed semantics, you must have at least SAP
kernel release 6.40 or higher. Read SAP Note 1486779 if you want to use CC with SAP

kernel release 6.40. You cannot use currently committed with SAP kernel releases
lower than 6.40.

dont run AUTORUNSTATS DURING THE MIGRATION

DBSTATC ? taken care of by SAP ?

Solution

Isolation level

Note:
You should enable DB2 AUTO_REORG to automate important table and index maintenance
activities.
Enabling AUTO_REORG requires a policy to be in place. See SAP Note 975352 for more
information.

> AUTO_REVAL = DEFERRED

> CF_DB_MEM_SZ = AUTOMATIC [PSCALE=YES]

> CF_GBP_SZ = AUTOMATIC [PSCALE=YES]
> CF_LOCK_SZ = AUTOMATIC [PSCALE=YES]
> CF_SCA_SZ = AUTOMATIC [PSCALE=YES]
> CF_CATCHUP_TRGT = AUTOMATIC [PSCALE=YES]

> CUR_COMMIT = ON

Note:
See SAP Note 1514016 for more information about isolation level "currently
committed".

LOGPRIMARY 20 # development # 100 for production

LOGSECOND 0
LOGFILSZ 1310720 # in 4KB pages 5GB
LOGBUFSZ
NEWLOGPATH .../origlog ?
MIRRLOGPATH .../mirrlog ?
SOFTMAX ?
BLK_LOG_DSK_FUL YES : cause hang NO: rolls back transaction, DB can crash
MAX_LOG = 0 # percentage of log space 1 transaction can use, 0 is unlimited
NUM_LOG_SPAN = LOGPRIMARY-2

LOGARCHMETH1=OFF Circular Logging

=disk:.../saparch/archives ? 500 for Dev, 2 TB for Production

5TB free

Note 1353421 - DB6: How to disable file system caching for tablespaces

Solution
In order to disable file system buffered I/O for table spaces, implement the
following:
" set the "FILE SYSTEM CACHING = NO" attribute for all table spaces by "ALTER
TABLESPACE <table space name> NO FILE SYSTEM CACHING"
" mount the file systems WITHOUT cio/dio option, if those options are available
on your platform
" restart the database to effect the changes

Note:
Do not mount file systems with cio/dio options, which disables file system buffered
I/Os for all accesses on the file system.

PGW: Note: we will probably need more memory for JFS2 cache for backups

VG_PR2_HOME
VG_PR2_SAPDATA ... distribution of sapdata directories
VG_PR2_ONLINE_LOGS orig
mirr
VG_PR2_ARCHIVE_LOGS

Compression option the conversion is using ?

db_cache
db_io
db_sum
db_space
db_queries
db_locks

check on stats
RUNSTATS0

11 5 drives/TB 5 JFS2 per VG 16384 PPs 64MB each

echo $DISPLAY; /usr/bin/X11/xterm -ls -geometry 132x24 -fn humm -sl 500 -sb -bg
black -fg green -T "orapr2 `/usr/bin/whoami`" -n "sd06mn `/usr/bin/whoami`" %

STATISTICS

BACKUP/RESTORE

DR

CLONE from DR

PRODUCTION BACKUP/RESTORE to ASHBURN

DB_UTILITIES

DB20 setup on MN08DBPROD20

ITC table

archiving
insert,deleting old rows

SAP

db2pd -db dbname -tcbstats