nas fails to insert into transaction log
search cancel

nas fails to insert into transaction log

book

Article ID: 280563

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

nas: Failed Query INSERT INTO NAS_TRANSACTION_LOG

 

nas.log is throwing many errors like the below (hundreds per minute?). I don't know how long this has been going on. I can open the transactionlog.db and can verify that some recent data is writing into NAS_TRANSACTION_LOG ok. The oldest log capture shows this also from 2 days ago. What is causing this? We are still using nas 9.40-T1 from development for troubleshooting a different case. Should this probe version be downgraded to previous? 

Mar  8 17:38:14:562 [17532] 3 nas: Failed Query  
 INSERT  INTO NAS_TRANSACTION_LOG (type,time,nimid,nimts,level,severity,message,sid,subsys,source,hostname,prid,robot,hub,nas,domain,origin,user_tag1,user_tag2,suppcount,tz_offset,visible,i18n_dsize,i18n_data) VALUES (<redacted>); 
Mar  8 17:38:14:562 [17532] 0 nas: Failed to insert data into transaction-log 
Mar  8 17:38:14:562 [17532] 1 nas: COM Error [0x80040e57] IDispatch error #3159 - [Microsoft OLE DB Driver for SQL Server] String or binary data would be truncated. 
Mar  8 17:38:14:562 [17532] 3 nas: ndbTableInsert error: error, '[Microsoft OLE DB Driver for SQL Server] String or binary data would be 

Environment

any version of nas

Cause

user_tag2 was too long

Resolution

Shorten the length of the user_tag2.