Switching to the New Log File Management

The Db2 LUW Admin Tools, which provide a log file management for Db2 LUW, are no longer supported with SAP NetWeaver 7.0. Starting with version 8.2 of the database, Db2 LUW has a built-in log file management. For more information about Db2 LUW’s log file management, see the document IBM Db2 for Linux, UNIX, and Windows: New Log File Management.

Enabling Log Archiving

If you did not enable log archiving for the database during the update, you have to enable it now according to the description in the document IBM Db2 for Linux, UNIX, and Windows: New Log File Management.

Backing Up the Database

Perform a full backup of the database.

Deleting Substitution Tablespaces

After the update, some tablespaces are no longer used and you can delete them.

To determine the names of these empty substitution tablespaces of the source release, enter the following db2 clp command:

Release upgrade only:

db2 "select tbspace from syscat.tablespaces TS where TS.tbspace like '%E%<source rel>%' and not exists ( select 1 from syscat.tables where tbspace = TS.tbspace or index_tbspace = TS.tbspace or long_tbspace = TS.tbspace )"

SPS update:

db2 "select tbspace from syscat.tablespaces TS where TS.tbspace like '%E%<rel>%' and not exists ( select 1 from syscat.tables where tbspace = TS.tbspace or index_tbspace = TS.tbspace or long_tbspace = TS.tbspace )"

To delete all obsolete tablespaces that are returned by the above mentioned db2 clp command, enter the following db2 clp command at the operating system level for each tablespace listed:

db2 drop tablespace <tablespace name>

Db2 LUW checks whether there are still database objects in the specified tablespace before it executes this command. If there are, the command is not executed.

Cleanup of Obsolete RUNSTATS Jobs

1. Log on to the SAP system.

   You require the authorizations for database administration and background jobs.

2. Call transaction DB13.

3. Select the currently planned actions.

   • Check Tables for Statistics Update

   • RUNSTATS and REORGCHK (DBSTATC)

   • RUNSTATS and REORGCHK for all Tables

4. Choose Delete to delete all selected actions.

Scheduling REORGCHK Jobs

1. Log on to the SAP system.

   You require the authorizations for database administration and background jobs.

2. Call transaction DB13.

3. Choose Pattern Setup.

   Several defined database actions appear.

4. Choose the action REORGCHK for all Tables.

5. To page through the descriptions of the selected actions, choose Next, and enter a start time for each one. Select times when the system is running, but with a low load.

6. Save your entries.

Depending on your Db2 version and SAP BW release and support package, BLU Acceleration might be enabled automatically in the NLS database after an update of your SAP BW system. However, although BLU Acceleration might be advisable under certain circumstances, it requires that your NLS system meets certain hardware and software requirements.