cancel
Showing results for 
Search instead for 
Did you mean: 

How much time does the ESS import take?

former_member188498
Active Participant
0 Kudos

Hi,

How much time does import of ESS into NWDI take?

I have selected following files for import yesterday:

SAP-JEE

SAP-BUILDT

SAP-ESS

SAP-JTECHS

SAPPCUI_GP

and looked at it today and it is still importing.

In CMS Transport Studio State column displays message: Import running.

Any ideas why it takes so long?

Regards,

Ladislav

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Ladislav,

it doesn't take this long.

clear the database logs and then import

Thanks

Bala Duvvuri

Answers (2)

Answers (2)

Former Member
0 Kudos

The configuration step "Import Software Component Archives" takes very long.

It is normal that for the "Sandbox" track this steps runs roughly ten minutes depending on your system performance. For other track templates this time may increase depending on the number and size of SCAs to import.

Typical reasons for long lasting imports are an "idleing" CBS (see above) or performance problems with the database (statistics not updated, log volumes running out of space etc.). A long running import may indicate general performance problems in your server setup (see note 889038).

Bhavin

Former Member
0 Kudos

Ladislav,

You are importing SAP_ESS which is huge package. Definately it takes time, I would say hours and it will also depend on your system as well. There is no specific answer to it. You can check CBS Build Space for status.

Click on "COMPONENT BUILD SPACE" and you will see whats the status with you track and how many request are queeued up.

Bhavin

former_member188498
Active Participant
0 Kudos

Hi,

it seems requests are queued all the time and import fails because of that.

Regards,

Ladislav

Former Member
0 Kudos

Ladislav,

are you importing all the files at a time or one by one .I guess you are importing EP_BUILDT also.

try to follow some order through out the process

EP_BUILDT

SAP-BUILDT

SAP-JEE

SAP-JTECHS

SAPPCUI_GP

SAP-ESS

Thanks

Bala Duvvuri

former_member188498
Active Participant
0 Kudos

Hi,

I have imported files one by one in this order:

SAP-JEE

SAP_BUILDT

SAP_JTECHS

SAPPCUI_GP

SAP_ESS

Is this order correct?

I didn't import EP_BUILDT - is it required?

I have checked the CBS logs and there is one broken DC in SAPPCUI_GP compartment

in the pcui_gp/isr development component.

The build log contains this error:

[javac] Compiling 316 source files to /usr/sap/PDI/JC26/j2ee/cluster/server0/temp/CBS/3/.B/22/t/0C0A08ED5B9ACC3F0164FD6D8A0DB879/classes

[javac] ERROR: /usr/sap/PDI/JC26/j2ee/cluster/server0/temp/CBS/3/.B/22/t/0C0A08ED5B9ACC3F0164FD6D8A0DB879/gen_wdp/packages/com/sap/pcui_gp/isr/isrprocessevent/FcISRProcessEvent.java:470: cannot resolve symbol

[javac] ERROR: symbol : method getWebContextAdapter ()

[javac] ERROR: location: interface com.sap.tc.webdynpro.services.task.ITask

[javac] ERROR: .getCurrentTask()

[javac] ERROR: ^

[javac] WARNING: Note: Some input files use or override a deprecated API.

[javac] WARNING: Note: Recompile with -deprecation for details.

[javac] 1 error

Maybe because of this error the requests are queued?

How to fix this?

Regards,

Ladislav

Former Member
0 Kudos

Ladislav,

yes EP_BUILDT is required.

Thanks

Bala Duvvuri

former_member188498
Active Participant
0 Kudos

Hi,

I have restarted the whole import process from the beginning.

The problem is that the import (cbs make step) hangs with the message:

20090226130230 Info :Starting Step CBS-make at 2009-02-26 13:02:30.0144 +1:00

20090226130230 Info :wait until CBS queue of buildspace PDI_ESSTrack_D is completely processed, before starting the import

20090226130230 Info :waiting for CBS queue activity

20090226130300 Info :build process already running: waiting for another period of 30000 ms

20090226130330 Info :build process already running: waiting for another period of 30000 ms

20090226130401 Info :build process already running: waiting for another period of 30000 ms

20090226130431 Info :build process already running: waiting for another period of 30000 ms

Regards,

Ladislav