Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
It corrects a number of bugs that may lead to the transaction log UFS filling
up:
IT07968 IN SPECIFIC TIMING CONDITIONS, DB2READLOG API CALLS (USED E.G BYCDC)
MIGHT RESULT IN LOGS
BEING LEFT IN ACTIVE LOG PATH.
IT08728 DB2 MAY LEAK FILE HANDLES WHEN USING HADR, OR READLOG/QREP/CDC (OR
ANY LOG READER).
IT10707 WITH MULTIPLE DB2READLOG API CALLERS (HADR, CDC, ETC), LOG FILESMAY
NOT BE RENAMED RESULTING
IN PRIMARY LOG PATH TO FILL UP
Lines starting with '#' are comments and should not be executed.
Downloaded DB2 LUW 10.5 SAP OEM License (Note 816773) 67837800102000003237
DB2_LUW_10.5_FP7SAP_AIX_64bit_51050644_1.zip
DB2_LUW_10.5_FP7SAP_RDBMS_Client_51050647.zip
db6_update_client.SAR
db6_update_db.SAR
* TE NOTE: Be sure to unzip the SAP zip file on AIX, not Windows - Done one time.
TE NOTE: (Note 1837312 was reviewed before the start of the project)
Before you start the database upgrade, make sure that you read SAP Note
1837312. This SAP Note contains the most
recent information about the database upgrade, as well as corrections to this
document. Make sure that you always
have the most recent version of this SAP Note.
For a list of known errors and available fixes in DB2 Version 10.5, see also
SAP Note 1837312.
NOTE: DB2 10.5 is not supported for SAP system releases lower than SAP NetWeaver
7.0.
If you have an older SAP release, you must upgrade your SAP system to SAP
NetWeaver 7.0 or higher
before you can use DB2 10.5.
References:</xmp>
<p style="margin-left :2em;font-family:courier;"><pre>
n <a href="/DB2\DB6UpgrGuide10_5_upd.pdf" target="_blank">SAP DB2 10.5 Upgrade
Guide</a> DB2 10.5 SAP Upgrade Guide
<a href="./DB2 10.5 Standard Parameter Settings.htm">DB2 10.5 Standard Parameter
Settings</a> DB2 10.5 Standard Parameter Settings
U <a href="/sap_notes/DB2_0000101809.pdf" target="_blank">SAP Note 101809</a>
DB6: Supported Fix Packs DB2 for Linux, UNIX and Windows
<a href="https://websmp230.sap-ag.de/sap/support/notes/101809"
target="_blank">SAP Note 101809 (live)</a> DB6: Supported Fix Packs DB2 for Linux,
UNIX and Windows
n <a href="/sap_notes/DB2_0001837312.pdf" target="_blank">SAP Note 1837312</a>
DB6: Upgrade to Version 10.5 of DB2 for LUW
<a href="https://websmp230.sap-ag.de/sap/support/notes/1837312"
target="_blank">SAP Note 1837312 (live)</a> DB6: Upgrade to Version 10.5 of DB2 for
LUW
n <a href="/sap_notes/DB2_0001871003.pdf" target="_blank">SAP Note 1871003</a>
DB6: Installing Fix Packs for DB2 10.5 (UNIX + Linux)
U <a href="/sap_notes/DB2_0000019466.pdf" target="_blank">SAP Note 19466</a>
Downloading SAP kernel patches
n <a href="/sap_notes/DB2_0001851853.pdf" target="_blank">SAP Note 1851853</a>
Using DB2 10.5 with SAP applications
n <a href="/sap_notes/DB2_0000867976.pdf" target="_blank">SAP Note 867976</a>
Changing JDBC driver on WEB AS Java 6.40/NW 7.0x/7.1x
n <a href="/sap_notes/DB2_0000816773.pdf" target="_blank">SAP Note 816773</a>
DB6: Installing an SAP OEM license
U <a href="/sap_notes/DB2_0001365982.pdf" target="_blank">SAP Note 1365982</a>
DB6: Current db6_update_db/db6_update_client script (V49)
<a href="https://websmp230.sap-ag.de/sap/support/notes/1365982"
target="_blank">SAP Note 1365982 (live)</a> DB6: Current
db6_update_db/db6_update_client script (V49) (was V46 for 10.5.4)
<a href="/sap_notes/DB2_0001819734.pdf" target="_blank">SAP Note 1819734</a>
DB6: Use of BLU Acceleration
<a href="/sap_notes/DB2_0002177857.pdf" target="_blank">SAP Note 2177857</a>
DB6: Defect in DB2 BINSORT might cause misordered index in 9.7 FP10 or 10.5 FP5SAP
The attach SAR files had a newer db6_update_db.jar file - It was merged into the
distribution media.
There was no difference in the scripts.
</pre></p><xmp>
===================================================================================
=============================
TE PREP STEPS
===================================================================================
=============================
[ ] Paperwork
CC# DBs
---------- ----------------------
CC00258017 CS7, CS7-DR
CC00258300 BJX, BHX, HRT
CC00258569 BJS, BJD
CC00258666 HRD, BHD, HRZ, BHZ
CC00259058 HC3, BHQ
CC00259071 BJQ
CC00259956 BHS
CC00259903 HRS
CC00260010 BHC
CC00259903 HRS, BHS, HRC, BJC, HC2, BH2, BJ2
as root
set -a
sid=`df | grep "/db2/db2" | awk '{ print substr($7,9)}'`
echo $sid
( ls -ld /db2/db2${sid}/FixPacks
ls -ld /db2/db2${sid}/FP4
ls -ld /db2/db2${sid}/10.5_FP4SAP
ls -ld /db2/db2${sid}/10.5_FP5
)
rm -r /db2/db2${sid}/FixPacks
rm -r /db2/db2${sid}/FP4
rm -r /db2/db2${sid}/10.5_FP4SAP
rm -r /db2/db2${sid}/10.5_FP5
etc
[ ] If you are upgrading a 10.5.4 system, clean up the old, old directories if they
still exist
# These directories can be removed, assuming we are not reverting the system
back to 10.1
as root
set -a
sid=`df | grep "/db2/db2" | awk '{ print substr($7,9)}'`
echo $sid
ls -ld /db2/db2${sid}/db2_software.old
ls -ld /db2/db2${sid}/sqllib_v101.old
rm -r /db2/db2${sid}/db2_software.old
rm -r /db2/db2${sid}/sqllib_v101.old
TE NOTE: You will need around 3465 MB free on the target server in
/db2/db2${sid} for 10.5 FP7SAP
The new DB2DIR will need 2485 MB in /db2/db2${sid}
The new sqllib will be 885 MB ( the old /db2/db2${sid}/sqllib is
saved in /db2/db2${sid}/sqllib_v101 )
sdf -f
[ ] Copy the 10.5_FP7 Media from CL1 on sap0505/sap0506 ( run on the system to
upgraded as db2xxx )
cd ~/10.5_FP7SAP
dir
drwxr-x--- 2 db2cl1 dbcl1adm 256 Jun 13 2012 DB2_10.5_license
drwxr-xr-x 3 db2cl1 dbcl1adm 4096 Jan 26 04:37
DB2_LUW_10.5_FP7SAP_RDBMS_AIX
drwxr-xr-x 3 db2cl1 dbcl1adm 4096 Feb 04 13:34
DB2_LUW_10.5_FP7SAP_RDBMS_AIX_CLIENT
drwxr-xr-x 2 db2cl1 dbcl1adm 256 Feb 09 09:18 SAR_Files
cd ~/10.5_FP7SAP/DB2_10.5_license
dir
total 24
-rw-r----- 1 db2bjd dbbjdadm 350 Aug 08 2013 README OEM
License.txt
-rw-r----- 1 db2bjd dbbjdadm 915 Aug 08 2013 db2aese_c.lic
-rw-r----- 1 db2bjd dbbjdadm 905 Aug 08 2013 sam32.lic
sdf -f
db2ls
-----------------------------------------------------------------------------------
----------------------------------
/db2/db2bjx/db2_software 10.1.0.4 4
Tue Aug 5 11:44:14 2014 EDT 0
Note: DB2DIR represents the location where the DB2 copy is installed.
DB2DIR=/db2/db2hc3/db2_software # if 10.1.x
or
DB2DIR=/db2/db2cs7/db2_V10.5 # if 10.5.4
TE NOTE: if db2ls shows 10.5.x , do the patch update, NOT THIS UPGRADE !
set -a
sid=`df | grep "/db2/db2" | awk '{ print substr($7,9)}'`
echo $sid
cd /db2/db2${sid}/10.5_FP7SAP/DB2_LUW_10.5_FP7SAP_RDBMS_AIX/AIX_64/ESE/disk1
./db2prereqcheck -v 10.5.0.7
TE NOTE (pgw): /opt will not be used for the install location and can be
ignored
================================================================================
HADR note: Install DB2 Software on both the Primary and the Standby DB servers
The installation of the DB2 10.5 software consists of the following steps that
you must perform in the
specified order:
1. You install the database software on the database server [
2. You update the database client software
Procedure
1. Log on to the database server as user root and make sure that you can open
programs with a
graphical user interface.
dzdo su - root
set -a
TMOUT=0
DISPLAY=163.241.153.108:0 # an example only, your IP address will be
different
xclock # to test that your X display is working
set -a
sid=`df | grep "/db2/db2" | awk '{ print substr($7,9)}'`
echo $sid
cd /db2/db2${sid}/10.5_FP7SAP/DB2_LUW_10.5_FP7SAP_RDBMS_AIX/AIX_64/ESE/disk1
./db2setup
# CAUTION You must make sure that the operating system requirements are met.
5. Choose DB2 Version 10.5 Fix Pack 7 Workgroup, Enterprise and Advanced
Editions [Install New]
NOTE As of DB2 10.5, there is just one install image for the DB2 Workgroup,
Enterprise, and Advanced
Edition. The applied DB2 license decides which edition will actually be
used.
The following steps can appear, but not necessarily in the sequence shown
below. The exact sequence of the installation
steps that follow depends on various factors, for example, your operating
system, already installed DB2 components,
your installation choices, and the DB2 Fix Pack level. Therefore, we cannot
provide a detailed step-by-step procedure
for the DB2 software installation in this document. The following steps
outline important points that you have to consider
when installing DB2 in an SAP environment:
- On the Introduction part of the screen DB2 Setup . DB2 Server Edition,
choose [Next->]
- Software License Agreement
(x) I accept the terms in the license agreement and choose [Next->]
- On the screen Select the installation type, choose
TE NOTE: We ran into an issue with AIX Clustered Nodes running a new
release of the cluster
software.
(x) Custom
[ View Features ]
[x] Server Support
[x] Base server support (required)
[x] Communication support - TCP/IP (required)
[x] Connect support (required)
[ ] DB2 Text Search
[x] DB2 data source support
[x] Guardium Installation Manager Client
[ ] Informix data source support
[x] Integrated Flash Copy Support
[ ] Spatial Extender server support
Uncheck -> [ ] Tivoli SA MP (installed)
IBM Tivoli System Automation for Multiplatforms provides high
availability
and disaster recovery capabilities for AIX, Line, Solaris
SPARC, and Windows.
This component is installed.
###################################################################################
####
CAUTION Do not install DB2 10.5 in the current instance directory of
your DB2 instance
(/db2/db2<dbsid>/sqllib) and below.
###################################################################################
####
[ English (required) ]
- On the Set User Information for the DB2 Administration Server screen,
choose the name of an existing DAS
user (typically dasusr1 or dasusr2), or enter the required information for
a new DAS user.
[x] Create DAS user later # this account is no longer needed and
is removed later
- On the Instance Setup screen, choose Do not create a DB2 instance and then
Next.
- On the Set Up Notifications screen, choose Do not set up your DB2 server to
send notifications at this time.
(x) Do not set up your DB2 server to send notifications at this time
- On the Summary screen, review the installation summary and start the
installation by choosing [Finish].
Product to install: DB2 Server Edition
Installation type: Custom
Selected Components:
Base client support
Java support
SQL procedures
Base server support
Connect support
DB2 data source support
IBM Software Development Kit (SDK) for Java(TM)
DB2 LDAP support
DB2 Instance Setup wizard
Integrated Flash Copy Support
Communication support - TCP/IP
DB2 Update Service
Replication tools
Sample database source
First Steps
Guardium Installation Manager Client
Languages:
English
All Products
TE NOTE: under the Post-install steps you may see a note about TSAMP (we do
not use it)
EXAMPLE LOG
======================================================================
============================================================
DB2 Setup log file started at: Tue Feb 16 18:47:38 2016 EST
============================================================
Selected Components:
Base client support
Java support
SQL procedures
Base server support
Connect support
DB2 data source support
IBM Software Development Kit (SDK) for Java(TM)
DB2 LDAP support
DB2 Instance Setup wizard
Integrated Flash Copy Support
Communication support - TCP/IP
DB2 Update Service
Replication tools
Sample database source
First Steps
Guardium Installation Manager Client
Languages:
English
All Products
Installing: DB2_PRODUCT_MESSAGES_EN
Installing: BASE_CLIENT
Installing: JAVA_RUNTIME_SUPPORT
Installing: DB2_JAVA_HELP_EN
Installing: BASE_DB2_ENGINE_R
Installing: GSK
Installing: JAVA_SUPPORT
Installing: SQL_PROCEDURES
Installing: ICU_SUP
Installing: JAVA_COMMON_FILES
Installing: BASE_DB2_ENGINE
Installing: CONNECT_SUPPORT
Installing: DB2_DATA_SOURCE_SUPPORT
Installing: JDK
Installing: LDAP_EXPLOITATION
Installing: INSTANCE_SETUP_SUPPORT
Installing: ACS
Installing: COMMUNICATION_SUPPORT_TCPIP
Installing: DB2_UPDATE_SERVICE
Installing: DATABASE_PARTITIONING_SUPPORT
Installing: EDB
Installing: REPL_CLIENT
Installing: DB2_SAMPLE_DATABASE
Installing: ITLM
Installing: CLPPLUS
Installing: FIRST_STEPS
Installing: ESE_PRODUCT_SIGNATURE
Installing: GUARDIUM_INST_MNGR_CLIENT
Explanation:
User response:
No action is required.
Installing or updating DB2 HA scripts for IBM Tivoli System Automation for
Multiplatforms (Tivoli SA MP) :.......Success
Executing control tasks :.......Success
Updating global registry :.......Success
Starting DB2 Fault Monitor :.......Success
Updating the db2ls and db2greg link :.......Success
Registering DB2 licenses :.......Success
Setting default global profile registry variables :.......Success
Initializing instance list :.......Success
Registering DB2 Update Service :.......Success
Updating global profile registry :.......Success
[ ] check db2ls
sap0530:db2ct1> db2ls
-----------------------------------------------------------------------------------
----------------------------------
/db2/db2bjs/db2_software 10.1.0.2 2
Tue Feb 26 15:36:37 2013 EST 0
/db2/db2bjs/db2_V10.5.7 10.5.0.7 7 1
Tue Feb 16 19:02:10 2016 EST 0
sap0596:db2cs7> echo $DB2DIR # Note the old version is still being used by
the DB
/db2/db2bjs/db2_software
[ ] Remove world writable from /db2 files which have it enabled [ dzdo su - root ]
We use AUTOSTORAGE for all tablespaces, double check that AUTO=1 for
SYSCATSPACE ***
***
ID TAB_SPACE PG_SZ CONTAIN EXTSZ PRFTH PFEFF TYPE TSCTYPE FSC
TOT_MB USED_MB USED AUTO TABLES INDXS OBJCTS
0 SYSCATSPACE 16384 16 2 -1 32 DMS ANY NO
5408.00 5383.71 99.00 1 143 372 515
SAP systems use SMS-based temporary tablespaces. Make sure that the temporary
tablespaces can grow to
at least twice the size of SYSCATSPACE.
Our temp tablespace use the standard sapdata UFSs. They should be OK.
NOTE: As a rough guideline, make sure that your log space has at least the
size of the SYSCATSPACE. If you
followed the parameter recommendations for the database parameters
LOGFILESIZ, LOGPRIMARY and LOGSECOND
(for more information, see SAP Note 1692571), the upgrade should run
without problems.
###################################################################################
#######################
TE NOTE: SAP suggests 60 for LOGPRIMARY 0 for LOGSECOND, we use
LOGPRIMARY of 40, LOGSECOND of 40 for PR2
We disable NUM_LOG_SPAN (usually set to 20) later in this
procedure.
###################################################################################
#######################
[ ] cleanup old work around ( At this time, all systems should have be updated.
This is just a doublecheck. )
###################################################################################
########
# make sure DB2PATH is set and that db2set works
###################################################################################
########
as db2xxx
if it is not set
tail -n 5 ~/.dbenv.sh
db2level | grep "10.5"
exit
ls -al /global.reg
rm /global.reg
ls -al /global.reg
exit
db2set
env | grep DB2PATH
SAP NOTE: 1851853 - DB6: Using DB2 10.5 with SAP Applications
check rowcomp
db2set DB2_ROWCOMPMODE_DEFAULT=ADAPTIVE
db_size -SC
db_size -SC
[ ] Check for LOADs in progress - Cannot run the update if any loads are active
TE README NOTE:
TE NOTE: on the Standby DBs make sure the SAP UFSs are mounted
1. Log in as <sapsid>adm
R3trans -x
R3trans loads the DB2 library and connects to the database. A log file
trans.log
is created in the current directory.
######################################################################
TE NOTE: We do not use the DB2 Runtime Client on non-database servers.
######################################################################
3. Another verification
TE NOTE: If not 7.20 or higher please have Basis update the SAP Kernel to at
least 7.20
***********************************************************************************
*********************************************
***********************************************************************************
*********************************************
PREP STEPS END HERE
***********************************************************************************
*********************************************
***********************************************************************************
*********************************************
Rechecks:
If you install the media in advance of the upgrade, double check the
requirements are still being met.
set -a
sid=`df | grep "/db2/db2" | awk '{ print substr($7,9)}'`
echo $sid
cd /db2/db2${sid}/10.5_FP7SAP/DB2_LUW_10.5_FP7SAP_RDBMS_AIX/AIX_64/ESE/disk1
./db2prereqcheck -v 10.5.0.7
[ ] Check for LOADs in progress - Cannot run the update if any loads are active
db2ls
-----------------------------------------------------------------------------------
----------------------------------
/db2/db2bjs/db2_software 10.1.0.2 2
Tue Feb 26 15:36:37 2013 EST 0
/db2/db2bjs/db2_V10.5.7 10.5.0.7 7 1
Tue Feb 16 19:02:10 2016 EST 0
###################################################################################
###########################################
START OF THE DB2 DOWNTIME
###################################################################################
###########################################
( as db2${sid} )
mkdir ~/cfg_backup_10.5.7
cd ~/cfg_backup_10.5.7
env | tee env_before_upg.txt
db2set -all | tee reg_before_upg.txt
db2 get dbm cfg | tee dbm_before_upg.txt
db2 get db cfg for $DB2DBDFT | tee db_before_upg.txt
db_space | tee db_space_before_upg.txt
After the database upgrade, you back up the database configuration again and
compare the files that contain the configuration before
and after the upgrade.
check DB2_ATS_ENABLE
shutdown_DB2
db2start
db2 stop hadr on database $DB2DBDFT
DB20000I The STOP HADR ON DATABASE command completed successfully.
shutdown_DB2
db2start
db2 stop hadr on database $DB2DBDFT
db2stop
TE NOTE: Do not roll forward until after the Primary DB has been upgraded
db2start
time db2 rollforward database $DB2DBDFT complete
DB20000I The ROLLFORWARD command completed successfully
# Both
startup_DB2
check_hadr
[ ] Disable DB2COMM
[ ] Disable NUM_LOG_SPAN
db2 connect
db2 update db cfg for $DB2DBDFT using NUM_LOG_SPAN 0 immediate
db2 get db cfg for $DB2DBDFT show detail | grep NUM_LOG_SPAN
[ ] Stop the admin instance (if it exists). As a DAS user, enter the following
command:
su - dasadm
source /db2/db2${sid}/sqllib/db2cshrc
/db2/db2${sid}/db2_software/das/bin/db2admin stop
change
fmc:2:respawn:/db2/db2ds1/db2_software/bin/db2fmcd #DB2 Fault Monitor
Coordinator
to
:fmc:1:respawn:/db2/db2ds1/db2_software/bin/db2fmcd #DB2 Fault Monitor
Coordinator
TE NOTE: If you are updating the Primary or Standby of an HADR pair, you will
need to take them out of DR mode before proceding.
The HADR will have to be recreated when the upgrades on the Primary
and the Standby have completed.
shutdown_DB2
as root
kill any leftover sap and db2 processes (everything except the topas_nmon)
You must shut down all DB2 instances when you apply a Fix Pack.
In a non-pureScale environment, a single DB2 copy can drive many DB2 instances.
Therefore, you must stop all SAP systems and DB2 instances that are affected
before you
update a DB2 copy. To display a list of all DB2 instances that belong to a DB2
copy,
execute the command "db2ilist" as user db2<dbsid>.
shutdown_DB2
db2start # needed for CommVault backup, do not startup if taking
CommVault snaps
* start the offline backup in CommVault ( retain 90 days W04-SPECIAL-90day )
[ ] Shutdown DB2
shutdown_DB2
###################################################################################
###########
[ ] Record Upgrade Time ( excluding the backups )
###################################################################################
###########
BHZ Fri Feb 19 16:16:38 EST 2016 Fri Feb 19 16:55:53 EST 2016 00:39:15
HRZ Fri Feb 19 17:09:34 EST 2016 Fri Feb 19 17:55:32 EST 2016 00:45:58
HRD Fri Feb 19 18:07:21 EST 2016 Fri Feb 19 19:02:51 EST 2016 00:55:30
BHD Fri Feb 19 18:07:21 EST 2016 Fri Feb 19 18:43:26 EST 2016 00:36:05
BHQ Thu Feb 25 16:13:27 EST 2016 Thu Feb 25 17:42:00 EST 2016 01:28:33
HC3 Thu Feb 25 19:23:46 EST 2016 Thu Feb 25 20:43:05 EST 2016 01:19:14
BHS Wed Mar 16 15:39:45 EDT 2016 Wed Mar 16 16:20:29 EDT 2016 00:40:44
BHC Thu Mar 17 15:54:20 EDT 2016 Thu Mar 17 16:38:09 EDT 2016 00:43:49
HRS Wed Mar 16 15:55:59 EDT 2016 Wed Mar 16 16:50:39 EDT 2016 00:54:40
HRC Thu Mar 17 15:55:38 EDT 2016 Thu Mar 17 17:04:29 EDT 2016 01:08:51
BJC Thu Mar 17 15:23:11 EDT 2016 Thu Mar 17 16:14:53 EDT 2016 00:51:42
###################################################################################
###########################################
SAP Client Updates
###################################################################################
###########################################
HADR Note: The SAP Client Updates must be run on both the Primary and Standby DB
servers.
Upgrade the Standby only after Production has finished.
You may still see ctmadm and root topas_nmon tasks. These are not a problem.
as root
If SAP is still running, have Basis shut it down (includeing the SAP OS
collector.
# Shut down the SAP system and the SAP database instance as follows:
#
# i) As user "<sapsid>adm", enter the following command:
# stopsap
# ii) Stop the SAP OS Collector with the following command:
# saposcol -k
2. Log in as <sapsid>adm
R3trans -x
R3trans loads the DB2 library and connects to the database. A log file
trans.log
is created in the current directory.
######################################################################
TE NOTE: We do not use the DB2 Runtime Client on non-database servers.
######################################################################
NOTE: If not 7.20 or higher please have Basis update the SAP Kernel to at
least 7.20
NOTE Even if R3trans loads the DB2 CLI driver libraries, an additional DB2
Runtime Client might be installed. By default, the
SAP kernel uses the DB2 CLI driver on all application servers of SAP
Release 7.0 and higher that have a local DB2 Runtime
Client installed, as well as access to a DB2 CLI driver in directory
/usr/sap/<SAPSID>/SYS/global/db6. In this case, the
DB2 Runtime Client is not used, and we recommend that you uninstall it to
avoid duplicate maintenance.
# $ ksh
# $ whence db2ilist
# /db2/db2hrc/sqllib/bin/db2ilist <- part of DB2 install
For each SAP application server that uses a DB2 Runtime Client and that is
not running on the database server, you must update
the DB2 Runtime Client. That is, you install the DB2 Runtime Client software
first and upgrade the DB2 Runtime Client instance
as part of the database and instance upgrade.
######################################################################
TE NOTE: We do not use the DB2 Runtime Client on non-database servers.
######################################################################
[ ] Updating the DB2 CLI Driver
TE NOTE: Not needed on DR using NFS to serve the /sapmnt/SID and /usr/sap/SID
UFSs
PGW NOTE: CS7-DR has local mount points - did the client upgrade
For SAP systems that use the DB2 CLI driver, you only have to update the DB2
CLI driver once in the shared directory
/usr/sap/<SAPSID>/SYS/global/db6.
Each application server can access this directory. Therefore, after the DB2 CLI
driver has been updated, it can be used
by all application servers.
For more information and the latest version of the db6_update_client scripts,
see SAP Note 1365982.
We checked note 1365982: the scripts are the same as included with FP4SAP media
we downloaded
Result: The new version of the DB2 CLI driver is automatically used after the
next SAP system restart
and no further action is required.
as xxxadm
=========
# MAKE BACKUPS - note for Java only systems db6_blidriver will not exist
ksh
COLUMNS=132
cp -rp /usr/sap/${DB2DBDFT}/SYS/global/db6/AIX_64/db6_clidriver \
/usr/sap/$
{DB2DBDFT}/SYS/global/db6/AIX_64/db6_clidriver.pre10.5.7
cp -rp /usr/sap/${DB2DBDFT}/SYS/global/db6/jdbc \
/usr/sap/${DB2DBDFT}/SYS/global/db6/jdbc.pre10.5.7
ls -al /usr/sap/${DB2DBDFT}/SYS/global/db6/AIX_64/db6_clidriver
ls -al /usr/sap/$
{DB2DBDFT}/SYS/global/db6/AIX_64/db6_clidriver.pre10.5.7
ls -al /usr/sap/${DB2DBDFT}/SYS/global/db6/jdbc
ls -al /usr/sap/${DB2DBDFT}/SYS/global/db6/jdbc.pre10.5.7
exit # back to csh
cp -r /db2/db2$
{sid}/10.5_FP7SAP/DB2_LUW_10.5_FP7SAP_RDBMS_AIX_CLIENT /tmp
# continue xxxadm
cd /tmp/DB2_LUW_10.5_FP7SAP_RDBMS_AIX_CLIENT/CLIENT
./db6_update_client.sh -h
If you see wrong calling method for script please change directory
to the mounted SAP DVD and call the script from there
cp -p LABEL.ASC ../
*********************************************************
* this is db6_update_client.sh script version 0010 *
*********************************************************
./db6_update_client.sh -u
*********************************************************
* this is db6_update_client.sh script version 0008 *
*********************************************************
#***************************************************************************#
# updating existing CLI drivers
#***************************************************************************#
directory /usr/sap/CS7/SYS/global/db6/AIX_64/db6_clidriver does
exist, deleting...
creating directory /usr/sap/CS7/SYS/global/db6/AIX_64/db6_clidriver
copying new CLI driver to
/usr/sap/CS7/SYS/global/db6/AIX_64/db6_clidriver
#***************************************************************************#
# copying JDBC driver
#***************************************************************************#
directory /usr/sap/CS7/SYS/global/db6/jdbc does exist, deleting
creating directory /usr/sap/CS7/SYS/global/db6/jdbc
copying new JDBC driver to /usr/sap/CS7/SYS/global/db6/jdbc
#***************************************************************************#
# create db2cli.ini
#***************************************************************************#
/usr/sap/CS7/SYS/global/db6/db2cli.ini does exist, nothing to do...
skipping creation of /usr/sap/CS7/SYS/global/db6/db2cli.ini
#***************************************************************************#
OR
The script "db6_update_client.sh" updates the DB2 CLI driver and the JDBC
driver for Java in the directory global/db6 for all available operating
systems.
The installation is now complete and you can restart your SAP system.
total 8
drwxr-xr-x 2 bhzadm sapsys 256 Jan 11 10:23 adm
drwxr-xr-x 2 bhzadm sapsys 256 Jan 11 10:23 bin
drwxr-xr-x 2 bhzadm sapsys 4096 Jan 11 10:23 bnd
drwxr-xr-x 2 bhzadm sapsys 256 Jan 11 10:23 cfg
drwxr-xr-x 2 bhzadm sapsys 256 Jan 11 10:23 cfgcache
drwxr-xr-x 4 bhzadm sapsys 256 Jan 11 10:23 conv
drwxr-xr-x 2 bhzadm sapsys 256 Jan 11 10:23 db2dump
drwxr-xr-x 3 bhzadm sapsys 256 Jan 11 10:23 lib
drwxr-xr-x 3 bhzadm sapsys 256 Jan 11 10:23 license
drwxr-xr-x 3 bhzadm sapsys 256 Jan 11 10:23 msg
dir /usr/sap/${DB2DBDFT}/SYS/global/db6/jdbc # for JAVA or ABAP/JAVE
systems
total 13048
-r-xr-xr-x 1 bjsadm sapsys 3235129 Feb 16 19:32 db2jcc.jar
-r-xr-xr-x 1 bjsadm sapsys 3433725 Feb 16 19:32
db2jcc4.jar
-r-xr-xr-x 1 bjsadm sapsys 1411 Feb 16 19:32
db2jcc_license_cu.jar
-rw-r--r-- 1 bjsadm sapsys 45 Feb 16 19:32
jdbcdriver.lst
as root
cd
rm -r /tmp/DB2_LUW_10.5_FP7SAP_RDBMS_AIX_CLIENT
***********************************************************************************
**************************
Issue with BPD:
***********************************************************************************
**************************
NOTE: For SAP kernel releases higher than the ones listed in this table, you
do not need a specific SAP kernel patch.
We recommend that you install the latest available SAP kernel patch
before you start the DB2 upgrade.
cd
R3trans -x -w 10.5.7.log
grep patchlevel 10.5.7.log | grep dbdb6slib.o
4 ETW000 [ dev trc,00000] Version of
'/usr/sap/BJS/SYS/exe/uc/rs6000_64/dbdb6slib.o' is "721.02", patchlevel (0.137)
##########################################################
backup the DBSL
##########################################################
Some systems use dbdb6slib.o (7.20, 7.21) others use dbdb6slib.so with
(7.41)
mv dbdb6slib.o dbdb6slib.o.PRE_10.5.7
mv patches.mf patches.mf.PRE_10.5.7
ls -al *.PRE_10.5.7
-rwxr-xr-x 1 bjsadm sapsys 5399911 Dec 04 2013
dbdb6slib.o.PRE_10.5.7
-rwxr-xr-x 1 bjsadm sapsys 329 Dec 04 2013
patches.mf.PRE_10.5.7
###################################################################################
#######################################
IF USING SAP 7.20
###################################################################################
#######################################
ls -al /tech/bas/kernels/DBSL_AIX_DB2_720_UNICODE_patch623
total 27340
drwxr-xr-x 2 60058 sapsys 96 Nov 19 15:40 .
drwxrwxr-x 131 9306 sapsys 9216 Nov 20 16:54 ..
-rw------- 1 60058 sapsys 4931 Sep 26 10:47
SIGNATURE.SMF
-rwxrwxr-x 1 60058 sapsys 13982562 Sep 23 13:45
dbdb6slib.o
-rwxrwxr-x 1 60058 sapsys 282 Sep 23 17:41 patches.mf
cp -p
/tech/bas/kernels/DBSL_AIX_DB2_720_UNICODE_patch623/dbdb6slib.o .
cp -p
/tech/bas/kernels/DBSL_AIX_DB2_720_UNICODE_patch623/patches.mf .
ls -al dbdb6slib.o*
-rwxrwxr-x 1 cs7adm sapsys 13982562 Sep 23 2014
dbdb6slib.o
-rwxrwxr-x 1 cs7adm sapsys 13982562 Sep 23 2014
dbdb6slib.o.PRE10.5.7
-rwxr-xr-x 1 cs7adm sapsys 8351412 Jan 27 08:50
dbdb6slib.o.SAVE
-rwxr-x--- 1 cs7adm sapsys 6874919 Jan 27 08:50
dbdb6slib.o_orig
ls -al patches*.mf*
-rwxrwxr-x 1 cs7adm sapsys 282 Sep 23 2014 patches.mf
-rwxrwxr-x 1 cs7adm sapsys 282 Sep 23 2014
patches.mf.PRE10.5.7
-rwxr-xr-x 1 cs7adm sapsys 282 Jan 27 08:50
patches.mf.SAVE
cd
R3trans -x
This is R3trans version 6.24 (release 721 - 10.06.14 - 20:14:07).
unicode enabled version
R3trans finished
###################################################################################
#######################################
IF USING SAP 7.21
###################################################################################
#######################################
ls -al /tech/bas/kernels/DBSL_AIX_DB2_721_UNICODE_patch325
total 6449
drwxr-xr-x 2 60058 sapsys 6 Nov 20 2014 .
drwxrwxr-x 137 9306 sapsys 138 Jun 16 06:24 ..
-rw------- 1 60058 sapsys 5014 Sep 15 2014
SIGNATURE.SMF
-rwxrwxr-x 1 60058 sapsys 7528420 Sep 12 2014 dbdb6slib.o
-rwxrwxr-x 1 60058 sapsys 313 Sep 13 2014 patches.mf
-rwxrwxr-x 1 60058 sapsys 332 Sep 13 2014
patchesdb.mf
cp -p /tech/bas/kernels/DBSL_AIX_DB2_721_UNICODE_patch325/dbdb6slib.o .
cp -p /tech/bas/kernels/DBSL_AIX_DB2_721_UNICODE_patch325/patches.mf .
cp -p /tech/bas/kernels/DBSL_AIX_DB2_721_UNICODE_patch325/patchesdb.mf .
dir dbdb6slib.*
-rwxrwxr-x 1 bjsadm sapsys 7528420 Sep 12 2014
dbdb6slib.o
-rwxr-xr-x 1 bjsadm sapsys 5399911 Dec 04 2013
dbdb6slib.o.PRE10.5.7
dir patches*
-rwxrwxr-x 1 bjsadm sapsys 313 Sep 13 2014
patches.mf
-rwxr-xr-x 1 bjsadm sapsys 329 Dec 04 2013
patches.mf.PRE10.5.7
-rwxrwxr-x 1 bjsadm sapsys 332 Sep 13 2014
patchesdb.mf
R3trans -x
This is R3trans version 6.24 (release 721 - 10.06.14 - 20:14:07).
unicode enabled version
R3trans finished (0012).
R3trans -d
trans.log
4 ETW000 [ dev trc,00000] function DbSlExpFuns loaded from
library /usr/sap/CS2/SYS/exe/run/dbdb6slib.o
4 ETW000
18 0.003475
4 ETW000 [ dev trc,00000] Version of
'/usr/sap/CS2/SYS/exe/run/dbdb6slib.o' is "721.02", patchlevel (0.325)
4 ETW000
714 0.004189
###################################################################################
###########################################
Upgrade the DB2 Instance and the Database
###################################################################################
###########################################
HADR Note: On the Standby, update the Instance, but not the DB. It will be copied
from the Primary DB.
shutdown_DB2
set -a
sid=`df | grep "/db2/db2" | awk '{ print substr($7,9)}'`
echo $sid
cd /db2/db2${sid}/db2_V10.5.7/instance/
Task #1 start
Description: Setting default global profile registry variables
Estimated time 1 second(s)
Task #1 end
Task #2 start
Description: Initializing instance list
Estimated time 5 second(s)
Task #2 end
Task #3 start
Description: Configuring DB2 instances
Estimated time 300 second(s)
Task #3 end
Task #4 start
Description: Updating global profile registry
Estimated time 3 second(s)
Task #4 end
su - db2${sid}
echo $DB2DIR
/db2/db2bjs/db2_V10.5.7
NOTE To check if all requirements for an upgrade are met, db2iupgrade calls
the program db2ckupgrade in the background.
If db2ckupgrade finds problems, the DB2 instance is not upgraded. In
this case, correct the problem and start
db2iupgrade again.
Since the DB2 system catalog has been changed with DB2 Version 10.5, you have
to upgrade the database.
1. If you are logged into the db2xxx account, log out and then log back in.
/db2/db2bjs/db2_V10.5.7
db2start
SQL8007W There are "90" day(s) left in the evaluation period for the
product <- will update the license later
"DB2 Advanced Enterprise Server Edition". For evaluation license terms and
The time it takes to upgrade the database depends on the size of the system
catalog. For a standard SAP NetWeaver 7.0
ABAP only, the upgrade approximately takes 10 to 30 minutes. If the upgrade
completes successfully, the following message
is displayed:
NOTE If the database upgrade fails, the error message SQL1704N is displayed
describing the cause of the failure. For a
list of possible solutions for each reason code, enter
One of the most common causes of upgrade failure is that there is not
enough log file space available. In this case,
the following error is returned:
NOTE If the database upgrade succeeds but additional actions are required,
the warning SQL1499W is displayed describing
the cause of the failure. In this case, see the DB2 administration
log /db2/<DBSID>/db2dump/db2<dbsid>.nfy for
more information.
startup_DB2
sap0520:db2cs2> db_sum
AGENTS:
DB2 Start Time Registerd Idle Waiting Register Top
Waiting Top From Pool Created Empty Pool Coord Top Max Overflows Stolen
-------------------------- ---------- ---------- ---------- ------------
----------- ---------- ------------------ ---------- ------------- ----------
2016-02-16-19.52.25.081194 13 0 0 13
0 28 15 13 0 0
-----------------------------------------------------------------------------------
----------------------------
Max number of coordinating agents (MAX_COORDAGENTS) = AUTOMATIC(200)
AUTOMATIC(200)
Max number of client connections (MAX_CONNECTIONS) =
AUTOMATIC(MAX_COORDAGENTS) AUTOMATIC(MAX_COORDAGENTS)
-----------------------------------------------------------------------------------
----------------------------------
/db2/db2bjs/db2_software 10.1.0.2 2
Tue Feb 26 15:36:37 2013 EST 0
/db2/db2bjs/db2_V10.5.7 10.5.0.7 7 1
Tue Feb 16 19:02:10 2016 EST 0
db2level
uses "64" bits and DB2 code release "SQL10057" with level identifier
"0608010E".
Informational tokens are "DB2 v10.5.0.7", "special_35127", "IP23949_35127",
and
Fix Pack "7".
Product is installed at "/db2/db2bjs/db2_V10.5.7".
db2ls
-----------------------------------------------------------------------------------
----------------------------------
/db2/db2bjs/db2_software 10.1.0.2 2
Tue Feb 26 15:36:37 2013 EST 0
/db2/db2bjs/db2_V10.5.7 10.5.0.7 7 1
Tue Feb 16 19:02:10 2016 EST 0
db2 connect to ${DB2DBDFT} # HADR Note: This will not work on the
Standby
[ ] remove the one off patches for 10.1 FP2 (if they still exist)
db2set DB2_TCG_DEFAULT_OPTIONS=
db2set DB2_CORRELATED_PREDICATES=
update $CONFIG/db_specific_${SID}.sh
db2 connect
db2 update db cfg for $DB2DBDFT using NUM_LOG_SPAN 20 immediate
db2 get db cfg for $DB2DBDFT show detail | grep NUM_LOG_SPAN
Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 20
20
To verify the success of the database upgrade, you can test if a database
activation succeeds by performing
the following steps:
time db2val
DBI1379I The db2val command is running. This can take several minutes.
The DB2 copy validation tool verifies basic functions of a DB2 software
installation and generates a report
with its findings.
db2ls
-----------------------------------------------------------------------------------
----------------------------------
/db2/db2bjs/db2_software 10.1.0.2 2
Tue Feb 26 15:36:37 2013 EST 0
/db2/db2bjs/db2_V10.5.7 10.5.0.7 7 1
Tue Feb 16 19:02:10 2016 EST 0
as db2xxx
db2ls
Install Path Level Fix Pack Special Install Number
Install Date Installer UID
-----------------------------------------------------------------------------------
----------------------------------
/db2/db2bjs/db2_V10.5.7 10.5.0.7 7 1
Tue Feb 16 19:02:10 2016 EST 0
To reverse if needed:
mv /db2/db2${sid}/db2_software.old /db2/db2${sid}/db2_software
or
mv /db2/db2cs2/db2_V10.5.old /db2/db2cs2/db2_V10.5
db2ls
-----------------------------------------------------------------------------------
----------------------------------
/db2/db2bjs/db2_software 10.1.0.2 2
Tue Feb 26 15:36:37 2013 EST 0
/db2/db2bjs/db2_V10.5.7 10.5.0.7 7 1
Tue Feb 16 19:02:10 2016 EST 0
as db2xxx
cd
mv sqllib_v101 sqllib_v101.old
The db6_update_db script checks various settings and enables some features, for
example, the automatic resize function
for the tablespaces. The script also reorganizes the tables of the DB2 system
catalog, updates the statistics for
these tables, and rebinds all invalid packages.
The following scripts are available on the RDBMS DVD and as attachments to SAP
Note 1365982:
These steps have been run once and not needed again:
RECOMMENDATION We recommend that you use the latest version of these scripts
that are available in SAP Note 1365982.
Procedure
1. Download the latest version of the scripts from SAP Note 1365982.
2. To run the scripts, follow the instructions in SAP Note 1365982.
To determine the version of the db6_update_db script, call the script with
the option -V or -version.
cd ~/10.5_FP7SAP/DB2_LUW_10.5_FP7SAP_RDBMS_AIX/AIX_64
./db6_update_db.sh -v
******************************************
db6_update_db tool version 52 <- verify the version
******************************************
The db6_update_db script checks various settings and enables some features,
for example, the automatic resize
function for the tablespaces. The script also reorganizes the tables of the
DB2 system catalog, updates the
statistics for these tables, and rebinds all invalid packages.
One time - download the attachments from note 1365982 version 62 Validity
13.01.2016 (DD.MM.YYYY)
./db6_update_db.sh -d $DB2DBDFT
**************************************************
* db6_update_db tool version 46
**************************************************
db6_update_db was called in a post database update/upgrade scenario !!
Parameter DBSID used : CS2
This is a Fixpak Update!!
**************************************************
The detected DB2 release is: 100504
This system is a SAP Netweaver System !!
No SAP Roles exist on this database
**************************************************
The SQL0204N errors can be ignored. The proper bind command should
include the "sqlerror continue"
clause which will suppress the error messages from being displayed.
cd /db2/db2${sid}/10.5_FP7SAP/DB2_LUW_10.5_FP7SAP_RDBMS_AIX/AIX_64
time db2 -z db6_update_db_out.log -tvf db6_update_db_out.sql
===========================================================================
sap0565:db2bjs> db_locks -b
10 locks found
10 blocks found
db2set DB2_FMP_COMM_HEAPSZ=0
db2set DB2_FMP_COMM_HEAPSZ=
db2set | grep DB2_FMP_COMM_HEAPSZ
es db6_update_db_out.log
The SQL0204N errors can be ignored. The proper bind command should include
the "sqlerror continue"
clause which will suppress the error messages from being displayed.
Check the entries in the file db6_update_db_out.log for error messages and
and correct any
errors that may have occurred (error messages in db2diaglog after the
release upgrade) that are
described in more detail in Note 1263266. Also refer to Note 1269713 for
the error analysis of
the log file db6_update_db_out.log. This note describes SQL errors that may
occur during the
rebind of the packages, but that you can ignore.
After the database upgrade, you have to install the DB2 license.
Procedure
- If you are an SAP OEM customer, see SAP Note 816773 to install the license.
NOTE Multi-partition databases: Install the license on each database host
- If you purchased DB2 directly from IBM, contact your IBM sales
representative
cd ~/10.5_FP7SAP/DB2_10.5_license
sap0520:db2cs2> dir
-rw-r----- 1 db2cs2 dbcs2adm 350 Nov 20 19:57 README OEM
License.txt
-rw-r----- 1 db2cs2 dbcs2adm 915 Nov 20 19:57 db2aese_c.lic
-rw-r----- 1 db2cs2 dbcs2adm 905 Nov 20 19:57 sam32.lic
db2licm -l
db2licm -a db2aese_c.lic
db2licm -l
db2greg -dump
I,DB2,10.5.0.7,db2bjs,/db2/db2bjs/sqllib,,1,0,/db2/db2bjs/db2_V10.5.7,,
V,DB2GPRF,DB2INSTDEF,db2bjs,/db2/db2bjs/db2_V10.5.7,
S,DB2,10.5.0.7,/db2/db2bjs/db2_V10.5.7,-,,7,0,,1455670345,1
check DB2_ATS_ENABLE
db2set DB2_ATS_ENABLE=
check DB2_ATS_ENABLE
db2set DB2COMM=
check db2comm
Checking the Registry ...
[i] DB2COMM=TCPIP [DB2_WORKLOAD]
Checking the DBM Config ...
Checking the DB Config ...
db2diag -A
shutdown_DB2
startup_DB2
switch_logfile
If you created a backup of the DB2 server configuration before the upgrade, it
is useful to create another backup of
the configuration after the upgrade.
(as db2<sid>)
cd /db2/db2${sid}/cfg_backup_10.5.7
env | tee env_after_upg.txt
db2set -all | tee reg_after_upg.txt
db2 get dbm cfg | tee dbm_after_upg.txt
db2 get db cfg for $DB2DBDFT | tee db_after_upg.txt
db_space | tee db_space_after_upg.txt
Note especially:
< Current effective arch level (CUR_EFF_ARCH_LVL) = V:10 R:5 M:0 F:5
I:0 SB:0
< Current effective code level (CUR_EFF_CODE_LVL) = V:10 R:5 M:0 F:5
I:0 SB:34127
---
> Current effective arch level (CUR_EFF_ARCH_LVL) = V:10 R:5 M:0 F:7
I:0 SB:0
> Current effective code level (CUR_EFF_CODE_LVL) = V:10 R:5 M:0 F:7
I:0 SB:35127
crontab /var/spool/cron/crontabs/db2${sid}
cd
R3trans -d
db2 connect
db6level
10.05.0007
###################################################################################
###########################################
END OF THE ACTUAL UPGRADE
###################################################################################
###########################################
[ ] Performing a Backup
You will need to have the OPS window removed from the CV Client. (It does not
need to be put back on)
CAUTION We strongly recommend that you perform a full offline backup of the
upgraded database.
HADR Note: We will need an offline or online backup in production for the
establishment of the DR system.
When the backup completes:
Mark all tapes it used as FULL
View Media
Properties for each tape
***********************************************************************************
*
[ ] If this is an HADR node, you must recreate the standby after upgrading it's
software
***********************************************************************************
*
CV-GUI
Look at the backup history for ${SID}HOT in SAP${SID}
right click browse and restore
[ Browse and Restore Options ] [ View Content ]
Select [x] CS7 in the left pane
[Recovery All Selected ...]
General : (x) Database Subset
Destination Computer: SAP${SID}-AIX-DR
Restore Arguments
(x) Offline Restore
Select the Available Image
Go back to General:
(x) Entire Database
[ Advanced ]
[ Rollforward ]
[ ] Disable Roll-Forward
[x] Leave in Roll-forward Pending State
[ Log Files ]
[ ] Restore Log Files (uncheck)
~/db2sa/scripts/DR_rsync_log_archive2.sh
on Standby
==========
Member ID = 0
Rollforward status = DB pending <--
Should be in pending mode
Next log file to be read = S0007866.LOG
Log files processed = -
Last committed transaction = 2015-01-29-01.28.33.000000 UTC
shutdown_DB2
# Kill the restore if it is in rollforward mode
db2start
db2 start hadr on database $DB2DBDFT as standby
Make sure all the secondary archives LOGs are copied from the primary to the
standby
$ . /home/dasadm/das/dasprofile
Replace <DASHOME> with the home directory of the DAS user, for example,
/home/dasusr1.
$DB2DIR/das/bin/db2admin stop
set -a
sid=`df | grep "/db2/db2" | awk '{ print substr($7,9)}'`
echo $sid
/db2/db2${sid}/db2_V10.5.7/instance/dasdrop
Explanation:
log_config
cd $CONFIG
check_config.sh | grep -i match
[ ] The following SAP tools for DB2 require a specific patch level to be able to
work with DB2 10.5 ( as xxxadm )
Tool Min Patch Level We install with 7.20 721 SAP install uses 720 721
741
-------- ----====------- -------------------- -------------------- ---- ---
---
dmdb6bkp 16 16 16 15 16
16
brdb6brt 27 32 29 25 32
32
For more information about how to download and apply the latest kernel patch for
these tools, see SAP Note 19466.
# TE NOTE: Should be good, just double check , if not, the SAP KERNEL has not
been updated yet
For more information about how to download and apply the latest kernel patch for
these tools, see SAP Note 19466.
###############################
check on the DBSL release level
###############################
###################################################################################
#######################################
IF USING SAP 7.20
###################################################################################
#######################################
dir /tech/bas/kernels/DMDB6BKP_720_AIX_DB2_patch16
total 3124
-rw------- 1 60058 sapsys 4928 Jun 07 2012 SIGNATURE.SMF
-rwxrwxr-x 1 60058 sapsys 1592836 Jun 06 2012 dmdb6bkp
-rwxrwxr-x 1 60058 sapsys 282 Jun 06 2012 patches.mf
as ( xxxadm )
cp -p /usr/sap/${DB2DBDFT}/SYS/exe/run/dmdb6bkp /usr/sap/$
{DB2DBDFT}/SYS/exe/run/dmdb6bkp.SAVE
cp -p /tech/bas/kernels/DMDB6BKP_720_AIX_DB2_patch16/dmdb6bkp /usr/sap/$
{DB2DBDFT}/SYS/exe/run/dmdb6bkp
dmdb6bkp -V | grep "patch level"
patch level 16
dir /tech/bas/kernels/BRDB6BRT_720_AIX_DB2_patch32
total 2370
-rw------- 1 60058 sapsys 4928 Apr 02 2014 SIGNATURE.SMF
-rwxrwxr-x 1 60058 sapsys 1206375 Mar 29 2014 brdb6brt
-rwxrwxr-x 1 60058 sapsys 282 Apr 01 2014 patches.mf
as ( xxxadm )
cp -p /usr/sap/${DB2DBDFT}/SYS/exe/run/brdb6brt /usr/sap/$
{DB2DBDFT}/SYS/exe/run/brdb6brt.SAVE
cp -p /tech/bas/kernels/BRDB6BRT_720_AIX_DB2_patch32/brdb6brt /usr/sap/$
{DB2DBDFT}/SYS/exe/run/brdb6brt
brdb6brt -V | grep "patch level"
patch level 32
cd
R3trans -d
db2 connect
db6level
TE NOTE: DO NOT DO THIS STEP AT THIS TIME, NEEDED TO REVERT UPGRADE IF NEEDED
# These directories can be removed, assuming we are not reverting the system
back to 10.1
#
# /db2/db2${sid}/db2_software.old
# /db2/db2${sid}/sqllib_v101.old
[ ] Remove world writable from /db2 files and dirs which have it enabled [ dzdo su
- root ]
as root
ls -ld /usr/local/bin/db2*
set -a
sid=`df | grep "/db2/db2" | awk '{ print substr($7,9)}'`
echo $sid
cd /usr/local/bin
ln -sf /db2/db2${sid}/db2_V10.5.7/bin/db2greg
ln -sf /db2/db2${sid}/db2_V10.5.7/install/db2ls
./db2ls
ls -al /usr/local/bin/db2*
cd ~/db2_V10.5.7/bnd/
db2 connect to $DB2DBDFT
db2 bind db2exfmt.bnd blocking all grant public
Include:
Basis please review the following information for the DB2 10.5 FP7SAP upgrade.
If your database is connected to SAP Solution Manager, you have to update the
data extractors for the upgraded database
using the setup wizard of SAP Solution Manager.
NOTE To monitor DB2 10.5, use SAP Solution Manager 7.1 or higher.
Procedure
1. Log on to your SAP Solution Manager system and call transaction SOLMAN_SETUP.
The screen SAP Solution Manager: Configuration appears in a separate Web
browser.
2. In the navigation frame, choose Managed Systems Configuration.
3. On the Database tab page, choose the upgraded database and the Configure
Database pushbutton.
The setup wizard of the SAP Solution Manager system appears.
4. Choose the Configure Automatically step.
5. Execute the automatic activity Database Extractor Setup.
Result
The setup wizard updates the back end of the DBA Cockpit and reschedules the
data extractors for the SAP Solution
Manager or the Database Performance Warehouse feature.
See SAP Note 1835822 - DB6: Compatibility Patches for IBM DB2 10.5 for LUW
Symptom : The DBA Cockpit creates SQL errors when you connect to IBM DB2 for
Linux, UNIX, and Windows version 10.5
(DB2 10.5 for LUW) or higher.
To be able to use new functionality of DB2 10.5 in the application server ABAP,
you need
adaptions in the area of monitoring (SAP transaction DBACOCKPIT) and in the ABAP
data
dictionary. Make sure that you have implemented the following minimum SAP Basis
support
packages required for the different SAP releases:
Description 1835822 DB6: Compatibility Patches for IBM DB2 10.5 for LUW
[ ] Paperwork
###################################################################################
#############################################
THE END
###################################################################################
#############################################