Active session count of an user

Hi,
Could you help me understand the concept of active user session count and the factors influencing the active sesssion count of an user
1) Does running multiple queries in a number of query windows in SQL developer lead to increase active session count?
2) Does a high degree of parallel option ( e.g. Parallel (Degree 8)) provided in a query lead to a higher session count?
3) Does the size of data processed in a query influence session count?
4) Does the complexity of a query influence session count?
5) Can a session remain active even after completion of a query and thereby increase the active sessioncount?
Regards
-Learnsequel

910874 wrote:
Could you help me understand the concept of active user session count and the factors influencing the active sesssion count of an userThat depends on the client. Does the client use some form of multi-threading? If so, the client needs a separate and active Oracle session servicing each of its running threads.
The user may only initiate a single connection to the database - but the application remembers the authentication and connection details and can transparently establish multiple additional sessions. (a common behaviour by TOAD and SQL-Developer)
1) Does running multiple queries in a number of query windows in SQL developer lead to increase active session count?Yes - as an Oracle session is serialised. It can only execute a single client request at a time. Thus if the client has 3 windows/tabs with each running a SQL query - then 3 Oracle sessions are required to service that client.
2) Does a high degree of parallel option ( e.g. Parallel (Degree 8)) provided in a query lead to a higher session count?No. PX slave processes are database processes. They only "assist" a session at specific times. Then they can "assist" other sessions with other parallel query processing. The database has a configurable PQ processing pool of processes. You can specify the minimum number of processes to create in the pool at startup. You can specify the ceiling of the pool.
So no number of sessions can grow the number of PQ processes beyond the maximum size of the pool. And the pool is there to service all sessions. Not just a single session.
3) Does the size of data processed in a query influence session count?No.
4) Does the complexity of a query influence session count?No.
5) Can a session remain active even after completion of a query and thereby increase the active sessioncount?This is default behaviour. If that session terminates, the client looses its database connection.
In the case of a multi-threaded client, it can decide to close one or more of the transparent "background" sessions it created to the database, when no longer needing such a session. However, it will keep its initial (first) session open as its primary connection to the database.

Similar Messages

How to find active sessions count on a server in weblogic server console

Hi All,
I would like to know how to find active sessions count on a server in weblogic console. I am using weblogic 11g.
Regards,
Sunil.

On the deployment, monitoring tab, you can select web applications. Here the number of current sessions are listed per web application deployed on the domain.
The deployment itself (deployments, application, monitoring, sessions) shows a list of sessions and where it is located. Unfortunately, there is no aggregation (but that is something you can so yourself as well).
When you are using a load balancer in front, the count of sessions on per web application on the domain gives you some clue how many sessions there are present on each server.
That is to say, when load balancer is using round-robin (and does that correct), you can take the total number of sessions divide it by the number of servers.

Active session count of ASA in HA

Hi,
We have configured our ASA5540 in active-standby failover.
We are observing that current active session count is twice of session count before configuring HA. Earlier average active session was 50000 and now after HA it is around 100000. Kindly let us know the reason for same.
Failover configuration of both firewall are as follows
failover
failover lan unit primary
failover lan interface FOLan GigabitEthernet1/0
failover polltime unit 15 holdtime 45
failover replication http
failover link StateLink GigabitEthernet1/1
failover interface ip FOLan 10.3.3.1 255.255.255.0 standby 10.3.3.2
failover interface ip StateLink 10.4.4.1 255.255.255.0 standby 10.4.4.2
failover
failover lan unit secondary
failover lan interface FOLan GigabitEthernet1/0
failover polltime unit 15 holdtime 45
failover replication http
failover link StateLink GigabitEthernet1/1
failover interface ip FOLan 10.3.3.1 255.255.255.0 standby 10.3.3.2
failover interface ip StateLink 10.4.4.1 255.255.255.0 standby 10.4.4.2
Regards,
Mukesh Tiwari

Hi,
I guess you have check this with "show conn count" or "show conn" commands on the ASA?
Ofcourse the first thing that comes to mind is that its somehow adding up the connection count of both ASA units. Though it shouldnt do this to my knowledge. You should just see almost equal amount of connections on both units. Both Primary and Secondary.
Have you tried to check if there is any host on your local network that would be taking alot of connections? Maybe somethings happened at the same time (even though it might not be likely)
Have you noticed any performance issues/problem after this upgrade to a A/S ASA pair?
- Jouni

How to avoid one active session for the same user account concurrently

Hi all ,
i am using model 1 architecture in my application.
in my application ,if one user login through 2 browser at a time ,he can do it.
But now ,i want to close first browser or redirect him to a exception page.
plz guide me how can i do it.
plz include case1.
what happen if he close page ,not logoff
case2
what happen if power cut happen on client side.

