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

More on this (it seems to be a critical code line :). In this case, we are not using IP and port in the trace, but the complete URL. Is that what we desired? I mean, to be homogeneous in all the "starting transaction messages" we should stick to ("ceñirnos a" :)) just IP and port.