We have a couple of feautures, which would be nice to have:
1) A TIMESTAMP field for insert into TLOG table
The date& secs sometimes are not unique, which makes it harder to read output
2) The adding of SID & Server on TLOG table - makes it easier to track errors in programs
And osuser as well.
3) the ability to have a field for giving messages an identifier
Ie it is nice to extract all messages from one particular job.
Just an open field wher you could put in your own defined "jobid"
Best regards from Denmark
Mette
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1) A TIMESTAMP field for insert into TLOG table
The date& secs sometimes are not unique, which makes it harder to read output
GM1: this inforamtion is store by log4plsql un ID field. you can read it direcly in plog table.
in log procedure un PLOG PACKAGE BODY line 300 you can find the output format. You can update it with for exemple:
hdr := TO_CHAR(pLDATE, 'HH24:MI:SS')||':'||LTRIM(TO_CHAR(MOD(pLHSECS,100),'09'))||'-'||getLevelInText(pLLEVEL)||'-'||pLSECTION||' ';
change by
hdr := TO_CHAR(pLDATE, 'HH24:MI:SS')||'-'||pID||':'||LTRIM(TO_CHAR(MOD(pLHSECS,100),'09'))||'-'||getLevelInText(pLLEVEL)||'-'||pLSECTION||' ';
1) A TIMESTAMP field for insert into TLOG table
The date& secs sometimes are not unique, which makes it harder to read output
2) The adding of SID & Server on TLOG table - makes it easier to track errors in programs
And osuser as well.
GM2: For the question 2 and 3 can you add this information in the message?
Regards
Guillaume Moulard
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
2) SID & Server
yes, I know that we can always store it in the message itself. But then we are not sure that everyone does this. So we cant depend on it. The same thing with an optional MessageNo (nice for tracking errors with numbers, PU0012 instaed af the actualt message text).
1) Timestamp
I have considered just adding a TIMESTAMP(6) field with a default value of systimestamp in TLOG table.
Best regards from Denmark
Mette
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
about the timestamp, you have 2 information in tlog table :
LDate set by sysdate,
LHSECS set by DBMS_UTILITY.GET_TIME (current time in 100th's of a second)
do you know the systimestamp compatibility?
G.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi there
First thanx for a great utility !!
Are you still doing development?
We have a couple of feautures, which would be nice to have:
1) A TIMESTAMP field for insert into TLOG table
The date& secs sometimes are not unique, which makes it harder to read output
2) The adding of SID & Server on TLOG table - makes it easier to track errors in programs
And osuser as well.
3) the ability to have a field for giving messages an identifier
Ie it is nice to extract all messages from one particular job.
Just an open field wher you could put in your own defined "jobid"
Best regards from Denmark
Mette
Hi,
Unfortunly... development going on, not relay.
1) A TIMESTAMP field for insert into TLOG table
The date& secs sometimes are not unique, which makes it harder to read output
GM1: this inforamtion is store by log4plsql un ID field. you can read it direcly in plog table.
in log procedure un PLOG PACKAGE BODY line 300 you can find the output format. You can update it with for exemple:
hdr := TO_CHAR(pLDATE, 'HH24:MI:SS')||':'||LTRIM(TO_CHAR(MOD(pLHSECS,100),'09'))||'-'||getLevelInText(pLLEVEL)||'-'||pLSECTION||' ';
change by
hdr := TO_CHAR(pLDATE, 'HH24:MI:SS')||'-'||pID||':'||LTRIM(TO_CHAR(MOD(pLHSECS,100),'09'))||'-'||getLevelInText(pLLEVEL)||'-'||pLSECTION||' ';
1) A TIMESTAMP field for insert into TLOG table
The date& secs sometimes are not unique, which makes it harder to read output
2) The adding of SID & Server on TLOG table - makes it easier to track errors in programs
And osuser as well.
GM2: For the question 2 and 3 can you add this information in the message?
Regards
Guillaume Moulard
HI again.
2) SID & Server
yes, I know that we can always store it in the message itself. But then we are not sure that everyone does this. So we cant depend on it. The same thing with an optional MessageNo (nice for tracking errors with numbers, PU0012 instaed af the actualt message text).
1) Timestamp
I have considered just adding a TIMESTAMP(6) field with a default value of systimestamp in TLOG table.
Best regards from Denmark
Mette
Hi,
about the timestamp, you have 2 information in tlog table :
LDate set by sysdate,
LHSECS set by DBMS_UTILITY.GET_TIME (current time in 100th's of a second)
do you know the systimestamp compatibility?
G.