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.
We have this job that runs daily. Judging bij de the Agent in use it moves daily ResourceManager data to a historic storage. RMLDATA to RMLDB with MODIFY-statements
This was never a real problem but as time progresses this job now runs for 3 or 4 hours+
And that's not desirable. Because of the agent in use, the resource in use on the reporting server and we can not query loggingdata then.
So, sounds familiar? Any idea's?
PS> Because of other processes we can not move this schedule to somewhere in the night.This message has been edited. Last edited by: FP Mod Chuck,
_____________________ WF: 8.0.0.9 > going 8.2.0.5
Posts: 668 | Location: Veghel, The Netherlands | Registered: February 16, 2010
Good question. But you tell me, because I don't know.
The fex started is rmusavlg.fex Only statement in this fex is: GKE %ARCHIVE_LOG
It's IBI internals. I really couldn't tell you.
And yes it's probably because of the volume of data. [ 5000+ / day ] And it seems to be slowing down. But then again, these volumes shouldn't be more that a few seconds work for any database-engine.
_____________________ WF: 8.0.0.9 > going 8.2.0.5
Posts: 668 | Location: Veghel, The Netherlands | Registered: February 16, 2010
What is the repository for the resource management database? Is it relational or FOCUS? If relational which RDBMS are you using. I found this post on techsupport that addresses Oracle.
Here is what was in that page. Not sure if it applies to SQL Server though. It would be worth having your tech guys check into though.
Solution Notes Problem
Poor performance when the daily Archive job is run with Resource Management.
Solution
This issue is occurring because the Resource Management Repository resides in an Oracle instance that uses a different code page than the Reporting Server and the Oracle Client. For example, the WebFOCUS Reporting Server has a code page of 65001 and the Oracle Client NLS_LANG variable is set to UTF8. This will trigger a data conversion between the Oracle Client and the database instance.
Having all pieces of the configuration use the same code page will resolve this issue. The user defined the Oracle database with a Unicode code page of AL32UTF8 which resolved the issue.
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005