Join us on 28-30 May 2013 in Veldhoven – The Netherlands for a new DB2 Symposium featuring 6 top notch presenters who offer you 9 one-day z/OS seminars on DBA, Programming and System Administration topics. As always you can join us for 3, 2 or just 1 day(s), depending on your needs and budget. One-day seminars and flexible registrations make the DB2 Symposium unique in the world!

http://www.db2-symposium.com/events/veldhoven-2013/

For more information see http://ruban.de/sources-events-links/, section “User Groups”, or click on http://ruban.de/sources-events-links/events/ to list alle DB2 events.

Call For Presentations:
You can submit your abstracts by clicking here.

IDUG DB2 Tech Conference in Berlin Wrap Up Article:
The Conference was a great success attracting attendees who came together to hear about the latest in DB2 and network with their peers. Read the wrap up article here.

Online registration is now open for IDUG DB2 Tech Conference in Barcelona, Spain, October 13-18, 2013!

If you have any questions, please contact IDUG Headquarters.

VIEW FULL DETAILS

The International DB2 Users Group is accepting presentation abstracts for the IDUG DB2 Tech Conference in Barcelona, Spain, October 13-18 2013. This is your opportunity to share your DB2 experience and expertise with an audience of your peers who rely on, or are considering incorporating DB2 in their shop. If your presentation abstract is selected to be delivered at the conference, you will receive one complimentary conference registration the DB2 Conference in Barcelona, Spain.

VIEW FULL DETAILS

For more information see http://ruban.de/sources-events-links/, section “User Groups”, or click on http://ruban.de/sources-events-links/events/ to list alle DB2 events.

Themen: Die GSE DB2 LUW Working Group Tagung in Heidelberg, DB2 Troubleshooting – db2stop hangs, Monitoring archivierter Log Files, automatisierte Datenbank-Reorganisation mit DB2 für LUW 10.1, Chats mit dem Labor, Schulungen / Tagungen / Informationsveranstaltung u.v.m.

Hier geht’s zum IBM DB2 Newsletter Archiv!

See Product Lifecycle for DB2 and IMS Tools for more details.

For products that are not listed in the Product Lifecycle matrix below or for additional IBM Software product lifecycle information that is licensed under the International Program License Agreement (IPLA), see IBM Software Support Lifecycle.

This script …

• locates all DB2 instances using profiles.reg (DB2 9.1) or global.reg (9.7 or later)
• executes commands passed as arguments

#!/bin/ksh
################################################################################
# xmpDB2All.sh - DB2 Command an allen DB2 Instanzen eines Systems ausführen
# ------------------------------------------------------------------------------
# Parameter: db2cmd         	- DB2 Command (je Instanz)
#            regfile         	- Pfad zu DB2 Instance Registry (optional)
#
# Calls ...: xmpLog.pl          - Logs events
#
# Comment  : Die Instanzen eines DB2 Systems sind unter Unix im Pfad /var/db2/vn
#            gespeichert. Mit dem Namen kann dann die /etc/passwd nach Instance
#            Home Directories durchsucht werden. Hier setzt man dann mit dem Cmd
#            db2profile die Umgebung und kann dann beliebige DB2 Commands 
#	         ausführen.  
#	         Dieses Script eignet sich besonders für das Stoppen und Starten
#	         aller Instanzen auf einem System, wobei die Instanzen nicht 
#            bekannt sein müssen.
#
# ------------------------------------------------------------------------------
# Autor      G.Ruban /18.09.00  - erste Version V1.1
#            G.Ruban /20.02.01  - V1.2 Protokollierung per xmpLog.pl Perl Script
#            G.Ruban /10.07.01  - V1.3 Perl Path (whence) in PATH setzen
#            G.Ruban /13.01.03  - V1.4 Output überarbeitet
#            G.Ruban /05.12.06  - V2.0: Some amendments necessary for DB2 V9.1
#            G.Ruban /29.07.11  - V2.1: Some amendments necessary for DB2 V9.7,
#                                       profiles.reg not longer supported,
#                                       function library xmpFunktion.sh removed
################################################################################

#-------------------------------------------------------------------------------
# Init 
#-------------------------------------------------------------------------------
  PROG=`basename $0`
  VER="2.1"

#-------------------------------------------------------------------------------
# Pfad der DBA's Administrationsfunktion, -steuerdaten festlegen 
#-------------------------------------------------------------------------------
# der Defaultwert ist : 
  xmpDbaDir="/opt/xmpdba"
  export xmpDbaDir
  xmpDbaDir="$xmpDbaDir"

#-------------------------------------------------------------------------------
# Perl Library in der Umgebung gefunden? Wenn nicht, setzen!
#-------------------------------------------------------------------------------
  if [ ! "$PERL5LIB" ]; then       	
     PERL5LIB=":/usr/local/bin:$xmpDbaDir/bin"
     export PERL5LIB
  else
     if [ -z `echo $PERL5LIB | grep "[.]*$xmpDbaDir/bin[.]*"` ]; then
        PERL5LIB="$PERL5LIB:/usr/local/bin:$xmpDbaDir/bin"
        export PERL5LIB
     fi    
  fi

