log4plsql-all-info Mailing List for LOG4PLSQL (Page 3)
Brought to you by:
gmoulard
Menu
▾
▴
log4plsql-all-info — all information DEV, USE, QUESTION, and more
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
(8) |
May
(4) |
Jun
(11) |
Jul
(13) |
Aug
(2) |
Sep
(1) |
Oct
(2) |
Nov
(9) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(3) |
Feb
(1) |
Mar
(4) |
Apr
(1) |
May
(1) |
Jun
(5) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(5) |
Dec
(6) |
| 2004 |
Jan
(7) |
Feb
(26) |
Mar
(8) |
Apr
(1) |
May
(5) |
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(4) |
Dec
(8) |
| 2005 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
|
May
(10) |
Jun
(2) |
Jul
|
Aug
(5) |
Sep
|
Oct
(7) |
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
(2) |
Mar
(4) |
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
(5) |
Sep
(2) |
Oct
(3) |
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2009 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <log...@li...> - 2005-08-24 18:34:03
|
Please let me know if it is not possible using the current log4plsql=20 context. Thanks Raja On 8/24/05, Raja Ram <raj...@gm...> wrote:=20 >=20 > Hi, > I am just exploring the way log4plsql is working and I want some=20 > clarification. > I have some stored procs like SP1, SP2, SP3 etc. and I have implemented= =20 > log4plsql there. The log is going into TLOG table and finally it is going= =20 > into a file called "lo4plsql.log". > Now I want separate files for all the Stored Procedure. SO How can I=20 > implement this??? > I will be really thankful to you and appreciate your time if you can=20 > answer my question as soon as possible. > Regards > Raja > |
|
From: <log...@li...> - 2005-08-24 17:41:40
|
Hi, I am just exploring the way log4plsql is working and I want some=20 clarification. I have some stored procs like SP1, SP2, SP3 etc. and I have implemented=20 log4plsql there. The log is going into TLOG table and finally it is going= =20 into a file called "lo4plsql.log". Now I want separate files for all the Stored Procedure. SO How can I=20 implement this??? I will be really thankful to you and appreciate your time if you can answe= r=20 my question as soon as possible. Regards Raja |
|
From: <log...@li...> - 2005-06-07 06:20:53
|
Dear Colleague, FRAUD CAN STRIKE, AT ANY TIME! Contrary to popular believe, fraud is not primarily a problem of employee dishonesty but increasingly involves senior managers, suppliers, customers, competitors, criminal groups and is achieved by deception, collusion, false reporting, bribery and technological abuse. BEING FOREWARNED IS FOREARMED! This totally updated program exposes the realities of fraud and proposes applied solutions that will make your organization more profitable and secure - ensuring that your corporate goals are secured and protected. Led by Michael Comer, world leading specialist & authority in Corporate Fraud - Detection & Prevention. Officiated by Dato' Sri Musa Hj Hassan, Deputy Inspector General of Police, Royal Malaysia Police Features a special clinic on Lie Detection - Deception At Work! Ensuring Your Decisions are Based on the Truth. OF PRIME IMPORTANCE & BENEFIT TO: Senior management members comprising Internal Audit, Risk & Compliance, Financial Controllers & Directors, Board Members & Stakeholders. IS YOUR ORGANIZATION ALREADY AT RISK? Gain piercing insights into the Prevention, Detection and Investigation of Fraud! BOOK YOUR SEATS NOW! CALL 03-7804 4666/777/888 ...before it's too late!!! Please share this email with your Internal Audit / Training / HR Dept, colleagues and friends... > REGISTER NOW - The Qualities of a Leader > <http://www.rayma.com.my/seminars/CF.shtml> > ------------------------------------------------------------------------ > CORPORATE FRAUD - IT HAPPENS! > Cutting Edge Detection & Prevention Strategies > > ------------------------------------------------------------------------ > Date:June 20-21, 2005 > Time: 9.00am to 5.00pm daily > Venue: Concorde Hotel, Kuala Lumpur > > Your Investment: RM2,380 per person > (inclusive of comprehensive program manual, lunches and refreshments) > > GROUP INCENTIVE: 10% OFF - 4 or more from the same company to > facilitate successful > team implementation of the knowledge and skills acquired from the > program. > ------------------------------------------------------------------------ > Details and Online Registration: > http://www.rayma.com.my/seminars/CF.shtml > > Download Brochure: > http://www.rayma.com.my/seminars/CF.pdf > > Register Online or call Evelyn NOW at > (603) 7804 4666 / 777 / 888 > Email: sem...@ra... <mailto:sem...@ra...> > |
|
From: <log...@li...> - 2005-06-06 17:50:13
|
Hi, =20 Unfortunately, is this stage, that is not possible.=20 You can write / port all plsql code and re-used the log4plsq background listener, but I thinck is more easy to re-used only the concept :-( Regards, Guillaume Moulard=20 -----Message d'origine----- De : log...@li... [mailto:log...@li...]=20 Envoy=E9 : lundi 30 mai 2005 16:26 =C0 : log...@li... Objet : [log4plsql] Log 4 pl/sql I would like use database Sybase in Log 4 pl/sql. Is possible???? ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the = office luge track? If you want to score the big prize, get to know the little guy. =20 Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=3D20 _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net |
|
From: <log...@li...> - 2005-05-30 14:23:53
|
I would like use database Sybase in Log 4 pl/sql. Is possible???? -- LINK EXPRESS - Banda Larga sem Fio www.linkexpress.com.br |
|
From: <log...@li...> - 2005-05-25 09:38:59
|
Thanks. -----Message d'origine----- De : log...@li... [mailto:log...@li...] Envoy=E9 : mercredi 18 mai 2005 20:15 =C0 : log...@li... Objet : RE: [log4plsql] Problem using Log4j feature. Hi, It's right, the 3.1.3 version have a bug in Log4JbackgroundProcess.=20 I put in sourceforge.net a version 3.1.3.1. I thinck is OK now. Regards, Guillaume Moulard -----Message d'origine----- De : log...@li... [mailto:log...@li...]=20 Envoy=E9 : mercredi 11 mai 2005 14:27 =C0 : log...@li... Objet : RE: [log4plsql] Problem using Log4j feature. The problem is due to a bug in the listener thread. messages in the pipe are not written and read in the same way, hance = reading in the pipe throws a SQLException. Code from package plog ------------------------ DBMS_PIPE.pack_message(pID); -- SEQUENTIAL ID DBMS_PIPE.pack_message(pLDATE); -- TIMESTAMP OF = LOG STATEMENT DBMS_PIPE.pack_message(MOD(pLHSECS,100)); -- HUNDREDTHS OF SECONDS FOR TIMESTAMP DBMS_PIPE.pack_message(pLLEVEL); -- LOG LEVEL DBMS_PIPE.pack_message(pLSECTION); -- LOG SECTION - ANALOGUE TO LOG4J Logger NAME DBMS_PIPE.pack_message(LLTEXTE); -- LOG MESSAGE DBMS_PIPE.pack_message(pLUSER); -- CALLING USER DBMS_PIPE.pack_message('SAVE_IN_LOG'); -- MESSAGE TYPE? DBMS_PIPE.pack_message(PMDC.getKeyString); -- MAPPED DOMAIN CONTEXT KEYS FOR LOG4J DBMS_PIPE.pack_message(PMDC.getValueString); -- MAPPED DOMAIN CONTEXT VALUES FOR LOG4J DBMS_PIPE.pack_message(PMDC.getSeparator); -- MAPPED DOMAIN CONTEXT SEPARATOR FOR LOG4J=20 Code from ReaderLogDataBase.sqlj -------------------------------- long piped_ID ; =20 String piped_LDATE ;=20 long piped_LHSECS ;=20 int piped_LLEVEL ; =20 String piped_LSECTION ;=20 String piped_LTEXTE ; =20 String piped_LUSER ; =20 String piped_COMMAND =3D "WAIT"; =20 ... #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out = piped_ID)} ; #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out piped_LDATE)};=20 #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out piped_LLEVEL)};=20 #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out piped_LSECTION)};=20 #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out piped_LTEXTE)};=20 #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out piped_LUSER)};=20 #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out piped_COMMAND)}; piped_LDATE must be of type Date and pLHSECS is not retrieved. -----Message d'origine----- De : log...@li... [mailto:log...@li...] Envoy=E9 : mardi 10 mai 2005 19:41 =C0 : log...@li... Objet : RE: [log4plsql] Problem using Log4j feature. In addition to my previous message I have written this procedure and it works well. So it shows that the message is actually written to the = pipe. declare s integer ; id number; ldate date; lhsecs number; lhlevel number; lsection varchar2(2000); ltext varchar2(2000); luser varchar2(30); begin plog.error('erreur toto'); s :=3D dbms_pipe.receive_message('LOG_PIPE',1); dbms_output.put_line(to_char(s)); dbms_pipe.unpack_message(id); dbms_pipe.unpack_message(ldate); dbms_pipe.unpack_message(lhsecs); dbms_pipe.unpack_message(lhlevel); dbms_pipe.unpack_message(lsection); dbms_pipe.unpack_message(ltext); dbms_pipe.unpack_message(luser); dbms_output.put_line(id||' '||ldate||' '||lhsecs||' '||lhlevel||' '||lsection||' '||ltext||' '||luser); end; -----Message d'origine----- De : log...@li... [mailto:log...@li...] Envoy=E9 : mardi 10 mai 2005 18:50 =C0 : log...@li... Objet : [log4plsql] Problem using Log4j feature. Hi all, I try to use the log4j feature with log4plsql. Unfortunetly, the listener process seems not to receive messages from = the DBMS_PIPE. Here is a fragment of the listener's ouput :=20 -------------------------------------------------------------------------= -- 2005-05-10 17:29:03,382 INFO [main] backgroundProcess.Run (Run.java:62) = - start log4plsql.properties: ./properties/log4plsql.xml 2005-05-10 17:29:03,388 DEBUG [main] backgroundProcess.Run (Run.java:63) = - log4j .properties : /ulis/users/ulisu9/Log4plsql/properties/log4j.xml 2005-05-10 17:29:03,430 DEBUG [main] backgroundProcess.ReaderThread (ReaderThrea d.java:40) - ReaderLogDataBase : Connect 2005-05-10 17:29:03,461 DEBUG [main] backgroundProcess.ReaderLogDataBase (Reader LogDataBase.sqlj:78) - Start logSource:source1 dbURI:jdbc:oracle:thin:@127.0.0.1 :1542:PRODU9 dbUser:ulog dbPass:ulog pipeName:LOG_PIPE 2005-05-10 17:29:04,207 = INFO [main] backgroundProcess.ReaderLogDataBase (Reader LogDataBase.sqlj:85) = - Startup logSource:source1 dbURI:jdbc:oracle:thin:@127.0.0 = .1:1542:PRODU9 dbUser:ulog dbPass:ulog pipeName:LOG_PIPE 2005-05-10 17:29:04,355 DEBUG [main] backgroundProcess.DynamicLevel (DynamicLeve l.java:34) - Level Creation name:OFF level:99999 syslogEquiv:10 =20 ..... 2005-05-10 17:29:48,999 DEBUG [Thread-1] backgroundProcess.ReaderLogDataBase (Re aderLogDataBase.sqlj:147) - = Start Log4j Backgroung fetching 2005-05-10 17:29:49,002 = DEBUG [Thread-1] backgroundProcess.ReaderLogDataBase (Re = aderLogDataBase.sqlj:169) - DBMS_PIPE.receive_message:1 2005-05-10 17:29:49,003 DEBUG [Thread-1] backgroundProcess.ReaderLogDataBase (Re aderLogDataBase.sqlj:210) - Nbr line read in logSource:source1 : 0 --------------------------------------------------- You can see that the DBMS pipe name is the default and that's the same = in the PLOGPARAM package. By inserting some debug code to the PLOG.LOG procedure I noticed that it actually writes to the pipe (the following code is executed and ret is = 0). ret :=3D DBMS_PIPE.send_message(pCTX.DBMS_PIPE_NAME); =20 IF RET <> 0 then raise_application_error(ERR_CODE_DBMS_PIPE, = MES_CODE_DBMS_PIPE || RET); END IF; =20 But the "DBMS_PIPE.receive_message:1" message seems to mean that the listener process finds no message in the pipe. Am I right ? Do you know where it comes from ? ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be = the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_ids93&alloc_id=16281&op=3Dick _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be = the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_ids93&alloc_id=16281&op=3Dick _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be = the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_ids93&alloc_id=16281&op=3Dick _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_idt12&alloc_id=16344&op=3Dick _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net |
|
From: <log...@li...> - 2005-05-18 18:15:32
|
Hi, It's right, the 3.1.3 version have a bug in Log4JbackgroundProcess.=20 I put in sourceforge.net a version 3.1.3.1. I thinck is OK now. Regards, Guillaume Moulard -----Message d'origine----- De : log...@li... [mailto:log...@li...]=20 Envoy=E9 : mercredi 11 mai 2005 14:27 =C0 : log...@li... Objet : RE: [log4plsql] Problem using Log4j feature. The problem is due to a bug in the listener thread. messages in the pipe are not written and read in the same way, hance = reading in the pipe throws a SQLException. Code from package plog ------------------------ DBMS_PIPE.pack_message(pID); -- SEQUENTIAL ID DBMS_PIPE.pack_message(pLDATE); -- TIMESTAMP OF = LOG STATEMENT DBMS_PIPE.pack_message(MOD(pLHSECS,100)); -- HUNDREDTHS OF SECONDS FOR TIMESTAMP DBMS_PIPE.pack_message(pLLEVEL); -- LOG LEVEL DBMS_PIPE.pack_message(pLSECTION); -- LOG SECTION - ANALOGUE TO LOG4J Logger NAME DBMS_PIPE.pack_message(LLTEXTE); -- LOG MESSAGE DBMS_PIPE.pack_message(pLUSER); -- CALLING USER DBMS_PIPE.pack_message('SAVE_IN_LOG'); -- MESSAGE TYPE? DBMS_PIPE.pack_message(PMDC.getKeyString); -- MAPPED DOMAIN CONTEXT KEYS FOR LOG4J DBMS_PIPE.pack_message(PMDC.getValueString); -- MAPPED DOMAIN CONTEXT VALUES FOR LOG4J DBMS_PIPE.pack_message(PMDC.getSeparator); -- MAPPED DOMAIN CONTEXT SEPARATOR FOR LOG4J=20 Code from ReaderLogDataBase.sqlj -------------------------------- long piped_ID ; =20 String piped_LDATE ;=20 long piped_LHSECS ;=20 int piped_LLEVEL ; =20 String piped_LSECTION ;=20 String piped_LTEXTE ; =20 String piped_LUSER ; =20 String piped_COMMAND =3D "WAIT"; =20 ... #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out = piped_ID)} ; #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out piped_LDATE)};=20 #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out piped_LLEVEL)};=20 #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out piped_LSECTION)};=20 #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out piped_LTEXTE)};=20 #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out piped_LUSER)};=20 #sql [ctx] { CALL DBMS_PIPE.unpack_message(:out piped_COMMAND)}; piped_LDATE must be of type Date and pLHSECS is not retrieved. -----Message d'origine----- De : log...@li... [mailto:log...@li...] Envoy=E9 : mardi 10 mai 2005 19:41 =C0 : log...@li... Objet : RE: [log4plsql] Problem using Log4j feature. In addition to my previous message I have written this procedure and it works well. So it shows that the message is actually written to the = pipe. declare s integer ; id number; ldate date; lhsecs number; lhlevel number; lsection varchar2(2000); ltext varchar2(2000); luser varchar2(30); begin plog.error('erreur toto'); s :=3D dbms_pipe.receive_message('LOG_PIPE',1); dbms_output.put_line(to_char(s)); dbms_pipe.unpack_message(id); dbms_pipe.unpack_message(ldate); dbms_pipe.unpack_message(lhsecs); dbms_pipe.unpack_message(lhlevel); dbms_pipe.unpack_message(lsection); dbms_pipe.unpack_message(ltext); dbms_pipe.unpack_message(luser); dbms_output.put_line(id||' '||ldate||' '||lhsecs||' '||lhlevel||' '||lsection||' '||ltext||' '||luser); end; -----Message d'origine----- De : log...@li... [mailto:log...@li...] Envoy=E9 : mardi 10 mai 2005 18:50 =C0 : log...@li... Objet : [log4plsql] Problem using Log4j feature. Hi all, I try to use the log4j feature with log4plsql. Unfortunetly, the listener process seems not to receive messages from = the DBMS_PIPE. Here is a fragment of the listener's ouput :=20 -------------------------------------------------------------------------= -- 2005-05-10 17:29:03,382 INFO [main] backgroundProcess.Run (Run.java:62) = - start log4plsql.properties: ./properties/log4plsql.xml 2005-05-10 17:29:03,388 DEBUG [main] backgroundProcess.Run (Run.java:63) = - log4j .properties : /ulis/users/ulisu9/Log4plsql/properties/log4j.xml 2005-05-10 17:29:03,430 DEBUG [main] backgroundProcess.ReaderThread (ReaderThrea d.java:40) - ReaderLogDataBase : Connect 2005-05-10 17:29:03,461 DEBUG [main] backgroundProcess.ReaderLogDataBase (Reader LogDataBase.sqlj:78) - Start logSource:source1 dbURI:jdbc:oracle:thin:@127.0.0.1 :1542:PRODU9 dbUser:ulog dbPass:ulog pipeName:LOG_PIPE 2005-05-10 17:29:04,207 = INFO [main] backgroundProcess.ReaderLogDataBase (Reader LogDataBase.sqlj:85) = - Startup logSource:source1 dbURI:jdbc:oracle:thin:@127.0.0 = .1:1542:PRODU9 dbUser:ulog dbPass:ulog pipeName:LOG_PIPE 2005-05-10 17:29:04,355 DEBUG [main] backgroundProcess.DynamicLevel (DynamicLeve l.java:34) - Level Creation name:OFF level:99999 syslogEquiv:10 =20 ..... 2005-05-10 17:29:48,999 DEBUG [Thread-1] backgroundProcess.ReaderLogDataBase (Re aderLogDataBase.sqlj:147) - = Start Log4j Backgroung fetching 2005-05-10 17:29:49,002 = DEBUG [Thread-1] backgroundProcess.ReaderLogDataBase (Re = aderLogDataBase.sqlj:169) - DBMS_PIPE.receive_message:1 2005-05-10 17:29:49,003 DEBUG [Thread-1] backgroundProcess.ReaderLogDataBase (Re aderLogDataBase.sqlj:210) - Nbr line read in logSource:source1 : 0 --------------------------------------------------- You can see that the DBMS pipe name is the default and that's the same = in the PLOGPARAM package. By inserting some debug code to the PLOG.LOG procedure I noticed that it actually writes to the pipe (the following code is executed and ret is = 0). ret :=3D DBMS_PIPE.send_message(pCTX.DBMS_PIPE_NAME); =20 IF RET <> 0 then raise_application_error(ERR_CODE_DBMS_PIPE, = MES_CODE_DBMS_PIPE || RET); END IF; =20 But the "DBMS_PIPE.receive_message:1" message seems to mean that the listener process finds no message in the pipe. Am I right ? Do you know where it comes from ? ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be = the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_ids93&alloc_id=16281&op=3Dick _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be = the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_ids93&alloc_id=16281&op=3Dick _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be = the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_ids93&alloc_id=16281&op=3Dick _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net |
|
From: <log...@li...> - 2005-05-11 12:27:15
|
The problem is due to a bug in the listener thread.
messages in the pipe are not written and read in the same way, hance =
reading in the pipe throws a SQLException.
Code from package plog
------------------------
DBMS_PIPE.pack_message(pID); -- SEQUENTIAL ID
DBMS_PIPE.pack_message(pLDATE); -- TIMESTAMP OF =
LOG STATEMENT
DBMS_PIPE.pack_message(MOD(pLHSECS,100)); -- HUNDREDTHS OF =
SECONDS FOR TIMESTAMP
DBMS_PIPE.pack_message(pLLEVEL); -- LOG LEVEL
DBMS_PIPE.pack_message(pLSECTION); -- LOG SECTION - =
ANALOGUE TO LOG4J Logger NAME
DBMS_PIPE.pack_message(LLTEXTE); -- LOG MESSAGE
DBMS_PIPE.pack_message(pLUSER); -- CALLING USER
DBMS_PIPE.pack_message('SAVE_IN_LOG'); -- MESSAGE TYPE?
DBMS_PIPE.pack_message(PMDC.getKeyString); -- MAPPED DOMAIN =
CONTEXT KEYS FOR LOG4J
DBMS_PIPE.pack_message(PMDC.getValueString); -- MAPPED DOMAIN =
CONTEXT VALUES FOR LOG4J
DBMS_PIPE.pack_message(PMDC.getSeparator); -- MAPPED DOMAIN =
CONTEXT SEPARATOR FOR LOG4J=20
Code from ReaderLogDataBase.sqlj
--------------------------------
long piped_ID ; =20
String piped_LDATE ;=20
long piped_LHSECS ;=20
int piped_LLEVEL ; =20
String piped_LSECTION ;=20
String piped_LTEXTE ; =20
String piped_LUSER ; =20
String piped_COMMAND =3D "WAIT"; =20
...
#sql [ctx] { CALL DBMS_PIPE.unpack_message(:out =
piped_ID)} ; =20
#sql [ctx] { CALL DBMS_PIPE.unpack_message(:out =
piped_LDATE)};=20
#sql [ctx] { CALL DBMS_PIPE.unpack_message(:out =
piped_LLEVEL)};=20
#sql [ctx] { CALL DBMS_PIPE.unpack_message(:out =
piped_LSECTION)};=20
#sql [ctx] { CALL DBMS_PIPE.unpack_message(:out =
piped_LTEXTE)};=20
#sql [ctx] { CALL DBMS_PIPE.unpack_message(:out =
piped_LUSER)};=20
#sql [ctx] { CALL DBMS_PIPE.unpack_message(:out =
piped_COMMAND)};
piped_LDATE must be of type Date and pLHSECS is not retrieved.
-----Message d'origine-----
De : log...@li...
[mailto:log...@li...]
Envoy=E9 : mardi 10 mai 2005 19:41
=C0 : log...@li...
Objet : RE: [log4plsql] Problem using Log4j feature.
In addition to my previous message I have written this procedure and it =
works well. So it shows that the message is actually written to the =
pipe.
declare=20
s integer ;
id number;
ldate date;
lhsecs number;
lhlevel number;
lsection varchar2(2000);
ltext varchar2(2000);
luser varchar2(30);
begin
plog.error('erreur toto');
s :=3D dbms_pipe.receive_message('LOG_PIPE',1);
dbms_output.put_line(to_char(s));
dbms_pipe.unpack_message(id);
dbms_pipe.unpack_message(ldate);
dbms_pipe.unpack_message(lhsecs);
dbms_pipe.unpack_message(lhlevel);
dbms_pipe.unpack_message(lsection);
dbms_pipe.unpack_message(ltext);
dbms_pipe.unpack_message(luser);
dbms_output.put_line(id||' '||ldate||' '||lhsecs||' '||lhlevel||' =
'||lsection||' '||ltext||' '||luser);
end;
-----Message d'origine-----
De : log...@li...
[mailto:log...@li...]
Envoy=E9 : mardi 10 mai 2005 18:50
=C0 : log...@li...
Objet : [log4plsql] Problem using Log4j feature.
Hi all,
I try to use the log4j feature with log4plsql.
Unfortunetly, the listener process seems not to receive messages from =
the DBMS_PIPE.
Here is a fragment of the listener's ouput :=20
-------------------------------------------------------------------------=
--
2005-05-10 17:29:03,382 INFO [main] backgroundProcess.Run (Run.java:62) =
- start log4plsql.properties: ./properties/log4plsql.xml =
2005-05-10 17:29:03,388 DEBUG [main] =
backgroundProcess.Run (Run.java:63) - log4j .properties : =
/ulis/users/ulisu9/Log4plsql/properties/log4j.xml =
2005-05-10 17:29:03,430 DEBUG [main] backgroundProcess.ReaderThread =
(ReaderThrea d.java:40) - ReaderLogDataBase : Connect =
2005-05-10 17:29:03,461 DEBUG [main] =
backgroundProcess.ReaderLogDataBase (Reader LogDataBase.sqlj:78) - =
Start logSource:source1 dbURI:jdbc:oracle:thin:@127.0.0.1 :1542:PRODU9 =
dbUser:ulog dbPass:ulog pipeName:LOG_PIPE =
2005-05-10 17:29:04,207 INFO [main] backgroundProcess.ReaderLogDataBase =
(Reader LogDataBase.sqlj:85) - Startup logSource:source1 =
dbURI:jdbc:oracle:thin:@127.0.0 .1:1542:PRODU9 dbUser:ulog dbPass:ulog =
pipeName:LOG_PIPE 2005-05-10 17:29:04,355 DEBUG =
[main] backgroundProcess.DynamicLevel (DynamicLeve l.java:34) - Level =
Creation name:OFF level:99999 syslogEquiv:10 =20
.....
2005-05-10 17:29:48,999 DEBUG [Thread-1] =
backgroundProcess.ReaderLogDataBase (Re aderLogDataBase.sqlj:147) - =
Start Log4j Backgroung fetching 2005-05-10 =
17:29:49,002 DEBUG [Thread-1] backgroundProcess.ReaderLogDataBase (Re =
aderLogDataBase.sqlj:169) - DBMS_PIPE.receive_message:1 =
2005-05-10 17:29:49,003 DEBUG [Thread-1] =
backgroundProcess.ReaderLogDataBase (Re aderLogDataBase.sqlj:210) - Nbr =
line read in logSource:source1 : 0 =20
---------------------------------------------------
You can see that the DBMS pipe name is the default and that's the same =
in the PLOGPARAM package.
By inserting some debug code to the PLOG.LOG procedure I noticed that it =
actually writes to the pipe (the following code is executed and ret is =
0).
ret :=3D DBMS_PIPE.send_message(pCTX.DBMS_PIPE_NAME); =20
IF RET <> 0 then
raise_application_error(ERR_CODE_DBMS_PIPE, =
MES_CODE_DBMS_PIPE || RET);
END IF; =20
But the "DBMS_PIPE.receive_message:1" message seems to mean that the =
listener process finds no message in the pipe. Am I right ?
Do you know where it comes from ?
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id=16281&op=3Dick
_______________________________________________
Log4plsql-all-info mailing list
Log...@li...
https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info
log4plsq : http://log4plsql.sourceforge.net
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id=16281&op=3Dick
_______________________________________________
Log4plsql-all-info mailing list
Log...@li...
https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info
log4plsq : http://log4plsql.sourceforge.net
|
|
From: <log...@li...> - 2005-05-10 17:40:47
|
In addition to my previous message I have written this procedure and it =
works well. So it shows that the message is actually written to the =
pipe.
declare=20
s integer ;
id number;
ldate date;
lhsecs number;
lhlevel number;
lsection varchar2(2000);
ltext varchar2(2000);
luser varchar2(30);
begin
plog.error('erreur toto');
s :=3D dbms_pipe.receive_message('LOG_PIPE',1);
dbms_output.put_line(to_char(s));
dbms_pipe.unpack_message(id);
dbms_pipe.unpack_message(ldate);
dbms_pipe.unpack_message(lhsecs);
dbms_pipe.unpack_message(lhlevel);
dbms_pipe.unpack_message(lsection);
dbms_pipe.unpack_message(ltext);
dbms_pipe.unpack_message(luser);
dbms_output.put_line(id||' '||ldate||' '||lhsecs||' '||lhlevel||' =
'||lsection||' '||ltext||' '||luser);
end;
-----Message d'origine-----
De : log...@li...
[mailto:log...@li...]
Envoy=E9 : mardi 10 mai 2005 18:50
=C0 : log...@li...
Objet : [log4plsql] Problem using Log4j feature.
Hi all,
I try to use the log4j feature with log4plsql.
Unfortunetly, the listener process seems not to receive messages from =
the DBMS_PIPE.
Here is a fragment of the listener's ouput :=20
-------------------------------------------------------------------------=
--
2005-05-10 17:29:03,382 INFO [main] backgroundProcess.Run (Run.java:62) =
- start log4plsql.properties: ./properties/log4plsql.xml =
2005-05-10 17:29:03,388 DEBUG [main] =
backgroundProcess.Run (Run.java:63) - log4j .properties : =
/ulis/users/ulisu9/Log4plsql/properties/log4j.xml =
2005-05-10 17:29:03,430 DEBUG [main] backgroundProcess.ReaderThread =
(ReaderThrea d.java:40) - ReaderLogDataBase : Connect =
2005-05-10 17:29:03,461 DEBUG [main] =
backgroundProcess.ReaderLogDataBase (Reader LogDataBase.sqlj:78) - =
Start logSource:source1 dbURI:jdbc:oracle:thin:@127.0.0.1 :1542:PRODU9 =
dbUser:ulog dbPass:ulog pipeName:LOG_PIPE =
2005-05-10 17:29:04,207 INFO [main] backgroundProcess.ReaderLogDataBase =
(Reader LogDataBase.sqlj:85) - Startup logSource:source1 =
dbURI:jdbc:oracle:thin:@127.0.0 .1:1542:PRODU9 dbUser:ulog dbPass:ulog =
pipeName:LOG_PIPE 2005-05-10 17:29:04,355 DEBUG =
[main] backgroundProcess.DynamicLevel (DynamicLeve l.java:34) - Level =
Creation name:OFF level:99999 syslogEquiv:10 =20
.....
2005-05-10 17:29:48,999 DEBUG [Thread-1] =
backgroundProcess.ReaderLogDataBase (Re aderLogDataBase.sqlj:147) - =
Start Log4j Backgroung fetching 2005-05-10 =
17:29:49,002 DEBUG [Thread-1] backgroundProcess.ReaderLogDataBase (Re =
aderLogDataBase.sqlj:169) - DBMS_PIPE.receive_message:1 =
2005-05-10 17:29:49,003 DEBUG [Thread-1] =
backgroundProcess.ReaderLogDataBase (Re aderLogDataBase.sqlj:210) - Nbr =
line read in logSource:source1 : 0 =20
---------------------------------------------------
You can see that the DBMS pipe name is the default and that's the same =
in the PLOGPARAM package.
By inserting some debug code to the PLOG.LOG procedure I noticed that it =
actually writes to the pipe (the following code is executed and ret is =
0).
ret :=3D DBMS_PIPE.send_message(pCTX.DBMS_PIPE_NAME); =20
IF RET <> 0 then
raise_application_error(ERR_CODE_DBMS_PIPE, =
MES_CODE_DBMS_PIPE || RET);
END IF; =20
But the "DBMS_PIPE.receive_message:1" message seems to mean that the =
listener process finds no message in the pipe. Am I right ?
Do you know where it comes from ?
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id=16281&op=3Dick
_______________________________________________
Log4plsql-all-info mailing list
Log...@li...
https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info
log4plsq : http://log4plsql.sourceforge.net
|
|
From: <log...@li...> - 2005-05-10 16:50:11
|
Hi all,
I try to use the log4j feature with log4plsql.
Unfortunetly, the listener process seems not to receive messages from =
the DBMS_PIPE.
Here is a fragment of the listener's ouput :=20
-------------------------------------------------------------------------=
--
2005-05-10 17:29:03,382 INFO [main] backgroundProcess.Run (Run.java:62) =
- start log4plsql.properties: ./properties/log4plsql.xml =
2005-05-10 17:29:03,388 DEBUG [main] =
backgroundProcess.Run (Run.java:63) - log4j .properties : =
/ulis/users/ulisu9/Log4plsql/properties/log4j.xml =
2005-05-10 17:29:03,430 DEBUG [main] backgroundProcess.ReaderThread =
(ReaderThrea d.java:40) - ReaderLogDataBase : Connect =
2005-05-10 17:29:03,461 DEBUG [main] =
backgroundProcess.ReaderLogDataBase (Reader LogDataBase.sqlj:78) - =
Start logSource:source1 dbURI:jdbc:oracle:thin:@127.0.0.1 :1542:PRODU9 =
dbUser:ulog dbPass:ulog pipeName:LOG_PIPE =
2005-05-10 17:29:04,207 INFO [main] backgroundProcess.ReaderLogDataBase =
(Reader LogDataBase.sqlj:85) - Startup logSource:source1 =
dbURI:jdbc:oracle:thin:@127.0.0 .1:1542:PRODU9 dbUser:ulog dbPass:ulog =
pipeName:LOG_PIPE 2005-05-10 17:29:04,355 DEBUG =
[main] backgroundProcess.DynamicLevel (DynamicLeve l.java:34) - Level =
Creation name:OFF level:99999 syslogEquiv:10 =20
.....
2005-05-10 17:29:48,999 DEBUG [Thread-1] =
backgroundProcess.ReaderLogDataBase (Re aderLogDataBase.sqlj:147) - =
Start Log4j Backgroung fetching 2005-05-10 =
17:29:49,002 DEBUG [Thread-1] backgroundProcess.ReaderLogDataBase (Re =
aderLogDataBase.sqlj:169) - DBMS_PIPE.receive_message:1 =
2005-05-10 17:29:49,003 DEBUG [Thread-1] =
backgroundProcess.ReaderLogDataBase (Re aderLogDataBase.sqlj:210) - Nbr =
line read in logSource:source1 : 0 =20
---------------------------------------------------
You can see that the DBMS pipe name is the default and that's the same =
in the PLOGPARAM package.
By inserting some debug code to the PLOG.LOG procedure I noticed that it =
actually writes to the pipe (the following code is executed and ret is =
0).
ret :=3D DBMS_PIPE.send_message(pCTX.DBMS_PIPE_NAME); =20
IF RET <> 0 then
raise_application_error(ERR_CODE_DBMS_PIPE, =
MES_CODE_DBMS_PIPE || RET);
END IF; =20
But the "DBMS_PIPE.receive_message:1" message seems to mean that the =
listener process finds no message in the pipe. Am I right ?
Do you know where it comes from ?
|
|
From: <log...@li...> - 2005-05-10 05:57:53
|
=20
Hi Guillaume,
=20
Thanks a lot for the help. We are now able to successfully install and =
test with log4plsql.
Thanks and Regards,
Ramalingam.R
Project Manager
Ph: +91 44 24483151 /52
Fax: +91 44 2448 3157
Mobile: +91-98410-41609
Email: ram...@in... =20
Ram...@ge... =20
-----Original Message-----
From: MOULARD Guillaume ROSI/DPS =
[mailto:gui...@fr...]
Sent: Monday, May 09, 2005 6:39 PM
To: log...@li...
Subject: [SPAM_EMAIL] - RE: [log4plsql] Log4PLSQl in 9i - Email has =
different SMTP TO: and MIME TO: fields in the email addresses
Yes, there is no problem.
=20
Please check your OracleVersion variable in setVariable.bat file.
=20
set OracleVersion=3D9.2
=20
because in 9i is nessesary to use a sysdba connection.
=20
Let me know if you have some problem (with yours install.log file).=20
=20
Guillaume.=20
=20
_____ =20
De : log...@li... =
[mailto:log...@li...]=20
Envoy=E9 : lundi 9 mai 2005 10:08
=C0 : Log...@li...
Cc : gmo...@us...
Objet : [log4plsql] Log4PLSQl in 9i
Hi,
=20
A simple question....Could you please help me to confirm if the =
Log4Plsql works in 9i environment.
=20
Thanks and Regards,
Ramalingam.R
Project Manager
Ph: +91 44 24483151 /52
Fax: +91 44 2448 3157
Mobile: +91-98410-41609
Email: ram...@in... =20
Ram...@ge... =20
=20
|
|
From: <log...@li...> - 2005-05-09 13:12:36
|
Yes, there is no problem.
=20
Please check your OracleVersion variable in setVariable.bat file.
=20
set OracleVersion=3D9.2
=20
because in 9i is nessesary to use a sysdba connection.
=20
Let me know if you have some problem (with yours install.log file).=20
=20
Guillaume.=20
=20
_____ =20
De : log...@li...
[mailto:log...@li...]=20
Envoy=E9 : lundi 9 mai 2005 10:08
=C0 : Log...@li...
Cc : gmo...@us...
Objet : [log4plsql] Log4PLSQl in 9i
Hi,
=20
A simple question....Could you please help me to confirm if the =
Log4Plsql
works in 9i environment.
=20
Thanks and Regards,
Ramalingam.R
Project Manager
Ph: +91 44 24483151 /52
Fax: +91 44 2448 3157
Mobile: +91-98410-41609
Email: ram...@in... =20
Ram...@ge... =20
=20
|
|
From: <log...@li...> - 2005-05-09 08:08:31
|
Hi,
=20
A simple question....Could you please help me to confirm if the =
Log4Plsql works in 9i environment.
=20
Thanks and Regards,
Ramalingam.R
Project Manager
Ph: +91 44 24483151 /52
Fax: +91 44 2448 3157
Mobile: +91-98410-41609
Email: ram...@in... =20
Ram...@ge... =20
=20
|
|
From: <log...@li...> - 2005-05-04 08:02:52
|
Good morning, I downloaded log4plsql utility and tested it, especially the ability to send log messages to the ORACLE pipe and process them by Log4JbackgroundProcess process. I found out that Log4JbackgroundProcess in current version is not compatible with PLOG package. The PLOG package creates pipe message in different structure. Some parameters have different type than is expected in Log4JbackgroundProcess (for example piped_LDATE is defined like String but the pipe message contains type Date). Do You know if there is available some newer version, that solve this problem? Thank You. Vladimir Kocur mailto:vla...@ne... |
|
From: <log...@li...> - 2005-03-17 10:13:52
|
Hi Vijay,
You can use=20
------------
log([LOG_CTX, ]TLOG.LLEVEL%type|TLOGLEVEL.LCODE%type [, Mess])
------------
Ex:
plog.log (LERROR , 'my Application error');=20
plog.log ('ERROR' , 'my Application error');=20
With:=20
-- The OFF has the highest possible rank and is intended to turn off
logging.
LOFF CONSTANT number :=3D 10 ;
-- The FATAL level designates very severe error events that will =
presumably
lead the application to abort.
LFATAL CONSTANT number :=3D 20 ;
-- The ERROR level designates error events that might still allow the
application to continue running.
LERROR CONSTANT number :=3D 30 ;
-- The WARN level designates potentially harmful situations.
LWARN CONSTANT number :=3D 40 ;
-- The INFO level designates informational messages that highlight the
progress of the application at coarse-grained level.
LINFO CONSTANT number :=3D 50 ;
-- The DEBUG Level designates fine-grained informational events that are
most useful to debug an application.
LDEBUG CONSTANT number :=3D 60 ;
-- The ALL has the lowest possible rank and is intended to turn on all
logging.
LALL CONSTANT number :=3D 70 ;
Or if you have define some other log level
plog.log ('AppError' , 'my Application error');=20
See : =
http://log4plsql.sourceforge.net/docs/UserGuideDOC.html#_Toc67467113
=20
Cordialement / Regards,
Guillaume Moulard
-----Message d'origine-----
De : Vijay Jain =20
Envoy=E9 : jeudi 17 mars 2005 10:49
=C0 : gmo...@us...
Objet : Help required in Log4plsql : setting the logging level
Hi Guillaume,
Please forgive me if this mail is not intentd to you.
I am trying to do the set up for the Log4plsql. Here I have 10 =
procedures in
which I've written different log stetment for various scenarios (for =
dubug,
fatal, info etc.). I want to change the logging level without making any
changes to these procedures. Can you please tell me where should I make =
the
changes so that the logging level can be changed dynamically?
Thanks,
Vijay
Mangalore-India
|
|
From: <log...@li...> - 2005-03-07 10:12:17
|
<mailto:log...@li...> Hi All, I read about log4plsql and wanted to use the same. I dowloaded the version 3.12 in zip format "Log4plsqlV3121.zip" But I have a problem configruing the same. I did change the log4plsql.xml to point to my DB.. I was also able to strat the "startLog4JbackgroundProcess.bat" But when I try to log using PLOG my procedure throws exception saying that the state of the paca\kage has chained.. Any help please.. Any detailed documentation on configuration would be of great help... thanks and regards.. -Ravi |
|
From: <log...@li...> - 2005-01-31 18:07:22
|
Hi,
=20
For you requiment, in this version, is necessary to use one custom =
context.=20
You can update the logging level at runtime dynamically
=20
pCTX PLOG.LOG_CTX :=3D PLOG.init (pLEVEL =3D> PLOG.LDEBUG);
=20
Regard,
=20
Guillaume.
_____ =20
De : log...@li...
[mailto:log...@li...]=20
Envoy=E9 : lundi 31 janvier 2005 13:01
=C0 : log...@li...
Objet : [log4plsql] Small addition to the application to allow for =
runtime
change of loglevel.
HI all,
=20
I have recently used the <http://log4plsql.sourceforge.net/> LOG4PLSQL
software for logging in a small application. I missed the possibility to
change the logging level at runtime. In the production environment code
changes are only allowed during specified deploy time windows, so =
changing
the DEFAULT_LEVEL parameter in the PLOGPARAM package specification was =
not
an option to change the logging level.
=20
See http://technology.amis.nl/blog/wp-trackback.php/352 for the source =
code
of the changes.
=20
Rgds
Dick Dijkshoorn.=20
|
|
From: <log...@li...> - 2005-01-31 12:02:32
|
HI all, =20 I have recently used the LOG4PLSQL software <http://log4plsql.sourceforge.net/> for logging in a small application. I missed the possibility to change the logging level at runtime. In the production environment code changes are only allowed during specified deploy time windows, so changing the DEFAULT_LEVEL parameter in the PLOGPARAM package specification was not an option to change the logging level. =20 See http://technology.amis.nl/blog/wp-trackback.php/352 for the source code of the changes. =20 Rgds Dick Dijkshoorn.=20 |
|
From: <log...@li...> - 2004-12-18 14:02:43
|
Carol, Unfortunly, I think only in first release guillaume -----Message d'origine----- De: "log...@li..."<log...@li...> Env: 17/12/2004 21:57:53 À: "log...@li..."<log...@li...> Cc: Objet: [log4plsql] Compatibility Is LOG4PLSQL compatible with Oracle version 7.3? Carol This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Any confidentiality or privilege is not waived or lost if this e-mail has been sent to you by mistake. |
|
From: <log...@li...> - 2004-12-17 21:05:05
|
Is LOG4PLSQL compatible with Oracle version 7.3? =20 Carol =20 This email may contain confidential and privileged material for the sole = use of the intended recipient(s). Any review, use, distribution or = disclosure by others is strictly prohibited. If you are not the intended = recipient (or authorized to receive for the recipient), please contact = the sender by reply email and delete all copies of this message. Any = confidentiality or privilege is not waived or lost if this e-mail has = been sent to you by mistake.=20 |
|
From: <log...@li...> - 2004-12-14 10:44:49
|
Hi Guillaume,
sorry i was so lazy not to post my approach to the idea: (Which is what
you proposed)
DELETE tlog
WHERE tlog.lsection LIKE plogcontext_name || '%' OR
tlog.lsection IS NULL;
Is use the "tlog.lsection is null" just because i have occurences of 3
rows for every logging session in tlog with a NULL Sextion.
As i am defining a plogcontext_name for every log purpose, sometimes with
an attached username as i use log4plsql in a multi user environment, it is
possible to delete just the section-tree belongin to one plsql program
(plogcontext_name), sometimes including the username, so it just deletes
the log for the currently running process of one user.
I think this works great, but i would like to have it in the plog package
:o)
Michael
log...@li...
14.12.2004 05:02
Bitte antworten an log4plsql-all-info
Mobile : unbekannt / Phone : unbekannt / Fax : unbekannt
An log...@li...
Kopie
Thema Log4plsql-all-info digest, Vol 1 #74 - 2 msgs [Virus
checked]
Send Log4plsql-all-info mailing list submissions to
log...@li...
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info
or, via email, send a message with subject or body 'help' to
log...@li...
You can reach the person managing the list at
log...@li...
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Log4plsql-all-info digest..."
Today's Topics:
1. Enhancement/Change on purge with given context
(log...@li...)
2. RE: Enhancement/Change on purge with given context
(log...@li...)
--__--__--
Message: 1
To: log...@li...
Date: Mon, 13 Dec 2004 18:12:42 +0100
From: log...@li...
Subject: [log4plsql] Enhancement/Change on purge with given context
Reply-To: log...@li...
Dies ist eine mehrteilige Nachricht im MIME-Format.
--=_alternative 005E8BC5C1256F69_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi and thanks for the work put into log4plsql!
In my work it's getting a more and more important and convenient way to=20
log technical information e.g. in plsql-migration-tools.
As i already use it simultaneously for different purposes, i would have=20
expected to have purge(pctx) work just on the given context - so my
other=20
logs would not be lost.
As purge does just a complete deletion of all log records i would=20
appreciate e.g. a log variant where purge just deletes all records of
the=20
given context (as i have written for myself for a special purpose).
What do you think of this enhancement?
Best Regards,
Michael Rinus
E- Plus Mobilfunk GmbH & Co. KG
D=FCsseldorf
--=_alternative 005E8BC5C1256F69_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
<br><font size=3D2 face=3D"sans-serif">Hi and thanks for the work put into
log4plsql!</font>
<br>
<br><font size=3D2 face=3D"sans-serif">In my work it's getting a more and
m=
ore
important and convenient way to log technical information e.g. in
plsql-mig=
ration-tools.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">As i already use it simultaneously
f=
or
different purposes, i would have expected to have purge(pctx) work just
on the given context - so my other logs would not be lost.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">As purge does just a complete
deleti=
on
of all log records i would appreciate e.g. a log variant where purge just
deletes all records of the given context (as i have written for myself
for a special purpose).</font>
<br>
<br><font size=3D2 face=3D"sans-serif">What do you think of this
enhancemen=
t?</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Best Regards,</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Michael Rinus</font>
<br><font size=3D2 face=3D"sans-serif">E- Plus Mobilfunk GmbH & Co.
KG<=
/font>
<br><font size=3D2 face=3D"sans-serif">D=FCsseldorf</font>
--=_alternative 005E8BC5C1256F69_=--
--__--__--
Message: 2
To: <log...@li...>
Subject: RE: [log4plsql] Enhancement/Change on purge with given context
Date: Mon, 13 Dec 2004 20:31:15 +0100
Organization: france telecom
From: log...@li...
Reply-To: log...@li...
C'est un message de format MIME en plusieurs parties.
------=_NextPart_000_0164_01C4E152.B1B232B0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Hi Michael,
Thank for your proposition,=20
Currently is not possible to identify witch log is created by one =
context.
Perapse, is possible to delete on the table the log create for one level =
or
for one section tree.=20
You think is interesting for yours log4plsql use?
Guillaume=20
=20
_____ =20
De : log...@li...
[mailto:log...@li...]=20
Envoy=E9 : lundi 13 d=E9cembre 2004 18:13
=C0 : log...@li...
Objet : [log4plsql] Enhancement/Change on purge with given context
=20
Hi and thanks for the work put into log4plsql!=20
In my work it's getting a more and more important and convenient way to =
log
technical information e.g. in plsql-migration-tools.=20
As i already use it simultaneously for different purposes, i would have
expected to have purge(pctx) work just on the given context - so my =
other
logs would not be lost.=20
As purge does just a complete deletion of all log records i would =
appreciate
e.g. a log variant where purge just deletes all records of the given =
context
(as i have written for myself for a special purpose).=20
What do you think of this enhancement?=20
Best Regards,=20
Michael Rinus=20
E- Plus Mobilfunk GmbH & Co. KG=20
D=FCsseldorf
------=_NextPart_000_0164_01C4E152.B1B232B0
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DWindows-1252">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Arial Black";
panose-1:2 11 10 4 2 1 2 2 2 4;}
@font-face
{font-family:"Book Antiqua";
panose-1:2 4 6 2 5 3 5 3 3 4;}
@font-face
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;}
@font-face
{font-family:"\@Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:sans-serif;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
h1
{margin-top:0cm;
margin-right:0cm;
margin-bottom:24.0pt;
margin-left:21.55pt;
text-indent:-21.55pt;
page-break-before:always;
mso-list:l14 level1 lfo14;
font-size:16.0pt;
font-family:Arial;
color:red;
font-weight:bold;}
h2
{margin-top:0cm;
margin-right:5.0cm;
margin-bottom:6.0pt;
margin-left:28.8pt;
text-indent:-28.8pt;
mso-list:l14 level2 lfo2;
border:none;
padding:0cm;
font-size:11.0pt;
font-family:Arial;
color:blue;
font-weight:bold;}
h3
{margin-top:12.0pt;
margin-right:0cm;
margin-bottom:3.0pt;
margin-left:36.0pt;
text-indent:-36.0pt;
mso-list:l14 level3 lfo15;
font-size:10.0pt;
font-family:Helvetica;
color:green;
font-weight:bold;
font-style:italic;}
h4
{margin-top:12.0pt;
margin-right:0cm;
margin-bottom:3.0pt;
margin-left:43.2pt;
text-indent:-43.2pt;
page-break-after:avoid;
mso-list:l14 level4 lfo16;
font-size:14.0pt;
font-family:"Times New Roman";
font-weight:bold;}
h5
{margin-top:12.0pt;
margin-right:0cm;
margin-bottom:3.0pt;
margin-left:50.4pt;
text-indent:-50.4pt;
mso-list:l14 level5 lfo17;
font-size:13.0pt;
font-family:"Times New Roman";
font-weight:bold;
font-style:italic;}
h6
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:57.6pt;
margin-bottom:.0001pt;
text-indent:-57.6pt;
page-break-after:avoid;
mso-list:l14 level6 lfo18;
font-size:11.0pt;
font-family:"Times New Roman";
font-weight:normal;
font-style:italic;}
p.MsoHeading7, li.MsoHeading7, div.MsoHeading7
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:64.8pt;
margin-bottom:.0001pt;
text-indent:-64.8pt;
page-break-after:avoid;
mso-list:l14 level7 lfo19;
font-size:11.0pt;
font-family:"Times New Roman";
font-weight:bold;}
p.MsoHeading8, li.MsoHeading8, div.MsoHeading8
{margin-top:12.0pt;
margin-right:0cm;
margin-bottom:3.0pt;
margin-left:72.0pt;
text-indent:-72.0pt;
mso-list:l14 level8 lfo20;
font-size:10.0pt;
font-family:Arial;
font-style:italic;}
p.MsoHeading9, li.MsoHeading9, div.MsoHeading9
{margin-top:12.0pt;
margin-right:0cm;
margin-bottom:3.0pt;
margin-left:79.2pt;
text-indent:-79.2pt;
mso-list:l14 level9 lfo21;
font-size:9.0pt;
font-family:Arial;
font-weight:bold;
font-style:italic;}
p.MsoIndex1, li.MsoIndex1, div.MsoIndex1
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:12.0pt;
margin-bottom:.0001pt;
text-indent:-12.0pt;
font-size:9.0pt;
font-family:"Times New Roman";}
p.MsoIndex2, li.MsoIndex2, div.MsoIndex2
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:24.0pt;
margin-bottom:.0001pt;
text-indent:-12.0pt;
font-size:9.0pt;
font-family:"Times New Roman";}
p.MsoIndex3, li.MsoIndex3, div.MsoIndex3
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:33.0pt;
margin-bottom:.0001pt;
text-indent:-11.0pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoIndex4, li.MsoIndex4, div.MsoIndex4
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:44.0pt;
margin-bottom:.0001pt;
text-indent:-11.0pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoIndex5, li.MsoIndex5, div.MsoIndex5
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:55.0pt;
margin-bottom:.0001pt;
text-indent:-11.0pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoIndex6, li.MsoIndex6, div.MsoIndex6
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:66.0pt;
margin-bottom:.0001pt;
text-indent:-11.0pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoIndex7, li.MsoIndex7, div.MsoIndex7
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:77.0pt;
margin-bottom:.0001pt;
text-indent:-11.0pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoIndex8, li.MsoIndex8, div.MsoIndex8
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:88.0pt;
margin-bottom:.0001pt;
text-indent:-11.0pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoIndex9, li.MsoIndex9, div.MsoIndex9
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:99.0pt;
margin-bottom:.0001pt;
text-indent:-11.0pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoToc1, li.MsoToc1, div.MsoToc1
{margin-top:4.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:Arial;
color:red;}
p.MsoToc2, li.MsoToc2, div.MsoToc2
{margin-top:1.0pt;
margin-right:0cm;
margin-bottom:1.0pt;
margin-left:8.5pt;
font-size:10.0pt;
font-family:Arial;
color:blue;}
p.MsoToc3, li.MsoToc3, div.MsoToc3
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:17.0pt;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:Arial;
color:green;}
p.MsoToc4, li.MsoToc4, div.MsoToc4
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:33.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoToc5, li.MsoToc5, div.MsoToc5
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:48.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoToc6, li.MsoToc6, div.MsoToc6
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:60.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoToc7, li.MsoToc7, div.MsoToc7
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:72.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoToc8, li.MsoToc8, div.MsoToc8
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:84.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoToc9, li.MsoToc9, div.MsoToc9
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:96.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoNormalIndent, li.MsoNormalIndent, div.MsoNormalIndent
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:35.4pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoFootnoteText, li.MsoFootnoteText, div.MsoFootnoteText
{margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman";}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:3.4pt;
margin-bottom:.0001pt;
font-size:18.0pt;
font-family:"Times New Roman";
color:black;
font-weight:bold;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoFooter, li.MsoFooter, div.MsoFooter
{margin:0cm;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:Arial;}
p.MsoIndexHeading, li.MsoIndexHeading, div.MsoIndexHeading
{margin-top:18.0pt;
margin-right:0cm;
margin-bottom:12.0pt;
margin-left:0cm;
border:none;
padding:0cm;
font-size:13.0pt;
font-family:"Times New Roman";
font-weight:bold;
font-style:italic;}
p.MsoCaption, li.MsoCaption, div.MsoCaption
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:0cm;
font-size:11.0pt;
font-family:"Times New Roman";
font-weight:bold;}
p.MsoTof, li.MsoTof, div.MsoTof
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:22.0pt;
margin-bottom:.0001pt;
text-indent:-22.0pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoEnvelopeAddress, li.MsoEnvelopeAddress, div.MsoEnvelopeAddress
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:5.0cm;
margin-bottom:.0001pt;
mso-element:frame;
font-size:12.0pt;
font-family:Arial;}
p.MsoEnvelopeReturn, li.MsoEnvelopeReturn, div.MsoEnvelopeReturn
{margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:Arial;}
p.MsoEndnoteText, li.MsoEndnoteText, div.MsoEndnoteText
{margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman";}
p.MsoToa, li.MsoToa, div.MsoToa
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:11.0pt;
margin-bottom:.0001pt;
text-indent:-11.0pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoMacroText, li.MsoMacroText, div.MsoMacroText
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:-2.85pt;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoList, li.MsoList, div.MsoList
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:14.15pt;
margin-bottom:.0001pt;
text-indent:-14.15pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListBullet, li.MsoListBullet, div.MsoListBullet
{margin-top:2.0pt;
margin-right:0cm;
margin-bottom:2.0pt;
margin-left:18.0pt;
text-indent:-18.0pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListNumber, li.MsoListNumber, div.MsoListNumber
{margin-top:2.0pt;
margin-right:0cm;
margin-bottom:2.0pt;
margin-left:19.85pt;
text-indent:-17.0pt;
mso-list:l11 level1 lfo4;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoList2, li.MsoList2, div.MsoList2
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:28.3pt;
margin-bottom:.0001pt;
text-indent:-14.15pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoList3, li.MsoList3, div.MsoList3
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:42.45pt;
margin-bottom:.0001pt;
text-indent:-14.15pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoList4, li.MsoList4, div.MsoList4
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:56.6pt;
margin-bottom:.0001pt;
text-indent:-14.15pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoList5, li.MsoList5, div.MsoList5
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:70.75pt;
margin-bottom:.0001pt;
text-indent:-14.15pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListBullet2, li.MsoListBullet2, div.MsoListBullet2
{margin-top:1.0pt;
margin-right:0cm;
margin-bottom:1.0pt;
margin-left:34.05pt;
text-indent:-14.2pt;
mso-list:l9 level1 lfo9;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListBullet3, li.MsoListBullet3, div.MsoListBullet3
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:46.3pt;
margin-bottom:.0001pt;
text-indent:-18.0pt;
mso-list:l6 level1 lfo10;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListBullet4, li.MsoListBullet4, div.MsoListBullet4
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:60.45pt;
margin-bottom:.0001pt;
text-indent:-18.0pt;
mso-list:l5 level1 lfo11;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListBullet5, li.MsoListBullet5, div.MsoListBullet5
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:74.6pt;
margin-bottom:.0001pt;
text-indent:-18.0pt;
mso-list:l4 level1 lfo12;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListNumber2, li.MsoListNumber2, div.MsoListNumber2
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:32.15pt;
margin-bottom:.0001pt;
text-indent:-18.0pt;
mso-list:l3 level1 lfo5;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListNumber3, li.MsoListNumber3, div.MsoListNumber3
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:46.3pt;
margin-bottom:.0001pt;
text-indent:-18.0pt;
mso-list:l2 level1 lfo6;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListNumber4, li.MsoListNumber4, div.MsoListNumber4
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:60.45pt;
margin-bottom:.0001pt;
text-indent:-18.0pt;
mso-list:l1 level1 lfo7;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListNumber5, li.MsoListNumber5, div.MsoListNumber5
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:74.6pt;
margin-bottom:.0001pt;
text-indent:-18.0pt;
mso-list:l0 level1 lfo8;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoTitle, li.MsoTitle, div.MsoTitle
{margin-top:12.0pt;
margin-right:0cm;
margin-bottom:3.0pt;
margin-left:0cm;
text-align:center;
font-size:16.0pt;
font-family:Arial;
font-weight:bold;}
p.MsoClosing, li.MsoClosing, div.MsoClosing
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:212.6pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoSignature, li.MsoSignature, div.MsoSignature
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:212.6pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman";}
p.MsoBodyTextIndent, li.MsoBodyTextIndent, div.MsoBodyTextIndent
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListContinue, li.MsoListContinue, div.MsoListContinue
{margin-top:0cm;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:14.15pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListContinue2, li.MsoListContinue2, div.MsoListContinue2
{margin-top:0cm;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:28.3pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListContinue3, li.MsoListContinue3, div.MsoListContinue3
{margin-top:0cm;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:42.45pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListContinue4, li.MsoListContinue4, div.MsoListContinue4
{margin-top:0cm;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:56.6pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoListContinue5, li.MsoListContinue5, div.MsoListContinue5
{margin-top:0cm;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:70.75pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoMessageHeader, li.MsoMessageHeader, div.MsoMessageHeader
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:2.0cm;
margin-bottom:.0001pt;
text-indent:-2.0cm;
background:#CCCCCC;
border:none;
padding:0cm;
font-size:12.0pt;
font-family:Arial;}
p.MsoSubtitle, li.MsoSubtitle, div.MsoSubtitle
{margin-top:0cm;
margin-right:0cm;
margin-bottom:3.0pt;
margin-left:0cm;
text-align:center;
font-size:12.0pt;
font-family:Arial;}
p.MsoSalutation, li.MsoSalutation, div.MsoSalutation
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoDate, li.MsoDate, div.MsoDate
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoBodyTextFirstIndent, li.MsoBodyTextFirstIndent, =
div.MsoBodyTextFirstIndent
{margin-top:0cm;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:-2.85pt;
text-indent:10.5pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoBodyTextFirstIndent2, li.MsoBodyTextFirstIndent2, =
div.MsoBodyTextFirstIndent2
{margin-top:0cm;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:14.15pt;
text-indent:10.5pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoBodyText2, li.MsoBodyText2, div.MsoBodyText2
{margin:0cm;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:"Times New Roman";}
p.MsoBodyText3, li.MsoBodyText3, div.MsoBodyText3
{margin-top:0cm;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:0cm;
font-size:8.0pt;
font-family:"Times New Roman";}
p.MsoBodyTextIndent2, li.MsoBodyTextIndent2, div.MsoBodyTextIndent2
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:17.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoBodyTextIndent3, li.MsoBodyTextIndent3, div.MsoBodyTextIndent3
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.MsoBlockText, li.MsoBlockText, div.MsoBlockText
{margin-top:78.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
text-align:center;
font-size:22.0pt;
font-family:Helvetica;
color:blue;
font-weight:bold;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p.MsoDocumentMap, li.MsoDocumentMap, div.MsoDocumentMap
{margin:0cm;
margin-bottom:.0001pt;
background:navy;
font-size:11.0pt;
font-family:Tahoma;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p
{mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Arial Unicode MS";}
address
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";
font-style:italic;}
pre
{margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:Tahoma;}
p.Chapitre, li.Chapitre, div.Chapitre
{margin:0cm;
margin-bottom:.0001pt;
font-size:20.0pt;
font-family:Arial;
color:black;
font-weight:bold;}
span.Date-doc
{font-family:Arial;
color:black;}
p.diffusion, li.diffusion, div.diffusion
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:17.0pt;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:Arial;
color:black;}
p.entet, li.entet, div.entet
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:Helvetica;}
p.entete, li.entete, div.entete
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:Arial;
color:black;
letter-spacing:2.7pt;
font-weight:bold;}
p.En-ttetableau, li.En-ttetableau, div.En-ttetableau
{margin-top:3.0pt;
margin-right:0cm;
margin-bottom:3.0pt;
margin-left:3.7pt;
font-size:10.0pt;
font-family:Arial;
font-weight:bold;}
p.entetepage, li.entetepage, div.entetepage
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:Helvetica;
color:black;}
p.Etape, li.Etape, div.Etape
{margin-top:3.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
text-align:center;
font-size:11.0pt;
font-family:Arial;
font-weight:bold;}
p.Textefragment, li.Textefragment, div.Textefragment
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:2.85pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.Fragsb, li.Fragsb, div.Fragsb
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:2.0pt;
margin-left:18.0pt;
text-indent:-18.0pt;
mso-list:l13 level1 lfo1;
font-size:11.0pt;
font-family:"Times New Roman";}
p.Fragmentsuite, li.Fragmentsuite, div.Fragmentsuite
{margin-top:6.0pt;
margin-right:5.0cm;
margin-bottom:6.0pt;
margin-left:28.8pt;
text-indent:-28.8pt;
border:none;
padding:0cm;
font-size:11.0pt;
font-family:Arial;
color:blue;
font-weight:bold;}
p.Fragment, li.Fragment, div.Fragment
{margin-top:0cm;
margin-right:5.0cm;
margin-bottom:12.0pt;
margin-left:28.8pt;
text-indent:-28.8pt;
border:none;
padding:0cm;
font-size:11.0pt;
font-family:Arial;
color:blue;
font-weight:bold;}
p.Guide, li.Guide, div.Guide
{margin-top:3.0pt;
margin-right:0cm;
margin-bottom:12.0pt;
margin-left:18.0pt;
text-indent:-18.0pt;
mso-list:l7 level1 lfo3;
font-size:11.0pt;
font-family:"Times New Roman";}
span.HighlightedVariable
{color:blue;}
p.Indextableau, li.Indextableau, div.Indextableau
{margin-top:3.0pt;
margin-right:10.75pt;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
text-align:right;
font-size:10.0pt;
font-family:Arial;
font-weight:bold;
font-style:italic;}
p.interligne, li.interligne, div.interligne
{margin:0cm;
margin-bottom:.0001pt;
line-height:150%;
font-size:12.0pt;
font-family:"Times New Roman";}
p.libell, li.libell, div.libell
{margin-top:3.0pt;
margin-right:10.6pt;
margin-bottom:3.0pt;
margin-left:3.45pt;
text-align:right;
font-size:10.0pt;
font-family:Arial;
font-weight:bold;
font-style:italic;}
p.Listeit, li.Listeit, div.Listeit
{margin-top:0cm;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:74.55pt;
text-indent:-17.85pt;
mso-list:l12 level1 lfo13;
font-size:12.0pt;
font-family:"Times New Roman";}
p.listepucetr, li.listepucetr, div.listepucetr
{margin-top:2.0pt;
margin-right:0cm;
margin-bottom:2.0pt;
margin-left:34.85pt;
text-indent:-17.85pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.Manuelrfrence, li.Manuelrfrence, div.Manuelrfrence
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.Module, li.Module, div.Module
{margin-top:4.0pt;
margin-right:0cm;
margin-bottom:15.0pt;
margin-left:0cm;
font-size:16.0pt;
font-family:Arial;
color:red;
font-weight:bold;}
p.Modulesuite, li.Modulesuite, div.Modulesuite
{margin-top:4.0pt;
margin-right:0cm;
margin-bottom:15.0pt;
margin-left:0cm;
page-break-before:always;
page-break-after:avoid;
font-size:16.0pt;
font-family:Arial;
color:red;
font-weight:bold;}
span.NVersion
{font-family:Arial;}
p.nomprojet, li.nomprojet, div.nomprojet
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
font-size:22.0pt;
font-family:Arial;
color:blue;
font-weight:bold;}
p.reference, li.reference, div.reference
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:2.85pt;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:Arial;
color:navy;
font-weight:bold;}
span.Rfrence
{font-family:Arial;
color:black;}
p.Sfragment, li.Sfragment, div.Sfragment
{margin-top:6.0pt;
margin-right:4.25pt;
margin-bottom:3.0pt;
margin-left:25.25pt;
text-indent:-25.25pt;
font-size:10.0pt;
font-family:Arial;
color:green;
font-weight:bold;
font-style:italic;}
p.SfragmentSup, li.SfragmentSup, div.SfragmentSup
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:3.0pt;
margin-left:22.7pt;
font-size:10.0pt;
font-family:Arial;
color:green;}
p.Sommaire, li.Sommaire, div.Sommaire
{margin-top:0cm;
margin-right:0cm;
margin-bottom:18.0pt;
margin-left:0cm;
text-align:justify;
page-break-before:always;
font-size:16.0pt;
font-family:Arial;
color:black;
font-weight:bold;}
p.Standard, li.Standard, div.Standard
{margin:0cm;
margin-bottom:.0001pt;
text-align:justify;
text-indent:1.0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
p.Tabledesmatires, li.Tabledesmatires, div.Tabledesmatires
{margin-top:0cm;
margin-right:0cm;
margin-bottom:12.0pt;
margin-left:.85pt;
font-size:16.0pt;
font-family:"Arial Black";
color:red;}
p.TableText, li.TableText, div.TableText
{margin:0cm;
margin-bottom:.0001pt;
punctuation-wrap:simple;
text-autospace:none;
font-size:8.0pt;
font-family:"Book Antiqua";}
p.TableHeading, li.TableHeading, div.TableHeading
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:0cm;
punctuation-wrap:simple;
text-autospace:none;
font-size:8.0pt;
font-family:"Book Antiqua";
font-weight:bold;}
p.tech2, li.tech2, div.tech2
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:12.0pt;
margin-left:0cm;
font-size:36.0pt;
font-family:Arial;
color:red;
text-shadow:auto;}
p.Textetableau, li.Textetableau, div.Textetableau
{margin-top:3.0pt;
margin-right:3.7pt;
margin-bottom:3.0pt;
margin-left:3.7pt;
font-size:11.0pt;
font-family:Arial;}
p.Code, li.Code, div.Code
{margin:0cm;
margin-bottom:.0001pt;
border:none;
padding:0cm;
font-size:8.0pt;
font-family:"Courier New";}
p.Source, li.Source, div.Source
{margin:0cm;
margin-bottom:.0001pt;
border:none;
padding:0cm;
font-size:9.0pt;
font-family:"Courier New";}
p.Titredechapitre, li.Titredechapitre, div.Titredechapitre
{margin-top:0cm;
margin-right:5.0cm;
margin-bottom:30.0pt;
margin-left:0cm;
text-indent:-18.0pt;
page-break-before:always;
mso-list:l10 level2 lfo22;
border:none;
padding:0cm;
font-size:20.0pt;
font-family:"Arial Black";
color:black;
font-weight:bold;}
p.Titre-document, li.Titre-document, div.Titre-document
{margin-top:54.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
text-align:center;
font-size:22.0pt;
font-family:Arial;
color:blue;
font-weight:bold;}
span.Titre-projet
{font-family:Arial;
color:blue;
font-weight:bold;}
p.TM4, li.TM4, div.TM4
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:120.4pt;
margin-bottom:.0001pt;
text-indent:-32.4pt;
mso-list:l8 level4 lfo23;
font-size:10.0pt;
font-family:"Times New Roman";
color:green;}
span.Type-document
{font-family:Arial;
color:gray;
font-weight:bold;}
span.EmailStyle136
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
/* Page Definitions */
@page
{mso-endnote-separator:url("cid:header.htm\@01C4E152.B1984210") es;
=
mso-endnote-continuation-separator:url("cid:header.htm\@01C4E152.B1984210=
") ecs;}
@page Section1
{size:595.3pt 841.9pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;
mso-footer:url("cid:header.htm\@01C4E152.B1984210") f1;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:-132;
mso-list-type:simple;
mso-list-template-ids:-1689120310;}
@list l0:level1
{mso-level-style-link:"Liste =E0 num=E9ros 5";
mso-level-tab-stop:74.6pt;
mso-level-number-position:left;
margin-left:74.6pt;
text-indent:-18.0pt;}
@list l1
{mso-list-id:-131;
mso-list-type:simple;
mso-list-template-ids:1498845350;}
@list l1:level1
{mso-level-style-link:"Liste =E0 num=E9ros 4";
mso-level-tab-stop:60.45pt;
mso-level-number-position:left;
margin-left:60.45pt;
text-indent:-18.0pt;}
@list l2
{mso-list-id:-130;
mso-list-type:simple;
mso-list-template-ids:-2142633324;}
@list l2:level1
{mso-level-style-link:"Liste =E0 num=E9ros 3";
mso-level-tab-stop:46.3pt;
mso-level-number-position:left;
margin-left:46.3pt;
text-indent:-18.0pt;}
@list l3
{mso-list-id:-129;
mso-list-type:simple;
mso-list-template-ids:206619086;}
@list l3:level1
{mso-level-style-link:"Liste =E0 num=E9ros 2";
mso-level-tab-stop:32.15pt;
mso-level-number-position:left;
margin-left:32.15pt;
text-indent:-18.0pt;}
@list l4
{mso-list-id:-128;
mso-list-type:simple;
mso-list-template-ids:1378678722;}
@list l4:level1
{mso-level-number-format:bullet;
mso-level-style-link:"Liste =E0 puces 5";
mso-level-text:\F0B7;
mso-level-tab-stop:74.6pt;
mso-level-number-position:left;
margin-left:74.6pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l5
{mso-list-id:-127;
mso-list-type:simple;
mso-list-template-ids:-1105936992;}
@list l5:level1
{mso-level-number-format:bullet;
mso-level-style-link:"Liste =E0 puces 4";
mso-level-text:\F0B7;
mso-level-tab-stop:60.45pt;
mso-level-number-position:left;
margin-left:60.45pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l6
{mso-list-id:-126;
mso-list-type:simple;
mso-list-template-ids:148657438;}
@list l6:level1
{mso-level-number-format:bullet;
mso-level-style-link:"Liste =E0 puces 3";
mso-level-text:\F0B7;
mso-level-tab-stop:46.3pt;
mso-level-number-position:left;
margin-left:46.3pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l7
{mso-list-id:38433194;
mso-list-type:simple;
mso-list-template-ids:-1796338000;}
@list l7:level1
{mso-level-number-format:bullet;
mso-level-style-link:Guide;
mso-level-text:\F026;
mso-level-tab-stop:18.0pt;
mso-level-number-position:left;
margin-left:18.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l8
{mso-list-id:96828900;
mso-list-template-ids:-1492623642;}
@list l8:level1
{mso-level-tab-stop:70.0pt;
mso-level-number-position:left;
margin-left:52.0pt;
text-indent:-18.0pt;}
@list l8:level2
{mso-level-text:"%1\.%2\.";
mso-level-tab-stop:124.0pt;
mso-level-number-position:left;
margin-left:73.6pt;
text-indent:-21.6pt;}
@list l8:level3
{mso-level-text:"%1\.%2\.%3\.";
mso-level-tab-stop:160.0pt;
mso-level-number-position:left;
margin-left:95.2pt;
text-indent:-25.2pt;}
@list l8:level4
{mso-level-style-link:TM4;
mso-level-text:"%1\.%2\.%3\.%4\.";
mso-level-tab-stop:214.0pt;
mso-level-number-position:left;
margin-left:120.4pt;
text-indent:-32.4pt;}
@list l8:level5
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.";
mso-level-tab-stop:268.0pt;
mso-level-number-position:left;
margin-left:145.6pt;
text-indent:-39.6pt;}
@list l8:level6
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.";
mso-level-tab-stop:304.0pt;
mso-level-number-position:left;
margin-left:170.8pt;
text-indent:-46.8pt;}
@list l8:level7
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.";
mso-level-tab-stop:358.0pt;
mso-level-number-position:left;
margin-left:196.0pt;
text-indent:-54.0pt;}
@list l8:level8
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.";
mso-level-tab-stop:412.0pt;
mso-level-number-position:left;
margin-left:221.2pt;
text-indent:-61.2pt;}
@list l8:level9
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9\.";
mso-level-tab-stop:448.0pt;
mso-level-number-position:left;
margin-left:250.0pt;
text-indent:-72.0pt;}
@list l9
{mso-list-id:497892198;
mso-list-type:simple;
mso-list-template-ids:-1302288374;}
@list l9:level1
{mso-level-number-format:bullet;
mso-level-style-link:"Liste =E0 puces 2";
mso-level-text:\2013;
mso-level-tab-stop:0cm;
mso-level-number-position:left;
margin-left:35.4pt;
text-indent:-14.15pt;
font-family:"Times New Roman";}
@list l10
{mso-list-id:605386609;
mso-list-type:simple;
mso-list-template-ids:-970032474;}
@list l10:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:18.0pt;
mso-level-number-position:left;
margin-left:18.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l11
{mso-list-id:1482850281;
mso-list-type:simple;
mso-list-template-ids:-827963982;}
@list l11:level1
{mso-level-style-link:"Liste =E0 num=E9ros";
mso-level-tab-stop:20.85pt;
mso-level-number-position:left;
margin-left:19.85pt;
text-indent:-17.0pt;
mso-ansi-font-size:10.0pt;
font-family:Arial;
mso-bidi-font-family:"Times New Roman";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l12
{mso-list-id:1566260869;
mso-list-type:simple;
mso-list-template-ids:1768060620;}
@list l12:level1
{mso-level-number-format:bullet;
mso-level-style-link:Liste_it;
mso-level-text:\F0B7;
mso-level-tab-stop:18.0pt;
mso-level-number-position:left;
margin-left:18.0pt;
text-indent:-18.0pt;
mso-ansi-font-size:14.0pt;
font-family:Symbol;
color:windowtext;}
@list l13
{mso-list-id:1599946789;
mso-list-type:simple;
mso-list-template-ids:-64166180;}
@list l13:level1
{mso-level-number-format:bullet;
mso-level-style-link:Frag_sb;
mso-level-text:\F0B7;
mso-level-tab-stop:18.0pt;
mso-level-number-position:left;
margin-left:18.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l14
{mso-list-id:1792239432;
mso-list-template-ids:-1510573108;}
@list l14:level1
{mso-level-style-link:"Titre 1";
mso-level-text:%1;
mso-level-tab-stop:21.6pt;
mso-level-number-position:left;
margin-left:21.6pt;
text-indent:-21.6pt;}
@list l14:level2
{mso-level-style-link:"Titre 2";
mso-level-text:"%1\.%2";
mso-level-tab-stop:28.8pt;
mso-level-number-position:left;
margin-left:28.8pt;
text-indent:-28.8pt;}
@list l14:level3
{mso-level-style-link:"Titre 3";
mso-level-text:"%1\.%2\.%3";
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
margin-left:36.0pt;
text-indent:-36.0pt;}
@list l14:level4
{mso-level-style-link:"Titre 4";
mso-level-text:"%1\.%2\.%3\.%4";
mso-level-tab-stop:43.2pt;
mso-level-number-position:left;
margin-left:43.2pt;
text-indent:-43.2pt;}
@list l14:level5
{mso-level-style-link:"Titre 5";
mso-level-text:"%1\.%2\.%3\.%4\.%5";
mso-level-tab-stop:50.4pt;
mso-level-number-position:left;
margin-left:50.4pt;
text-indent:-50.4pt;}
@list l14:level6
{mso-level-style-link:"Titre 6";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
mso-level-tab-stop:57.6pt;
mso-level-number-position:left;
margin-left:57.6pt;
text-indent:-57.6pt;}
@list l14:level7
{mso-level-style-link:"Titre 7";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
mso-level-tab-stop:64.8pt;
mso-level-number-position:left;
margin-left:64.8pt;
text-indent:-64.8pt;}
@list l14:level8
{mso-level-style-link:"Titre 8";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
margin-left:72.0pt;
text-indent:-72.0pt;}
@list l14:level9
{mso-level-style-link:"Titre 9";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
mso-level-tab-stop:79.2pt;
mso-level-number-position:left;
margin-left:79.2pt;
text-indent:-79.2pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
</head>
<body lang=3DFR link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<div>
<p><font size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'>Hi </span></font><font size=3D2 =
face=3Dsans-serif><span
lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:sans-serif'>Michael</span></font><f=
ont
size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'>,<o:p></o:p></span></font></p>
<p><font size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'>Thank for your proposition, =
<o:p></o:p></span></font></p>
<p><font size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'>Currently is not possible to identify =
witch log
is created by one context. Perapse, is possible to delete on the table =
the log
create for one level or for one section tree. =
<o:p></o:p></span></font></p>
<p><font size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'>You think is interesting for yours =
log4plsql use?<o:p></o:p></span></font></p>
<p><font size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'>Guillaume <o:p></o:p></span></font></p>
<p><font size=3D2 color=3Dnavy face=3D"Comic Sans MS"><span lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:"Comic Sans =
MS";color:navy'>=A0</span></font><font
size=3D2 face=3D"Comic Sans MS"><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:"Comic Sans MS"'><o:p></o:p></span></font></p>
</div>
<div>
<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>
<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>
</span></font></div>
<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>De :</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
log...@li...
[mailto:log...@li...] <br>
<b><span style=3D'font-weight:bold'>Envoy=E9 :</span></b> lundi 13 =
d=E9cembre
2004 18:13<br>
<b><span style=3D'font-weight:bold'>=C0 :</span></b> =
<st1:PersonName =
w:st=3D"on">log...@li...</st1:PersonName><br>=
<b><span style=3D'font-weight:bold'>Objet :</span></b> [log4plsql]
Enhancement/Change on purge with given =
context</span></font><o:p></o:p></p>
</div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
</span></font><font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;
font-family:sans-serif'>Hi and thanks for the work put into =
log4plsql!</span></font>
<br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>In
my work it's getting a more and more important and convenient way to log
technical information e.g. in plsql-migration-tools.</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>As
i already use it simultaneously for different purposes, i would have =
expected
to have purge(pctx) work just on the given context - so my other logs =
would not
be lost.</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>As
purge does just a complete deletion of all log records i would =
appreciate e.g.
a log variant where purge just deletes all records of the given context =
(as i
have written for myself for a special purpose).</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>What
do you think of this enhancement?</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Best
Regards,</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Michael
Rinus</span></font> <br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>E-
Plus Mobilfunk GmbH & Co. KG</span></font> <br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>D=FCsseldorf</span></fo=
nt><o:p></o:p></p>
</div>
</body>
</html>
------=_NextPart_000_0164_01C4E152.B1B232B0--
--__--__--
_______________________________________________
Log4plsql-all-info mailing list
Log...@li...
https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info
End of Log4plsql-all-info Digest
|
|
From: <log...@li...> - 2004-12-13 19:32:04
|
Hi Michael, Thank for your proposition,=20 Currently is not possible to identify witch log is created by one = context. Perapse, is possible to delete on the table the log create for one level = or for one section tree.=20 You think is interesting for yours log4plsql use? Guillaume=20 =20 _____ =20 De : log...@li... [mailto:log...@li...]=20 Envoy=E9 : lundi 13 d=E9cembre 2004 18:13 =C0 : log...@li... Objet : [log4plsql] Enhancement/Change on purge with given context =20 Hi and thanks for the work put into log4plsql!=20 In my work it's getting a more and more important and convenient way to = log technical information e.g. in plsql-migration-tools.=20 As i already use it simultaneously for different purposes, i would have expected to have purge(pctx) work just on the given context - so my = other logs would not be lost.=20 As purge does just a complete deletion of all log records i would = appreciate e.g. a log variant where purge just deletes all records of the given = context (as i have written for myself for a special purpose).=20 What do you think of this enhancement?=20 Best Regards,=20 Michael Rinus=20 E- Plus Mobilfunk GmbH & Co. KG=20 D=FCsseldorf |
|
From: <log...@li...> - 2004-12-13 17:12:57
|
Hi and thanks for the work put into log4plsql! In my work it's getting a more and more important and convenient way to=20 log technical information e.g. in plsql-migration-tools. As i already use it simultaneously for different purposes, i would have=20 expected to have purge(pctx) work just on the given context - so my other=20 logs would not be lost. As purge does just a complete deletion of all log records i would=20 appreciate e.g. a log variant where purge just deletes all records of the=20 given context (as i have written for myself for a special purpose). What do you think of this enhancement? Best Regards, Michael Rinus E- Plus Mobilfunk GmbH & Co. KG D=FCsseldorf |
|
From: <log...@li...> - 2004-12-06 17:20:34
|
Sandy,=20
=20
You are right, when you change the default level in PLOGPARAM pakage =
spec,
some code is invalidated.=20
If you want change the default log level, you can use the context.=20
=20
Declare
pCTX PLOG.LOG_CTX :=3D PLOG.init (pLEVEL =3D> PLOG.LDEBUG);
begin
PLOG.debug (pCTX, 'Hello LOG');
end;
/
=20
=20
If we don't use a constant for the default level, we can't use it in a
static declaration:=20
=20
FUNCTION init
(
pSECTION IN TLOG.LSECTION%type default NULL ,
-- root of the tree section
pLEVEL IN TLOG.LLEVEL%type default
PLOGPARAM.DEFAULT_LEVEL , -- log level (Use only for debug)
pLOG4J IN BOOLEAN default
PLOGPARAM.DEFAULT_USE_LOG4J, -- if true the log is send to log4j
pLOGTABLE IN BOOLEAN default
PLOGPARAM.DEFAULT_LOG_TABLE, -- if true the log is insert into tlog =
pOUT_TRANS IN BOOLEAN default
PLOGPARAM.DEFAULT_LOG_OUT_TRANS, -- if true the log is in transactional =
log
pALERT IN BOOLEAN default
PLOGPARAM.DEFAULT_LOG_ALERT, -- if true the log is write in =
alert.log
pTRACE IN BOOLEAN default
PLOGPARAM.DEFAULT_LOG_TRACE, -- if true the log is write in trace =
file
pDBMS_OUTPUT IN BOOLEAN default
PLOGPARAM.DEFAULT_DBMS_OUTPUT, -- if true the log is send in standard
output (DBMS_OUTPUT.PUT_LINE)
pDBMS_PIPE_NAME IN VARCHAR2 default
PLOGPARAM.DEFAULT_DBMS_PIPE_NAME, --
pDBMS_OUTPUT_WRAP IN PLS_INTEGER default
PLOGPARAM.DEFAULT_DBMS_OUTPUT_LINE_WRAP
)
RETURN LOG_CTX;
=20
=20
There is a lot of performance problem.=20
=20
let me know if they is big problems for you.
=20
Guillaume
=20
_____ =20
De : log...@li...
[mailto:log...@li...]=20
Envoy=E9 : dimanche 28 novembre 2004 22:55
=C0 : log...@li...
Objet : [log4plsql] Change logging level for entire application?
=20
Hi,=20
This is an excellent and extremely useful program for plsql development.
Thank you for taking the time to write and maintain this program and =
thanks
for making it open source.=20
I have one question though: If I want to set the logging level for the
entire application/database to e.g. info because I have to trace a bug =
on a
production system I=92d like to be able to do so without invalidating =
the plog
and plogparam packages and hence all packages that make use of =
log4plsql.=20
The only way to set the logging level for the entire database is to =
change
the value of the DEFAULT_LEVEL constant in the plogparam package
specification. (At least that is what I believe but as a beginner I =
might be
wrong here ...).=20
If this really is the case I think it would be a good idea to define the
constants in the package body as the recompilation of a body does not =
cause
the other packages to be invalidated.
I=92d suggest to change the code similar to the following:=20
Pslogparam.sql:
replace constant DEFAULT_LEVEL with FUNCTION specification
getApp_logginglevel (reason: prevent invalidation in case of =
recompilation)
=20
Pblogparam.sql:=20
FUNCTION getApp_loggingLevel RETURN tlog.llevel%TYPE
IS
lv_app_logging_level tlog.llevel%TYPE;
BEGIN
lv_app_logging_level :=3D 70; -- all
RETURN lv_app_logging_level;
END getApp_loggingLevel;=20
What do you think of this? Or is there some functionality already where =
I
can achieve the same results without recompiling the package spec?
Cheers,=20
Sandy=20
|
|
From: <log...@li...> - 2004-12-06 16:45:48
|
=20 Bernhard,=20 =20 Please see: in OTN Note:272557.1 =20 Oracle 9i when you execute the following statements: begin sys.dbms_system.set_sql_trace_in_session(. . .); end; You get the following errors: ORA-06550: line 2, column 2: PLS-00201: identifier 'SYS.DBMS_SYSTEM' must be declared ORA-06550: line 2, column 2: PL/SQL: Statement ignored USER is "SYSTEM" Even though the user which is executing the package has the DBA and SYSDBA roles. This was not the behavior is Oracle8i since user with DBA or SYSDBA role wa= s able to execute this code without any errors.=20 1.1.1 Cause In 9.2 for security reasons dbsm_system is protected, so you need to grant execute privileges=20 explicitly. This is the expected behavior in 9.2.=20 1.1.2 Fix Grant the execute privileges to the user explicitly via a grant execute statement. E.g., grant execute on sys.dbms_system to scott; =20 Guillaume _____ =20 De : log...@li... [mailto:log...@li...]=20 Envoy=E9 : lundi 6 d=E9cembre 2004 15:38 =C0 : log...@li... Objet : [log4plsql] After installing I can=B4t compile plog package body =20 There=B4s a error: PLS-00201 SYS.DBMS_SYSTEM Bezeichner muss deklariert wer= den =20 Any advice ? =20 =20 =20 =20 =20 |
9 messages has been excluded from this view by a project administrator.
