IBM solidDB V6.1 in-memory database extends IBM Data Management portfolio
IBM United States
Software Announcement 208-132
June 17, 2008
 ENUS208132.PDF (582KB)
|
|
Table of contents
| | Document options |
|
| |
|
IBM solidDB V6.1, IBM solidDB Cache for DB2 V6.1, and IBM solidDB Cache for IDS V6.1 offer the same
enhanced capability for three different environments:
-
solidDB
-
solidDB Cache for DB2
-
solidDB Cache for IDS
In all three environments, solidDB can:
-
Deliver extreme speed: solidDB is designed to keep data in main memory at all times rather than on
disk. Applications can take advantage of its capability through standard ODBC, JDBC, SQL
interfaces.
-
Deliver extreme availability: solidDB can be configured to maintain two copies of the data
synchronized at virtually all times. In case of system failure, solidDB is designed to allow
applications to recover access to solidDB in less than a second.
-
Help reduce cost: solidDB is designed to be easy to deploy and administer since it can be embedded
directly into applications and run virtually unattended, helping to lower total cost of ownership
since it can be programmatically controlled by the application and it doesn't require dedicated
database administrators.
Back to top
IBM solidDB V6.1, a relational in-memory database, can deliver extreme speed, by performing up to
ten times faster than conventional disk-based databases. It uses the familiar SQL language and
enables applications to potentially achieve tens of thousands of transactions per second with
response times measured in microseconds. Whether deployed as a cache for IBM DB2® or IDS, or
standalone as the database of record, solidDB delivers performance-critical data with extreme speed.
solidDB integrates with existing IBM data servers to accelerate access to their data. This
acceleration can be particularly valuable for performance-critical data frequently accessed by many
concurrent users, typical of applications such as ticketing and reservation systems, online gaming,
event processing and alerting, e-commerce applications, and software as a service (SaaS) application
platforms. Additionally, data from DB2 or IDS can be cached in solidDB to help support peak
workloads experienced by such applications as customer service and stock trading.
IBM solidDB can help achieve extreme availability, by recovering from system failures in less than a
second. Using a two-node, hot-standby configuration, solidDB maintains copies of the data
synchronized between two solidDB nodes. This configuration can also be deployed with solidDB Cache
for DB2 or IDS, and complements the High Availability and Disaster Recovery (HADR) capabilities of
these data servers to deliver a more comprehensive solution.
The extreme speed and extreme availability of IBM solidDB, as compared to conventional disk-based
databases, is designed to enable businesses to keep data available and accessible. Greater
availability can help lower the costs associated with both planned and unplanned outages and delays.
solidDB can further help reduce costs because it can be controlled by the application and run
virtually unattended. Unattended database operation accelerates deployments and can help to reduce
administrative costs. Furthermore, because solidDB runs on commodity as well as best-of-breed
hardware, businesses can select from the most suitable solutions for their business need.
Back to top
Refer to the
Hardware requirements
and
Software requirements
sections for details.
Back to top
-
June 24, 2008: Electronic software delivery
-
July 25, 2008: Media
Back to top
Extreme speed
Achieving extreme speed with in-memory database technology
In-memory databases exist to meet the performance demands of real-time applications requiring
extreme speed and predictable response times. As their name implies, in-memory databases reside
entirely in main memory rather than on disk, making data access extremely fast.
Figure 1: Extreme speed of solidDB compared to conventional, disk-based database as measured in
maximum qualified throughput (MQTH)
Compared to on-disk databases that cache all data into main memory, solidDB in-memory database is
engineered to be faster with higher transaction throughput along with shorter and more consistent
response times.
Figure 1 show results from the Telecom One benchmark where solidDB in-memory database performance
was compared with conventional, on-disk database performance. It illustrates approximately 10 times
the throughput advantage for solidDB. Telecom One is a database benchmark test program developed by
Solid, an IBM Company, and is based on a database benchmark methodology designed for
telecommunications applications published as part of a Master's Thesis at the University of Helsinki
in 2003. More information about the Telecom One benchmark is available at
The above test was measured on a system with double CPU, dual-core
Intel® Xeon 2.66 GHz processor (total 8 cores) and 4 GB RAM, running
Windows® Server 2003 SP2. The test was performed using Telecom One
Benchmark v.4.1. with a 10 minute ramp up and 20 minutes sampling. The
test was performed on solidDB configured with asynchronous logging,
linked library deployment, and 5 minute checkpoint interval, on 128
concurrent clients simulating 100,000 mobile phone subscribers.
In-memory databases, such as solidDB, work under the premise that all
data that must be accessible with extreme speed will be in main memory.
Thus, it has data structures and access methods specifically designed for
storing, searching, and processing data in main memory, with efficient
concurrency control mechanisms. This has two potential performance
advantages over conventional, disk-based databases. First, it eliminates
the need to transfer data blocks from disk to main memory. This is
because any data requested by the application is already in main memory.
Second, solidDB is faster than disk-based databases, even if the latter
cache all data in main memory, since solidDB employs data structures and
access methods that are optimized for main memory access.
Additionally, solidDB is designed to leverage large memory sizes offered
by 64-bit computers, along with the processing scalability provided by
multicore, multiprocessor architectures. solidDB's access methods also
implement efficient concurrency control mechanisms to support large
numbers of concurrent transactions with transactional integrity while
providing response times measured in microseconds. Whether deployed as a
cache for IBM DB2 or IDS, or standalone as the database of record,
solidDB can help deliver performance-critical data with extreme speed.
Data persistence and recoverability
While solidDB in-memory database works under the premise that all data is
accessible in main memory, all the time, solidDB also writes updated data
to disk to help ensure recoverability of the data. This is accomplished
by solidDB's checkpoint function and transaction logging mechanisms.
When using the checkpoint function, solidDB copies committed transactions
from main memory to database files on disk. If the server fails between
checkpoints, solidDB helps ensure that the disk has a consistent snapshot
of the data. In between checkpoints, solidDB writes committed
transactions to a transaction log. After a system crash, solidDB will
attempt to automatically recover transactions committed since the last
checkpoint to the most recent committed state using this transaction log
and roll-forward recovery. In order to balance performance and
durability, solidDB transaction logging has different configuration
options. With strict logging, transactions are logged as soon as they
are committed, synchronously. With relaxed logging, solidDB defers
writing to the transaction log, asynchronously. Additionally, solidDB's
snapshot-consistent checkpoint function lets transaction logging be
turned off. This helps applications to achieve even faster performance
in situations where it is sufficient to provide recoverability only to
the last checkpoint.
Acceleration of access to data in DB2 or IDS
While conventional, disk-based databases provide the ability to store
very large databases and the versatility to support a broad variety of
workloads, solidDB in-memory database is designed to achieve higher
speeds for the data that fits into main memory. Thus, having
performance-critical portions of DB2 or IDS data in solidDB Cache can
help achieve the best of both worlds. Once performance-critical portions
of DB2 or IDS have been loaded into solidDB Cache, applications can
access and update those portions with short and consistent response times
measured in microseconds, and with throughput of tens of thousands of
transactions per second, while all changes are automatically synchronized
with DB2 or IDS. Meanwhile, DB2 or IDS makes the entire database
accessible to a broader set of applications for a wide variety of
workloads.
Whether deployed as a cache for IBM DB2 or IDS, or standalone as the
database of record, solidDB can boost performance even further by
providing a hot-standby configuration where read operations can be load
balanced across primary and hot-standby solidDB instances transparently
to the application. To take advantage of load balancing, an application
uses solidDB's ODBC or JDBC drivers that maintain only one logical
connection to both primary and hot-standby solidDB instances. In this
configuration, write transactions are automatically directed to the
primary solidDB node, and read transactions can be directed either only
to the hot-standby solidDB node, or load balanced across primary and
hot-standby solidDB instances, with the intent that application
developers do not have to write code. Using load balancing might yield
up to a 100 percent performance improvement by taking advantage of the
computation power of both primary and standby database instances. The
hot-standby configuration increases availability of solidDB nodes,
typically with sub-second failover in the event of a failure.
Hot-standby configuration can also increase performance by providing a
transaction logging optimization. With adaptive durability, the primary
solidDB instance can benefit from the performance boost of relaxed
logging, without sacrificing durability, because durability is maintained
by synchronizing with the hot-standby instance over the network. When a
failure occurs, the remaining solidDB instance is designed to
automatically shift to synchronous logging to provide greater durability
of data.
Additionally, for large tables that do not fit into the main memory of a
single server, solidDB Cache for DB2 or IDS allows administrators to
partition tables across multiple solidDB Cache instances for scaling out
across multiple servers. For instance, a large customer table on DB2 or
IDS that contains 1,000,000 customers can be partitioned into four
solidDB Cache instances with each storing 250,000 customers, instead of
caching all 1,000,000 customers into a single solidDB Cache instance.
Partitioning tables can be useful when the size of the
performance-critical data that must be cached is several dozens of
gigabytes. In this case, multiple commodity servers can be used to host
solidDB Cache instances instead of a single 64-bit processor server with
80 gigabytes of main memory. To boost performance even further, and
provide high availability of the performance-critical data at the same
time, partitioning of data across multiple solidDB Cache instances can be
combined with the hot-standby configuration of solidDB to deliver
automatic load balancing of read operations and sub-second failover.
Figure 2: Multiple instances of solidDB Cache accelerate DB2 and IDS
performance across multiple servers
Extreme availability
solidDB servers can typically recover from system failures in less than a
second, helping to provide the data availability required by
performance-critical applications. Using a two-node, hot-standby
configuration, solidDB maintains two copies of data synchronized between
the solidDB nodes. In case of system failure, failover between solidDB
nodes can occur in less than a second. This feature helps to protect
users from unplanned outages. Additionally, there are potential
secondary benefits to this architecture such as the ability to use the
solidDB hot-standby node for maintenance tasks (rolling upgrades,
reporting, and backup) without having to take the primary solidDB node
offline. Whether a system failure or a planned "switchover" between the
pair of solidDB nodes, the secondary solidDB server is designed to
quickly take over the processing load, minimizing the chance of data
loss. The failover is engineered to be transparent to the application;
solidDB ODBC and JDBC drivers maintain the database connection and
session attributes.
Additionally, solidDB offers several high availability configuration
options that specify how primary and secondary solidDB servers are
synchronized. These can be selected at the system, session, and
transaction levels. This enables users to balance throughput,
durability, and recovery time with greater flexibility.
The hot-standby configuration of solidDB can also be deployed with
solidDB Cache for DB2 or IDS, where the latter is configured for High
Availability and Disaster Recovery (HADR).
Figure 3: DB2 and IDS configured for High Availability and Disaster
Recovery
Hot-standby configuration:
-
Configurable replication and logging settings to achieve right trade-off
between performance, mean time to recovery (MTTR) — the average time to
recover from failure, and durability
-
Sub-second failover in case one of the solidDB Cache instances becomes
unavailable
-
Transparent connectivity:
-
Where application maintains only one logical connection to both primary
and secondary solidDB Cache instances
-
Lets the application maintain connection handle and session attributes
over failovers and switchovers
-
Transparent load balancing of read operations
Flexibility to balance data safety, application throughput, and recovery
time
solidDB offers several high-availability configuration options that
specify how primary and secondary database servers are synchronized. At
run time, applications can query these configurations and modify them for
individual sessions and transactions. This enables users to balance data
safety, application throughput, and recovery time with greater
flexibility.
Synchronous configuration
Synchronous replication is the most suitable configuration to minimize
and help avoid transaction loss. In this scenario, transactions are not
committed at the primary database before they are acknowledged by the
secondary one. Three different settings for synchronous replication are
available to users:
-
The secondary database acknowledges the commit record as soon as it
receives the request from the primary database.
-
The secondary database acknowledges the commit record after processing
the transaction request it receives from the primary database, but before
writing to the log.
-
The secondary database acknowledges the commit record after the
transaction log is fully committed at the secondary database. These
settings have an impact on the overall recovery time and the performance
of the application. Recovery time is much shorter when all transactions
committed at the primary database are also committed at the secondary
database. In case of a system failure of the primary database, the
secondary database has no required recovery to perform, and can quickly
take over the role of the primary database.
Asynchronous configuration
When using the asynchronous replication configuration, a commit command
that an application issues returns as soon as the transaction is
committed at the primary server. The application does not need to wait
for an acknowledgment from the secondary database server.
Figure 4: Built-in, high-availability state machine simplifies
integration with high availability managers
Further, solidDB maintains hot-standby states for both servers,
indicating their state to be active, standby, or another transitional
state associated with failovers. solidDB exposes these states to
applications, allowing them to query and programmatically set these
states. High availability managers use these states to monitor the
status of solidDB instances, and orchestrate the failover process when
appropriate.
Low cost
The extreme speed and extreme availability of IBM solidDB is intended to
address the need for businesses to always keep data available, helping to
avoid the costs associated with both planned and unplanned outages.
solidDB can further help to reduce costs because it can be controlled by
the application and run virtually unattended. Unattended operations can
let businesses accelerate deployments and potentially reduce
administrative costs that help result in a lower total cost of ownership.
Furthermore, since solidDB can run on commodity as well as best-of-breed
hardware, it allows you to choose the most appropriate solution for your
business needs.
solidDB deployment options
solidDB helps to deliver extreme speed to applications, whether deployed
as cache to accelerate access to data stored in DB2 and IDS, or deployed
standalone as the database of record. solidDB integrates with existing
IBM data servers, and thus can be deployed as a cache for IBM DB2 and IDS
to accelerate access to data stored. This acceleration can be
particularly valuable for performance-critical data frequently accessed
by many concurrent users, typical of applications such as ticketing and
reservation systems, online gaming, event processing and alerting,
e-commerce applications, and software as a service (SaaS) application
platforms. Additionally, data from DB2 or IDS can be cached in solidDB
to help to support peak workloads experienced by such applications as
customer service and stock trading.
Once performance-critical data is specified for caching and loaded from
DB2 or IDS into solidDB Cache, applications are able to query and modify
the data in solidDB using SQL. These changes are automatically
propagated to DB2 or IDS, with all transactions asynchronously persisted
in DB2 or IDS. Reporting and other read transactions are executed
against DB2 or IDS. Alternatively, solidDB Cache for DB2 or IDS can be
used as a read-only cache, where the data is updated only in DB2 or IDS,
and subsequently reloaded into solidDB Cache for querying.
Figure 5: IBM solidDB deployed as cache to DB2 or IDS
For large database sizes, data can be partitioned using multiple solidDB
Cache instances as shown in Figure 2.
-
Application may use solidDB Cache in client/server fashion, or can link
with solidDB linked library.
-
solidDB Cache hot-standby pair can be used for high availability and load
balancing of reads.
-
solidDB scales across multiple servers.
Performance data information
All performance data contained in this publication was obtained in the
specific operating environment and under the conditions described or
referenced above and are presented as an illustration. Performance
obtained in other operating environments may vary and customers should
conduct their own testing.
Accessibility by people with disabilities
A U.S. Section 508 Voluntary Product Accessibility Template (VPAT) can be requested via the IBM Web
site
Section 508 of the U.S. Rehabilitation Act
The products in this announcement are capable as of July 25, 2008, when used in accordance
with IBM's associated documentation, of satisfying the applicable requirements of Section 508 of the
Rehabilitation Act, provided that any assistive technology used with the product properly
interoperates with it. A U.S. Section 508 Voluntary Product Accessibility Template (VPAT),
containing details on the products accessibility compliance, can be requested on the following Web
site
IPLA and Subscription and Support considerations
IPLA licenses can be transferred from one machine to another within, but
not limited to an enterprise. You may aggregate the capacity for all the
processors the product is operated on to achieve a more economic price.
This will result in a single Proof of Entitlement (PoE). It is your
responsibility to manage the distribution of Value Units within the
limits of the entitlement of the product license.
Subscription and Support must cover the same capacity as the product
license entitlement. Subscription and Support will be available in the
country in which the agreement is made.
Trademarks
-
-
DB2 is a registered trademark of International Business Machines
Corporation in the United States or other countries or both.
-
-
Intel is a registered trademark of Intel Corporation.
-
-
Windows is a registered trademark of Microsoft Corporation.
-
-
Other company, product, and service names may be trademarks or service
marks of others.
Back to top
IBM training provides education to support many IBM offerings.
Descriptions of courses for IT professionals and managers are on the IBM
training Web site
Call IBM training at 800-IBM-TEACH (426-8322) for catalogs, schedules,
and enrollments.
Instructor-led course listing
Course number Course name Brief description
CF180 for US; CF18G Relational Database After an overview of
for WW Design relational concepts
that are important
for designing
relational
databases, learn
about the different
views of the data of
the application
domain and the steps
included in this
comprehensive
relational database
design methodology.
Back to top
Product information is available via the Offering Information Web site
Also, visit the Passport Advantage® Web site
Back to top
No hardcopy publications are shipped with these products.
The following publications will be available on the Internet and are
shipped electronically with the solidDB products. The Internet site can
be reached via
-
IBM solidDB Getting Started Guide
-
IBM solidDB Administrator Guide
-
IBM solidDB Programmer Guide
-
IBM solidDB SQL Guide
-
IBM solidDB High Availability User Guide
-
IBM solidDB In-Memory Database User Guide
-
IBM solidDB Linked Library Access User Guide
-
IBM solidDB Advanced Replication Guide
-
IBM solidDB Connector Guide
Back to top
Specified operating environment
Hardware requirements
Minimum hardware requirements:
-
32 bit and 64 bit (x64) Windows® and Linux™: All systems based on Intel® or AMD processors
that are capable of running the supported Windows or Linux operating systems (x86 and x64 systems).
-
AIX® for IBM System p™ systems: 64-bit systems with POWER5™, or later processors are required.
-
Solaris: 32-bit and 64-bit systems with UltraSPARC processors, AMD 32-bit and 64-bit processors, or
Intel x86 processors are required.
-
HP-UX: Itanium-based HP Integrity Series systems are required.
Memory requirements: The amount of memory required for the solidDB JDBC and ODBC clients depends on
the operating system and the database applications that are running. In most cases, it should be
sufficient to use the minimum memory requirements of the operating system as the minimum requirement
for running the solidDB JDBC and ODBC clients.
The amount of memory required for the solidDB connector depends on the operating system and the
database applications that are running. In most cases, it should be sufficient to use the minimum
memory requirements for DB2® Linux, UNIX, and Windows (LUW), or IDS as the minimum requirement for
running the solidDB connector.
The amount of memory required for the solidDB in memory engine depends on the operating system and
the database applications that are running. Memory requirements will primarily depend on the size
of the database.
Disk space requirements: The minimum disk space is 10 MB for a typical installation. The actual
space required will vary depending on the logging parameters selected, use of the on disk engine,
and the size of the database stored on disk.
Software requirements
This section indicates the operating systems and data servers supported by solidDB, solidDB Cache
for DB2, and solidDB Cache for IDS at the time of this announcement.
Linux
-
Red Hat Enterprise Linux (RHEL) 4 and 5
-
SUSE Linux Enterprise Server (SLES) 9 and 10
Windows
-
32 bit and 64 bit (x64) Windows Server 2003, Standard Server, Enterprise Server, and Datacenter
Editions
-
32 bit and 64 bit (x64) Windows XP Professional Edition
-
32 bit and 64 bit (x64) Windows Vista® Business, Enterprise, and Ultimate editions
AIX
-
AIX 5L™ V5.3 for POWER5 and POWER6™ 64-bit systems
HP-UX
-
HP-UX 11i V2 for HP 64-bit Integrity servers (Itanium-based systems)
Solaris
-
Solaris 10 for Sun UltraSPARC, AMD 32 bit and 64 bit, and Intel x86 servers
solidDB Cache for DB2
-
DB2 for Linux, UNIX, and Windows Enterprise Server Edition V9.5
-
DB2 for Linux, UNIX, and Windows Enterprise Server Edition V9.1
-
DB2 9 for z/OS®
-
DB2 for z/OS V8
-
Restrictions: When running solidDB Cache for DB2 with DB2 for z/OS, the solidDB Connector must run
on a Linux, UNIX, or Windows platform, not on the System z™ platform.
-
Prerequisites: When running solidDB Cache for DB2 with DB2 for z/OS, a license of DB2 Connect® is
required and must run on the same server as the solidDB Connector.
solidDB Cache for Informix™ Dynamic Server (IDS)
-
IDS V11.5 Enterprise Edition
-
IDS V11.1 Enterprise Edition
The program's specifications and specified operating environment information may be found in
documentation accompanying the program, if available, such as a README file, or other information
published by IBM, such as an announcement letter. Documentation and other program content may be
supplied only in the English language.
Planning information
Customer responsibilities:
Successful application operation and management of IBM products are the responsibility of the
user. Examples of those responsibilities are:
-
Confirming the validity of the proposed equipment and programs
-
Developing appropriate system procedures
-
Incorporating protective measures to safeguard the privacy of data from unauthorized modification,
destruction, or disclosure
-
Incorporating sufficient checkpoints, balances, and controls into the application design to satisfy
accuracy, restart, and audit requirements
-
Establishing adequate backup contingency plans
-
Preparing adequate documentation
-
Providing qualified personnel to obtain the desired results
Software Maintenance is included with licenses purchased through Passport Advantage and Passport
Advantage Express. Product upgrades and technical support are provided by the Software Maintenance
offering as described in the Agreements. Product upgrades provide the latest versions and releases
to entitled software, and technical support provides voice and electronic access to IBM support
organizations, worldwide.
IBM includes one year of Software Maintenance with each program license acquired. The initial
period of Software Maintenance can be extended by the purchase of a renewal option, if available.
Packaging
IBM solidDB V6.1.0 Multiplatform English
-
License Information (paper)
-
solidDB V6.1.0 Multiplatform Media Pack (DVD)
IBM solidDB Cache V6.1.0 for DB2 Multiplatform English
-
License Information (paper)
-
solidDB Cache V6.1.0 for DB2 Multiplatform Media Pack (DVD)
IBM solidDB Cache V6.1.0 for IDS Multiplatform English
-
License Information (paper)
-
solidDB Cache V6.1.0 for IDS Multiplatform Media Pack (DVD)
Security, auditability, and control
The products in this announcement use the security and auditability features of the host hardware
and software.
The customer is responsible for evaluation, selection, and implementation of security features,
administrative procedures, and appropriate controls in application systems and communication
facilities.
Back to top
IBM Software Services has the breadth, depth, and reach to manage your services needs. You can
leverage the deep technical skills of our lab-based, software services team and the business
consulting, project management, and infrastructure expertise of our IBM Global Services team. Also,
we extend our IBM Software Services reach through IBM Business Partners to provide an extensive
portfolio of capabilities. Together, we provide the global reach, intellectual capital, industry
insight, and technology leadership to support a wide range of critical business needs.
To learn more about IBM Software Services or to contact a Software Services sales specialist, visit
To locate an IBM Business Partner, visit
Back to top
This product is only available via Passport Advantage. It is not available as shrinkwrap.
Product information
Product
Licensed function title Product group category
IBM solidDB solidDB solidDB
IBM solidDB Cache for DB2 solidDB solidDB
IBM solidDB Cache for IDS solidDB solidDB
PID Charge unit
Program name number description
IBM solidDB 5724-V17 SubCapacity
Processor Value
Unit (PVU)
IBM solidDB 5724-V17 Processor Value
Unit (PVU)
IBM solidDB Cache for DB2 5724-V18 Processor Value
Unit (PVU)
IBM solidDB Cache for DB2 5724-V18 SubCapacity
Processor Value
Unit (PVU)
IBM solidDB Cache for IDS 5724-V19 Processor Value
Unit (PVU)
IBM solidDB Cache for IDS 5724-V19 SubCapacity
Processor Value
Unit (PVU)
Charge metrics definitions
Value Unit
A Value Unit is a pricing charge metric for program license entitlements which is based upon the
quantity of a specific designated measurement used for a given program. Each program has a
designated measurement. The most commonly used designated measurement is a processor core.
However, for select programs, there are other designated measurements such as users or resources
which may include servers, client devices, and messages. The number of Value Unit entitlements
required for a program depends on how the program is deployed in your environment and must be
obtained from a Value Unit table. You must obtain a Proof of Entitlement (PoE) for the calculated
number of Value Unit entitlements for your implementation. The Value Unit entitlements are specific
to a program and may not be exchanged, interchanged, or aggregated with Value Unit entitlements of
another program.
Processor (Value Unit)
A processor core is a functional unit within a computing device that interprets and executes
instructions. A processor core consists of at least an instruction control unit and one or more
arithmetic or logic unit. With multicore technology, each core is considered a processor. Not all
processor cores require the same number of Processor Value Unit entitlements. To calculate the
number of Processor Value Unit entitlements required, refer to the Processor Value Unit table on the
following Web site
With full capacity licensing, a PoE must be acquired for the appropriate
number of Processor Value Units based on all activated processor cores
available for use on the server.
Sub-capacity processor (Value Unit)
For programs eligible for sub-capacity licensing, a PoE must be acquired
for the appropriate number of Processor Value Units based on all
activated processor cores available for use in each partition (utilizing
eligible partitioning technologies) where the program runs. Refer to the
International Passport Advantage Agreement Attachment for sub-capacity
terms or the program's license information to determine applicable
sub-capacity terms.
Passport Advantage program licenses
IBM solidDB
Part
Part description number
IBM solidDB
solidDB Proc VU (PVU) License & SW Subscrip & Spt 12 D0461LL
Months
solidDB Proc VU (PVU) License & SW Subscrip & Spt E04WULL
AnRnwl
solidDB Proc VU (PVU) License & SW Subscrip & Spt D0462LL
Reinstate 12 Months
IBM solidDB Cache for DB2
Part
Part description number
IBM solidDB Cache for DB2
solidDB Cache DB2 Proc VU (PVU) License & SW Subscrip & D045ZLL
Spt 12 Months
solidDB Cache DB2 Proc VU (PVU) License & SW Subscrip & E04WTLL
Spt AnRnwl
solidDB Cache DB2 Proc VU (PVU) License & SW Subscrip & D0460LL
Spt Reinstate 12 Months
IBM solidDB Cache for IDS
Part
Part description number
IBM solidDB Cache for IDS
solidDB Cache IDS Proc VU (PVU) License & SW Subscrip & D046JLL
Spt 12 Months
solidDB Cache IDS Proc VU (PVU) License & SW Subscrip & E04XCLL
Spt AnRnwl
solidDB Cache IDS Proc VU (PVU) License & SW Subscrip & D046KLL
Spt Reinstate 12 Months
Passport Advantage supply
Part
Program name/description number
solidDB Cache for DB2 V6.1.0
solidDB Cache for DB2 Multiplatform V6.1.0 DVD Media BB0X4EN
Pack English
solidDB Cache for IDS V6.1.0
solidDB Cache for IDS Multiplatform V6.1.0 DVD Media BB0X5EN
Pack English
solidDB V6.1.0
solidDB Multiplatform V6.1.0 DVD Media Pack English BB0X3EN
Passport Advantage customer: Media pack entitlement details
Customers with active maintenance or subscription for the products listed are entitled to receive
the corresponding media pack.
solidDB V6.1.0
Entitled maintenance Part
offerings description Media packs description number
solidDB per Processor solidDB Multiplatform BB0X3EN
Value Unit V6.1.0 DVD Media Pack
English
solidDB per SubCapacity solidDB Multiplatform BB0X3EN
Processor Value Unit V6.1.0 DVD Media Pack
English
solidDB Cache for IDS V6.1.0
Entitled maintenance Part
offerings description Media packs description number
solidDB Cache for IDS per solidDB Cache for IDS BB0X5EN
Processor Value Unit Multiplatform V6.1.0 DVD
Media Pack English
solidDB Cache for IDS per solidDB Cache for IDS BB0X5EN
SubCapacity Processor Multiplatform V6.1.0 DVD
Value Unit Media Pack English
solidDB Cache for DB2 V6.1.0
Entitled maintenance Part
offerings description Media packs description number
solidDB Cache for DB2 per solidDB Cache for DB2 BB0X4EN
Processor Value Unit Multiplatform V6.1.0 DVD
Media Pack English
solidDB Cache for DB2 per solidDB Cache for DB2 BB0X4EN
SubCapacity Processor Multiplatform V6.1.0 DVD
Value Unit Media Pack English
Sub-capacity
IBM solidDB
Part number Part description
D0463LL solidDB SubCap PVU License & SW
Subscrip & Spt 12 Months
E04WWLL solidDB SubCap PVU License & SW
Subscrip & Spt AnRnwl
D0466LL solidDB SubCap PVU License & SW
Subscrip & Spt Reinstate 12 Mo
IBM solidDB Cache for DB2
Part number Part description
D046HLL solidDB Cache DB2 SubCap PVU
License & SW Subscrip & Spt 12
Months
E04XBLL solidDB Cache DB2 SubCap PVU
License & SW Subscrip & Spt
AnRnwl
D046ILL solidDB Cache DB2 SubCap PVU
License & SW Subscrip & Spt
Reinstate 12 Mo
IBM solidDB Cache for IDS
Part number Part description
D046FLL solidDB Cache IDS SubCap PVU
License & SW Subscrip & Spt 12
Months
E04XALL solidDB Cache IDS SubCap PVU
License & SW Subscrip & Spt
AnRnwl
D046GLL solidDB Cache IDS SubCap PVU
License & SW Subscrip & Spt
Reinstate 12 Mo
Sub-capacity for selected middleware products
Sub-capacity licensing on a per processor or per Value Unit basis is available for selected
middleware products. To offer sub-capacity licensing, IBM software products implement IBM Tivoli®
License Compliance Manager within their offerings so that you can monitor and report quarterly to
IBM on the use of the programs on a continuous basis.
More information can be found on the Passport Advantage Web site
Eligibility requirements for sub-capacity licensing
To be eligible for sub-capacity licensing terms on this product, you must
agree to install and configure IBM Tivoli License Manager for IBM
Software, in accordance with the IBM Tivoli License Manager publications,
and to enable the collection of program use data on all eligible machines
subject to sub capacity terms.
For those machines running programs with sub-capacity licensing terms,
you must use IBM Tivoli License Manager for IBM Software to monitor
program use and submit to IBM an IBM Use Report each calendar quarter.
Multiple copies of IBM Tivoli License Manager for IBM Software or IBM
Tivoli License Manager are not required. You can use more copies if you
need them to support your operational environment, but only one copy is
required to monitor all your sub-capacity licensed products.
Additionally, if this is the first product you have licensed under sub
capacity terms, you must agree to the terms of an attachment to your
Passport Advantage or Passport Advantage Express contract and submit a
new Passport Advantage enrollment form. First-time sub-capacity clients
also have an opportunity to ensure a primary business contact is
established for their contracts.
For more information on required and entitled license capacity, license
requirements, and reporting, refer to Software Announcement
205-093
, dated April 19, 2005.
If you order (this product) under sub-capacity terms, IBM Tivoli License
Manager for IBM Software will be made available to you if you do not
already have one. You must install and configure this tool for your
sub-capacity products. Alternately, you can use Tivoli License Manager.
Once the license manager software is installed, you will be required to
register online. (IBM may need to contact you in order to finalize the
registration process.) You must monitor program use on a continuous basis
with an IBM Tivoli License Manager for IBM Software and submit IBM Use
Reports to IBM on a calendar quarterly basis.
IBM Tivoli License Manager for IBM Software is documented in the
following customer publications, which are available from IBM
Publications Center at
Publication Form
Planning, Installation, and SC32-1431
Configuration
Administration SC32-1430
Problem Determination SC32-9102
Data Dictionary SC32-1432
Release Notes SC32-1429
For IBM Tivoli License Manager configuration guidance and instructions
for specific products (including this product) acquired with sub capacity
terms, refer to
The Web site will give you information about how to set up the product
for detection by IBM Tivoli License Manager, any required maintenance,
and any required steps that are unique to this product.
Back to top
The information provided in this announcement letter is for reference and
convenience purposes only. The terms and conditions that govern any
transaction with IBM are contained in the applicable contract documents
such as the IBM International Program License Agreement, IBM
International Passport Advantage Agreement, and the IBM Agreement for
Acquisition of Software Maintenance.
Licensing:
IBM International Program License Agreement including the License
Information document and PoE govern your use of the Program. PoEs are
required for all authorized use.
Part number products only, offered outside of Passport Advantage, where
applicable, are license only and do not include Software Maintenance.
This software license includes Software Maintenance, previously referred
to as Software Subscription and Technical Support.
License Information form numbers
Program
Program name number Form number
IBM solidDB 5724-V17 L-CLAW-7DBJWB
IBM solidDB Cache for DB2 5724-V18 L-CLAW-7DBJWB
IBM solidDB Cache for IDS 5724-V19 L-CLAW-7DBJWB
The program's License Information will be available for review on the IBM
Software License Agreement Web site
Limited warranty
Limited warranty applies:
Yes
Warranty:
IBM warrants that when the program is used in the specified
operating environment, it will conform to its specifications. The
warranty applies only to the unmodified portion of the program. IBM does
not warrant uninterrupted or error-free operation of the program or that
IBM will correct all program defects. You are responsible for the
results obtained from the use of the program.
IBM provides you with access to IBM databases containing information on
known program defects, defect corrections, restrictions, and bypasses at
no additional charge. Consult the
IBM Software Support Handbook
for further information at
IBM will maintain this information for at least one year after the
original licensee acquires the program (warranty period).
Program technical support:
Technical support of a program product will be available for a
minimum of five years from the general availability date, as long as your
Software Maintenance is in effect. This technical support allows you to
obtain assistance (via telephone or electronic means) from IBM for
product-specific, task-oriented questions regarding the installation and
operation of the program product. Software Maintenance also provides you
with access to updates, releases, and versions of the program. You will
be notified, via announcement letter, of discontinuance of support with
12 months' notice. If you require additional technical support from IBM,
including an extension of support beyond the discontinuance date, contact
your IBM representative or IBM Business Partner. This extension may be
available for a fee.
Money-back guarantee:
If for any reason you are dissatisfied with the program and you are
the original licensee, you may obtain a refund of the amount you paid for
it, if within 30 days of your invoice date you return the program and its
PoE to the party from whom you obtained it. If you downloaded the
program, you may contact the party from whom you acquired it for
instructions on how to obtain the refund.
For programs acquired under the IBM International Passport Advantage
Agreement, this term applies only to your first acquisition of the
program.
Authorization for use on home/portable computer:
The program may be stored on the primary machine and another
machine, provided that the program is not in active use on both machines
at the same time. You may not copy and use this program on another
computer without paying additional license fees.
Product name
IBM solidDB No
IBM solidDB Cache for DB2 No
IBM solidDB Cache for IDS No
Usage restriction:
Yes. For additional information refer to the License Information
Document that is available on the IBM Software License Agreement Web site
International Passport Agreement
Passport Advantage applies:
Yes, and through the Passport Advantage Web site at
This product is only available via Passport Advantage. It is not
available as shrinkwrap.
Agreement for Acquisition of Software Maintenance
The following agreement applies for maintenance and does not require
customer signatures:
-
IBM Agreement for Acquisition of Software Maintenance (Z125-6011)
Software Maintenance applies:
Yes. Software Maintenance is included with licenses purchased
through Passport Advantage and Passport Advantage Express. Product
upgrades and technical support are provided by the Software Maintenance
offering as described in the Agreements. Product upgrades provide the
latest versions and releases to entitled software and Technical Support
provides voice and electronic access to IBM support organizations,
worldwide.
IBM includes one year of Software Maintenance with each program license
acquired. The initial period of Software Maintenance can be extended by
the purchase of a renewal option, if available.
While your Software Maintenance is in effect, IBM provides you assistance
for your routine, short duration installation and usage (how-to)
questions, and code-related questions. IBM provides assistance via
telephone and, if available, electronic access, to your information
systems (IS) technical support personnel during the normal business hours
(published prime shift hours) of your IBM support center. (This
assistance is not available to your end users.) IBM provides Severity 1
assistance 24 hours a day, 7 days a week. For additional details,
consult your
IBM Software Support Handbook
at
Software Maintenance does not include assistance for the design and
development of applications, your use of programs in other than their
specified operating environment, or failures caused by products for which
IBM is not responsible under the applicable agreements.
For additional information about the International Passport Advantage
Agreement and the IBM International Passport Advantage Express Agreement,
visit the Passport Advantage Web site at
Other terms
Volume orders (IVO):
No
System i™ Software Maintenance applies:
No
Educational allowance available
Not applicable.
Back to top
IBM has transformed its delivery of hardware and software support services to help you achieve
higher system availability. Electronic Services is a Web-enabled solution that offers an exclusive,
no-additional-charge enhancement to the service and support available for IBM servers. These
services are designed to provide the opportunity for greater system availability with faster problem
resolution and preemptive monitoring. Electronic Services comprises two separate, but
complementary, elements: Electronic Services news page and Electronic Services Agent.
The Electronic Services news page is a single Internet entry point that replaces the multiple entry
points traditionally used to access IBM Internet services and support. The news page enables you to
gain easier access to IBM resources for assistance in resolving technical problems.
The Electronic Service Agent™ is no-additional-charge software that resides on your server. It
monitors events and transmits system inventory information to IBM on a periodic, client-defined
timetable. The Electronic Service Agent automatically reports hardware problems to IBM. Early
knowledge about potential problems enables IBM to deliver proactive service that may result in
higher system availability and performance. In addition, information collected through the Service
Agent is made available to IBM service support representatives when they help answer your questions
or diagnose problems. Installation and use of IBM Electronic Service Agent for problem reporting
enables IBM to provide better support and service for your IBM server.
Back to top
Passport Advantage
For Passport Advantage information and charges, contact your IBM representative or authorized IBM
Business Partner. Additional information is also available at
Business Partner information
If you are an IBM Business Partner — Distributor for Workstation
Software acquiring products from IBM, you may link to Passport Advantage
Online for resellers where you can obtain Business Partner pricing
information. An IBM ID and password are required.
Trademarks
-
-
POWER5, System p, AIX 5L, POWER6, System z, Informix, IBMLink, System i,
and Electronic Service Agent are trademarks of International Business
Machines Corporation in the United States or other countries or both.
-
-
Passport Advantage, AIX, DB2, z/OS, DB2 Connect, Lotus, Tivoli, and
PartnerWorld are registered trademarks of International Business Machines
Corporation in the United States or other countries or both.
-
-
Intel is a registered trademark of Intel Corporation.
-
-
Windows and Windows Vista are registered trademarks of Microsoft
Corporation.
-
-
Linux is a trademark of Linus Torvalds in the United States, other
countries or both.
-
-
Other company, product, and service names may be trademarks or service
marks of others.
At a glance
