Client Copy space assumption/calculation

I have a ECC 6.0 Dev box ( oracle DB), I installed the EHP4 from EHP ready system with free disk space 128 GB out of 400 GB disk ( Orcacle + SAP DATA FILES) . I want to have 4 clients on this server in total and i need to create 2 more client now, how can i calculate that this 128 GB space would be sufficient enough for these clients. Any way we can calculate and plan accordingly .
Please advice.
Regards
Edited by: indian tiger on Jun 25, 2010 9:20 PM

Hi,
Could you go through the following Note:-
SAP Note 118823 - CC-ADMIN: Size of a client
cheers !
PRADi

Similar Messages

Client Copy and System Restore query

Dear All,
I have few major doubt regarding client copy and system restor.
1. In my Quality system there are 2 clients: 100 and 200.In my PRD there is only 1 client 300(other than the standard default clients). My doubt is during remote client copy with SAP_ALL profile from PRD to QUA why the space increases only in MB.
I have been asked the same question by my management. They are saying PRD is 300GB and QUA is 220GB then why the space increases in MB though all data is copied in client 200(QUA) from client300(PRD)
2. If I delete client why the space is released in MB. Because according to them it should be in GBs.
3. Now my third query is I have to restore PRD backup in QUA.So I said that this requires same <SID> and Same sapce in the sapdatafiles(OS is HP-UX 11.31 and DB is Oracle 10g).So I have to explain them why these two things are contradary to each other. In case of client copy space required is only in MB and in case of System restore of PRD in QUA sapce require is in GBs.
Your suggestions will be highly obliged.
Regards,
PG

1. In my Quality system there are 2 clients: 100 and 200.In my PRD there is only 1 client 300(other than the standard default clients). My doubt is during remote client copy with SAP_ALL profile from PRD to QUA why the space increases only in MB.
Response > Because during client copy your customizing and other objects are copied.
The database structures,tables etc are already present.
2. If I delete client why the space is released in MB. Because according to them it should be in GBs.
Response > Since client deletion is not same as deleting database /customizing tables .If you delete complete dataspaces/tables then there will be sizeable difference.Similar logic as Response 1
3. Now my third query is I have to restore PRD backup in QUA.So I said that this requires same <SID> and Same sapce in the sapdatafiles(OS is HP-UX 11.31 and DB is Oracle 10g).So I have to explain them why these two things are contradary to each other. In case of client copy space required is only in MB and in case of System restore of PRD in QUA sapce require is in GBs.
Response > Since in a system copy you will copy data files (which includes tables,and all otehr strucutres ) hence the size required will be similar to PRD.

How much space does client copy of ECC6 IDES client 800 requires

Hello
Does anyone knows how much space does client copy of ECC6 IDES client 800 requires?

But I do not have enaugh disk capacity at the moment. So I ned to order it
You donot have to perform the client copy actually . You have to just run the test, it will not consume any disk, probably some archive files will be generated
Regards,
Subhash

As much as the space in HD is necessary to be able to make a Client Copy??

Hi everybody!!
As much as the space in HD is necessary to be able to make a Client Copy??
After the installation, the still servant with approximately 11 GB of free space in C (Total 30 GB) and around 100 free GB in E (Total 190 GB) , in E installed SAP himself ECC6 along with the data base ( Oracle 10,0,2 ), when all tag aiming at the record E did installation itself, but in a minute to make the Client Copy he remains without space in the Drive C (38,3 MB Free)
The Client Copy is for the "Client 300 Test", the Client Copy in DEV with 3 Client ( 100 DEV, 120 QA DEV, 130 Sandbox ) it could come true trouble-free
thanks
Edited by: Manuel Sandoval on Aug 18, 2008 7:16 PM
Edited by: Manuel Sandoval on Aug 18, 2008 7:20 PM

Where do the "Client Copy" goes down the process in reviewing the "TCode ST22" I find the following:
Runtime Errors         DBIF_SETG_SQL_ERROR
Date and Time          19.08.2008 06:21:19
Short text
     SQL error occurred when accessing table.
What can you do?
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
How to correct the error
     Database error text........: "ORA-03106: fatal two-task communication protocol
      error"
     Internal call code.........: "[SETG/GET /INDX_HIER ]"
     Please check the entries in the system log (Transaction SM21).
     If the error occures in a non-modified SAP program, you may be able to
     find an interim solution in an SAP Note.
     If you have access to SAP Notes, carry out a search with the following
     keywords:
     "DBIF_SETG_SQL_ERROR" " "
     "SAPLSHI2" or "LSHI2U25"
     "STREE_READ_BUFFERED_DATA_GENER"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
System environment
    SAP-Release 700
    Application server... "mts-qua"
    Network address...... "192.168.1.48"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x Intel 80686"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "MTS-QUA"
    Database type..... "ORACLE"
    Database name..... "ECQ"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "May 22 2007 00:14:27"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "OCI_10201_SHARE (10.2.0.1.0) "
    Patch level. 111
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
     NT 6.0"
    Memory consumption
    Roll.... 8176
    EM...... 2090448
    Heap.... 0
    Page.... 16384
    MM Used. 1943008
    MM Free. 145920
User and Transaction
    Client.............. 300
    User................ "SAP*"
    Language key........ "E"
    Transaction......... " "
    Program............. "SAPLSHI2"
    Screen.............. "SAPLSMTR_NAVIGATION 0100"
    Screen line......... 2
Information on where terminated
    Termination occurred in the ABAP program "SAPLSHI2" - in
     "STREE_READ_BUFFERED_DATA_GENER".
    The main program was "SAPLSMTR_NAVIGATION ".
    In the source code you have the termination point in line 57
    of the (Include) program "LSHI2U25".