+You can use a column in the table to check the current user logged in status. Once the user gets logged in the application change the flag at the backend. In this way you can know whether the user is already logged in the apllication or not, and based on this you can show a proper message to the user.+
+If the user closes the browser window without logging off the application, then in this case you can use the session Listoners.+
Well not the right approach Listeners would it for you.For browser closure problem.If user does that automatically container destroys the session object as per configured session-timeout.
*@OP*
Problem 1:
Try to a write an implementation of sessionListener / sessionAttributeListener (for having a check on user loggins and apply a global filter which checks available users who have already logged in)
Hope the below thread might give you some idea of how to go about.
http://forum.java.sun.com/thread.jspa?threadID=5226527&messageID=9922478
Problem 2:
consequently configure session-timeout parameter in minutes under web.xml for session browser close and inactivity state problems.
REGARDS,
RaHuL

What is a "logged in user" on the "Active Sessions" report in CF8 Server Monitor?

I was looking at the Active Sessions Report (The Chart View) and saw I have more "logged in users" than "active sessions".
I had expected them to be nearly the same.    It's on our Intranet where I log users in (using cflogin and cfloginuser) at the begining of their session and users should be logged when the session ends.
I couldn't find a detailed explaination of what a "logged in user" means.   There is a chance that the same user is logged into a nested application as well as the Intranet, but I don't think that is what I'm seeing.
I also don't see a way to get a list of what CF is counting as a logged in user. I can only see a way to get the total count.
Any help is appreciated.
Thanks,
Jeff

Thank you Michael for the reply, but I don't think that is the issue.
When a user opens their browser on the intranet, a session begins and they are logged in (using the cflogin and cfloginuser).    If they close their browser, the session should hang around for 20 min. (per the server setting).   I am assuming this is still considered an "Active Session" since I can see this behavior in the report.
At first, the Active Sessions and Logged In Users are exactly the same.   When the sessions start to time out, the active sessions are reduced, but the Logged In Users remain the same.    Then, after a while, they start to move together. So I have more Logged In Users than Active Sessions.
I left the Server Monitor open last night and for most of the night, I had 0 sessions, but 57 "logged in users".   This morning, as people opened their browsers, the Active Sessions and Logged In Users moved together.   The gap of 57 looks consistent.
It looks like people are remaining logged in after their session ended.
I am really looking for a detailed explaination of "active session" and/or "logged in user" as used in the server monitor. It would be really nice to find a way to list the details about each item counted in the "logged in user" and not just the total count.
Thanks Again for your reply.
jsm

Active Sessions problem for JMX client

Hello,
I've written my own JMX client to pull data from MBean Server using instruction from Connecting to an MBeanServer - SAP NetWeaver Composition Environment Library - SAP Library. Client is connecting to server every 5 minutes. After some time I noticed that Active Session Count is rising. Also when checking Login Sessions in VA I see multiple sessions for username provided in JMX client configuration.
My understanding of this situation is that I initiate new session using RMI-P4 connector, but never terminate it which leaves opened sessions on the server.
My question is, is ther a way to close connection to MBeanServer?
Best regards,
wojtek

Good morning Jeremy,
The URL works fine. The only thing in the NetWeaver log is the NullPointerException.
Hmm... Just brainstorming here.
The id I am using is the one having the problems with NetWeaver not filling in all the MII session variables. I suppose there could be a null pointer because of one of those variables being null... I have an open OSS message about that issue. Although that would affect the URL too.
Would it be a good idea to have the Basis guy check the logging level in NetWeaver? seems I only see error and fatal.
Thanks for the suggestion.
--Amy Smith
--Haworth

Count all active Session

Hey all,
I want to know how many users are on my site. So I tryed so count all activ session:
int countActiveSessions = FacesContext.getCurrentInstance().
getExternalContext().getSessionMap().size();But it returns allways 0. Is the method false or how can I count all sessions?
Thanks for help

You are OT. Your question concertn much more servlet than JavaServer Faces.
Anyway sessionMap is not the map of all sessions. It is the map of your own session. With a session map you can retrieve the session attributes.
Look there if you want count the active sessions:
http://www.java.happycodings.com/Java_Servlets/code10.html

How can I find out if a user has an active session

How can I find out if a user has an active session or sessionObject in the application Server.
When a user logs on to my web-application, I want him to be able to see a
list of all the other users that are also loged on. To do this I need to get a
list of all the session objects avaliable in the sever at that perticular moment?
In J2EE 2.1 I found the class "javax.servlet.http.HttpSessionContext" with the method "getIds()"
that returned all the session Id's. By using the method getSession(java.lang.String sessionId)
from the same class, you could then retrieve the sessionObject.
But these methods are depricated (and want to be able to use the
latest version of J2EE).
Is there any other way to do this?
I'm using JBoss application server.

Check out HttpSessionListener -> http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/servlet/http/HttpSessionListener.html
Essentially what you have to do is implement this interface. You also have to register the listener in your web.xml, like this:
<listener>
    <listener-class>
        package.name.YourListener
    </listener-class>
</listener>sessionCreated() will get called each time the app server creates a session and sessionDestroyed() will get called each time the app server invalidates a session. You could have a Map that contains all the active sessions, and a method for printing a list of all of the active sessions.

Counting how many active sessions in a webapp

Hi folks,
I was wondering if it is possible to count how many active sessions that there currently are in a webapp? I've looked at the ServletContext and ServletConfig classes, but I can't find anything. Any ideas?
Cheers,
Raj.

