Database log full

what are the option to free up the log?
1. kill spid filling up log.
2. backup the tran log - to disk or truncate only or no_log.
3. change the database to simple recovery mode, delete ldf file and then revert back to full recovery mode.
4. detach database, delete log file and reattach mdf again.
I am especially interested to know if the last two are commonly used in case dba is not able to free up log using other ways.
thanks.

First find why the log file is not truncating,
SELECT name,
log_reuse_wait
FROM sys.databases;
The recovery model dictates log behavior and whether the log will truncate on checkpoint or requires a transaction log backup, full and bulk logged recovery requires that you backup the log to keep the log size manageable, refer
here to the different kinds of backups and their affect on the T-Log.
The action you take will be dictated by the reason for the log not truncating. There are numerous reasons that the log does not truncate including replication, mirroring, transaction log backup, active transaction, etc. BACKUP LOG TRUNCATE ONLY
is no longer supported as it removes the ability to restore the database to a point in time.
The last two options are last ditch efforts to regain control of the log file size and should only be done after a full backup of the database is taken to insure that a viable backup is available.
David Dye My Blog

Similar Messages

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

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

SharePoint Content Database Log Truncation

Upon searching the web I found that DPM 2010 does not truncate the SQL log when it does the express full. Logs are truncated only when someone does a incremental (log backup)
Now For sharepoint content db, DPM does not do SQL transaction log incremental backup right?
So how are the content db logs truncated?
My recovery type is Full (we use mirroring). Should I backup the databases manually for the log truncation to occur?

They way this works is that DPM will back up the content database, and then back up the ldf file associated with it. You will see entries in the application event log corresponding to each action. The important ones to note will be:
Log Name:      Application
Source:        MSSQL$MIRRORA
Date:          4/28/2015 7:53:17 PM
Event ID:      18264
Task Category: Backup
Level:         Information
Computer:      CButchSQL1.domain.com
Description:
Database backed up. Database: WSS_Content_number4, creation date(time): 2015/04/24(19:20:20), pages dumped: 2282, first LSN: 173:445:49, last LSN: 173:465:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE:
{'{72BA7E1C-DB2D-4C40-B4A1-BDAF62B6E213}1'}). This is an informational message only. No user action is required.
This one of course indicates your content database was backed up. After that, you should see:
Log Name:      Application
Source:        MSSQL$MIRRORA
Date:          4/28/2015 7:53:25 PM
Event ID:      18265
Task Category: Backup
Level:         Information
Computer:      CButchSQL1.domain.com
Description:
Log was backed up. Database: WSS_Content_number4, creation date(time): 2015/04/24(19:20:20), first LSN: 173:163:1, last LSN: 173:472:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\Program Files\Microsoft
SQL Server\MSSQL10_50.MIRRORA\MSSQL\DATA\DPM_SQL_PROTECT\CBUTCHSQL1\MIRRORA\WSS_Content_number4_log.LDF\TempLog\TempLog.log'}). This is an informational message only. No user action is required.
DPM essentially does a temporary backup of the log to the temp location listed and immediately deletes it. Once the log file is backed up for a database in full recovery mode, SQL will then truncate the log automatically for you. If you see the
18265 event and the db is in full recovery mode, then SQL is failing somehow to truncate and should be investigated. If you see 18264 but then no 18265, then you should check to be sure this isn't DPM R2 UR5 protecting SP with SQL Always On backend as
we are investigating an issue where DPM is not properly backing up the log files. Right now, you can manually truncate those log files until a fix is created.
Thanks, Chris Butcher - MSFT This posting is provided "AS IS" with no warranties, and confers no rights

If your database in Full Recovery mode, can you use Bulk Insert Task to load data

If your database in Full Recovery mode, can you use Bulk Insert Task to load data

If your database in Full Recovery mode, can you use Bulk Insert Task to load data
Yes you can ofourse but dont be in idea that logging will be mininal. Loggign will be as per recovery model full. Every thing will be logged. If you are going to use bulk insert task you can consider switching recovery model to Bulk logged but you will not
have option to do point in time recovery.
PS: please dont create duplicate threads
If you read first Note section in below link it clearly states that yes logging will be full and you can use
http://technet.microsoft.com/en-us/library/ms191244(v=sql.105).aspx
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Sql backup detected corruption in database log

