Oracle Configuration monitoring graphical interface does not come up with a workaround

Root user, execute Xhost + and then switch to Oracle user run NETCA

DISPLAY

On the Linux/unix class operating system, display is used to set where the graphic will be displayed. Direct login to the GUI or login command line interface using STARTX to start the graphics, display environment variables will be automatically set to: 0:0, you can open the terminal, the output graphics program name (such as Xclock) to start the program, the graphics will be displayed on the local window, Enter printenv on the terminal to view the current environment variables, the output results are as follows:
display=:0.0
Use Xdpyinfo to view more detailed information about the current display.
The display environment variable format is as follows Hostname:displaynumber.screennumber, we need to know that on some machines, there may be multiple display devices sharing the same set of input devices, such as connecting two CRT monitors on a single PC, But they only share the use of a keyboard and a mouse. This set of display devices has a common displaynumber, and each individual device in this set of display devices has its own separate screennumber. Both Displaynumber and Screennumber are zero-based numbers. In this way, for our ordinary users, Displaynumber, Screennumber are all 0. Hostname refers to Xserver host name or IP address, the graphics will be displayed on this machine, can be started the graphical interface of the Linux/unix machine, can also be installed exceed, x-deep/ 32 Xserver Windows machines that run on Windows platforms. If host is empty, it means that Xserver is running natively, and the graphics program (xclient) uses a UNIX socket to connect to Xserver instead of TCP. When connecting using TCP, Displaynumber subtracts the value of 6000 for the connected port, and if Displaynumber is 0, it is connected to port 6000; When using the UNIX socket connection, the path of the connected UNIX socket is represented, and if Displaynumber is 0, it is connected to/tmp/. X11-unix/x0. Screennumber is almost always 0.
If you use SU Username or su-username to switch to another user, and use the command
Export display=:0.0
When you set the display environment variable, you receive the following error when you run a graphics program (such as Xclock):
Xlib:connection to ': 0.0 ' refused by server
XLIB:NO protocol specified
Error:can ' t open display:: 0.0
This is because Xserver does not allow graphics for other users to appear on the current screen by default. If you need other users ' graphics to appear on the current screen, you should perform the following commands with the user currently logged in, that is, the user before switching identities
Xhost +

Xhost is used to control access to the X server, this command will allow other user-initiated graphics programs to display graphics on the current screen. Usually when you run an application on HostB from Hosta to HostB, as an application, Hosta is the client, but as a graph it is shown on hosta and Hosta Xserver is required, so hosta is
Server. So before logging in to HostB, you need to run Xhost + on Hosta to enable other users to access Hosta Xserver.
Xhost + is to enable all users to access Xserver.
Xhost + IP enables users on the IP to access xserver.
Xhost + Nis:[email protected] enables NIS users on domain to access
Xhost + inet:[email protected] enables inet users on domain to access.
Between 2 Linux machines, if you set up a server-side configuration file/etc/ssh/sshd_config contains
X11forwarding No
The client configuration file/etc/ssh/ssh_config contains
ForwardX11 Yes
The display environment variable is automatically set after SSH from the client to the server side, allowing graphical programs executed on the server side to display graphics on the client. Viewing the environment variables on the server is displayed as follows (this result is different from the same time)
display=localhost:10.0
With NETSTAT-LNP on the client, you can see that the program is listening on port 6010.
TCP 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN 4827/1
If you want to allow graphics programs on the remote machine to display graphics on the xserver of the local machine, you need to set the xserver of the local machine to listen for the appropriate TCP port, in addition to setting the display environment variable for the far end machine. Today's Linux systems are not listening to TCP ports by default for security reasons. You can modify the/ETC/X11/XINIT/XSERVERRC file by modifying the
exec/usr/bin/x11/x-dpi 100-nolisten TCP
Revision changed to
exec/usr/bin/x11/x-DPI 100
Allows you to start listening on a TCP port when you start a drawing directly using STARTX.
Modify the/ETC/KDE3/KDM/KDMRC to
Serverargslocal=-nolisten TCP
Revision changed to
Serverargslocal=
When KDM is allowed as the display manager, the corresponding TCP port is listened to when the session is started.
Modify/etc/gdm/gdm.conf, add in [Security] section
Disallowtcp=false
Or, in the login window, select "Options", "Configure Login Manager ..." Security page, Cancel "Deny TCP connections to Xserver", allow GDM as the display manager, startup will Listen to the appropriate TCP port when you speak.

