cancel
Showing results for 
Search instead for 
Did you mean: 

ecc6:import abap last more than 70 hours

Former Member
0 Kudos

windows 2003 ECC6SR3+sql server 2005

there is no error when i install it. but the phase import abap last more than 70 hours. the log shows that the last excuting run on the day the phase import abap begun.

i think it means that the installation has not activited more than 60 hours.

is there anyone meet the problem?

i need your help!

thank you !

best regards!

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Ye,

Check your log files with last updated time.

Sorting Process as per CPU utilization is also good ideam.

Cheers

Deepanshu

Former Member
0 Kudos

hi Deepanshu and Markus

i had been watch at the task manager. from i found the installation was stopped, these columns of installation process has no changed.

CPU, mem Usage, I/O reads bytes, I/O wites bytes.

i had checked the last update time with the log file. it was updated on the day the import abap phase begun.

thank you for your advice!

best regards!

Former Member
0 Kudos

Hi Yang,

Is it still under same status

Cheers

Deepanshu

Former Member
0 Kudos

Hi Deepanshu,

The same status. And it has not been changed.

Best regards!

Former Member
0 Kudos

Hi Yang

Check for log files and your file system correctly created or not.

Cheers

Deepanshu

former_member603052
Contributor
0 Kudos

Hi Ye Yang,

If u think the installation is stopped,You close the SAPInst window and again start the installation and select Continue as old installation and try. Hope ur installation goes smooth.

Regards,

Kalyan

markus_doehr2
Active Contributor
0 Kudos

I would open task manager and sort the processes by CPU and check if the system is still doing something. Then check, as already suggested, the logfiles in the installation directory.

Markus

Former Member
0 Kudos

First, check your installation directory and search for the last file updated (this should have some information about what is going on). Another thing to check is to make sure the DB log has not filled up and/or that the log archives have filled up the backup partition.

Hope that helps.

J. Haynes