Source Code Extract
Line SourceCde
   27             DO_NOT_READ_DEVCLASS       = 'X'
   28        IMPORTING
   29 *          MESSAGE          =
   30             STRUCTURE_HEADER = STRUCTURE_HEADER
   31        EXCEPTIONS
   32             OTHERS           = 0.
   33 *
   34   READ TABLE BUFFER_DATA WITH KEY TREE_ID = STRUCTURE_ID.
   35   MODIFY_INDEX = SY-TABIX.
   36 *
   37   IF NOT STRUCTURE_HEADER-BUFFERVAR CS BUF_NODE.
   38     GET_NODES = FALSE.
   39     BUFFER_DATA-NODES_OK = FALSE.
   40   ENDIF.
   41   IF NOT STRUCTURE_HEADER-BUFFERVAR CS BUF_REF.
   42     GET_REFERENCES = FALSE.
   43     BUFFER_DATA-REFS_OK = FALSE.
   44   ENDIF.
   45   IF NOT STRUCTURE_HEADER-BUFFERVAR CS BUF_TEXT.
   46     GET_TEXTS_LANGUAGE = SPACE.
   47     BUFFER_DATA-TEXT_OK = FALSE.
   48   ENDIF.
   49 *
   50 * get nodes and/or references
   51   IF GET_NODES EQ TRUE OR GET_REFERENCES EQ TRUE.
   52     SELECT SINGLE * FROM TTREELOADS WHERE TREE_ID EQ STRUCTURE_ID.
   53     IF SY-SUBRC EQ 0.
   54       CLEAR BUFFER_NODES. REFRESH BUFFER_NODES.
   55       CLEAR BUFFER_REFS. REFRESH BUFFER_REFS.
   56       IF GET_NODES EQ TRUE AND GET_REFERENCES EQ TRUE.
>>>>>         IMPORT BUFFER_NODES BUFFER_REFS FROM DATABASE INDX_HIER(XX)
   58                                ID STRUCTURE_ID.
   59         BUFFER_DATA-NODES_READ = TRUE.
   60         BUFFER_DATA-REFS_READ = TRUE.
   61       ELSE.
   62         IF GET_NODES EQ TRUE.
   63           IMPORT BUFFER_NODES FROM DATABASE INDX_HIER(XX)
   64                                ID STRUCTURE_ID.
   65           BUFFER_DATA-NODES_READ = TRUE.
   66         ELSEIF GET_REFERENCES EQ TRUE.
   67           IMPORT BUFFER_REFS FROM DATABASE INDX_HIER(XX)
   68                                ID STRUCTURE_ID.
   69           BUFFER_DATA-REFS_READ = TRUE.
   70         ENDIF.
   71       ENDIF.
   72 *     nodes[] = buffer_nodes[].
   73 *     references[] = buffer_refs[].
   74       APPEND LINES OF BUFFER_NODES TO NODES.
   75       APPEND LINES OF BUFFER_REFS TO REFERENCES.
   76     ELSE.
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 1
SY-DBCNT 1
SY-FDPOS 2
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE SAP Easy Access
SY-MSGTY E
SY-MSGID 01
SY-MSGNO 289
SY-MSGV1 SAP*
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080819
SY-UZEIT 062116
SY-XPROG
SY-XFORM
Active Calls/Events
No.   Ty.          Program                             Include                             Line
      Name
   10 FUNCTION     SAPLSHI2                            LSHI2U25                               57
      STREE_READ_BUFFERED_DATA_GENER
    9 FUNCTION     SAPLSHI2                            LSHI2U14                               82
      STREE_READ_TOP_LINE_GENER
    8 FUNCTION     SAPLSHI1                            LSHI1U12                               73
      STREE_STRUCTURE_READ_TOP_NODE
    7 FUNCTION     SAPLSHI1                            LSHI1U14                               47
      STREE_STRUCTURE_READ_N_TOP_LEV
    6 FUNCTION     SAPLSHI6                            LSHI6U08                               38
      STREE_HIERARCHY_READ
    5 FUNCTION     SAPLSMNU_NEW                        LSMNU_NEWU02                          130
      MENU_GET_MENU_TREE_PART
    4 FUNCTION     SAPLSMTR_NAVIGATION_MODULES         LSMTR_NAVIGATION_MODULESU01           140
      NAVIGATION_LOAD_MENU_DATA
    3 FORM         SAPLSMTR_NAVIGATION                 LSMTR_NAVIGATIONF11                    14
      HELP_FORM_LOAD_ALL
    2 FORM         SAPLSMTR_NAVIGATION                 LSMTR_NAVIGATIONF0I                   511
      CONTROL_INITIALIZE_TREE
    1 MODULE (PBO) SAPLSMTR_NAVIGATION                 LSMTR_NAVIGATIONO01                    10
      STATUS_0100
Chosen variables
Name
    Val.
No.      10 Ty.          FUNCTION
Name STREE_READ_BUFFERED_DATA_GENER
GET_NODES
    X
    5
    8
    0
    0
GET_REFERENCES
    X
    5
    8
    0
    0
GET_TEXTS_LANGUAGE
    2
    0
    0
    0
STRUCTURE_ID
    S000
    53332222222222222222222222222222
    30000000000000000000000000000000
    00000000000000000000000000000000
    00000000000000000000000000000000
