See https://stackoverflow.com/questions/53244913/oracle-12c-client-install-hangs-silent-unattended
On Tuesday, September 25, 2018 at 1:26:14 AM UTC+12, anonymus wrote: > > can you please share the blog link. (just for later reference in this > thread) > > On Monday, September 24, 2018 at 4:09:58 PM UTC+5:30, Isha G wrote: >> >> I have found a blog actually and I am working on it. >> Thanks a lot for all the suggestions. >> >> On Mon, Sep 24, 2018 at 3:46 PM Isha G <[email protected]> wrote: >> >>> Hi, >>> Same thing happens with remote Powershell and I understand this may not >>> be Ansible issue. >>> Any suggestions? From Oracle 12 c side >>> >>> On Mon, Sep 24, 2018 at 3:30 PM Isha G <[email protected]> wrote: >>> >>>> Hi, >>>> Thanks for the replies. >>>> I have the same issues with the with remote powershell. >>>> I still see 0% CPU utilization. I am not sure how to move forward. I am >>>> still seeing the same issues. >>>> >>>> On Mon, Sep 24, 2018 at 1:40 AM Jordan Borean <[email protected]> >>>> wrote: >>>> >>>>> It's very hard for us to help you in this situation but basically it >>>>> boils down to you running these checks and finding out what is causing >>>>> the >>>>> program to hang; >>>>> >>>>> * Use something like procexp to see if the setup.exe process is >>>>> spawning any child processes that are running in the background >>>>> * Ensure your quoting is not screwing up the install process, in your >>>>> first example you have quoted the responseFile path arg but you don't >>>>> need >>>>> this quoted. >>>>> * Try and replicate this through another WinRM session like >>>>> PowerShell's Invoke-Command or Enter-PSSession >>>>> * Use Ansible become on the task to escape the boundary of the WinRM >>>>> logon and run through a psuedo-interactive process >>>>> * See if there is any logging you can enable on the Oracle installer, >>>>> this could tell you the stage it is up to and what it may be waiting on >>>>> >>>>> As for why you cannot see it when running through Ansible, Ansible >>>>> uses a completely separate session to run your processes as any normal >>>>> interactive logon. This is not unique to Ansible but how Windows treats >>>>> things like network logons such as WinRM. >>>>> >>>>> Thanks >>>>> >>>>> Jordan >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Ansible Project" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/ansible-project/e2e0f876-862d-4b74-a045-93f0f74355fd%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/ansible-project/e2e0f876-862d-4b74-a045-93f0f74355fd%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/4f6f55ff-b492-46a4-9d09-31603c51226d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
