Skip to Content

het system copy cluster tables

Hi

i retake a discussion i had some days ago about an heterogenous system copy about system 7.01 with many tablespaces created ad hoc .

The problem was that in target system there weren't the same tablespaces of source system. For five of them , infact, the tables came back to original tablespace PSAPSR3.

4 of these tables are cluster tables:

RFBLG (BSEG, BSEC,etc)

KOCLU ( KONV)

CDCLS (CDPOS)

EDI40 (EDID4)

I saw that there was a problem in TSORA TAORA and IAORA , missing the entries for these tablespaces. I've adjusted these tables and changing the se13 associating the referred table name to the right class (ex USR62,USR63,etc) and activated it.

I did the same thing also for a not cluster table like STXL and only for this table i solved the problem.

Fot other cluster table i see in export that program r3ldctl and r3szchk don't take these new entries ...only the DDLORA.TPL is right.....but in DBSIZE.XML no tablespace for the four cluster tables.

In STR files i find the following entry:

:{xxxadm}:/mnt/xprt_p1e/EXPP1E2/ABAP/DATA> grep KOCLU *.STR

KOCLU.STR:tab: KOCLU

KOCLU.STR:att: CLUST 3 ?? C all KOCLU~0 CLUST 3

It seems that it looks for entry in taora called CLUST

Am i missing something to solve this situation?

Thanks

Nick

Immagine.png (6.1 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on May 18, 2015 at 08:28 PM

    Hi Nick,

    Could you please cross check table DD09L for your tables.

    If the TABART is still APPL1 and not your new USR* TABART then please execute report RSFXTBRT (leave the mode field blank).

    The report should confirm the inconsistencies you have. Once you are happy that the report is confirming the tables you have mentioned then please run the report again and this time fill "FIX" in the mode field. Then of course, please cross check DD09L again to make sure the changes are persistent.

    After you've done the above, please run your export step again to confirm that DBSIZE.XML now takes the different tablespaces into account.

    Kind Regards,

    Amerjit

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Nicola Blasi

      Nick,

      If I were in your boots I wouldn't even bother with separate tablespaces. There is only one case where I had to do that and that was a unique case.

      It seems to me like you're maintaining/have inherited a "legacy" layout whereas now would be the moment to go back to the "norm".

      Your RFBLG isn't abnormally big by any reasonable standards and your EDI40 could be significantly reduced by some housekeeping (see note #706478). As for KOCLU/CDCLS/STXL, I'd imagine the sum of all three would be less than 100GB.

      Amerjit

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.