Sapnote_0000022514 - CC-InFO Error Analysis for Client Copy

7/28/2019 Sapnote_0000022514 - CC-InFO Error Analysis for Client Copy

http://slidepdf.com/reader/full/sapnote0000022514-cc-info-error-analysis-for-client-copy 1/5

17.12.2012 Page 1 of 5

SAP Note 22514 - CC-INFO: Error analysis for client copy

Note Language: English Version: 31 Validity: Valid Since 15.10.2001

Summary

Symptom

A client copy terminates for no apparent reason.

The client copy programs do not copy all tables.

Additional key words

SCC0, SCC1, SCC2, SCC5, SCC7, SCC8, SCC9, SCCL, RSCLICOP, RSCCPROT

Cause and prerequisites

The error has not been classified yet.

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:

o CC-RELEASE - You should first refer to the Note applying to your

release.

o CC-TOPIC - These Notes provide information and detail problems on

the various areas (e.g. adresses, remote copy, clienttransport...).

o CC-INFO and CC-ADMIN - These Notes contain information which help

you to plan a copy and to avoid errors.

o 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 in Note 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



17.12.2012 Page 2 of 5


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 thelast 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 sourcesystem 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 Note 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 programterminated:

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



17.12.2012 Page 3 of 5


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).

In addition, you should regard the related notes.

Header Data

Release Status: Released for Customer

Released on: 14.10.2001 22:00:00

Master Language: German

Priority: Recommendations/additional info

Category: Help for error analysis

Primary Component: BC-CTS-CCO Client Copy (For ByD issues select

BC-TLM-CP)

The Note is release-independent



17.12.2012 Page 4 of 5


Related Notes

Number Short Text

634620 CC-TOPIC: Error in the client transport as of WAS 6.10

613872 Oracle traces with ORADEBUG

572139 CC-INFO: Client copy hangs with a certain table

557132 CC-TOPIC: Remote client copy

552711 FAQ: Client copy

495911 Trace analysis for logon problems

491923 CC RELEASE: Client copy errors in Release 6.20

489690 CC INFO: Copying large production clients

446485 CC-ADMIN: Special copying options

446294 CC INFO: Logical system name and client copy

442415 Inconsistent table BDCP --> client-specific change pointer

432152 CC-RELEASE: Error in client copy in Release 6.10390317 VA02: Double/incorrect planned revenues after client copy

365304 CC-ADMIN: Reports for deleting tables

355713 CC-TOPIC: User masters during client copy

350189 CC-TOPIC: Error messages, client copy terminations

350101 CC-TOPIC: Client copy and addresses up to 4.6D

339932 Termination with invalid BCD number in developer trace

338578 CC-TOPIC: Error in client transport as of 4.5

304605 SAP query: Queries missing after client copy

211492 Inconsistency between ABAP Dictionary <-> database

206523 CC-RELEASE: Client copy errors in 4.6C and 4.6D

192494 CC-TOPIC: Copy logs (SCC3)

191660 CC-ERROR: No authorization for client copy

180949 CC-INFO: Change documents for a client copy

161495 CC-RELEASE: Error in client copy in 4.6A and 4.6B

147537 CC RELEASE: Error in client copy in Release 4.5B

139418 Logging user actions

130540 CC-TOPIC: Client copy and addresses in 4.0B

126619 CC RELEASE: Error in client copy in Release 4.0B

125032 Search for corrupted texts in cluster table STXL

118823 CC-ADMIN: Size of a client

116787 CC-TOPIC: Remote client copy

99502 CC-RELEASE: SCC1 in Release 4.0B

96296 CC-ERROR: Database problem in client copy

91980 Missing output of RFC short dump after login error

91096 Table Compare: Info about Cust. Cross System Check

89384 Checking cluster tables with R3check

85193 Invalid name for TemSe object/syslog message F3T

83819 DB6: Collecting support data

73779 AS/400: Problems during client transport R3trans

70547 CC-TOPIC: Client transport



17.12.2012 Page 5 of 5


Number Short Text

70290 CC-INFO: Excluding tables with 'RSCCEXPT'

69556 CC-TOPIC: Missing tables and data

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

68048 Deactivating the automatic SAP* user

67205 CC-INFO: Copying large and productive clients

49023 AS/400: Client Copy

48400 Reorganization of TemSe and Spool

47502 CC-REMOTE: Messages of the Remote Clientcopy

42870 CC-ADMIN: Periodic scheduling does not work

41839 CC-TOPIC: User masters and client copies until 4.0

37104 Error analysis: Background processing system

33873 What do the semaphores mean?

24853 CC-INFO: Client copy, functionality

19574 CC-ADMIN: Controlling data selection during client copy

15374 Checklist: Performance analysis

6975 Validierung/Substitution/rules - utility reports

2857 What table delivery classes are there? What is their signifi

Attributes

Attribute Value

Transaction codes HIER

Transaction codes SCC1






Transaction codes SCCL

Transaction codes SE01




Transaction codes SM21

Transaction codes SM59

Transaction codes ST22

Documents

Sapnote_0000022514 - CC-InFO Error Analysis for Client Copy