Session and lock history

Hi,
DB :10.2
I am asked to check Is there session level lock in the db Yesterday,not now.Is it possible to check?
Thanks & Regards,
Vn

>
I got a call from apps team,One of the standard job is got hang.So it's Killed.
We didn't schedule blocking session script in crontab.
>
I'm assuming you mean that yesterday a job was hung and got killed. And that now, today you want to try to find out why the job hung.
Except in an emergency you should not 'kill' a session until someone finds out what the problem is. You should not wait until the next day.
You should have a team meeting and discuss the proper procedure to follow when a problem (or potentiall problem) occurs in the DB. That process should include:
1. Determine if an emergency exists that threatens the integrity of the system. If it does take appropriate action immediately.
2. Determine the possible causes of the problem. For a session that appears to be hung find out what the session is currently doing. There may be info in V$SESSION_LONGOPS. You can check other system views to find out what other sessions are doing and even what sessions are being blocked by other sessions.
3. Then KILL or DISCONNECT the problem session if necessary.
You need to adopt a process where you do any possible troubleshooting at the time that a problem occurs or, for an emergency, immediately after you deal with the emergency.
And now that you know that you might want info about a hung session you need to document how you go about finding that information so you can use it the next time BEFORE the session is killed.
Solving a problem involves the planning and preparation for dealing with it faster and more effectively if it should happen again.

Similar Messages

I want to disable "restore previous session" and enable "History record" at the same time.

I want to disable "restore previous session" and enable "History record" at the same time.
Because I don't want others to access my account such as "Gmail", "Facebook". But I want firefox to record my browsing history.
What should I do?

I managed to remove the "Restore Previous Session" button from the home page by changing my default home page with this : www.google.com/firefox/ (the default home page from the previous versions of Firefox). It worked for me, I hope it works for you too.

Question about BC4J data tags, Oracle sessions and Locking!

Hi ,
I have seen numerous examples of JSPs using data tags and in all the examples the data tag for the application module has the "username" and "password" harcoded in it.
My questions are:
1) For a stateful application should we be including the username and password in every JSP page. I personally believe that we should not.
2) If we have a username and password in every JSP page will it not start a new ORACLE user session and if so will it not cause locking problems?
3) If we don't hard code the username and password in every JSP page, will it reuse the same ORACLE session ?
4) How do we avoid locking problems when we use data tags?
5)I can understand the inclusion of username and password in every JSP page if it is a stateless application but again Is there a way we can avoid hardcoding the username and password in every single page?
I would appreciate if some one can let me know if any of my assumptions are incorrect.
JDeveloper Team/Juan any advice?

The username and password are optional. They can be provided via the connections.properties file. The multple entries for username and password don't mean that separate connection are made. The first time the ApplicationModule tag is encountered, your application instance is created. If you are running in reserved mode (look at your releasePageResources tag) the application instance is kept until your Http session times out. If you are running in Stateful or Stateless mode, you application instance is returned to the application pool and retrieved the next time you need an instance. Please refer to the application pool documentation and to the source in oracle\jbo\common\ampool provided in jbohtmlsrc.zip.

Integrated ITS: multiple sessions and locking issue

We are upgrading to ECC 6.0 from 4.6C and have Integrated ITS turned on. We have built a custom PZM3 as one entry and exit point for our ESS services. But we have issues with session management when navigating between some services like PZ14 and PZ02. The PZ14 session and the corresponding lock are not released upon going to the PZ02 service directly. But this happens for only some services. If you navigate between PZ02 and PZ12 it works fine. I followed the instructions of note# 959417, but it didn't work. Not only it is causing locking issues, but also memory usage issues as multiple user sessions are being created on the server. I did check some of posts similar to this one, but the issue still persists.
Our WAS release: 7.00; ABAP support package: SAPKB70009; Patch level: 75.
I would appreciate if anyone could shed some light on this issue. Thank you for your time and consideration.
Kshitij