Unfortunately I am not a SQL Admin. I have moderate SQL experience at best.
I have four or five database in SQL 2005 that were the primary members of a mirror. The physical server (the one I am currently working on) was virtualized (P2V) then started as a virtual machine. Downtime was minimal. Maybe an hour or so
I believe.
Although I didn't check immediately after boot up, I have since noticed the mirror status is suspended. Attempts to resume fail. It appears my best bet is to backup the database, restore on the target, then recreate the mirror. The problem
is, attempts to run a Full backup of the database returns the following error on all the database I've tried to backup. After about 20% is says: SystemData.SqlClient.SqlError: BACKUP detected corruption in the database log. Check the errorlog for
more information. (Microsoft.SqlServer.Smo)
I've tried setting the recovery type to Simple, but that fails telling me the database is part of a mirror and to be honest I'm not sure setting to Simple is the best option.
As it stands, the mirror is broken and I can not perform a full backup.
Any suggestions on how to proceed are greatly appreciated.
Thank you.

Thank you Uri. Following are the results. Again, I'm not a SQL Admin but it appears this does not indicate errors?
DBCC results for 'TAIQRY'.
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
DBCC results for 'sys.sysrowsetcolumns'.
There are 546 rows in 5 pages for object "sys.sysrowsetcolumns".
DBCC results for 'sys.sysrowsets'.
There are 80 rows in 1 pages for object "sys.sysrowsets".
DBCC results for 'sysallocunits'.
There are 93 rows in 1 pages for object "sysallocunits".
DBCC results for 'sys.sysfiles1'.
There are 2 rows in 1 pages for object "sys.sysfiles1".
DBCC results for 'sys.syshobtcolumns'.
There are 546 rows in 5 pages for object "sys.syshobtcolumns".
DBCC results for 'sys.syshobts'.
There are 80 rows in 1 pages for object "sys.syshobts".
DBCC results for 'sys.sysftinds'.
There are 0 rows in 0 pages for object "sys.sysftinds".
DBCC results for 'sys.sysserefs'.
There are 93 rows in 1 pages for object "sys.sysserefs".
DBCC results for 'sys.sysowners'.
There are 15 rows in 1 pages for object "sys.sysowners".
DBCC results for 'sys.sysprivs'.
There are 135 rows in 1 pages for object "sys.sysprivs".
DBCC results for 'sys.sysschobjs'.
There are 86 rows in 1 pages for object "sys.sysschobjs".
DBCC results for 'sys.syscolpars'.
There are 579 rows in 10 pages for object "sys.syscolpars".
DBCC results for 'sys.sysnsobjs'.
There are 1 rows in 1 pages for object "sys.sysnsobjs".
DBCC results for 'sys.syscerts'.
There are 0 rows in 0 pages for object "sys.syscerts".
DBCC results for 'sys.sysxprops'.
There are 9 rows in 1 pages for object "sys.sysxprops".
DBCC results for 'sys.sysscalartypes'.
There are 27 rows in 1 pages for object "sys.sysscalartypes".
DBCC results for 'sys.systypedsubobjs'.
There are 0 rows in 0 pages for object "sys.systypedsubobjs".
DBCC results for 'sys.sysidxstats'.
There are 151 rows in 2 pages for object "sys.sysidxstats".
DBCC results for 'sys.sysiscols'.
There are 266 rows in 2 pages for object "sys.sysiscols".
DBCC results for 'sys.sysbinobjs'.
There are 23 rows in 1 pages for object "sys.sysbinobjs".
DBCC results for 'sys.sysobjvalues'.
There are 187 rows in 27 pages for object "sys.sysobjvalues".
DBCC results for 'sys.sysclsobjs'.
There are 14 rows in 1 pages for object "sys.sysclsobjs".
DBCC results for 'sys.sysrowsetrefs'.
There are 0 rows in 0 pages for object "sys.sysrowsetrefs".
DBCC results for 'sys.sysremsvcbinds'.
There are 0 rows in 0 pages for object "sys.sysremsvcbinds".
DBCC results for 'sys.sysxmitqueue'.
There are 0 rows in 0 pages for object "sys.sysxmitqueue".
DBCC results for 'sys.sysrts'.
There are 1 rows in 1 pages for object "sys.sysrts".
DBCC results for 'sys.sysconvgroup'.
There are 0 rows in 0 pages for object "sys.sysconvgroup".
DBCC results for 'sys.sysdesend'.
There are 0 rows in 0 pages for object "sys.sysdesend".
DBCC results for 'sys.sysdercv'.
There are 0 rows in 0 pages for object "sys.sysdercv".
DBCC results for 'sys.syssingleobjrefs'.
There are 140 rows in 1 pages for object "sys.syssingleobjrefs".
DBCC results for 'sys.sysmultiobjrefs'.
There are 131 rows in 1 pages for object "sys.sysmultiobjrefs".
DBCC results for 'sys.sysdbfiles'.
There are 2 rows in 1 pages for object "sys.sysdbfiles".
DBCC results for 'sys.sysguidrefs'.
There are 0 rows in 0 pages for object "sys.sysguidrefs".
DBCC results for 'sys.sysqnames'.
There are 91 rows in 1 pages for object "sys.sysqnames".
DBCC results for 'sys.sysxmlcomponent'.
There are 93 rows in 1 pages for object "sys.sysxmlcomponent".
DBCC results for 'sys.sysxmlfacet'.
There are 97 rows in 1 pages for object "sys.sysxmlfacet".
DBCC results for 'sys.sysxmlplacement'.
There are 17 rows in 1 pages for object "sys.sysxmlplacement".
DBCC results for 'sys.sysobjkeycrypts'.
There are 0 rows in 0 pages for object "sys.sysobjkeycrypts".
DBCC results for 'sys.sysasymkeys'.
There are 0 rows in 0 pages for object "sys.sysasymkeys".
DBCC results for 'sys.syssqlguides'.
There are 0 rows in 0 pages for object "sys.syssqlguides".
DBCC results for 'sys.sysbinsubobjs'.
There are 0 rows in 0 pages for object "sys.sysbinsubobjs".
DBCC results for 'sysdiagrams'.
There are 0 rows in 0 pages for object "sysdiagrams".
DBCC results for 'sys.queue_messages_1977058079'.
There are 0 rows in 0 pages for object "sys.queue_messages_1977058079".
DBCC results for 'sys.queue_messages_2009058193'.
There are 0 rows in 0 pages for object "sys.queue_messages_2009058193".
DBCC results for 'sys.queue_messages_2041058307'.
There are 0 rows in 0 pages for object "sys.queue_messages_2041058307".
CHECKDB found 0 allocation errors and 0 consistency errors in database 'TAIQRY'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

