Notes
Notes
Notes
=================
Configuation
Memory
Logs
Archives
/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
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
===================
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
sap0505:db2cl1> db2mtrk -h
Usage: db2mtrk -i | -d | -a | -p [-m | -w] [-v] [-r interval [count]] [-h]
/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
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.
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.
> CUR_COMMIT = ON
Note:
See SAP Note 1514016 for more information about isolation level "currently
committed".
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
db_cache
db_io
db_sum
db_space
db_queries
db_locks
check on stats
RUNSTATS0
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
DB_UTILITIES
archiving
insert,deleting old rows
SAP