ECC6 Installation

Dear Sir or Madam,
We are about to explore new ECC6 system. I have some questions regarding the installations.
1) Will ECC6 come together with some modules such as FI-CO,SD,MM,etc?
2) During installation, will I be able to select which module I want to install?
3) Will some modules such as BI, APO come together also? Or are they separate ADD-ons?
4) Is there any disk-space guidance from SAP regarding the ECC6 installation? We're probably interested to install IDES (for education purpose).
If you tell me what the total number is, which part of installation that number allocate to?
I've tried using the service.sap.com/sizing but it seems this tools is more for business rather than to suit our purpose.
Thank you for your kind attention in this case.
Regards,
Fausto

Hi Fausto,
1) Yes, ECC6.0 comes with all the default modules like any other SAP R/3.
2) No, There is no such option is avilable because all the module are integrated.
3) BI and APO Comes to gather. They can be installed seperately as well.
4)Yes, you can refer http://service.sap.com/install-guides. Configuratio of H/ware depend's on your OS,DB and no. of users.
Regards,
Hari.
PS:Points are welcome.

Similar Messages

Steps on ecc6 installation in suse linux

hi sir/madams
i am new in ecc6 installation on linux systesm please provide a sap installation steps on suse linux...and thankul to all
regads
suresh

Check the install guide as above for ECC/ERP 6.0 and also be sure to check the following SAP notes:
Note 171356 - SAP software on Linux: Essential information
Note 1275776 - Linux: Preparing SLES for SAP environments
Depending on the version you running:
Note 1310037 - SUSE LINUX Enterprise Server 11: Installation notes
Note 958253 - SUSE LINUX Enterprise Server 10: Installation notes
Nelis

ECC6 Installation Failure

