on 07-03-2007 4:00 PM
Dear all,
I need some clarification on note 355771 regarding the new tablespace layout in an ABAP only system. At the moment, I am using Oracle 9.2.0.7 with SAP Kernel 6.40 and dictionary managed tablespaces with the old tablespace layout. I am upgrading to Oracle 10.2.0.2 soon and then I am doing a full reorganisation to have ASSM tablespaces and the new tablespace layout implemented. I understand that PSAPUNDO, SYSTEM and PSAPTEMP remain as they were. Also, I need to create the new
PSAPSR3
PSAPSR3USR
PSAPSR3640
tablespaces, which will be ASSM. Then I need to export/import the contents of the tablespaces below to the tablespaces above
PSAPLOADD/I
PSAPSOURCED/I
PSAPDDICD/I
PSAPPROTD/I
PSAPCLUD/I
PSAPPOOLD/I
PSAPSTABD/I
PSAPBTABD/I
PSAPDOCUD/I
PSAPUSER1D/I
What is not clear to me is exactly what goes to where: For example:
Am I exporting the contents of PSAPUSER1D/I and importing them to PSAPSR3USR
Am I exporting the contents of PSAPEL640D/I and PSAPES640D/I and importing them to PSAPSR3640
Am I exporting the contents of all the rest and importing them to PSAPSR3
Is this the way to implement the new tablespace layout? I didn't find exact instructions on what data from the old tablespaces should be imported to each of the new tablespaces.
Many thanks
Andreas
In general, if the schema owner is SAPSR3, tablespaces PSAPUSERD/I go to PSAPSR3USR, all the version related tablespaces go to PSAPSR3<REL>, the remaining tablespaces to PSAPSR3.
You can find the mapping between old and new layout and all the informations needed for migration to the new layout in the note 355771.
According to that note you can perform the conversion using the BR*Tools.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
David, thanks
Peter, are you sure that it can only be done with R3load? Note 355771 at the bottom of page 4 reads that it can be done with brtools (see also notes 646681 and 541538). I know it can be done via R3load as I have done this in the past as part of a Unicode conversion
I wouldn't use Oracle exp and imp, but brspace provides its own option for exporting/importing tablespaces
Regards
Andreas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
sorry, you are right, br*tools are a second option which handle the stuff correct.
It wasn't just clear what kind of tools you are going to use.
By the way, you will not be able to change the schema-id when using br*tools.
The schemaid is used in two places:
1. it is part of the database user, who owns all the SAP Tables
2. it is part of the tablespace names.
you would be able to change it for 2. but not for 1.
regards
Peter
you will only be able to convert from Old TS layout to the new one using R3load based homogenious system copy.
There are some more things to do than pure moving data which is automatically handled by r3load / sapinst.
If you just export / import the contents of existing old tablespaces to the new tablespaces with Oracles exp/imp tools the SAP Datadictionary will not work correctly.
regards
peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.