NODES[]
    Table IT_235[0x1102]
    \FUNCTION=STREE_READ_TOP_LINE_GENER\DATA=INEXTLEVEL[]
    Table reference: 44
    TABH+ 0(20) = 00000000800EC451000000002C000000EB000000
    TABH+ 20(20) = 000000004E040000FFFFFFFF046C0000F0080000
    TABH+ 40( 8) = 08000000C1248001
    store        = 0x00000000
    ext1         = 0x800EC451
    shmId        = 0     (0x00000000)
    id           = 44    (0x2C000000)
    label        = 235   (0xEB000000)
    fill         = 0     (0x00000000)
    leng         = 1102 (0x4E040000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000033
    occu         = 8     (0x08000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0x30F6BC51
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC013B251
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
REFERENCES[]
    Table IT_236[0x516]
    \FUNCTION=STREE_READ_TOP_LINE_GENER\DATA=REFERENCES[]
    Table reference: 45
    TABH+ 0(20) = 00000000C0F6BC51000000002D000000EC000000
    TABH+ 20(20) = 0000000004020000FFFFFFFF046C000020120000
    TABH+ 40( 8) = 10000000C1248001
    store        = 0x00000000
    ext1         = 0xC0F6BC51
    shmId        = 0     (0x00000000)
    id           = 45    (0x2D000000)
    label        = 236   (0xEC000000)
    fill         = 0     (0x00000000)
    leng         = 516   (0x04020000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000082
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0x78F6BC51
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x0014B251
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
TEXTS[]
    Table[initial]
SY-REPID
    SAPLSHI2
    5454544322222222222222222222222222222222
    310C389200000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
UP_NAME_USER_EXIT_2
    USER_EXIT_2
    5545545455322222222222222
    5352F5894F200000000000000
    0000000000000000000000000
    0000000000000000000000000
REF_TABLE_NAME
    2222222222222222
    0000000000000000
    0000000000000000
    0000000000000000
I_TNODET[]
    Table[initial]
TTREELOADS
    S000                            20060927073108G
    53332222222222222222222222222222333333333333334
    30000000000000000000000000000000200609270731087
    00000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000
NODE_TYPE_STEXT_F_MODULE
    STREE_NODE_TYPE_GET_STEXT_XXXX
    555445444455554544555545555555
    34255FEF45F4905F754F34584F8888
    000000000000000000000000000000
    000000000000000000000000000000
SY-SUBRC
    0
    0000
    0000
BUFFER_NODES
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
BUFFER_NODES[]
    Table[initial]
BUFFER_REFS
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
BUFFER_REFS[]
    Table[initial]
TRUE
    X
    5
    8
    0
    0
SYST-REPID
    SAPLSHI2
    5454544322222222222222222222222222222222
    310C389200000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
INDX_HIER
    XXS000                            ############################################################
    5553332222222222222222222222222222000000000000000000000000000000000000000000000000000000000000
    8830000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
INDX_HIER-CLUSTR
    0
    00
    00
GLOBAL_TREE_REF_TYPE_STXT
    STREE_GET_STEXT_FOR_RTYPE_XXXX
    555445445555455544555555455555
    34255F754F34584F6F2F24905F8888
    000000000000000000000000000000
    000000000000000000000000000000
PROPERTY_OWN_LONGTEXT
    1
    3
    1
    0
    0
NODE_TYPES_WITH_OWN_LONGTEXT[]
    Table[initial]
TRTYPEH
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
    2222
    0000
    0000
    0000
No.       9 Ty.          FUNCTION
Name STREE_READ_TOP_LINE_GENER
DISPLAY_MODE
    D
    4
    4
    0
    0
FILTER_ID
    22222222222222222222222222222222
    00000000000000000000000000000000
    00000000000000000000000000000000
    00000000000000000000000000000000
STRUCTURE_ID
    S000
    53332222222222222222222222222222
    30000000000000000000000000000000
    00000000000000000000000000000000
    00000000000000000000000000000000
TABLE_NAME
    TMENU01
    544453322222222
    4D5E50100000000
    000000000000000
    000000000000000
MESSAGE
                         000
    2222222222222222222223332222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PARENT_NODE
    22222222222222222222222222222222
    00000000000000000000000000000000
    00000000000000000000000000000000
    00000000000000000000000000000000
STRUCTURE_TOP_LINE[]
    Table IT_233[0x1234]
    \FUNCTION=STREE_STRUCTURE_READ_N_TOP_LEV\DATA=STRUCTURE[]
    Table reference: 42
    TABH+ 0(20) = 0000000030F1C151000000002A000000E9000000
    TABH+ 20(20) = 00000000D2040000FFFFFFFF04640000900E0000
    TABH+ 40( 8) = 08000000C1248001
    store        = 0x00000000
    ext1         = 0x30F1C151
    shmId        = 0     (0x00000000)
    id           = 42    (0x2A000000)
    label        = 233   (0xE9000000)
    fill         = 0     (0x00000000)
    leng         = 1234 (0xD2040000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000063
    occu         = 8     (0x08000000)
    access       = 1     (ItAccessStandard)

Space requirement for client copy

Hi,
I have installed ECC6.0 IDES (ABAP only) with Oracle DB.
I am trying to perform a client copy with option SAP_CUST
Source Client: 001
Target Client: 010
Can anyone tell me whether I require the same amount of disk space of 001 to perform a successful client copy (to client 010)?
And, if so, how to check how much space is being used by the client 001( database and application)?
Best Regards,
Moulinath
Edited by: Moulinath Ray on Dec 23, 2008 11:58 AM

Hi Moulinath,
The amount of space depends on the amount of data being copied. If you copy the "application data + customising data + user master data", then size will be the same.
Obviously client independent data is not copied.
ou can use RSSPACECHECK to see the amount of space being used.
Kind regards,
hemanth

Unable to create IDOCs after client copy

I'm unable to create IDOCs after a client copy. I receive a SAPSQL_ARRAY_INSERT_DUPREC or insert of duplicate rows ABAP dump.
Does anyone know what how to fix this. Thank you in advance.
Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB
Date and Time          22.10.2007 16:50:51
ShrtText
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLEDI1" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"F09_IDOC_INSERT_WITH_NUMBER" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
"SAPLEDI1" or "LEDI1F09"
"F09_IDOC_INSERT_WITH_NUMBER"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"F09_IDOC_INSERT_WITH_NUMBER"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "auaplxr3q"
Network address.......... "128.197.135.5"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "000B439ED600"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "auaplxr3q"
Database type............ "ORACLE"
Database name............ "Q63"
Database owner........... "SAPR3"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
Created on............... "Mar 22 2007 20:48:46"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "175"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
Roll..................... 16128
EM....................... 4189928
Heap..................... 0
Page..................... 0
MM Used.................. 1469352
MM Free.................. 2718056
SAP Release.............. "640"
User and Transaction
Information on where terminated
The termination occurred in the ABAP program "SAPLEDI1" in
"F09_IDOC_INSERT_WITH_NUMBER".
The main program was "SAPMSSY1 ".
The termination occurred in line 108 of the source code of the (Include)
program "LEDI1F09"
of the source code of program "LEDI1F09" (when calling the editor 1080).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)" but was not handled locally,
not declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLEDI1 ". Its source code starts in line 5
of the (Include) program "LEDI1F09 ".
Source Code Extract
Line
SourceCde
78
perform call_badi tables list_container_insert
79
using control
80
ident.
81
Aufruf des Badi's für das einstreuen neuer Segmente
82
perform call_insert_badi tables list_container_insert
83
using control
84
ident
85
changing maxsegnum.
86
87
   free list_container_insert
88
FREE_RETURN = 1.
89
ELSE. " no other IDoc is open in create-mode
90
LOOP AT LIST_CONTAINER_CREATE WHERE MANDT EQ SY-MANDT
91
AND   DOCNUM EQ IDENT.
92
LIST_CONTAINER_CREATE-DOCNUM = DOCNUM.
93
MODIFY LIST_CONTAINER_CREATE.
94
ADD 1 TO MAXSEGNUM.
95
ENDLOOP.
96
if control-mestyp eq c_mestyp.
97
CALL FUNCTION 'FUNCTION_EXISTS'
98
EXPORTING
99
funcname           = c_func
100
EXCEPTIONS
101
FUNCTION_NOT_EXIST = 1.
102
IF syst-subrc IS INITIAL. "Anwendungssystem
103
perform call_transform
104
tables list_container_create
105
using control.
106
ENDIF.
107
endif.
>>>>>
INSERT EDID4 FROM TABLE LIST_CONTAINER_CREATE.
109
Aufruf des Badi's für das Anwendungsmapping einzelner Felder
110
perform call_badi tables list_container_create
111
using control
112
ident.
113
perform call_insert_badi tables list_container_create
114
using control
115
ident
116
changing maxsegnum.
117
118
free list_container_create
119
FREE_RETURN = 0.
120
ENDIF.
121
122
insert status records
123
124
SYN_ERROR_IN = ' '.
125
CNTR_STATUS = 0.
126
REFRESH LIST_STATUS.
127
CLEAR LIST_STATUS.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
2
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC and RFC Control
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
13 FORM         SAPLEDI1                            LEDI1F09                              108
F09_IDOC_INSERT_WITH_NUMBER
12 FUNCTION     SAPLEDI1                            LEDI1U19                               33
EDI_DOCUMENT_CLOSE_CREATE_TAB
11 FUNCTION     SAPLEDIR                            LEDIRU01                              273
IDOC_INBOUND_WRITE_TO_DB
10 FORM         SAPLEDIN                            LEDINF01                              457
ONE_IDOC_STORE
9 FUNCTION     SAPLEDIN                            LEDINU05                              234
IDOC_INBOUND_ASYNCHRONOUS
8 FORM         SAPLEDIN                            LEDINV05                               19
IDOC_INBOUND_ASYNCHRONOUS
7 FORM         SAPMSSY1                            SAPMSSY1                              254
XAB_RUN_DRIVER
6 FUNCTION     SAPLSXAB                            LSXABU01                                9
RFC_RUN_XAB_DRIVER
5 FUNCTION     SAPLERFC                            LERFCU01                               59
ARFC_EXECUTE
4 FUNCTION     SAPLERFC                            LERFCU02                              229
ARFC_DEST_SHIP
3 FORM         SAPLERFC                            LERFCV02                               28
ARFC_DEST_SHIP
2 FORM         SAPMSSY1                            SAPMSSY1                               69
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
%_RFC_START
Chosen variables
Name
Val.
No.      13 Ty.          FORM
Name F09_IDOC_INSERT_WITH_NUMBER
CONTROL-MESTYP
USERCLONE
554544444222222222222222222222
53523CFE5000000000000000000000
C_MESTYP
FIDCCH
444444222222222222222222222222
694338000000000000000000000000
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
LIST_STATUS-STAPA2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
C_FUNC
IDOC_TRANSFORM
444455544544542222222222222222
94F3F421E36F2D0000000000000000
SYST-REPID
SAPLEDI1
5454444322222222222222222222222222222222
310C549100000000000000000000000000000000
SY-UNAME
Q63CLNT140
533444533322
1633CE414000
%_DUMMY$$
2222
0000
SY-MSGV1
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SYST-SUBRC
0
0000
0000
ALE_IDOC_TO_APL_OK
62
33
62
LIST_CONTAINER_CREATE[]
Table IT_20[9x1068]
FUNCTION-POOL=EDI1DATA=LIST_CONTAINER_CREATE[]
Table reference: 14
TABH+ 0(20) = 070000008036F5B8000000000000000000000000
TABH+ 20(20) = 0000000E00000014000000090000042CFFFFFFFF
TABH+ 40(16) = 0400002300000CA0000824C401000000
store        = 0x070000008036F5B8
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 14    (0x0000000E)
label        = 20    (0x00000014)
fill         = 9     (0x00000009)
leng         = 1068 (0x0000042C)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000048
occu         = 8     (0x00000008)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x070000008036F610
pghook       = 0x07000000802D86D0
idxPtr       = 0x0000000000000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
store_id     = 23    (0x00000017)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
LIST_CONTAINER_CREATE
1400000000000511747000000009E1BPADRML                     00000002#èXD63        070TST_QA140_1
3333333333333333333333333333434544544222222222222222222222333333330E54332222222233355555433353
14000000000005117470000000095120142DC0000000000000000000000000000238846300000000070434F11140F1
CONTROL
1400000000000511747640 64        2SAPQ63    LSQ63CLNT140
3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
G_MAXSYNERR
1
0000
0001
<%_TABLE_EDID4>
ALE_DISPATCH_ERROR
27
33
27
ALE_IDOC_READY_FOR_APL
64
33
64
%_SPACE
2
0
IDENT
0000000000000001
3333333333333333
0000000000000001
ALE_IDOC_TO_APL_ERROR
63
33
63
No.      12 Ty.          FUNCTION
Name EDI_DOCUMENT_CLOSE_CREATE_TAB
IDENTIFIER
0000000000000001
3333333333333333
0000000000000001
NO_DEQUEUE
X
5
8
SYN_ACTIVE
Y
5
9
IDOC_CONTROL
1400000000000511747640 64        2SAPQ63    LSQ63CLNT140
3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
SYNTAX_RETURN
0
0000
0000
INT_EDIDD[]
Table IT_10[9x1062]
FUNCTION-POOL=EDINDATA=G_T_DATA_RECORDS[]
Table reference: 9
TABH+ 0(20) = 0700000080284B80070000008028530800000000
TABH+ 20(20) = 000000090000000A0000000900000426FFFFFFFF
TABH+ 40(16) = 0400000900000AA8000824C401000000
store        = 0x0700000080284B80
ext1         = 0x0700000080285308
shmId        = 0     (0x00000000)
id           = 9     (0x00000009)
label        = 10    (0x0000000A)
fill         = 9     (0x00000009)
leng         = 1062 (0x00000426)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000039
occu         = 8     (0x00000008)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x0700000080320D90
pghook       = 0x07000000802E1508
idxPtr       = 0x0000000000000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
store_id     = 17    (0x00000011)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
hsdir        = 0x0000000000000000
ext2         = 0x07000000802852A8
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x0700000080284B30
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
NO_IGNORE
2
0
EDI_IDOC_SYNTAX_ERROR_IN
60
33
60
DOCNUM
0000000000511747
3333333333333333
0000000000511747
EXCLUSIVE
E
4
5
SYNCHRONOUS
S
5
3
APL_TESTIDOC_CHECK_OK
55
33
55
FREE_RETURN
0
0000
0000
INT_EDIDD
1400000000000000001000009E1BPADRML                  00000000##XD63        070TST_QA140_17 X00
3333333333333333333333333434544544222222222222222222333333330054332222222233355555433353322533
14000000000000000010000095120142DC0000000000000000000000000000846300000000070434F11140F1700800
SUB_INT_ACK_POSITIVE
14
33
14
G_INSERT_OK
2
0
LIST_CONTAINER_INSERT_TMP[]
Table[initial]
LIST_CONTAINER_INSERT_TMP
0000000000000000000000000                              00000000##
2223333333333333333333333333222222222222222222222222222222333333330022222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No.      11 Ty.          FUNCTION
Name IDOC_INBOUND_WRITE_TO_DB
PI_DO_HANDLE_ERROR
X
5
8
PI_NO_DEQUEUE
X
5
8
PI_RETURN_DATA_FLAG
X
5
8
PI_RFC_MULTI_CP
0000
3333
0000
PI_STATUS_MESSAGE
000000000000000000000000000000000000000000000000000000000000
2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PE_IDOC_NUMBER
0000000000000001
3333333333333333
0000000000000001
PE_INBOUND_PROCESS_DATA
140BAPI                                                  6
3334454222222222222222222222222222222222222222222222222223222222222222222222222222222222222222
1402109000000000000000000000000000000000000000000000000006000000000000000000000000000000000000
PE_STATE_OF_PROCESSING
0
0000
0000
T_DATA_RECORDS[]
Table IT_10[9x1062]
T_LINKED_OBJECTS[]
Table IT_11[0x100]
FUNCTION-POOL=EDINFORM=ONE_IDOC_STOREDATA=LT_LINKED_OBJECTS[]
Table reference: 10
TABH+ 0(20) = 000000000000000007000000802853F000000000
TABH+ 20(20) = 0000000A0000000B0000000000000064FFFFFFFF
TABH+ 40(16) = 0400000900002BB00010249401000000
store        = 0x0000000000000000
ext1         = 0x07000000802853F0
shmId        = 0     (0x00000000)
id           = 10    (0x0000000A)
label        = 11    (0x0000000B)
fill         = 0     (0x00000000)
leng         = 100   (0x00000064)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000190
occu         = 16    (0x00000010)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
hsdir        = 0x0000000000000000
ext2         = 0x0700000080285390
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x0700000080285340
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
PC_CONTROL_RECORD
1400000000000000000    30        2          LSQ63CLNT140
3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
%_VIASELSCR
0
4
%_SPACE
2
0
L_STATUS
64
33
64
L_ALE_SUCCESS_MESSAGE
B1                  S005                                                  No filters
4322222222222222222253332222222222222222222222222222222222222222222222222246266676772222222222
21000000000000000000300500000000000000000000000000000000000000000000000000EF069C45230000000000
ST_PREVIOUS_PARTNER_DATA-SYNCHK
X
5
8
C_TRUE
X
5
8
SYST-REPID
SAPLEDIR
5454444522222222222222222222222222222222
310C549200000000000000000000000000000000
C_ELEMENT_UNPROCESSED_IDOCS
Unprocessed_IDocs
56776667766544667222222222222222
5E02F353354F94F33000000000000000
ST_PREVIOUS_STATE_OF_PROCE
0
0000
0000
ST_INBOUND_PROCESS_DATA-EDIVR2
6
3
6
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
L_SYN_ACTIVE
Y
5
9
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
L_SYNTAX_RETURN
0
0000
0000
%_DUMMY$$
2222
0000
SY-REPID
SAPLEDIR
5454444522222222222222222222222222222222
310C549200000000000000000000000000000000
No.      10 Ty.          FORM
Name ONE_IDOC_STORE
IDOC_NUMBER_IN
0000000000000000
3333333333333333
0000000000000000
STATE_OF_PROCESSING_IN
0
0000
0000
INBOUND_PROCESS_DATA_IN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GT_NEW_IDOC_IDENTIFICATIONS[]
Table[initial]
G_LAST_IDOC_NUMBER
0000000000000000
3333333333333333
0000000000000000
SYST-REPID
SAPLEDIN
5454444422222222222222222222222222222222
310C549E00000000000000000000000000000000
CURRENT_CONTROL_RECORD_IN-DOCNUM
0000000000000000
3333333333333333
0000000000000000
CONV_ERROR
2
0
C_TRUE
X
5
8
SY
0000000000000000000000000000000000000000000000000000000000000000000000000000000200000000000000
0002000000010009000000000000000000000000000100000001000000010000000000000000004C00000000000000
STATUS_MESSAGE_IN
000000000000000000000000000000000000000000000000000000000000
2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_IDOC_SELECT_AND_WRITE_TO_DB
5
3
5
SY-REPID
SAPLEDIN
5454444422222222222222222222222222222222
310C549E00000000000000000000000000000000
STATUS_MESSAGE_IN-STAMID
22222222222222222222
00000000000000000000
GT_NEW_IDOC_IDENTIFICATIONS
0000000000000000
3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
STATUS_MESSAGE_IN-STAMNO
000
333
000
RET_FLAG
X
5
8
G_RFC_CODEPAGE
0000
3333
0000
RSJOBINFO-JOBSUBRC
0
0000
0000
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
SY-LANGU
E
4
5
G_T_DATA_RECORDS[]
Table IT_10[9x1062]
LT_LINKED_OBJECTS[]
Table IT_11[0x100]
CURRENT_CONTROL_RECORD_IN
1400000000000000000    30        2          LSQ63CLNT140
3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
SWO_%OBJID
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No.       9 Ty.          FUNCTION
Name IDOC_INBOUND_ASYNCHRONOUS
IDOC_CONTROL_REC_40[]
Table IT_3[1x524]
FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_CONTROL_REC_40[]
Table reference: 3
TABH+ 0(20) = 07000000802D876007000000802D449000000000
TABH+ 20(20) = 0000000300000003000000010000020C000000E0
TABH+ 40(16) = 0400000900001FE0000A249001000000
store        = 0x07000000802D8760
ext1         = 0x07000000802D4490
shmId        = 0     (0x00000000)
id           = 3     (0x00000003)
label        = 3     (0x00000003)
fill         = 1     (0x00000001)
leng         = 524   (0x0000020C)
loop         = 224   (0x000000E0)
xtyp         = TYPE#000136
occu         = 10    (0x0000000A)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 0
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x07000000802DB9D8
pghook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 10    (0x0000000A)
lineAlloc    = 10    (0x0000000A)
store_id     = 9     (0x00000009)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
hsdir        = 0x0000000000000000
ext2         = 0x07000000802D88A0
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x07000000802D8710
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
IDOC_DATA_REC_40[]
Table IT_4[9x1063]
FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_DATA_REC_40[]
Table reference: 4
TABH+ 0(20) = 07000000802D880807000000802D896000000000
TABH+ 20(20) = 00000004000000040000000900000427FFFFFFFF
TABH+ 40(16) = 04000009000020500008249001000000
store        = 0x07000000802D8808
ext1         = 0x07000000802D8960
shmId        = 0     (0x00000000)
id           = 4     (0x00000004)
label        = 4     (0x00000004)
fill         = 9     (0x00000009)
leng         = 1063 (0x00000427)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000138
occu         = 8     (0x00000008)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 0
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x07000000802E1550
pghook       = 0x07000000802D8860
idxPtr       = 0x0000000000000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
store_id     = 12    (0x0000000C)
shmIsReadOnly = 0     (0x

Hi Rohan,
Welcome to SDN!
This error means that you're trying to duplicate a record on the DB... check the IDOC number ranges... it might help
Regards
Juan
Please reward with points if helpful

Procedure to know client size, and client copy.

Dear Experts,
                    I am new to client copy process.Please help me in some of my queries.The client which i want to copy is a customizing client (120) in development server.And new client to be created is also on development server itself.
1). How can I know the exact size of the client which i want to copy?
2). Will all the customizing done on the (120) client be copied to the new client created .
3). Will all the profiles and parameters be copied as the source client?
4). And Detailed process from client creation to client copy.
Please help me .
Thanks in Advance
Regards
Akif

