BI Publisher Performance - JDK version 1_5_0_7

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, and 10.1.3.4.1.

There is a bug in Java SE Development Kit (JDK) 5.0 version 1_5_0_7 that impacts the performance of Oracle BI Publisher. For better performance, upgrade to JDK 5.0 update 11 (1_5_0_11). Download and install this update from the following location:

http://java.sun.com/javase/downloads/index_jdk5.jspAfter installing the JDK update, you must modify the OC4J start-up script or batch file to point to the new JDK location.

To modify the OC4J start-up script:

1.On Windows, open \oc4j_bi\bin\oc4j.cmd for editing. On Linux or UNIX machines, open $OracleBI\setup\oc4j.sh for editing.
2.Set the JAVA_HOME variable to point to the new JDK location. For example, JAVA_HOME=D:\Program Files\Java\jdk1.5.0_11.
If you installed Oracle BI Presentation Services using the Basic Install option on the machine where JDK has been updated, then you must modify the instanceconfig.xml file to point to the new JDK location:

To modify the instanceconfig.xml file:

1.Open the /web/config/instanceconfig.xml file for editing.
2.Set the JavaHome parameter to the point to the new JDK location. For example, D:\Program Files\Java\jdk1.5.0_11.

Startup & Shutdown & Status of OBIEE services on LINUX

Startup the BI services
Set the BI_HOME to the Oracle BI Home path e.g. /opt/oracle/product/OracleBI
$export BI_HOME=/opt/oracle/product/OracleBI
#Start the BI sever
$$BI_HOME/setup/run-sa.sh start
#Start the presentation service
$$BI_HOME/setup/run-saw.sh-start
#Start the scheduler
$$BI_HOME/setup/run-sch.sh start
#Start the cluster controller – only required when BI servers clustered
$$BI_HOME/setup/run-ccs.sh start
Shutdown the BI services
Set the BI_HOME to the Oracle BI Home path e.g. /opt/oracle/product/OracleBI
$export BI_HOME=/opt/oracle/product/OracleBI
#Stop the cluster controller – only required when BI servers clustered
$$BI_HOME/setup/run-ccs.sh stop
#Stop the BI sever
$$BI_HOME/setup/run-sa.sh stop
#Stop the presentation service
$$BI_HOME/setup/run-saw.sh stop
#Stop the scheduler
$$BI_HOME/setup/run-sch.sh stop



-----------------------------------
Oracle BI uses shell scripts located in the directory OracleBI_HOME/setup to set environment variables and run specific component shell commands.

The main administration scripts (scripts which call other scripts) are:

oc4j (start OC4J)
run-sa.sh (calls user.sh and starts the Oracle BI Server)
run-saw.sh (calls saw.sh and starts the Oracle BI Presentation Services.)
run-sch.sh (for BI Scheduler)
run-ccs.sh (for the Cluster Controller)
sa-cli.sh (Sets up the environment for running the Oracle BI Client)

Under Linux, no initialization process is necessary.

The order in which the services are stopped, then restarted, is important. Use the following sequence to start the OBI Component:
■OC4J
■Oracle Business Intelligence Server service.
■Oracle Business Intelligence Presentation Services service.
■Oracle Business Intelligence Scheduler Server service.

-----------------------------------------
Testing the Oracle BI Client
To test the Oracle BI Client :

Run Oracle BI Client by opening another session.
From the setup directory OracleBI_HOME/setup, run the shell command:
.sa-cli.shTo test the client/server connectivity, run the command:

nqcmd If the test is successful, press the Enter key several times to quit nqcmd.

----------------------------------------------
How to check that a service is running?

With Linux - ps (process statut)

[root@oel11g ~]# ps -ef|grep sawserver
obi 5102 1 0 15:16 pts/3 00:00:00 /bin/sh /usr/local/OracleBI/setup/sawserver.sh
obi 5109 5102 0 15:16 pts/3 00:00:08 /usr/local/OracleBI/web/bin/sawserver
root 5984 4661 0 15:39 pts/2 00:00:00 grep sawserver
[root@oel11g ~]# ps -ef|grep nqsserver
obi 5081 1 0 15:16 pts/3 00:00:12 /usr/local/OracleBI/server/Bin/nqsserver -quiet
root 6001 4661 0 15:40 pts/2 00:00:00 grep nqsserver

Reset oc4jadmin password in oas10g 10.1.3.0.1

. Stop the home instance: opmnctl stopproc process-type=home


2. Edit j2ee/home/config/system-jazn-data.xml (make a backup copy first).


3. Find the oc4j admin tab, and where the obfuscated password is, enclosed by the and tabs, delete it and enter your new password,

which must be prefixed with an exclamation mark (!) e.g. !Manager1 (rules are : > 5 chars, must have at least one number).

4. Delete the contents of the $ORACLE_HOME\j2ee\home\persistence\ascontrol\ascontrol\securestore directory (there will typically be 2 files in here).


5. Restart the home instance, and test to see if you can now login to host:port/em.