#-------------------------------------------------------------------------------
# Determine db2ls command to inquire installed software
#-------------------------------------------------------------------------------
  db2lspath=`which db2ls`
  rc=$?
  if [ $rc -ne 0 ] ; then
     echo ">>> $PROG: DB2 Utility db2ls not found in current path."
	 db2lspath="/usr/local/bin/db2ls"
	 echo ">>> Execution path set to $db2lspath."
  fi

#-------------------------------------------------------------------------------
# Inquire latest installation path of DB2 (provides 1 item)
#-------------------------------------------------------------------------------  
  db2sw=`$db2lspath | grep db2 | awk '{print $1}' | tail -1`
  rc=$?
  if [ $rc -ne 0 ] ; then
     echo "Neither DB2 V9.7 nor V9.1 found, continue searching older versions ..."
	 echo "abends with RC=16"
 	 exit 16	
  fi 
  if [ ! "$db2sw" ]; then
	echo "$0: DB2 command db2ls found but no installed DB2 products found!"
	echo "abends with RC=16"
 	exit 16	
  fi   

#-------------------------------------------------------------------------------
# For archive reasons only: Determination of profiles.reg and global.reg
# < V9.1: /tmp/profiles.reg
# = V9.1: /opt/IBM/db2/V9.1/profiles.reg
# = V9.7: /var/[opt/]db2/global.reg
# regfile=`find /var/db2/ -name 'global.reg' -type f -print;find /var/opt/db2/ -name 'global.reg' -type f -print;find /var/db2/ -name 'profiles.reg' -type f -print;find $db2ip -name 'profiles.reg' -type f -print`
#-------------------------------------------------------------------------------  

#-------------------------------------------------------------------------------
# Inquire all instances from DB2 registry, list instance name and path only
#-------------------------------------------------------------------------------  
  db2greg=$db2sw"/bin/db2greg -dump"
  echo ">>> $db2greg"
  ilist=`$db2greg | awk -F, '/I,DB2/ {print $4":"$5}'`
  echo ">>> $ilist"

#-------------------------------------------------------------------------------
# Info Block ausgeben
#-------------------------------------------------------------------------------
  echo $PROG " - V$VER"
  echo "======================================================="
  echo "Current User ................: "`id`
  echo "Current Date/Time ...........: "`date +%Y-%m-%d-%H.%M.%S`
  echo "System ......................: "`uname -n`
  echo "DB2 Command .................: $1"

