Tuesday, July 16, 2013

OBIEE 11G Installation error during configuration steps with message "Distributing Repository" failed

Problem:

When attempting to install OBIEE11g (11.1.1.7) on Windows 64bit, the installation failed at the 
configuration steps with error message "Distributing Repository" failed.


Answer:

To avoid this issue, make sure that the locale en_US.UTF-8 exists on the installation computer before you install Oracle Business Intelligence.


Installing BI Applications 7.9.6.4 on BI EE 11.1.1.7.0

The Oracle Business Intelligence Application 7.9.6.4 installer fails on Oracle BI EE 11.1.1.7.0 with the error “NQSConfig.INI not found. Please make sure your environment is set up properly”. Also  7.9.6.4 JAZN file is incompatible with BI EE 11.1.1.7.0. This causes authentication failures when a user tries to log in to the Analytics page.

Issue 1: The Oracle Business Intelligence Application 7.9.6.4 installer fails on Oracle BI EE 11.1.1.7.0 with the error “NQSConfig.INI not found. Please make sure your environment is set up properly”.

Issue 2: The Oracle Business Intelligence Application 7.9.6.4 JAZN file is incompatible with BI EE 11.1.1.7.0. This causes authentication failures when a user tries to log in to the Analytics page.

Error Message
NQSConfig.INI not found. Please make sure your environment is set up properly


Please down the attached file Technote1561846.1_InstallSecurity.zip and apply the solution.ID 1561846.1
If required apply patch p16321623_7964_Generic





Patch Download from here

Patch Doc

Wednesday, July 3, 2013

Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P


Error: 
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 17001] Oracle Error code: 932, message: ORA-00932: inconsistent datatypes: expected - got CLOB at OCI call OCIStmtExecute. [nQSError: 17010] SQL statement preparation failed. (HY000)
SQL Issued: SELECT 0 s_0, "SPM - Strategic Plan"."Res Statement"."Responsibility Statment Ar" s_1, "SPM - Strategic Plan"."Res Statement"."Responsibility Statment" s_2 FROM "SPM - Strategic Plan" 
Solutions:
Create a view in database by selecting all the columns  and use this DBMS_LOB.SUBSTR(<Clob column>) for clob column.
example: SELECT  rs.sp_id,  

        CAST(DBMS_LOB.substr(rs.RESPONSIBILITY_STATMENT,4000,1)AS VARCHAR2(4000)) RESPONSIBILITY_STATMENT,
        CAST(DBMS_LOB.substr(rs.RESPONSIBILITY_STATMENT_AR,2150,1) AS VARCHAR2(4000)) RESPONSIBILITY_STATMENT_AR,
       CAST(DBMS_LOB.substr(rs.RESPONSIBILITY_STATMENT_AR,4000,2151) AS VARCHAR2(4000))
FROM 
       xxspm_respon_statment rs

If it is English characeter it will accept up to 4000 char , If it is Arabic character it will allow you 2150 characters you can split the data in to two columns like in the example.


1) In the RPD physical layer change the data type to Longvarchar
2) In the report level add two arabic columns using concatinate symbal ( || ) in the expersion builder report will work

good luck.