SAP Note 460268 - Could not find stored procedure

118823 - CC-ADMIN Size of a client

Header

Version / Date 44 / 2005-10-27

Priority Recommendations/additional info

Category Installation information

Primary Component BC-CTS-CCO Client Copy (For ByD issues select BC-TLM-CP)

Secondary Components

Summary

Symptom

To be able to schedule client copies and also for system planning, the size of clients or tables in a client is required.

Reason and Prerequisites

In productive environments some tables can become very large. This is important both for performance planning and for system planning.

Solution

For local client copies or remote copies you can carry out a tablespace analysis in the log after a test run. This analysis estimates the memory space required. For the latest information refer to Note 35415.

Depending on the release, typical Customizing clients have the following sizes:           3.0: approx. 150 - 200 MB3.1: approx. 200 - 250 MB4.0: approx. 350 - 400 MB4.5: approx. 450 - 500 MB4.6: approx. 150 - 1500 MB *     * depending on the components of mySAP.com applied

Production clients with application data can of course be considerably larger.

The following reports shall help you to estimate the memory requirements of a client. However, you must know that there is no 'optimal' memory requirement for a client on the database. Each tool uses its own estimation that occasionally leads to very different results (for more information, refer to point 3 of Note 35415). In any case it is recommended that you also use the tools of the database or of Transaction DB02 to be able to evaluate the estimations.

You also need to consider that for client copies into an already existing client, you can only partly calculate the memory requirements of the new client with the existing size of the client (for more information refer to point 2 of Note 70643).

The reports have a problem in principle with tables that are not stored transparently, but as POOL or CLUSTER tables. This data is heavily compressed, and the results of the reports are clearly too high as a result. The tables in question are mostly found in areas of the database that have corresponding names, such as PSAPCLUD or PSAPPOOLD and so on. Examples are: POOL table ATAB, CLUSTER tables RFBLG and AABLG.

For information about the table category, go to the ABAP dictionary (Transaction SE11). As of Release WebAS 6.20, the table category of the respective table is specified in the output list of RSTABLESIZE. You can use this to sort and

SAP Note 460268 - Could not find stored procedure

Summary

filter the data accordingly.

As of Release WebAS 6.20, reports RSSPACECHECK and RSTABLESIZE give you the option of replacing the CLUSTER tables with the CLUSTER. This takes the compression into account. (This is in accordance with the behavior of the client copy. Therefore, as of Release 4.6, you should carry out a client copy test run in another client in the system to analyze the system resources, instead of using report YKSPACEC. You would then have the option of carrying out an analysis of the areas of the database in the log display (Transaction SCC3)).

You can decide the size of individual tables in a client with the enclosed report YSTABSIZ as of Release 4.0. For Release 3.x, there is the equivalent program ZSTABSIZ. As from Basis Release 6.10, you can use report RSTABLESIZE as delivered.

           Both the table name and the client can be entered generically. Thus, you can determine the distribution of a client with the table name '*' and the distribution of one table to different clients by entering the table name and the client '*'.

           Furthermore, it is possible to exclude tables of delivery classes 'L' and 'A' from the selection.

           The report delivers the number of the entries in table, the table width and the memory requirement in bytes. In this case, the memory requirement is the result of the maximum row width and the number of rows. The value might differ considerably from the needed memory requirements if the table entries are on average considerably smaller than the maximum width. Also, the results might be affected if a compression is used.

To calculate the memory requirement in a subdivided manner by database areas, use the attached program YKSPACEC. As of Basis Release 6.10, you can use report RSSPACECHECK as delivered. However, these reports run only on databases with database areas (INFORMIX, ORACLE, ADABAS and DB2/CS), i.e. not with DB2/400.

           For ORACLE and INFORMIX, please make sure that you have implemented advance correction 228745 from Note 35415.

           The report delivers the memory requirement of the tables in the database areas affected and the free space in the database areas in KByte. Depending on the database used, this is a more or less exact estimation of the memory actually used in the respective database areas.

Affected Releases

Software Component Release From

Release To Release And subsequent

SAP_APPL 30 300 31I

SAP_APPL 40 40A 40B

SAP_APPL 45 45A 45B

SAP_APPL 46 46A 46B

SAP_APPL 46C 46C 46C

SAP_BASIS 46 46A 46D

SAP_BASIS 60 610 640 X

Related Notes

666061 FAQ: Database objects, segments and extents

659487 CC-ERROR: Resource analysis terminates on ORACLE

592393 FAQ: Oracle

SAP Note 460268 - Could not find stored procedure

Related Notes

552711 FAQ: Client copy

489690 CC INFO: Copying large production clients

355771 Oracle: Explanation of the new tablespace layout

113675 Collec.note preconf.line of bus. sys. Automotive-A

67205 CC-INFO: Copying large and productive clients

35415 CC-TOPIC: Memory space analysis / Test run

24853 CC-INFO: Client copy, functionality