Sql_id of active session not in v$sql

Hi all,
How do you explain this?
There is one active session in v$session with a sql_id. But when I query v$sql using that sql_id I got nothing back. Is this because the sql_id was pushed out of shared memory or some other reason? The connection is shared session.
Our db is 10.2.0.3 and server is MS window 2003 server.
Thanks,
Shirley

Hi,
Can you check what is the wait event of that session? Also can you tell me how you decided its active?
select sql_id, prev_sql_id, last_call_et, status, program, event, sid from v$session where sid = <sid>Regards
Anurag

Similar Messages

Monitor Activity - Active Sessions : Not displaying all sessions

I'm encountering an issue whereby the active sessions are not being listed in the Monitor Activity -> Active Sessions screen.
However, the number of Active Sessions is being displayed.
Any ideas?

Hi Dave,
I think there's some confusion here. The select list right after the label Display is for you to select the maximum number of rows you want to display on the report. The actual number of sessions in the report will be shown below.
I did this just now on apex.oracle.com. I chose a value of 15 (the default) for Display. And at the split second that I clicked Go, there were only 4 active database sessions - and the pagination label at the bottom of the report was "1 - 4", which was correct.
I just think you're misinterpreting Display.
Joel

Session not being clean up by JRun

My application is using IPlanet WebServer and JRun3.02 Application server. I am having a problem with active session not getting cleaned up by the App Server. When the user goes through the application and finishes the process, I invalidate the session by doing 'session.Invalidate()'. I also have set a 30 minute timeout value in the JRun global.properties file to invalidate the session if the user starts but not finish going through the application. However, the number of active session count in the JRun log doesn't seem to go down. After a few days, I ran out of sessions and the application hungs. I keep a few objects on the session including a pretty big 'pdfObject' that I use to create a PDF document on the fly.
Any idea why JRun not able to clean up the sessions after the 30 minute timeout has passed? Does the fact that I have stored objects on the session preventing JRun from invalidating and cleaning up the session?
Thanks in advance.

Hi afikru
According to the Servlet specification session.invalidate() method should unbind any objects associated with it. However I'm not conversant with JRun application server so I can only provide some pointers here to help you out.
Firstly, try locating some documentation specific to your application server which may throw some light on why this may be happening.
Secondly, I'd suggest running the Server within a Profiling tool so that you can see what objects are being created and how many of those. Try explicitly running the Garbage Collector and see if the sessions come down.
Keep me posted on your progress.
Good Luck!
Eshwar R.
Developer Technical Support
Sun microsystems

SQL 2012 sp1 EE setup disappears when installing Setup Support files ( Error: sqm does not have active session)

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

Running of process flow does not show any Active session in Database

