| Database Blocking Lock [message #530409] |
Tue, 08 November 2011 01:38  |
 |
Paules
Messages: 128
Registered: March 2011
Location: United Arab Emirates
|
Senior Member |
|
|
Hai,
Can anyone advice , how to avoid blocking locks.
Regards,
Paules.
|
|
|
|
| Re: Database Blocking Lock [message #530410 is a reply to message #530409] |
Tue, 08 November 2011 01:43  |
 |
Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...
|
Senior Member
Account Moderator |
|
|
Do not lock or forbid more than one session or use MS/Access.
If you had never blocking locks then lock would not exist.
Locks and blocking locks are necessary to ensure transactional properties.
Regards
Michel
[Updated on: Tue, 08 November 2011 01:44] Report message to a moderator |
|
|
|
|
|
|
|
|
|
|
|
| Re: Database Blocking Lock [message #530418 is a reply to message #530415] |
Tue, 08 November 2011 02:13 |
John Watson
Messages: 8962
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
Hi - what tool are you using to diagnose the problem? I would usually run the $ORACLE_HOME/rdbms/admin/utllockt.sql script as a starting point. Can you do that, while the problem is occuring? As Michel says, locks are probably to do with your application, but the output of that script will confirm this.
John.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Database Blocking Lock [message #530436 is a reply to message #530435] |
Tue, 08 November 2011 03:42 |
John Watson
Messages: 8962
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
Quote:We upgraded our database server from Oracle Database 10g Release 10.1.0.3.0 - Production RH4 to Oracle Database 10g Release 10.2.0.1.0 - 64bit Production.
Paules, who did this upgrade? If it was external consultants, they should have explained how and why they re-configured memory usage. Also, they should have applied the 10.2.0.5 patchset.
You probably need to investigate the whole upgrade process, and see if it really was done appropriately.
|
|
|
|
|
|
| Re: Database Blocking Lock [message #530441 is a reply to message #530438] |
Tue, 08 November 2011 04:00 |
John Watson
Messages: 8962
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
I think you have a problem: your upgrade was not planned and tested properly, and your consultants did not do a good job. For example:
The issue of blocking sessions should have been identified before you went live.
The 10.2.0.5 patchet should have been applied before the data migration.
The changes in memory config should have been controled.
The bahaviour of your reports should have been identified and corrected before going live.
Immediate advice: apply the 10.2.0.5 patchset. See how the application performs then, and if there are issues create a new topic and post the AWR reports (or statspack reports if you don't have the appropriate licences for AWR) that show the problems.
You might want to ask your consultants for comments on the above. Good luck.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Database Blocking Lock [message #530449 is a reply to message #530444] |
Tue, 08 November 2011 04:29 |
John Watson
Messages: 8962
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
Quote:It is not possible to alter the values of the parameters Instead of applying the patch set? Of course you can. But to what values? There is no reason to assume that values appropriate to 10.1.0.3 are appropriate to the current release and workload.
But before you do anything, you must apply the latest patchset. This includes hundreds (thousands?) of bug fixes as well as major improvements in behaviour. There is no point in trying to tune the outdated release you have at the moment. Go back to your consultants, and tell them that they should have done this.
I can't contribute any more to this discussion. Good luck.
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
