Re: Unable to execute runInstaller

From: Jack van Zanen <jack_at_vanzanen.com>
Date: Fri, 23 Oct 2015 14:49:35 +1100
Message-ID: <CAFeFPA_9ObenrJS90y9uBEgPBWG4g42nzGKGnax9DyLandrghw_at_mail.gmail.com>



We run similar way with putty and x-tunneling never an issue When we log on using our own account the DISPLAY is automatically set correctly
Check this setting.
When we su to oracle we need to use that setting and it does not always end in "0.0"

Jack van Zanen



This e-mail and any attachments may contain confidential material for the sole use of the intended recipient. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please contact the sender and delete all copies. Thank you for your cooperation

On Fri, Oct 23, 2015 at 1:19 AM, Chris Taylor < christopherdtaylor1994_at_gmail.com> wrote:

> You need to make sure "xclock" or "xeyes" works to verify the server is
> able to talk to your workstation.
>
> So like this:
>
> - Run Hummingbird Exceed
> - open a terminal window
> - export DISPLAY=<IPv4_IP_addr>:0.0
> - execute xhost +
> - open a putty session
> - ​RUN xeyes or xclock to verify you can bring up an xwindow
> program correctly​
>
> - su to oracle
> - export DISPLAY=<IPv4_IP_addr>:0.0
> - ​RUN xeyes or xclock again now to verify you can still bring up
> an xwindow program correctly​
>
> - change to appropriate directory
>
> I'm going to bet that xeyes/xclock will fail also after you sudo into
> oracle but I bet it works correctly prior to you doing the su.
>
>
> On Thu, Oct 22, 2015 at 8:54 AM, Sandra Becker <sbecker6925_at_gmail.com>
> wrote:
>
>> I am trying to install EE 12c. I receive the error
>> "*Could not execute auto check for display colors using command
>> /usr/bin/xdpyinfo. Check if the DISPLAY variable is set. Failed* "
>>
>> My MOS account is still pending for my new employer, so I can't
>> research/open SR there. I've googled and found several suggestions, none
>> of which solved my problem. Other DBAs on the team can execute
>> runInstaller on the same server. What I've tried so far
>>
>> - Run Hummingbird Exceed
>> - open a terminal window
>> - export DISPLAY=<IPv4_IP_addr>:0.0
>> - execute xhost +
>> - open a putty session
>> - su to oracle
>> - export DISPLAY=<IPv4_IP_addr>:0.0
>> - change to appropriate directory
>> - ./runInstaller
>> - Run Xming (after ensuring configuration through XLaunch)
>> - open a putty session
>> - su to oracle
>> - export DISPLAY=<IPv4_IP_addr>:0.0
>> - change to appropriate directory
>> - ./runInstaller
>>
>> I get the same error with both processes no matter what server I am on.
>> I have watched another team member execute it on two different servers.
>>
>> Question:
>>
>> 1. Am I doing something incorrectly in my process? I followed what
>> the other DBA gave me.
>> 2. Could this be a firewall or account configuration issue specific
>> to my/my PC?
>>
>>
>> --
>> Sandy B.
>>
>>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Oct 23 2015 - 05:49:35 CEST

Original text of this message