Logs for Database Locks

Hi All,
One of my ztable did not get updated with the new entries using the UPDATE statement. This happend last week in one of our landscape systems. I assume that the ztable was locked during that instance since many users were updating the table via a webapplication.
Is there any log which I can pull out and see that this ztable was actually locked during that particular time.
I do know the exact time and date. Is there any t-code which can help me see the OLD lock details.
( The problem is I am not able to reproduce the same scenario now ).
Thanks
Yogesh

Hi,
this data is stored in the system logs. It depends how long this data is saved (basic settings).
Please check transaction ST11 or try to make it happen again and monitor it via ST01.
Kind regards,
Peter

Similar Messages

Any body able to help me : The transaction log for database 'KDS' is full

Hi Experts,
I am facing the follwoing problem when i entered into the portal.
[NWMss][SQLServer JDBC Driver][SQLServer]The transaction log for database 'KDS' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases.
Exception id: 10:51_28/09/07_0006_3439451
See the details for the exception ID in the log file
Please give me a solution urgent.
Message was edited by:
Ramanan Panchabakesan

Ameya,
The log file seems to be....[ i have bolded the warning number and bold+underline the error number].kindly see this
#1.5 #001320E973F2004900000281000010D400043B2BF18A5CFD#1190959829445#com.sap.engine.services.deploy##com.sap.engine.services.deploy######01eb74206d8811dc8114001320e973f2#SAPEngine_System_Thread[impl:5]_5##0#0#Warning#1#/System/Server#Plain###
Warning occurred on server <b>3439450</b> during startApp sap.com/cafruntimemonitoringear : Application sap.com/cafruntimemonitoringear has weak reference to application sap.com/com.sap.jdo and is starting it!#
#1.5 #001320E973F2004900000283000010D400043B2BF18A5DCF#1190959829445#com.sap.engine.services.deploy##com.sap.engine.services.deploy######01eb74206d8811dc8114001320e973f2#SAPEngine_System_Thread[impl:5]_5##0#0#Warning#1#/System/Server#Plain###
Warning occurred on server <b>3439450</b> during startApp sap.com/cafruntimemonitoringear : Application sap.com/cafruntimemonitoringear has weak reference to application sap.com/caf~km.proxies and is starting it!#
#1.5 #001320E973F2004900000285000010D400043B2BF18A5E85#1190959829445#com.sap.engine.services.deploy##com.sap.engine.services.deploy######01eb74206d8811dc8114001320e973f2#SAPEngine_System_Thread[impl:5]_5##0#0#Warning#1#/System/Server#Plain###
Warning occurred on server <b>3439450</b> during startApp sap.com/cafruntimemonitoringear : Application sap.com/cafruntimemonitoringear has weak reference to application sap.com/cafruntimeear and is starting it!#
#1.5 #001320E973F2004900000287000010D400043B2BF18A5F72#1190959829461#com.sap.engine.services.deploy##com.sap.engine.services.deploy######01eb74206d8811dc8114001320e973f2#SAPEngine_System_Thread[impl:5]_5##0#0#Warning#1#/System/Server#Plain###
Warning occurred on server <b>3439450</b> during startApp sap.com/cafruntimemonitoringear : Application sap.com/cafruntimemonitoringear has a weak reference to resource jmsfactory/TopicConnectionFactory with type javax.jms.TopicConnectionFactory but the resource is not available and the application may not work correctly!#
#1.5 #001320E973F2001100000002000010D400043B2BF18FC93A#1190959829805#com.sap.jms##com.sap.jms.LOCK_EXCEPTION######837a4dd06d8911dcbe35001320e973f2#SAPEngine_System_Thread[impl:5]_34##0#0#Warning#1#/System/Server#Java###Couldn't acquire Lock $service.jms_provider. Current JMS lock owner is server node with id = .#1#<i><b><u>3439451</u></b></i>#
#1.5 #001320E973F200490000028D000010D400043B2BF1A40473#1190959831134#com.sap.engine.services.jndi##com.sap.engine.services.jndi######01eb74206d8811dc8114001320e973f2#SAPEngine_System_Thread[impl:5]_5##0#0#Path##Java###Caught #1#com.sap.engine.services.jndi.persistent.exceptions.JNDIException: Error during s object serialization.
at com.sap.engine.services.jndi.implclient.ClientContext.serializeObject(ClientContext.java:3335)
at com.sap.engine.services.jndi.implclient.ClientContext.serializeDirObject(ClientContext.java:3224)
at com.sap.engine.services.jndi.implclient.ClientContext.rebind(ClientContext.java:1032)
at com.sap.engine.services.jndi.implclient.ClientContext.rebind(ClientContext.java:957)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebApplicationConfig.bind(WebApplicationConfig.java:455)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebApplicationConfig.parse(WebApplicationConfig.java:116)
at com.sap.engine.services.servlets_jsp.server.runtime.context.ApplicationContext.init(ApplicationContext.java:617)
at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.createContext(WebContainerHelper.java:540)
at com.sap.engine.services.servlets_jsp.server.container.StartAction.prepareStart(StartAction.java:51)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.prepareStart(WebContainer.java:475)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.jndi.persistent.exceptions.JNDIException: Error during s object serialization.
at com.sap.engine.services.jndi.persistent.RemoteSerializator.toByteArray(RemoteSerializator.java:55)
at com.sap.engine.services.jndi.implclient.ClientContext.serializeObject(ClientContext.java:3332)
... 24 more
Caused by: java.io.NotSerializableException: com.sap.engine.system.ORBProxy
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.jndi.persistent.RemoteSerializator.toByteArray(RemoteSerializator.java:48)
... 25 more