Guyz,
i'm installing ecc6.0..before starting details, lemme tell you that system is going to be used for sandbox and max users are 4-5 ....
my machine has 79GB diskspace and 3.6 GB RAM .... as per installation guide's minimal hardware requriements are --> 62 GB Disk & 3 GB ram ....i'm doing a domain installation and all domian related configurations are intact ('coz already i installed SOLUTION MANAGER successfully with teh same domain config) .... during SAPinst process, screen prompts for the MSSql Data base file sizes and its location like C:\ECCDATA1 .....ECCDATA7 and proposed size of all folders are 155GB, which doesn't match with recommended requriements....
though we can edit the size and location of these individual folders, i've got following questions:
1> Do we have to have all ECCDATA1 ....ECCDATA7 folders ? though we can delete from SAPInst, how many of them we can have for minimal installation for a sandbox ?
2> as this is a test run of ecc6 installation, what could be the above folders' sizes to carry on the installation ?
3> after test run, in real deployment (pls note that this is sandbox of max users 4-5 only), how much size for these folders aswell as how much whole diskspace should i require it ?
appreciate if you could share your thoughts on this....
Btw its ECC IDES system.....
thanks
Edited by: Kasu on Dec 18, 2007 3:46 PM
Edited by: Kasu on Dec 18, 2007 3:48 PM

Hi Markus
i installed solman on different box though ....
can i assume that number fiiles can be changed by me during SAPinst.... yesterday after failure, i'm trying to top up the diskspace with another 200gb...if it happens, i'm gonna do as proposed by sapinst or else i'll have to squeeze in with less number files....is htat fine?
in this connection i have another question, i'm sure u can answer ....
after ecc6 installation i'm planning to install NW 04s AS ABAP, AS JAVA , BI JAVA on separate box ... i ordered all dvds from sap which i got .... in one box along with dvds i found a 'First Steps' document by SAP which says 'Installation of IDES SAP NW 2004s SR2 with BW7.0/SEM6.0 " . below are the dvds i got from SAP :
SAP NETWEAVER 2004S SR2 Kernel 7.00 (Material No. - 53001135)
MS SQL SERVER (Material No. - 53001041)
SAP BW 7.00 (Material No . - 53001018)
actually ECC6 is only with AS ABAP and as i want BW also (without portals), i'm planning to install AS ABAP, AS JAVA , BI JAVA on separate box.... are the above DVDs correct for my installation of NW 04s ?
thanks in advance

ECC6 Installation error when start instance step

Hi all,
I'm doing to install IDES ECC6 SR3 on window x64 with oracle database.
I have some error in start instance step as error log below.
Could you help me to investigate it?
I try to do it more time but it can not pass this step.
Thank you very much.
This thread is same my problem but it still is not solved.
Solution Manager 4.0 on Win install problem
CJS-30149 ABAP processes of instance FSM/DVEBMGS00 ABAP: MSNOTRUNNING did not start after 10:00 minutes. Giving up.
Connect to message server (st/3900) failed: NIECONN_REFUSED.
C:\usr\sap\FSM\SCS01\work
trc file: "dev_enqsrv", trc level: 1, release: "700"
Thr 2932 Thu Jun 26 14:01:51 2008
Thr 2932 stopAllThreads: stop Thread worker thread ...Thr 2932 done
Thr 2932 stopAllThreads: stop Thread Listener thread ...Thr 2932 done
Thr 2932 stopAllThreads: stop Thread IOThread_0 ...Thr 2932 done
Thr 2932 stopAllThreads: stop Thread ADM-thread ...Thr 2932 stopAllThreads: stop ADM-thread not implemented. Hard kill
Thr 2932 *** ERROR => ShmDelete: Invalid shared memory Key=1. http://shmnt.c 719
Thr 2932 *** ERROR => ShmCleanup: ShmDelete failed for Key:1. http://shmnt.c 793
Thr 2932 *** ERROR => ShmDelete: Invalid shared memory Key=82. http://shmnt.c 719
Thr 2932 *** ERROR => ShmCleanup: ShmDelete failed for Key:82. http://shmnt.c 793
Thr 2932 ***LOG GEZ=> Server shutdown (normal shutdown) http://encllog.cpp 493
Thr 2932 Enqueue server: normal shutdown
Ref.
My RAM is 3.33 GB
and SWAP Memory around 22 GB.
I've check requisition option in master installation and all result is pass to install.

INFO 2009-02-24 08:18:02.593
Execution of the command "E:\oracle\DEV\102\bin\lsnrctl status LISTENER" finished with return code 0. Output:
LSNRCTL for 64-bit Windows: Version 10.2.0.2.0 - Production on 24-FEB-2009 08:18:02
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=DEV.WORLD))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for 64-bit Windows: Version 10.2.0.2.0 - Production
Start Date                24-FEB-2009 07:07:02
Uptime                    0 days 1 hr. 11 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   E:\oracle\DEV\102\network\admin\listener.ora
Listener Log File         E:\oracle\DEV\102\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEV.WORLDipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEVipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=mm)(PORT=1527)))
Services Summary...
Service "DEV" has 1 instance(s).
Instance "DEV", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
INFO 2009-02-24 08:18:02.625
Switched to user: devadm.
INFO 2009-02-24 08:18:04.703
Execution of the command "E:\oracle\DEV\102\bin\lsnrctl status LISTENER" finished with return code 0. Output:
LSNRCTL for 64-bit Windows: Version 10.2.0.2.0 - Production on 24-FEB-2009 08:18:04
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=DEV.WORLD))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for 64-bit Windows: Version 10.2.0.2.0 - Production
Start Date                24-FEB-2009 07:07:02
Uptime                    0 days 1 hr. 11 min. 2 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   E:\oracle\DEV\102\network\admin\listener.ora
Listener Log File         E:\oracle\DEV\102\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEV.WORLDipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEVipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=mm)(PORT=1527)))
Services Summary...
Service "DEV" has 1 instance(s).
Instance "DEV", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
INFO 2009-02-24 08:18:07.750
Execution of the command "E:\oracle\DEV\102\bin\lsnrctl status LISTENER" finished with return code 0. Output:
LSNRCTL for 64-bit Windows: Version 10.2.0.2.0 - Production on 24-FEB-2009 08:18:07
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=DEV.WORLD))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for 64-bit Windows: Version 10.2.0.2.0 - Production
Start Date                24-FEB-2009 07:07:02
Uptime                    0 days 1 hr. 11 min. 5 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   E:\oracle\DEV\102\network\admin\listener.ora
Listener Log File         E:\oracle\DEV\102\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEV.WORLDipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEVipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=mm)(PORT=1527)))
Services Summary...
Service "DEV" has 1 instance(s).
Instance "DEV", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
INFO 2009-02-24 08:18:08.921
Execution of the command "E:\oracle\DEV\102\bin\lsnrctl status LISTENER" finished with return code 0. Output:
LSNRCTL for 64-bit Windows: Version 10.2.0.2.0 - Production on 24-FEB-2009 08:18:08
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=DEV.WORLD))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for 64-bit Windows: Version 10.2.0.2.0 - Production
Start Date                24-FEB-2009 07:07:02
Uptime                    0 days 1 hr. 11 min. 6 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   E:\oracle\DEV\102\network\admin\listener.ora
Listener Log File         E:\oracle\DEV\102\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEV.WORLDipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEVipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=mm)(PORT=1527)))
Services Summary...
Service "DEV" has 1 instance(s).
Instance "DEV", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
INFO 2009-02-24 08:18:58.421
Execution of the command "E:\oracle\DEV\102\bin\lsnrctl status LISTENER" finished with return code 0. Output:
LSNRCTL for 64-bit Windows: Version 10.2.0.2.0 - Production on 24-FEB-2009 08:18:58
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=DEV.WORLD))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for 64-bit Windows: Version 10.2.0.2.0 - Production
Start Date                24-FEB-2009 07:07:02
Uptime                    0 days 1 hr. 11 min. 55 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   E:\oracle\DEV\102\network\admin\listener.ora
Listener Log File         E:\oracle\DEV\102\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEV.WORLDipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEVipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=mm)(PORT=1527)))
Services Summary...
Service "DEV" has 1 instance(s).
Instance "DEV", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
INFO 2009-02-24 08:18:58.703
Switched to user: devadm.
INFO 2009-02-24 08:19:00.546
Execution of the command "E:\oracle\DEV\102\bin\lsnrctl status LISTENER" finished with return code 0. Output:
LSNRCTL for 64-bit Windows: Version 10.2.0.2.0 - Production on 24-FEB-2009 08:19:00
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=DEV.WORLD))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for 64-bit Windows: Version 10.2.0.2.0 - Production
Start Date                24-FEB-2009 07:07:02
Uptime                    0 days 1 hr. 11 min. 57 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   E:\oracle\DEV\102\network\admin\listener.ora
Listener Log File         E:\oracle\DEV\102\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEV.WORLDipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEVipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=mm)(PORT=1527)))
Services Summary...
Service "DEV" has 1 instance(s).
Instance "DEV", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
INFO 2009-02-24 08:19:06.281
Execution of the command "E:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe -testconnect" finished with return code 0. Output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
E:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20090224081904
E:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
E:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:44
E:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe -testconnect
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(DB) INFO: disconnected from DB
E:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: job completed
E:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20090224081906
INFO 2009-02-24 17:51:16.343
Execution of the command "C:\j2sdk1.4.2_19-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 0. Output:
java version "1.4.2_19-rev"
Java(TM) Platform, Standard Edition for Business (build 1.4.2_19-rev-b07)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_19-rev-b07, mixed mode)
Import Monitor jobs: running 1, waiting 111, completed 0, failed 0, total 112.
Import Monitor jobs: running 2, waiting 110, completed 0, failed 0, total 112.
Import Monitor jobs: running 3, waiting 109, completed 0, failed 0, total 112.
Loading of 'PCL2' import package: OK
Import Monitor jobs: running 2, waiting 109, completed 1, failed 0, total 112.
Import Monitor jobs: running 3, waiting 108, completed 1, failed 0, total 112.
Loading of 'PCL4' import package: OK
LSNRCTL for 64-bit Windows: Version 10.2.0.2.0 - Production on 24-FEB-2009 17:51:33
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=DEV.WORLD))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for 64-bit Windows: Version 10.2.0.2.0 - Production
Start Date                24-FEB-2009 07:07:02
Uptime                    0 days 10 hr. 44 min. 31 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   E:\oracle\DEV\102\network\admin\listener.ora
Listener Log File         E:\oracle\DEV\102\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEV.WORLDipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\DEVipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=mm)(PORT=1527)))
Services Summary...
Service "DEV" has 1 instance(s).
Instance "DEV", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully

Ecc6 installation issue..

hi every body ..
iam installing sap ecc6
after installing kernal ,oracle clint next asking for java component bs2005sr2..
but in my dump iam not found the files ...
..how can i get ?
is it available in online ?
how can i down load from internet
can u please help me in this issue..
thanks
regards
sadasiva

Hi,
You have to download the J2EE Component DVD from the Service Market place.
You can do it as below:
1. Goto service.sap.com\swdc >Installation and Upgrades>A-Z Index>Click 'E'>SAP ERP>SAP ERP 6.0>Installation and Upgrade-->Oracle.
In the Downloads tab, click the "BS 2005 SR3 Java Components" and download the DVD and give the path during your installation.
Hope it is useful to you.
Regards,
Satish Dhanalakoti

ECC6 installation error -port 21200

Hi All,
     while trying to install ECC6 i am getting the following errors
"load resource pool D:\DVD8_java\InsMaster\IM_WINDOWS_I386\resourcepool.xml"
"guiengine: no GUI connected; waiting for a connection on host ECC6, port 21200 to continue with the installation" even after setting the path as u have mentioned.
I am getting the below error when i tried using "sapinst SAPINST_SKIP_ERRORSTEP=true"
"guiengine: call to bind() for socket 21200 1780 failed . No error
103 guiengine.connection.failed 21200, 943
Exit status of child: 1 "
Could anyone tell me how to resolve this?
Regards,
Ravi