Dear Umesh,
                   As you told to add the space i did that .And started the client copy but it ended with 4 following errors:-
Table/Object
Component
Error
AGR_HIER
BC-SEC-USR-PFC
Write Error (See System Log)
DSYS_PHCONT_E_CD
PY-XX
Write Error (See System Log)
SOES
BC-SRV-GBT
Write Error (See System Log)
ZFX_BCBNR
DDIC Error        (See SE14)
Please suggest what should be done of this errors.
And thx for ur total support.
Regards
Akif
<u></u><u></u>

SAP* not authorized after Client copy

Dear All,
Here's the scenario:
1. Created a new logical system for a new Quality client 230.
2. Created the new client 220
3. scheduled a test remote client copy from the new client, source Production. (Successful)
4. Scheduled the actual client copy to run last night.
5. Today morning, I'm logging into the new client with SAP*, it prompted me to change password.
6. I want to look for the client copy logs (SCC3), but getting "not authorized"
7. Checked all other transactions, all giving "not authorized" error
Any help would be appreciated. Thanks in advance.

Dear Reza,
Better to go for Client Export Import process . This is what SAP reccomends for coping clients between
different systems ( Like from Production to Quality ) as the remote client copy has many
disadvantages..
For this 1 ) you should get the downtime of production system and do the client export process .
SCC8 . See the logs at scc3 .
2) Copy the datafile and cofile to the Source system
3) Import it usting stms_import .
Monitor the logs as the logs will be grown massive and make sure enough space is there.
4) After client copy , go for post processing ( scc7 ) .
Hope you are clear and feel free to get back if any doubts.
Regards,
Nibu