6. Open the system-jazn-data.xml file and check that the startup has re-encoded the password you entered.

OAS10g 10.1.3.1.0 in RHEL 5

First Execute the below command ...
./runInstaller -ignoreSysPreReqs -silent -responseFile ../../stage/Response/oracle.as.j2ee.top.allProductsNoSOA.rsp



Check for required packages:
rpm -q compat-db compat-gcc-34 compat-gcc-34-c++ compat-libgcc-296 compat-libstdc++-296 compat-libstdc++-33 gcc gcc-c++ glibc glibc-common glibc-devel glibc-headers libgcc make libXp

2. Set environment
ORACLE_BASE=/opt/oracle
ORACLE_HOME=$ORACLE_BASE/920
ORACLE_SID=ORCL
LD_LIBRARY_PATH=$ORACLE_HOME/lib
PATH=$PATH:$ORACLE_HOME/bin

export ORACLE_BASE ORACLE_HOME ORACLE_SID LD_LIBRARY_PATH

2. Workaround #1
su -
# cd /usr/lib
# ln -s libstdc++-3-libc6.2-2-2.10.0.so libstdc++-libc6.1-1.so.2

3. Download and Install:
http://oss.oracle.com/projects/compat-oracle/dist/files/RedHat/compat-libcwait-2.1-1.i386.rpm
http://oss.oracle.com/projects/compat-oracle/dist/files/RedHat/compat-oracle-rhel4-1.0-5.i386.rpm
rpm -ivh compat-libcwait-2.1-1.i386.rpm
rpm -ivh compat-oracle-rhel4-1.0-5.i386.rpm --nodeps

4. Workaround #2
su -
# cd /usr/bin
# ln -s gcc34 gcc32

Session Timeout for Oracle Single Sign-On

Idle Session Timeout is value (in minutes for Oracle Single Sign-On Server) after which user has to re-login, if they are inacte (No Activity / Idle) during that time. It is recommended to set Idle Session time out (Global Inactivity timeout) for security reasons. By default there is No Value set for Idle Session Timeout for Oracle Single Sign-On Server Server which means any application (like portal, discoverer, BI, forms & reports) using Oracle Single Sign-on for authentication will NOT logout user session because of Inactivity (This can be a Security Risk).

Default Session Time Out value for Oracle E-Business Suite 11i/R12 is 30 Minutes to know more about Idle Session timeout in Oracle Apps 11i, R12 check my previous post at Idle Session in Oracle Apps R12, 11i

Default Session Timeout for Apps 11i/R12 integrated with Single Sign-On Server
——————————————————————————–
For Oracle E-Business Suite (Apps 11i/R12) Customers integrated with Oracle Single Sign-On, default session time out for E-Business Suite/11i/R12 is 30 minutes where as no value for SSO which means If Apps User try to access apps after 30 minutes of Inactivity, user will get warning that session timeout and prompted to re-login. This will take user to new window and
user without actually typing user name password can re-login to Apps
.

The reason behind this security loop hole is that user logged out from Apps 11i/R12 after 30 minutes of inactivity but user cookie is still valid on SSO(as no idle session time out set on SSO Server) and user can re-login to apps without entering password as its authenticated by SSO server.

How to avoid this situation ?
Make Idle Session Timeout for Oracle SSO server in line with Apps 11i/R12

How to set Session Time out or Global Inactivity Timeout for Oracle Single Sign-On Server
—————————————————————————————–

1. Execute ssogito.sql from $ORACLE_HOME/sso/admin/plsql/sso (on SSO Tier) as orasso schema
2. There are few more steps on SSO server which you can find in link below


Oracle Documentation
———————————
Configuring the Global User Inactivity Timeout at Global Inactivity Timeout in Oracle SSO Server

You can subscribe to posts from this site in your mail box from right menu bar and contact me using Contact Us page on this site for feedback and things you like to see on this site.



Related Docs

357687.1 - How to Verify if mod_osso Global Inactivity Timeout (GITO) is Working
301894.1 - What is the difference between the SSO session duration timeout and the global inactivity timeout values
340708.1 - Global Inactivity TimeOut (GITO) does not work
561224.1 - Where In The Metadata Repository Database Is The GITO Cookie Name Stored?
445336.1 - SSO Global Inactivity Timeout Is Not Protecting the Customize Link
418385.1 - Interminent 500 Internal Server Error accessing Production with SSO GIT set on Test system

Installing oas10g 10.1.3.0.1 in RHEL 5

when you are trying to install oas10g 10.1.3.1.0 in RHEL 5 it will through error ,saying this is supporte only in rhel 3 and rhel 4.

To fix this problem .Follow the steps given below


export LD_ASSUME_KERNEL=2.4.1;

or LD_ASSUME_KERNEL in the bash progile

.run the bash profile then try to install again .

SOA10g DOWNLOAD LINK

https://edelivery.oracle.com/EPD/Download/get_form?egroup_aru_number=9132671