![]() Issue #2: Instant Client doesn't have TNSPING, and sometimes doesn't include SQL*Plus. or, the PATH didn't resolve the executable, and you get no results.Įither way, you are blind to possibly multiple client installations. ![]() either your PATH successfully resolves the executable and you get ONE version result.If you are relying on the PATH and running a utility like SQLPLUS or TNSPING you'll have one of two unacceptable results: Super super helpful, honestly probably one of the nicest features since they added the Powershell Step.Issue #1: Multiple Oracle clients are installed.Ī very common issue I see in my environment is that I see both workstations and (app) servers with multiple Oracle clients, sometimes as many as four, and possibly with different versions and architectures. 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.Īnother 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. That will cleanup the files off the local machine and leave no trace behind for you. Then after that step Create another powershell step with: Remove-Item $filecopysteppath -Recursive $filecopysteppath\client_install.rsp", "-Silent", "-nowait" "-force" Then you would create a second Powershell step to: Start-Process $filecopysteppath\setup.exe -ArgumentList "-IgnoreSysPrereqs", "-ResponseFile. You could do a File-Copy step to put that setup.exe and the response file on the local machine you are deploying too. You could also make it a bit more complex, depending on how ambitious you feel.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |