From "Try & Buy" to Production Database

Monday Mar 31st 2003 by Marin Komadina
Share:

Join Marin Komadina as he explains what the DBA needs to know regarding licensing, database packaging models, on a Sun Solaris platform.

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

Version 8.1 Enhancements

DB2 v.8.1 Enterprise Server Edition (ESE) coming with a full set of new and updated options, such as Connection Concentrator, Catalog Caching, Online Reorganization, Online Index Maintenance, Snapshot table functions, Online Database Checking Tool, Logging Enhancements, Multi- FixPak Install for UNIX, Rollforward to Localtime, Disk storage management and concurrency (lock contention), Web- based Administration Tool ... and many others.

One of the great enhancements is Multi-FixPak Install for customers that have a requirement for support multiple Fixpaks to coexist on the same machine running the same version of database code.

This feature makes it possible to have a production and test database on the same machine, on different FixPack levels. Regular FixPak is installed on top of the existing code. When the customer needs Alternate FixPak it can be installed and will behave as a fully installable database with same level of code as the regular FixPak.

Version 8.1 Database Packaging Models

In version 8.1, Datababase Packaging Models have new definitions and all have same level of portability, availability, and the same database engine with differences in included options and licensing model.

DB2 Workgroup Server Edition (WSE)is a multi-user, single host, web enabled database with included Java support, but without support for inter or intra partition parallelism. WSE should be used for small systems with a countable number of users. WSE has a registration limit of a maximum of 4 processors.

DB2 Workgroup Server Unlimited Edition (WSUE) has the same functionality, and the same registration limit of a maximum 4 processors, but a different pricing model.

DB2 UDB Enterprise Server Edition (ESE) is the highest level of DB2 database version with intrapartition parallelism support (the database engine can process SQL statement segments in parallel), and interpartition parallelism support (process a query in parallel across all of the nodes). ESE has Partitioning and Clustering options as additional add-on features.

Installed database options can be checked with pkginfo command:

	$  pkginfo | grep db2
... 
	application db2engn81      Engine (PTF 1720600-014)
	application db2jdbc81      Java Support (PTF 1720600-037)
	application db2pext81      Parallel Extension (PTF 1720600-055)
	application db2rte81       Run-time Environment (PTF 1720600-015)
	application db2spb81       Stored Procedure Builder
	...

DB2 Version 8 Licensing and License Management

Licensing Policy for DB2 is based on several factors:

  • number of registered or concurrent users,
  • number of processors,
  • number of database partitions and
  • high availability configuration

Every factor has special meaning and all together define total database licensing price.

User license (Connection License):

1.) Registered user license is an unlimited access user license. This license is based on the number of client seats (individuals) that access any DB2 servers in a company.

2.) Concurrent user license is a limited access user license for the maximum concurrent client connections coming to one database server.

Server license is a DB2 license based on the number of server processors.

IBM Licensing Models for DB2

DB2 Workgroup Server Edition (WSE) is licensed by the number of connections to the database.

The licensing price is defined with a base price for server license + n x user connections (registered or concurrent). The base server license covers machines ranging from uni-processor up to 4-way SMP and is offered in a packaging suite of 50 user connections.

DB2 WSE has a special discount price in shrink-wrap purchase combination (database without Passport Advantage and customer support), but then you have no further rights on discounts for future upgrades.

DB2 Workgroup Server Unlimited Edition (WSUE) is licensed by the number of available processors for external access (web access from external network) and per connection for users on a corporate network. Special discount versions (shrink-wrap licensing) are not possible. A maximum 4 licensed processor allowed.

DB2 UDB Enterprise Server Edition (ESE) is licensed by the number of available processors and database connections. This licensing method has no limit on the number of processors. ESE has Partitioning and Clustering support as add-on features for the DB2 database engine, which are additionally licensed per processors.

Licensing for High Availability Configurations

For High-Availability (HA) configurations, special licensing rules applies. It is a question of standby failover node and how it is used in combination with other nodes.

1.) Mutual takeover is a configuration where every node can replace any other nodes in a case of failover. Defined configuration scripts have to be prepared to establish load balancing after takeover so that all database partitions handle approximately same data volume after failover. All nodes are working nodes and all need a separate license.

2.) "Idle standby" (Cold Standby) configuration has one idle node. idle node will take over the work of one failed node when a failure occurs. The idle node can run with or without an activated database, however, there should not be any transactional work on that node. [lbc1] For DB2 UDB EE we have only to pay for one processor on the idle node, even if we are running on a four-way SMP machine. If we have implemented idle standby configuration with DB2 UDB Enterprise Extended Edition (EEE), then we need licenses for all processors on the idle node.

3.) In "Active standby" (Hot Standby) configuration all servers have active DB2 databases. One node is designated as the active standby node and will take over any of failover nodes in the system in a case of failure. This configuration does not waste machine resources, however, the Hot Standby machine must be fully licensed. Compared to idle standby, idle standby is dedicated to just one failed server's workload, while an active standby is set up to take the work of two servers in the event of a failure.