DB2 transaction log full

I am installing ECC6 for DB2 on RedHat AS4 platform. During import ABAP phase(running3, waiting1, completed15, total19), I have a strange error. System tell me that DB2 transaction log full. It seems unreasonable. System should know data volume during data import. I increased DB2 log file size when I got the error, and now, import ABAP is still in progress. Does anybody know why I got this error? Thanks so much.

Hello
there should be an SAPINST-Dialog similar to
"SAP System > Database Import"
where you can enter
Number of Parallel Jobs
In newer installations you started in "Default Mode" you need to review your summary dialog and mark the corresponding dialog for respecification.
Then you can specify your desired number of parallel Jobs
Best regards
Dirk

Database Log file Shrink information

Hello Team,
Database log file shrink information: Due to space problem
One of my database having 600 gb,under 600 gb log file having 260 gb, in this database we take full backup daily no log backup. If we shrink the log file any impact is happen?
We shrink the log file internally what will happen?
One of my database having 600 gb,log file having 260 gb, in this database we take full backup daily and every 15 min take log backup.
This is scenario we shrink the log file what will happen.

Hello,
You should not try to shrink the log file regularly, because is resource intensive, it takes a lot of time and it creates fragmentation on the disk storage.
If you don’t backup the log files of the databases (option 1) you don’t have the ability to restore to a point in time between backups full and differential. If
you don’t want to backup files then it makes sense to change the recovery model to simple.
Backing up the logs regularly minimize the risk of the logs getting filled and extending their size.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

[Forum FAQ] How do I restore the CDC enabled database backups (FULL + DIFF) while maintaining the CDC integrity