The transaction log for database 'EMP_SP_SearchApp_CrawlStoreDB_32fdb1522c5249088db8b09c1917dbec' is full due to 'ACTIVE_TRANSACTION'

Hi
we have a sharepoint farm for uploading documents in huge number daily and we conifgured RBS for sql server content db.
we are facing issue in sql server instance:
Suddenly the SQL server instance restarts and sometimes failover to node1 and sometimes just restart and keep running on the current server
and did some invistagations we found that
-Analysis of data shows that the slowness of IO for tempdb.ldf is cause of the issue
-tried to check tempdb using db properties but I couldn’t see the properties it gives me error,
-There might be a big transaction locking the tempdb.
Also noted that there are lot of errors:
The transaction log for database 'MOJSP_SearchApp_CrawlStoreDB_32fdb1522c5249088db8b09c1917dbec' is full due to 'ACTIVE_TRANSACTION'
This might also be part of the problem causing locking.
we found the errors like
The transaction log for database 'EMP_SP_SearchApp_CrawlStoreDB_32fdb1522c5249088db8b09c1917dbec' is full due to 'ACTIVE_TRANSACTION'
I see that log_reuse_wait_desc (reuse of transaction log space is currently waiting on as of the last checkpoint) is 'ACTIVE_TRANSACTION'
adil

Hi Adil,
Method1:
On your SharePoint SQL Server database, open the SQL Server Management Studio.
Connect to the local SQL Server.
Right click Your Database Name.
Go to -> Properties -> Options.
Change Recover Model from Full to Simple -> Click OK.
Right click Your Database Name, go to Tasks -> Shrink -> Shrink Files.
Select a File type of Log, then Shrink.
Method2:
Run SQL Management Studio and login to your SharePoint instance.
Click on "New Query".
Type in the following commands:
USE [database name];
BACKUP LOG [Your Database Name] WITH TRUNCATE_ONLY;
DBCC
SHRINKFILE ([Your Log File Name], 1);
Replace [Your Database Name] and [Your Log File Name] with your log file.
This will truncate your log file to 1mb.
Method3:
Issue CHECKPOINT on the tempdb
USE tempdb
GO
CHECKPOINT
GO
Take Transactional log backup on the user database
BACKUP LOG CustomerXS TO DISK = N'M:\MSSQL\Backup\MSSQLSERVER\XS and RT\XS_Movement.trn' WITH COMPRESSION GO

The transaction log for database 'Test_db' is full due to 'LOG_BACKUP'

My dear All,
Came up with another issue:
App team is pushing the data from one Prod1 server 'test_1db' to another Prod2 server 'User_db' through a job, here while pushing the data after some duration job is failing and throwing the following error
'Error: 9002, Severity: 17, State: 2.'The transaction log for database 'User_db' is full due to 'LOG_BACKUP'''.
On Prod2 server 'User_db' log is having enough space 400gb on drive and growth is 250mb. I really confused that why job is failing as there is lot of space available. Kindly guide me to troubleshoot the issue as this issue is occuring from more than
1 week. Kindly refer the screenshot for the same.
Environment: SQL Server 2012 with sp1 Ent-edition. and log backup duration is every 15 mints and there is no High availability between the servers.
Note: Changing to simple recovery model may resolve but App team is required to run in Full recovery model as they need of log backups.
Thanks in advance,
Nagesh
Nagesh

Dear V,
Thanks for the susggestions.
I have followed some steps to resolve the issue, as of now my jobs are working without issue.
Steps:
Generating log backup for every 5 minutes
Increased the growth 500mb to unrestricted.
Once whole job completed we are shrinking the log file.
Nagesh

