Database - RAC/Scalability (MOSC)

MOSC Banner

Session context lost when RAC switched to second node

edited Mar 25, 2018 5:03AM in Database - RAC/Scalability (MOSC) 1 commentAnswered

Hello,

We have problem in our production database and I need your help gays ...

Our problem is: the session context has been lost and returns NULL while the Oracle crashed and switched to second node.

Setting : DBMS_SESSION.set_context('CONTEXT_NAME', p_name, p_value);

Getting : p_value = DBMS_SESSION.set_context('CONTEXT_NAME', p_name);

in documentation of Oracle :

A global application context enables application context values to be accessible across database sessions, including Oracle RAC instances.Oracle Database stores the global application context information in the System (sometimes called "Shared") Global Area (SGA) so that it can be used for applications that use a sessionless model, such as middle-tier applications in a three-tiered architecture. These applications cannot use a session-based application context because users authenticate to the application, and then it typically connects to the database as a single identity. Oracle Database initializes the global application context once, rather than for each user session. This improves performance, because connections

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center