Common Errors and workarounds

Cause:
X-windows emulation is no yet correctly configured or is being mis-used.
Solution:
1.Make sure that ' DISPLAY ' is set properly as either:
<ip address of the DBA desktop pc>:0.0
Or
Note:in This example,ip_address/hostnameis the host name or IP address of the system so you want to use to display Oracle Universal Installer (Your workstation or PC).
eg. [Email protected] ~]# Xhost +
Access control disabled, clients can connect from any host
[Email protected] ~]# su-oracle
[Email protected] ~]$ export display=192.16.2.98:0.0
[Email protected] ~]$ CD database/
[Email protected] database]$./runinstaller
Starting Oracle Universal Installer ...
Checking Installer Requirements ...
Checking operating system version:must be redhat-3, SuSE-9, redhat-4, UnitedLinux-1.0, asianux-1 or asianux-2
Passed
All installer requirements met.
Preparing to launch Oracle Universal Installer from/tmp/orainstall2009-03-05_03-36-28pm. Please wait ... [Email protected] database]$ Oracle Universal Installer, Version 10.2.0.1.0 Production
Copyright (C) 1999,2005, Oracle. All rights reserved.

2. Oracle Customer support have seen instances where use of the Unix/linux "su" command, even "su-oracle" have caused this "Can ' t connect to X11 Window Server" error. Therefore, sure is logged on as the Oracle account. Log directly into the install session. Do not use any variety of "su".
Use of Oracle Log on, not "su-oracle"
eg. [Email protected] database]$./runinstaller

3.Oracle Customer support have seen instances where the incorrect "ulimit" setting for number of files (aka "-N", aka "Nofi Les ") has caused the" Can ' t connect to X11 Window Server "error. Therefore, please be sure this your values for ' nofiles ' in the output of ' ulimit-a ' is at least 65536.

Note: The first 2 methods only need to satisfy one can avoid this error: directly with the Oracle login, cannot su-oracle or set Display=ip_address_that you want to the use of the display Oracle Univ Ersal installer:0.0

No.35 xhost:unable to open display ""
Log in as root user
Enter the command Xdpyinfo, recording the name of the display: After the string, such as name of display:127.0.0.1:1.0
Executing the Xhost + command (which makes it accessible to all customers)
The return information is:
Access control disabled,clients can connect from any host
If Xhost + cannot be executed, you can enter the command export display=:0 Execute
Then execute Xhost +
Xhost + IP (name indicates that the IP machine can use the service)
2. Log in as Oracle user
If the name of display after Xdpyinfo is executed under the previous root login: The string after is 127.0.0.1:1.0
Then execute the export display=:1.0 under the Oracle user
Then execute the xdpyinfo command, if you can get a message stating that you have succeeded
This will solve the xhost problem of installing Oracle under Linux.
If it is still unsuccessful, make sure that StartX is turned on.

XDMCP is disabled

Enable XDMCP on Red Hat Linux

In RHEL, by default, only the local host is enabled for X 11. You need to be able to connect from the external box to edit the file/etc/gdm/custom.conf. The default setting for RHEL is

Disallowtcp=yes
Which should be changed to "false"
To enable XDMCP Some users need you to enable it.
[XDMCP]
Enable=true
After restarting the X 11 server using the command
Init 3 && Init 5
If in addition you want to provide the ability to log in as root, you need the Security section, as shown below
[Security]
Disallowtcp=false
Allowremoteroot=true
If a firewall is enabled, you need to open several ports
177 (UDP) port and Port 6000-6005 (TCP)
If you are using Gnome to open TCP port 16001 and TCP 35091 in two directions.
-A rh-firewall-1-input-m state--state new-m tcp-p TCP--dport 16001-j ACCEPT
-A rh-firewall-1-input-m state--state new-m udp-p UDP--dport 177-j ACCEPT
-A rh-firewall-1-input-m state--state new-m tcp-p TCP--dport 35091-j ACCEPT
-A rh-firewall-1-input-m state--state new-m tcp-p TCP--dport 6000:6005-j ACCEPT

Oracle Configuration monitoring graphical interface does not come up with a workaround