Hi Team,
I am running a process flow in OWB 11g ( From Design Center ) which is having around 100 maps within it. However, from Control Center I can see the Process Flow is running ( i.e. Green check is visible beside the process flow) but when I run SQL query in backend database ; I am unable to see any running object ( i.e. OWB map name as package object) there corresponding to this Process Flow
I am running the below query to check the availability of running session :-
SELECT A.LOGON_TIME,A.SID,B.OBJECT_NAME,A.*
FROM gv$session A, dba_objects B
WHERE A.PLSQL_ENTRY_OBJECT_ID = B.OBJECT_ID
AND A.STATUS = 'ACTIVE'
Could you please suggest if this is something wrong in the development of the Process Flow or we can`t see any running map there in backend when we execute any process flow from OWB ?
Thanks in advance
Nilava Sen

Try below query
select sid,module,program,status,sql_id from gv$session where status='ACTIVE';
select * from gv$access;

SCCM sql query Client status if active or not in specific Collection

I would like to create an sql report to show if config manager client is active or not in specific Collection
, im using the query belong to "ManoharPusala"
Thank you so much which is
SELECT S.Name0 as 'Computer Name', S.User_Name0 as 'User Name',Case when CS.ClientActiveStatus='1' then
'Active' When CS.ClientActiveStatus='0' then 'Inactive' end as 'Client Active Status' FROM v_R_System S inner Join v_CH_ClientSummary CS on S.ResourceId=CS.ResourceID
is working as well but i want to modify it to query form a specific Collection
, please help me .
Thanks

Hi,
Please try to add "Join _RES_COLL_collectionID as coll on s.Name0=coll.name" to the end of the query.
SELECT S.Name0 as 'Computer Name', S.User_Name0 as 'User Name',Case when CS.ClientActiveStatus='1' then 'Active' When CS.ClientActiveStatus='0' then 'Inactive' end as 'Client Active Status' FROM v_R_System S inner Join v_CH_ClientSummary CS on S.ResourceId=CS.ResourceID join _RES_COLL_PRI0000A as coll on S.Name0=coll.name
Best Regards,
Joyce

SCCM sql query Client status if active or not

I would like to create an sql report to show if config manager client is active or not, right now I query
v_R_System, for installed client. Any guidance on which table to query for active or not active clients would be helpful.

I had the same question. I found that this query does what I wanted. You can certainly change the number of days since LastHardwareScan.
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ResourceId in (select SMS_R_System.ResourceID from
SMS_R_System inner join SMS_G_System_WORKSTATION_STATUS on SMS_G_System_WORKSTATION_STATUS.ResourceID = SMS_R_System.ResourceID where DATEDIFF(dd,SMS_G_System_WORKSTATION_STATUS.LastHardwareScan,GetDate()) < 90)
I hope this helps :)

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

Multitrack session not active?

Might be a dumb question but adobe not letting me open a file in the editor just pops up with an error saying "Multitrack session not active. Mixer controls are enabled only when a multitrack session is the active document"
Any ideas?
Using adobe Audition for Mac Beta.
Cheers
Ben...

If you check the dates on the original post, it's from about 3 years ago before the Audition for Mac was officially released, hence the desire to get all queries about that software in the one place.
Anyhow, that was then and this is now.
The only time I know you get that warning is when you attempt to use the Mixer view without having first set up a multitrack session--the mixer is inactive until you have a session to mix. The tabs to control Edit View vs Mixer view are at the top of that main window where you normally see waveforms or the mixer.
There are lots of ways to create a multitrack session...I guess the most basic is File--->New--->Multitrack Session. This will give you a dialogue window where you set up things like the title, the bit depth and sample rate, whether you want a stereo or mono master, that sort of thing. Alternately, just Edit--->Insert--->Into Multitrack Session which will give you a choice of existing sessions or the dialogue box to create a new one again.

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

File- Print not working from SQL Developer 1.2.1 Build MAIN-32.13

File->Print not working from SQL Developer 1.2.1 Build MAIN-32.13.
I downloaded sqldeveloper-1.2.1.3213.ZIP and extract to a local directory. From the extracted directory I ran ..\sqldeveloper\sqldeveloper.exe from Windows XP sp2. The program itself seems to run just fine but File-Print doesn't do anything. In Help-About, Java Platform is reported as 1.5.0_06 and Oracle IDE is 1.2.1.3213. I'm not sure where to look for what is causing the problem.
Thanks

I hadn't tried CTRL-P before but I did today. On the first attempt, I saw a small jump in the memory usage for sqldeveloper.exe as reported in Windows Task Manager. Otherwise, there was no change. A second CTRL-P in the same session produced a further bump but subsequent attempts in the same session produced no further change in CPU or Memory Usage.
Using Task Manager to monitor this further, I tried File->Print again and saw that sqldeveloper would periodically climb to 1 or 2 percent CPU and consume a little more memory. After a minute or so, though, all activity stops again.
I do not get a print dialog box from SQLDeveloper using either CTRL-P or File->Print

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.

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,
Kevin

Hi,
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?
Thanks

Hi,
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,
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

Sql_id of active session not in v$sql

Similar Messages

Maybe you are looking for