DB2 cluster agent for Sun Cluster (DB2 UDB HA agent for Sun Cluster) is given with DB2 server distribution media starting from version 7 FixPack 5 or can be downloaded from IBM's official site. Sun Cluster 2.2 is fully supported and Sun Cluster 3.0 is supported starting with version 7.1 FixPack 3.

Licensing Procedure




We will start with a very basic situation, where we have installed a DB2 database. It is 90 days "Try & Buy" database version 8.1 for Sun Solaris.




Test database license information:




>> 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             = ""

Installed DB2 database is version 8.1 and it is DB2 Enterprise Extended Edition.

This version is licensed for 1 processor on a 4-processor machine.

One very important parameter regarding licensing is the Enforcement Policy.

The Enforcement Policy has two possible values with the following meanings:

  • HARD specifies that unlicensed requests will not be allowed.
  • SOFT specifies that unlicensed requests will be logged but not restricted.

To register a new license instead of an existing Try & Buy, we need the distribution CD with the real database license. The full pathname to the license key is /cdrom/db2/license/db2udbeee.lic

# cat db2udbeee.lic
License Certificate for XXXXXX IBM DB2 UDB Enterprise-Extended Edition, V8.1
[LicenseCertificate]
VendorName=IBM Toronto Lab
VendorPassword=XXXXXXXXXXXXXX
VendorID=XXXXXXXXXXXXXXXXXXXX
ProductName=DB2 Enterprise - Extended Editi
ProductID=XXXX
ProductVersion=8.1
ProductPassword=PASS
ProductAnnotation=
LicenseStyle=nodelocked
LicenseStartDate=XXXXXX
LicenseDuration=13932
LicenseEndDate=12/31/2037
LicenseCount=1
MultiUseRules=
RegistrationLevel=3
TryAndBuy=No
SoftStop=No
TargetType=ANY
TargetTypeName=Open Target
TargetID=ANY
ExtendedTargetType=
ExtendedTargetID=
DerivedLicenseStyle=
DerivedLicenseStartDate=
DerivedLicenseEndDate=
DerivedLicenseAggregateDuration=
SerialNumber=
Upgrade=No
-----------------------------------------------------------------------------------------
# 
xxxxxxxxxxxxxxxxxx.00.00.00.00.00.00.00.00 xxxxxxxxxxxxxxxxx "" "7.1"
#[admin_comment] "IBM Toronto Lab" "DB2 Enterprise - Extended Editi" "xxxxxxxxx" "0" "1"
#

As root user we are going to add a new license:

/opt/IBMdb2/V8/adm/db2licm a  /cdrom/db2/license/db2udbeee.lic

The registration process will put the product license key in the file nodelock located on /var/lum/ with the following rights:

-rw-r--r--   1 root     other        313 Feb  6 13:52 nodelock

Nodelock file content after registration:

# cat nodelock
# 
5effaa0123d34e.01.00.11.0d.21.01.01.00 fffe832apvbeema4ipvamqa "" "7.1"
#[admin_comment] "IBM Toronto Lab" "DB2 Enterprise Edition" "3546226633" "0" "1"

Every new separate licensed product added to an existing installation will have a license entry in the nodelock file.

After registration, we will restart the database and check thelicensing information again:

>> db2licm -l
Product Name                  = "DB2 Enterprise - Extended Edition"
Product Password              = "PASS"
Version Information           = "8.1"
Expiry Date                   = "Permanent"
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             = ""

Database error log (db2diag.log) is reporting the following error message:

SQL8017W  The number of processors on this machine exceeds the defined 
entitlement of "1" for the product "DB2 Enterprise - Extended Edition".  The 
number of processors on this machine is "4".  You should purchase additional 
processor entitlements from your IBM representative or authorized dealer and 
update your license using the License Center or the db2licm command line 
utility. For more information on updating processor licenses, refer to the 
Quick Beginnings manual for your platform.  For more information on the 
db2licm utility, refer to the DB2 Command Reference.

We are getting this error because we have 4 CPUs on the machine and we had registered only one CPU. We need to register all of the processors using the database password:

$ db2licm -n PASS 4

New license information after processor registration:

>> db2licm -l
Product Name                  = "DB2 Enterprise - Extended Edition"
Product Password              = "PASS"
Version Information           = "8.1"
Expiry Date                   = "Permanent"
Concurrent Connect User Policy = "Disabled"
Registered Connect User Policy = "Disabled"
Enforcement Policy            = "Soft Stop"
Number of processors          = "4"
Number of licensed processors = "4"
Annotation                    = ""
Other information             = ""

The DB2 database is fully registered for 4 processors, without the Connect User Policy enabled.

For per user connection licensing we would need to add additional Conncurent or Registered User licenses (db2licm -u num_user_licenses).

Conclusion

DB2 offers outstanding technology with affordable prices for software licensing, support and upgrades. The user is obligated to provide internal audit on license use and to report changes in license configuration periodically to IBM.

Support for older database versions is still provided and working well.

Can we expect that IBM will cut support and press customers to recheck compliance for older database versions like Oracle did? We'll have to wait and see...

» See All Articles by Columnist Marin Komadina

Share:
Home
Mobile Site | Full Site
Copyright 2017 © QuinStreet Inc. All Rights Reserved