Need client copy of production server in quality server

Hi,
I need the client copy of production server with application data in quality server. How i do this?
Main purpose is we have no data in quality server in testing purpose. if we configure the client of production server in Quality, we can test it by our requirement.
Regards
Somu

Try this
Preparatory steps in source SAP system
1 Take the trace of control file in the source system using the following command at SQL prompt as below:
SQL>alter database backup controlfile to trace;
The trace file can be found in the location <drive>\Oracle\<SID>\saptrace\usertrace.
2. Open the file with notepad and save a copy as controlsrc.txt
3. Stop the SAP
4 Shutdown the database from SQL prompt.
5. Take backup of database files.
6. Start SAP
Steps in the Target system
7. Install SAP system with <TGTSID>
8. Stop the SAP.
9. Shutdown the database from SQL prompt.
10. Take the backup of database files.
11. Edit controlfilesrc.txt with regard to the locations of datafiles of source system to be placed in target system taking in to account the space available in different drives and save as control.sql. Also SET DATABASE u201C<TGTSID>u201D RESETLOGS.
12. Replace the database files with source systems database files conforming to the control.sql
13. Start the database in nomount state from SQL prompt as below.
SQL>startup nomount
14. Run the control.sql script as follows:
SQL>@@<location of directory>\control.sql.
Once the script runs successfully, the database will be in mount state
15. Open the database with resetlogs option as follow:
SQL>alter database open resetlogs;
16. Create OPS$ users of source system conforming to target system conventions in database.
17 Set the environment variable dbs_ora_schema to SAP<SRCSID> as the owner of the database objects will still be as SAP<SRCSID>..
18. Start SAP.
Lalit Kumar

