Client Deletion, Transaction log getting full.

Hi Gurus,
We are trying to delete a client by running:
clientremove
client = 200 (*200 being the client we want to remove)
select *
The transaction log disk space allocated is 50GB, it is getting full (in simple mode) and client deletion never completes. The size of the table it is accessing is 86 GB, and i think 200 client will be occupying around 40-45GB. Client 200 has 15.5 million rows in the table.
I am i giving proper command ?is there any explicit commit i can include or any workaround for deleting the client and not hammer the log file.
Thanks guys
Edited by: SAP_SQLDBA on Jan 22, 2010 6:51 PM

Hi,
Backup the active transaction log file and Shrink the file directly.
Please refer the following SAP Notes to get more information.
[ Note 625546 - Size of transaction log file is too big|https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=625546]
[ Note 421644 - SQL error 9002: The transaction log is full|https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=421644]
Which version of SQL Server u are using ? SP Level ?
Frequently perform Transaction Log backup (BACKUP TRANS) to remove inactive space within the Transaction Log Files.
Please refer [Note 307911 - Transaction Log Filling Up in SQL Server 7.0|https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=307911] to get more information about the reasons for such kind of situation.
Regards,
Bhavik G. Shroff

Similar Messages

Keep getting errors from application log that indicates transaction log is full but it has plenty of space

Dealing with a 4rd party application that inserts into its log table, but watching sql profiler i see a ton of the same traffic. Its trying to insert into the table, but generates an error that mentions the transaction log for that DB is full.
Well, earlier I had reset the recovery mode to simple, from full since this is a test system and dont really care about recovery.
So the message mentions to check the log_reuse_wait_desc column in sys.databases and there the value is 'CHECKPOINT'. At least at that point in time.
There is plenty of space in the transaction log and the physical disk has plenty of space as well.
What could be causing the error that seems to suggest the transaction log is full, when in fact it is not?

What is the setup for autogrowth on the log file?
Transaction log shrink:
http://www.sqlusa.com/bestpractices2005/shrinklog/
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

O10g se db install - application log gets full

Hi
I have installed o10g se db release 10.1.0.2 on windows server. (AMD Athlon 1.3GHz, 512 MBy RAM, windows 2000 server, sp4).
After installation the application log gets full with the error message:
Source: Perflib
Description:
The Open Procedure for service "Nbf" in DLL "C:\WINNT\system32\perfctrs.dll" failed. Performance data for this service will not be available. Status code returned is data DWORD 0.
Does anyone know what is the cause an how to solve the problem.
Regards, Petr

Matt,
I am glad (well not glad, it sucks but I'm glad I'm not alone) to hear you are experiencing the same thing. I have literally tried everything to get this to work. I even took a brand new laptop out of the box and Adobe was the only thing I installed. I can usually follow other posts and fix issues but I am stumped and WAY aggrivated. I love the concept as does my editing team but I'm in charge of installing and updating 5 PC's and my team is now aggrivated that they can't get what they need to do their jobs. Even if you download the trials, you don't get everything you need for the whole cloud process. Not to mention we all need updates badly and really need to start using Edge Animate.

How to delete Transaction Logs in SQL database

Hi,
Can any one explain me the process how to delete the transcation logs in SQL database.
Thanks
Sunil

Sunil,
Yes you can take online backup in MS SQL server.
The transaction log files contain information about all changes made to the database. The log files are necessary components of the database and may never be deleted. Why you want to delete it?
I am taking any backup, do i need to turn off the SAP server that is running at the moment or can i take it online
There are three main types of SQL Server Backup: Full Database Backup, Differential Database Backup and Transaction Log Backup. All these backups can be made when the database is online and do not require you to stop the SAP system.
Check below link for details
http://help.sap.com/erp2005_ehp_04/helpdata/EN/89/68807c8c984855a08b60f14b742ced/frameset.htm
Thanks
Sushil

The transaction log is full

Hi guys, I made a backup, I shrinked the log file but I still have this error when I try to delete a huge table
The transaction log for database 'Reporting' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
My set for the log is Autogrowt 10% until 6000mb. My backup state is simple recovery..
Any advice?
Thanks

If you need to delete the only part of the data and its part is huge ,use the below statement to keep the log in reasonable size
WHILE 1 = 1
BEGIN
DELETE TOP (500000)
FROM tbl;
IF @@ROWCOUNT < 500000 BREAK;
END
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

