on 09-11-2013 4:04 PM
Hi,
Issue is solved.
I modified DBSIZE.XML file with 150GB instead wrong 600GB sapinst calculated.
After that sapinst (SPM) duplicated size to 250GB so I continue until it finished successfully.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jorge,
Which 'R3szchk' patch did you use for the export? I strongly recommend you to use the latest one. I have seen cases where this issue was because 'R3szchk' was calculating the database size wrongly at the export already.
You can download the latest one from
http://service.sap.com/swdc -> Support Packages and Patches -> Browse our Download Catalog
Additional Components -> SAP Kernel ...
Regards,
Hugo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
R3szchk information
--------------------
kernel release 720
kernel make variant 720_REL
DBMS client library MAXDB_774_b09
DBSL shared library version 720.00
compiled on Linux GNU SLES-9 x86_64 cc4.1.2 use-pr100217 for linuxx86_64
compiled for 64 BIT
compilation mode UNICODE
compile time May 4 2010 20:03:21
update level 0
patch number 0
source id 0.046
I did not updated, but the export is already on target server and we have no time.
If I modify DBSIZE.XML to 250GB instead 600GB could work?
Do sapinst (SPM) works with jobs in import ABAP phase on MaxDB as Oracle?
Regards
What is the database size of source system in db02 and also, estimated database size in dbsize.xml?
Thanks
Sunny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
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.