cancel
Showing results for 
Search instead for 
Did you mean: 

Import Java Dump is taking long time...

Former Member
0 Kudos

I am installing SAP ERP 6.0 Dual Stack on Win Server 2008 / MaxDB. The Import Java Dump is taking too long . It seems even the logs will only be updated once the installation completes this phase or it gives any error.
Can anyone suggest regarding this.

Thanks

HARISH

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Nicholas,

After customizing the PAGING SIZE to Minimum : 24000 MB and Maximum : 72000 MB ,

it worked and has crossed the IMPORT JAVA DUMP phase.

Thanks a ton...

Cheers ....

HARISH

nicholas_chang
Active Contributor
0 Kudos

please check on your hw resources, cpu, especially memory, to ensure no bottleneck.

Former Member
0 Kudos

Hi Nicholas,

Thanks for the quick reply.
I have checked the Memory. It is more than sufficient.
Though the execution in running in the this phase from the past 16 hours but now I can see the status bar showing info regarding the various processes running.
So all going well for now .

Thanks

Former Member
0 Kudos

Hi ,

Its been 4 days .DB got disconnected . I have made it online. It is still runnning IMPORT JAVA DUMP.

As far as memory is conecrned the total drive size where I am installing the product is 931GB and the total paging size for all drives is : 16318MB.

Please guide what else can I check ?

Thanks ....

nicholas_chang
Active Contributor
0 Kudos

Hi,

Could you please check the log space? and ensure no filesystem full. Also, increase the swap sapce to at least 20480MB and see how it goes.

Besides, please check the available log.

Cheers,

NIcholas Chang

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

I guess you meant 2048, correct?

nicholas_chang
Active Contributor
0 Kudos

Hi Benny,

Paging should be at least 20GB (20480MB) or twice the size of physical memory.

Cheers,

Nicholas Chang

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

Yes, I forgot this is 2012 and we are now using RAM in large scale ;-)When I used to do this regularly it was a different case *g*

Thanks,

Benny