Hi Gaurav,
         Thanks for the reply but in the file there are lot of thing and i dont find any port having no "21200" could you please let me know how to find out the port no?
there are some entries starting with
rasadv              9753/udp
imip-channels      11320/tcp                           #IMIP Channels Port
directplaysrvr     47624/tcp                           #Direct Play Server
directplaysrvr     47624/udp                           #Direct Play Server
sapdp00 3200/tcp
Thanks,
Ravi

Hetrogeneous ECC6 Installation

Hi,
Client wanted to install ECC6 implementation on hetrogeneous environment. Database instalnce on HP-UX , Central instance on Windows2003. I know that technically it is possible but it is very complex . My questions is do we face any problems during installation / after that installation. What about future upgradation ? how simple ? what are the disadvantages if we select this senario.Also license ,software download on windows/unix We need to put all this to client .
Please suggest.
Thanks in advance
Kristene

Hi Ramesh,
You have entered several postings asking for the upgrade documentation, and always received a response that you have to BE a SAP CUSTOMER in order to login to the SAP website and retrieve this documentation. I do not believe that it is SDN policy to provide assistance to illegal SAP installations

IDES ECC6 Installations

Dear experts,
I have to install a IDES ECC 6 server in one of our servers. This is a Windows 2003 64bit Machine and DB is Oracle. Unfortunately I have download many things but couldnu2019t get it right. As you also know there are SO MANY things as IDES downloads I couldnu2019t figure out which is the correct installation and what more downloads I have to do.
Please help me to figure out what are the correct down loads, and where can I find them in the service market place.
Thank You
Thanura

Hi Thanura,
Please find the below path to identify your SAP ECC6 in the service market place.
https://service.sap.com/support / Installations and Upgrades - Entry by Application Group/SAP ERP 6.0/IDES-Version -
here you can find your component by ZIP number(starts with 5).
With regards,
Senthil Kumar.C

The javac executable is missing during ECC6 installation

Before I installing a fresh ECC6 on W2K3 64bit, I have installed Java version 1.4.2.18 and added in the environment variables.
But i hit problem at the stage of Java Development Kit. The error message was "Directory C:\j2sdk1.4.2_18 is not valid JDK directory:the javac executable is missing.

