Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Recover for Db2 13.1.

Determining unloaded keys file space requirements

Use the following information to help estimate the size to allocate for unloaded keys files. Your RUNSTATS must be current, or you must use your own row estimate.

Multiply the number of rows in the table space by the record length to get the bytes needed by BMC AMI Recover, as follows:

Size = NR * RL

In the equation, the variables are defined as follows:

  • Size is bytes in unloaded keys file.
  • NR is the number of rows given by the value of CARD from the SYSIBM.SYSTABLEPART table.
  • RL is the record length displayed in message BMC40806 LENGTH OF RECORDS=length. This message prints in the BMC AMI Recover plan when SKEYDDN is specified and can be obtained from an ANALYZE ONLY job. This length is the maximum key size involved plus six or seven bytes. (For more details, see Determining-sort-work-space-requirements.)

For unloaded keys files, all partitions in a run are added together.

Related topic

Building-BMC-AMI-Recover-jobs



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*