The transaction log for database 'SharePoint_Config' is full

Hi all ,
I am very new to sharepoint. when i tried to remove a wsp file from central administration i got the message like
The transaction log for database 'SharePoint_Config' is full. To find out why space in the log cannot
be reused, see the log_reuse_wait_desc column in sys.databases.
Can anybody help me to solve this please. I saw one solution in net like this but i don't know how to do this. Can anybody help me how to do these steps please.
1.
Take the configuration database offline and detach it
2.
Copy the current MDF to a new location (to be used as a way of recovering the database if needed)
3.
Put the database back on-line, reattach it and then put it within simple mode (from full), with an aim of this stopping the database from
increasing in size
4.
Shrink the database and recover log space
5.
Should the shrinking fail, we'd look at detaching the database, making a sideways copy of the log file to another database
6.
We would then reattach the database, which should generate a new log file
Thank you

Hi Soumya,
I don't have any dba resource. And it is not a lab environment. It's Corporate environment.
Thanks alot for ur quick reply.
I normally don't just come onto the threads and tell people that they need a consultant, but you might want to look at getting a consultant to help make sure that your SharePoint environment is health and can be restored in the event of a server failure.
Based on the problem that you have described it might not be recoverable, or at least it might not be as recoverable as you want it to be.
At the very least you'll want to watch this video of my session at TechEd 2014 which talks about backups and how to set them up.
http://channel9.msdn.com/events/TechEd/NorthAmerica/2014/DBI-B214#fbid=
Thank You,
Denny Cherry

The transaction log for database 'mydatabase' is full. To find out why space in the log cannot be reused, see the log_reuse_wait

Every time I get this error, at different points of testing inserts and deletions on my table:
The transaction log for database 'mydatabase' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
Why do I keep getting this? All I'm doing is deleting several hundred thousand records and inserting them into a couple of tables. i shouldn't have to truncate my log every time or my application bombs out!
sys.databases only gives me this info for log_reuse_wait_desc which does nothing for me:
LOG_BACKUP

sp_helpdb BizTalkDTADb
ALTER DATABASE BiztalkDTADb
SET RECOVERY SIMPLE;
GO
DBCC SHRINKFILE (BiztalkDTADb_log, 1);
GO
sp_helpdb BizTalkDTADb
GO
ALTER DATABASE BiztalkDTADb
SET RECOVERY FULL
GO

The transaction log for database 'BizTalkMsgBoxDb' is full.

Hi All,
We are getting the following error continously in the event viewer of our UAT servers. I checked the jobs and all the backup jobs were failing on the step to backup the transaction log file and were giving the same error. Our DBA's cleaned the message box manually and backed up the DB but still after some time the jobs starts failing and this error is logged in the event viewer.
The transaction log for database 'BizTalkMsgBoxDb' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases".
Thanks,
Abdul Rafay
http://abdulrafaysbiztalk.wordpress.com/
Please mark this answer if it helps

Putting the database into simple recovery mode and shrinking the log file isn't going to help: it'll just grow again, it will probably fragment across the disk thereby impacting performance and, eventually, it will fill up again for the same reason
as before. Plus you put yourself in a very vulnerable position for disaster recovery if you change the recovery mode of the database: and that's before we've addressed the distributed transaction aspect of the BizTalkDatabases.
First, make sure you're backing up the log file using the BizTalk job Backup BizTalk Server (BizTalkMgmtDb). It might be that the log hasn't been backed up and is full of transactions: and, eventually, it will run out of space. Configuration
instructions at this link:
http://msdn.microsoft.com/en-us/library/aa546765(v=bts.70).aspx Your DBA needs to get the backup job running properly rather than panicking!
If this is running properly, and backing up (which was the case for me) and the log file is still full, run the following query:
SELECT Name, log_reuse_wait_desc
FROM sys.databases
This will tell you why the log file isn't properly clearing down and why it cannot use the space inside. When I had this issue, it was due to an active transaction.
I checked for open transactions on the server using this query:
SELECT
s_tst.[session_id],
s_es
.[login_name]
AS [Login Name],
DB_NAME
(s_tdt.database_id)
AS [Database],
s_tdt
.[database_transaction_begin_time]
AS [Begin Time],
s_tdt
.[database_transaction_log_record_count]
AS [Log Records],
s_tdt
.[database_transaction_log_bytes_used]
AS [Log Bytes],
s_tdt
.[database_transaction_log_bytes_reserved]
AS [Log Rsvd],
s_est
.[text]
AS [Last T-SQL Text],
s_eqp
.[query_plan]
AS [Last Plan]
FROM
sys.dm_tran_database_transactions
s_tdt
JOIN
sys.dm_tran_session_transactions
s_tst
ON s_tst.[transaction_id]
= s_tdt.[transaction_id]
JOIN
sys.[dm_exec_sessions]
s_es
ON s_es.[session_id]
= s_tst.[session_id]
JOIN
sys.dm_exec_connections
s_ec
ON s_ec.[session_id]
= s_tst.[session_id]
LEFT
OUTER
JOIN
sys.dm_exec_requests
s_er
ON s_er.[session_id]
= s_tst.[session_id]
CROSS
APPLY
sys.dm_exec_sql_text
(s_ec.[most_recent_sql_handle])
AS s_est
OUTER
APPLY
sys.dm_exec_query_plan
(s_er.[plan_handle])
AS s_eqp
ORDER
BY [Begin Time]
ASC;
GO
And this told me the spid of the process with an open transaction on BizTalkMsgBoxDB (in my case, this was something that had been open for several days). I killed the transaction using KILL spid, where spid is an integer. Then I ran the BizTalk
Database Backup job again, and the log file backed up and cleared properly.
Incidentally, just putting the database into simple transaction mode would have emptied the log file: giving it lots of space to fill up again. But it doesn't deal with the root cause: why the backups were failing in the first place.