HttpSessionListener was introduced in servlet spec 2.3 which is supported in Tomcat 4.0 but not 3.3.
If upgrading to 4.0 is not an option, there is no elegant way to get what you need. There is no API call that returns all the active sessions so you must do it yourself. One way is to create a class that implements HttpSessionBindingListener to track your sessions. Instantiate it on start-up and add its reference as a session attribute when the session is first created. You can then update your custom session info in the valueBound and valueUnbound methods.

Count of active sessions in OC4J

is there any way i can get the count of active sessions in my servlet in OC4J container?
any and all help is appreciated.
thanks
nik

Hi,
I am not sure whether it works. But try starting server with -console option. This opens up a graphic console and try if you can find the info you wanted there.
srinath

Sp_who2 -need only active sessions from users which are not the background sessions

Hello,
sp_who2 -need only active sessions from users which are not the background sessions
Please assist.
Best regards,
Vishal

Its better to use DMV's to view only active sessions from users (spid>50) as mentioned by Shanky.
You can do that using sp_who2 but it requires a bit of programming to list only user sessions.
SELECT
S.SESSION_ID,
S.STATUS,
S.HOST_NAME,
C.CLIENT_NET_ADDRESS,
CASE WHEN S.LOGIN_NAME = S.ORIGINAL_LOGIN_NAME THEN S.LOGIN_NAME ELSE S.LOGIN_NAME END LOGIN_NAME,
S.PROGRAM_NAME,
C.CONNECT_TIME,
S.LOGIN_TIME,
CASE S.TRANSACTION_ISOLATION_LEVEL
WHEN 0 THEN 'UNSPECIFIED'
WHEN 1 THEN 'READUNCOMITTED'
WHEN 2 THEN 'READCOMMITTED'
WHEN 3 THEN 'REPEATABLE'
WHEN 4 THEN 'SERIALIZABLE'
WHEN 5 THEN 'SNAPSHOT'
ELSE CAST(S.TRANSACTION_ISOLATION_LEVEL AS VARCHAR(32))
END AS TRANSACTION_ISOLATION_LEVEL_NAME,
S.LAST_SUCCESSFUL_LOGON,
S.LAST_UNSUCCESSFUL_LOGON,
S.UNSUCCESSFUL_LOGONS,
S.CPU_TIME AS CPU_TIME_MS,
S.MEMORY_USAGE AS MEMORY_USAGE_PAGES,
S.ROW_COUNT,
S.PREV_ERROR,
S.LAST_REQUEST_START_TIME,
S.LAST_REQUEST_END_TIME,
C.NET_TRANSPORT,
C.PROTOCOL_TYPE,
S.LANGUAGE,
S.DATE_FORMAT,
ST.TEXT AS QUERY_TEXT
FROM
SYS.DM_EXEC_SESSIONS S
FULL OUTER JOIN SYS.DM_EXEC_CONNECTIONS C ON C.SESSION_ID = S.SESSION_ID
CROSS APPLY SYS.DM_EXEC_SQL_TEXT(C.MOST_RECENT_SQL_HANDLE) ST
WHERE
S.SESSION_ID IS NULL
OR S.SESSION_ID > 50
ORDER BY
S.SESSION_ID
-Prashanth

Active session Spike on Oracle RAC 11G R2 on HP UX

Dear Experts,
We need urgent help please, as we are facing very low performance in production database.
We are having oracle 11G RAC on HP Unix environment. Following is the ADDM report. Kindly check and please help me to figure it out the issue and resolve it at earliest.
---------Instance 1---------------
          ADDM Report for Task 'TASK_36650'
Analysis Period
AWR snapshot range from 11634 to 11636.
Time period starts at 21-JUL-13 07.00.03 PM
Time period ends at 21-JUL-13 09.00.49 PM
Analysis Target
Database 'MCMSDRAC' with DB ID 2894940361.
Database version 11.2.0.1.0.
ADDM performed an analysis of instance mcmsdrac1, numbered 1 and hosted at
mcmsdbl1.
Activity During the Analysis Period
Total database time was 38466 seconds.
The average number of active sessions was 5.31.
Summary of Findings
   Description           Active Sessions      Recommendations
                         Percent of Activity
1 CPU Usage             1.44 | 27.08         1
2 Interconnect Latency .07 | 1.33           1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Findings and Recommendations
Finding 1: CPU Usage
Impact is 1.44 active sessions, 27.08% of total activity.
Host CPU was a bottleneck and the instance was consuming 99% of the host CPU.
All wait times will be inflated by wait for CPU.
Host CPU consumption was 99%.
   Recommendation 1: Host Configuration
   Estimated benefit is 1.44 active sessions, 27.08% of total activity.
   Action
      Consider adding more CPUs to the host or adding instances serving the
      database on other hosts.
   Action
      Session CPU consumption was throttled by the Oracle Resource Manager.
      Consider revising the resource plan that was active during the analysis
      period.
