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.
Last time I worked with Sybase (10/11) there were 3 different types of temp tables all with different persistence/availability options.
1. If you created the table as tempdb..table_name, the table would exist until deleted or until the Sybase instance was restarted. Anybody (with required permissions) could view these tables.
2. If you created the table as #table_name via a SQL statement, the table would only exist as long as your Sybase session was active. As soon as you log out, the table would be deleted. Also, only the session in which the tables was created could query it. If you are creating the table in one request and then trying to report on it in another request, you may be getting disconnected from the server and then reconnecting. This means the table is getting deleted.
3. If you created the tables as #table_name via a stored procedure, the table only exist as long as the stored procedure is running. As soon as the stored procedure finishes, the table is deleted. I don't believe WF (or any other product) cannot access these tables.