"The transaction log for database 'speakasiaonline' is full." I'm getting this message when I m trying to login to speakasia website and am unable to open it. Pl help.

The transaction log for database 'speakasiaonline' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

What does it return?
SELECT log_reuse_wait_desc FROM sys.databases WHERE database_id=2
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

The transaction log for database 'ECC' is full + ECC6.0 Installation Failur

Guyz,
my ecc6 installation failed after 8 hours run with following error log snippet...
exec sp_bindefault 'numc3_default','SOMG.MSGNO'
DbSlExecute: rc = 99
(SQL error 9002)
error message returned by DbSl:
The transaction log for database 'ECC' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
(DB) ERROR: DDL statement failed
(ALTER TABLE [SOMG] ADD CONSTRAINT [SOMG~0] PRIMARY KEY CLUSTERED ( [MANDT], [OBJTP], [OBJYR], [OBJNO] ) )
DbSlExecute: rc = 99
(SQL error 4902)
error message returned by DbSl:
Cannot find the object "SOMG" because it does not exist or you do not have permissions.
ECCLOG1 data file has got 25GB initial size and growth was restricted to 10% (PROPOSED BY SAPInst)...
i'm assuming this error was due to lack of growth space for ECCLOG1 datafile...am i right? if so how much should i allocate memory for this log ? or is there any workaround ?
thanks in advance

Kasu,
If SQL is complaining that the log file is full then the phase of the install that creates the SQL data/log files has already occurred (happens early in the install) and the install is importing programs, config and data into the db.
Look at the windows application event log for "Transaction log full" events to confirm.
To continue, in SQL Query analyzer try:
"Backup log [dbname] with truncate_only"
This will remove only inactive parts of the log and is safe when you don't require point-in-time recovery (which you don't during an install).
Then, go to the SQL Enterprise manager, choose the db in question and choose the shrink database function, choose to shrink only the transaction log file and the space made empty by the truncate will be removed from the file.
Change the recovery mode in SQL Server to "simple" so that the log file does not grow for the remainder of the install.
Make sure you change the recovery mode back to "full" after the install is complete.
Your transaction log appears to have filled the disk partition you have assigned to it.
25GB is huge for a transaction log and you would normally not see them grow this large if you are doing regular scheduled tlog backups (say every 30-60 minutes) because the log will truncate every time, but its not unusual to see one get big during an install, upgrade or when applying hotpacks.
Tim

The transaction log for database 'tempdb' is full

Hi,
When I try to login into SQL SERVER 2008, suddenly below error message is popped out.
ADDITIONAL INFORMATION:
The transaction log for database 'tempdb' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases (Microsoft SQL Server, Error: 9002)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.00.4000&EvtSrc=MSSQLServer&EvtID=9002&LinkId=20476
BUTTONS:
OK
I could restart SQL SERVER, but I need to identify cause of it. Any pointer on cause of this issue may help me. Thanks

What does it return?
SELECT log_reuse_wait_desc FROM sys.databases WHERE database_id=2
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

The transaction log for database 'WSS_Content' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Hi all,
Observing the below error in event logs once in every day at 3:30 AM on the on SQL Server Machine, it is being used for TFS 2010.
The transaction log for database 'WSS_Content' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
Kindly advice me here on what to do?
Thanks in advance

