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.
Similar Messages
-
Average Active Sessions on Performance page
Hi all
how do we fetch details for average active sessions in performance page.
Specifically which tables do we use to get those details.
ThanksHi,
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. -
Average Active Sessions graph not updated after restart
Hi,
I just wanted to ask - I have restarted a database (11.1.0.7) with GC 11.1.0.1 but after the restart of the db the graphs on a performance tab are not updated. It means that the doesn't refresh and doesn't show actual data...
I checked jobs on the target database and GC repository but nothing is broken. Info on Home tab of the target DB is actual but not the graphs..
I also tried to clearstate and restart the agent but no change..
Any idea?
ThanksThis is a bug and can be solved by applying
Patch 10307099: PERFORMANCE CHARTS DO NOT UPDATE AFTER DATABASE IS RESTARTED
This patch is included in the july 2011 PSU: Grid Control Patch Set Update 11.1.0.1.4 for the Oracle Management Service, see MOS doc ID 1334286.1
Eric -
How to config EM performance page to display 30 days Average Active Session
Does EM supports displaying 30 days ASH data in the performance page without clicking the calendar tool?
Now EM only can show 7 days view.AWR collects performance related statistics and derives performance metrics from them to track a potential problem. Unlike Statspack, snapshots are collected automatically every hour by a new background process called MMON and its slave processes. To save space, the collected data is automatically purged after 7 days. Both the snapshot frequency and retention time can be modified by the user. To see the present settings, you could use:
select snap_interval, retention
from dba_hist_wr_control;
SNAP_INTERVAL RETENTION
+00000 01:00:00.0 +00007 00:00:00.0
To change the settings--say, for snapshot intervals of 20 minutes and a retention period of two days
begin
dbms_workload_repository.modify_snapshot_settings (
interval => 20,
retention => 2*24*60
end;
Hope this helps,
Regards,
http://www.oracleracexpert.com
Overview of Transparent Application Failover in Oracle RAC
http://www.oracleracexpert.com/2010/04/overview-of-transparent-application.html
In function 'lcdprm':: Warning after patch in RAC
http://www.oracleracexpert.com/2010/04/in-function-lcdprm-warning-gets.html -
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 TiwariHi,
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 -
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 -
HI Folks,
WIndows : 2008 R2
SQL : 2012 sp1 EE
Setup disappears when installing setup support files On passiive node ( 2 node cluster), sql is runing on active node without any issue
Error : SQM does not active session ( In summary detail txt file)
blog is suggesting . Save the following in a .reg file and merge to populate the registry: (
here i am confusing how to save and where to save , how to merge and how to populate)
http://blogs.msdn.com/b/sqljourney/archive/2012/05/07/sql-2008-2008-r2-setup-disappears-fails-when-installing-setup-support-files.aspx
Can you share your views, if you need any information for clarification. pls let us know for resolution.
Thanks in Advance.Sorry but there is already released SP2 for SQL Server 2012. Start installation on the passive node first
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence -
Cannot deploy EAR. There are already active sessions
Hi WebDyn Pro's,
I'm running NW SP14
Sporadically, I cannot deploy my WebDynpro app to the NW server. In NWDS, I indicate to Deploy and run. I get an error in the console indicating:
<b>"Cannot log in. There are already active sessions. Session id 0 An administrator logged in via API /"</b>
I restarted the server and the NWDS workstations but that didn't help. I've had this same error in the past. Usually it goes away. I thought I solved it, but evidently not.
On the NW server, I cannot log into SDM GUI either. I get the same error.
As mentioned above, this error occurs sporadically. I can deploy just fine 50 times. And then all of sudden I start getting this error, even though no one has touched the server.
Thoughts?
Thanks,
KevinHi,
Have you checked if anyone else is actually using SDM to deploy?
There are some quite significant deployment tasks that my basis team perform which will occupy the SDM tool for a long time and stop me and my other developers from deploying anything.
I've also caused this problem myself when my SDM deployment has stalled - I've been deploying a custom B2B .ear file and the deployment has just got stuck in processing for ages. In the end I've had to kill the SDM task from Windows Task Manager but this causes SDM to think someone is still logged in so I've then had to restart the SDM service from the SAP Management Console.
If this is not the case I'd suggest raising it through OSS if you can't find any relevant messages on there.
Hope this helps,
Gareth Ryan. -
No data in Active sessions pie-chart and availability is 0%
Hi All,
Does anyone know why my Enterprise Manager cosole in Oracle 10g installed on windows xp professional is not showing any data? Availabilty is always 0% for the instance ORCL and the active sessions pie-chart is always showing 0.01 since May 17,2005.
Can anyone tell me how to configure EM so that instance ORCL and the active sessions start showing data again?
ThanksHi,
Kindly activate the data request. Post that, Under "request available for reporting" a symbol will appear which means that the data has been moved to Active table and is available for reporting at further levels.
And you can then check for contents in the active table of the DSo, you should get the records.
Change log: Contains the change history for the delta update from the DataStore object into other data targets, such as DataStore objects or InfoCubes. It makes sense in case of delta uploads.
Regards,
hemlata -
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,
JeffThank 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 -
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. -
How to get active sessions in tomcat 5.0?
Hi,
As I am working on monitoring related requirement, I need to get no. Of active sessions,sessions created, etc.
I found interesting code in ManagerServlet, As it has some protected methods, I cant call it from its object, I need to create servlet for my work, So I even can't extend ManagerServlet, So I've created one POJO for that, But now I need to populte the context and many other objects,
Is there any other way out for this?,
I really appriciate any kind of help. :-)
-Jeffhi :-)
http://java.sun.com/j2ee/tutorial/1_3-fcs/doc/Servlets.html
or
http://www.google.com.ph/search?hl=en&q=java+servlet+tutorial&btnG=Google+Search&meta=
regards, -
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. -
Any way to get number of active sessions
Hi,
With the deprecation of the HttpSessionContext interface as of Servlet API
2.1 for security reasons, is there any way to know how many sessions are
currently active in a given WebLogic instance?
Thanks,
Sanjiv
You could make it a singleton. The overhead is nothing ... trust me. Run
WebLogic through a profiler if you don't ;-)
Good luck,
Cameron Purdy, LiveWater
"Sanjiv Gulati" <[email protected]> wrote in message
news:[email protected]...
> Thanks for sharing this technique. Although I haven't used the
> HttpSessionBindingListener interface myself, this will work as long as I
add
> an instance of SessionCounter in each new session. The only modifications
> I'll add to the code below would be a synchronized block within the
> valueBound and valueUnbound methods so that modifications to m_cSessions
are
> thread safe.
>
> The overhead associated with this approach will be the following:
> 1) For every session there will be an associated SessionCounter, and
> 2) Serialization of requests that end up invoking the valueBound &
> valueUnbound methods.
>
> But I guess this cannot be avoided.
>
> Thanks,
> Sanjiv
>
> Cameron Purdy <[email protected]> wrote in message
> news:[email protected]...
> > The only portable implementation is to have all requests go through your
> > servlet code (or JSP code) and check if the session is new
> > (HttpSession.isNew). If so, register a value with the session that
> > implements HttpSessionBindingListener. Something like:
> >
> > class SessionCounter implements HttpSessionBindingListener {
> > // count of active sessions
> > private static int m_cSessions;
> > // accessor for count of active sessions
> > public int getSessionCount() {
> > return m_cSessions;
> > }
> > // this object placed on a session
> > void valueBound(...) {
> > ++m_cSessions;
> > }
> > // this object removed from a session
> > void valueUnound(...) {
> > --m_cSessions;
> > }
> > // end class
> > }
> >
> > It is host-local ... meaning it only tracks one host in a cluster.
> > Actually, it only tracks sessions within one classloader on one host in
a
> > cluster, but don't worry about that distinction.
> >
> > And no, I've never done it, but it is apparent that you could, if you
> chose
> > to:
> >
> > 1) Count sessions
> > 2) Track all session instances
> > 3) Have session-level events, such as onCreate/onDestroy
> >
> > Hope it helps,
> >
> > Cameron Purdy, LiveWater
> >
> > "Sanjiv Gulati" <[email protected]> wrote in message
> > news:[email protected]...
> > > Hi,
> > >
> > > With the deprecation of the HttpSessionContext interface as of Servlet
> API
> > > 2.1 for security reasons, is there any way to know how many sessions
are
> > > currently active in a given WebLogic instance?
> > >
> > > Thanks,
> > > Sanjiv
> > >
> > >
> >
> >
>
>
-
Active sessions showing no data in pie-chart
Hi All,
Does anyone know why my Enterprise Manager cosole in Oracle 10g installed on windows xp professional is not showing any data? Availabilty is always 0% for the instance ORCL and the active sessions pie-chart is always showing 0.01 since May 17,2005.
Can anyone tell me how to configure EM so that instance ORCL and the active sessions start showing data again?
ThanksWhat errors were you seeing in the log files, i am experienceing the same issue but the listener appears to be fine.
Maybe you are looking for
-
Hi All, Greetings. I have two queries namely, 1.Query for cancelled requisitions and 2.Query for Internal Requisitions without Internal Sales Orders. I was on a task to combine those two queries.. Can we do that? if so, please help me do that.. Thank
-
(To SUN DTS) Where is tcp.c in solaris 8 open source foundation?
Dear SUN DTS, I have downloaded the solaris 8 open source foundation. But I cannot find tcp.c file. Ip.c was there as ip.c.export. Is this SUN's purpose not giving out the tcp.c, or this is someone's mistake when packaging. Without it, the source fou
-
Updated I Web on Leopard - now uses 80-90% of CPU power!
Hi, I manage several websites using Iweb every day. I just updated ("small bug fixes"), and now it's worse than ever, using 80-90% of CPU in my Activity Monitor without even doing anything in the program, just opening it and letting it sit for a se
-
I have a main application, with a custom VBox component, which then holds a nested Form component. So three layers deep in total. Upon form submit, what is the best way to get the data from the form component(third layer) back up to the main app (fir
-
OEM is not conifgured when try to reconfigure it manually
Hi Guru's, This question asked previously but after applying the solutions what exactly i am getting there still i am not able to reconfigure the EM manually. C:\Data> set ORACLE_SID=orcl C:\Data> emca -deconfig dbcontrol db -repos drop DROP USER sys