| Oracle® Fusion Applications Administrator's Guide 11g Release 1 (11.1.1.5) Part Number E14496-02 |
|
|
View PDF |
| Oracle® Fusion Applications Administrator's Guide 11g Release 1 (11.1.1.5) Part Number E14496-02 |
|
|
View PDF |
This chapter describes common problems that you might encounter when using Oracle Business Intelligence and explains how to solve them.
This chapter includes the following topics:
Introduction to Troubleshooting Oracle Business Intelligence
Diagnosing Oracle Transactional Business Intelligence Query Problems
Problems and Solutions for Oracle Enterprise Performance Management
Using My Oracle Support for Additional Troubleshooting Information
In addition to this chapter, review the Oracle Fusion Middleware Error Messages Reference for information about the error messages you may encounter.
This section provides guidelines and a process for using the information in this chapter. Using the following guidelines and process will focus and minimize the time you spend resolving problems.
Guidelines
When using the information in this chapter, Oracle recommends:
After performing any of the solution procedures in this chapter, immediately retrying the failed task that led you to this troubleshooting information. If the task still fails when you retry it, perform a different solution procedure in this chapter and then try the failed task again. Repeat this process until you resolve the problem.
Making notes about the solution procedures you perform, symptoms you see, and data you collect while troubleshooting. Examples of information that you should collect include:
Screenshots of the error or behavior.
The user ID that you used when the error or issue occurred.
The steps that you used to perform the task.
From where you accessed Oracle BI. For example, embedded analytics, the reporting pane, reports and analytics work area, integrated search, BI Composer, Oracle BI Presentation Services, or Oracle BI Publisher.
If you cannot resolve the problem using the information in this chapter and you must log a service request, the notes you make will expedite the process of solving the problem.
Process
Follow the process outlined in Table 18-1 when using the information in this chapter. If the information in a particular section does not resolve your problem, proceed to the next step in this process.
Table 18-1 Process for Using the Information in this Chapter
| Step | Section to Use | Purpose |
|---|---|---|
|
1 |
Perform problem-specific troubleshooting procedures for Oracle Business Intelligence Enterprise Edition and Oracle Business Intelligence Publisher. This section describes:
|
|
|
2 |
Use this section to diagnose Oracle Transactional Business Intelligence query issues. |
|
|
3 |
Use this section to diagnose Oracle Enterprise Management issues. |
|
|
3 |
Use My Oracle Support to get additional troubleshooting information about Oracle Fusion Applications or Oracle BI. My Oracle Support provides access to several useful troubleshooting resources, including Knowledge Base articles and Community Forums and Discussions. |
|
|
4 |
Log a service request if the information in this chapter and My Oracle Support does not resolve your problem. You can log a service request using My Oracle Support at |
Use the following information to determine where to begin troubleshooting your Oracle BI issue.
Oracle BI Technologies
To properly troubleshoot an Oracle BI issue, you must identify in the Oracle Fusion application user interface which underlying Oracle BI technologies are being used. When identifying these technologies, consider the following:
The most common analyses are Online Transactional Business Intelligence analyses. Note that Oracle Transaction Business Intelligence can be referred to as real-time or transactional business intelligence. Oracle Transactional Business Intelligence objects analyze very recent data such as today's data or this week's data.
Oracle Fusion Financials also uses Financial Reporting technology.
Some analyses use Essbase, Real Time Decisions, or Oracle BI Publisher reports.
Oracle BI Query Log
A useful tool to determine the underlying technology for troubleshooting purposes is the Oracle BI query log: nqquery.log. From this log you can identify the datasource and connectivity set-up (for example, transactional database, warehouse database, Financial Reporting datasource, or Essbase datasource) and the datasource objects such as table names and column names.
Warehouse Enablement Setting
When troubleshooting, you should also note whether during the Oracle Fusion Applications setup, the Warehouse Enablement was set to Yes, No, or NA. Use Table 18-2 to determine whether the warehouse source or Oracle Transactional Business Intelligence source services the subject area.
Table 18-2 Warehouse Enablement Settings
| Setting | Means that ... |
|---|---|
|
Yes |
Real-Time Subject Area is serviced by OTBI source. Common Subject Area is services by Warehouse source. |
|
No |
Real-Time Subject Area is serviced by OTBI source. Common Subject Area is serviced by OTBI source. Some measures are not available. Some measured return zero. |
|
NA |
NA |
This section describes common problems and solutions. It contains the following topics:
Cannot Log Into Oracle Business Intelligence as a User With the BISystem Role
The "My Account" Link Does Not Display in Presentation Services
Oracle BI Publisher Reports Are Missing from the Presentation Services Shared Folders
Oracle BI Publisher Reports Are Missing from the Oracle BI Publisher Server Shared Folders
In most cases, Presentation Services fails because the BI Server is not running.
Problem
The BI Server may not be running.
Solution
To determine if the BI Server is running:
Log into Fusion Applications Control.
Open the Business Intelligence node and select coreapplication.
Click the Capacity Management page, and then click the Availability tab.
Under BI Server, locate coreapplication_obis1 and check its status.
If you discover that the BI Server is not running, see Section 18.3.2.
For additional information about this issue, see the "Managing Oracle Business Intelligence" and "Diagnosing and Resolving Issues in Oracle Business Intelligence" chapters in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
Problem
The Cluster Controller might not be communicating with the BI Server and the BI Server log might contain information describing why it cannot communicate.
Solution
To check the Cluster Controller log files in Fusion Applications Control:
Log into Fusion Applications Control.
Open the Business Intelligence node and select coreapplication.
Click the Diagnostics tab, and then click the Log Messages subtab.
Go to the View/Search Log Files section and click Cluster Controller Log. The Log Messages page displays.
Search for an entry similar to the following entry:
[2011-02-28T12:54:51.000+00:00] [OracleBIServerComponent] [NOTIFICATION:1] [] [] [ecid: 004bLSdkE549Xb9LJe_Aif0000Zg000000] [tid: b7f686c0] nqsserver: Clustered Oracle BI Server started. Version: 11.1.1.4.0.110109.0239.000. [2011-02-28T12:54:52.000+00:00] [OracleBIServerComponent] [NOTIFICATION:1] [] [] [ecid: 004bLSdkE549Xb9LJe_Aif0000Zg000000] [tid: 66f6ba0] [43071] A connection with Cluster Controller somemachine.company.com:7001 was established.
Note that if this entry does not exist, then the Cluster Controller is not communicating correctly with the BI Server. If the Cluster Controller is not communicating with the BI Server, then go to the following "To check the BI Server log file in Fusion Applications Control" procedure.
To check the BI Server log file in Fusion Applications Control:
Log into Fusion Applications Control.
Open the Business Intelligence node and select coreapplication.
Click the Diagnostics tab, and then click the Log Messages subtab.
Go to the View/Search Log Files section and click BI Server Log. The Log Messages page displays.
Search for an entry similar to the following entry:
[2011-01-31T20:47:38.000-08:00] [OBIPS] [ERROR:10] [] [saw.security.odbcuserpopulationimpl.initialize] [ecid: ] [tid: ] Odbc driver returned an error (SQLDriverConnectW).State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 73006] Cannot obtain Oracle BI Servers from either the primary Cluster Controller (somemachine.company.com) or the secondary Cluster Controller () specified for the clustered DSN. (HY000)[[File:odbcuserpoploaderimpl.cpp Line:282 [2011-01-31T20:47:38.000-08:00] [OBIPS] [ERROR:16] [] [saw.security.odbcuserpopulationimpl.initialize] [ecid: ] [tid: ] Unable to create a system user connection to BI Server during start up. Trying again. [[File:odbcuserpoploaderimpl.cpp Line:283
When logging into Oracle Business Intelligence as a user with the BISystem role, a message displays stating that you have entered an invalid user name or password.
Problem 1
A user ID with the BISystem role may be locked. The system can lock this user ID if an administrator makes multiple attempts to log in with the incorrect password.
Solution 1
Ask the Oracle Internet Directory administrator to go to the Oracle Internet Directory and check the user ID. If this user ID is locked, you must unlock it.
Problem 2
The password of the user ID with the BISystem role may not be synchronized with the credential store.
Solution 2
To confirm that the password is correct:
Log into Oracle WebLogic Server Administration Console.
Go to Domain Structure and click Security Realms, and select myrealm. The Settings for myrealm page displays.
Click the Users and Groups tab, and then the Users subtab.
In the Users table, locate and select the user that has the BISystem role assigned to it. The settings page displays.
Click the Passwords tab and reset the user password. Click Save.
Log into Fusion Applications Control.
Open the WebLogic Domain node and right-click BIDomain.
Select Security, and then select Credentials.
Select oracle.bi.system and the select system.user.
Edit the password to match the user password that you set in Oracle WebLogic Server.
Restart the Oracle BI Administration Server, Oracle Managed Server, and Oracle Process Manager and Notification Server. For detailed instructions on how to restart these servers, see the "Starting and Stopping Business Intelligence" chapter in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
Problem 3
The problem may be that the Oracle Internet Directory password is incorrect.
Solution 3
To check and correct the Oracle Internet Directory password:
Log into Fusion Applications Control.
Open the Business Intelligence node and select coreapplication.
Click the Diagnostics tab, and then click the Log Messages subtab.
Go to the View/Search Log Files section and click Log Viewer to search all log files. The Log Messages page displays.
Go to the Search section and expand the Selected Targets section.
In the Selected Targets table, locate AdminServer and click the corresponding View list of target files button.
Search for Oracle Internet Directory errors. If the error is due to the wrong password, you will find an error such as the following error:
<Feb 15, 2011 12:31:10 PM PST> <Error> <Console> <BEA-240003> <Console
encountered the following error weblogic.security.providers.authentication.
LDAPAtnDelegateException: [Security:090294]could not get connection
atweblogic.security.providers.authentication.
LDAPAtnDelegate.getConnection(LDAPAtnDelegate.java:3483)
at weblogic.security.providers.authentication.LDAPAtnDelegate.
getConnection(LDAPAtnDelegate.java:3470)
at weblogic.security.providers.authentication.LDAPAtnDelegate.
listUsers(LDAPAtnDelegate.java:2258)
at weblogic.security.providers.authentication.LDAPAuthenticatorImpl.
listUsers(LDAPAuthenticatorImpl.java:178)
at weblogic.security.providers.authentication.
OracleInternetDirectoryAuthenticatorMBeanImpl.listUsers
... 110 more
Caused by: netscape.ldap.LDAPException: error result (49); Invalid
credentials
To correct this issue, log into Oracle WebLogic Server Administration Console.
Go to Domain Structure, click Security Realms, and select myrealm.
Select the Users and Groups tab, and then select the Users subtab.
Select the user ID. The settings for the user ID display.
Click the Passwords subtab and reset the user's password to the correct password. If you are not sure of the password, see the Oracle Internet Directory administrator.
In the Global Header of Presentation Services, the My Account option is missing. Normally the user can select the Signed In As list and the My Account option displays.
Problem
The problem may be a global user ID (GUID) refresh issue that requires you to recover the catalog.
Note:
For more information, see "Regenerating User GUIDs" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.Solution
To recover the catalog:
Start a command prompt.
Enter the following commands:
cd<Oracle_bi_Instance>/config/OracleBIPresentationServicesComponent/
coreapplication_obips1/
Open the instanceconfig.xml file.
Note:
Before you modify theinstanceconfig.xml, it is critical that you understand how to properly modify this file. For more information, see the "Configuring the Oracle Business Intelligence System" chapter in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.Locate the <catalog> element and add the following:
<UpdateAccountGUIDS>Recover</UpdateAccountGUIDs>
Save instanceconfig.xml.
Stop and restart Presentation Services.
Log into Fusion Applications Control.
Open the Business Intelligence node and select coreapplication.
Select the Capacity Management tab, and then select the Availability subtab.
Under BI Presentation Services, select coreapplication_obips1.
Click the Stop Selected button and confirm that coreapplicataion_obips1 stopped.
Re-select coreapplication_obips1.
Click the Start Selected button and confirm that coreapplication_obips1 started.
Open instanceconfig.xml.
Remove the following:
<UpdateAccountGUIDS>Recover</UpdateAccountGUIDs>
Note:
You must perform this step to ensure that your system is secure.Save instanceconfig.xml.
Stop and restart the BI Server.
When users log into Presentation Services and access the Oracle BI Presentation Catalog to browse the shared folders for their reports, the shared folders do not contain any reports.
Problem
The reports might not exist on the file system.
Solution
To confirm that the items exist on the file system:
Log into Fusion Applications Control.
Open the Business Intelligence node and select coreapplication.
Click the Deployment tab, and then click the Repository subtab.
Go to the BI Presentation Catalog section of the page and note the catalog path.
Use OS commands or a file explorer to navigate to the catalog path.
Browse the catalog for reports. Depending upon the outcome of this step, you may do one of the following:
If the reports do not exist in the catalog, it is probably because of a GUID refresh issue. See the following "To refresh the GUIDs:" procedure.
If the reports are not in the catalog, then it may be that you recently completed an unsuccessful catalog merge. Note that even if the last statement of the merge indicated success, the merge still might not have completed successfully. If you suspect that your catalog merge was not successful, then repeat the catalog merge.
To refresh the GUIDs:
Note:
For more information, see "Regenerating User GUIDs" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.Start a command prompt.
Enter the following commands:
cd <Oracle_bi_Instance>/config/OracleBIServerComponent/coreapplication_obis1/ edit NQSconfig.ini .. set FMW_UPDATE_ROLE_AND_USER_REF_GUIDS=YES ./opmnctl stopproc ias-component=coreapplication_obis1 ./opmnctl startproc ias-component=coreapplication_obis1
Repeat the previous step and set the FMW_UPDATE_ROLE_AND_USER_REF_GUIDS parameter in NQSConfig.INI back to NO.
Note:
You must perform this step to ensure that your system is secure.Restart the BI Server. For detailed instructions on how to perform this task, see the "Starting and Stopping Business Intelligence" chapter in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
When users log into Oracle BI Publisher and access the shared folders containing their reports, they see no reports. This problem can occur even though users can locate their reports in the Presentation Services Catalog's shared folders.
Problem 1
The user may not have the proper privileges to view the report.
Solution 1
To access Presentation Services and check the privileges required to access reports:
Log into Presentation Services as a user with administrator privileges.
Go to the Global Header and click the Signed In As list.
Click My Account. The My Account page displays.
Click the Roles and Catalog Groups tab and note the roles and groups in this page. Click OK to exit this page.
Go to the Global Header and click Sign Out to log out of Presentation Services.
Log back into BI Presentation Services using the log in credentials of the user who cannot view the reports in the Oracle BI Publisher Server shared folders.
Access the user's privileges using the previous steps.
If the user does not have the proper privileges, log into Presentation Services as a user with administrator privileges and navigate to the Manage Privileges page to assign the proper privileges to the user.
For more information, see the "Setting Oracle BI Presentation Catalog Privileges for an Application Role" section in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.
Problem 2
An error may have occurred when Oracle BI Publisher connected to Presentation Services.
Solution 2
To override the BISystemUser account:
By default Oracle BI Publisher connects to Presentation Services using the BISystemUser account that is stored in the credential store. However, it is possible for users to override this.
Open the xmlp-server-config.xml file in the following directories:
(UNIX) BI_DOMAIN_HOME/config/bipublisher/repository/Admin/Configuration (Windows) FA_MW_HOME\config\bipublisher\repository\Admin\Configuration
Confirm that the SAW_USERNAME and SAW_PASSWORD properties are not set. Note that if these properties have been set, it will cause an error. Before you change these properties, ask your administrator why they have been set.
To un-set these properties, set their values to "".
Restart the WebLogic domain. For more information, see Section 3.3.4.
Problem 3
The catalog may be corrupted.
Solution 3
To check if the catalog is corrupted:
Log into Presentation Services as a user with administrator privileges.
Go to the Global Header and click Catalog. The Catalog page displays.
In the Search pane, enter the following search criteria:
In the Name field, type *.
In the Location field, click the list and choose All.
In the Type field, click the list and choose Data Model.
Click Search. If the search results include the Shared Folder, then the catalog is corrupt. Note that if the Shared Folder is included in your search results, Oracle BI Enterprise Edition has classified it as a data model rather than a folder. Perform the following "To fix the corrupted catalog" procedure to fix the catalog.
To fix the corrupted catalog:
Open Catalog Manager and open the catalog in offline mode.
Navigate to Shared Folders.
Right-click the object in the Name column and select Properties.
Set the following properties to null:
bip:DisplayName
Caption
compositeSignature
DESCRIPTION
objectName
Save your changes.
This section describes how you to use the NQQuery.log file and the AdminServer-diagnostic.log file to diagnose Oracle Transactional Business Intelligence query issues such as ODBC errors, ORA-errors, other database errors, and query performance issues.
The NQQuery.log file is useful for any analysis that uses the BI Server to query the datasource (for example, OTBI or OBIA). The NQQuery.log records the logical SQL sent by the Oracle BI Presentation layer to the BI Server layer and the physical or ANSI SQL sent by the BI Server to the datasource.
This section contains the following topics:
You can enable the NQQuery.log file to diagnose issues that you encounter in Oracle Transactional Business Intelligence queries. Use one of the following methods to enable the NQQuery.log file.
You can enable query logging from the Oracle BI Administration Tool. For information and procedures about enabling the query log file, see "Managing the Query Log" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
You can enable the LogLevel system session variable for the repository by accessing the repository and setting the LogLevel system variable to 7. For information and procedures about setting this variable, see "About System Session Variables" section in the Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (Oracle Fusion Applications Edition).
If you have administrator permissions, you can log into Presentation Services, access the analysis that you want to troubleshoot, and temporarily change its logging level to 2. This will turn on logging for the analysis even when logging is turned off for all analyses. For more information, see "Setting the Query Logging Level" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
If you use this method to enable the NQQuery.log file, look for the following:
An error like "no log found." An error like this indicates that there is a known error. Look in the NQQuery.log file, which contains additional logging.
The timestamp to help you locate the log entry.
The logical SQL as shown in the error message. This is the SQL sent by Presentation Services to the BI Server layer.
The physical SQL related to the above mentioned logical SQL. Search for "physical". The physical SQL is the SQL sent by BI Server through ODBC to the database.
For any more detailed errors.
Note that the NQQuery.log file is not searchable in the Fusion Applications Control Log Viewer.
After enabling query logging, if the BI Server caching is enabled, you must clear the cache before re-executing the analysis so that the NQQuery.log file will contain the correct information. Use the following procedure to perform this task.
To clear the BI Server cache:
Log into Presentation Services as an administrator.
In the Global Header, click Administration. The Administration page displays.
Click Manage Sessions. The Manage Sessions page displays.
Scroll to the Cursor Cache section of the page and click the Close All Cursors button.
The request query executed from Presentation Services will be shown in the NQQuery.log file as follows:
RqList 0 as c1 GB, Dim - Procurement Item.Category Name as c2 GB, Dim - Procurement Item.Item Description as c3 GB, # of PO Lines:[DAggr(Fact - Purchasing - Order.# of PO Lines by [ Dim - Procurement Item.Category Name, Dim - Procurement Item.Item Description] )] as c4 GBOrderBy: c1 asc, c2 asc, c3 asc
This query trace explains how a measure is calculated. It also shows the logical table source used to render the data. The query should use the logical table sources having priority 5 for the requests executed from the Oracle Transactional Business Intelligence Real Time Subject Areas.
The query trace shows the view object, its view criteria, and its view links that are used to execute the request. See the following:
<ADFQuery mode="SQLBypass" queryid="14604-3902" locale="en"><Parameters></Parameters>
<Projection>
<Attribute><Name><![CDATA[CategoryName]]></Name>
<ViewObject><![CDATA[FscmTopModelAM.PrcPoPublicViewAM.
PurchasingItemP]]></ViewObject>
</Attribute>
<Attribute><Name><![CDATA[ItemDescription]]></Name>
<ViewObject><![CDATA[FscmTopModelAM.PrcPoPublicViewAM.
PurchasingItemP]]></ViewObject>
</Attribute>
<Attribute><Name><![CDATA[PurchasingDocumentHeaderTypeLookupCode]]></Name>
<ViewObject><![CDATA[FscmTopModelAM.PrcPoPublicViewAM.StandardLinePVO]]>
</ViewObject>
</Attribute>
<Attribute><Name><![CDATA[PoLineId]]></Name>
<ViewObject><![CDATA[FscmTopModelAM.PrcPoPublicViewAM.StandardLinePVO]>]
</ViewObject>
</Attribute>
<Attribute><Name><![CDATA[ItemNumber]]></Name>
<ViewObject><![CDATA[FscmTopModelAM.PrcPoPublicViewAM.PurchasingItemP]]>
</ViewObject>
</Attribute>
</Projection>
JoinSpec>
<ViewObject>
<Name><![CDATA[FscmTopModelAM.PrcPoPublicViewAM.PurchasingItemP]]></Name>
<ViewLink><Name><![CDATA[oracle.apps.prc.po.publicView.analytics.link.
PurchasingDocumentLinePVOToPurchasingItemPVO]]></Name></ViewLink>
</ViewObject>
<ViewObject>
<Name><![CDATA[FscmTopModelAM.PrcPoPublicViewAM.StandardLinePVO]]></Name>
<ViewLink><Name><![CDATA[oracle.apps.prc.po.publicView.analytics.link.
PurchasingDocumentLinePVOToPurchasingItemPVO]]></Name></ViewLink>
</ViewObject>
</JoinSpec>
<DetailFilter>
<ViewCriteria>
<ViewCriteriaRow conjunction="VC_CONJ_AND">
<Attribute><Name><![CDATA[PurchasingDocumentVersionCoSequence]]></Name>
<ViewObject><![CDATA[FscmTopModelAM.PrcPoPublicViewAM.StandardLinePVO]]>
</ViewObject>
</Attribute>
<Value><![CDATA[0]]></Value>
<Predicate operator="OPER_EQ"/>
</ViewCriteriaRow>
<ViewCriteriaRow conjunction="VC_CONJ_AND" negated="true">
<Attribute><Name><![CDATA[PurchasingDocumentVersionCoCanceledFlag]]></Name>
<ViewObject><![CDATA[FscmTopModelAM.PrcPoPublicViewAM.StandardLinePVO]]>
</ViewObject>
</Attribute>
<Value><![CDATA[Y]]></Value>
<Predicate operator="OPER_EQ"/>
</ViewCriteriaRow>
</ViewCriteria>
</DetailFilter>
</ADFQuery>
You or the administrator can review the query trace to check that the desired View Objects (VOs) and View Links are executed. The execution of the view objects and view must be based on the Logical model code to render the measure or attributes executed in the request.
The SQL Bypass database should be setup in the repository to send the physical query to the database directly, rather than through the ADF Server. The NQQuery.log file shows the physical query sent to the database if the SQL Bypass database is enabled. See the following excerpt from the log file:
WITH
SAWITH0 AS (select T744257.C501728333 as c1,
T744257.C281594243 as c2,
T744257.C469784899 as c3,
T744257.C168071223 as c4
from
(SELECT V110617254.CATEGORY_NAME AS C501728333, V110617254.
ITEM_DESCRIPTION
AS C281594243, V278099157.TYPE_LOOKUP_CODE263 AS C469784899,
V278099157.PO_LINE_ID AS C168071223, V110617254.ITEM_NUMBER AS
C348883104, V278099157.CO_SEQUENCE AS C78750419, V278099157.CO_
CANCELED_FLAG AS C443371219, V278099157.PO_HEADER_ID1 AS PKA_
PurchasingDocumentHeaderP0, V278099157.VERSION_ID AS PKA_
PurchasingDocumentVersion0 FROM (SELECT PurchasingDocumentLine.PO_LINE_ID,
PurchasingDocumentHeader.PO_HEADER_ID AS PO_HEADER_ID1,
PurchasingDocumentHeader.TYPE_LOOKUP_CODE AS TYPE_LOOKUP_CODE263,
PurchasingDocumentVersion.CO_CANCELED_FLAG,
PurchasingDocumentVersion.CO_SEQUENCE,
PurchasingDocumentVersion.VERSION_ID,
(DECODE(PurchasingDocumentLine.ITEM_ID, NULL,
DECODE(PurchasingDocumentLine.VENDOR_PRODUCT_NUM, NULL,
(PurchasingDocumentLine.ITEM_DESCRIPTION || '[' || CategoryTranslation.
CATEGORY_NAME || ']'),(PurchasingDocumentLine.VENDOR_PRODUCT_NUM || '[' ||
PurchasingDocumentHeader.VENDOR_ID || ']')),TO_CHAR(PurchasingDocumentLine.
ITEM_ID))) AS ITEM_NAME FROM PO_LINES_ALL PurchasingDocumentLine,
PO_HEADERS_ALL PurchasingDocumentHeader, PO_VERSIONS PurchasingDocumentVersion
WHERE (PurchasingDocumentLine.PO_HEADER_ID = PurchasingDocumentHeader.
PO_HEADER_ID AND PurchasingDocumentHeader.PO_HEADER_ID =
PurchasingDocumentVersion.PO_HEADER_ID) AND ( (
(UPPER(PurchasingDocumentHeader.TYPE_LOOKUP_CODE) = UPPER('STANDARD') ) ) ))
V278099157, (SELECT DISTINCT ( DECODE(PL.ITEM_ID,NULL,DECODE(PL.
VENDOR_PRODUCT_NUM, NULL,(PL.ITEM_DESCRIPTION || '[' || TL1.CATEGORY
_NAME||']'),(PL.VENDOR_PRODUCT_NUM || '[' || PH.VENDOR_ID ||']')), TO
_CHAR(I.ITEM_NUMBER))) AS ITEM_NUMBER, PL.ITEM_DESCRIPTION,
PL.CATEGORY_ID,TL1.CATEGORY_NAME, DECODE(PL.ITEM_ID, NULL,DECODE
(PL.VENDOR_PRODUCT_NUM, NULL, 'DESCRIPTION BASED ITEMS','SUPPLIER
ITEMS'),'INVENTORY_ITEMS') AS ITEMTYPE FROM PO_LINES_ALL PL,
EGP_CATEGORIES_TL TL1, PO_HEADERS_ALL PH, PO_SYSTEM_PARAMETERS_ALL SP,
EGP_SYSTEM_ITEMS_B I WHERE PL.CATEGORY_ID=TL1.CATEGORY_ID AND PL.CATEGORY_ID IS
NOT NULL AND PL.PO_HEADER_ID=PH.PO_HEADER_ID AND PL.PRC_BU_ID=SP.PRC_BU_ID AND
I.INVENTORY_ITEM_ID=PL.ITEM_ID) V110617254 WHERE V278099157.ITEM_NAME =
V110617254.ITEM_NUMBER( + ) AND ( ( (V278099157.CO_SEQUENCE = 0 ) ) AND
( NOT ( (V278099157.CO_CANCELED_FLAG = 'Y' ) ) ) )) T744257),
SAWITH1 AS (select D1.c1 as c2, D1.c2 as c3,
case when D1.c3 = 'STANDARD' then D1.c4 end as c4
from
SAWITH0 D1), SAWITH2 AS (select D1.c2 as c2, D1.c3 as c3,
D1.c4 as c4,
ROW_NUMBER() OVER (PARTITION BY D1.c2, D1.c3, D1.c4 ORDER BY D1.c2 DESC,
D1.c3 DESC, D1.c4 DESC) as c5from SAWITH1 D1),SAWITH3 AS (select
count(distinct case D1.c5 when 1 then D1.c4 else NULL end )
as c1, D1.c2 as c2, D1.c3 as c3from SAWITH2 D1
group by D1.c2, D1.c3)
select distinct 0 as c1, D1.c2 as c2, D1.c3 as c3, D1.c1 as c4 from
SAWITH3 D1
order by c2, c3
Use this physical SQL to diagnose which tables, columns joins, and filters are being used by the BI Server to gather data. Table names are aliased (for example, T744257). Search for the table alias in the RPD to find the actual table name. Run the SQL to check whether it works in SQL*Plus.
For performance issues, look for filter columns that are not indexed, and known database performance causes such as NOT IN clauses. Also use Oracle Database Control for performance advice.
The NQQuery.log file also indicates the user who executed the analysis, the timestamp, and the OBI Connection Object used for the analysis. From the Connection Object name, you can refer back to the Oracle BI repository to find the set up properties of the connection, such as whether it uses a native connection or ODBC.
The Oracle BI NQQuery.log file contains detailed BI Server errors, so it is recommended to check this log file. You can access this log file with the Fusion Application Control. The NQQuery.log file shows queries executed at the time of starting the BI Server service. Be sure to check this log for any query failures.
Oracle BI EE gets the view object physical query from the Oracle ADF Server. This query involves the view object query and the security predicate associated to it. You or the administrator need to research the WebLogic Server log file if you suspect an issue in the view object query. You will find this information in the AdminServer-diagnostic.log file. This file is located in the WebLogic Server domain associated to Oracle JDeveloper 11g.
The AdminServer-diagnostic.log file shows the user name, view object, attributes, the view link source and destination entities, and the view criteria for view objects (including security view criteria). In this file you will find the roles associated to the user and the security predicate associated to the roles and users in the roles. This file also shows the composite view object API called for the view object, along with view links and view criteria.
The BI Server uses the properties in the connection pool object, which is located in the Oracle BI repository. Use the following procedure to confirm that your connectivity is set up correctly.
To confirm that your connectivity is set up correctly:
Note:
This procedure uses the ADF BC Datasource as an example.In the Physical layer of the Administration Tool, expand the database object for the ADF Business Component data source.
Right-click a physical table and click View Data.
Check that the appropriate data displays. Note that if you have just imported, you may need to check in the new objects before you perform this test.
This section describes common problems and solutions for Oracle Enterprise Performance Management. It contains the following topics:
This section describes common problems and solutions for Foundation Services. It contains the following topics:
Log files are the best tools for analyzing what might be wrong with the system configuration. The logging configuration file, the defaults it ships with, and instructions for changing change those defaults will help with the analysis.
Configuration: The logging.xml file in the following directories contains the loggers and their default levels:
(UNIX) DOMAIN_HOME/servers/server_name/logs (Windows) DOMAIN_HOME\servers\server_name\logs
The DOMAIN_HOME is named BIDomain.
Output: The default locations of the loggers are rooted in the following directories:
(UNIX) DOMAIN_HOME/servers/server_name/logs (Windows) DOMAIN_HOME\servers\server_name\logs
These files include:
/registry/registry.log
/css/css.log
/workspace/Framework.log
/workspace/workspace.log
/financialreporting/fr.log
CalcManager.log
Loggers: Increase or decrease the levels of these loggers:
oracle.EPMCSS
oracle.bi.bifndnepm.epmreg
oracle.bi.bifndnepm.bpmui
oracle.bi.bifndnepm.workspace
oracle.EPMFR
oracle.EPMAnnotations
oracle.EPMJCR
oracle.EPMADM
oracle.bi.bifndnepm.calcmgr
To change logger levels, perform the following steps:
Go to Fusion Applications Control.
From the navigation pane, expand the farm and then WebLogic Domain.
Right-click a Managed Server from within the domain (each server's log levels can be independently set).
Choose Logs > Log Configuration.
In the Logger Name column, expand the oracle runtime loggers to display loggers.
Change the logging level as appropriate.
Problem
Some components are not operating correctly, or appear to have some minor issues. This is a broad category, but snooping the web traffic can help development resolve some issues by looking for irregular status, content, and redirection, and just providing the flow of calls up to the problem area.
Solution
Connect to http://www.fiddler2.com/fiddler2 and install version 2 (beta is stable). Launch Fiddler through one of these methods:
Start Menu: Programs > Fiddler2
Microsoft Internet Explorer: Tools > Fiddler2
Mozilla Firefox: Tools > Monitor With Fiddler > Launch Fiddler Now
Ensure Do not use Fiddler is not selected.
Connect to the starting URL and continue normally until the problem occurs.
When the problem occurs, in Fiddler, choose File > Save > All Sessions.
Enter a name for the session archive (.saz) file.
Note:
Be aware that the file may contain sensitive information, such as user ID and password information. Therefore, manage the file carefully.This section describes common problems and solutions for EPM Registry. It contains the following topics:
Problem
The EPM Registry initialization fails in the BIDomain domain. Oracle Fusion General Ledger and Oracle Fusion Customer Relationship Management (CRM) code running within the FinancialsDomain and CRMDomain domains, respectively, has direct integration with the EPM Registry API and consumes EPM Security Component, which also tightly integrates with the EPM Registry API. When EPM Registry initialization fails, it greatly impacts communication with downstream EPM products in the BI domain.
Solution
To resolve this problem:
Login to Oracle WebLogic Server Console as the Oracle WebLogic Server administrative user.
From Domain Structure portlet, navigate to Services > Data Sources and select EPMSystemRegistry Datasource from the available list of datasources.
Click on the Connection Pool tab and confirm that the correct information is available for URL property.
Click on the Targets tab and confirm that the data source is targeted to all of the required Oracle WebLogic Servers and clusters running in the Financials domain.
Click on the Monitoring tab and confirm that the data source for all of the targeted Oracle WebLogic Servers and clusters is in Running state. Optionally, try clicking Test Data Source button to test the data source for a given server.
If, in Step 5, the data source was not in the Running state, click the Control tab and attempt to start the data source using the Start button.
If any errors were encountered during Step 5 or 6, consider restarting the Oracle WebLogic Server domain.
Problem
An error is returned when connecting to Essbase Server from the Fusion Applications domain, using the Essbase Cluster lookup URL that is built using the host and port information retrieved for Essbase_FA_Cluster, from EPM Registry using the Registry API.
Solution
To resolve this issue, perform the following validations with appropriate actions:
Verify that the host and port values for the LOGICAL_WEB_APP component in EPM System Registry, where webAppType is PROVIDER_SERVICES_WEB_APP, exactly matches the host and port that the APS Web application is running on in the BI domain. Follow these steps:
Run the EPM Registry Editor utility using the following command:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/config/foundation/11.1.2.0/epmsys_registry.sh view LOGICAL_WEB_APP | tee -a logical_webapp_report.txt (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\config\foundation\11.1.2.0\epmsys_registry.bat view LOGICAL_WEB_APP > logical_webapp_report.txt
In the logical_webapp_report.txt file that is generated as a result of Step 1, search for the following string:
*"webAppType = PROVIDER_SERVICES_WEB_APP"
For the COMPONENT containing the matching string, verify that HOST/port/SSL_PORT exactly match what the APS Web application is actually running on in the BI domain. If any of these values are different in the Essbase cluster lookup URL, they should be appropriately updated in EPM Registry for the given Logical Webapp Component. This solution is discussed in Section 18.5.1.3.3.
Confirm that the APS Web application is in an Active state in the BI domain, by logging into the BI Admin Server console and reviewing the deployment profile of APS.
If verification of Step 1 successfully passes, verify the Oracle Access Manager protection policies and confirm that the Essbase cluster lookup URL is excluded from those policies
Problem
If the host or port for Logical Web App components in the EPM Registry do not exactly match the actual host and port that EPM Web applications are running on in the BIDomain domain, there may be connection or launch issues for EPM Web applications from within the Fusion user interface. In this case, you must update the host and port for Logical Web App components in EPM Registry.
Solution
To resolve the issue:
Execute the following command so that respective component IDs are available in the file for later use.
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/config/foundation/11.1.2.0/epmsys_registry.sh view LOGICAL_WEB_APP | tee -a logical_webapp_report.txt (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\config\foundation\11.1.2.0\epmsys_registry.bat view LOGICAL_WEB_APP > logical_webapp_report.txt
The EPM Registry Dump (.html report) that is created by running epmsys_registry.sh and epmsys_registry.bat does not include the component IDs that are required to update the host and port properties for individual components.
After successfully executing this command, the logical_webapp_report.txt file now contains exported data for five Logical Web App components - something similar to:
COMPONENT - 1 NAME - Default ID - a01b453873d1e7b5S7b70c01f12e34faed1bS7fdc TYPE - LOGICAL_WEB_APP HOST - hostname HYPERION HOME - /scratch/aime1/work/mw8747/Oracle_BI1 PROPERTIES - webAppType = CALC_WEBAPP context = calcmgr
The ID highlighted above in bold will be available for COMPONENT - [1-5]; this is what you will be required to use in subsequent steps.
For the individual ID of COMPONENT - [1-5], execute the following EPM Registry update command:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/config/foundation/11.1.2.0/epmsys_registry.sh updateproperty \#ID/@port port (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\config\foundation\11.1.2.0\epmsys_registry.bat updateproperty #ID/@port port
For example:
./epmsys_registry.sh updateproperty \#a01b453873d1e7b5S7b70c01f12e34faed1bS7fdc/@port 16050
Validate that you have successfully updated the host and port for Logical Web App components:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/config/foundation/11.1.2.0/epmsys_registry.sh view LOGICAL_WEB_APP | tee -a logical_webapp_update_report.txt (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\config\foundation\11.1.2.0\epmsys_registry.bat view LOGICAL_WEB_APP > logical_webapp_report.tx
After these updates, restart the BIDomain, CRMDomain and FinancialsDomain domains, so that new changes take effect. See Section 3.3.4
Problem
The following error about Oracle Enterprise Scheduler Essbase Cube creation in the BIDomain domain is returned because of a Hyperion security username and password authentication failure:
EPMCSS-00301: Failed to authenticate user. Invalid credentials. Enter valid credentials.
Solution
To resolve this issue, verify that the password stored in credential store for Application Identity (App ID) used by the Oracle Enterprise Scheduler job to connect to Essbase exactly matches the password for the given Application Identity in the underlying LDAP Identity Store:
Identify which App ID is used by the Oracle Enterprise Scheduler job in the given domain, to connect to an Essbase single cluster.
The following application identities are used for the respective domains:
Oracle Fusion Customer Relationship Management: FUSION_APPS_CRM_ADF_APPID
Oracle Fusion Projects: FUSION_APPS_PRJ_ESS_APPID
Oracle Fusion General Ledger: FUSION_APPS_GL_ESSBASE_APPID
Run the WLST listCred script with the appropriate map and key. See the section "listCred" in the Oracle Fusion Middleware Application Security Guide.
The password obtained in Step 2 can then be used to compare the existing password for the given App ID in the underlying LDAP ID Store, using the following command line ldapcompare:
ldapcompare -h hostname -p port -D "bind_user_dn" -w bind_user_password -a userpassword -v appid_password_from_credstore -b "appid_dn"
If Step 3 does not run with positive results, it implies that the credential store password and the LDAP store password failed the comparison test. In this case, passwords in credential store and LDAP ID Store should be synched.
This section describes common problems and solutions for EPM Workspace. It contains the following topics:
Problem
Errors occur with certain functionality.
Solution
Check the status of Workspace by entering this URL:
http://server_name:19000/workspace/status
This URL displays a summary of any fatal errors that prevent Workspace from running, and a list of integrated products.
Enable the client debugging feature by selecting Navigate > Administer > Workspace Server Settings and selecting Client Debug Enabled.
All users who log on after selecting this option will be affected. The URLs that can be accessed include the following:
http://server_name:19000/workspace/debug/configInfo.jsp http://server_name:19000/workspace/debug/userInfo.jsp
The first URL shows information about the system including metadata from integrated products (for example, menus, preferences panels, and so on); the second URL shows information about the current user, including groups, effective roles, and Workspace menu items as interpreted and filtered for the current user.
Problem
The http://server_name:19000/workspace/ URL fails to respond or an error occurs.
Solution
Workspace initialization happens at the first request, not at server startup. If initialization fails, it is reattempted at every subsequent request. Any error during initialization is logged in the workspace.log file. The error message displays a page that replaces the normal Workspace Log on screen. Finally, the error is reported in the status report servlet, /workspace/status. Only the log files include Exception stack traces. The following tasks must successfully complete in order before Workspace allows logons, and can be matched up in the workspace.log file:
Parse and validate the file /conf/WSProducts.xml in the Workspace Web application.
Initialize the Shared Services Registry:
Connect to the Shared Services Registry.
Find the unique WORKSPACE component in the Shared Services Registry.
Find the unique Workspace LOGICAL_WEB_APP component in the Shared Services Registry.
View the Workspace configuration properties from LOGICAL_WEB_APP.
Find at least one WEB_SERVER component that is a child of WORKSPACE.
Update LOGICAL_WEB_APP with host and port information from the Oracle WebLogic Server MBean.
Update LOGICAL_WEB_APP with any missing configuration properties.
Initialize Shared Services.
Scan the Shared Services Registry for integrated products, and match every discovered product with a configuration file from the following resources:
/conf/WSProducts.xml (Workspace)
WorkspaceConfig file attribute of LOGICAL_WEB_APP (all other products)
Problem
Menu lists appear truncated in either height or width.
Solution
To resolve this issue:
From Microsoft Internet Explorer, choose Tools > Internet Options > Security > CustomLevel > Miscellaneous.
For Allow script-initiated windows without size or position constraints, select Enable.
This section describes common problems and solutions for Allocation Manager. It contains the following topics:
Problem
No Essbase applications are listed under the Essbase node.
Solution
This could be due to any of the following:
You are not provisioned to work with Allocation Manager. You must have at least one of the following access privileges to work with Allocation Manager:
Create General Ledger Allocation Rules
Administer Allocation Rules
Generate General Ledger Allocation Rules.
The Essbase cluster name is not Essbase_FA_Cluster. If the Essbase server is not under this cluster, it is ignored by Allocation Manager.
The stripe ID for General Ledger is different than the stripe ID for Workspace, so different security may be applied when Allocation Manager communicates with Essbase. Check the Allocation Manager log file to ensure that the stripe ID (or the application ID) for Allocation Manager is the same as the stripe ID for General Ledger.
The Essbase application contains an empty Comment field. Each Essbase application must contain at least one character in the Comment field, or it is ignored by Allocation Manager.
The application is not an Essbase aggregate storage application; only Essbase aggregate storage applications may be used with General Ledger.
Problem
Business rules cannot be deployed from Allocation Manager to General Ledger. You receive the error message:
no WSDLLOCATION set
Solution
In the EPM registry, ensure that the WSDLLOCATION property is defined for Allocation Manager. The WSDLLOCATION property contains the General Ledger web services URL.
This section describes common problems and solutions for Smart View. It contains the following topics:
Problem
Smart View may become disabled in Microsoft Office applications.
Solution
Smart View is a COM add-in, which Microsoft Office applications can disable. To re-enable Smart View, follow instructions in Excel Help for re-enabling COM add-ins.
Problem
Smart View collects and records events, errors, and other information in a log file, typically SmartViewLogs.log. When you experience performance or other issues, you can enable the logging in this file of additional information about profiling and requests and responses between Smart View and the server. This additional information can help Oracle Support to troubleshoot your issues.
Solution
To enable additional troubleshooting information:
Close all Microsoft Office applications.
Select Start, and then Run.
Enter regedit and click OK to open the registry.
Navigate to HKEY_CURRENT_USER\Software\Hyperion Solutions\HyperionSmartView\Options.
Right click Options, select New, and then String Value.
Name the new string value Profile.
Double-click Profile to open Edit String.
From Edit String, under Value Data, enter one of the following values:
0: Logging is not enabled. Initialized value bEnableProfiling is set to false.
1: Profile entries are logged when an event completes. This setting provides little information about abrupt terminations, but performance is better than with 2.
2: Profile entries are logged immediately. Use this setting to determine the function in which a termination occurred. This setting provides the most detailed information but has the greatest negative impact on performance.
Close the registry.
Restart Excel.
From the Smart View ribbon, select Options.
Go to the Advanced page and ensure that Route Messages to File is selected. The log file, typically SmartViewLogs.log, will now begin recording profiling and request/response information between Smart View and the server in addition to the other information it records.
Note:
To improve performance, when you no longer need to log profiling and request/response information, delete the Profile entry that you created in the registry.Problem
If the server takes longer to process a Smart View operation than the timeout value set on the client computer, users may receive a connection timeout error, or zero values may be displayed for Smart View functions.
Solution
Increase the timeout limit for Smart View client computers. Smart View uses Win-Inet APIs to communicate with the provider. These are the same modules that Internet Explorer uses. To increase the timeout value for a Windows client computer:
In the Windows registry of the client computer, navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\InternetSettings.
Set the following values:
"ReceiveTimeout"=dword:00dbba00 "KeepAliveTimeout"=dword:0002BF20 "ServerInfoTimeout"=dword:0002BF20
Problem
The Shared Connections panel of the Smart View Panel displays no server names. This typically happens when your applications are not properly registered during installation and configuration.
Solution
Review the information in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide to ensure that applications and servers are properly configured.
This section describes common problems and solutions for Financial Reporting. It contains the following topics:
This section describes common problems and solutions for setting up data sources and debugging setup and connectivity issues:
Problem
You are unable to connect to an Essbase cube.
Solution
Verify that the Essbase Server name and port are correct. Verify the user credentials used to make the connection are correct and the User has at least read rights to the cube.
Problem
An error occurred while creating a database connection.
Solution
Check the Financial Reporting log file. If the log file has the following error, a Catalog GUID refresh is required.
"Caused by: javax.jcr.LoginException: access denied for user to path /users/userid"
For more information, see "Regenerating User GUIDs" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.
Problem
You are unable to set up a database connection.
Solution
When you create a database connection, it is appended to the list in the Database Manager dialog box.
To add a database connection:
In Workspace, select Tools, then Database Connection Manager.
Click New.
In Database Connection Name, enter a name for the database connection.
Select a data source type of Essbase.
In Server, add the Essbase Server Name and Port Number.
Re-enter the User ID and Password.
To add application and database names, click the magnifying glass, and make your selections.
Note:
The Application Lookup button displays a tree view of the applications and corresponding databases; the applications are listed as parents and the databases are listed as children. You can search on an application or database. For data sources that are not associated with a database, only applications are listed.Click OK.
The database connection profile is appended to the list in Database Connection Manager dialog box.
This section describes common problems and solutions for setting up data sources and debugging setup and connectivity issues:
Problem
When running a report, following error is displayed:
Error 1012:Report contains an invalid grid. The following dimensions could not be found: <i>xxx</i>
Solution
This error may occur if the database was recently changed on the report. To resolve the issue, open and save the report that has mismatched dimensions. This causes the dimensions that existed in the old database connection but not in the new database connection to be removed. The dimension and its members that existed in the rows and columns are removed from the grid. If, as a result of the removal, no dimension exists in the row or column, you need to add a valid dimension to the cleared row or column in order for the report to run. Dimensions that exist in the new database connection but not in the old one, are added to the POV.
This section describes common problems and solutions for setting up data sources and debugging setup and connectivity issues:
Problem
Financial Reporting cannot be accessed from Workspace.
Solution
Check if the Financial Reporting web application is running. In Internet browser, enter protocol://server:port/hr/status.jsp. If the web application is running, the following message is displayed:
The Oracle© Hyperion Financial Reporting, Fusion Edition Web application is available.
View the Financial Reporting log file fr.log from the following directories to see if there are any com.sun.xml.ws.wsdl.parser related errors:
(UNIX) DOMAIN_HOME/servers/server_name/logs/financialreporting (Windows) DOMAIN_HOME\servers\server_name\logs\finsncialreporting
In this case, it is possible that analytics web application is not running. If fr.log contains multiple instances of Caused by: javax.jcr.LoginException: access denied for user to path /users/userid, then a Catalog GUID refresh is required.
For more information, see "Regenerating User GUIDs" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.
Problem
Unable to connect to Financial Reporting through a firewall from the Financial Reporting Studio.
Solution
By default, Financial Reporting components communicate with each other through Remote Method Invocation (RMI) on dynamically assigned Transmission Control Protocol (TCP) ports. To communicate through a firewall, you must specify the port for each Financial Reporting component separated by the firewall in the JConsole.exe file, and then open the necessary ports in your firewall. In addition, you may need to open ports for the Reports Server RDBMs, for data sources that you report against, and for LDAP/NTMLM for external authentication. The Print Server defaults to 8297. This can be changed by modifying the PrintServers property in FR Mbeans and restarting. Once connected, all RMI Services can use anonymous ports by default for communication. Alternatively a range of ports can be configured for communication by setting RMIPortRangeLower and RMIPortRangeUpper within the Financial Reporting configuration. You can change the port assignments to use in a firewall environment for servers in the Financial Reporting Mbeans called RMIPortRangeUpper and RMIPortRangeLower.
To locate the Financial Reporting MBeans properties to modify in Fusion Applications Control:
From the navigation pane, expand the BIDomain farm, Application Deployments, and then Internal Applications.
Expand FinancialReporting(11.1.1)(bi_cluster_name).
Right-click FinancialReporting(11.1.1)(bi_server_name) and choose System MBean Browser.
In the System MBean Browser page, expand Application Defined MBeans.
Expand Application Defined MBeans, com.hyperion, Server:bi_server_name.
Expand Financial Reporting.
Click Financial Reporting.
In the Application Defined MBeans: Financial Reporting page, scroll down to PrintServers, RMIPortRangeUpper, and RMIPortRangeLower.
Click on each attribute and add a value in the Value field and click Apply.
Problem
Financial Reporting Print server is not working.
Solution
To resolve this issue:
Ensure that the Financial Reporting Print Server service has been created and started.
Verify 32-bit Ghostscript is installed by running. From the Start menu, choose All Programs > Ghostscript.
Examine the FRPrintLogging.log file in the install_directory\Oracle\FinancialReportingStudio\diagnostics\logs\FinancialReporting directory.
Verify that the PrintServers property in Financial Reporting MBeans now shows the Financial Reporting Print Server computer and port number. The default port is 8297. This may show multiple financial Reporting Print Servers if more than one have been configured.
To locate the PrintServers property to modify in Fusion Applications Control:
From the navigation pane, expand the BIDomain farm, Application Deployments, and then Internal Applications.
Expand FinancialReporting(11.1.1)(bi_cluster_name).
Right-click FinancialReporting(11.1.1)(bi_server_name) and choose System MBean Browser.
In the System MBean Browser page, expand Application Defined MBeans.
Expand Application Defined MBeans, com.hyperion, Server:bi_server_name.
Expand Financial Reporting.
Click Financial Reporting.
In the Application Defined MBeans: Financial Reporting page, scroll down to PrintServers.
Click on the attribute and check the value in the Value field.
If necessary, adjust the value and click Apply.
Verify that the Financial Reporting Print Server server name and port can be reached from the Financial Reporting web application server machines. Use telnet to connect to the Financial Reporting Print Server.
Problem
When the Batch Scheduler is opened, the following error displays:
application HReports is not defined
This may happen if the fressclient.ear application is not started in the General Ledger's Oracle Enterprise Scheduler domain.
Solution
From the Oracle WebLogic Server Console for the Oracle Enterprise Scheduler domain, perform the following to steps:
Navigate to Deployments and select fressclient.
Select Start, then Servicing all Requests.
Problem
When the Batch Scheduler is opened, or at the time of job submission, permission errors are shown. This may happen if the user is not granted the oracle.as.scheduler.security.MetadataPermission permission.
Solution
Check if the user has oracle.as.scheduler.security.MetadataPermission permission in the fscm stripe using Fusion Applications Control.
Problem
All the jobs fail.
Solution
This may happen if the Essbase server is not running.
To check if the Essbase server is running and restart (if needed):
Determine the current status:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/bin/opmnctl status (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\bin/opmnctl status
OPMN generates a list of the running components and processes. The following message indicates that the Essbase Server (essbaseserver1) is already running:
Processes in Instance: BIInstance ---------------------------------+--------------------+---------+--------- ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------- essbaseserver1 | Essbase | 27879 | Alive coreapplication_obiccs1 | OracleBIClusterCo~ | 10828 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 18308 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 18337 | Alive coreapplication_obips1 | OracleBIPresentat~ | 26455 | Alive coreapplication_obis1 | OracleBIServerCom~ | 21716 | Alive
Restart the Essbase server:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/bin/opmnctl restartproc ias-component=component_name (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\bin\opmnctl restartproc ias-component=component_name
For example
APPLICATIONS_CONFIG_HOME/BIInstance/bin/opmnctl restartproc ias-component=essbaseserver1
This section describes common problems and solutions for Oracle Hyperion Provider Services. It contains the following topics:
Problem
Provider Services appears not to be functional. You may need to determine whether Provider Services is running.
Solution
To determine whether Provider Services is running:
Launch a web browser.
Enter the connection URL for the corresponding products:
Smart View Provider: https://Provider_Services_server:Provider_Services_port/aps/SmartView
Java API: https://Provider_Services_server:Provider_Services_port/aps/JAPI
If an HTTP error is returned, the Provider Services server is not running.
You may need to find out if you are connecting to the right port.
If you are running Provider Services with Oracle Access Manager, then the default Provider Services port number is 9704. If you are not running Provider Services with Oracle Access Manager, then the default Provider Services port number is 4443.
To start the Provider Services server, use the following script from the fusionapps Middleware directory:
(UNIX) FA_MW_HOME/user_projects/domains/bi_foundation_domain_name/bin/startWebLogic.sh (Windows) FA_MW_HOME\user_projects\domains\bi_foundation_dmain_name\bin\startWebLogic.cmd
Problem
Provider Services version information is not provided in a user interface.
Solution
You can find the Provider Services version information in the following locations:
Operating system console window that is displayed when the Provider Services server is running
Provider Services log files
Problem
In Excel, a Maximum numbers of rows [5000] Exceeded error is returned if there are more than 5,000 rows on the Smart View grid. By default, the maximum number of rows is set to 5000 and the maximum number of columns to 256. In Excel 2003, you cannot exceed these limits. However, in Excel 2007 and 2010, there are no limits on the number of rows or columns, and you can change the default settings.
Solution
To change maximum row and column settings in Excel 2007 or 2010:
Launch Excel.
From the Smart View ribbon, select Open, and then Smart View Panel.
In the Smart View Panel, click Edit Provider Services to open the Provider Services server preferences dialog box.
Change the settings for Number of Rows and Number of Columns as needed. Enter 0 to remove any limits to the number of rows or columns.
Problem
You may need to monitor the number of sessions on a Provider Services server.
Solution
To monitor Provider Services server sessions, from Administration Services Console:
From Enterprise View or a custom view, under the Provider Services node, select a provider.
Under the provider node, select Action, and then Sessions.
Problem
You may need to monitor active-active Essbase clusters.
Solution
To monitor Provider Services server sessions, from Administration Services Console:
From Enterprise View or a custom view, under the Provider Services node, select a provider.
Under the provider node, expand Essbase Clusters and select the active-active Essbase cluster node you want to monitor.
Choose Action, and then edit the active-active Essbase cluster.
Problem
You may need to enable or disable individual active-active Essbase cluster components.
Solution
To enable or disable an active-active Essbase cluster component, follow the steps in the Oracle Hyperion Enterprise Performance Management System High Availability and Disaster Recovery Guide.
This section describes common problems and solutions. It contains the following topics:
Essbase Agent Startup Fails Due to serviceinstanceref ref="audit" Entry in jps-config-jse.xml
Essbase Agent Startup Fails with an Error While Loading Shared Libraries
Unable to Write File During Data Load or Building Aggregate Views
Log files are the best tools for analyzing what might be wrong with the system configuration. The logging configuration file, the defaults it ships with, and instructions for changing change those defaults will help with the analysis.
Essbase log files
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/Essbase.log (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\essbase\Essbase.log
Oracle Diagnostic Logging (ODL) logs
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/ESSBASE_ODL.log (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\essbase\ESSBASE_ODL.log
Lease Manager logs
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/leasemanager_essbase_machine_name.log (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\leasemanager_essbase_machine_name.log
Shared Services logs
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/SharedServices_Security_Client.log (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\SharedServices_Security_Client.log
OPMN Logs
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/diagnostics/logs/OPMN/opmn/opmn.log (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\diagnostics\logs\OPMN\opmn\opmn.log
Esssbase ping log
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/diagnostics/logs/OPMN/opmn/EssbasePing.log (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\diagnostics\logs\OPMN\opmn\EssbasePing.log
OPMN debug log
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/diagnostics/logs/OPMN/opmn/debug.log (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\diagnostics\logs\OPMN\opmn\debug.log
Note:
The system will generate the OPMN debug log only if DEBUG mode is turned on inopmn.xml.OPMN console log
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/diagnostics/logs/OPMN/opmn/console*.log (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\diagnostics\logs\OPMN\opmn\console*.log
Note:
The system will generate the OPMN console log only ifDEBUG mode is turned on in opmn.xml.Problem
The Essbase Agent startup fails with the following error:
Fatal Error: FUSIONAPPID not specified in the cfg file
Solution
To modify essbase.cfg and restart the Essbase server:
Locate the essbase.cfg file in the following directories:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/Essbase/essbaseserver_name/bin (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\Essbase\essbaseserver_name\bin
Make sure that the following entry is present in essbase.cfg:
FUSIONAPPID appidname
Restart the Essbase server.
To restart the Essbase server using opmnctl:
Determine the current status:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/bin/opmnctl status (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\bin/opmnctl status
OPMN generates a list of the running components and processes. The following message indicates that the Essbase Server (essbaseserver1) is already running:
Processes in Instance: BIInstance ---------------------------------+--------------------+---------+--------- ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------- essbaseserver1 | Essbase | 27879 | Alive coreapplication_obiccs1 | OracleBIClusterCo~ | 10828 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 18308 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 18337 | Alive coreapplication_obips1 | OracleBIPresentat~ | 26455 | Alive coreapplication_obis1 | OracleBIServerCom~ | 21716 | Alive
Restart the Essbase server:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/bin/opmnctl restartproc ias-component=component_name (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\bin\opmnctl restartproc ias-component=component_name
For example
APPLICATIONS_CONFIG_HOME/BIInstance/bin/opmnctl restartproc ias-component=essbaseserver1
To start Essbase server using Fusion Applications Control:
From the navigation pane, expand the farm and then WebLogic Domain for the BIDomain domain.
Expand Essbase Servers, and then select the Essbase server.
From the Essbase Server menu, choose Administration, then Ports Configuration.
Select the Listen port, and then click Edit.
Change the port number, and then click OK.
From the Essbase Server menu, choose Control, then Restart.
Problem
The Essbase Agent startup fails with the following error:
1051223 - Single Sign On function call [css_init] failed with error [CSS Error: CSS method invocation error: getInstance: Failed to get CSSSystem instance, please check SharedServices_Security_Client.log for more information
Solution
To modify essbase.cfg and restart the Essbase server:
Locate the essbase.cfg file in the following directories:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/Essbase/essbaseserver_name/bin (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\Essbase\essbaseserver_name\bin
Make sure that the following entry is commented out using XML style comments in the essbase.cfg file. For example, <!-- -->:
serviceinstanceref ref="audit"
Restart the Essbase server.
To restart the Essbase server using opmnctl:
Determine the current status:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/bin/opmnctl status (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\bin/opmnctl status
OPMN generates a list of the running components and processes. The following message indicates that the Essbase Server (essbaseserver1) is already running:
Processes in Instance: BIInstance ---------------------------------+--------------------+---------+--------- ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------- essbaseserver1 | Essbase | 27879 | Alive coreapplication_obiccs1 | OracleBIClusterCo~ | 10828 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 18308 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 18337 | Alive coreapplication_obips1 | OracleBIPresentat~ | 26455 | Alive coreapplication_obis1 | OracleBIServerCom~ | 21716 | Alive
Restart the Essbase server:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/bin/opmnctl restartproc ias-component=component_name (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\bin\opmnctl restartproc ias-component=component_name
For example
APPLICATIONS_CONFIG_HOME/BIInstance/bin/opmnctl restartproc ias-component=essbaseserver1
To start the Essbase server using Fusion Applications Control:
From the navigation pane, expand the farm and then WebLogic Domain for the BIDomain domain.
Expand Essbase Servers, and then select the Essbase server.
From the Essbase Server menu, choose Administration, then Ports Configuration.
Select the Listen port, and then click Edit.
Change the port number, and then click OK.
From the Essbase Server menu, choose Control, then Restart.
Problem
The Essbase Agent startup fails with the following error:
Error while loading shared libraries: libARicu24.so: cannot open shared object file: No such file or directory
Solution
To modify opmn.xml file and restart the Essbase server:
Locate the opmn.xml file in the following directories:
(UNIX) APPLICATIONS_CONFIG_HOME/config/OPMN/opmn (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\config\OPMN\opmn
Update the following ODBC-related entries in opmn.xml:
<variable append="true" id="LD_LIBRARY_PATH" value="$ORACLE_HOME/common/ODBC/Merant/6.0/lib$:$ORACLE_HOME/jdk/jre/lib/i386/server$:$ESSBASEPATH/bin"/>
<variable id="ODBCINI" value="$ORACLE_HOME/common/ODBC/Merant/6.0/odbc.ini"/>
<variable id="ODBCINST" value="$ORACLE_HOME/common/ODBC/Merant/6.0/odbcinst.ini"/>
Restart the Essbase server:
Determine the current status:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/bin/opmnctl status (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\bin/opmnctl status
OPMN generates a list of the running components and processes. The following message indicates that the Essbase Server (essbaseserver1) is currently running:
Processes in Instance: BIInstance ---------------------------------+--------------------+---------+--------- ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------- essbaseserver1 | Essbase | 27879 | Alive coreapplication_obiccs1 | OracleBIClusterCo~ | 10828 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 18308 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 18337 | Alive coreapplication_obips1 | OracleBIPresentat~ | 26455 | Alive coreapplication_obis1 | OracleBIServerCom~ | 21716 | Alive
Restart the Essbase server:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/bin/opmnctl restartproc ias-component=component_name (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\bin\opmnctl restartproc ias-component=component_name
For example
APPLICATIONS_CONFIG_HOME/BIInstance/bin/opmnctl restartproc ias-component=essbaseserver1
Problem
A communication error occurs when attempting to issue commands using the opmnctl command line for OPMN.
For example:
qtfhp3:/vol1/nnguyen/rc11/Oracle/Middleware/user_projects/epmsystem1/bin]$ opmnctl status RCV: No such file or directory Communication error with the OPMN server local port. Check the OPMN log files opmnctl status: opmn is not running.
Solution
To modify opmn.xml:
Edit opmn.xml to assign a different local and a remote port to OPMN, or just a remote port to OPMN. The currently assigned ports may already be used by another process. See the following example:
<notification-server interface="any"> <ipaddr remote="<hostname>"/> <port local="6711" remote="6712"/>
Restart OPMN and try the opmnctl command again.
Problem
An Essbase application stops responding or shuts down abnormally.
Solution
To determine why the application is not responding:
Check the Essbase.log file for the following error message:
1002089 RECEIVED ABNORMAL SHUTDOWN COMMAND - APPLICATION TERMINATING
Check the Essbase.log file for the following message:
Exception error log [log00001.xcp] is being created...
If either of the above messages are found, contact Technical Support.
Note that if you find the log00001.xcp file, save it. Oracle Support will need this file to troubleshoot the issue.
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/app/appname/log000001.xcp (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\essbase\app\appname\log000001.xcp
Problem
An application does not respond after being started, or an error message like the following is displayed in the Essbase log file:
Network Error 10048 : Unable to Bind Host Server Socket On Port 4213
Solution
A port conflict may be occurring. Correct the port-related entries in opmn.xml.
For example, update the Essbase port range to match the port that Essbase is actually using:
<port id="essbase-port-range" range="32768-33768"/>
Problem
During an operation on an Essbase aggregate storage database, the following error is displayed:
Persistent data does not match the outline. There is no member in dimension [Abc] for member number [12345]. Data is corrupted.
Solution
To clear the database and reload it from the original sources or from a saved exported backup:
Save the list of current aggregate views.
Clear all data in the database.
Reload the data from original sources or from a backup.
Rebuild the aggregate views using the list specified.
Problem
You do not know the Essbase login credentials when Essbase is included in the Oracle Business Intelligence installation.
Solution
Use the Weblogic default user name and password to log in to Essbase. The default user name and password are weblogic and welcome1.
Problem
An Essbase application process cannot be shut down.
Solution
To check the application log for active processing:
Access the application log. Note the following locations:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/app/appname/appname.log (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\essbase\app\appname\appname.log
Check the application log and look for the following message:
RECEIVED SHUTDOWN COMMAND - SERVER TERMINATING.
If you see the proceeding message, wait a few minutes to allow the application to self-terminate. The application may be doing cleanup tasks associated with the shutdown process.
If you see the following message, the application is still processing user requests. Wait for user requests or any other operation that is still in progress to terminate, and then try shutting down the application.
Cannot unload database <dbname> while user <username> is performing database operation. Wait for the user to complete the operation, or ask the user to abort it. Log out all users and then unload the database. Cannot unload database <dbname> when it is still in use
If you need to terminate the application, perform the following steps:
If you need to terminate the application even when there are user requests in progress on the database, you can run the following sequence MaxL statements to forcefully terminate user requests:
#Display active sessions to see current requests display session on application <appname> #Disallow new connections to the application alter application <appname> disable connects; #Force logout of all, and terminate requests alter system logout session on database <appname>.<dbname> force;
After forcefully logging out all users, wait for a few minutes, and then use the following MaxL statement to check if any user requests are still running:
#Display active sessions display session on application <appname>;
If there are no requests running, attempt to stop the application process.
Problem
The Essbase port numbers need to be changed when Essbase is installed in high-availability mode.
Solution
To run the Essbase failover automation script to change the Essbase port:
Go to the following location:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/bin/essbase_ha (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\bin\essbase_ha
Look for the %SHARED_FOLDER% location specified in the file essfoenv.properties.
Edit the %SHARED_FOLDER%\EssFoConfig.properties file or %SHARED_FOLDER%/EssFoConfig.properties file.
Look for SYSTEM_AGENT_PORTNUMBER(1|2), and change the port number. There are two Essbase instances, so make sure to change the one that you need.
Execute essfoconfig.sh (UNIX) or essfoconfig.bat (Windows) without any parameter. The Help prints so you can see a list of options for parameters.
Execute the following command:
essfoconfig.sh update prpName
where prpName is the port number property in Step 4.
For example, the following command updates the agent port of the first Essbase instance:
essfoconfig.sh update SYSTEM_AGENT_PORTNUMBER1
Problem
The Essbase port numbers need to be changed when Essbase is installed in non-high-availability mode.
Solution
Go to Fusion Applications Control and change the Essbase port.
From the navigation pane, expand the farm and then WebLogic Domain for the BIDomain domain.
Expand Essbase Servers, and then select the Essbase server.
From the Essbase Server menu, choose Administration, then Ports Configuration.
Select the Listen port, and then click Edit.
Change the port number, and then click OK.
Restart Essbase server. From the Essbase Server menu, choose Control, then Restart.
Problem
Following a data load failure to a specified load buffer, the following error displays for subsequent loads to the same load buffer:
Data load buffer [123] does not exist.
Solution
This error may occur when data loads initialize a load buffer and load multiple data files to it before committing it to the cube. If an error occurs that causes one of the steps to fail, then the load buffer is automatically destroyed, causing all subsequent steps to fail with the previous error.
Use one of the following methods to correct this error:
Determine the cause of the original data load error and try to resolve it.
Set the Essbase data load options to indicate that the data load should not be aborted on error; instead, have data load errors written or appended to the log file
Problem
Upon attempting to load data into an Essbase aggregate storage database, the following error displays:
Specified load buffer resource usage [100] is above currently available value [0].
Solution
Other ongoing data load operations have reserved part of the cache for their load buffers. Use one of the following methods to correct this error:
Reduce the resource usage for this data load, and try again. If you are using MaxL, you must explicitly create the load buffer, using the optional resource_usage argument. For example:
alter database AsoSamp.Sample initialize load_buffer with buffer_id 1 resource_usage .5;
Wait for other operations to finish.
To see what reservations have been made to the cache resources, run the following MaxL statement:
query database "app"."db" list load_buffers;
For more information about the query database, alter database, and other MaxL statements, see the Oracle Essbase Technical Reference.
Problem
Essbase does not start when it is in cluster mode and Oracle Business Intelligence domain is installed with a non-domain-qualified host name.
Solution
The error occurs when the Essbase host specified in the cluster configuration properties file, EssFOConfig.properties, is domain-qualified, but is not in the EPM Registry, leading to a mismatch.
For more information about viewing the EPM Registry, see the "Viewing the Components in the Shared Services Registry," section in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
To check if there is an Essbase host name qualification mismatch:
Use the following command to return all the Essbase clusters that were configured in the registry:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/config/foundation/11.1.2/epmsys_registry.sh view CLUSTER (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\config\foundation\11.1.2\epmsys_registry.bat view CLUSTER
Drill into the specific Essbase Server instance underneath this cluster, and view that node to see the host name:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/config/foundation/11.1.2/epmsys_registry.sh view #Essbase_Server_GUID (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\config\foundation\11.1.2\epmsys_registry.bat view #Essbase_Server_GUID
Note that GUID is the global unique ID of an Essbase Server instance as returned from the full viewing of the EPM Registry.
Access the EPM registry and confirm that the host in the cluster configuration properties file displays exactly how Essbase is configured in the EPM Registry.
Restart Essbase.
Problem
When the user attempts to log in to Essbase, the login attempt fails. The problem may be an authentication failure. When the Essbase login fails due to an authentication problem, it reports the following errors:
ERROR - 103 - Unexpected Essbase error 1051440.
ERROR - 1051440 - Essbase user [bi-001] Authentication Fails against the Shared Services Server with Error [EPMCSS-1009004: Failed to read data from the policy store.].
Solution
To determine login failure problems by gathering detailed error messages:
Locate the essbase.cfg file in the following directories:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/Essbase/essbaseserver_name/bin (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\Essbase\essbaseserver_name\bin
Using a text editor, add the following text on its own line:
LOGINFAILUREMESSAGEDETAILED
For more information about this and other essbase.cfg configuration settings, see the Oracle Essbase Technical Reference.
Stop and restart the Essbase server. For detailed procedures, see "Starting and Stopping Essbase Server" in the Oracle Essbase Database Administrator's Guide.
Use the following paths to access the Essbase.log file, which contains any error messages:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/Essbase.log (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\essbase\Eessbase.log
In the same path where Essbase.log is found, see the SharedServices_Security_Client.log to locate security-related error messages.
To gather debug-level error messages:
Note:
Keep the debug statistics available for diagnostic purposes, in case you need to contact Technical Support.Locate the essbase.cfg file in the following directories:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/Essbase/essbaseserver_name/bin (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\Essbase\essbaseserver_name\bin
Using a text editor, add the following text on its own line:
AGENTLOGMESSAGELEVEL DEBUG
For more information about this and other essbase.cfg configuration settings, see Oracle Essbase Technical Reference.
Stop and restart the Essbase server. For detailed procedures, see the "Starting and Stopping Essbase Server" section in Oracle Essbase Database Administrator's Guide.
Use the following paths to access the Essbase.log file, which contains any error messages:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/Essbase.log (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\essbase\Eessbase.log
To check for and correct BI domain login errors:
See Table 18-3 to identify if you have a debug login failure problem. Go to each file listed in the table and search for the corresponding error message. If one or both of your files contain errors, use the following procedure to correct them.
Table 18-3 File Names and Error Messages
| File Name | Error Message |
|---|---|
|
|
|
|
|
|
To add a valid Essbase user name to the credential store from Fusion Applications Control, perform the following:
From the navigation pane, expand the farm and then WebLogic Domain for the BIDomain domain.
Right-click BIDomain and click Security.
Click Credentials. The Credentials page displays.
In the Credential table, expand essbaseserver.
Select the Essbase server and click the Edit the selected credential key button. The Edit Key page displays.
Verify that the user name and password are correct.
Problem
The following error occurs on a UNIX platform:
Failed to open file [filename]: a system file error occurred. Please see application log for details.
Solution
To open a file on UNIX:
Confirm that the specified file exists.
If the file exists, increase the maximum number of open file descriptors. To do this, consult the UNIX operating system's documentation for the ulimit command.
Problem
GL writeback fails with the following error:
The accounting date conversion failed for %s to %s in the ACCOUNTING_DATE column. Unable to proceed with GL export.
Problem
This error may occur when GL writeback cannot format the date string in the way that GL tables expect.
To fix this issue, make sure that the <DATE_FORMAT> tag in the cubeMap.xml file has date format represented in one of the following acceptable formats, and that it matches with the date value stored in the accounting date alias table of the outline. The following are the acceptable date formats:
mon dd yyyy Month dd yyyy mm/dd/yy mm/dd/yyyy yy.mm.dd dd/mm/yy dd.mm.yy dd-mm-yy dd Month yy dd mon yy Month dd, yy mon dd, yy mm-dd-yy yy/mm/dd yymmdd dd Month yyyy dd mon yyyy dd/mon/yy yyyy-mm-dd yyyy/mm/dd Day, Month dd, yyyy
Problem
GL writeback fails with the following error:
The group id node has active GL operations in state [<state_name>]. Use the appropriate API call in sequence. Unable to proceed with [api name] call.
Solution
This error may occur if more than one user tries to use the GL writeback-related API calls with the same group ID. To fix this issue, ensure that all users using GL writeback operations are using different group IDs.
Problem
GL writeback fails with the following error:
This application is not a valid GL application for Essbase.
Solution
The error may occur if the cubeMap.xml file is either not present in the app/ db directory, or is not parsed properly. For the GL writeback to work properly, the cubeMap.xml file must be present and contain the required information to be parsed successfully.
To confirm that cubeMap.xml was parsed correctly:
Ensure that cubeMap.xml file exists in the app/ db directory and contains the correct information.
To ensure that cubeMap.xml was found and parsed successfully, check the Essbase application log for the following entry:
Parsing of cubeMap.xml file succeeded
Problem
GL writeback fails with the following error:
Failed to Establish Connection With SQL Database Server. See log for more information.
Solution
The error may occur if the SQL drivers are not set up correctly.
To confirm that the SQL drivers are set up correctly:
Ensure that the ODBC Merant drivers path in odbcinst.ini is correct.
Ensure that the ODBCINST variable in opmn.xml is pointing to the correct odbcinst.ini file.
Ensure that an Oracle GL target database is running. For the GL writeback to work, a GL system is required, with cubeMap.xml correctly set up with the GL system information as follows:
<HOST>somemachine.company.com</HOST> <PORT>port</PORT> <SID>SID</SID>
Ensure that Essbase.cfg contains driver descriptors information in the following format, so that Essbase can connect to drivers in the odbcinst.ini:
BPM_Oracle_DriverDescriptor "DataDirect 6.0 Oracle Wire Protocol"
Problem
When performing an operation against an Essbase cube, one of the following errors occurs:
Network error [12345]: Cannot Send Data
Network error [12345]: Cannot Receive Data
Solution
The error may indicate that Essbase has terminated abnormally. If an xcp file is found in the following location, save it and contact Oracle Support:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/app/appname/log000001.xcp (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\essbase\app\appname\log000001.xcp
In essbase.cfg, increase the network timeout parameters using the settings NETDELAY and NETRETRYCOUNT. For more information, see "Essbase.cfg Configuration Settings" in Oracle Essbase Technical Reference.
Problem
OPMN fails to start Essbase in high-availability mode.
Solution
For Essbase clustering to work, all Essbase failover cluster data must be on shared storage with the ARBORPATH variables set correctly.
To confirm that Essbase can start in high-availability mode:
Ensure that OPMN is started by a network or domain user.
Ensure that ARBORPATHs are specified as mapped drives, and not as UNC paths.
Problem 1
During a dimension build or outline restructure, error code 1130203 occurs.
Solution 1
The error indicates that not enough memory was available to perform the operation. Use one of the following methods to correct this error:
Increase the amount of virtual memory available to the operating system.
If Essbase is running on a 32-bit platform, keep in mind that the maximum memory available to Essbase is between 2 GB and 4 GB, regardless of how much RAM is installed on the machine. Because Essbase loads both the old and new outlines in memory during the restructure, there is a restriction on the largest outline that can be modified on such a machine. For example, if the platform only allows 2 GB of memory to be used by a process, and an Essbase application process is already using 200 MB memory, then the maximum-size outline that can be modified is 900 MB. Switching to a 64-bit installation of Essbase will lift this limitation.
Problem 2
During dimension build or outline restructure, outline validation fails with one of the following errors:
There were errors validating the outline. Please check the error file.
Outline has errors
Solution 2
Review the application log or the error file (if available) to see what specific errors are causing the validation error.
Problem 3
During dimension build or outline restructure, one of the following errors occurs:
Cannot write the new outline file during the restructuring of [%s]
Error writing outline change log file for database [%s]
Solution 3
Check the application log for other errors. If none are found, check to see if the file system is full. Remember that making a change to an Essbase outline requires at least as much free space as the existing outline.
Problem
The Console.log displays the following error:
Fatal Error: Invalid item index in security file
Solution
The Essbase security file, essbase.sec, is invalid. Use one of the following methods to correct this error:
Restart Essbase using the latest backup security file by copying essbase_timestamp.bak to essbase.sec. Both files are located in the following directories
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/Essbase/essbaseserver_name/bin (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\Essbase\essbaseserver_name\bin
For more information, see "Managing the Essbase Security File" in Oracle Essbase Database Administrator's Guide.
Open the essbase.cfg file and set the ENABLESWITCHTOBACKUPFILE setting to TRUE. This setting allows Essbase to automatically use a backup security file. The essbase.cfg file is located in the following directories:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/Essbase/essbaseserver_name/bin (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\Essbase\essbaseserver_name\bin
If you edit Essbase.cfg, restart Essbase to enable the change.
For more information, see "Essbase.cfg Configuration Settings" in Oracle Essbase Technical Reference.
Problem
The Administrator does not know if Essbase is running.
Solution
Use the following OPMN command to determine if the Essbase agent is running:
(UNIX) APPLICATIONS_CONFIG_HOME/BIInstance/bin/opmnctl status (Windows) APPLICATIONS_CONFIG_HOME\BIInstance\bin/opmnctl status
To start Essbase server using Fusion Applications Control:
From the navigation pane, expand the farm and then WebLogic Domain for the BIDomain domain.
Expand Essbase Servers, and then select the Essbase server to see if it is running.
If it is not running, From the Essbase Server menu, choose Control, then Restart.
Problem
When attempting to load data into an Essbase aggregate storage database or while building aggregate views, the following error is displayed:
Failed to extend file [<path>/ess0001.dat]: a system file error occurred. Please see application log for details.
Solution
This error indicates that the file system is out of space. Essbase can require significant temporary disk storage while performing a data load or aggregate view build. The "default" tablespace is the location where cube data is stored. The "temp" tablespace is where Essbase writes temporary data while building the cube. By default, both tablespaces are on the disk drive where Essbase is installed.
During the operation, the space required by the temp tablespace is at least as big as the resulting change in the database size, so the total free space required is at least twice as big as the resulting change to the database size. For example, loading a database that is 1GB will require at least 2GB of free space. Building 10GB worth of aggregate views will require at least 20GB of free space. Note that after the operation is complete, the files created in the temp tablespace are deleted.
Use one of the following methods to correct this error:
To correct this error, use MaxL statements to view or change the tablespace settings.
If the tablespace locations do not have enough free space, consider moving one or both tablespaces to different disk drives, or limit the size of the existing file locations and add new locations on other disk drives. Note that you cannot remove a tablespace location that already contains data.
You can use My Oracle Support (formerly MetaLink) to help resolve Oracle Fusion Applications problems. My Oracle Support contains several useful troubleshooting resources, such as:
Knowledge base articles
Community forums and discussions
Patches and upgrades
Certification information
You can access My Oracle Support at https://support.oracle.com.
|
 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|