First thing to check is, what is happening at 3:30am to cause the log to fill up? Is there any maintenance tasks being run against the DB, such as index re-organizations or rebuilds? If so, take a look at what the job is doing, maybe it could
be tuned (ex: A Maintenance Plan with a rebuild indexes task will rebuild *every* index whether it needs it or not. Look at using something that checks how fragmented an index is, and then intelligently determines what, if anything, to do to that
index.)
Basically, the error is telling you that SQL is trying to do something in the DB, and has filled up the log (either because it's not getting backed up often enough, or the transaction in question is running *very* long, or your log is set to not auto-grow)
So, a couple possible solutions:
Increase the frequency of Transaction Log backups of WSS_Content (only works if the DB is in Full Recovery)
If you've got the disk space, turn on auto-growth for the TLog (or just manually grow it larger) {This will work for both Full and Simple Recovery}
It would be nice to know what's causing the space to not be re-used, but with this occuring at 3:30am, you'll either need to set up an Agent job to run around that time and record its results, or manually run something like "select log_reuse_wait_desc from
sys.databases where name = 'WSS_Content';" Me, I prefer to be soundly sleeping at 3:30am and would set up an Agent job to run from say about 3:00am to 3:45am once per minute (maybe even more frequently.)
DON'T shrink the log, though. SQL will idealy grow the log as large as it needs it (if autogrowth is enabled) and no more. If you shrink the file, SQL will just have to re-grow it later again, which can affect performance.
Jason A.

Restore transaction log for log shipping failed

restore transaction log failed and i get this error:
*** Error: An error occurred while processing the log for database 'XXX'. THe log block version is higher than this server allows.
can anyone help me, i don't have any idea how to solve it. Thank you

i'm using SQL 2008 R2.. currently the LSRestore job failed on standby server.
Date 4/23/2014 6:51:00 PM
Log Job History (LSRestore_)
Step ID 1
Server
Job Name LSRestore_
Step Name Log shipping restore log job step.
Duration 00:01:37
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
2014-04-23 18:52:37.60 *** Error: Could not apply log backup file 'T:\Tlog\20140417084500.trn' to secondary database 'DB'.(Microsoft.SqlServer.Management.LogShipping) ***
2014-04-23 18:52:37.60 *** Error: An error occurred while processing the log for database 'DB'. THe log block version is higher than this server allows.
RESTORE LOG is terminating abnormally.
Processed 0 pages for database 'DB', file 'DB_Data' on file 1.
Processed 17181 pages for database 'DB', file 'DB_Log' on file 1.(.Net SqlClient Data Provider) ***

Database select for update locks ADF

Hi,
When a user has initiated an update session in an adf application and locking is optimistic it will acquire a lock on table row using select for update no wait; . But when the user closes a tab the session would not be terminated. Now i know as HTTP is a stateless protocol, we can wait for the timeout and then the lock will be released using a session listener implementation. But if the user instead tries to log in again in a new tab and tries to edit the same record he will receive a message stating that another user already holds a lock on the record which is correct, but is misleading.
So can we rely on javascript for these scenarios that as soon as the user closes the tab the session should be terminated.
Here's a snippet
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/dojo/1.4/dojo/dojo.xd.js" ></script>
<script type="text/javascript">
var unLoad = function() {
    dojo.io.script.get({
    url:'http://127.0.0.1:7101/myapp/adfAuthentication?logout=true',
    timeout:15000,
dojo.addOnWindowUnload(unLoad);
</script>I know this might not work always as it depends on the fact that request might / might not be processed by the server.
Are there any alternate solutions and also reducing the session timeout is ruled out in my scenario.

Ramandeep,
So are there other alternatives or solutionsAlternatives or solutions to what, exactly? As Jobinesh has told you, as long as you use optimistic locking, ADF doesn't acquire database locks except in the context of a transaction that is going to be completed in the current HTTP request. You could obviously force ADF to deviate from this if you called "postChanges" during an HTTP request and leave the transaction hanging, but that would just be wrong in an optimistic locking scenario - the solution would be "don't do that."
John

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

You want to know the amount of space the transaction log for the Customer database is using. Which T-SQL command would you use?

You want to know the amount of space the transaction log for the Customer database is using. Which T-SQL command would you use?

Forced me to do a little research.
DBCC SQLPERF(logspace)
See also
http://stackoverflow.com/questions/198343/how-can-i-get-the-size-of-the-transaction-log-in-sql-2005-programmatically
For every expert, there is an equal and opposite expert. - Becker's Law
My blog
My TechNet articles

Logs for Database Locks

Similar Messages

Maybe you are looking for