how are you calling the installer? we've done oracle silent installs many times and i don't think we've run into this problem.
I am calling the installer using their documented silent install procedure.
I first start by recording the installation to obtain a response file setup.exe -record -destinationFile C:\temp\response.rsp. I then package the response file into a BLPackage and run a command executing setup.exe -responseFile C:\temp\response.rsp -silent -noWait.
The noWait switch closes the console window that it spawns after the installation is complete.
I've always done this as 'custom software' not a blpackage, and the install commands were the same. though I don't remeber if I had something after the install like you do.
where are you running that command? as an 'external command' in the blpackage? or somewhere else?
I am running this via an external command in the blpackage.
The reason I also opted for the BLpackage is that the files were already located on a mounted network file system and I wanted to point to the directory and run them from there instead of loading all of the data to the file depot.
The reason I have multiple jobs is that I decided to package each of the patches separately. Two of the patches also run into this same process.
I was thinking about creating a batch job look for the java.exe process that is run as BladeLogicRSCD and just have it loop every 15 seconds until the process could no longer be found, sort of as a placeholder just to keep the deploy job alive. I'm not sure if there is a better method than this, but I believe that might work.
You can do a 'mount at staging' network deploy type for the custom software (or msi, rpm etc) objects in the cm. this would actually run the nfs mount command at the run time of the deploy.
you could add a while loop in the external command to wait for the process to exit.