Question
Background: When restoring Full + DIFF backups of a Change Data Capture (CDC) enabled database to a different SQL server, the CDC integrity is not being maintained. We did RESTORE the databases with the KEEP_CDC option.
How do I successfully restore the CDC enabled database backups (FULL + DIFF) while maintaining the CDC integrity?
Answer
When restoring a CDC enabled database on a different machine that is running SQL Server, besides using use the KEEP_CDC option to retain all the CDC metadata, you also need to add Capture and Cleanup jobs.
In addition, as you want to restore FULL + DIFF backups of a CDC enabled database, you need to note that the KEEP_CDC and NoRecovery options are incompatible. Use the KEEP_CDC option only when you are completing the recovery. I made a test to display
the whole process that how to restore the CDC enabled database backups (FULL + DIFF) on a different machine.
Create a database named ’CDCTest’ in SQL Server 2012, then enable the CDC feature and take full+ differential backups of the database.
-- Create database CDCTest
CREATE DATABASE [CDCTest] ON PRIMARY
( NAME = N'CDCTest ', FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\ CDCTest.mdf' , SIZE = 5120KB ,
MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB )
LOG ON
( NAME = N'CDCTest _log', FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\ CDCTest _log.LDF' , SIZE = 3840KB ,
MAXSIZE = 2048GB , FILEGROWTH = 10%)
GO
use CDCTest;
go
-- creating table
create table Customer
custID int constraint PK_Employee primary key Identity(1,1)
,custName varchar(20)
--Enabling CDC on CDCTest database
USE CDCTest
GO
EXEC sys.sp_cdc_enable_db
--Enabling CDC on Customer table
USE CDCTest
GO
EXEC sys.sp_cdc_enable_table
@source_schema = N'dbo',
@source_name = N'Customer',
@role_name = NULL
GO
--Inserting values in customer table
insert into Customer values('Mike'),('Linda')
-- Querying CDC table to get the changes
select * from cdc.dbo_customer_CT
--Taking full database backup
backup database CDCTest to disk = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\ CDCTest.bak'
insert into Customer values('David'),('Jane')
-- Querying CDC table to get the changes
select * from cdc.dbo_customer_CT
--Taking differential database backup
BACKUP DATABASE CDCTest TO DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\ CDCTestdif.bak' WITH DIFFERENTIAL
GO
Restore Full backup of the ‘CDCTest’ database with using KEEP_CDC option in a different server that is running SQL Server 2014.
Use master
Go
--restore full database backup
restore database CDCTest from disk = 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\Backup\CDCTest.bak' with keep_cdc
Restore Diff backup of the ‘CDCTest’ database.
Restore Database CDCTest From Disk = 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\Backup\CDCTest.bak'
    With Move 'CDCTest' To 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\DATA\CDCTest.mdf',
        Move 'CDCTest _log' To 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\DATA\CDCTest _log.LDF',
        Replace,
        NoRecovery;
