07.02.2013 Views

Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Checks under z/<strong>OS</strong> and <strong>DB2</strong><br />

We recommend the following setup and checks at z/<strong>OS</strong> and <strong>DB2</strong> level:<br />

► Workload monitor<br />

► Stored procedures<br />

► <strong>DB2</strong> bufferpool<br />

Installation of stored procedure <strong>SAP</strong>CL<br />

Starting with NetWeaver 2004s, a new stored procedure, <strong>SAP</strong>CL, is used to<br />

collect <strong>DB2</strong> per<strong>for</strong>mance data from the Instrumentation Facility Interface (IFI). In<br />

previous releases, this function was provided by rfcoscol.<br />

Stored procedure <strong>SAP</strong>CL is available from the <strong>SAP</strong> Marketplace Web site as<br />

part of z/<strong>OS</strong> 64 bit kernel.<br />

Also, since NetWeaver 2004s, CCMS corrections are delivered as part of <strong>SAP</strong><br />

Basis Support Package and not with specific transports (see 427748).<br />

It is important to keep the system updated with the latest support packages in<br />

order to have all IFI monitor functions work.<br />

We downloaded <strong>SAP</strong>CAR and <strong>SAP</strong><strong>DB2</strong>CL from the <strong>SAP</strong> Marketplace. To make<br />

<strong>SAP</strong>CAR work, we set the correct TAGs <strong>for</strong> automatic conversion with the<br />

following chtag command:<br />

SC04:/SC04/sap/appo>chtag -t -c iso8859-1 -R <strong>SAP</strong>CAR<br />

After this command, we verified the correct tag:<br />

SC04:/SC04/sap/appo>ls -T<br />

t ISO8859-1 T=on <strong>SAP</strong>CAR<br />

So we could unpack the <strong>SAP</strong><strong>DB2</strong>CL package that contained the following files:<br />

► sapdb2cl, the stored procedure executable<br />

► DBRM.db2cldb, the database request module<br />

We then per<strong>for</strong>med the installation of <strong>SAP</strong>CL from an <strong>SAP</strong> GUI.<br />

We ensured that the <strong>SAP</strong> GUI user installing <strong>SAP</strong>CL had the authorizations and<br />

permissions described in the “Permissions, Privileges and Authorizations <strong>for</strong><br />

<strong>SAP</strong>CL” section of the <strong>SAP</strong> Database Guide.<br />

318 <strong>Best</strong> <strong>Practices</strong> <strong>for</strong> <strong>SAP</strong> <strong>BI</strong> <strong>using</strong> <strong>DB2</strong> 9 <strong>for</strong> z/<strong>OS</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!