Finding 2: Interconnect Latency
Impact is .07 active sessions, 1.33% of total activity.
Higher than expected latency of the cluster interconnect was responsible for
significant database time on this instance.
The instance was consuming 110 kilo bits per second of interconnect bandwidth.
20% of this interconnect bandwidth was used for global cache messaging, 21%
for parallel query messaging and 7% for database lock management.
The average latency for 8K interconnect messages was 42153 microseconds.
The instance is using the private interconnect device "lan2" with IP address
172.16.200.71 and source "Oracle Cluster Repository".
The device "lan2" was used for 100% of interconnect traffic and experienced 0
send or receive errors during the analysis period.
   Recommendation 1: Host Configuration
   Estimated benefit is .07 active sessions, 1.33% of total activity.
   Action
      Investigate cause of high network interconnect latency between database
      instances. Oracle's recommended solution is to use a high speed
      dedicated network.
   Action
      Check the configuration of the cluster interconnect. Check OS setup like
      adapter setting, firmware and driver release. Check that the OS's socket
      receive buffers are large enough to store an entire multiblock read. The
      value of parameter "db_file_multiblock_read_count" may be decreased as a
      workaround.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Additional Information
Miscellaneous Information
Wait class "Application" was not consuming significant database time.
Wait class "Cluster" was not consuming significant database time.
Wait class "Commit" was not consuming significant database time.
Wait class "Concurrency" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
Wait class "Network" was not consuming significant database time.
Wait class "User I/O" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
Hard parsing of SQL statements was not consuming significant database time.
The database's maintenance windows were active during 100% of the analysis
period.
----------------Instance 2 --------------------
          ADDM Report for Task 'TASK_36652'
Analysis Period
AWR snapshot range from 11634 to 11636.
Time period starts at 21-JUL-13 07.00.03 PM
Time period ends at 21-JUL-13 09.00.49 PM
Analysis Target
Database 'MCMSDRAC' with DB ID 2894940361.
Database version 11.2.0.1.0.
ADDM performed an analysis of instance mcmsdrac2, numbered 2 and hosted at
mcmsdbl2.
Activity During the Analysis Period
Total database time was 2898 seconds.
The average number of active sessions was .4.
Summary of Findings
    Description                 Active Sessions      Recommendations
                                Percent of Activity