#-------------------------------------------------------------------------------
# Argumente Prüfen
#-------------------------------------------------------------------------------
  if [ $# -lt 1 or $1 = ? ] ; then
	echo "Syntax für $0 db2cmd regfile"
	echo "... where db2cmd  = DB2 Command, e.g. db2stop"
	echo "Abend mit RC=4"
 	exit 4
  fi

#-------------------------------------------------------------------------------
# Perl Bin Path in PATH setzen
#-------------------------------------------------------------------------------
  perlpath=`whence perl`
  if [ $? -ne 0 ] ; then
     if [ -x "/usr/local/bin/perl" ]; then
	PATH="$PATH:/usr/local/bin"
     	export PATH
     else
        if [ -x "/usr/bin/perl" ]; then
	   PATH="$PATH:/usr/bin"
     	   export PATH
        else
           echo "$0: Perl Binary not found, possibly cannot execute Perl."
        fi
     fi
  else
     perlpath=`dirname $perlpath`
     PATH="$PATH:$perlpath"
     export PATH
  fi
# echo "PATH=$PATH"

#-------------------------------------------------------------------------------
# Liste der Instanzen aus profiles.reg abarbeiten
#-------------------------------------------------------------------------------
  maxrc=0
  for i in $ilist
  do
	#---------------------------------------------------------------------------
	# split instance name and instance path
	#---------------------------------------------------------------------------
	instname=${i%:*}
	instpath=${i#*:}
	#echo ">>>instname=$instname  instpath=$instpath"

	#---------------------------------------------------------------------------
	# Prüfen, ob db2profile Script vorhanden ist
	#---------------------------------------------------------------------------
	echo "--------------------------------------------------------------------------------"
	if [ -x "$instpath/db2profile" ]; then
		echo "- Instance ..................: $instname"	
		echo "  - Home Directory ..........: $instpath"	
		out=`ksh -c ". $instpath/db2profile; $1; exit"`
		rc=$?
		echo "  - Requested Command - RC ..: $rc"	
		echo "  - Command Output ..........: $out"	
		if [ $rc -gt maxrc ]; then
			maxrc=$rc
		fi
		#---------------------------------------
		# Protokollierung
		#---------------------------------------
		perl ${xmpDbaDir}/bin/xmpLog.pl -a "xmpDB2All.sh" -s "I" -t "RC=$rc CMD=$1"
	else
		echo "- Instance ..................: $instname"	
		echo "  - Home Directory ..........: $instpath"	
		echo "    Warning! IBM-supplied script 'db2profile' not found in DB2 path."
        rc=4
		if [ $rc -gt maxrc ]; then
			maxrc=$rc
		fi
	fi
 done

#-------------------------------------------------------------------------------
# *** ENDE ***
#-------------------------------------------------------------------------------
  if [ $maxrc -ne 0 ]; then
	WarningMsg "$0 finished. (RC=$maxrc)"
  else
	echo "$0 finished. (RC=$maxrc)"
  fi
  perl ${xmpDbaDir}/bin/xmpLog.pl -a "xmpDB2All.sh" -s "I" -t "MAXRC=$maxrc" 

exit $maxrc

(Some comments are in german language. If you need assistence, please contact!)

This script may helps administrators to …

• first stop all application services
• then stop all DB2 instances
• to do their maintenance, e.g. full system backups, hardware or software maintenance
• use it in rc2.d to start/stop DB2, so help starting/stopping a server

######################################################################
# DB2CJTrace-Start.sh
######################################################################
clear
echo "Start DB2 CLI+JDBC Trace ..........."
echo "- enter path to trace file: (e.g. /db2inst1/db2/db2diag/$DB2INSTANCE)"
read tfp
datestr=`date +%Y-%m-%d-%H.%M.%S`
CLIFile=$tfp/CLI-Trace-$datestr.txt
JDBCFile=$tfp/JDBC-Trace-$datestr.txt
echo "* CLI Trace File : $CLIFile"
echo "* JDBC Trace File: $JDBCFile"
#
db2 UPDATE CLI CFG FOR SECTION COMMON USING TracePathName NULL
db2 UPDATE CLI CFG FOR SECTION COMMON USING TraceFileName $CLIFile
db2 UPDATE CLI CFG FOR SECTION COMMON USING TraceComm 1
db2 UPDATE CLI CFG FOR SECTION COMMON USING TraceFlush 1
db2 UPDATE CLI CFG FOR SECTION COMMON USING TraceTimeStamp 3
db2 UPDATE CLI CFG FOR SECTION COMMON USING TraceFlushOnError 1
db2 UPDATE CLI CFG FOR SECTION COMMON USING Trace 1
#
db2 UPDATE CLI CFG FOR SECTION COMMON USING JDBCTracePathName NULL
db2 UPDATE CLI CFG FOR SECTION COMMON USING JDBCTraceFileName $JDBCFile
db2 UPDATE CLI CFG FOR SECTION COMMON USING JDBCTraceFlush 1
db2 UPDATE CLI CFG FOR SECTION COMMON USING JDBCTrace 1
echo "DB2 CLI+JDBC Trace activated:"
db2 get cli cfg

######################################################################
# DB2CJTrace-Stop.sh
######################################################################
clear
echo "Stop DB2 CLI+JDBC Trace ..........."
db2 UPDATE CLI CFG FOR SECTION COMMON USING Trace 0
db2 UPDATE CLI CFG FOR SECTION COMMON USING JDBCTrace 0
echo "DB2 CLI+JDBC Trace stopped:"
db2 get cli cfg

Starting with DB2 Version 9.1, the license file for DB2 products is shipped separately in a file called the Activation key.

The Activation key part numbers for DB2 products are located in the following technotes:

• DB2 10.1 – Activation part numbers
• DB2 9.8 – Activation part numbers
• DB2 9.7 – Activation part numbers
• DB2 9.5 – Activation part numbers

Start by viewing the IBM Passport Advantage Online customer sign in page:http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm.
Then click on the “Customer Sign In” button and type in your IBM ID and password for your Passport Advantage account.

May 11th, 2011, PDF 557 KB

As of DB2 Version 9.7 Fix Pack 3, DB2 allows you to move from one DB2 database to another database schema with the new RESTORE … TRANSPORT option. SAP customers can use this new DB2 capability to either migrate their system catalog tablespace to a different page size, or to move schemas (and thus entire SAP instances) from one database to another.

Click here.

May 11th 2011, PDF 819KB

SAP products have been released for several versions of the IBM DB2 for Linux, UNIX, and Windows database. For each of these DB2 versions, SAP makes special recommendations for the database manager and the database parameterization as well as for the DB2 registry variables. To automatically check the existing parameterization of a DB2 for LUW database against the SAP recommendations, you can use the new, very easy-to-use parameter check tool.

Click here.

Click here.

No Installation Manager needed!

IBM Data Studio client Linux 32 bit Install – ibm_ds320_lin_im32.zip (1500 MB)
IBM Data Studio client Linux 64 bit Install – ibm_ds320_lin_im64.zip (1500 MB)
IBM Data Studio client Windows Install – ibm_ds320_win.zip (1500 MB)