| Oracle® Business Intelligence Applications Installation and Configuration Guide Version 7.9.4 E10742-01 |
|
 Previous |
 Next |
| Oracle® Business Intelligence Applications Installation and Configuration Guide Version 7.9.4 E10742-01 |
|
Previous |
Next |
This chapter details some common problems related to the Oracle Business Analytics Warehouse and suggests possible solutions. It contains the following topics:
Section H.1, "Oracle Business Analytics Warehouse Installation and Initial Configuration Issues"
Section H.3, "Unicode Issues with Informatica and the Oracle Business Analytics Warehouse"
Section H.4, "UNIX Installation Issues with the Oracle Business Analytics Warehouse"
Section H.5, "Oracle Business Analytics Warehouse Upgrade Issues"
Note: When you troubleshoot installation and configuration issues, use the following log information:
On Windows:
the Informatica Server Log (check the Informatica Event Viewer)
the Informatica Rep Server Log (check the Informatica Event Viewer)
the Informatica Repagent Log (check the Informatica Event Viewer)
the workflow log (located in ..\Informatica\Server\WorkFlowLogs)
the session log for the session that fails (located in ..\Informatica\Server\SessLogs)
the (Teradata) loader logs (located in ..\Informatica\Server\Tgtfiles)
the Data Warehouse Application Console logs (located in the \DAC\log directory)
On UNIX:
the Informatica Server Log (located in ..informatica/server/server.log)
the Informatica Rep Server Log (located in ..informatica/repserver/repserver.log)
the Informatica Repagent Log (located in ..informatica/repserver/reagent.log)
the workflow log (located in ../informatica/Server/WorkFlowLogs)
the session log for the session that fails (located in ../informatica/Server/SessLogs)
the (Teradata) loader logs (located in ../informatica/Server/Tgtfiles)
the Data Warehouse Application Console logs (located in the /DAC/log directory)
Table H-1 provides information about problems and solutions related to the installation and initial configuration of the Oracle Business Analytics Warehouse.
Table H-1 Oracle Business Analytics Warehouse Installation and Configuration Issues
| Symptom/Error Message | Probable Cause/Solution |
|---|---|
|
Cannot connect to the Oracle Business Analytics Warehouse running on DB2. |
Make sure that the DB2 configuration matches the requirements listed in Section 3.4, "IBM DB2 UDB-Specific Database Guidelines for Oracle Business Analytics Warehouse". |
|
After installing Informatica's ODBC driver (V3.5) on a Windows computer, you cannot open the Query Analyzer, and the Enterprise Manager shows an error message. |
The ODBC driver installation replaces the odbcbcp.dll file with an older version. The Informatica documentation contains the procedure for correcting this problem. |
|
Cannot connect to Oracle Business Analytics Warehouse from Informatica. |
Make sure that the server running the Informatica Server software has an ODBC connection to the Oracle Business Analytics Warehouse using a Siebel ODBC driver and an ODBC connection to the Oracle Business Analytics Warehouse using the Merant Closed 3.5 32-bit driver. |
|
Error: ORA-12541: TNS:no listener. |
Check the Compatibility tab in Informatica service configuration. It should be Oracle 8. If it is not set to Oracle 8, change it and restart the Informatica server. |
|
Error 2140 (Informatica service failed to start). |
The server may not be started or the Informatica Service may not be started. See Informatica's installation and configuration guide on Siebel eBusiness Third-Party Bookshelf for detailed information. |
|
Informatica installation fails with an Unhandled Exception error and displays a message similar to this: "Error Number: 0x80040707. Description: Dll function call crashed: ISRT._DoInstall." |
The computer is probably running out of virtual memory. Restart the computer and reinstall Informatica. |
|
After selecting "Warehouse Default Amount (Yen)" as the currency symbol, the dollar sign ($) is still displayed. |
The currencies.xml file must be edited. For instructions, see Appendix B, "Changing the Default Currency in Analytics Applications". |
Table H-2 provides information about problems and solutions related to issues with Informatica and loading. To view the Informatica log file details, double-click the workflow.
Table H-2 Informatica and Loading Issues
Table H-3 provides information about problems and solutions related to Unicode issues with Informatica and the Oracle Business Analytics Warehouse.
Table H-3 Unicode Issues with Informatica and Oracle Business Analytics Warehouse
| Symptom/Error Message | Probable Cause/Solution |
|---|---|
|
Task fails and generates the error message: "TRANSF_1_1_1_1> TE_7073 Aggregate Error: Expecting keys to be ascending." Tasks known to fail are SDE_DtlForecastFact and SDE_CostList |
In Informatica Mapping Designer, open the corresponding mapping and in the Aggregator transformation, remove the check from the Sortedinput check box. |
|
In the Windows 2000 environment, with a double-byte language, such as Japanese, when you try to input the path for the directory where Informatica is installed for the value $PMRootDir in the Workflow Manager, the double-byte characters are converted to question marks. This causes the ETL to fail because it cannot find the Informatica Server folder and its subdirectories. |
Share the folder under a new name with no double-byte characters, and use the network share as the value for $PMRootDir. |
|
When Configuring the Informatica Server or Informatica Repository Server, there are major truncations in some of the tabs. For example, in the Server tab and the Repository tab in the Configure Informatica Service screen (choose Start, then Programs, then Informatica Server, then Informatica Server Setup, then Configure Informatica Service), the field names are truncated. |
Informatica 6.x does not support non-English messages and resources. Delete the following files to display all messages in English. PC/PM client folder\*411.dll PMServer folder\bin\*411.dll PMRepServer folder\bin\*411.dll |
|
Unable to start the Informatica repository with the Informatica Repository Server on UNIX. The Oracle_BI_DW_Base (MS Windows Japanese and superset of Shift-JIS) is not compatible with that of pmrepagent (UTF-8 encoding of Unicode). |
Make sure Japanese locales are installed on the UNIX machine. The environment variables on the UNIX machine are not complete. Set the environment variable PM_CODEPAGENAME to MS932. For other languages, set the variable appropriately. |
|
The database connection code page is incorrect for Unicode/Non-Latin code pages. |
The database connection code page has to be set manually through the Informatica Workflow Manager.
|
|
Unable to install Informatica PowerMart on non-English UNIX locales (for example, ESN, DEU, FRA, ITA). The following error message appears: "FATAL ERROR during initialization, Invalid language specified, Application terminated." |
This error will occur when the locale environment variables are set inconsistently or not at all. These settings are determined by entering the command |
Table H-4 provides information about issues related to installing the Oracle Business Analytics Warehouse on UNIX.
Table H-4 UNIX Installation Issues with Oracle Business Analytics Warehouse
| Symptom/Error Message | Probable Cause/Solution |
|---|---|
|
When starting Informatica in pmserver.log, the following error messages appear: FATAL ERROR: LM_36023 [Tue Mar 11 23:12:41 2003]: (9968|1) The IP address [172.0.129.141] for this machine did not match the IP address [172.20.94] in the repository for server [ORACLE_BI_DW_SERVER]. FATAL ERROR: SF_34014 [Tue Mar 11 23:13:41 2003]: (9968|1) Server initialization failed. INFO: SF_34014 [Tue Mar 11 23:13:41 2003]: (9968|1) Server shut down. |
Launch Workflow Manager, then right-click on Oracle_BI_DW_Base and click More. Make sure the Host Name is the machine name where the Informatica Repository Server resides. |
|
When connecting to the Informatica Repository Server from the Repository Administration Console, the following error messages appear:
|
Use Oracle 32-bit library.
DB2 databases running on AIX: Database Connection Error: Database driver event...Error occurred loading library [No such file or directory] Database driver event...Error occurred loading library [libpmdb2.a]
|
|
When restoring the Informatica Repository, the following error message appears in the dwdb.log: ERROR: OBJM_54543 [Tue Mar 25 17:47:16 2003]: (164|2484) DataBase error: ORA-01461: can bind a LONG value only for insert into a LONG column |
The database is Unicode and the environment variable is needed.
|
|
When starting pmserver on UNIX, the following error message appears: INFO: LM_36039 [Thu Mar 27 11:40:29 2003]: (6772|1) The maximum number of sessions that can run simultaneously is [10]. FATAL ERROR: CMN_1011 [Thu Mar 27 11:40:29 2003]: (6772|1) Error allocating system shared memory of [3000000] bytes for [Load Manager Shared Memory]. Error is [0]: [] FATAL ERROR: SF_34004 [Thu Mar 27 11:40:29 2003]: (6772|1) Server initialization failed. INFO: SF_34014 [Thu Mar 27 11:40:29 2003]: (6772|1) Server shut down. |
In the pmserver.cfg file, change MaxSessions to Note: For each 10 count increase of MaxSessions, increase the LMSharedMem by 2000000 bytes. |
|
A session fails (any session), and the following error message appears: TM_6227 Error: codepage incompatible in session [SDE_RecordExtractStart]. The source database DB2_OLTP and server ORACLE_BI_DW_SERVER do not have compatible code pages. (One way compatibility is required). |
For Informatica servers running on UNIX, in the pmserver.cfg file, set ValidateDataCodePages to For Informatica servers running on Windows, navigate to Informatica Server setup, then Configuration, and remove the check from the Validate Data CodePages check box. |
|
When trying to start the Informatica Server, the following error message appears: sdcb50a125{qauser7a}/> pmserver exec(): 0509-036 Cannot load program pmserver because of the following errors: 0509-150 Dependent module libpmcef.a could not be loaded. 0509-022 Cannot load module libpmcef.a. 0509-026 System error: A file or directory in the path name does not exist. |
Set the environment parameters as follows: setenv PATH /export/home/informatica/pm:.:${PATH} setenv LD_LIBRARY_PATH /export/home/informatica/ pm:${LD_LIBRARY_PATH} |
Table H-5 provides information about problems and solutions related to issues with upgrading the Oracle Business Analytics Warehouse.
Table H-5 Upgrade Issues
| Symptom/Error Message | Probable Cause/Solution |
|---|---|
|
When upgrading from Oracle Business Analytics Warehouse version 7.5.3 to version 7.7, duplicate rows are inserted into a mini dimension table from the dimension table. |
Before upgrading, all leading and trailing spaces need to be removed from the data. Before running the workflow for the mini dimension that appears in the upgrade folder, modify the data to remove leading and trailing spaces by using the RTRIM and LTRIM functions. For example: In cases where you find leading and trailing spaces, modify the SQL override for the mini dimension mapping in the main folder as shown in the example below:
SELECT DISTINCT
CASE WHEN G1.VAL IS NULL THEN RTRIM(LTRIM(DS.AREA)) ELSE G1.VAL END AS AREA,
CASE WHEN G1.NAME IS NULL THEN RTRIM(LTRIM(DS.AREA)) ELSE G1.NAME END AS AREA_I,
CASE WHEN G2.VAL IS NULL THEN RTRIM(LTRIM(DS.SUB_AREA)) ELSE G2.VAL END AS SUB_AREA
CASE WHEN G2.NAME IS NULL THEN RTRIM (LTRIM(DS.SUB_AREA)) ELSE G2.NAME END AS SUB_AREA_I
CASE WHEN G3.VAL IS NULL THEN RTRIM(LTRIM(DS.SEV_CD)) ELSE G3.VAL END AS SEV_CD
CASE WHEN G3.NAME IS NULL THEN RTRIM (LTRIM(DS.SEV_CD)) ELSE G3.NAME END AS SEV_CD_I
CASE WHEN G4.VAL IS NULL THEN RTRIM(LTRIM(DS.PRIO_CD)) ELSE G4.VAL END AS PRIO_CD
CASE WHEN G4.NAME IS NULL THEN RTRIM (LTRIM(DS.PRIO_CD)) ELSE G4.NAME END AS PRIO_CD_I
FROM
W_SRVREQ_DS DS,
W_LOV_G G1,
W_LOV_G G2,
W_LOV_G G3,
W_LOV_G G4
WHERE
W_SRVREQ_DS
LEFT OUTER JOIN V_LOV_G G1 ON
DS.AREA = G1.NAMEVAL AND
G1.TYPE = 'SR_AREA'
LEFT OUTER JOIN W_LOV_G G2 ON
DS.SUB_AREA = G2.NAMEVAL AND
G2.TYPE = 'SR_AREA'
LEFT OUTER JOIN W_LOV_G G3 ON
DS.SEV_CD = G3.NAMEVAL AND
G3.TYPE = 'SR_SEVERITY'
LEFT OUTER JOIN W_LOV_G G4 ON
DS.PRIO_CD = G4.NAMEVAL AND
G4.TYPE = 'SR_PRIORITY'}
|
Table H-6 provides information about problems and solutions related to Oracle BI Interactive Dashboards.
Table H-6 Oracle BI Dashboard Issues
| Symptom/Error Message | Probable Cause/Solution |
|---|---|
|
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P File: ./project/webodbcaccess/odbcstatementimpl.cpp, Line: 186 State: S1000. Code: 10058. [NQODBC] [SQL_STATE: S1000] [nQSError: 10058] A general error has occurred. [nQSError: 17001] Oracle Error code: 4030, message: ORA-04030: out of process memory when trying to allocate 246284 bytes (hash-join subh,kllcqas:kllsltba) at OCI call OCIStmtFetch. [nQSError: 17012] Bulk fetch failed. (S1000) |
This is caused by a shortage of RAM on a dedicated (non shared server) environment. Depending on the Oracle version, the options for DBAs are:
|
Table H-7 provides information about problems and solutions related to ETL in Oracle BI Applications.
