Online Tutorials & Training Materials | STechies.com
Register Login
Advertisement

Error analysis for client copy

|| 0

Error analysis for client copy
Stechies

A client copy terminates for no apparent reason. The client copy programs do not copy all tables.

Solution

The data that is necessary for error analysis is described here; this Note also explains how you can find the error yourself.

The name prefixes of the Notes of the client copy tools follow the following scheme:

  • CC-RELEASE - You should first refer to the Note applying to your release.
  • CC-TOPIC - These Notes provide information and detail problems in the various areas (e.g. addresses, remote copy, client transport...).
  • CC-INFO and CC-ADMIN - These Notes contain information which help you to plan a copy and to avoid errors.
  • CC-ERROR - These Notes deal with individual errors and how to solve them.

1. If you cannot find any suitable Note or solve the problem yourself, we require the following information (please do not copy larger protocols into the message. Instead, provide them, if requested, on sapservX as described inDocument 40024):

a) What type of client copy you want to execute (local copy, remote copy, client transport or copy according to transport request)?
b) Which copy profile are you using (SAP_ALL, SAP_USER, SAP_CUST ...)?
c) The protocols (transaction SCC3)
The final status of the copy, e.g. "ended with errors".
The protocol combination of the copy - approximately one to two screen pages, in particular also any copying errors.

Error messages in the log file (file log) of the copy. Error messages can be found more easily when the log is expanded to level 2 only.
Other warnings and messages for the tables where errors occur. Expand the log completely and search for the table names.
You can save the protocol file itself via

'Details -> File protocol', 'Expand everything', 'Protocol -> Save in PC file...', selection 'unconverted'.

Logon in English or German, the protocol is saved in the language in which you logon.

d) The relevant part of the system log documenting the termination from the run-time environment point of view (Transaction SM21). For the selection criteria, use (e.g. in the event of a termination) the last entry in the log of the client copy as the start value (note that the termination can occur hours or even days after the last entry) or use the period in which the problems occurred.

You should select the central SysLog (via 'SysLog -> Select'), if it is set up. Otherwise, all SysLogs where a process was active have to be taken into account. In the case of remote copies, you must also take the source system into account (usually time-outs).

e) If there is a short dump (Transaction ST22) with the termination, add the most important keywords and the code statement. If required, the entire DUMP can be put on sapservX.

f) Which transport request (<sid>KTnnn) was used for an export/import? Using SE01 check the status of the transport request (<sid>KTnnn and <sid>KOnnn; <sid>represents the source system). You should particularly observe Document 70547.

g) If the client copy is scheduled as a background job, check job management SMX/SM37 and spool SP02/SP01. If there were problems writing the log, the missing information can be found in the spool.

2. Copying phase (log SCC3):

The last entered phase indicates the step where the program terminated:

a) Analysis phase (up to 3.0F Phase A?):

Program terminated during initialization. If there is no system error, the cause is contained in the log.

b) Copy phase (up to 3.0F Phase C?):

  • The terminated tables can be found in the log.
  • Check this with Transaction SE11. Choose the database utility from the utilities menu (->SE14). Here you can test the database consistency by using 'check'.
  • Check the size of the tables by using SE16, Note 118823 or Report 'NROWS' (as of Release 4.0B).
  • Analyze the system log message (SM21):
  • Timeout: The customer should either start the job in the background and/or increase the maximum runtime (max_wprun_time).
  • INTTAB error: Does not cause a termination. (Up to 3.0E: tables which are larger than 10,000 bytes cannot be copied).
  • SQL error: Correct the problem in the database and restart the copy. Pay particular attention to Note 96296.

c) Subsequent processing phase (up to 3.0F Phase N?):

The currently executed exit program which caused the error is located in the log. Send an error message to the component which is responsible for this module so that you can receive the quickest help possible.

3. In order to compare table contents between two clients or even between two systems, there are comparative tools from the customizing area (also see Note 91096). Create an R3 RFC destination in Transaction SM59.

4. Database table CCSELTAB has been available since Release 4.6. The selected tables are logged in this table. After doing a client copy, you can use

Transaction SE16 and selection CCSELTAB-STATUS <> 'P' to find out which tables have not yet been successfully processed. Here the STATUS and error message (CCSELTAB-ARBGB and CCSELTAB-MSGNR) are important.          

This table however only exists temporarily. It only ever contains the data of the last client copy (also test runs).



 


Advertisement
Advertisement
Advertisement