From “Try & Buy” to Production Database

One day a project manager will come with a huge list of customer
requirements. He will explain that project is extremely important and we will
not have another chance if we mess this one up. The customer has been working
with a test development on Sun Solaris platform with DB2 version 8.1 “Try &
Buy”. Now he is ready to start with a real production and needs help to choose
the right licensing model and database packaging option.

I will explain in this article what the DBA needs to know regarding licensing,
database packaging models, and the article will be oriented to Sun Solaris
platform.

This article covers:

  • Database
    Versions and FixPack Levels
  • Version
    8.1 Enhancements
  • Version
    8.1 Packaging Models
  • Version
    8.1 Licensing and Licensing Models
  • Licensing
    Procedure – Working Case
  • Conclusion

Database Versions and FixPak
Levels

DB2 version is the main code release and the FixPack is
database code enhancements.

A short overview of the most common database versions used
on Solaris platform, with minimum set of operating system patches:

Database Version

Solaris Platforms

 

2.5.1

2.6

Solaris 7

Solaris 8

Solaris 9

DB2 v.5.2 UDB
Enterprise-Extended Edition (EEE)

Patch 103640 and
101242

Patch 105181


 

 

DB2 v.6.1 UDB and UDB
EEE

Patch 103640 and
101242

Patch 105181

 

DB2 v.7.1 UDB EEE

Patch 105181


DB2 v.8.1 Enterprise
Server Edition (ESE) with Clustering and Partitioning option

DB2 version 8.1 is compatible
with Solaris 7,8 and 9. Existing additional Recommended Patches and Security
Patches:

DB2 Workgroup Server certified
on Solaris versions:

* Solaris 7 (32-bit) "Recommended & Security
Patches" +107226-17 + 107153-01 + 106327-10

* Solaris 8 (32-bit) "Recommended & Security
Patches" +108921-12 + 108940-24+108434-03 and 108528-12

* Solaris 9 (32-bit) None

DB2 Enterprise Server Edition certified on Solaris
versions:

* Solaris 7 (32-bit) "Recommended & Security
Patches" +107226-17 + 107153-01 + 106327-10

* Solaris 7 (64-bit) "Recommended & Security
Patches" +107226-17 + 107153-01 + 106300-11

* Solaris 8 (32-bit) "Recommended & Security
Patches" +108921-12 + 108940-24+108434-03 and 108528-12

* Solaris 8 (64-bit) "Recommended & Security
Patches" +108921-12 + 108940-24+108435-03 and 108528-12

* Solaris 9 (32-bit) None

* Solaris 9 (64-bit) None

The actual DB2 version and license information can be
displayed with the db2licm (License Manager) command:


>> db2licm -l
Product Name = “DB2 Enterprise – Extended Edition”
Product Password = “PASS”
Version Information = “8.1”
Expiry Date = “01.04.2003 (Try & Buy)”
Concurrent Connect User Policy = “Disabled”
Registered Connect User Policy = “Disabled”
Enforcement Policy = “Soft Stop”
Number of processors = “4”
Number of licensed processors = “1”
Annotation = “”
Other information = “”

In the output below, the database is Enterprise Extended
Edition version 8.1, with product password PASS. The license for this database is Try
& Buy and expires on 01.04.2003.

The system has 4 CPUs and only one is registered.

To get detail information about the database level and FixPak,
we use the db2level command:


>> db2level
DB21085I Instance “db2udb1” uses DB2 code release “SQL07025” with level
identifier “03060105” and informational tokens “DB2 v7.1.0.20”, “s020616” and
“U484483”.

The last part of the db2level command output is called “informational
token,
” where we can read the database version (7.1.0.68) and FixPack level
(U484483).

There were many FixPacks for version 7; the following
table is a short overview for the Solaris 32 platform.

Global version

Official FixPack for
SUN

Informational token

Detail version

V710

Fixpack 1

U472077 s000727

7.1.0.1

V710

Fixpack 3

U475377 s010426

7.1.0.41

V720

Fixpack 4

U478687 s010913

7.1.0.51or 7.1.0.50

V720

Fixpack 5

U480362 s011211

7.1.0.55

V720

Fixpack 6

U481409 s020313

7.1.0.60

V720

Fixpack 7

U482564 s020616

7.1.0.65

V720

Fixpack 7

U484483 s020616

7.1.0.68

V720

Fixpack 8

U484613 s021110

7.1.0.72

Marin Komadina
Marin Komadina
Marin was born June 27, 1968 in Zagreb, Croatia. He graduated in 1993 form The Faculty for Electrotechnology and Computer Sciences, University of Zagreb in Croatia. He started his professional career as a System specialist and DBA for the Croatian company Informatika System. His most important project was the development and implementation of the enterprise, distributed point of sales solution, based on the Oracle technology. In 1999, Marin became the company CTO, where he played an active role in company development and technical orientation. After Informatika System, Marin worked as an IT Manager Assistant for the Austrian international retail company "Segro," on location in Graz (Austria) and Zagreb (Croatia). He was responsible for the company's technical infrastructure and operational support. Segro used IBM technology, OS/400 operating system and DB2 database. In 1998, Marin joined the international telecommunication company VIPNet GSM that was a part of greater concern, Mobilkom Austria& Western Wireless Int. USA. After one year, Marin took over the IT System Manager position, where he managed many multi-platform, telecommunication projects and was leading the IT system department. In 2001, Marin started to work in Germany as a senior system architect. He is currently working for German banks on different banking projects.

Latest Articles