Our Basis admin found out that using a parameter ~DISCONNECTONCLOSE = 1 would resolve most of this issues -- and it did. But now we are having issues with some users having popup blockers turned on. We referred to SAP notes 892250/596698-- followed it -- implemented it-- but some users
still have issues -- like today while working from home via VPN, I am having issues with session management. But working from office yesterday,
the sessions worked just fine.

Kill a session and release all locks immediatly

Hi,
How to kill a session and release all locks immediately.
Thank you
AK

> Actually I am working on development envrionment (Not
production) with oracle 10g DB. What heppened is that
I needed to replace a stored DB Package, but I
couldn't even when I am the only connected user.
A read lock is placed on data dictionary objects when used - that prevents someone else from changing that data dictionary object and in effect pull the carpet from beneath the feet of the process using that object.
When trying to replace a package, it will fail if another session is busy using that package.
As for being the only user on the database and still running into this problem - there could have been a DBMS_JOB executing that package.
> I killed all sessions, and even next day still the
locks are there from a session I killed 1 day
before!
Unusual. But a killed session can take 24+ hours to rollback. A rollback is often a lot more time consuming than the elapsed run-time of the session at the time it was killed.
Back with Oracle 8i and prior, it was not uncommon to see a killed session lingering forever until the instance was bounced. But I have not yet seen this in 10G.
Suggest that when you run into this situation again, you monitor the killed session to determine just what it is doing (looking at its current wait states and events) - and whether it is indeed hanging and not releasing any locks that should have been released.

RFBIBL00 and locked session

Hi all,
Why when I launch RFBIBL00 this program create a locked BI session?
thank you.

Hi Fabrizio,
I'm not sure because I haven't a system here, anyway
i beleve that you have the lock because in the BGR00 record there is a date field. If it is not initial the session is locked, else no.
I don't remember if there is any check starting RFBIBL00.
I hope it help you.
bye enzo

Re: Transactions and Locking Rows for Update

Dale,
Sounds like you either need an "optimistic locking" scheme, usually
implemented with timestamps at the database level, or a concurrency manager.
A concurrency manager registers objects that may be of interest to multiple
users in a central location. It takes care of notifying interested parties
(i.e., clients,) of changes made to those objects, using a "notifier" pattern.
The optimistic locking scheme is relatively easy to implement at the
database level, but introduces several problems. One problem is that the
first person to save their changes "wins" - every one else has to discard
their changes. Also, you now have business policy effectively embedded in
the database.
The concurrency manager is much more flexible, and keeps the policy where
it probably belongs. However, it is more complex, and there are some
implications to performance when you get to the multiple-thousand-user
range because of its event-based nature.
Another pattern of lock management that has been implemented is a
"key-based" lock manager that does not use events, and may be more
effective at managing this type of concurrency for large numbers of users.
There are too many details to go into here, but I may be able to give you
more ideas in a separate note, if you want.
Don
At 04:48 PM 6/5/97 PDT, Dale "V." Georg wrote:
I have a problem in the application I am currently working on, which it
seems to me should be easily solvable via appropriate use of transactions
and database locking, but I'm having trouble figuring out exactly how to
do it. The database we are using is Oracle 7.2.
The scenario is as follows: We have a window where the user picks an
object from a dropdown list. Some of the object's attributes are then
displayed in that window, and the user then has the option of editing
those attributes, and at some point hitting the equivalent of a 'save'button
to write the changes back to the database. So far, so good. Now
introduce a second user. If user #1 and user #2 both happen to pull up
the same object and start making changes to it, user #1 could write back
to the database and then 15 seconds later user #2 could write back to the
database, completely overlaying user #1's changes without ever knowing
they had happened. This is not good, particularly for our application
where editing the object causes it to progress from one state to the next,
and multiple users trying to edit it at the same time spells disaster.
The first thing that came to mind was to do a select with intent to update,
i.e. 'select * from table where key = 'somevalue' with update'. This way
the next user to try to select from the table using the same key would not
be able to get it. This would prevent multiple users from being able to
pull the same object up on their screens at the same time. Unfortunately,
I can think of a number of problems with this approach.
For one thing, the lock is only held for the duration of the transaction, so
I would have to open a Forte transaction, do the select with intent to
update, let the user modify the object, then when they saved it back again
end the transaction. Since a window is driven by the event loop I can't
think of any way to start a transaction, let the user interact with the
window, then end the transaction, short of closing and re-opening the
window. This would imply having a separate window specifically for
updating the object, and then wrapping the whole of that window's event
loop in a transaction. This would be a different interface than we wanted
to present to the users, but it might still work if not for the next issue.
The second problem is that we are using a pooled DBSession approach
to connecting to the database. There is a single Oracle login account
which none of the users know the password to, and thus the users
simply share DBSession resources. If one user starts a transaction
and does a select with intent to update on one DBSession, then another
user starts a transaction and tries to do the same thing on the same
DBSession, then the second user will get an error out of Oracle because
there's already an open transaction on that DBSession.
At this point, I am still tossing ideas around in my head, but after
speaking with our Oracle/Forte admin here, we came to the conclusion
that somebody must have had to address these issues before, so I
thought I'd toss it out and see what came back.
Thanks in advance for any ideas!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc. [email protected]
>
>
>
>
====================================
Don Nelson
Senior Consultant
Forte Software, Inc.
Denver, CO
Corporate voice mail: 510-986-3810
aka: [email protected]
====================================
"I think nighttime is dark so you can imagine your fears with less
distraction." - Calvin