1   Top SQL Statements          .11 | 27.65          5
2   Interconnect Latency        .1 | 24.15           1
3   Shared Pool Latches         .09 | 22.42          1
4   PL/SQL Execution            .06 | 14.39          2
5   Unusual "Other" Wait Event .03 | 8.73           4
6   Unusual "Other" Wait Event .03 | 6.42           3
7   Unusual "Other" Wait Event .03 | 6.29           6
8   Hard Parse                  .02 | 5.5            0
9   Soft Parse                  .02 | 3.86           2
10 Unusual "Other" Wait Event .01 | 3.75           4
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Findings and Recommendations
Finding 1: Top SQL Statements
Impact is .11 active sessions, 27.65% of total activity.
SQL statements consuming significant database time were found. These
statements offer a good opportunity for performance improvement.
   Recommendation 1: SQL Tuning
   Estimated benefit is .05 active sessions, 12.88% of total activity.
   Action
      Investigate the PL/SQL statement with SQL_ID "d1s02myktu19h" for
      possible performance improvements. You can supplement the information
      given here with an ASH report for this SQL_ID.
      Related Object
         SQL statement with SQL_ID d1s02myktu19h.
         begin dbms_utility.validate(:1,:2,:3,:4); end;
   Rationale
      The SQL Tuning Advisor cannot operate on PL/SQL statements.
   Rationale
      Database time for this SQL was divided as follows: 13% for SQL
      execution, 2% for parsing, 85% for PL/SQL execution and 0% for Java
      execution.
   Rationale
      SQL statement with SQL_ID "d1s02myktu19h" was executed 48 times and had
      an average elapsed time of 7 seconds.
   Rationale
      Waiting for event "library cache pin" in wait class "Concurrency"
      accounted for 70% of the database time spent in processing the SQL
      statement with SQL_ID "d1s02myktu19h".
   Rationale
      Top level calls to execute the PL/SQL statement with SQL_ID
      "63wt8yna5umd6" are responsible for 100% of the database time spent on
      the PL/SQL statement with SQL_ID "d1s02myktu19h".
      Related Object
         SQL statement with SQL_ID 63wt8yna5umd6.
         begin DBMS_UTILITY.COMPILE_SCHEMA( 'TPAUSER', FALSE ); end;
   Recommendation 2: SQL Tuning
   Estimated benefit is .02 active sessions, 4.55% of total activity.
   Action
      Run SQL Tuning Advisor on the SELECT statement with SQL_ID
      "fk3bh3t41101x".
      Related Object
         SQL statement with SQL_ID fk3bh3t41101x.
         SELECT MEM.MEMBER_CODE ,MEM.E_NAME,Pol.Policy_no
         ,pol.date_from,pol.date_to,POL.E_NAME,MEM.SEX,(SYSDATE-MEM.BIRTH_DATE
         ) AGE,POL.SCHEME_NO FROM TPAUSER.MEMBERS MEM,TPAUSER.POLICY POL WHERE
         POL.QUOTATION_NO=MEM.QUOTATION_NO AND POL.BRANCH_CODE=MEM.BRANCH_CODE
         and endt_no=(select max(endt_no) from tpauser.members mm where
         mm.member_code=mem.member_code AND mm.QUOTATION_NO=MEM.QUOTATION_NO)
         and member_code like '%' || nvl(:1,null) ||'%' ORDER BY MEMBER_CODE
   Rationale
      The SQL spent 92% of its database time on CPU, I/O and Cluster waits.
      This part of database time may be improved by the SQL Tuning Advisor.
   Rationale
      Database time for this SQL was divided as follows: 100% for SQL
      execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
      execution.
   Rationale
      SQL statement with SQL_ID "fk3bh3t41101x" was executed 14 times and had
      an average elapsed time of 4.9 seconds.
   Rationale
      At least one execution of the statement ran in parallel.
   Recommendation 3: SQL Tuning
   Estimated benefit is .02 active sessions, 3.79% of total activity.
   Action
      Run SQL Tuning Advisor on the SELECT statement with SQL_ID
      "7mhjbjg9ntqf5".
      Related Object
         SQL statement with SQL_ID 7mhjbjg9ntqf5.
         SELECT SUM(CNT) FROM (SELECT COUNT(PROC_CODE) CNT FROM
         TPAUSER.TORBINY_PROCEDURE WHERE BRANCH_CODE = :B6 AND QUOTATION_NO =
         :B5 AND CLASS_NO = :B4 AND OPTION_NO = :B3 AND PR_EFFECTIVE_DATE<=
         :B2 AND PROC_CODE = :B1 UNION SELECT COUNT(MED_CODE) CNT FROM
         TPAUSER.TORBINY_MEDICINE WHERE BRANCH_CODE = :B6 AND QUOTATION_NO =
         :B5 AND CLASS_NO = :B4 AND OPTION_NO = :B3 AND M_EFFECTIVE_DATE<= :B2
         AND MED_CODE = :B1 UNION SELECT COUNT(LAB_CODE) CNT FROM
         TPAUSER.TORBINY_LAB WHERE BRANCH_CODE = :B6 AND QUOTATION_NO = :B5
         AND CLASS_NO = :B4 AND OPTION_NO = :B3 AND L_EFFECTIVE_DATE<= :B2 AND
         LAB_CODE = :B1 )
   Rationale
      The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
      This part of database time may be improved by the SQL Tuning Advisor.
   Rationale
      Database time for this SQL was divided as follows: 0% for SQL execution,
      0% for parsing, 100% for PL/SQL execution and 0% for Java execution.
   Rationale
      SQL statement with SQL_ID "7mhjbjg9ntqf5" was executed 31 times and had
      an average elapsed time of 3.4 seconds.
   Rationale
      Top level calls to execute the SELECT statement with SQL_ID
      "a11nzdnd91gsg" are responsible for 100% of the database time spent on
      the SELECT statement with SQL_ID "7mhjbjg9ntqf5".
      Related Object
         SQL statement with SQL_ID a11nzdnd91gsg.
         SELECT POLICY_NO,SCHEME_NO FROM TPAUSER.POLICY WHERE QUOTATION_NO
         =:B1
   Recommendation 4: SQL Tuning
   Estimated benefit is .01 active sessions, 3.03% of total activity.
   Action
      Investigate the SELECT statement with SQL_ID "4uqs4jt7aca5s" for
      possible performance improvements. You can supplement the information
      given here with an ASH report for this SQL_ID.
      Related Object
         SQL statement with SQL_ID 4uqs4jt7aca5s.
         SELECT DISTINCT USER_ID FROM GV$SESSION, USERS WHERE UPPER (USERNAME)
         = UPPER (USER_ID) AND USERS.APPROVAL_CLAIM='VC' AND USER_ID=:B1
   Rationale
      The SQL spent only 0% of its database time on CPU, I/O and Cluster
      waits. Therefore, the SQL Tuning Advisor is not applicable in this case.
      Look at performance data for the SQL to find potential improvements.
   Rationale
      Database time for this SQL was divided as follows: 100% for SQL
      execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
      execution.
   Rationale
      SQL statement with SQL_ID "4uqs4jt7aca5s" was executed 261 times and had
      an average elapsed time of 0.35 seconds.
   Rationale
      At least one execution of the statement ran in parallel.
   Rationale
      Top level calls to execute the PL/SQL statement with SQL_ID
      "91vt043t78460" are responsible for 100% of the database time spent on
      the SELECT statement with SQL_ID "4uqs4jt7aca5s".
      Related Object
         SQL statement with SQL_ID 91vt043t78460.
         begin TPAUSER.RECEIVE_NEW_FAX_APRROVAL(:V00001,:V00002,:V00003,:V0000
         4); end;
   Recommendation 5: SQL Tuning
   Estimated benefit is .01 active sessions, 3.03% of total activity.
   Action
      Run SQL Tuning Advisor on the SELECT statement with SQL_ID
      "7kt28fkc0yn5f".
      Related Object
         SQL statement with SQL_ID 7kt28fkc0yn5f.
         SELECT COUNT(*) FROM TPAUSER.APPROVAL_MASTER WHERE APPROVAL_STATUS IS
         NULL AND (UPPER(CODED) = UPPER(:B1 ) OR UPPER(PROCESSED_BY) =
         UPPER(:B1 ))
   Rationale
      The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
      This part of database time may be improved by the SQL Tuning Advisor.
   Rationale
      Database time for this SQL was divided as follows: 100% for SQL
      execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
      execution.
   Rationale
      SQL statement with SQL_ID "7kt28fkc0yn5f" was executed 1034 times and
      had an average elapsed time of 0.063 seconds.
   Rationale
      Top level calls to execute the PL/SQL statement with SQL_ID
      "91vt043t78460" are responsible for 100% of the database time spent on
      the SELECT statement with SQL_ID "7kt28fkc0yn5f".
      Related Object
         SQL statement with SQL_ID 91vt043t78460.
         begin TPAUSER.RECEIVE_NEW_FAX_APRROVAL(:V00001,:V00002,:V00003,:V0000
         4); end;
