6 Creating DB2 databases for object tables and directories

Sample jobs for creating databases are provided in SAMPLIB to help install OAM. These sample jobs help you create the DB2 databases, create the application plans, grant authority to use the application plans, and access the databases. Before running the sample jobs, you must:

Change the JOB statement to meet your installation’s requirements.
Verify that the user ID that is specified on the JOB statement has the correct authority to perform the requested operations.
Add a JOBLIB for the appropriate DSNLOAD if it is not in the linklist.
Verify that the subsystem name specified with the SYSTEM keyword on the DSN command is the name of your DB2 subsystem.
Change the plan name on the RUN statement to match your current DB2 version and release level.
Start DB2.

If you choose to have SMS manage your DB2 VSAM data sets, create an ACS routine for the VSAM DB2 allocations. Enable the Object and or the Object Backup storage group, enable the volumes, and then validate and activate the SCDS.

Note: When planning for larger data object support (greater than 50MB) keep in mind that:

If large object support (LOB) is not enabled, objects larger than 32640 bytes and less than or equal to 256 MB are stored in multiple rows in the 32 KB DB2 table. For example, a 256 MB object takes more than 8000 rows to store in the 32 KB table. You might have to increase the number of DB2 locks specified (per user and table space) in order to prevent lock escalations and timeouts. Ensure that the tables used to store the larger objects have the required capacity.
If LOB is enabled, objects larger than 32640 bytes are stored directly into DB2 in a LOB column with each BLOB as a varying length string up to the OAM maximum object size of 2000 MB.
Objects greater than 256 MB require LOB to be enabled.