We have taken an optimistic data locking approach. Retrieved values are
stored as initial values; changes are stored seperately. During update, key
value(s) or the entire retieved set is used in a where criteria to validate
that the data set is still in the initial state. This allows good decoupling
of the data access layer. However, optimistic locking allows multiple users
to access the same data set at the same time, but then only one can save
changes, the rest would get an error message that the data had changed. We
haven't had any need to use a pessimistic lock.
Pessimistic locking usually involves some form of open session or DBMS level
lock, which we haven't implemented for performance reasons. If we do find the
need for a pessimistic lock, we will probably use cached data sets that are
checked first, and returned as read-only if already in the cache.
-DFR
Dale V. Georg <[email protected]> on 06/05/97 03:25:02 PM
To: Forte User Group <[email protected]> @ INTERNET
cc: Richards* Debbie <[email protected]> @ INTERNET, Gardner*
Steve <[email protected]> @ INTERNET
Subject: Transactions and Locking Rows for Update
I have a problem in the application I am currently working on, which it
seems to me should be easily solvable via appropriate use of transactions
and database locking, but I'm having trouble figuring out exactly how to
do it. The database we are using is Oracle 7.2.
The scenario is as follows: We have a window where the user picks an
object from a dropdown list. Some of the object's attributes are then
displayed in that window, and the user then has the option of editing
those attributes, and at some point hitting the equivalent of a 'save' button
to write the changes back to the database. So far, so good. Now
introduce a second user. If user #1 and user #2 both happen to pull up
the same object and start making changes to it, user #1 could write back
to the database and then 15 seconds later user #2 could write back to the
database, completely overlaying user #1's changes without ever knowing
they had happened. This is not good, particularly for our application
where editing the object causes it to progress from one state to the next,
and multiple users trying to edit it at the same time spells disaster.
The first thing that came to mind was to do a select with intent to update,
i.e. 'select * from table where key = 'somevalue' with update'. This way
the next user to try to select from the table using the same key would not
be able to get it. This would prevent multiple users from being able to
pull the same object up on their screens at the same time. Unfortunately,
I can think of a number of problems with this approach.
For one thing, the lock is only held for the duration of the transaction, so
I would have to open a Forte transaction, do the select with intent to
update, let the user modify the object, then when they saved it back again
end the transaction. Since a window is driven by the event loop I can't
think of any way to start a transaction, let the user interact with the
window, then end the transaction, short of closing and re-opening the
window. This would imply having a separate window specifically for
updating the object, and then wrapping the whole of that window's event
loop in a transaction. This would be a different interface than we wanted
to present to the users, but it might still work if not for the next issue.
The second problem is that we are using a pooled DBSession approach
to connecting to the database. There is a single Oracle login account
which none of the users know the password to, and thus the users
simply share DBSession resources. If one user starts a transaction
and does a select with intent to update on one DBSession, then another
user starts a transaction and tries to do the same thing on the same
DBSession, then the second user will get an error out of Oracle because
there's already an open transaction on that DBSession.
At this point, I am still tossing ideas around in my head, but after
speaking with our Oracle/Forte admin here, we came to the conclusion
that somebody must have had to address these issues before, so I
thought I'd toss it out and see what came back.
Thanks in advance for
any
ideas!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc. [email protected]
------ Message Header Follows ------
Received: from pebble.Sagesoln.com by notes.bsginc.com
(PostalUnion/SMTP(tm) v2.1.9c for Windows NT(tm))
id AA-1997Jun05.162418.1771.334203; Thu, 05 Jun 1997 16:24:19 -0500
Received: (from sync@localhost) by pebble.Sagesoln.com (8.6.10/8.6.9) id
NAA11825 for forte-users-outgoing; Thu, 5 Jun 1997 13:47:58 -0700
Received: (from uucp@localhost) by pebble.Sagesoln.com (8.6.10/8.6.9) id
NAA11819 for <[email protected]>; Thu, 5 Jun 1997 13:47:56 -0700
Received: from unknown(207.159.84.4) by pebble.sagesoln.com via smap (V1.3)
id sma011817; Thu Jun 5 13:47:43 1997
Received: from tes0001.macktrucks.com by relay.macktrucks.com
via smtpd (for pebble.sagesoln.com [206.80.24.108]) with SMTP; 5 Jun
1997 19:35:31 UT
Received: from dale by tes0001.macktrucks.com (SMI-8.6/SMI-SVR4)
id QAA04637; Thu, 5 Jun 1997 16:45:51 -0400
Message-ID: <[email protected]>
Priority: Normal
To: Forte User Group <[email protected]>
Cc: "Richards," Debbie <[email protected]>,
"Gardner," Steve <[email protected]>
MIME-Version: 1.0
From: Dale "V." Georg <[email protected]>
Subject: Transactions and Locking Rows for Update
Date: Thu, 05 Jun 97 16:48:37 PDT
Content-Type: text/plain; charset=US-ASCII; X-MAPIextension=".TXT"
Content-Transfer-Encoding: quoted-printable
Sender: [email protected]
Precedence: bulk
Reply-To: Dale "V." Georg <[email protected]>

