1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Oracle Client Installation

Avatar
Ward Galanis

Hello,

Trying to install Oracle Client 11 G using package with the following command line (identifying stuff removed)

\\servername\oracleclient\setup.exe -ignoreSysPrereqs -ignorePrereq -responseFile \\servername\oracleclient\response\client_install.rsp -silent -nowait -force.

The Include Entire Directory box is checked as it will fail 100% if not checked.

This works from the command line on a local machine and works "sometimes" as a package.  Given that I get successful installations some of the time I am wondering what I am missing.  I have over 200 machines to deploy and it is starting to look like I'll need my walking shoes and a USB stick.

I suspect that part of the problem is that setup installs its own JRE and then runs in another process.

0

Comments

4 comments
Date Votes
  • Avatar
    Bouma, Colby

    Try using a Command step instead of an Install step.

    0
  • Avatar
    Stephen Valdinger

    Hmmm. You could do a command step for this. You could also make it a bit more complex, depending on how ambitious you feel. You could do a File-Copy step to put that setup.exe and the response file on the local machine you are deploying too. Then you would create a second Powershell step to:

    Start-Process $filecopysteppath\setup.exe -ArgumentList "-IgnoreSysPrereqs" , "-ResponseFile .$filecopysteppath\client_install.rsp" , "-Silent" , "-nowait" "-force"

     

    Then after that step Create another powershell step with:

    Remove-Item $filecopysteppath -Recursive

    That will cleanup the files off the local machine and leave no trace behind for you. It *should* work as described, but I don't have a Powershell window handy at the moment to make sure those switches/syntax is 100% correct.

     

    Another nice thing about using the Powershell steps is that you can wrap your code in a Try/Catch block to capture the $_.Exception output from powershell if there is an error, and you'll be able to review it in Output.log for the deployment. Super super helpful, honestly probably one of the nicest features since they added the Powershell Step.

    0
  • Avatar
    Ward Galanis

    Since I had the free version, the command step is not available (that is changing shortly).  I solve my problem by creating setup.bat with the command line inside that and running the batch file.  I kept the copy files to machine intact as the Oracle setup is rather piggy when it comes to taking up file space.  A consequence of running in java, I imagine.

    0
  • Avatar
    Stephen Valdinger

    Glad you got it working. You'll definitely enjoy having a paid version of PDQ!

    0