Client Copy- Cancelled

Hi,
I am doing a local client copy with SAP_ALL profile on ECC 6.0 (Kernal 700 Patch- 133). After creating a new client, i started the client copy with sap* user with SCCL t-code.
After some time, the client copy got cancelled and it gave a SYSTEM_CORE_DUMP in ST22.
"Error in the SAP kernel.
The current ABAP "SAPLSDBI_DYNSQL" program had to be terminated because the
ABAP processor detected an internal system error."
Do you think I have to upgrade the kernal to patch level 185 for this error or it can be solved by some other ways.
Please suggest.
Regards,
Jitender

Do you think I have to upgrade the kernal to patch level 185 for this error or it can be solved by some other ways.
Kernel upgrade is not required only for this activity, as you are allready in 133. First of all check the space at file system on OS level and remove the core dump, then run the check db and see the space available on database, then perform a test run and at last execute the local client copy
Regards,
Subhash

Client Copy Using Client Export/Import

Hi Everyone,
This is regarding Client Copy Using Client Export/Import Method. We have two system Production and Development system. Iam planning to do a client copy from from PRD to DEV. I know most of the steps to perform Client Copy.I have some doubhts So if some one can please help me out i would really appreciate it.
!) I want to know which user should be used to perfrom Client Export ?
2) I want to know know which user to be used to perform Client delete?
3) Is there any particular USER who is recommended to perform Client Copy or any USER can do it?
4) After the Client Delete Procedure thorugh SCC5 ..to get back the client space we do Reorganization ? can anyone plzz tell me what are the tables that i need to reorganize or if anyone can provide me the steps for Reorganization i would be really thankful.
Waiting For your Replies
Best Regards

