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
Similar Messages
-
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,
RaghavanHi,
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. -
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 vasconceloshi filipe,
i will follow up on this problem in you OSS message.
regards, frank -
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 khanyou 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...
<b>(DB6) [IBM][CLI Driver][DB2/AIX64] SQL0964C The transaction log for the database is full. SQLSTATE=57011</b>
<i>[root] > su - db2<sid></i>
<i>1> db2 get db cfg for <SID> | grep -i logfilsiz</i>
Log file size (4KB) (LOGFILSIZ) = 16380
<i>2> db2 get db cfg for <SID> | grep -i logprimary</i>
Number of primary log files (LOGPRIMARY) = 20
<i>3> db2 get db cfg for <SID> | grep -i logsecond</i>
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!)
<i>4> db2 update db cfg for <SID> using logsecond 80 immediate</i>
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.
<i>5> db2 get db cfg for <SID> | grep -i logprimary</i>
Number of primary log files (LOGPRIMARY) = 20
<i>6> db2 get db cfg for <SID> | grep -i logsecond</i>
Number of secondary log files (LOGSECOND) = 80
<i>7> db2stop</i>
02/20/2007 09:17:12 0 0 SQL1064N DB2STOP processing was successful.
SQL1064N DB2STOP processing was successful.
<i>8> db2start</i>
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:
<i>9> db2 get snapshot for database on <SID></i>
<b>Log space available to the database (Bytes)= 2353114756 (= 2.353 MB)
Log space used by the database (Bytes) = 4329925244 (= 4.329 MB)</b>
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 ...<b>see sapnote 25.351 for details</b>...
GreetZ, AH -
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
SantoshYes, 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 -
DB2 Transaction log Problem after set db manuell to Rollforward
Hello,
I have a problem when set the db2 manuell in rollforward mode. After I set the command db2rfpen ON E35 my database (E35) is in rollforward mode.
Now I can see with command "db2 rollforward db E35 query status" the Last committed transaction
but the timestamp of the Last committed transaction is 2106-02-07-06.28.15.000000 UTC
but we do not have year 2106!!
did someone have similar issue or a solution for my problem??
Is it possible to manuell update the table via SQL? But I dont know which table i should update..
Thanks in advanced.
RobinHi,
following output of db2 get snapshot for all databases because db2 get snapshot for database E35 does not work..
there I think the timestamp is also ok. Thanks for your help!
regards
Robin
Database Snapshot
Database name = E35
Database path = /db2/E35/db2e35/NODE0000/SQL00001/MEMBER0000/
Input database alias =
Database status = Active
Catalog database partition number = 0
Catalog network node name = srvnetapp07
Operating system running at database server= LINUXAMD64
Location of the database = Local
First database connect timestamp = 08/11/2014 12:16:58.594371
Last reset timestamp =
Last backup timestamp = 08/08/2014 09:57:42.000000
Snapshot timestamp = 08/11/2014 12:17:46.494342
Number of automatic storage paths = 4
Automatic storage path = /db2/E35/sapdata1
Node number = 0
State = In Use
File system ID = 64782
Storage path free space (bytes) = 23376351232
File system used space (bytes) = 3045990400
File system total space (bytes) = 26422341632
Automatic storage path = /db2/E35/sapdata2
Node number = 0
State = In Use
File system ID = 64783
Storage path free space (bytes) = 23376351232
File system used space (bytes) = 3045990400
File system total space (bytes) = 26422341632
Automatic storage path = /db2/E35/sapdata3
Node number = 0
State = In Use
File system ID = 64784
Storage path free space (bytes) = 23376351232
File system used space (bytes) = 3045990400
File system total space (bytes) = 26422341632
Automatic storage path = /db2/E35/sapdata4
Node number = 0
State = In Use
File system ID = 64785
Storage path free space (bytes) = 23376351232
File system used space (bytes) = 3045990400
File system total space (bytes) = 26422341632
High water mark for connections = 13
Application connects = 9
Secondary connects total = 11
Applications connected currently = 1
Appls. executing in db manager currently = 0
Agents associated with applications = 11
Maximum agents associated with applications= 13
Maximum coordinating agents = 13
Number of Threshold Violations = 0
Locks held currently = 29
Lock waits = 2
Time database waited on locks (ms) = 56
Lock list memory in use (Bytes) = 77568
Deadlocks detected = 0
Lock escalations = 0
Exclusive lock escalations = 0
Agents currently waiting on locks = 0
Lock Timeouts = 0
Number of indoubt transactions = 0
Total Private Sort heap allocated = 0
Total Shared Sort heap allocated = 6
Shared Sort heap high water mark = 245
Post threshold sorts (shared memory) = 0
Total sorts = 2
Total sort time (ms) = 2
Sort overflows = 0
Active sorts = 0
Buffer pool data logical reads = 68507
Buffer pool data physical reads = 1312
Buffer pool temporary data logical reads = 0
Buffer pool temporary data physical reads = 0
Asynchronous pool data page reads = 899
Buffer pool data writes = 0
Asynchronous pool data page writes = 0
Buffer pool index logical reads = 52871
Buffer pool index physical reads = 449
Buffer pool temporary index logical reads = 0
Buffer pool temporary index physical reads = 0
Asynchronous pool index page reads = 0
Buffer pool index writes = 0
Asynchronous pool index page writes = 0
Buffer pool xda logical reads = 0
Buffer pool xda physical reads = 0
Buffer pool temporary xda logical reads = 0
Buffer pool temporary xda physical reads = 0
Buffer pool xda writes = 0
Asynchronous pool xda page reads = 0
Asynchronous pool xda page writes = 0
Total buffer pool read time (milliseconds) = 4912
Total buffer pool write time (milliseconds)= 0
Total elapsed asynchronous read time = 3219
Total elapsed asynchronous write time = 0
Asynchronous data read requests = 454
Asynchronous index read requests = 0
Asynchronous xda read requests = 0
No victim buffers available = 0
LSN Gap cleaner triggers = 0
Dirty page steal cleaner triggers = 0
Dirty page threshold cleaner triggers = 0
Time waited for prefetch (ms) = 982
Unread prefetch pages = 0
Direct reads = 986
Direct writes = 2
Direct read requests = 77
Direct write requests = 1
Direct reads elapsed time (ms) = 243
Direct write elapsed time (ms) = 0
Database files closed = 0
Host execution elapsed time = 5.785568
Commit statements attempted = 16
Rollback statements attempted = 2
Dynamic statements attempted = 6950
Static statements attempted = 23
Failed statement operations = 0
Select SQL statements executed = 6936
Xquery statements executed = 0
Update/Insert/Delete statements executed = 6
DDL statements executed = 0
Inactive stmt history memory usage (bytes) = 0
Internal automatic rebinds = 0
Internal rows deleted = 0
Internal rows inserted = 0
Internal rows updated = 0
Internal commits = 21
Internal rollbacks = 0
Internal rollbacks due to deadlock = 0
Number of MDC table blocks pending cleanup = 0
Rows deleted = 0
Rows inserted = 0
Rows updated = 13838
Rows selected = 13897
Rows read = 141752
Binds/precompiles attempted = 0
Log space available to the database (Bytes)= 333797877
Log space used by the database (Bytes) = 26523
Maximum secondary log space used (Bytes) = 0
Maximum total log space used (Bytes) = 37070
Secondary logs allocated currently = 0
Log pages read = 0
Log read time (sec.ns) = 0.000000000
Log pages written = 13
Log write time (sec.ns) = 0.006250000
Number write log IOs = 9
Number read log IOs = 0
Number partial page log IOs = 7
Number log buffer full = 0
Log data found in buffer = 0
Log to be redone for recovery (Bytes) = 26523
Log accounted for by dirty pages (Bytes) = 26523
Node number = 0
File number of first active log = 90
File number of last active log = 94
File number of current active log = 90
File number of log being archived = Not applicable
Package cache lookups = 6955
Package cache inserts = 20
Package cache overflows = 0
Package cache high water mark (Bytes) = 1026593
Application section lookups = 20824
Application section inserts = 29
Catalog cache lookups = 740
Catalog cache inserts = 55
Catalog cache overflows = 0
Catalog cache high water mark = 429098
Catalog cache statistics size = 0
Workspace Information
Number of hash joins = 4
Number of hash loops = 0
Number of hash join overflows = 0
Number of small hash join overflows = 0
Post threshold hash joins (shared memory) = 0
Active hash joins = 0
Number of OLAP functions = 0
Number of OLAP function overflows = 0
Active OLAP functions = 0
Statistic fabrications = 0
Synchronous runstats = 0
Asynchronous runstats = 0
Total statistic fabrication time (milliseconds) = 0
Total synchronous runstats time (milliseconds) = 0
Memory usage for database:
Node number = 0
Memory Pool Type = Backup/Restore/Util Heap
Current size (bytes) = 65536
High water mark (bytes) = 65536
Configured size (bytes) = 204800000
Node number = 0
Memory Pool Type = Package Cache Heap
Current size (bytes) = 1179648
High water mark (bytes) = 1179648
Configured size (bytes) = 472317952
Node number = 0
Memory Pool Type = Other Memory
Current size (bytes) = 196608
High water mark (bytes) = 196608
Configured size (bytes) = 20971520
Node number = 0
Memory Pool Type = Catalog Cache Heap
Current size (bytes) = 524288
High water mark (bytes) = 524288
Configured size (bytes) = 10485760
Node number = 0
Memory Pool Type = Buffer Pool Heap
Secondary ID = 1
Current size (bytes) = 494010368
High water mark (bytes) = 494010368
Configured size (bytes) = 494010368
Node number = 0
Memory Pool Type = Buffer Pool Heap
Secondary ID = System 32k buffer pool
Current size (bytes) = 1835008
High water mark (bytes) = 1835008
Configured size (bytes) = 1835008
Node number = 0
Memory Pool Type = Buffer Pool Heap
Secondary ID = System 16k buffer pool
Current size (bytes) = 1572864
High water mark (bytes) = 1572864
Configured size (bytes) = 1572864
Node number = 0
Memory Pool Type = Buffer Pool Heap
Secondary ID = System 8k buffer pool
Current size (bytes) = 1441792
High water mark (bytes) = 1441792
Configured size (bytes) = 1441792
Node number = 0
Memory Pool Type = Buffer Pool Heap
Secondary ID = System 4k buffer pool
Current size (bytes) = 1376256
High water mark (bytes) = 1376256
Configured size (bytes) = 1376256
Node number = 0
Memory Pool Type = Shared Sort Heap
Current size (bytes) = 2359296
High water mark (bytes) = 3932160
Configured size (bytes) = 40435712
Node number = 0
Memory Pool Type = Lock Manager Heap
Current size (bytes) = 159645696
High water mark (bytes) = 159645696
Configured size (bytes) = 159711232
Node number = 0
Memory Pool Type = Database Heap
Current size (bytes) = 87687168
High water mark (bytes) = 87687168
Configured size (bytes) = 119472128
Node number = 0
Memory Pool Type = Application Heap
Secondary ID = 107
Current size (bytes) = 65536
High water mark (bytes) = 65536
Configured size (bytes) = 1048576
Node number = 0
Memory Pool Type = Application Heap
Secondary ID = 106
Current size (bytes) = 65536
High water mark (bytes) = 65536
Configured size (bytes) = 1048576
Node number = 0
Memory Pool Type = Application Heap
Secondary ID = 105
Current size (bytes) = 65536
High water mark (bytes) = 65536
Configured size (bytes) = 1048576
Node number = 0
Memory Pool Type = Application Heap
Secondary ID = 104
Current size (bytes) = 65536
High water mark (bytes) = 65536
Configured size (bytes) = 1048576
Node number = 0
Memory Pool Type = Application Heap
Secondary ID = 103
Current size (bytes) = 65536
High water mark (bytes) = 65536
Configured size (bytes) = 1048576
Node number = 0
Memory Pool Type = Application Heap
Secondary ID = 102
Current size (bytes) = 65536
High water mark (bytes) = 65536
Configured size (bytes) = 1048576
Node number = 0
Memory Pool Type = Application Heap
Secondary ID = 101
Current size (bytes) = 196608
High water mark (bytes) = 196608
Configured size (bytes) = 1048576
Node number = 0
Memory Pool Type = Application Heap
Secondary ID = 100
Current size (bytes) = 65536
High water mark (bytes) = 65536
Configured size (bytes) = 1048576
Node number = 0
Memory Pool Type = Application Heap
Secondary ID = 99
Current size (bytes) = 65536
High water mark (bytes) = 65536
Configured size (bytes) = 1048576
Node number = 0
Memory Pool Type = Application Heap
Secondary ID = 98
Current size (bytes) = 65536
High water mark (bytes) = 65536
Configured size (bytes) = 1048576
Node number = 0
Memory Pool Type = Application Heap
Secondary ID = 97
Current size (bytes) = 131072
High water mark (bytes) = 131072
Configured size (bytes) = 1048576
Node number = 0
Memory Pool Type = Applications Shared Heap
Current size (bytes) = 458752
High water mark (bytes) = 458752
Configured size (bytes) = 81920000 -
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,
RajeshHi 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 -
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 advanceKasu,
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 -
SAP xMII Log/ SQL transaction Log
We have an application where we are inserting data from a PLC to the SQL Server using the xMII.
The SQL server no. of times gives the Transaction Log Full error.
This causes the error any data insertion or deletion in SQL
In tern the xMII logs error, the log file for a day (in the Lighthammer\Logs\cms.log)is seen as large as 15 GB.
We are not able to open such a huge file...
Moreover we are unable to know if there are anyu other errors other than due to the SQL logged by xMII
How can we see the Log created by xMII, this will help us in troubleshooting .
Message was edited by:
Amol KurdukarHi All,
Thanks for the help.
Ryan,
I have resolved the issue of transaction log by archiving the Log at increased frequency.
Jeremy,
We are required to have the PLC data in SQL as the Customer wants to have that and they do not have any other database, SCADA etc.
The SQL server logs (consolidates) not only the PLC data but data from some other devices as well
Moreover this is data then used for confirming the production to SAP and maintaining the status of the confirmation. This also involves queuing of the data in SQL if the data is not confirmed to SAP for any reason.
We are not logging the data every minute, The data is logged depending on a batch completion, shift completion etc.
Hope this clarifies, let us know your comments. -
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
NageshDear 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 youHi 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 -
Backup and restore full and transaction log in nonrecovery mode failed due to LSN
In SQL 2012 SP1 enterprise, when taking a full backup and followed up a transaction log backup immediately, the transaction log backup starts with an earlier LSN than the ending LSN of the full backup. As a result, I cannot restore
the transaction log backup after the full backup both as nonrecovery on another machine. I was trying to make the two machine in sync for mirroring purpose. An example is as follows.
full backup: first 1121000022679500037, last 1121000022681200001
transaction log: first 1121000022679000001, last 1121000022682000001
--- SQL Scripts used
BACKUP DATABASE xxx TO DISK = xxx WITH FORMAT
go
backup log xxx to disk = xxx
--- When restore, I tried the
restore log BarraOneArchive from disk=xxx WITH STOPATMARK = 'lsn:1121000022682000001', NORECOVERY
Also tried StopBeforeMark, did not work either. Complained about the LSN too early to apply to the databaseI think that what I am saying is correct .I said in sync mirroring ( i was not talking about witness) if network goes for few minutes or some longer time may be 20 mins ( more than that is reare scenario IS team has backup for that) logs on Principal will
continue to grow as they wont be able to commit because there connection with mirror is gone so commit from mirror is not coming.After network comes online Mirror will replay all logs and will soon try to come up with principal
Books Online says this: This is achieved by waiting to commit a transaction on the principal database, until the principal server receives a message from the mirror server stating that it has hardened the transaction's log to disk. That is,
if the remote server would go away in a way so that the primary does not notice, transactions would not commit and the primary would also be stalled.
In practice it does not work that way. When a timeout expires, the principal will consider the mirror to be gone, and Books Online says about this case
If the mirror server instance goes down, the principal server instance is unaffected and runs exposed (that is without mirroring the data). In this section, BOL does not discussion transaction logs, but it appear reasonable that the log records are
retained so that the mirror can resync once it is back.
In Async Mirroring Transaction log is sent to Mirror but it does not waits for Acknowledgement from mirror and commits the transaction.
But I would expect that the principal still gets acknowledgement that the log records have been consumed, or else your mirroring could start failing f you backup the log too frequently. That is, I would not expect any major difference between sync and async
mirroring in this regard. (Where it matters is when you fail over. With async mirroring, you are prepared to accept some data loss in case of a failover.)
These are theories that could be fairly easily tested if you have a mirroring environment set up in a lab, but I don't.
Erland Sommarskog, SQL Server MVP, [email protected] -
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 PMHi,
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 -
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 -
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 helpHi,
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
Maybe you are looking for
-
Ipad icons too big to see full screen after updating to IOS 8?
I have an IPAD Retina (4th generation) and after I updated to IOS 8, it worked fine for 2 or 3 days. Yesterday my screen went too large to display the full screen (icons are also large). When I open an app, everything is large. I tried changing the f
-
Get rid of on-screen volume display dv7
Hi, I have a dv7-4280us laptop, and I want to know if there's a way to remove the little notice that appears when you turn the volume up or down. (this thing: http://img853.imageshack.us/i/volume.png/) While it's useful, I play a lot of games, most o
-
I am not able to publish my site to a test site. I get this message: The account (my email address) does not have privileges to create an Adobe Business Catalyst temporary site. Please contact the sit eadministrator. This is a new site so there is no
-
Hi, my i pad is disabled, how can i activate ?
my i pad is disabled, how can i reactivate?
-
Why it takes 4 - 6 hours to download movies on imaciTunes
Why does it takes so long to download a movie on itunes (between 4 and 6 or, even 8 hours to download) when you purchase a movie on itunes before it is complete?