This content has been marked as final. Show 9 replies
Gyanprakash Pandey wrote:Those have been verified and ruled out as relevant.
Check your hostfile and hostname. I've faced this issue and root cause was /etc/hosts file has incorrect hostname and ip mappings.
As stated Xterm is working on all the others such runInstaller, owm, and so on, except on ua.
I have used the truss to trace ua and that does not generate the helpful info for this issue.
I wonder that whether any other tools could be used for this troubleshoot. If any , please let me know.
I have exactly the same problem and same error - installed FMW on Solaris 10 box, ran the config.sh from same MW ORACLE_HOME/bin directory successfully via x-server to configure a domain without any issue, xclcok works fine.
I tried putty, realVNC and XMING, all same error while no issue with xclock and config.sh. Opened a ticket with Oracle Support (Oracle Discoverer group) but no luck so far. I only tried on our development box and did not try others.
Can you tell which Oracle Support Group you have been working with? My SR# is SR 3-6366510871 (Title - "Error when running Oracle Fusion Middleware Upgrade Assistant: Can't connect to X11 window server"), you may mention this to your Oracle Support analyst so it may force them to look internally for a possible bug.
My "SR 3-6006952911 : TF: Upgrade Assistant Cannot Start" has been opened under Oracle Fusion Middleware. THe support engineer has been working with Oracle developer on the issue. No progress has ever been made for more than 3 months since it was logged. At the meantime I use the command line mode instead.
I have found out the issue existing if the component is installed with WLS(FMW), and no existing if the component is installed as the stand alone.
I used the WebTier11g to the verification.
Thanks for the update.
Yes, it's very frustrating being stuck at this non-sense step for so long. The SR I opened is a month old now but I did so much research before opening a SR as I simply try to upgrade our Discoverer 10g to 11g (22.214.171.124), this Discoverer is integrated with our E-Business Suite Application R12.
I have looked at command line option too but to perform schema upgrade using the command line interface, the syntax requires -oidHost and oidSslPort which we don't use OID in our environment:
ua MR -discoverer -oidHost <oid_host> -oidSslPort <oid_ssl_port>
I wonder how you did the command line upgrade for schema data upgrade, I would be really appreciate if you could share it.