on 11-07-2011 3:35 PM
Dear all,
I was doing SystemCopy.
I'll want to upgrade 60 SR3,
Upgrade phase(pre-upgrade) Required /ASU/Upgrade tool.
So I atached ST-PI 2008_46C_0 SPAM Install , but Error Appered.
Activation of shadow nametabs with DDL |
19:06:41: Retcode 1: error in DDL statement for BDLDTOC - repeat |
Error 959-ORA-00959: tablespace 'PSAPBTABI' does not exi when executing ADD-FIELD of |
Error in DDL statement for when executing ADD-FIELD of |
(dummy, do not translate) |
No DDL commands found for activation of BDLDTOC |
1 shadow nametab activations resulted in errors |
End: Activation of shadow nametabs with DDL (20111104190653) |
Activating inactive nametabs |
End date and time : 20111104190653 |
| Ended with return code: ===> 8 <===
How can I attach ST-PI Tool.
I thought , Oracle Structured Changed at System Copy PSAPBTAB* to PSAPSR3I.
if I Have to re-systemcopy
How Can I do Systemcopy using Old Tablespace Structure.
Best Regards,
Naofumi Yamazu
[sorce System]
Windows Server 2003 R2/SP2 32bit
Oracle 9i
SAP r/3 46C (Kernel 46D_EXT 32bit)
[Target System]
Windows Server 2003 R2/SP2 x64
Oracle 10.2.0.4 64bit
SAP r/3 46C (Kernel 46D_EXT 32bit)
You don't necessarily have to use the old tablespace layout. Check note [777615 - Incorrect data class/database container assignment|https://service.sap.com/sap/support/notes/777615] and also the related notes mentioned there. Basically you have to correct the entries in TAORA/IAORA.
If you want to do the system copy with the old layout, either do a database based copy (backup/restore) or change the DDLORA.TPL file when using sapinst. Use the search function and the documentation for more info on that-
Cheers Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Michael-san,
I understand I donnot nessary to re-copy Target system.
I seem TAORA, TSORA is correct entry .
I want to atattch ST-PI 2008_46C for this system.
I thought ST-PI Installer(using SAINT) searching PSAPBTABI.
Please let us know if any workaround.
Best Regard,
Naofumi Yamazu
テーブル: TAORA
表示された項目数: 7 / 7 固定列 1 一覧幅 0250
-
TABART | TABSPACE | PCTINC | OFREELIST | OFREEGROUP | OPCTFREE | OPCTUSED |
-
APPL0 | PSAPSR3 | 0000 | 001 | 01 | 10 | 40 | |
APPL1 | PSAPSR3 | 0000 | 1 | 1 | 10 | 40 | |
APPL2 | PSAPSR3 | 0000 | 1 | 1 | 10 | 40 | |
CLUST | PSAPSR3 | 0000 | 1 | 1 | 10 | 40 | |
POOL | PSAPSR3 | 0000 | 1 | 1 | 10 | 40 | |
SDIC | PSAPSR3 | 0 | 1 | 1 | 10 | 40 | |
SDOCU | PSAPSR3 | 0000 | 1 | 1 | 10 | 40 | |
SLDEF | PSAPSR346C | 0000 | 1 | 1 | 10 | 40 | |
SLEXC | PSAPSR346C | 0000 | 1 | 1 | 10 | 40 | |
SLOAD | PSAPSR3 | 0000 | 1 | 1 | 10 | 40 | |
SPROT | PSAPSR3 | 0000 | 1 | 1 | 10 | 40 | |
SSDEF | PSAPSR346C | 0000 | 1 | 1 | 10 | 40 | |
SSEXC | PSAPSR346C | 0000 | 1 | 1 | 10 | 40 | |
SSRC | PSAPSR3 | 0000 | 1 | 1 | 10 | 40 | |
TEMP | PSAPSR3 | 0000 | 1 | 1 | 10 | 40 | |
USER | PSAPSR3USR | 0000 | 1 | 1 | 10 | 40 | |
USER1 | PSAPSR3USR | 0000 | 1 | 1 | 10 | 40 | |
USER7 | PSAPSR3USR | 0 | 1 | 1 | 10 | 40 | |
USER8 | PSAPSR3USR | 0 | 1 | 1 | 10 | 40 |
-
テーブル: TSORA
表示された項目数: 2 / 2 固定列 1 一覧幅 0250
-
TABSPACE | INDSPACE |
-
PSAPSR3 | PSAPSR3 | |
PSAPSR346C | PSAPSR346C | |
PSAPSR3USR | PSAPSR3USR |
-
Hm, weird TAORA seems to be ok. Still there is a bunch of possibilites, sadly i don't have an 4.6C system anymore so i can not give you more detailed advice. It might be best to open a SAP support message on how to proceed, this might be worth the time and save you trouble when upgrading to ERP 6.0.
Two things you might consider:
- temporarily create a tablespace PSAPBTABI, reorg the objects to the correct tablespace (PSAPSR3) after the installation and drop the tablespace
- try to manually change the tablespace in SE14 for BDLDTOC to PSAPSR3, but i cannot say if this is possible at all in your situation
Cheers Michael
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.