Finding 2: Interconnect Latency
Impact is .1 active sessions, 24.15% of total activity.
Higher than expected latency of the cluster interconnect was responsible for
significant database time on this instance.
The instance was consuming 128 kilo bits per second of interconnect bandwidth.
17% of this interconnect bandwidth was used for global cache messaging, 6% for
parallel query messaging and 8% for database lock management.
The average latency for 8K interconnect messages was 41863 microseconds.
The instance is using the private interconnect device "lan2" with IP address
172.16.200.72 and source "Oracle Cluster Repository".
The device "lan2" was used for 100% of interconnect traffic and experienced 0
send or receive errors during the analysis period.
   Recommendation 1: Host Configuration
   Estimated benefit is .1 active sessions, 24.15% of total activity.
   Action
      Investigate cause of high network interconnect latency between database
      instances. Oracle's recommended solution is to use a high speed
      dedicated network.
   Action
      Check the configuration of the cluster interconnect. Check OS setup like
      adapter setting, firmware and driver release. Check that the OS's socket
      receive buffers are large enough to store an entire multiblock read. The
      value of parameter "db_file_multiblock_read_count" may be decreased as a
      workaround.
   Symptoms That Led to the Finding:
      Inter-instance messaging was consuming significant database time on this
      instance.
      Impact is .06 active sessions, 14.23% of total activity.
         Wait class "Cluster" was consuming significant database time.
         Impact is .06 active sessions, 14.23% of total activity.
Finding 3: Shared Pool Latches
Impact is .09 active sessions, 22.42% of total activity.
Contention for latches related to the shared pool was consuming significant
database time.
Waits for "library cache lock" amounted to 5% of database time.
Waits for "library cache pin" amounted to 17% of database time.
   Recommendation 1: Application Analysis
   Estimated benefit is .09 active sessions, 22.42% of total activity.
   Action
      Investigate the cause for latch contention using the given blocking
      sessions or modules.
   Rationale
      The session with ID 17 and serial number 15595 in instance number 1 was
      the blocking session responsible for 34% of this recommendation's
      benefit.
   Symptoms That Led to the Finding:
      Wait class "Concurrency" was consuming significant database time.
      Impact is .1 active sessions, 24.96% of total activity.
Finding 4: PL/SQL Execution
Impact is .06 active sessions, 14.39% of total activity.
PL/SQL execution consumed significant database time.
   Recommendation 1: SQL Tuning
   Estimated benefit is .05 active sessions, 12.5% of total activity.
   Action
      Tune the entry point PL/SQL "SYS.DBMS_UTILITY.COMPILE_SCHEMA" of type
      "PACKAGE" and ID 6019. Refer to the PL/SQL documentation for addition
      information.
   Rationale
      318 seconds spent in executing PL/SQL "SYS.DBMS_UTILITY.VALIDATE#2" of
      type "PACKAGE" and ID 6019.
   Recommendation 2: SQL Tuning
   Estimated benefit is .01 active sessions, 1.89% of total activity.
   Action
      Tune the entry point PL/SQL
      "SYSMAN.EMD_MAINTENANCE.EXECUTE_EM_DBMS_JOB_PROCS" of type "PACKAGE" and
      ID 68654. Refer to the PL/SQL documentation for addition information.
Finding 5: Unusual "Other" Wait Event
Impact is .03 active sessions, 8.73% of total activity.
Wait event "DFS lock handle" in wait class "Other" was consuming significant
database time.
   Recommendation 1: Application Analysis
   Estimated benefit is .03 active sessions, 8.73% of total activity.
   Action
      Investigate the cause for high "DFS lock handle" waits. Refer to
      Oracle's "Database Reference" for the description of this wait event.
   Recommendation 2: Application Analysis
   Estimated benefit is .03 active sessions, 8.27% of total activity.
   Action
      Investigate the cause for high "DFS lock handle" waits in Service
      "mcmsdrac".
   Recommendation 3: Application Analysis
   Estimated benefit is .02 active sessions, 5.05% of total activity.
   Action
      Investigate the cause for high "DFS lock handle" waits in Module "TOAD
      9.7.2.5".
   Recommendation 4: Application Analysis
   Estimated benefit is .01 active sessions, 3.21% of total activity.
   Action
      Investigate the cause for high "DFS lock handle" waits in Module
      "toad.exe".
   Symptoms That Led to the Finding:
      Wait class "Other" was consuming significant database time.
      Impact is .15 active sessions, 38.29% of total activity.