You need to use the correct JDK. If your system is 64bit you need to download the 64bit JDK.
See note 941595 - Download J2SE 1.4.2 for the x64 platform
Markus

Ecc6 installation Swap error

Hi all,
My system details :
HDD : 640 GB / RAM : 6GB
I have done partitions for installing ABAP + JAVA
D(Oracle) : 50GB
SAPDATA : 350 GB
General : 240GB
when i install sap it says sap system requirement doesnt match. SWAP atleast 1024 MB is needed.
2. while installing it stops near create datbase
in view log :
unable to get the name of domain controller for domain
account user = ora_c11_dba/administrators/ORA_C11_OPER does not exist
Can any one help me on this,where I am doing wrong.
Thanks,
Shashi

Hi,
Condition : SWAP SIZE
Result code : condiition not met
Severity : Medium
Message : for the selected services at least 10240MB swap space are recommeded
current value 1865MB
thanks

The transaction log for database 'ECC' is full + ECC6.0 Installation Failur

Guyz,
my ecc6 installation failed after 8 hours run with following error log snippet...
exec sp_bindefault 'numc3_default','SOMG.MSGNO'
DbSlExecute: rc = 99
(SQL error 9002)
error message returned by DbSl:
The transaction log for database 'ECC' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
(DB) ERROR: DDL statement failed
(ALTER TABLE [SOMG] ADD CONSTRAINT [SOMG~0] PRIMARY KEY CLUSTERED ( [MANDT], [OBJTP], [OBJYR], [OBJNO] ) )
DbSlExecute: rc = 99
(SQL error 4902)
error message returned by DbSl:
Cannot find the object "SOMG" because it does not exist or you do not have permissions.
ECCLOG1 data file has got 25GB initial size and growth was restricted to 10% (PROPOSED BY SAPInst)...
i'm assuming this error was due to lack of growth space for ECCLOG1 datafile...am i right? if so how much should i allocate memory for this log ? or is there any workaround ?
thanks in advance

Kasu,
If SQL is complaining that the log file is full then the phase of the install that creates the SQL data/log files has already occurred (happens early in the install) and the install is importing programs, config and data into the db.
Look at the windows application event log for "Transaction log full" events to confirm.
To continue, in SQL Query analyzer try:
"Backup log [dbname] with truncate_only"
This will remove only inactive parts of the log and is safe when you don't require point-in-time recovery (which you don't during an install).
Then, go to the SQL Enterprise manager, choose the db in question and choose the shrink database function, choose to shrink only the transaction log file and the space made empty by the truncate will be removed from the file.
Change the recovery mode in SQL Server to "simple" so that the log file does not grow for the remainder of the install.
Make sure you change the recovery mode back to "full" after the install is complete.
Your transaction log appears to have filled the disk partition you have assigned to it.
25GB is huge for a transaction log and you would normally not see them grow this large if you are doing regular scheduled tlog backups (say every 30-60 minutes) because the log will truncate every time, but its not unusual to see one get big during an install, upgrade or when applying hotpacks.
Tim

IDES ECC 6.0 Installation failed at IMPORT ABAP -- Urgent pls....

