on 02-21-2013 11:48 AM
Dear friends,
we r trying to do package splitting for our 640 system but package splitter is throwing errors. Can you please suggest sometihng.
I have tried both package splitters which are available in marketplace under SYSTEM COPY TOOLS 7.00 & SYSTEM COPY TOOLS 7.10.
***************************************************************************************************************************************************************
INFO: 2013-02-21 08:46:42
Package Splitter is started.
CONFIG: 2013-02-21 08:46:42
Application options:
extDirs=C:\ASHISH\ABAP\DB\ORA
outputDir=C:\ASHISH\ABAP\STRo
packageLimit=200
str=
strDirs=C:\ASHISH\ABAP\DATA
tableLimit=50
top=20
CONFIG: 2013-02-21 08:46:42
List of packages with table structure: 'SAP0000'.
CONFIG: 2013-02-21 08:46:42
List of packages with views: 'SAPVIEW'.
CONFIG: 2013-02-21 08:46:42
Version table: 'SVERS'.
CONFIG: 2013-02-21 08:46:42
List of data conversion tables: 'DDNTF,DDNTT,DDNTF_CONV_UC,DDNTT_CONV_UC'.
ERROR: 2013-02-21 08:46:42 com.sap.inst.split.str.StrExtSplitTask run
Fatal exception during execution of the Package Splitter.
java.lang.IllegalStateException: Package name cannot be null or empty
at com.sap.inst.basis.PackageConfig.containsPackage(PackageConfig.java:184)
at com.sap.inst.basis.PackageConfig.isEmptyPackage(PackageConfig.java:135)
at com.sap.inst.split.str.StrExtSplitTask.initNormalPackages(StrExtSplitTask.java:205)
at com.sap.inst.split.str.StrExtSplitTask.doRun(StrExtSplitTask.java:122)
at com.sap.inst.split.str.StrSplitTask.run(StrSplitTask.java:194)
at com.sap.inst.split.PackageSplitter.startAppJob(PackageSplitter.java:348)
at com.sap.inst.lib.app.CommandLineApp.doMain(CommandLineApp.java:111)
at com.sap.inst.split.PackageSplitter.main(PackageSplitter.java:390)
INFO: 2013-02-21 08:46:42
Package Splitter is stopped.
***************************************************************************************************************************************************************
Hi,
you can't split DNTF,DDNTT,DDNTF_CONV_UC,DDNTT_CONV_UC
For additional database-specific information, see also Note 888210 - NW 7.**: System copy (supplementary note).
We don't need to apply Note 925309 - Oracle: Problems in homogeneous migration because we have SAP BASIS >700 SP09 (current is 701 SP08).
Note 813562 - Incorrect create index statement for partitioned indexes is not to be applied because only available for 6.20-6.40.
As mentioned in note 88210 no need to specify the database version.
BR,
Prabhakar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
As per the system copy guide, you can't split DNTF,DDNTT,DDNTF_CONV_UC,DDNTT_CONV_UC
Please see the attachment for your reference.
You should delete the entries of these tables before starting the splitting.
Or you can use the package splittin feature available in the SAPINST itself for splitting..
Thanks and Regards,
Vimal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hallo,
If your exports is combined with unicode conversion maybe you have to read this note : Note 833946 - Note 833946-Splitting of STR files :
"
As part of the unicode conversion R3load STR files have been split before the export to create smaller packages for the system copy. As a result the tables DDNTT and DDNTT_CONV_UC have been separated into different STR files as well as the tables DDNTF and DDNTF_CONV_UC.
The problem may occur if you use the perl based script SPLITSTR.PL or the java based package splitter tool version 1 from the SAP Service Markte Place or from the installation kit NW 04 SR1.
Solution
..."
Regards,
Paul
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
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.