Skip to Content

Syscopy (during Unicode convertion): Import on same tablespace layout

Hi forum,

we're working on a Unicode convertion of our ECC landscape made of Solaris

10 Sparc and Oracle 10.2.0.4.

We use the procedure described in UC for SAPNetWeaver 7.0 SP 14 and

higher. Export runs well without error

or problem in our db (1,6 TB of used space).

During import SAPinst show me a different, then source system,

tablespaces layout:

PSAPSR3

PSAPSR3700

PSAPSR3FACT

PSAPSR3ODS

PSAPSR3USR

SYSAUX

PSAPUNDO

PSAPTEMP

SYSTEM

But my soursce system was:

PSAPBTABD

PSAPBTABI

PSAPCLUD

PSAPCLUI

PSAPDDICD

PSAPDDICI

PSAPDIMD

PSAPDIMI

PSAPDOCUD

PSAPDOCUI

PSAPEL700D

PSAPEL700I

PSAPES700D

PSAPES700I

PSAPFACTD

PSAPFACTI

PSAPLOADD

PSAPLOADI

PSAPODSD

PSAPODSI

PSAPPOOLD

PSAPPOOLI

PSAPPROTD

PSAPPROTI

PSAPSOURCED

PSAPSOURCEI

PSAPSTABD

PSAPSTABI

PSAPTEMP

PSAPUNDO

PSAPUSER1D

PSAPUSER1I

PSAPZ***********

PSAPZ***********

PSAPZ***********

SYSAUX

SYSTEM

We have already read 425079, so, can we use source system layout?

can SAPinst use our previous tablespace layout during import? ... or do

we must it manualy?

Regards.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Oct 16, 2009 at 10:35 AM

    Hello,

    It is far better that you create the target database using the new layout. The old tablespace layout with multiple tablespaces and data/index separation is no longer adapted to modern environments, and a Unicode conversion gives you a unique opportunity to switch to a more appropriate structure for your DB.

    Regards,

    Mark

    Add comment
    10|10000 characters needed characters exceeded