Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Login from DS to Oracle Server fails RC=32033 EDA -17

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Login from DS to Oracle Server fails RC=32033 EDA -17
 Login/Join
 
Master
posted
We get this message quite frequently when we use our test oracle instance which is much less powerful and less used than the production instance. On production this occurs rarely.

What I am guessing is happening is that the login process is not actually failling but taking too long, because when you try next time it works fine.

This would suggest that there is a threshhold time for login beyond which wf assumes that the login attempt is invalid, NOT because the password is invalid, but because the instance is not present or not reachable.

Does anyone know if this is a settable parameter we can set higher for our test instance where login takes longer?

Thanks

John



Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2
Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
 
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006Report This Post
Master
posted Hide Post
Tried to do this in Oracle SQLNET.ORA set to 300s = 5 mins to timeout. Works in 9.2+

#Timeout Parameters
SQLNET.INBOUND_CONNECT_TIMEOUT = 300
SQLNET.SEND_TIMEOUT = 300
SQLNET.RECV_TIMEOUT = 300

http://www.psoug.org/reference/net_services.html

This message has been edited. Last edited by: hammo1j,



Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2
Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
 
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Login from DS to Oracle Server fails RC=32033 EDA -17

Copyright © 1996-2020 Information Builders