Content database transaction log is full

Hi guys,
i am facing some very serious issues right here, SharePoint content can't be updated because the transaction log drive for the logs is full. the following message is displayed in the event viewer
'The transaction for database wss_content_guid is full. To find out why space can't be reused see the log_reuse_wait_desc column in sys.databases'
Pls help

Hi,
The recommended way to truncate the transaction log if you are using a full recovery model is to back up the log. SQL Server 2005 automatically truncates the inactive parts of the transaction log when you back up the log. It is also recommended that you pre-grow the transaction log to avoid auto-growing the log. For more information about growing the transaction log, see Managing the Size of the Transaction Log File (http://go.microsoft.com/fwlink/?LinkId=124882). For more information about using a full recovery model, see Backup Under the Full Recovery Model (http://go.microsoft.com/fwlink/?LinkId=127985). For more information about using a simple recovery model, see Backup Under the Simple Recovery Model (http://go.microsoft.com/fwlink/?LinkId=127987).
We do not recommend that you manually shrink the transaction log size or manually truncate the log by using the Truncate method.
Transaction logs are also automatically backed up when you back up the farm, Web application, or databases by using either the SharePoint Central Administration Web site or the Stsadm command-line tool. For more information about the Stsadm command-line tool, see Backup: Stsadm operation (Windows SharePoint Services).
So I would suggest you backing up SharePoint by either the SharePoint Central Administration Web site or the Stsadm command-line tool.
For more information about Best Practice on Backups, please refer to the following articles:
Best Practice on Backups
http://blogs.msdn.com/joelo/archive/2007/07/09/best-practice-on-backups.aspx
Back up logs (Windows SharePoint Services 3.0)
http://technet.microsoft.com/en-us/library/cc811601.aspx
Hope this helps.
Rock Wang
Rock Wang– MSFT

Delete transaction log file

Hi,
I have three T-log files in my database, Now I want to delete 2 Transaction log files.
Can I do the below action:
1. dbcc shrinkfile(log1,truncateonly)
2 dbcc shrinkfile(log2,truncateonly)
2. Then remove the file using command or SSMS.
Regards

Hi Satheesh,
What about this:
Can I use the below procedure:
dbcc shrinkfile(LOG2,emptyfile)
dbcc shrinkfile (LOG3,emptyfile)
alter database PRT remove file LOG2
alter database PRT remove file LOG3
Note: I have already LOG1 as my primary logfile existing there, I want to remove only secondary logfiles
Regards

800 client deleted how to get it back

while doing ale-idoc in ides 4.7, i have deleted the 800 client from tcode-scc4. will i have to re install sap again? if there is any alternative steps to get back the '800' client again, pls tell me the steps.

go to change mode and create an entry for 800
Thanks
Bala Duvvuri

CV_HOME/cv/log getting full

Hello,
We have installed a RAC 11.2.0.1 on two nodes and we have observed a lot of log files at CV_HOME/cv/log. From the doc, this is the directory that will collect traces in case you run cluster verify with SRVM_TRACE=TRUE. The logs are generated and rotated every 5 minutes.
-rw-r----- 1 oracle ci 130746 Jan 14 20:13 cvutrace.log.0_20110114201611
-rw-r----- 1 oracle ci 59616 Jan 14 20:16 cvutrace.log.0_20110114201809
-rw-r----- 1 oracle ci 130770 Jan 14 20:18 cvutrace.log.0_20110114202112
-rw-r----- 1 oracle ci 59602 Jan 14 20:21 cvutrace.log.0_20110114202309
-rw-r----- 1 oracle ci 130756 Jan 14 20:23 cvutrace.log.0_20110114202612
-rw-r----- 1 oracle ci 59602 Jan 14 20:26 cvutrace.log.0_20110114202808
Has someone observed similar behaviour, who is generating them? It doesnt look to me to come from a database job or an operating system cron.
Thanks for your replies!

Hi,
Check this note...This will solve our problem.
*Large Number of Trace Files Generated Every 5 min Under $ORACLE_BASE/grid/cv/log/ [ID 1192676.1]*
Regards,
Levi Pereira

Update deactivated when DB2 transaction logs fill.

Hi All,
We are running SAP on DB2 Version9 on AIX platform.
We notirced that when transaction logs get full, the Update workprocess gets deactivated. This happens in any usage type that we have.. SRM, ECC , BI.
In the workprocess log we find this
C &+ ABAP location info 'SAPLSNR3', 2480
C &+ SAP user 'P1245690', transaction code 'WRF_WSOA2'
C &+
C *** ERROR in DB6Execute[dbdb6.c, 4556] (END)
B ***LOG BYL=> DBQ action required because of database error [dbsh#2 @ 1100] [dbsh 1100 ]
B SQL code: -964, SQL text: SQL0964C The transaction log for the database is full. SQLSTATE=57011 row=1
M ThIVBChangeState: update deactivated
M ***LOG R0R=> ThIVBChangeState, update deactivated () [thxxvb.c 11442]
M
M Sun Aug 8 08:30:44 2010
M *** ERROR => ThVBCheckCommit: reject bad ROLLBACK [thxxvb.c 13471]
A
A Sun Aug 8 08:57:56 2010
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
I have never heard of Update being deactivated for transaction log full at DB level. Update can be held up butwill it get deactivated.
Is it possible that update gets deactivated if it not able to post the tranaction data in DB?
Please let me know your ideas on this and how we can prevent this update from deactivating.
Thanks and REgards,
Raghavan

Hi,
If you search for "SQL0964C The transaction log for the database is full" then some of solutions ask for to execute the below mentioned steps :-
Use the following procedure to increase the size of the DB2 transaction log (logfilsiz):
1. Determine the current log file size setting by issuing the command:
su - <db2instance>
db2 list db directory # to list the database name
db2 connect to <databaseName>
db2 get db config for <databaseName> and check LOGFILSIZ parameter.
A sample output given from my test system :-
Log file size (4KB) (LOGFILSIZ) = 16380
Number of primary log files (LOGPRIMARY) = 20
Number of secondary log files (LOGSECOND) = 40
Changed path to log files (NEWLOGPATH) =
Path to log files = /db2/<dataname>/log_dir/NODE0000/
Overflow log path (OVERFLOWLOGPATH) =
Mirror log path (MIRRORLOGPATH) =
First active log file =
Block log on disk full (BLK_LOG_DSK_FUL) = YES
Percent max primary log space by transaction (MAX_LOG) = 0
Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0
2. Increase the size of the log file size setting by issuing the command:
db2 UPDATE db cfg for <databaseName> using LOGFILSIZ <new_value>
Example:
db2 UPDATE db cfg for <databaseName> using LOGFILSIZ 5000
3. Stop the ibmslapd process.
4. Issue the commands:
db2 force applications all
db2stop force
5. Restart ibmslapd process.
Once the db issue is resolved then your update work process must be running fine.

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

Cancel the query which uses full transaction log file

Hi,
We have reindexing job to run every week sunday. During the last run, the transaction log got full and the subsequent transactions to the database got errorred out stating 'Transaction log is full'. I want to restrict the utilization of the log file, that
is, when the reindexing job reaches the utilization of the log file to a certain threshold automatically the job should get cancelled. Is there any way to get it.

Hi,
We have reindexing job to run every week sunday. During the last run, the transaction log got full and the subsequent transactions to the database got errorred out stating 'Transaction log is full'. I want to restrict the utilization of the log file, that
is, when the reindexing job reaches the utilization of the log file to a certain threshold automatically the job should get cancelled. Is there any way to get it.
Hello,
Instead of Putting limit on trn log it would be good to find out cause causing high utilization.Even if you find that your log is growing because of some transaction it would be a blunder to rollback its little easy to do it for Index rebuild but if you
cancel for some delete operation you would end up in mess.Please don't create a program to delete or kill running operation.
You can create custom job for alert for trn log file growth.That would be good.
From 2008 onwards Index rebuild is fully logged so sometimes it causes trn log issue.To solve this either you run index rebuild for specific tables or for selective tables.
Other option is widely accepted Ola Hallengren script for index rebuild.I suggest you try this
http://ola.hallengren.com/
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

MSSQL Transaction Log full

Hi,
whenever I am ruuning Client copy it got stuck because of Trnsactional log getting full.Then I have to take backup of Transactional log & then again start client copy.
For a client copy it takes around 48 hour & I am facing this problem 10 times.
Please let me know if there can be some solution to avoid this situation.Aslo please suggest procedure to avoid it.
we are using MSSQL 2005 databsae & Windows 2003 server.
Cheers
Santosh

Yes, I would highly recommend running transaction log backups every 15 minutes at least. Especiallly if you are creating 10GB of transaction data every day.
This client copy issue may very well be a lifesaver for you in the future.
Re-evaluate your backup/recovery scenario.
Here's a little bit of basic info from my blog:
http://joeybear23.blogspot.com/2008/04/sap-backuprecovery-planning.html

Transaction log full

Transaction log is full in production system ,when i was tried login into sap system it show the error message 'SNAP_NO_NEW_ENTRIES'.
our system is db2 and AIX ,can any body hlep us step by step procedure for reslove the issue .
For best answer will reward.
Thanks
Imran khan

you have to increase the sum of the logs in order to enlarge the database log...plz do not forget that the log must fit the underlying file system, eg. /db2/<SID>/dir_log..so you might have to increase this as well using SMITTY...
(DB6) [IBM][CLI Driver][DB2/AIX64] SQL0964C The transaction log for the database is full. SQLSTATE=57011
[root] > su - db2<sid>
1> db2 get db cfg for <SID> | grep -i logfilsiz
Log file size (4KB) (LOGFILSIZ) = 16380
2> db2 get db cfg for <SID> | grep -i logprimary
Number of primary log files (LOGPRIMARY) = 20
3> db2 get db cfg for <SID> | grep -i logsecond
Number of secondary log files (LOGSECOND) = 40
so we have log file of max. 16.380 * 4.096 * 60 = 4.025.548.800 bytes (about 4 gb)...this needs to be increased by increasing either LOGPRIMARY and/or LOGSECONDARY...(assuming that your logfile size is 16kb...query db2 for your size!)
4> db2 update db cfg for <SID> using logsecond 80 immediate
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
SQL1363W One or more of the parameters submitted for immediate modification
were not changed dynamically. For these configuration parameters, all
applications must disconnect from this database before the changes become
effective.
5> db2 get db cfg for <SID> | grep -i logprimary
Number of primary log files (LOGPRIMARY) = 20
6> db2 get db cfg for <SID> | grep -i logsecond
Number of secondary log files (LOGSECOND) = 80
7> db2stop
02/20/2007 09:17:12 0 0 SQL1064N DB2STOP processing was successful.
SQL1064N DB2STOP processing was successful.
8> db2start
02/20/2007 09:17:19 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
-> plz keep in mind that the sap system needs to be down when re-starting db2...
check via snapshot:
9> db2 get snapshot for database on <SID>
Log space available to the database (Bytes)= 2353114756 (= 2.353 MB)
Log space used by the database (Bytes) = 4329925244 (= 4.329 MB)
Maximum secondary log space used (Bytes) = 2993640963
Maximum total log space used (Bytes) = 4330248963
Secondary logs allocated currently = 46
Appl id holding the oldest transaction = 9
so now our log is about 6.5 gb ...see sapnote 25.351 for details...
GreetZ, AH

Question about full backup and Transaction Log file

I had a query will taking full backup daily won't allow my log file to grow as after taking the full backup I still see the some of the VLF in status 2. It went away when I manually took the backup of log file. I am bit confused shall I
perform backup of transaction log and full database backup daily to avoid such things in future also until I run shrinkfile the storage space from server won't get reduced right.

yes, full backup does not clear log file only log backup does. once the log backup is taken, it will set the inactive vlfs in the log file to 0.
you should perform log backup as the per your business SLA in data loss.
Go ahead and ask this to yourself:
If a disaster strikes and your database server is lost and your only option is restore it from backup,
how much data loss can your business handle??
the answer to this question is how frequently your log backup should be?
if the answer is 10 mins, you should have log backups every 10 mins atleast.
if the answer is 30 mins, you should have log backups every 30 mins atleast.
if the answer is 90 mins, you should have log backups every 90 mins atleast.
so, when you restore, you will restore latest fullbackup+differential(latest one taken after restored fullback)
and all the logbackups taken since the latest(restored full or differential backup).
there several resources on web,inculding youtube videos, that explain these concepts clearly.i advice you to look at them.
to release the file space to OS, you should the shrink the file. log file shrink happens from the end upto the point it reaches an active vlf.
if there are no inactive vlf's in the end,despite how many inactive vlf's the log file has in the begining, the log file is not shrinkable
Hope it Helps!!

Client Deletion, Transaction log getting full.

Similar Messages

Maybe you are looking for