Firefox don't close when "browsing and Download History" is deleted on exit

Firefox doesn't close properly in about 50 % of cases. When closing FF, the window closes but the process firefox.exe isn't terminated. When trying to open FF again you got the error message "Firefox is already running, but not responding. To open a new window, you must first close the existing Firefox process, or restart your system." After terminating the process firefox.exe in the windows task manager, FF can be started again.
Error only occurs when under "Options/Privacy/Use custom settings for history" at "Clear History when Firefox closes" the option "Browsing and Download History" is selected.
All other options selected or not don't cause the issue.
I switched this option it several times. When "Browsing and Download History" at "Clear History when Firefox closes" isn't selected, the error doesn't appear.
Reproducible regardless if "Remember my browsing history" and "Remember download history" are selected or not.
Reproducible:
- after new installation of Firefox (Firefox 29.0.1 german, Windows7 64-bit)
- with different profiles, even with all addons disabled or running in safe mode
- with new profile with no addons or dictionaries installed
- with windows firewall turned off and deactivated antivirus program
- with hardware accellaration on and off
I know the issue has already reported at bugzilla.mozilla.org and described at
https://support.mozilla.org/en-US/questions/997918
https://support.mozilla.org/de/questions/997670
I want to describe the problem more precisely:
It only occurs when "Browsing and Download History" is delete on exit. The other option at "Clear History when Firefox closes" don't cause this issue.
Is there any other solution then to turn "Browsing and Download History" off?

