SQL0964C  The transaction log for the database is full

Hi,
i am planning to do QAS refresh from PRD system using Client export\import method. i have done export in PRD and the same has been moved to QAS then started imported.
DB Size:160gb
DB:DB2 9.7
os: windows 2008.
I facing SQL0964C  The transaction log for the database is full issue while client import and regarding this i have raised incident to SAP then they replied to increase some parameter like(LOGPRIMARY,LOGSECOND,LOGFILSIZ) temporarily and revert them back after the import. Based on that i have increased from as below mentioned calculation.
the filesystem size of /db2/<SID>/log_dir should be greater than LOGFILSIZ*4*(Sum of LOGPRIMARY+LOGSECONDARY) KB
From:
Log file size (4KB)                         (LOGFILSIZ) = 60000
Number of primary log files                (LOGPRIMARY) = 50
Number of secondary log files               (LOGSECOND) = 100
Total drive space required: 33GB
To:
Log file size (4KB)                         (LOGFILSIZ) = 70000
Number of primary log files                (LOGPRIMARY) = 60
Number of secondary log files               (LOGSECOND) = 120
Total drive space required: 47GB
But still facing the same issue. Please help me to resolve the ASAP.
Last error TP log details:
3 ETW674Xstart import of "R3TRTABUFAGLFLEX08" ...
4 ETW000   1 entry from FAGLFLEX08 (210) deleted.
4 ETW000   1 entry for FAGLFLEX08 inserted (210*).
4 ETW675 end import of "R3TRTABUFAGLFLEX08".
3 ETW674Xstart import of "R3TRTABUFAGLFLEXA" ...
4 ETW000  [     dev trc,00000]  Fri Jun 27 02:20:21 2014                                             -774509399  65811.628079
4 ETW000  [     dev trc,00000]  *** ERROR in DB6Execute[dbdb6.c, 4980] CON = 0 (BEGIN)                    85  65811.628164
4 ETW000  [     dev trc,00000]  &+     DbSlModifyDB6( SQLExecute ): [IBM][CLI Driver][DB2/NT64] SQL0964C  The transaction log for the database is full. 
4 ETW000                                                                                                  83  65811.628247
4 ETW000  [     dev trc,00000]  &+     SQLSTATE=57011 row=1                                                                                             
4 ETW000                                                                                                  51  65811.628298
4 ETW000  [     dev trc,00000]  &+                                                                                                                      
4 ETW000                                                                                                  67  65811.628365
4 ETW000  [     dev trc,00000]  &+     DELETE FROM "FAGLFLEXA" WHERE "RCLNT" = ?                                                                        
4 ETW000                                                                                                  62  65811.628427
4 ETW000  [     dev trc,00000]  &+       cursor type=NO_HOLD, isolation=UR, cc_release=YES, optlevel=5, degree=1, op_type=8, reopt=0                    
4 ETW000                                                                                                  58  65811.628485
4 ETW000  [     dev trc,00000]  &+                                                                                                                      
4 ETW000                                                                                                  53  65811.628538
4 ETW000  [     dev trc,00000]  &+     Input SQLDA:                                                                                                     
4 ETW000                                                                                                  52  65811.628590
4 ETW000  [     dev trc,00000]  &+                        1 CT=WCHAR           T=VARCHAR         L=6     P=9     S=0   
4 ETW000                                                                                                  49  65811.628639
4 ETW000  [     dev trc,00000]  &+                                                                                                                      
4 ETW000                                                                                                  50  65811.628689
4 ETW000  [     dev trc,00000]  &+     Input data:                                                                                                      
4 ETW000                                                                                                  49  65811.628738
4 ETW000  [     dev trc,00000]  &+     row 1:             1 WCHAR           I=6       "210"               34  65811.628772
4 ETW000  [     dev trc,00000]  &+                                                                                                                      
4 ETW000                                                                                                  51  65811.628823
4 ETW000  [     dev trc,00000]  &+                                                                                                                      
4 ETW000                                                                                                  50  65811.628873
4 ETW000  [     dev trc,00000]  *** ERROR in DB6Execute[dbdb6.c, 4980] (END)                              27  65811.628900
4 ETW000  [    dbtran  ,00000]  ***LOG BY4=>sql error -964   performing DEL on table FAGLFLEXA                    
4 ETW000                                                                                                3428  65811.632328
4 ETW000  [    dbtran  ,00000]  ***LOG BY0=>SQL0964C  The transaction log for the database is full.  SQLSTATE=57011 row=1
4 ETW000                                                                                                  46  65811.632374
4 ETW000  [     dev trc,00000]  dbtran ERROR LOG (hdl_dbsl_error): DbSl 'DEL'                             59  65811.632433
4 ETW000                         RSLT: {dbsl=99, tran=1}
4 ETW000                         FHDR: {tab='FAGLFLEXA', fcode=194, mode=2, bpb=0, dbcnt=0, crsr=0,
4 ETW000                                hold=0, keep=0, xfer=0, pkg=0, upto=0, init:b=0,
4 ETW000                                init:p=0000000000000000, init:#=0, wa:p=0X00000000020290C0, wa:#=10000}
4 ETW000  [     dev trc,00000]  dbtran ERROR LOG (hdl_dbsl_error): DbSl 'DEL'                            126  65811.632559
4 ETW000                         STMT: {stmt:#=0, bndfld:#=1, prop=0, distinct=0,
4 ETW000                                fld:#=0, alias:p=0000000000000000, fupd:#=0, tab:#=1, where:#=2,
4 ETW000                                groupby:#=0, having:#=0, order:#=0, primary=0, hint:#=0}
4 ETW000                         CRSR: {tab='', id=0, hold=0, prop=0, max.in@0=1, fae:blk=0,
4 ETW000                                con:id=0, con:vndr=7, val=2,
4 ETW000                                key:#=3, xfer=0, xin:#=0, row:#=0, upto=0, wa:p=0X00000001421A3000}
2EETW125 SQL error "-964" during "-964" access: "SQL0964C  The transaction log for the database is full.  SQLSTATE=57011 row=1"
4 ETW690 COMMIT "14208" "-1"
4 ETW000  [     dev trc,00000]  *** ERROR in DB6Execute[dbdb6.c, 4980] CON = 0 (BEGIN)                 16208  65811.648767
4 ETW000  [     dev trc,00000]  &+     DbSlModifyDB6( SQLExecute ): [IBM][CLI Driver][DB2/NT64] SQL0964C  The transaction log for the database is full. 
4 ETW000                                                                                                  75  65811.648842
4 ETW000  [     dev trc,00000]  &+     SQLSTATE=57011 row=1                                                                                             
4 ETW000                                                                                                  52  65811.648894
4 ETW000  [     dev trc,00000]  &+                                                                                                                      
4 ETW000                                                                                                  51  65811.648945
4 ETW000  [     dev trc,00000]  &+     INSERT INTO DDLOG (SYSTEMID, TIMESTAMP, NBLENGTH, NOTEBOOK) VALUES (  ? , CHAR(   CURRENT TIMESTAMP - CURRENT TIME
4 ETW000                                                                                                  50  65811.648995
4 ETW000  [     dev trc,00000]  &+     ZONE   ), ?, ? )                                                                                                 
4 ETW000                                                                                                  49  65811.649044
4 ETW000  [     dev trc,00000]  &+       cursor type=NO_HOLD, isolation=UR, cc_release=YES, optlevel=5, degree=1, op_type=15, reopt=0                   
4 ETW000                                                                                                  55  65811.649099
4 ETW000  [     dev trc,00000]  &+                                                                                                                      
4 ETW000                                                                                                  49  65811.649148
4 ETW000  [     dev trc,00000]  &+     Input SQLDA:                                                                                                     
4 ETW000                                                                                                  50  65811.649198
4 ETW000  [     dev trc,00000]  &+                        1 CT=WCHAR           T=VARCHAR         L=44    P=66    S=0   
4 ETW000                                                                                                  47  65811.649245
4 ETW000  [     dev trc,00000]  &+                        2 CT=SHORT           T=SMALLINT        L=2     P=2     S=0   
4 ETW000                                                                                                  48  65811.649293
4 ETW000  [     dev trc,00000]  &+                        3 CT=BINARY          T=VARBINARY       L=32000 P=32000 S=0   
4 ETW000                                                                                                  47  65811.649340
4 ETW000  [     dev trc,00000]  &+                                                                                                                      
4 ETW000                                                                                                  50  65811.649390
4 ETW000  [     dev trc,00000]  &+     Input data:                                                                                                      
4 ETW000                                                                                                  49  65811.649439
4 ETW000  [     dev trc,00000]  &+     row 1:             1 WCHAR           I=14      "R3trans"           32  65811.649471
4 ETW000  [     dev trc,00000]  &+                        2 SHORT           I=2        12744              32  65811.649503
4 ETW000  [     dev trc,00000]  &+                        3 BINARY          I=12744   00600306003200300030003900300033003300310031003300320036003400390000...
4 ETW000                                                                                                  64  65811.649567
4 ETW000  [     dev trc,00000]  &+                                                                                                                      
4 ETW000                                                                                                  52  65811.649619
4 ETW000  [     dev trc,00000]  &+                                                                                                                      
4 ETW000                                                                                                  51  65811.649670
4 ETW000  [     dev trc,00000]  *** ERROR in DB6Execute[dbdb6.c, 4980] (END)                              28  65811.649698
4 ETW000  [    dbsyntsp,00000]  ***LOG BY4=>sql error -964   performing SEL on table DDLOG                36  65811.649734
4 ETW000  [    dbsyntsp,00000]  ***LOG BY0=>SQL0964C  The transaction log for the database is full.  SQLSTATE=57011 row=1
4 ETW000                                                                                                  46  65811.649780
4 ETW000  [    dbsync  ,00000]  ***LOG BZY=>unexpected return code 2          calling ins_ddlog           37  65811.649817
4 ETW000  [     dev trc,00000]  db_syflush (TRUE) failed                                                  26  65811.649843
4 ETW000  [     dev trc,00000]  db_con_commit received error 1024 in before-commit action, returning 8
4 ETW000                                                                                                  57  65811.649900
4 ETW000  [    dbeh.c  ,00000]  *** ERROR => missing return code handler                               1974  65811.651874
4 ETW000                         caller does not handle code 1024 from dblink#5[321]
4 ETW000                         ==> calling sap_dext to abort transaction
2EETW000 sap_dext called with msgnr "900":
2EETW125 SQL error "-964" during "-964" access: "SQL0964C  The transaction log for the database is full.  SQLSTATE=57011 row=1"
1 ETP154 MAIN IMPORT
1 ETP110 end date and time   : "20140627022021"
1 ETP111 exit code           : "12"
1 ETP199 ######################################
Regards,
Rajesh

Hi Babu,
I believe you should have taken a restart of your system if log primary are changed.  If so, then increase log primary to 120 and secondary to 80 provide size and space are enough.
Note 1293475 - DB6: Transaction Log Full
Note 1308895 - DB6: File System for Transaction Log is Full
Note: 495297 - DB6: Monitoring transaction log    
Regards,
Divyanshu

Similar Messages

  • 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

  • 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

  • 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 '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.

  • How to find the transaction code for the particular program or include

    Dear All,
    Please help me on this queary.
    1) How to find what is the transaction assigned for the particular Report
    2) How to find the particular include is used in which programs and also transaction codes
    I have one ZProgram that contains only includes no selection screen, I have to find where this program is used, in that one include is ther I would like to know in which program and in which transaction that is used,
    They have given ME9F, ME21N/22n, wheren this includle is calling.
    Please kinely help on this.
    Thanks and Regards,
    Muralikrishna

    HI
    1. you can find the transaction for your report by opening in se80. On the left side window it will show the transaction if there is any.
    2. to find in which programs particular inclue is called , just open include in se38 and press where used list icon. in the pop up window select programs.
    regards
    vijay
    reward points if helpful

  • Configure the Change Log for the activity

    Hi to all,
    I would like to know if it is possible to configure the "change log" for the activity.
    Thanks in advanced,
    Matte

    Carlos,
    Can you be more specific on the term 'Configure'.  Change log is automatically generated by SBO.  The only thing you can change is the numbers of Historical instances of the log
    Administration > System Initialization > General Settings.......Services Tab...History or Log Settings.  Be default it is 99 instances.
    Suda

  • How many calls are held in the call log for the iPhone 3g?

    How many calls are held in the call log for the iPhone 3g?

    Creating a separate CSQ is the way to do it. Keep in mind that depending on your error handling, a single request could still generate more than one call into the CSQ. You would want to look at the CCDR table for the call ID or write the ImplementationID into one of the Enterprise Data variables that gets stored to the DBA to act as a UID. 

Maybe you are looking for