Finding 6: Unusual "Other" Wait Event
Impact is .03 active sessions, 6.42% of total activity.
Wait event "reliable message" in wait class "Other" was consuming significant
database time.
   Recommendation 1: Application Analysis
   Estimated benefit is .03 active sessions, 6.42% of total activity.
   Action
      Investigate the cause for high "reliable message" waits. Refer to
      Oracle's "Database Reference" for the description of this wait event.
   Recommendation 2: Application Analysis
   Estimated benefit is .03 active sessions, 6.42% of total activity.
   Action
      Investigate the cause for high "reliable message" waits in Service
      "mcmsdrac".
   Recommendation 3: Application Analysis
   Estimated benefit is .02 active sessions, 4.13% of total activity.
   Action
      Investigate the cause for high "reliable message" waits in Module "TOAD
      9.7.2.5".
   Symptoms That Led to the Finding:
      Wait class "Other" was consuming significant database time.
      Impact is .15 active sessions, 38.29% of total activity.
Finding 7: Unusual "Other" Wait Event
Impact is .03 active sessions, 6.29% of total activity.
Wait event "enq: PS - contention" in wait class "Other" was consuming
significant database time.
   Recommendation 1: Application Analysis
   Estimated benefit is .03 active sessions, 6.29% of total activity.
   Action
      Investigate the cause for high "enq: PS - contention" waits. Refer to
      Oracle's "Database Reference" for the description of this wait event.
   Recommendation 2: Application Analysis
   Estimated benefit is .02 active sessions, 6.02% of total activity.
   Action
      Investigate the cause for high "enq: PS - contention" waits in Service
      "mcmsdrac".
   Recommendation 3: Application Analysis
   Estimated benefit is .02 active sessions, 4.93% of total activity.
   Action
      Investigate the cause for high "enq: PS - contention" waits with
      P1,P2,P3 ("name|mode, instance, slave ID") values "1347616774", "1" and
      "3599" respectively.
   Recommendation 4: Application Analysis
   Estimated benefit is .01 active sessions, 2.74% of total activity.
   Action
      Investigate the cause for high "enq: PS - contention" waits in Module
      "Inbox Reader_92.exe".
   Recommendation 5: Application Analysis
   Estimated benefit is .01 active sessions, 2.74% of total activity.
   Action
      Investigate the cause for high "enq: PS - contention" waits in Module
      "TOAD 9.7.2.5".
   Recommendation 6: Application Analysis
   Estimated benefit is .01 active sessions, 1.37% of total activity.
   Action
      Investigate the cause for high "enq: PS - contention" waits with
      P1,P2,P3 ("name|mode, instance, slave ID") values "1347616774", "1" and
      "3598" respectively.
   Symptoms That Led to the Finding:
      Wait class "Other" was consuming significant database time.
      Impact is .15 active sessions, 38.29% of total activity.
Finding 8: Hard Parse
Impact is .02 active sessions, 5.5% of total activity.
Hard parsing of SQL statements was consuming significant database time.
Hard parses due to cursor environment mismatch were not consuming significant
database time.
Hard parsing SQL statements that encountered parse errors was not consuming
significant database time.
Hard parses due to literal usage and cursor invalidation were not consuming
significant database time.
The Oracle instance memory (SGA and PGA) was adequately sized.
   No recommendations are available.
   Symptoms That Led to the Finding:
      Contention for latches related to the shared pool was consuming
      significant database time.
      Impact is .09 active sessions, 22.42% of total activity.
         Wait class "Concurrency" was consuming significant database time.
         Impact is .1 active sessions, 24.96% of total activity.
Finding 9: Soft Parse
Impact is .02 active sessions, 3.86% of total activity.
Soft parsing of SQL statements was consuming significant database time.
   Recommendation 1: Application Analysis
   Estimated benefit is .02 active sessions, 3.86% of total activity.
   Action
      Investigate application logic to keep open the frequently used cursors.
      Note that cursors are closed by both cursor close calls and session
      disconnects.
   Recommendation 2: Database Configuration
   Estimated benefit is .02 active sessions, 3.86% of total activity.
   Action
      Consider increasing the session cursor cache size by increasing the
      value of parameter "session_cached_cursors".
   Rationale
      The value of parameter "session_cached_cursors" was "100" during the
      analysis period.
   Symptoms That Led to the Finding:
      Contention for latches related to the shared pool was consuming
      significant database time.
      Impact is .09 active sessions, 22.42% of total activity.
         Wait class "Concurrency" was consuming significant database time.
         Impact is .1 active sessions, 24.96% of total activity.
