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 for further assistance. Reference the community FAQ to learn more about the community.

Focal Point    Focal Point Forums  Hop To Forum Categories  Performance Management Framework (PMF)    PMF Oracle configuration tips (one of a series) - schema name and CASE

Read-Only Read-Only Topic
PMF Oracle configuration tips (one of a series) - schema name and CASE
In PMF, if you configure using RDBMS on Oracle or DB/2, there are a few additional items to pay attention to. SQL Server is relatively straightforward comparatively (which is why we typically recommend demos and POCs to be on SQL Server).

Besides what's needed to set up the connectivity for the adaptor, there are three settings specific to Oracle in PMF:

Schema Name: The Oracle schema which contains among other things the identity of the PMF data mart's DB Owner.
Tablespace Name: The name of the tablespace used in Oracle for the PMF data mart.
Index space Name: The name of the index space used in Oracle for the PMF data mart.

PMF V 5.0 and early 5.1 prompted for these properties. If they were entered incorrectly, or if a DBA changed them (and even changing the CASE of these names can have an effect) the user had to go in and change the settings in the a_defaults.fex file.

PMF V 5.1.3 introduced a test/reprompt logic, so that if these were not set properly they could be corrected. PMF tests against the schema and looks at the owners configured for the database tables. If they dont' exactly match, PMF will refuse to resync (for fear of corrupting the master files for the app, or the database). It pops up an error that "the schema name isn't correctly configured."

We've seen one customer situation where the schema name started out as UPPERCASE when the data mart was built, but then was changed to lowercase later on (the DBA thought this woudl be harmless). Changing the schema name doesn't change the Owner registered to each table in Oracle. So the owners were [UPPERCASENAME].[table name] whereas the schema was being entered as [lowercasename].[table name]. So when PMF went to test the schema for validity (and since FOCUS generally uses case sensitive matching) it detected a mismatch.

The answer was to have the adaptor configured with the new lowercase schema name, but to configure PMF to use the UPPERCASE schema name. When the prompt came up, this was typed in, and all worked.

Just another tip in a series.


Bob Jude Ferrante
Director of Business and Development
WebFOCUS Performance Management

I'll take any questions about PMF - business or technical - anytime!

Posts: 919 | Registered: March 26, 2003Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  Performance Management Framework (PMF)    PMF Oracle configuration tips (one of a series) - schema name and CASE

Copyright © 1996-2020 Information Builders