avoiding duplicated DB-Error in second layer

### Description
o Transaction ID for ontimeinterval
o LM_I for every database operation
o Avoided repeating 'Database Error' in second call-layer

I was about to say that it is a bit of an overkill, but you happen to be right (a little :-))
There is this LM_T before the call to transactionIdSet and (if LmtNotifier is set) this trace line will come out with the previous transactionId, whilst the first one will come with N/A.
First of all I need to move the call to transactionIdSet to before the LM_T.
And then I could set the transactyionId to N/A atthe end of the loop even though it is nothing worth as it will just start the loop all over again and remove the N/A for the nexttransactionId in turn.