From what I have been reading from other posts on this forum, the issue may
be caused by the clear history settings.
Press the '''<Alt>''' or '''<F10>''' key to bring up the tool bar.
Then '''Tools > Options > Privacy'''.
The button next to '''History''', select '''Use Custom Settings'''.
At the bottom of the page, turn on '''Clear History When Firefox Closes.'''
At the far right, press the '''Settings''' button. Turn on ONLY '''Cache''' and
'''Form And Search History''' leaving the others off.
This is not a cure but will make it easier if Firefox locks up.
'''https://support.mozilla.org/questions/997866?esab=a&s=&r=1&as=s''' {web link}

The Firefox about:home page always shows "Restore Previous Session" and opens random things even after a clean exit.

I don't like anything opening automatically when I start Firefox, so before Firefox 4 I set Firefox to open a blank page when it starts. I still had set a page I visit frequently as my home page, so I could get to that page quickly by pressing the home button. If I needed to close Firefox it was nice and easy to have the option to save my session and close (I've already searched and read another post and answer on how to restore this feature in about:config). I understand that Firefox 4 always saves your session and you can restore it from the history menu, but then I would have to remember if I had anything open and click menu/History/Restore Previous Session.
Now in Firefox 4 I have left the home page set to about:home so if I had tabs open when I closed it I would see the Restore Previous Session "button" the next time I start it. However, when I close all windows and tabs before exiting Firefox, the Restore Previous Session "button" will be sometimes be there. If I click it, it will open a random tab or window that I visited the previous day, which was NOT the last tab/window that I had open.
If I do have tabs open when I close it, it does correctly re-open them when using the Restore Previous Session button, it only does this if I do a clean exit (close all tabs/windows before close).
I tried deleting the sessionstore.js and sessionstore.bak files from my Firefox appdata directory (there were no other sessionstore.* files). This is a clean install of Firefox 4, I didn't install on top of Firefox 3.6.xx. I uninstalled Firefox 3.6.xx before installing and made sure to delete any leftover files in my appdata, programdata and program files directories.

I thought about that before and tried it, and it doesn't seem to make a difference. I did it just now, I opened a blank tab and closed everything else, waited a minute then closed Firefox. I waited another minute and launched Firefox. The Restore Previous Session box was there on about:home. I clicked it and it opened a new window with about:home in it.

Odd situation with Safari after enabling account expiration and locking

