on 05-26-2014 10:53 AM
Hello,
we have some exchange tablespaces after some failed SUM operations. At the end we use JSPM and SPAM/SAINT to implement the Solution Manager SPs.
PSAPSR3702, brtools found 2 objects while dropping, nothing to display with sql commands, abort drop
PSAPSR3702X, 40G of data, reorg to PSAPSR3 needed
Should we reorg and drop the tablespaces?
We found the following note, but I need an action plan.
1848753 - SUM 1.0: exchange tablespace (e.g. PSAPSR3702X) handling during release upgrade/update
br
Patrick
Dear Patrick,
please read http://service.sap.com/sap/support/notes/1715052. I hope it help.
With best regards,
Alexander
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
Please read this discussion to understand why there are two tablesapces.
http://scn.sap.com/thread/3383195
If you have used SUM to do a patching with the help of a shadow instance then SUM will create a tablespace called PSAPSR3702X and the source tablespace PSAPSR3702 will be empty after the SP update.
If there are objects in the PSAPSR3702 tablespace then you can move them to the target tablespace.
su - orasid
brspace -c force -o process,time -u / -f tbreorg -a reorg -tablespace PSAPSR3702 -t "*" -parallel 3 -degree 3 -newts PSAPSR3702X
Regards
RB
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.