OBIEE Patch 18277370 conflicts with Patch 17611288 installed during OBIA 11.1.1.8.1 installation

OBIEE Patch 18277370 conflicts with Patch 17611288 installed during OBIA 11.1.1.8.1 installation

When attempting to apply OBIEE required patch 18277370, conflict is detected with Patch 17611288 which is for Fusion / OTBI applications.

Do not apply 18277370 in this case as it will rollback patch 17611288 and you may encounter an issue with EM not working post patching.


Instead obtain controlled Patch 20805649 from Product Support. EM should work without issue after applying Patch 20805649.

Related Posts:

FMW 11.1.1.7.0 - Applying Patch 20805649: REL9 BP16 CUMULATIVE JDEVADF_11.1.1.7.9ADF-FAREL9-BP_GENERIC_150401.1409.6807

Upgrading Oracle Business Intelligence (BI) Publisher Repository from 10g to 11g

FMW 11.1.1.7.0 - Applying Patch 20805649: REL9 BP16 CUMULATIVE JDEVADF_11.1.1.7.9ADF-FAREL9-BP_GENERIC_150401.1409.6807

FMW 11.1.1.7.0 - Applying Patch 20805649: REL9 BP16 CUMULATIVE JDEVADF_11.1.1.7.9ADF-FAREL9-BP_GENERIC_150401.1409.6807

- Review the patch README file to ensure all the pre-requisites for this patch are met including opatch version, environment variables are set, access to valid inventory, etc

- Set ORACLE_HOME to $MW_HOME/oracle_common 

- For Standalone JDeveloper install type, shutdown JDeveloper and make sure that the Embedded/Integrated WLS Server is also stopped.

- No action needed for WebCenter/SOA/Classic, etc.install type:

- For Standalone WLS install type, make sure that the WLS server is stopped.


Applying patch 20805649

- $ unzip -d PATCH_TOP p20805649_111170_Generic.zip

- $ cd PATCH_TOP/20805649

- Run OPatch to apply the patch.

  For OUI Home, run $ opatch apply

  For Standalone JDeveloper Home.

     Use the following command

     $ opatch apply -jdk [Path to jdk] -jre [Path to jre]
     

Post Patch instructions


a) For Standalone JDeveloper install type:

- Start JDeveloper and ensure Embedded/Integrated WLS Server is also started.

- If patch does not deploy to Integrated WLS Server then shutdown JDeveloper and integrated WLS, clean up tmp directory $JDEV_USER_DIR]\DefaultDomain\servers\DefaultServer\tmp\* .

- Once this has been done, restart JDeveloper and the integrated WLS.

b) For WebCenter/SOA/Classic/etc. install type:

- Restart all WLS Managed Servers and WLS Admin Server.

c) For Standalone WLS install type:

-   Start all WLS Managed Servers and WLS Admin Server


Rollback patch

-  $ cd PATCH_TOP/20805649

-  $ opatch rollback -id  20805649 -jdk [Path to jdk/jre]


a) For Standalone JDeveloper install type:

   Clean up tmp directory under $JDEV_USER_DIR]\DefaultDomain\servers\DefaultServer\tmp\* .