Hi Gurus,
ecc6 installation failed at IMPORT ABAP step (to be precise - 16th step out of 19 steps) while importing 'SAPSSEXC' package .....
snippets of following logs are below
1> IMPORT_MONITOR.LOG
2> SAPINST.LOG
3> SAPSSEXC.LOG
<h2>IMPORT_MONITOR.LOG</h2>
ERROR: 2008-01-08 01:32:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l
SAPSSEXC.log -loadprocedure fast' exited with return code -1,073,741,819.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-01-08 02:42:03 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is successfully completed.
WARNING: 2008-01-08 02:42:17
Cannot start import of packages with views because not all import packages with tables are loaded
successfully.
WARNING: 2008-01-08 02:42:17
1 error(s) during processing of packages.
INFO: 2008-01-08 02:42:17
Import Monitor is stopped.
<h2>SAPINST.LOG</h2>
WARNING 2008-01-08 02:42:21
Execution of the command "C:\j2sdk1.4.2_16-x64\bin\java.exe -classpath migmon.jar -showversion
com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs
F:\ECC6\InstExport1\EXP1;F:\ECC6\InstExport2\EXP2;F:\ECC6\InstExport3\EXP3;F:\ECC6\InstExp4\EXP4;F:
\ECC6\InstExport5\EXP5;F:\ECC6\InstExport6\EXP6;F:\ECC6\InstExport6\EXP7;F:\ECC6\InstExport6\EXP8;F
:\ECC6\InstExport6\EXP9;F:\ECC6\InstExport6\EXP10;F:\ECC6\InstExport6\EXP11 -installDir
C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS -orderBy "" -r3loadExe
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3
-monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code
103. Output:
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 16, failed 1, total 19.
Loading of 'SAPAPPL2' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.
ERROR 2008-01-08 02:42:23
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s)
import_monitor.java.log, import_monitor.log.
ERROR 2008-01-08 02:42:24
FCO-00011 The step runMigrationMonitor with step key
|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|in
d|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigratio
nMonitor was executed with status ERROR .
<h2>SAPSSEXC.LOG</h2>
(DB) INFO: D301T~A created
(DB) INFO: D345T created
(DB) INFO: D345T~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: import of D345T completed (6585 rows) #20080107180224
(DB) INFO: DSYST created
(DB) INFO: DSYST~0 created
(IMP) INFO: import of DSYST completed (54353 rows) #20080107194721
(DB) INFO: DYNPSOURCE created
(DB) INFO: DYNPSOURCE~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: import of DYNPSOURCE completed (190478 rows) #20080107205002
(DB) INFO: ENHSPOTCONTRACT~1 created
(DB) INFO: ENHSPOTHEADER created
(DB) INFO: ENHSPOTHEADER~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: import of ENHSPOTHEADER completed (4078 rows) #20080107205109
(DB) INFO: INDTEXT created
(DB) INFO: INDTEXT~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(DB) INFO: PERMISSION created
(DB) INFO: PERMISSION~0 created
(IMP) INFO: import of PERMISSION completed (112356 rows) #20080107214109
(DB) INFO: PERMISSION~IF created
(DB) INFO: REPOSRC created
(DB) INFO: REPOSRC~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
ANY POINTERS WILL BE HIGHLY APPRECIATED
THANKS IN ADVANCE

