In addition to Jordan's recommendations, have you created an oraInventory? I haven't automated the OUI on Windows but generally, on *nix platforms you need to manually create an empty OUI inventory with the appropriate ownerships and permissions. (You can work this out from a successful install but on a Linux-based host it would be similar to:
# Make an ORACLE_BASE mkdir -p /u01/app/oracle/ chown -R oracle:oinstall /u01 # Create the Oracle Inventory cat > /etc/oraInst.loc <<EOF inventory_loc=/u01/app/oracle/oraInventory inst_group= EOF chown oracle:oinstall /etc/oraInst.loc chmod 664 /etc/oraInst.loc Also, as you've been advised more than once, check the OUI logs. This is slightly older 11g documentation but the general gist still applies: https://docs.oracle.com/cd/B28359_01/em.111/b31207/b_oui_appendix.htm#CHDBDFIF1 Cheers, Will. On Sun, 23 Sep 2018 at 21:10, 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/CAKtKohRUDDqAnhXcD8JowZ4Sp8DuKS-dA3zwSW%3DQnPGwJfghsA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