b) For WebCenter/SOA/Classic/etc. install type:

   Clean up tmp directory for Admin & Managed Servers under $MW_HOME]/user_projects/domains/[DOMAIN_NAME]/servers/[SERVER NAME]/tmp/*

c) For Standalone WLS install type:
   Restart all WLS Managed Servers and WLS Admin Server

- Start JDeveloper and make sure that the Embedded WLS Server is also started.

Related Posts:


FMW 11.1.1.8.0 - Applying Patch 20022599: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.9

WebCenter Content 11.1.1.8.9 Stuck Threads Issue - Applying Patch 20319643: STUCK THREADS DUE TO UNSAFE RIDC CODE - HASHMAP

FMW 11.1.1.7.0 MDS Patch 17693339 removed after applying ADF Patch for WebCenter Portal - Patch 21880254: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 20224749 21789440

FMW 11.1.1.7.0 - Applying Patch 18182516: UTF-8 CHARACTERS E3 E80 E81 NOT RECOGNIZED PROPERLY BY B2B

OBIEE Patch 18277370 conflicts with Patch 17611288 installed during OBIA 11.1.1.8.1 installation

Error while renumbering Work Repository ID in ODI - java.lang.RuntimeException: com.sunopsis.dwg.SQLMasterReposException: ORA-02292: integrity constraint (SID_ODIREPO.FK_VERSION_SNP_DAT) violated - child record found

Error while renumbering Work Repository ID in ODI - java.lang.RuntimeException: com.sunopsis.dwg.SQLMasterReposException: ORA-02292: integrity constraint (SID_ODIREPO.FK_VERSION_SNP_DAT) violated - child record found

at oracle.odi.ui.framework.adapter.DefaultAdapter.executeBackgroundTask(DefaultAdapter.java:611)
at oracle.odi.ui.framework.UIFramework.executeBackgroundTask(UIFramework.java:347)
at com.sunopsis.graphical.dialog.SnpsDialogRenumberId.dialogOkActionHook(SnpsDialogRenumberId.java:113)
at com.sunopsis.graphical.definition.DialogDefinitionNode$1.vetoableChange(DialogDefinitionNode.java:407)
at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:335)
at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:252)
at oracle.bali.ewt.dialog.JEWTDialog.fireVetoableChange(JEWTDialog.java:1530)

at oracle.bali.ewt.dialog.JEWTDialog.dismissDialog(JEWTDialog.java:1560)



If you are encountering errors as above while renumbering the Work Repository ID in Oracle Data Integrator (ODI), kindly refer to the steps in this post and check if the issue is resolved.

Related posts:

In OBIA 11.1.1.8.1, import error  ODI-10013: The import action has been cancelled because it could damage your repository. This is due to SNP_COL object that has object identifier 82624500 that is greater than that for the current SNP_COL id sequence. Importing this object would lead to primary key violations in the future

In OBIA 11.1.1.8.1, import error ODI-10013: The import action has been cancelled because it could damage your repository. This is due to SNP_COL object that has object identifier 83689500 that is greater than that for the current SNP_COL id sequence. Importing this object would lead to primary key violations in the future

In OBIA 11.1.1.8.1, import error  ODI-10013: The import action has been cancelled because it could damage your repository. This is due to SNP_COL object that has object identifier 82624500 that is greater than that for the current SNP_COL id sequence. Importing this object would lead to primary key violations in the future

- Connect to database instance hosting the Work Respository

Take backup: create database dump or backup to store actual Work Repository data

Take SID_BIA_ODIREPO schema backup of the target.

SQL> CREATE OR REPLACE DIRECTORY DPUMP as '/sid/oracle/exp_dump';

Directory created.

SQL> grant read, write on directory dpump to system;

Grant succeeded.


expdp system/******* DIRECTORY=DPUMP DUMPFILE=SID_BIA_ODIREPO.dmp SCHEMAS=SID_BIA_ODIREPO logfile=SID_BIA_ODIREPO_Export.log

Renumber the Objects IDs, and change the Work Repository internal ID

On target instance, connect as ODIREPO

SQL> conn SID_BIA_ODIREPO/******

Run select query to get the current value of REP_SHORT_ID


Run update query to update REP_SHORT_ID to new value

Run select query again to confirm REP_SHORT_ID has now got a new value

(Refer to Doc ID 424680.1 for sample SQLs, use these SQLs very carefully)

Re-attempt smart import

Smart import should now be successful without any import errors.


Also recommended to apply below patch on ODI 11.1.1.7.0 if not applied already


- Download and apply Patch 20005164: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 18204886 14743289 (Backup repositories before applying patch)

Related posts:

ODI 11.1.1.7.0 - Applying Patch 20005164: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 18204886 14743289

Error while renumbering Work Repository ID in ODI - java.lang.RuntimeException: com.sunopsis.dwg.SQLMasterReposException: ORA-02292: integrity constraint (SID_ODIREPO.FK_VERSION_SNP_DAT) violated - child record found

Oracle Business Intelligence Enterprise Edition Plus Client 11.1.1.7.0 Installation - Oracle BI Client Installer (64-bit) biee_client_install_x64.exe

Oracle Business Intelligence Enterprise Edition Plus Client 11.1.1.7.0 Installation - Oracle BI Client Installer (64-bit) biee_client_install_x64.exe

For BI Admin tool client upgrade:
- Go to the windows box and uninstall current version of BI Admin tool

- Follow steps as below to install the new version using the installer: 

1) Download biee_client_install_x64.exe either from BI Analytics page or from OTN.

BI Analytics

2) Run the installer by invoking biee_client_install_x64.exe

3) Select language from the drop down menu and click ok

4) InstallAnywhere Introduction -> Click Next

5) Choose Installer Folder

6) Choose Shortcut Folder. Select appropriate option & click Next

7) Pre-Installation Summary

8) Installation Complete

9) Set up ODBC Connection to Fusion Applications

To set up the ODBC connection from the Windows machine, you must locate the correct port on the Fusion Applications BI Server. Typically it is 10206, but if ports were changed as part of the FA install, perform the following steps:

- Log in to the BI Server's Enterprise Manager Console.
- Expand Business Intelligence within the Farm_BIDomain and select coreapplication. Select Overview and the sub tab Processes.
- Expand the BI Servers, and make a note of the port number.

You csn now create a new ODBC connection.

Select Oracle BI Server Driver on the Windows machine.

10) Enter the Server name for the host that contains the BI Domain. Click Next.

11) On the resulting screen, enter the BI Server port (either 10205 or derived above) and the user name/password with which you plan to connect. Click Next.

12) Click Finish

Also see other relevant post

OBI 11.1.1.8.1 -  nQSError : 62022 Javahost has not been configured correctly. Please check your configuration in NQSConfig.ini.

[OracleBIServerComponent] [ERROR:1] [] [] [ecid: ] [tid: 1464]  [nQSError: 93001] Can not load library, oracore11.dll, due to, The specified module could not be found error in OBIEE 11g NQSAdminTool.log file

Applying OBIA 11g: PATCH OBIEE 11.1.1.7.150120 for for Oracle Business Intelligence Enterprise Edition and Exalytics

Upgrading Oracle Business Intelligence (BI) Publisher Repository from 10g to 11g

Applying OBIA 11g: PATCH OBIEE 11.1.1.7.150120 for Oracle Business Intelligence Enterprise Edition and Exalytics

Applying OBIA 11g: PATCH OBIEE 11.1.1.7.150120 for for Oracle Business Intelligence Enterprise Edition and Exalytics

OBIEE 11.1.1.7.150120 comes as patch 20124371.

For the details of the list of patches you may apply in addition to OBIEE 11.1.1.7.150120, please refer to this post. 

Before applying the patch, please ensure you have a good cold backup to restore from if needed.

• On the OBIEE MT server, backup the following: 

<SID>/oraclebi/mwh/Oracle_BI1/bifoundation/server/<SID>/admin/instances/
<SID>/<BIHOST>/bifoundation/OracleBIServerComponent/coreapplication_obis1/repository 
<SID>/oraclebi/mwh/Oracle_BI1/bifoundation/jee/mapviewer.ear/web.war/WEB-INF/conf/mapViewerConfig.xml

• Stop the services.
• cd /<SID>/oraclebi/mwh/Oracle_BI1/bifoundation/web/catalogmanager/configuration/  and remove the following files if exist:

- org.eclipse.osgi

-org.eclipse.equinox.app

• Set the environment variables, go to staging area & apply the patches as below:

1) opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc -jre $ORACLE_HOME/jdk/jre

  Make sure the patch is applied by running:   opatch lsinventory| grep 16569379

2) opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc -jre $ORACLE_HOME/jdk/jre

   Make sure the patch is applied by running: opatch lsinventory| grep 16913445

3) opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc -jre $ORACLE_HOME/jdk/jre

Make sure the patch is applied by running: opatch lsinventory| grep 19823874

4) opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc -jre $ORACLE_HOME/jdk/jre

Make sure the patch is applied by running: opatch lsinventory| grep 19822893

5) opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc -jre $ORACLE_HOME/jdk/jre

Make sure the patch is applied by running: opatch lsinventory| grep 16997936

6) opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc -jre $ORACLE_HOME/jdk/jre

Make sure the patch is applied by running: opatch lsinventory| grep  20022695

7) opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc -jre $ORACLE_HOME/jdk/jre

Make sure the patch is applied by running: opatch lsinventory| grep  19825503

8) opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc -jre $ORACLE_HOME/jdk/jre

Make sure the patch is applied by running: opatch lsinventory| grep  19822826

9) opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc -jre $ORACLE_HOME/jdk/jre

Make sure the patch is applied by running: opatch lsinventory| grep  19822857

10) opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc -jre $ORACLE_HOME/jdk/jre

Make sure the patch is applied by running: opatch lsinventory| grep  17019008

11) opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc -jre $ORACLE_HOME/jdk/jre

Make sure the patch is applied by running: opatch lsinventory| grep  16984654

• Copy the BIPublisherDesktop32.exe and BIPublisherDesktop64.exe files

Source: /<SID>/oraclebi/mwh/Oracle_BI1/clients/bipublisher/repository/Tools

Target: /<SID>/admin/user_projects/domains/bi_<SID>/config/bipublisher/repository/Tools

• Copy msmdacc64.dll :

Source: /<SID>/oraclebi/mwh/Oracle_BI1/clients/bipublisher/repository/Admin/DataSource 

Target:/<SID>/admin/user_projects/domains/bi_<SID</config/bipublisher/repository/Admin/DataSource

• Remove the jsp_servlet subdirectory associated with Oracle BI Publisher (if it exists):

/<SID>/admin/user_projects/domains/bi_<SID>/servers/bi_server1/tmp/_WL_user/bipublisher_11.1.1 and remove any jsp_servlet subdirectory that you find.

• Look in each directory below 

<Middleware home>/<Domain home>/servers/bi_server1/tmp/_WL_user/bipublisher_11.1.1, and remove any jsp_servlet subdirectory that you find.

• If you backed up the mapViewerConfig.xml because it had been modified, then copy the backed-up file to its original location at

/<SID>/oraclebi/mwh/Oracle_BI1/bifoundation/jee/mapviewer.ear/web.war/WEB-INF/conf/

• Admin tool client upgrade:

- Go to the windows box and uninstall current version of BI Admin tool

        - Install the new version of BI Admin Tool using the installer

• Backup & configure config.xml and xdo.cfg files

Go to /<SID>/admin/instances/SID_host/config/OracleBIJavaHostComponent/coreapplication_obijh1 and backup the files config.xml and xdo.cfg.

In the config.xml file, configure the XMLP tag for large data as follows:

<XMLP>< InputStreamLimitInKB>0</InputStreamLimitInKB>

<ReadRequestBeforeProcessing>false</ReadRequestBeforeProcessing></XMLP>

In the xdo.cfg file, add the following parameter inside the properties tag:

<property name="xlsx-keep-values-in-same-column">true</property>

• Backup & configure opmn.xml

Go to /SID/admin/instances/SID_host/config/OPMN/opmn and backup opmn.xml

Add OBIEE_COMPILER_LOCK_OPTIMIZATION_LEVEL variable for BI Server as 

following.

•<ias-component id="coreapplication_obis1" inherit-environment="true"> 

<environment> 

<variable id="OBIEE_COMPILER_LOCK_OPTIMIZATION_LEVEL" value="2"/> 

</environment>

• Start the services
• Refresh the catalogs

Related Posts:

OBI 11.1.1.8.1 -  nQSError : 62022 Javahost has not been configured correctly. Please check your configuration in NQSConfig.ini.

[OracleBIServerComponent] [ERROR:1] [] [] [ecid: ] [tid: 1464]  [nQSError: 93001] Can not load library, oracore11.dll, due to, The specified module could not be found error in OBIEE 11g NQSAdminTool.log file

Upgrading Oracle Business Intelligence (BI) Publisher Repository from 10g to 11g

Oracle Business Intelligence Enterprise Edition Plus Client 11.1.1.7.0 Installation - Oracle BI Client Installer (64-bit) biee_client_install_x64.exe

OBIA 11g: PATCH OBIEE 11.1.1.7.150120 - Patchlist

OBIA 11g: PATCH OBIEE 11.1.1.7.150120 - Patchlist

OBIEE 11.1.1.7.150120 comes as patch 20124371. 

If you unzip it, it will contain eight other zip files containing the patches for each of the components (of which patch 19822893 is one) and a readme.htm file which contains the installation instructions.

Patch 16913445 - Patch 11.1.1.7.150120 (1 of 8) Oracle Business Intelligence Installer (BIINST)
Patch 19822893 - Patch 11.1.1.7.150120 (2 of 8) Oracle Business Intelligence Publisher (BIP)
Patch 19825503 - Patch 11.1.1.7.150120 (3 of 8) Enterprise Performance Management Components Installed from BI Installer 11.1.1.7.0 (BIFNDNEPM)
Patch 19822857 - Patch 11.1.1.7.150120 (4 of 8) Oracle Business Intelligence Server (BIS)
Patch 19822826 - Patch 11.1.1.7.150120 (5 of 8) Oracle Business Intelligence Presentation Services (BIPS)
Patch 19823874 - Patch 11.1.1.7.150120 (6 of 8) Oracle Real-Time Decisions (RTD)
Patch 16997936 - Patch 11.1.1.7.150120 (7 of 8) Oracle Business Intelligence ADF Components (BIADFCOMPS)
Patch 20022695 - Patch 11.1.1.7.150120 (8 of 8) Oracle Business Intelligence Platform Client Installers and MapViewer


Also you must download and install:

Patch 16569379 - Dynamic Monitoring Service patch

If you use Internet Explorer 11, download and install:

Patch 18277370 - JDeveloper patch

You may additionally apply below bug fix patches.

Patch 17019008: CRASH IN NQSSERVER (ABORTED)


Patch 16984654: STATUS MAX TIME DOES NOT CANCEL DATABASE QUERY WHEN CONNECTING TO ESSBASE

Detailed steps for applying the OBIA 11g: PATCH OBIEE 11.1.1.7.150120 patch are covered in this post below.

Applying OBIA 11g: PATCH OBIEE 11.1.1.7.150120 for for Oracle Business Intelligence Enterprise Edition and Exalytics



Related Posts:

OBIEE Patch 18277370 conflicts with Patch 17611288 installed during OBIA 11.1.1.8.1 installation

Oracle Business Intelligence Enterprise Edition Plus Client 11.1.1.7.0 Installation - Oracle BI Client Installer (64-bit) biee_client_install_x64.exe

[OracleBIServerComponent] [ERROR:1] [] [] [ecid: ] [tid: 1464]  [nQSError: 93001] Can not load library, oracore11.dll, due to, The specified module could not be found error in OBIEE 11g NQSAdminTool.log file

OBI 11.1.1.8.1 -  nQSError : 62022 Javahost has not been configured correctly. Please check your configuration in NQSConfig.ini

Upgrading Oracle Business Intelligence (BI) Publisher Repository from 10g to 11g