no...loading was not finished....it aborted with 'Retry', 'View Log', & Stop options...i retried with no luck...
this is 'Central system ' installation btw....
it failed with below error
ERROR 2008-01-08 02:42:23
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
<h2>IMPORT_MONITOR.LOG</h2>
INFO: 2008-01-07 16:33:26
Import Monitor is started.
CONFIG: 2008-01-07 16:33:26
Application options:
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=F:\ECC6\InstExport1\EXP1;F:\ECC6\InstExport2\EXP2;F:\ECC6\InstExport3\EXP3;F:\ECC6\InstExp4\EXP4;F:\ECC6\InstExport5\EXP5;F:\ECC6\InstExport6\EXP6;F:\ECC6\InstExport6\EXP7;F:\ECC6\InstExport6\EXP8;F:\ECC6\InstExport6\EXP9;F:\ECC6\InstExport6\EXP10;F:\ECC6\InstExport6\EXP11
installDir=C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS
jobNum=3
loadArgs= -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2008-01-07 16:33:26
List of packages with table structure: 'SAP0000'.
CONFIG: 2008-01-07 16:33:26
List of packages with views: 'SAPVIEW'.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
INFO: 2008-01-07 16:33:26 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2008-01-07 16:33:26
Data codepage 4103 is determined using TOC file 'F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL1' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL1.TSK MSS -l SAPAPPL1.log
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL0.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL0.TSK MSS -l SAPAPPL0.log
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPSSEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSEXC.TSK MSS -l SAPSSEXC.log
TRACE: 2008-01-07 16:33:28 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
TRACE: 2008-01-07 16:33:32 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
TRACE: 2008-01-07 16:33:32 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
INFO: 2008-01-08 00:15:00 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is successfully completed.
TRACE: 2008-01-08 00:15:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is started.
TRACE: 2008-01-08 00:15:27 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPAPPL2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL2.TSK MSS -l SAPAPPL2.log
INFO: 2008-01-08 00:15:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
TRACE: 2008-01-08 00:15:56 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is started.
TRACE: 2008-01-08 00:15:56 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDIC' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDIC.TSK MSS -l SAPSDIC.log
TRACE: 2008-01-08 00:15:58 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -loadprocedure fast
TRACE: 2008-01-08 00:16:02 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -loadprocedure fast
INFO: 2008-01-08 00:49:00 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is successfully completed.
TRACE: 2008-01-08 00:49:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is started.
TRACE: 2008-01-08 00:49:40 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPCLUST' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPCLUST.TSK MSS -l SAPCLUST.log
TRACE: 2008-01-08 00:50:11 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPCLUST' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -loadprocedure fast
INFO: 2008-01-08 00:53:51 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is successfully completed.
TRACE: 2008-01-08 00:54:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is started.
TRACE: 2008-01-08 00:54:40 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLEXC' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport3\EXP3\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLEXC.TSK MSS -l SAPSLEXC.log
TRACE: 2008-01-08 00:54:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLEXC' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -loadprocedure fast
INFO: 2008-01-08 01:02:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is successfully completed.
TRACE: 2008-01-08 01:02:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is started.
TRACE: 2008-01-08 01:02:50 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSRC' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSRC.TSK MSS -l SAPSSRC.log
TRACE: 2008-01-08 01:03:11 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSRC' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -loadprocedure fast
INFO: 2008-01-08 01:09:19 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is successfully completed.
TRACE: 2008-01-08 01:09:46 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is started.
TRACE: 2008-01-08 01:09:51 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPPOOL' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPPOOL.TSK MSS -l SAPPOOL.log
TRACE: 2008-01-08 01:09:55 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPPOOL' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -loadprocedure fast
INFO: 2008-01-08 01:14:03 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is successfully completed.
TRACE: 2008-01-08 01:14:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is started.
TRACE: 2008-01-08 01:14:18 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDOCU' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDOCU.TSK MSS -l SAPSDOCU.log
TRACE: 2008-01-08 01:14:21 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDOCU' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -loadprocedure fast
INFO: 2008-01-08 01:15:50 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is successfully completed.
TRACE: 2008-01-08 01:16:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is started.
TRACE: 2008-01-08 01:16:19 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSPROT' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSPROT.TSK MSS -l SAPSPROT.log
TRACE: 2008-01-08 01:16:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSPROT' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -loadprocedure fast
INFO: 2008-01-08 01:17:55 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is successfully completed.
TRACE: 2008-01-08 01:18:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is started.
TRACE: 2008-01-08 01:18:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLOAD' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLOAD.TSK MSS -l SAPSLOAD.log
TRACE: 2008-01-08 01:18:31 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLOAD' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -loadprocedure fast
INFO: 2008-01-08 01:18:43 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is successfully completed.
TRACE: 2008-01-08 01:18:46 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is started.
TRACE: 2008-01-08 01:18:48 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER.TSK MSS -l SAPUSER.log
TRACE: 2008-01-08 01:18:50 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -loadprocedure fast
INFO: 2008-01-08 01:20:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is successfully completed.
TRACE: 2008-01-08 01:20:15 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is started.
TRACE: 2008-01-08 01:20:16 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDDIM' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDDIM.TSK MSS -l SAPDDIM.log
TRACE: 2008-01-08 01:20:16 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDDIM' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -loadprocedure fast
INFO: 2008-01-08 01:20:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is successfully completed.
TRACE: 2008-01-08 01:20:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is started.
TRACE: 2008-01-08 01:20:45 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDFACT' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDFACT.TSK MSS -l SAPDFACT.log
TRACE: 2008-01-08 01:20:46 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDFACT' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -loadprocedure fast
INFO: 2008-01-08 01:20:51 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is successfully completed.
TRACE: 2008-01-08 01:21:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2008-01-08 01:21:22 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDODS' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDODS.TSK MSS -l SAPDODS.log
TRACE: 2008-01-08 01:21:23 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -loadprocedure fast
INFO: 2008-01-08 01:21:25 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is successfully completed.
TRACE: 2008-01-08 01:21:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER1' import package is started.
TRACE: 2008-01-08 01:21:47 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER1' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPUSER1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER1.TSK MSS -l SAPUSER1.log
TRACE: 2008-01-08 01:21:52 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER1' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPUSER1.cmd -dbcodepage 4103 -l SAPUSER1.log -loadprocedure fast
INFO: 2008-01-08 01:21:53 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER1' import package is successfully completed.
TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is started.
TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAP0000' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAP0000.TSK MSS -l SAP0000.log -o D
TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAP0000' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -loadprocedure fast
INFO: 2008-01-08 01:22:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
ERROR: 2008-01-08 01:32:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code -1,073,741,819.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-01-08 02:42:03 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is successfully completed.
WARNING: 2008-01-08 02:42:17
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2008-01-08 02:42:17
1 error(s) during processing of packages.
INFO: 2008-01-08 02:42:17
Import Monitor is stopped.

Sapinst needs to log you off in order to reliably continue the installation

Hi,
When I was doing ECC6 installation on windows, just after choosing the installation mode (Typical, Custom) sapinst prompts for user logoff. Below is the some error message
"sapinst needs to log you off in order to reliably continue the installation" then after I choose ok automatically user got logged off and I logged in again and the installation continued as usually.
But my qustion is why it is happened. Please let me know the reason for this.
Thanks in advance.

Hi,
Yes...Sunil is correct.
SAPinst uncars many files into the installation directory and for then to take effect we need to log off and on.
Regards,
Nirmal.K

ECC6 on DB2 9

Hello All,
We are going to install ECC6 on DB2 9.1 on Windows.
I am newbie to DB2. Can anybody tell the important guidelines to follow for the ECC6 installation ?
Regards,
Vivdha

Hi Vividha,
You can check the following link for better info.
http://service.sap.com/installation
Regards,
Hari.

Experiences on SAP Best Practise packages?

We are considering applying a specific SAP Best Practise package on top of ECC6. It will be a new ECC6 installation.
I have read the BP faq pages http://help.sap.com/bp_bw370/html/faq.htm and read note 1225909 - How to apply SAP Best Practices - and the specific note and the specific installation guide for required Best Practise package.
I understand that applying a BP package is something not that easy but should speed up the implementation process.
If you have been participating in a project that implemented SAP Best Practises on ERP, would you please share your experiences with me.
Here are some topics for discussion:
(BP=SAP Best Practise package)
BP implementation could make constraints to your future EHP or SP upgrades, while BP is tightly linked to certain EHP and SP-level?
SAP support?
Installation process including config steps according BP installation guide is longer than usual, while there can be multiple activation and configuration steps done by others than basis consultants?
BPs are country dependent. What if your application is used multinationally?
What if you later find BP unneccessary?
generate difficulties in the beginning but did considerably speed up reaching the final goal compared to ECC6 without BP.
traps to fall in?
typical issues that basis staff has to notify when preparing/installing a ERP system to be with BP?
positive/negative things
I am not saying above statements are true or false. Just wanted to charge you giving comments.
Br: KimZi
Edited by: Kimmzini Siewoinenski on Aug 11, 2009 8:35 PM

Hi,
Make sure your web service URL correct in Live Office connection and also in Xcelsius data manager.
Did you check all connection in refresh button proprties? you may try selecting "Refresh after component are Loaded" in Refresh button properties Behavior tab.
I think Xcelsius refresh are serial refresh so it may be possible that first component refresh is still in progress but you are expecting other component to refresh.
Click on "Enable Load Cursor" in data manager's Usage tab, it will give you visibility of refresh. If anything refreshing you will see hour glass.
Cheers

ECC6 Installation

Similar Messages

Maybe you are looking for