SAP Note 460268 - Could not find stored procedure

Note 35415 - CC-TOPIC: Memory space analysis / Test run

Header

Version / Date 98 / 2005-05-20

Priority Correction with low priority

Category Program error

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

Secondary Components

Summary

Symptom

1. A termination with 'Integer overflow during addition'. COMPUTE_INT_TIMES_OVERFLOWor due to runtime overrun occurs (TIME-OUT).

2. Up to Release 3.1H: 'Resource analysis' returns reserved memory space instead of free memory space.

3. The memory space calculated is larger than actually needed.

4. The database analysis tools return different values to the client copy.

5. A timeout occurs in the resource analysis.

6. An export test run returns errors in the log. For example 'Transport program tp could not be started'.

7. At the end of a file log, the following values are too small, if parallel processes (as of Release 4.6) were used:   TA 021   Selected objects          :  TA 022   Processed objects        :   TA 172   Deleted tables            :  TA 026   Memory requirement in KB  :

8. In a remote copy, the messages of the previous item are missing completely.

Other terms COMPUTE_INT_TIMES_OVERFLOW, COMPUTE_INT_PLUS_OVERFLOW

SCCR_CHECK_TABLESPACE_ORACLE, SCC1, SAPMSCC1, SAPLSCCR, DBIF_DSQL2_SQL_ERROR, RSCCPROT, TABLESPACE, RESOURCENCHECK, RESOURCENANALYSE, SCC8, , LSCCRU08, LSCCRU09, LSCCAU05, LSCCAU06

Reason and Prerequisites

1. The problem has several causes:

a) The test run is started online

b) As of Release 3.0F, the error may also occur in the log (Transaction SCC3) during the database analysis (resources analysis) of a test run.

2. The problem is known under Oracle (up to Release 3.1H):

              If you choose function 'Resource analysis', the system does not display the free tablespace but the filled space.

3. There are several causes of a too high estimation:

a) There is no possibility to determine the range of the free storage in the extents of existing tables. Therefore, for every table copied, the number of required extents is calculated as if all existing tables were full. This may cause considerable differences between the forecasted memory requirement and the actual requirement. The difference is especially large if deletions were made in the target system (not only in the target client). In particular, if, for example, a complete client was

SAP Note 460268 - Could not find stored procedure

Summary

only deleted a short time ago. In this case, contrary to what the test run states, it is often so that next to no memory is required.

b) Particularly great is the difference with database POOLs and CLUSTER. The extents for POOLs and CLUSTER are very large in general. For every table in the pool/cluster only at least one extent each is estimated as required storage. Examples are POOL ATAB or CLUSTERs RFBLG and AABLG.

c) There is a program error in the function moduels for ORACLE and INFORMIX.

4. The following points are known:

a) There is no precise number for a database´s useable free memory space. The client copier uses the tools of the databases for analysis. On the other hand, for example, DB02 uses separate algorithms. The result is an estimation in each case.

                       If 'Resource analysis' displays sufficient memory, you may then assume that this is correct.

b) With Informix databases on NT and AIX systems, 'Resource analysis' only returns half of the memory that is actually available.

c) For ORACLE and INFORMIX the values for some database areas are too high.

5. The resource analysis may need more than the allowed online time.

6. A test run is not supported by transport tools.

7. The values are added up in local variables. The information from the parallel processes are lost, i.e. only tables copied by the main process were taken into account.

8. The information is not displayed with remote copies.

Solution

To increase the reliability of the resource analysis, you can generally recommend the installation/change of the programs related to the note. In this case, you should note the necessity of using upper case letters in the areas between   'EXEC SQL.' and 'ENDEXEC.'Also, no comments are permitted in these areas.

As of Release 4.0B, only preliminary correction 228745 resp. 236071 for ORACLE and INFORMIX is required. The correction is included in the following (Basis) Support Packages:    SAPKH40B63 ; SAPKH45B42 ; SAPKB46B30 ; SAPKB46C21 ; SAPKB46D10Replace the coding of function modules    SCCR_CHECK_TABLESPACE_INFORMIX   SCCR_CHECK_TABLESPACE_ORACLEcompletely by the coding from the corresponding correction instructions.

1. COMPUTE_INT_TIMES_OVERFLOW / TIME-OUT

a) Schedule the test run in the background.

b) The preliminary corrections solve both problems. If the resource analysis terminates with a timeout despite of the preliminary correction, increase parameter (using Transaction RZ11 as of Release 4.6 without restarting the system):    rdisp/max_wprun_time

2. Replace function module SCCR_CHECK_TABLESPACE_ORACLE according to the accompanying source code. In Release 3.1x, you must also change module LSCC1U11.

3. The memory space calculated is too large

a) There is no known solution.

b) There is no known solution.

c) Replace function module SCCR_CHECK_TABLESPACE_INFORMIX resp. SCCR_CHECK_TABLESPACE_ORACLE according to the accompanying source code.

SAP Note 460268 - Could not find stored procedure

Summary

4. The database tools return different values to those of the client copy.

a) There is no known solution or no solutions required.

b) Replace function module SCCR_CHECK_TABLESPACE_INFORMIX according to the accompanying source code.

c) Replace function module SCCR_CHECK_TABLESPACE_INFORMIX resp. SCCR_CHECK_TABLESPACE_ORACLE according to the accompanying source code.

5. Change the modules according to the accompanying source code for your Release.

              If this is not sufficient, increase the following parameter (using Transaction RZ11 as of Release 4.6 without restarting the system):    rdisp/max_wprun_time

6. Since a test run for a client export yields no useful result, the use of this function is not recommended. Instead use Transaction DB02 or the reports from Note 118823.

              The errors can be ignored.

7. If these values are required, you must not use parallel processes in a test run.

8. Implementing preliminary correction 225123 creates these messages.

Affected Releases

Software Component Release From Release To Release And subsequent

SAP_APPL 30 300 31I X

SAP_APPL 40 40A 40B X

SAP_APPL 45 45A 45B X

SAP_APPL 46 46A 46B X

SAP_APPL 46C 46C 46C

SAP_BASIS 46 46A 46D X

Correction delivered in Support Package

Support Packages Release Package Name

SAP_APPL 40B SAPKH40B63

SAP_APPL 45B SAPKH45B42

SAP_BASIS 46B SAPKB46B29

SAP_BASIS 46B SAPKB46B30

SAP_BASIS 46C SAPKB46C20

SAP_BASIS 46C SAPKB46C21

SAP_BASIS 46D SAPKB46D10

Related Notes

659487 CC-ERROR: Resource analysis terminates on ORACLE

350189 CC-TOPIC: Error messages, client copy terminations

118823 CC-ADMIN: Size of a client

69444 CC-TOPIC: Error messages/terminations up to 4.0B

SAP Note 460268 - Could not find stored procedure

Related Notes

69064 CC-RELEASE: Client copy in 3.0F

60233 Oracle rollback segments, more information.

42290 CC-INFO: Space estimate too high

24853 CC-INFO: Client copy, functionality

3155 Termination due to tablespace overflow

- See more at: http://stechno.net/sap-notes.html?view=sapnote&id=35415#sthash.n1Hwhdu4.dpuf