Cognos and the bundled Db2 scope trap.

Cognos Analytics ships with a limited use copy of Db2 to hold its content store. That copy is one of the most common scope traps in an IBM audit, because it is so easy to treat a free database as a general one.

Why Cognos includes Db2 at all

Cognos needs a relational store for its content, configuration, and audit logging. To make deployment simple, IBM bundles a Db2 instance for that purpose under a restricted use grant. The grant is narrow on purpose. The bundled Db2 is licensed to serve the Cognos content store and the directly related functions described in the Cognos License Information document. It is not a license to run a shared database.

How the trap springs

The trap is rarely deliberate. A team already running the bundled Db2 sees a convenient, installed, paid for database and points another workload at it. A reporting feed, a small application, a data mart, an integration job. Each addition feels harmless. Each one moves use outside the content store grant and turns a free instance into unlicensed standalone Db2, counted in PVU across its cores.

• Schemas in the bundled instance that do not belong to the Cognos content store.
• Application connections to the instance from systems other than Cognos.
• The bundled Db2 surviving after Cognos is decommissioned and running on its own.
• Reporting or ETL jobs reading directly from the content store database.

How to defend the position

Start from the Cognos License Information document, because it defines what the bundled grant actually allows. Then map every schema and connection in the instance. A large share of what an auditor flags is genuine content store activity, supported Cognos function, or administration that sits inside the grant. Only true out of scope use belongs in the finding, and even then the question moves to audit negotiation, where the residual is reduced and future terms protected.