Go
--restore differential database backup
restore database CDCTest from disk = 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\Backup\CDCTestdif.bak' with keep_cdc
Add the Capture and Cleanup jobs in the CDCTest database.
--add the Capture and Cleanup jobs
Use CDCTest
exec sys.sp_cdc_add_job 'capture'
GO
exec sys.sp_cdc_add_job 'cleanup'
GO
insert into Customer values('TEST'),('TEST1')
-- Querying CDC table to get the changes
select * from cdc.dbo_customer_CT
Reference
Track Data Changes (SQL Server)
Restoring a SQL Server database that uses Change Data Capture
Applies to
SQL Server 2014
SQL Server 2012
SQL Server 2008 R2
SQL Server 2008
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Question
Background: When restoring Full + DIFF backups of a Change Data Capture (CDC) enabled database to a different SQL server, the CDC integrity is not being maintained. We did RESTORE the databases with the KEEP_CDC option.
How do I successfully restore the CDC enabled database backups (FULL + DIFF) while maintaining the CDC integrity?
Answer
When restoring a CDC enabled database on a different machine that is running SQL Server, besides using use the KEEP_CDC option to retain all the CDC metadata, you also need to add Capture and Cleanup jobs.
In addition, as you want to restore FULL + DIFF backups of a CDC enabled database, you need to note that the KEEP_CDC and NoRecovery options are incompatible. Use the KEEP_CDC option only when you are completing the recovery. I made a test to display
the whole process that how to restore the CDC enabled database backups (FULL + DIFF) on a different machine.
Create a database named ’CDCTest’ in SQL Server 2012, then enable the CDC feature and take full+ differential backups of the database.
-- Create database CDCTest
CREATE DATABASE [CDCTest] ON PRIMARY
( NAME = N'CDCTest ', FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\ CDCTest.mdf' , SIZE = 5120KB ,
MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB )
LOG ON
( NAME = N'CDCTest _log', FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\ CDCTest _log.LDF' , SIZE = 3840KB ,
MAXSIZE = 2048GB , FILEGROWTH = 10%)
GO
use CDCTest;
go
-- creating table
create table Customer
custID int constraint PK_Employee primary key Identity(1,1)
,custName varchar(20)
--Enabling CDC on CDCTest database
USE CDCTest
GO
EXEC sys.sp_cdc_enable_db
--Enabling CDC on Customer table
USE CDCTest
GO
EXEC sys.sp_cdc_enable_table
@source_schema = N'dbo',
@source_name = N'Customer',
@role_name = NULL
GO
--Inserting values in customer table
insert into Customer values('Mike'),('Linda')
-- Querying CDC table to get the changes
select * from cdc.dbo_customer_CT
--Taking full database backup
backup database CDCTest to disk = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\ CDCTest.bak'
insert into Customer values('David'),('Jane')
-- Querying CDC table to get the changes
select * from cdc.dbo_customer_CT
--Taking differential database backup
BACKUP DATABASE CDCTest TO DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\ CDCTestdif.bak' WITH DIFFERENTIAL
GO
Restore Full backup of the ‘CDCTest’ database with using KEEP_CDC option in a different server that is running SQL Server 2014.
Use master
Go
--restore full database backup
restore database CDCTest from disk = 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\Backup\CDCTest.bak' with keep_cdc
Restore Diff backup of the ‘CDCTest’ database.
Restore Database CDCTest From Disk = 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\Backup\CDCTest.bak'
    With Move 'CDCTest' To 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\DATA\CDCTest.mdf',
        Move 'CDCTest _log' To 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\DATA\CDCTest _log.LDF',
        Replace,
        NoRecovery;
Go
--restore differential database backup
restore database CDCTest from disk = 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\Backup\CDCTestdif.bak' with keep_cdc
Add the Capture and Cleanup jobs in the CDCTest database.
--add the Capture and Cleanup jobs
Use CDCTest
exec sys.sp_cdc_add_job 'capture'
GO
exec sys.sp_cdc_add_job 'cleanup'
GO
insert into Customer values('TEST'),('TEST1')
-- Querying CDC table to get the changes
select * from cdc.dbo_customer_CT
Reference
Track Data Changes (SQL Server)
Restoring a SQL Server database that uses Change Data Capture
Applies to
SQL Server 2014
SQL Server 2012
SQL Server 2008 R2
SQL Server 2008
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Error in db6conv failed due to transaction log full

Hi,
I have a huge problem with my production system.
I was executing db6conv v4.08 to convert a table to a new tablespace and it stopped due to a transaction log full.
Now I have this situation:
table soffcont1
db6conv: status: preliminary
I check the job db6conv_job_soffcont1 with status scheduled.
The problem is that when I want to execute this jobs it gives me an error:
Definition of job db6conv_job_soffcont1 is incomplete. Operation is not possible.
regards,
filipe vasconcelos

hi filipe,
i will follow up on this problem in you OSS message.
regards, frank

MySQL syntax error with TestStand 4.0 database logging

I had been using MS Access database to log results which worked fine but the access database is too limited. Switched to MySql. Database works fine and I can query it from Visual C++ and was able to create all my result tables fine from TestStand.
I get a syntax error when actually trying to log results and it has to do with either a missing quote or and extra quote, I can't quite tell. I thought I saw a post on this somewhere but can't find it now. Here is the complaint from TestStand:
An error occurred calling 'LogOneResult' in 'ITSDBLog' of 'zNI TestStand Database Logging'
An error occurred executing a statement.
Statement: UUT_RESULT.
[MySQL][ODBC 3.51 Driver][mysqld-5.0.45-community-nt]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DEFAULT VALUES' at line 1
Description: [MySQL][ODBC 3.51 Driver][mysqld-5.0.45-community-nt]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DEFAULT VALUES' at line 1
Number: -2147467259
NativeError: 1064
SQLState: 37000
Reported by: Microsoft OLE DB Provider for ODBC Drivers
Description: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
Number: -2147217887
NativeError: 0
SQLState: 37000
Reported by: Microsoft OLE DB Provider for ODBC Drivers
Source: TSDBLog
And here is all that appears in the MySql logfile:
INSERT INTO UUT_RESULT DEFAULT VALUES
070914
You can't see it here but the string is truncated after the word VALUES. The next line starts with the odd number.
Any ideas?
Thanks,
Bill Peters
BAE SYSTEMS

