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

Yeah, I can't put the trace where I would want to as I didn't havr ethe ip and port (part of the URL), so I put it here instead.
About the URL, it contains all we want and even more.
I could split up the URL and report only IP and port, but ... we only lose information if we do that.
Why spend time and lines to make it worse that it already is?
Perhaps we should add the path of the URL in connectionTreat instead of removing it from here?
It is true what you say about being homogeneous, of course