CBS make fails of SAP_ESS SCA file fails in NWDI 7.0 SP14 after ~4 hours

Question

Hi,
    We wish to do ESS customization in our new NWDI 7.0 SP14 system (on RHEL 4.7). Importing the SAPESS09P_3-20000512.SCA (after importing its dependicies) in a ESS track completed in the Repository-import phase but fails in the next CBS-make phase with a timeout of 14430 seconds (~4 hours). The exact error i am getting is listed below. Is their some way to bump up this timeout value?
   I am new to this and am very interested in what more experienced folks suggest about this.
thanks in advance,
Steven McElwee, Duke University
20080224153849 Info   :Starting Step CBS-make at 2008-02-24 15:38:49.0310 -5:00
20080224153850 Info   :wait until CBS queue of buildspace NDI_XSSTrack_D is completely processed, before starting the import
20080224153850 Info   :waiting for CBS queue activity
20080224153921 Info   :build process already running: waiting for another period of 30000 ms
20080224153951 Info   :build process already running: waiting for another period of 30000 ms
20080224154021 Info   :build process already running: waiting for another period of 30000 ms
.......... lots more messages
20080224193917 Info   :build process already running: waiting for another period of 30000 ms
20080224193947 Info   :build process already running: waiting for another period of 30000 ms
20080224194017 Info   :no changes on the CBS request queue (NDI_XSSTrack_D) after a waiting time of 14430000 ms
20080224194017 Fatal  :The request queue is not processed by the CBS during the given time intervall => TCS cannot import the request because queue is not empty
20080224194017 Fatal  :Please look after the operational status of the CBS.
20080224194018 Info   :Step CBS-make ended with result 'fatal error' ,stopping execution at 2008-02-24 19:40:18.0480 -5:00

Answer 1

Well, I restored our NWDI system from an archive backup taken just prior to defining the new XSS Track. I then carefully followed the ESS NWDI Cookbook instructions to create the XSS Track and to import everything (SAP-JEE, SAP-BUILDT,  SAP-JTECHS, and SAP-PCUI) except for SAP_ESS. I then archived to tape everything again. That was yesterday.
Today, I kicked off the import of SAP_ESS. So far, so good- it imported into the repository and is now in the process of Activation in the CBS. There have been no problems with threads stuck in the CBS queue in the QUEUED state.
Of course, it has been only 2 hours so far.
About the CBS properties for BUILD_TOOL_JDK_HOME,
JDK_HOME_PATHS and idleStart. Aside from idleStart, i have left them unchanged. But will keep this in mind should the previously mentioned wierd CBS behavior return.
Disk space is a little tight right now. I had 4 GB free before the import of SAP_ESS. Now i have 2 GB free, which seems to be holding. We have a script running to archive and delete the oracle redo logs since they are being generated at a pretty fast rate.
Once i know one way or the other about the success of this, i will post a message.
thank you everyone for your help so far!
Steven