Sure. There were two bugs in the ini file that contains the default TS schemas (I think it was Default_Database_Options.ini or like that...).
Anyway the table description for STEP_NUMERICLIMIT had for it's command line INSERT INTO MEAS_NUMERICLIMIT. I guess TestStand looked at that and said hmm I better create that table too. Then later down the page when you try to create MEAS_NUMERICLIMIT it says the table already exists even though it is empty. The generate SQL button builds a bad file and then the database viewer creates a bad database. I would have to go into MySql and drop the database. I had to save the schema under a custom name, edit it read it back in, generate a new SQL file, but then it would still fail validation because the ini files don't get updated until you exit TestStand. So basically I did this process 3 times before I got it right.
It's wasn't a big deal but it's amazing how a little thing can cause a lot of work.
The second bug, I'm not certain was initially in the file or somehow got set on the fly. There was a random int statement at the very end of the SQL table description for UUT_RESULT. It was also in the schema INI file. Since the int had no name and occurred in a odd place, it created a syntax error in MySql. Same fix as above.
But like I said it's working great now. I like this approach because I serve it to the net with Apache and parse the database with simple PHP scripts.
Thanks,
Bill Peters
BAE SYSTEMS

FINANTIAL DOCUMENTS MISSING --- ORACLE LOGS FULL

Hi Experts,
9 documents are missing and when they were saved the system showed the message "update has been stopped". This was because of the Oracle LOGS (full).
When Oracle problem was solved the documents were not found in SM13 to recovered.
Any clue?
On the other hand If a have finantial documents in QAS how can I put it on PRD?
Regards.

Hi,
Schedule your backups according to the full backup time.
Do a test of full backup and fine the time that it takes to complete the full backup. You can include "plus archivelog" if you want your archive logs to be backed up along with the full backup. This is most preferred as this makes restoration easy too.
If your full backup takes, say, 4 hrs to complete and if you schedule your full backup at 00 00 hrs on your scheduler, then schedule the archive backups after 04 00 hrs. This will solve your problems with missing archive backups.
>> "But from RMAN specialist I heard that this may cause problems with full backup. During full backup also archive logs are backed up (at the start and end) so there might be a problem with accessing the file that is used by another process. And this may cause problem with full backup - which we want to avoid especially."
This will throw out errors if your input to full backup consists "delete input" for your archived logs, else the process will not have any problem and succeed.
Also when one or more of backups run concurrently, "ORA-00230: operation disallowed: snapshot control file enqueue unavailable" error may occur but this is rare case.
Thank you!!

Change the database log on parameters in the run time with CR10 Delphi2007?

Hi,
I'm using crystal report 10 and Crystal VCL for Delphi. How can I change the database log on parameters in the run time?

You have to use the ConnectBuffer. See [this|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes.do] note for details.
Also, consider searching the notes database:
https://www.sdn.sap.com/irj/scn/advancedsearch?cat=sdn_ossnotes&query=&adv=true
The search; VCL database crystal, returns a number of notes that may be of use.
Ludek

How to create a database with full import

Any other way to create a database without using below steps :
1)create database
2)use show=y and then create all the tablespace
3)and last imp full=y and ignore=y

i used following option to create a database from full exp
1)create database (sample database with same DBname on other server)
2)use show=y and then create all the tablespace
3)and last imp full=y and ignore=y
I just wanted to know is there any other way to create the Db with imp option without creating all the tablespace.

Turn database logging on

hello all,
turn database logging on , - FRA configured, what i have to do?
1) can i go mount status and alter database in archivelog mode and then start the database?
or anything else like logging vs nologging, just confused

Hi
you can enable archivelog mode and force logging mode (for dataguard, streams,...).
ALTER DATABASE FORCE LOGGING;
or
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
you find a lot of infos in the oracle dok.
In which context do you ask this question?
HTH

Database log full

Similar Messages

Maybe you are looking for