Finding 10: Unusual "Other" Wait Event
Impact is .01 active sessions, 3.75% of total activity.
Wait event "IPC send completion sync" in wait class "Other" was consuming
significant database time.
   Recommendation 1: Application Analysis
   Estimated benefit is .01 active sessions, 3.75% of total activity.
   Action
      Investigate the cause for high "IPC send completion sync" waits. Refer
      to Oracle's "Database Reference" for the description of this wait event.
   Recommendation 2: Application Analysis
   Estimated benefit is .01 active sessions, 3.75% of total activity.
   Action
      Investigate the cause for high "IPC send completion sync" waits with P1
      ("send count") value "1".
   Recommendation 3: Application Analysis
   Estimated benefit is .01 active sessions, 2.59% of total activity.
   Action
      Investigate the cause for high "IPC send completion sync" waits in
      Service "mcmsdrac".
   Recommendation 4: Application Analysis
   Estimated benefit is .01 active sessions, 1.73% of total activity.
   Action
      Investigate the cause for high "IPC send completion sync" waits in
      Module "TOAD 9.7.2.5".
   Symptoms That Led to the Finding:
      Wait class "Other" was consuming significant database time.
      Impact is .15 active sessions, 38.29% of total activity.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Additional Information
Miscellaneous Information
Wait class "Application" was not consuming significant database time.
Wait class "Commit" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
CPU was not a bottleneck for the instance.
Wait class "Network" was not consuming significant database time.
Wait class "User I/O" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
The database's maintenance windows were active during 100% of the analysis
period.
Please help.

Hello experts...
Please do the needful... It's really very urgent.
Thanks,
Syed

Scale up curve on "Average Active Sessions"

In Grid Control 11g, Targets -> Databases -> Performance, the Average Active Sessions graph has the curve very low, almost near the bottom X axis. I know we don't have many active sessions. But it's also because this is a 4-node RAC with 96 CPUs in total. Without artificially reducing the CPU count, is there a way to scale up the curve so it does not "crawl" at the bottom? (It would be ideal if it could be manually controlled at will so when the number of active sessions does go through the roof, I can bring down the scale.)

Hi,
Did you get answer to your query ? I'm also looking for answer for this.
Basically, my requirement is get user impact due to any outage and I would like to know trend of users in the system at any given point of time.

The number of active sessions isn't decreasing in OC4J instance

Hi Guru’s,
Could you help me, please?
The number of active sessions isn’t decreasing in OC4J instance after our clients closed the application.
Our partner use Oracle AS 10gR3 (10.1.3.4.0) with J2EE and HTTP mode.
When we monitoring our OC4J instance with Performance tab on Oracle EM, we appreciate that the value of Active Sessions on ‘Servlets and JSPs’ are very high. If users close our applications, then number of active sessions isn’t decreasing and active status isn’t becoming inactive.
Which OC4J settings responsible for managing active sessions and how can I get more information about the active session details?
Thanks in advance,
Zoltan

Dinesh.Rajak wrote:
When I deployed this code Tomcat, it is giving the output as 0, hence tried with accessing the jsp file in multiple browsers but still it is showing the count of active session as 0 - plz helpPlease, don't resurrect old threads, and it's still the wrong forum. Create a new thread if you have a specific question, and create the thread in the correct forum. I'm closing this thread.
Kaj

Session counter vs cfschedule

Hi all,
Got a bit of a riddle here. Trying to count current active number of sessions and as per ColdFusion documentation that should be done as follows:
onSessionStart:
<cfset Application.sessions = Application.sessions + 1>
onSessionEnd:
<cfset Arguments.ApplicationScope.sessions = Arguments.ApplicationScope.sessions - 1>
That all works as expected as long as one doesn't use cfschedule events. Now in my application cfschedule runs every minute as a result creating new sessions as it goes. What I'm trying to do is detect cfschedule event as a session 'runner' and ignore it for my session totals.
On session start, that is done as follows:
<cfif FindNoCase("CFSCHEDULE",CGI.HTTP_USER_AGENT) EQ 0>
<cfset Application.sessions = Application.sessions + 1>
</cfif>
This way cfschedule is not counted as a site user, hence not logged.
Now my question to the community is:
How do you detect cfschedule event on session end? I was unable to locate any documentation explaining what sort of information is being passed inside the sessionScope to onSessionEnd function, hence how to access CGI info (if it's possible at all).
Absolutely any input on this would be highly appreciated!
Regards,
Simon

Hi guys,
cfchedule event starts a new session itself. As well as that it seems it's a session just like the one user would start loading the site. Therefore, as any other session it runs the session counter (Application.sessions) and increases it.
I have managed to successfully detect it upon start with the code provided in my initial post.
To answer to BKBK, if on session end, which was started by cfschedule event I would not run the same test to check whether the session in fact was initiated by the cfscheduler, the counter would be reduced.
Your suggestion does not help to solve the issue as counter meant to display only the sessions started by visitors, hence genuine data on the current site activity. An example to explain it in detail:
At a sample given time I have 5 users online. Then cfscheduler runs and creates extra session. I detect it and skip counter logging. At this moment I still have 5 users. Now let's assume the same users are browsing the website and sessions are extended beyond the original 30 minute timeout of inactivity. After 30 minutes cfscheduler's session will expire and run through the onSessionEnd function. If I would not detect it as such, the counter would be reduced to 4, even though 5 users are currently online. There's the problem I'm trying to solve.
The solution I have posted is still not 100% confirmed as sometimes it indeed shows some weird statistics.
Simon

Active session count of an user

Similar Messages

Maybe you are looking for