Hi Mohammed,
1)I want to know which user should be used to perfrom Client Export ?
You can use your personal defined on the system UserID.
2) I want to know know which user to be used to perform Client delete?
Same as above, just make sure you have an account on the client and you log on to the right client
3) Is there any particular USER who is recommended to perform Client Copy or any USER can do it?
I am not aware that you should use a particular user. I have been doing copies/deletions with my UserID, as system administrator.
4) After the Client Delete Procedure thorugh SCC5 ..to get back the client space we do Reorganization ? can anyone plzz tell me what are the tables that i need to reorganize or if anyone can provide me the steps for Reorganization i would be really thankful.
Reorganization ( I personally) use SAPDBA tool. However -if you use ORACLE, there are other alternatives as well. What is your DB vendor? I will append more info in a bit.
Rgds,
Loukas

Setting up a new client. Is "client copy" necessary?

Hi,
I just installed NSP. As I don't want to work in client 000, I have created a new development client 100.
Our internal notes suggest that I must always copy client 000 to client 100. However, this takes up a few hours and chews up another 30G of harddisk space.
This is a freshly installed system just for testing. I am wondering if "client copy" is really a must or just a suggestion. What exactly do I lose if I don't do a client copy?
Thank you in advance for your help.
Peter

Can someone please help me? I still haven't received a good reply on how important it is to do a client copy.
In my test case, I like the base client 000 to have nothing in it. I then would like to set up two totally different companies as two different clients. These companies have nothing in common. I don't see why I really should do a client copy.
Regards,
Peter