Hi team,
i found the following puzzling situation today.
I enabled account expiration and locking in a workspace, thereafter all end users were requested to change their password as soon as they attempted to login to the application.
Some of these users went through this process smoothly and after changing the password they could log in. Others apparently succeeded in changing the password but the password change process is triggered again and again.
These users are receiving the following message after clicking on "apply changes" (p50 of app 4155).
ERR-1777: Page 50 provided no page to branch to. Please report this error to your application administrator.
When clicking on "restart application", they get the following additional screen:
You have successfully logged out. You have been redirected here after using a logout link provided by an authentication scheme. To redirect to a page in your flow instead, do something like this:
Create a page in your flow and give it an alias PUBLIC_PAGE.
On the Flow Builder page attributes page, select the "Yes - This page is public" Public Page attribute.
Change the logout URL in your authentication template to redirect to this new page after the logout procedure executes. For example, using the API, make your logout URL:
wwv_flow_custom_auth_std.logout?p_this_flow=&FLOW_ID&p_next_flow_page_sess=&FLOW_ID:PUBLIC_PAGE:&SESSION
Note that the suggested URL uses a somewhat outdated syntax lacking the period after the application items, so you might want to revise it for future releases.
After various tests it turned out that the problem is in the browser (don't ask me what).
Safari users do not succeed in changing their passwords through page 4155:50, while Firefox users do.
I have a password change page inside my application though and everybody can change their password from there successfully.
Also, after changing the password using Firefox, Safari users can log in without problems whatsoever.
So the final question is: what's wrong with page 50 of application 4155 when run from Safari on Mac?
It happened with Apex 3.1.2 and Safari Version 3.2.1 (5525.27.1)
Thanks!
Flavio
http://oraclequirks.blogspot.com/search/label/Apex

Scott,
that was exactly what i was about to do yesterday night, but at the post office i realized i didn't know the address :D
Then, fortunately for me, but regrettably for you (hehehe), i realized that Safari is not the culprit.
For some reason people using Safari were always submitting the page with enter, while Firefox users were submitting with the button.
I made a test and Safari is fine as long as you click on the button, the bug is in the submit through the enter key.
Thanks and sorry about the mac air, may be the next time!
Flavio
PS: aren't you coming to ODTUG Kaleidoscope?

Killing User sessions and user calcs

Hi all,
We have a situation where users run their business rules during evening and at times in night.
We also have a maxl script which does aggregation and other calcs daily in night and it does not run as other calcs are launched by users.
Is it possible to kill the user session and calcs launched by users before running maxl calculation for consolidations?
I know I can do in in EAS, but want to try to do it in MAxL for automation.
Thanks in advance

You would be better off locking people out. After you kick off the automated calc, killing sessions doesn't stop them from initiating calcs while your automated calc is running. In answer to your question, yes, you can do that in maxl.
alter system kill request all;
You have other options if you want to be more selective on what you kill.
kill request <session-id>
kill request by user
kill request on application
kill request on database
Check out the technical documentation for more info - http://docs.oracle.com/cd/E17236_01/epm.1112/esb_tech_ref/launch.html.
Kyle Goodfriend
http://www.in2hyperion.com
Please make sure to assign helpful/answered to responses if applicable - it rewards those who help and benefits the user community.

RD Session Host lock down best practice document

Hello,
I am currently working on deploying an RDS Farm. My farm has several RD Session host servers. Today I learned that you can do some bad things to the RD Session hosts, if a user presses
CTRL + Alt + End when having a open session. I locked all of this down using different GPOs which include disabled access task manager, cmd, locking the server, reboot and shutdown etc.
However, this being sad how would I know what else to lock down since I am new to this topic. I tried to find some Microsoft document about best practices what should be locked down but I wasn’t
successful and unfortunately a search in the forum did not bring up anything else.
With all the different features and option Windows Server 2008 R2 has I do not even know where to start.
Can some please point me into the right direction.
Thank you
Marcus

Hi,
The RD Session host lock down best practices of each business is different, every enterprise admin can only to find the most suitable for their own solutions based on their IT infrastructure.
I collected some resource info for you.
Remote Desktop Services: Frequently Asked Questions
http://www.microsoft.com/windowsserver2008/en/us/rds-faq.aspx
Best Practices Analyzer for Remote Desktop Services
http://technet.microsoft.com/en-us/library/dd391873(WS.10).aspx
Remote Desktop Session Host Capacity Planning for 2008 R2
http://www.microsoft.com/downloads/details.aspx?FamilyID=CA837962-4128-4680-B1C0-AD0985939063&displaylang=en
RDS Hardware Sizing and Capacity Planning Guidance.
http://blogs.technet.com/iftekhar/archive/2010/02/10/rds-hardware-sizing-and-capacity-planning-guidance.aspx
Technical Overview of Windows Server® 2008 R2 Remote Desktop Services
http://download.microsoft.com/download/5/B/D/5BD5C253-4259-428B-A3E4-1F9C3D803074/TDM%20RDS%20Whitepaper_RC.docx
Remote Desktop Load Simulation Tools
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c3f5f040-ab7b-4ec6-9ed3-1698105510ad
Hope this helps.
Technology changes life……

Safari is showing everything greyed out and locked, how do I change that?

I'm having a problem where Safari periodically locks and greys the screen. It wil continue to update / refresh but I can't inter act with it. The onjly way I've been ab l to clear this is to reset my ipad. Obviously dont want to keep doing that all the time. Top of screen shows a closed padlock. Not sure why or how it got there. Ideas??

Try clearing Safari's cache : Settings > Safari > Clear Cache (and Clear History)
If that doesn't work then try closing Safari completely and then re-open it : from the home screen (i.e. not with Safari 'open' on-screen) double-click the home button to bring up the taskbar, then press and hold any of the apps on the taskbar for a couple of seconds or so until they start shaking, then press the '-' in the top left of the Safari app to close it, and touch any part of the screen above the taskbar so as to stop the shaking and close the taskbar.
A third option is a reset : press and hold both the sleep and home buttons for about 10 to 15 seconds (ignore the red slider), after which the Apple logo should appear - you won't lose any content, it's the iPad equivalent of a reboot.
The padlock symbol means that you've got rotation lock on. Depending on what you've got Settings > General > Use Side Switch To set to (rotation lock or mute notifications), then you can lock the rotation by the switch on the right hand side of the iPad, or via the taskbar : double-click the home button; slide from the left; and it's the icon far left; press home again to exit the taskbar. The function that isn't on the side switch is set via the taskbar instead : http://support.apple.com/kb/HT4085

Wait events and locks monitoring /resolving scripts

Looking for wait events and locks monitoring /resolving scripts /tips.

Hi,
Looking for wait events and locks monitoring /resolving scriptsHere is the collection of monitoring scripts that I
use, and it has dozens of scripts for locking:
http://www.oracle-script.com
For one-off scripts, here is a script by Laurent Baylac to show locks in Oracle 10g:
http://www.dba-village.com/village/dvp_scripts.ScriptDetails?ScriptIdA=3508
SET LINESIZE 500
SET PAGESIZE 1000
COLUMN username FORMAT A15
COLUMN machine FORMAT A25
COLUMN logon_time FORMAT A20
SELECT LPAD(' ', (level-1)*2, ' ') || NVL(s.username, '(oracle)') AS username,
s.osuser,
s.sid,
s.serial#,
s.lockwait,
s.status,
s.module,
s.machine,
s.program,
TO_CHAR(s.logon_Time,'DD-MON-YYYY HH24:MI:SS') AS logon_time
FROM v$session s
CONNECT BY PRIOR s.sid = s.blocking_session
START WITH s.blocking_session IS NULL;
SET PAGESIZE 14
-- Search for locked objects
-- To be executed under the SYSTEM account
-- Compatible with Oracle10.1.x and higher
select
distinct to_name object_locked
from
v$object_dependency
where
to_address in
select /*+ ordered */
w.kgllkhdl address
from
dba_kgllock w,
dba_kgllock h,
v$session w1,
v$session h1
where
(((h.kgllkmod != 0) and (h.kgllkmod != 1)
and ((h.kgllkreq = 0) or (h.kgllkreq = 1)))
and
(((w.kgllkmod = 0) or (w.kgllkmod= 1))
and ((w.kgllkreq != 0) and (w.kgllkreq != 1))))
and w.kgllktype = h.kgllktype
and w.kgllkhdl = h.kgllkhdl
and w.kgllkuse = w1.saddr
and h.kgllkuse = h1.saddr
Don Burleson
Oracle Press author

When trying to clear the history (Browsing and download history, cookies, form and search history, and cache) firefox freezes and sometimes Ill get a warning for an unresponsive script.

When trying to clear the history (Browsing and download history, cookies, form and search history, and cache) firefox freezes and sometimes Ill get a warning for an unresponsive script.
Using MacOSX 10.6.8 on Macbook Pro
Using Firefox 10.0.2

Try to exclude the cookies from the clear history settings and let the cookies expire at the end of the session instead.

Session and lock history

Similar Messages

Maybe you are looking for