Error in Client copy

Hi Team,
We got a problem during client import because of the transaction log being full.We observe that the transaction log space in initially at 95 % free but when we start the import job its keep on growing drastically and reaching its maximum available size before the import completes.
Is there any way to switch off the transaction log temporarily during the import job ? we are running on SQL 2005 , ECC 6.0.
I got following command from some forum ( sp_dboption QAS, 'trunc. log on chkpt', false )
(sp_dboption QAS, 'trunc. log on chkpt', true* )*
which says these SQL queries would switch off the changes recording on to transaction log. i dont know whether this would work on SQL 2005. Please let me know the way to fulfill my requirement.
Any quick replies would much appriciated. Please help me to fix this issue.
Thanks & Regards,
Vinod

Hi Topquark,
Thanks for the information.
what you said was true..simple recovery model did not help us to switch off the logging in SQL server 2005. We do not have any past experince as we are performing the client copy activity first for our client. We have around 17.5 GB free space available at file system for transaction log directory.
we have autogrowth enabled and set to 50MB. Production client export job was sucessfull( it is aroung 5.4 GB export copy) when we start the import job intially it is 98 % free however it was running fine for some after that it started increasing and occupying all free space before import job completes.Hence job fails due to insufficient free space.
In normal circumstances log file growth was normal. I have exported the histroy of log space couldn't find much info.
We have tried following options to fix this issue but all are went with no sucess.
1) tried with changing database recovery mdel to 'Simple'
2) Shrink the transaction log file and provided 17.5 GB free space.
3) Created addditional transactional log in other disk drive.
Please let us know what do more on this?
Thanks & Regards,
Vinod

Can a client be refreshed with client copy?

I created a new client by
doing client copy from client 200 creating client 202
Now I want to refresh client 202 from client 200 (ALL ON SAME SERVER) , can I just re-run the client copy with source client being client 200 to client 202?
If so what am I to expect?
If not, then do I need to first drop client 202 and then do the client copy to re-create the client?
maria

Dear Maria,
Greetings!
To be clear, now your situation is to have a client copy from your Production client 200 to the Quality client 202.
Coming to the status of other clients in Quality system, the data or any other settings of the other clients is NOT going to be changed because of this client copy.
As far as the configuration part, you will have to perform the following functionalities in your Target client (Quality - 202)
1. Transaction SCC9 - Select Profile - Choose the SAP profile as per your need.
2. Enter the RFC destination to the Source system client - Production Client 200 - This RFC destination could be an already existing connection between both the systems or a newly created one.
3. Make an RFC system comparison to be sure that the connection is perfect.
4. Set-up the parallel processing parameters, Menu option Goto - Parallel Process. This option is dependent on the physical memory availability of the Quality server.
5. Execute a TEST RUN, prior to start of the actual client copy to verify Target client feasibilities. In case of any mismatch in table definition or table fields corresponding action has to be performed.
Please remember the following pre-requsities before starting the client copy.
1. Both the Source and Target client is to be locked against access to end users or other users. For a pre-caution lock all the users except SAP*, DDIC, TMSADM, BASIS and other System Admin users in both the clients.
2. No auto-logout parameters or restrictions on workprocess runtime exists as profile parameters in the system.
3. Additional space for a client is available in the database so the the client copy in not interrupted.
Kindly process the client copy in a server session such that network interruptions and other interruptions could be avoided.
Kindly revert in case you need further informations on the same.
Thank you
Regards,
Vineeth

Third party Client copy tools -

Hi,
We have a production system copy in our QA which has about 6.5 terrabyte. How do we know the size of the client in that system? If I have to make another client copy in my QA it will be highly impossible - considering storage, memory, backup times etc. To justity buying a third party tool I need to give exact size of the production client in QA ( not the whole database size) to the mgmt. Is it possible?
Any one know any third party tools to copy subsets of a client? such as Gold client, Infoshuttle etc.? Which product is a better option?
Thanks for your responses in advance.

Sam,
Did you solve your problem?
Just to update you on the new products of Gamma:
InfoShuttle Client Builder is designed specifically for SAP customers who need a flexible solution for building new clients in non-production environments. By enabling user-selected master, transaction and related configuration data to be quickly and easily replicated from production systems into new fully functional lean clients for development, test and training environments, Client Builder dramatically reduces the time and disk space needed when compared with creating a full database copy.
InfoShuttle® Data On Demand is the only Certified for SAP® NetWeaver solution to offer a comprehensive and systematic way to move user-selected production data into existing non-production environments, such as development, QA and training. As part of the InfoShuttle Suite of application data management solutions, Data On Demand provides a flexible method for replicating subsets of current master and transactional data, insuring full data integrity, reducing application and upgrade deployment risk, improving productivity and shortening development and test cycles.
You build new clients for every new project.
SAP customers can easily build a new client once with Client Builder and then keep the systems up to date with Data On Demand, both of which can be automated as a standard process.
Technical Specifications
     Not hardware or OS dependent runs inside of SAP
     Supports SAP R/3 versions 4.6, 4.7, ECC 5.0 and 6.0
     Supports the transfer of selected transactional data while maintaining links with associated documents
     Ships with InfoShuttles unique Content Library of data objects for core SAP R/3 modules as well as tools to enhance them or create new objects
     Runs in foreground or background mode
     Data can be transferred out of SAP R/3 to other applications via XML
     Data object maintenance separated into distinct components for ease of customization and simplification of upgrades
     All supported object-to-object relationships established in separate Relationship Registry to simplify enhancement and prevent errors
     Incorporation of Business Add-ins (BADIs) to allow for customization without modification and/or copying of standard data objects
     Web-services enabled
Good luck

Client Copy space assumption/calculation

Similar Messages

Maybe you are looking for