log4plsql-all-info Mailing List for LOG4PLSQL (Page 4)
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...> - 2004-12-06 14:38:31
|
There=B4s a error: PLS-00201 SYS.DBMS_SYSTEM Bezeichner muss deklariert werden =20 Any advice ? _____ =20 =20 =20 Bernhard Schmid=20 Tel.: +49(0)831/206-466 Fax: +49(0)831/206-58466 E-Mail: <mailto:sc...@az...> sc...@az...=20 |
|
From: <log...@li...> - 2004-11-28 21:55:16
|
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.
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=B9d like to be able to do so without invalidating the plo=
g
and plogparam packages and hence all packages that make use of log4plsql.
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 b=
e
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=B9d suggest to change the code similar to the following:
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;
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-11-02 15:46:28
|
My zip utilities tell me that = http://prdownloads.sourceforge.net/log4plsql/Log4plsql.zip is not a = proper zip file. Has anyone else experienced this situation? Bill |
|
From: <log...@li...> - 2004-10-27 18:08:42
|
Hi, Can anyone help me with this question I have?? This is an amazing piece of Open Source code that we really want to use. We have different databases, using Oracle 8i , 9 and 10g. Will this work for all versions? I checked through all the documentation and it seems version compatibility is not mentioned there. So I guess it must be compatible with all versions. But I just want to confirm. Is anyone aware of any such known bugs or issues that might relate to different Oracle versions..Or any other related information. PS: I do not know if this is the right forum to ask this question. If it is not, then I am really sorry for any inconvinience I caused. thanks oj |
|
From: <log...@li...> - 2004-10-22 23:11:01
|
I have modify the following function of the PLOG package:
FUNCTION getTextInLevel (
pCode TLOGLEVEL.LCODE%type
) return TLOG.LLEVEL%type
IS
ret TLOG.LLEVEL%type ;
BEGIN
case pCode
when 'ALL' then ret := 70;
when 'DEBUG' then ret := 60;
when 'INFO' then ret := 50;
when 'WARN' then ret := 40;
when 'ERROR' then ret := 30;
when 'FATAL' then ret := 20;
when 'OFF' then ret := 10;
end case;
-- SELECT LLEVEL into ret
-- FROM TLOGLEVEL
-- WHERE LCODE = pCode;
RETURN ret;
EXCEPTION
WHEN OTHERS THEN
return PLOGPARAM.DEFAULT_LEVEL;
END getTextInLevel;
/
Since my trace give me that the most performed simple query was:
SELECT LLEVEL FROM TLOGLEVEL
WHERE LCODE = :b1
call count cpu elapsed disk query current
rows
------- ------ -------- ---------- ---------- ----------
---------- ----------
Parse 0 0.00 0.00 0 0 0
0
Execute 15655 0.53 0.66 0 0 0
0
Fetch 15655 0.90 2.09 100 46965 0
15655
------- ------ -------- ---------- ---------- ----------
---------- ----------
total 31310 1.43 2.75 100 46965 0
15655
The code that forced this execution was the one that tested if the loging
at level (Debug or Info) was enabled and
no logging was performed since the level was error.
The code could be modified in a better way implementing a caching
structure at session level on table TLOGLEVEL.
Regards,
Francesco |
|
From: <log...@li...> - 2004-10-06 16:17:43
|
I see a couple of options for you, both of which would require some coding: 1. Since Log4J is thread safe, you could have one Java process that spawns a new Log4Plsql background process for each RAC node. These would all log to the same Log4J logger, which automatically can handle multiple threads logging at the same time. Log messages might be somewhat out of order, however, depending on Oracle pipe read performance and timing. This introduces a single point of logging failure, however - this single Java VM. 2. Log each RAC node with it's own Java process to its own log file, and have other code that searches/consolidates/reports on log data across all nodes. This may be fine, depending on log reporting needs - any single transaction may be limited to a single node, so finding the right log file may be enough. Each node has a single point of logging failure, however, which may not be acceptible. 3. Use a Java App Server cluster to read the Oracle log4Plsql pipe messages using J2EE facilities to manage processes listening to each Oracle RAC node (some custom combination of JMS and JNDI for instance), and passing log messages on to Log4J using it's JMS listener or something. This is obviously the most work, but would be the most fault tolerant. Whichever method is chosen, I would reccommend modifying Log4Plsql background process to read all pieces of the pipe message at once instead of reading each message field in a new JDBC round-trip. I've used a PL/SQL procedure with multiple OUT parameters to do this - make one PL/SQL call, and get back all the message fields in one call.=20 Much more efficient. Greg Woolsey Sabrix inc. On Wed, 6 Oct 2004 10:22:11 +0200, log...@li... <log...@li...> wrote: > Manish, >=20 > I'm sorry, is not possible for me to test in RAC environement. >=20 > I thinck is possible to connect one log4jbackgroud thread by node. I thni= ck > is possible to log en alert or trace file to. If you log in table you wil= l > create some performance problem. >=20 > In every case is necessary to test... >=20 > Regards > Guillaume Moulard >=20 > -----Message d'origine----- > De : log...@li... > [mailto:log...@li...] > Envoy=E9 : mardi 5 octobre 2004 19:35 > =C0 : log...@li... > Objet : [log4plsql] Using Log4plsql with Oracle 9i/10g RAC >=20 >=20 >=20 > Is it possible to use log4plsql utility in a Real > Application Cluster (RAC) environment? We would like > to send log messages to a file using log4jbackgroud > process. > We have a 3 node configuration and Oracle can run the > job on any node based on the load. Your documentation > says that log4jbackgroundprocess will open one thread > per logsource. If the pl/sql job and > log4jbackgroundprocess happen to connect to different > instace, they will not be able to talk to each other. > Oracle metalink note says that DBMS_PIPE is not > cluster aware. > Any comments. I guess we can always store the messages > in the table (even in RAC) but would like to avoid > this because of overhead. > Rgds, > manish >=20 > _______________________________________________ > Log4plsql-all-info mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info > log4plsq : http://log4plsql.sourceforge.net >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out mo= re > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Log4plsql-all-info mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info > log4plsq : http://log4plsql.sourceforge.net > |
|
From: <log...@li...> - 2004-10-06 08:22:31
|
Manish, I'm sorry, is not possible for me to test in RAC environement.=20 I thinck is possible to connect one log4jbackgroud thread by node. I = thnick is possible to log en alert or trace file to. If you log in table you = will create some performance problem.=20 In every case is necessary to test... Regards=20 Guillaume Moulard -----Message d'origine----- De=A0: log...@li... [mailto:log...@li...]=20 Envoy=E9=A0: mardi 5 octobre 2004 19:35 =C0=A0: log...@li... Objet=A0: [log4plsql] Using Log4plsql with Oracle 9i/10g RAC Is it possible to use log4plsql utility in a Real Application Cluster (RAC) environment? We would like to send log messages to a file using log4jbackgroud process. We have a 3 node configuration and Oracle can run the job on any node based on the load. Your documentation says that log4jbackgroundprocess will open one thread per logsource. If the pl/sql job and log4jbackgroundprocess happen to connect to different instace, they will not be able to talk to each other. Oracle metalink note says that DBMS_PIPE is not cluster aware. Any comments. I guess we can always store the messages in the table (even in RAC) but would like to avoid this because of overhead. Rgds, manish =09 _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net |
|
From: <log...@li...> - 2004-10-05 17:35:11
|
Is it possible to use log4plsql utility in a Real Application Cluster (RAC) environment? We would like to send log messages to a file using log4jbackgroud process. We have a 3 node configuration and Oracle can run the job on any node based on the load. Your documentation says that log4jbackgroundprocess will open one thread per logsource. If the pl/sql job and log4jbackgroundprocess happen to connect to different instace, they will not be able to talk to each other. Oracle metalink note says that DBMS_PIPE is not cluster aware. Any comments. I guess we can always store the messages in the table (even in RAC) but would like to avoid this because of overhead. Rgds, manish __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail |
|
From: <log...@li...> - 2004-06-08 12:58:15
|
Hi
We are using log4plsql with log4j to log messages to external appenders.
Appenders are getting the messages from log4plsql if the threshold is =
set.
If the threshold is set in log4j configuration file then appenders are =
not getting the messages.
Problem:
Levels in log4plsql using are=20
10,OFF
20,FATAL
30,ERROR
40,WARN
50,INFO
60,DEBUG
70,ALL
which are different from Log4j
Log4j default level are :
Integer.MAX_VALUE, OFF
50000,FATAL
40000,ERROR
30000,WARN
20000,INFO
10000,DEBUG
Integer.MIN_VALUE,ALL
=09
And these are reverse orders also ( as compared with the levels =
log4plsql levels in the table).
Is it possible to change the code log4plsql Background process according =
to log4j levels?
=09
a).Instead of callAppenders in ReaderLogDatabase.sqlj
switch (piped_LLEVEL) {
case 20:
dbLogger.fatal(piped_LTEXTE);
break;
case 30:
dbLogger.error(piped_LTEXTE);
break;
case 40:
dbLogger.warn(piped_LTEXTE);
break;
case 50:
dbLogger.info(piped_LTEXTE);
break;
case 60:
dbLogger.debug(piped_LTEXTE);
break;
default:
dbLogger.error(piped_LTEXTE);
break; =09
=09
or
b). we can extend level class and write a new class for log4plsql for =
log4j and for setting threshold give the class name in the =
configuration file. For this code change in log4plsql background process =
is=20
public
boolean isGreaterOrEqual(Priority r) {
return r.isGreaterOrEqual(this);
}
As the check for the Priority is different for log4j and log4plsql.
or
Any other solution please let me know.
Thanks&Regards,
Ramakrishna.
Visit our website at http://www.ubs.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.
|
|
From: <log...@li...> - 2004-06-08 11:51:37
|
Log4plsql (Background process) use log4j to log the message/alert to =
external appenders.
It initializes the log4j from the configuration file.
Hi,
We are using log4plsql with log4j to log external appenders.
Appenders are getting the messages from log4plsql if the threshold is =
set.
If the threshold is set in log4j configuration file then appenders are =
not getting the messages.
Problem:
Levels in log4plsql using are=20
10,OFF
20,FATAL
30,ERROR
40,WARN
50,INFO
60,DEBUG
70,ALL
which are different from Log4j
Log4j default level are :
Integer.MAX_VALUE, OFF
50000,FATAL
40000,ERROR
30000,WARN
20000,INFO
10000,DEBUG
Integer.MIN_VALUE,ALL
=09
And these are reverse orders also ( as compared with the levels =
log4plsql levels in the table).
Is it possible to change the code log4plsql Background process according =
to log4j levels?
or
Any other solution please let me know.
Thanks&Regards,
Ramakrishna.
Visit our website at http://www.ubs.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.
|
|
From: <log...@li...> - 2004-06-08 08:06:44
|
Hi, =20 I have downloaded your Log4plsql.zip at my end. I have unzipped it and pushed the files on a HP unix 11.1 m/c having java ver 1.4. =20 As per the direction in UserGuide.html I have also done the required changes in the setVariable.sh file. Ran install.sh. =20 Till this point everything is working fine. =20 When I do the required setup changes for using Log4j features it starts throwing errors. =20 It gives a java.lang.ClassFormatError Run.java (Invalid pc in line number table).=20 =20 While going through net I came to know that this is mostly due to different jvm versions. =20 Thus I had to compile files at my end and get fresh .class files. =20 I am stuck here in generating ReaderLogDatabase classes as I don't find any source file. I found one file but that is a generated file and it seems the class files sent for ReaderLogDatabase is not having the required byte code for my m/c. =20 Please guide. Let me know if you need any more information. =20 Also note that in UserGuide.html under Install section 5.2, explanation is not proper. Can you elaborate the same? =20 Looking for a positive reply. =20 Thanks & regards Rajeev =20 =20 |
|
From: <log...@li...> - 2004-06-07 16:12:52
|
Hi,
We are using Log4plsql Background process to log for external appenders =
using log4j.
All the appenders are getting the messages if no threshold is not set.
In case threshold is set for the appenders, appenders are not getting =
the messages.
Appenders are getting Initialization messages, and not getting the =
messages from DB_PIPE.
I think the problem is at dbLogger.callAppenders(event) of =
ReaderLogDataBase.sqlj, as the threshold is set for the event reading =
from cache (dynamic level).This dynamic level is different from log4j =
default levels.
Log4j default level are=20
public final static int OFF_INT =3D Integer.MAX_VALUE;
public final static int FATAL_INT =3D 50000;
public final static int ERROR_INT =3D 40000;
public final static int WARN_INT =3D 30000;
public final static int INFO_INT =3D 20000;
public final static int DEBUG_INT =3D 10000;
//public final static int FINE_INT =3D DEBUG_INT;
public final static int ALL_INT =3D Integer.MIN_VALUE;
And these are reverse orders also ( as compared with the levels =
log4plsql levels in the table).
Is it possible to change the code ReaderLogDataBase so that it uses the =
log4j levels,
or
the values in the table can be changed according to log4j levels?
I would appreciate if you can look at the it and let us know the =
solution.
Thanks&Regards,
Ramakrishna.
Visit our website at http://www.ubs.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.
|
|
From: <log...@li...> - 2004-05-17 15:30:06
|
Hi, For me there is only Oracle8 or more. Regards, Guillaume Moulard gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ and : http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all-i= nfo or http://www.mail-archive.com/log...@li... for log...@li... -----Message d'origine----- De : log...@li... [mailto:log4plsql-all-i= nfo...@li...] Envoy=E9 : lundi 17 mai 2004 16:51 =C0 : log...@li... Objet : [log4plsql] log4plsql Hi, What are the prerequisites for logplsql? Thanks & Regards, Ritu Kohli UBS Investment Bank Tel: +44-(0)20 7567 6806 Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id%62&alloc_ida84&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...> - 2004-05-17 14:50:49
|
Hi, What are the prerequisites for logplsql?=20 Thanks & Regards, Ritu Kohli UBS Investment Bank Tel: +44-(0)20 7567 6806 Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. |
|
From: <log...@li...> - 2004-05-07 17:31:05
|
The problem is in PLOG package body where it calls DBMS_PIPE.SEND_MESSAGE: ret :=3D DBMS_PIPE.send_message(pCTX.DBMS_PIPE_NAME); The defaults for the second and third parameters are used, which are not good for this situation. The second parameter is the max wait time in seconds, which defaults to 1000 days. The third parameter is the max pipe size, which defaults to 8K if the pipe hasn't already been created with a larger size. The thing to would be to specify a timeout for SEND_MESSAGE that is smaller, perhaps 30 seconds. Then check the return value from SEND_MESSAGE: 0 =3D success 1 =3D timeout - either the pipe was blocked by another process for the entire timeout period, or it is full. 3 =3D interrupt - don't know what this could mean, but probably not good. For status =3D 2, we could do something like this: Try to send again, hoping the pipe was just locked temporarily. If we get status 1 again, do a DBMS_PIPE.PURGE to attempt to clear the pipe (potentially losing log messages) and resend the current message. If it is still full or locked, raise an error or some other logging error handling mechanism. Perhaps Log4Plsql should take a cue from Log4J and only log once to some central place (it uses standard output) when it encounters a logging error, and does not attempt any more logging. Log4Plsql could log the first logging error (table error, pipe error, etc.) to the alert log or something, then set a package flag that stops all future logging for that session. I also have some pending changes that completely re-do the background process, making it available to include in a Java App Server application for more robust pipe listening. Greg Woolsey Sabrix Inc. On Thu, 6 May 2004 19:26:07 +0200, log...@li... <log...@li...> wrote: >=20 > Hi Jose, >=20 > For ChainSAW could you use pLOGTABLE =3D> TRUE. I think is only necessary= to log in table. >=20 > In my 10G when a log with pLOG4J =3D> TRUE, if there is no Log4jBackgroun= dProcess, my plsql block is in wait. When I launch the > Log4jBackgroundProcess the process restart to log. >=20 > Be careful, if you shutdown you database, all message in pipe is lost. >=20 > -- My test case ----------------------- >=20 > Declare >=20 > pCTX PLOG.LOG_CTX :=3D PLOG.init (pSECTION =3D> 'firstSection', >=20 > pLEVEL =3D> PLOG.LDEBUG, >=20 > pLOG4J =3D> TRUE >=20 > ); >=20 > begin >=20 > for i in 1..2000 loop >=20 > PLOG.debug (pCTX, 'Hello LOG:'||i); >=20 > end loop; >=20 > end; >=20 > / >=20 > Regards, > Guillaume Moulard > gmo...@us... >=20 > Project : LOG4PLSQL : Oracle Database Loggin tools > see : http://log4plsql.sourceforge.net/ > and : http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all= -info or > http://www.mail-archive.com/log...@li... > for log...@li... >=20 > -----Message d'origine----- > De : SAG - Jose Antonio Tarifa >=20 > Envoy=E9 : jeudi 6 mai 2004 15:05 > =C0 : Guillaume Moulard > Objet : RE: Log4jBackgroundProcess Problem >=20 > Hello Guillaume, >=20 > thank your for your reply. But my problem is another. >=20 > We MUST use pLOG4J =3D> TRUE, because we want to trace every log in our C= hainSAW client. But the problem is when > Log4jBackgroundProcess is not running because an error in Java or another= problem (imagine the process shuts down suddenly because a > socket error, or anything else). Then, Oracle seems to be blocked sendin= g logs through the pipe to the process. And that is my > problem, if the process stops suddenly, every PL/SQL procedure in our dat= abase using Log4PLSQL are blocked. >=20 > greetings, >=20 > Jos=E9 Antonio Tarifa Lorenzo >=20 > -----Mensaje original----- >=20 > De: Guillaume Moulard [mailto:gmo...@us...] >=20 > Enviado el: jueves, 06 de mayo de 2004 13:03 >=20 > Para: log...@li... >=20 > Asunto: RE: Log4jBackgroundProcess Problem >=20 > Jos=E9, >=20 > If you don't use in the context the pLOG4J =3D> TRUE it in not necessary = to lauche the Log4jBackgroundProcess. >=20 > I don't now the unstable behaviour of Oracle when PL/SQL code writes a lo= g. Perapse you can send more informations about you >=20 > problem. >=20 > Regards, >=20 > Guillaume Moulard >=20 > gmo...@us... >=20 > Project : LOG4PLSQL : Oracle Database Loggin tools >=20 > see : http://log4plsql.sourceforge.net/ >=20 > and : http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all= -info or >=20 > http://www.mail-archive.com/log...@li... >=20 > for log...@li... >=20 > -----Message d'origine----- >=20 > De : jatarifa >=20 > Envoy=E9 : vendredi 30 avril 2004 11:05 >=20 > =C0 : gmo...@us... >=20 > Objet : Log4jBackgroundProcess Problem >=20 > Hello Guillaume. >=20 > I am the technical consultor of OMEL (Operador del Mercado >=20 > Electrico Espa=F1ol - http://www.omel.es) and we are very >=20 > interested to incorporate your development to our Database, >=20 > because we think is a great tool to monitorize the electricity >=20 > market. >=20 > But we have a problem. We have put in our test environment >=20 > the latest version of Log4PLSQL and we have noticed an >=20 > unstable behaviour of Oracle when PL/SQL code writes a log >=20 > to Log4jBackgroundProcess and this Java program is not >=20 > running. >=20 > Oracle seems to be locked on PLOG statement on PL/SQL >=20 > code until Log4jBackgroundProcess is started!!! >=20 > Is that a normal behaviour (I think no) of Oracle or is >=20 > something wrong in PLOG PLSQL code? >=20 > As I said after, we are very interested in Log4PLSQL and the >=20 > Spain Electricity Market would be improved with this tool. >=20 > Thank you >=20 > Jos=E9 Antonio Tarifa >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by Sleepycat Software > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to > deliver higher performing products faster, at low TCO. > http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3 > _______________________________________________ > Log4plsql-all-info mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info > log4plsq : http://log4plsql.sourceforge.net > |
|
From: <log...@li...> - 2004-05-06 17:33:52
|
Hi Jose,
For ChainSAW could you use pLOGTABLE =3D> TRUE. I think is only necessary t=
o log in table.
In my 10G when a log with pLOG4J =3D> TRUE, if there is no Log4jBackgroundP=
rocess, my plsql block is in wait. When I launch the
Log4jBackgroundProcess the process restart to log.
Be careful, if you shutdown you database, all message in pipe is lost.
-- My test case -----------------------
Declare
pCTX PLOG.LOG_CTX :=3D PLOG.init (pSECTION =3D> 'firstSection',
pLEVEL =3D> PLOG.LDEBUG,
pLOG4J =3D> TRUE
);
begin
for i in 1..2000 loop
PLOG.debug (pCTX, 'Hello LOG:'||i);
end loop;
end;
/
Regards,
Guillaume Moulard
gmo...@us...
Project : LOG4PLSQL : Oracle Database Loggin tools
see : http://log4plsql.sourceforge.net/
and : http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all-i=
nfo or
http://www.mail-archive.com/log...@li...
for log...@li...
-----Message d'origine-----
De : SAG - Jose Antonio Tarifa
Envoy=E9 : jeudi 6 mai 2004 15:05
=C0 : Guillaume Moulard
Objet : RE: Log4jBackgroundProcess Problem
Hello Guillaume,
thank your for your reply. But my problem is another.
We MUST use pLOG4J =3D> TRUE, because we want to trace every log in our Cha=
inSAW client. But the problem is when
Log4jBackgroundProcess is not running because an error in Java or another p=
roblem (imagine the process shuts down suddenly because a
socket error, or anything else). Then, Oracle seems to be blocked sending =
logs through the pipe to the process. And that is my
problem, if the process stops suddenly, every PL/SQL procedure in our datab=
ase using Log4PLSQL are blocked.
greetings,
Jos=E9 Antonio Tarifa Lorenzo
-----Mensaje original-----
De: Guillaume Moulard [mailto:gmo...@us...]
Enviado el: jueves, 06 de mayo de 2004 13:03
Para: log...@li...
Asunto: RE: Log4jBackgroundProcess Problem
Jos=E9,
If you don't use in the context the pLOG4J =3D> TRUE it in not necessary to=
lauche the Log4jBackgroundProcess.
I don't now the unstable behaviour of Oracle when PL/SQL code writes a log.=
Perapse you can send more informations about you
problem.
Regards,
Guillaume Moulard
gmo...@us...
Project : LOG4PLSQL : Oracle Database Loggin tools
see : http://log4plsql.sourceforge.net/
and : http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all-i=
nfo or
http://www.mail-archive.com/log...@li...
for log...@li...
-----Message d'origine-----
De : jatarifa
Envoy=E9 : vendredi 30 avril 2004 11:05
=C0 : gmo...@us...
Objet : Log4jBackgroundProcess Problem
Hello Guillaume.
I am the technical consultor of OMEL (Operador del Mercado
Electrico Espa=F1ol - http://www.omel.es) and we are very
interested to incorporate your development to our Database,
because we think is a great tool to monitorize the electricity
market.
But we have a problem. We have put in our test environment
the latest version of Log4PLSQL and we have noticed an
unstable behaviour of Oracle when PL/SQL code writes a log
to Log4jBackgroundProcess and this Java program is not
running.
Oracle seems to be locked on PLOG statement on PL/SQL
code until Log4jBackgroundProcess is started!!!
Is that a normal behaviour (I think no) of Oracle or is
something wrong in PLOG PLSQL code?
As I said after, we are very interested in Log4PLSQL and the
Spain Electricity Market would be improved with this tool.
Thank you
Jos=E9 Antonio Tarifa
|
|
From: <log...@li...> - 2004-05-06 11:03:51
|
Jos=E9, If you don't use in the context the pLOG4J =3D> TRUE it in not necessary to= lauche the Log4jBackgroundProcess. I don't now the unstable behaviour of Oracle when PL/SQL code writes a log.= Perapse you can send more informations about you problem. Regards, Guillaume Moulard gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ and : http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all-i= nfo or http://www.mail-archive.com/log...@li... for log...@li... -----Message d'origine----- De : jatarifa Envoy=E9 : vendredi 30 avril 2004 11:05 =C0 : gmo...@us... Objet : Log4jBackgroundProcess Problem Hello Guillaume. I am the technical consultor of OMEL (Operador del Mercado Electrico Espa=F1ol - http://www.omel.es) and we are very interested to incorporate your development to our Database, because we think is a great tool to monitorize the electricity market. But we have a problem. We have put in our test environment the latest version of Log4PLSQL and we have noticed an unstable behaviour of Oracle when PL/SQL code writes a log to Log4jBackgroundProcess and this Java program is not running. Oracle seems to be locked on PLOG statement on PL/SQL code until Log4jBackgroundProcess is started!!! Is that a normal behaviour (I think no) of Oracle or is something wrong in PLOG PLSQL code? As I said after, we are very interested in Log4PLSQL and the Spain Electricity Market would be improved with this tool. Thank you Jos=E9 Antonio Tarifa |
|
From: <log...@li...> - 2004-04-28 08:43:13
|
Hi group, =20 we have put in our test environment the lastest version of Log4PLSQL and = we have noticed an unstable behaviour of Oracle when PL/SQL code writes = a log to Log4jBackgroundProcess and this Java program is not running. Oracle seems to be locked on PLOG statement on PL/SQL code until = Log4jBackgroundProcess is started!!! Is that a normal behaviour (I think no) of Oracle or is something wrong = in PLOG PLSQL code? Thanks Jos=E9 Antonio Tarifa (jat...@om... <mailto:jat...@om...> ) |
|
From: <log...@li...> - 2004-03-26 17:12:39
|
I would suggest using the logging to table feature, and put a custom trigger on the table to send email when your desired criteria are met. For performance, you may want to batch the outgoing messages into a different table, and have a scheduled job check for new messages to send, since sending mail can take some time (up to several seconds, depending on the mail server and load). Greg Woolsey Sabrix, Inc. -----Original Message----- From: log...@li... [mailto:log...@li...]=20 Sent: Tuesday, March 23, 2004 8:21 AM To: log...@li... Subject: [log4plsql] Integration with utl_smtp I am about to implement Log4plsql on a couple of databases. What I would really like to have is the ability to automatically send an email whenever a certain message level is logged (e.g. Fatal or Error). I cannot use the connection to Log4j, however, because of internal policy restrictions. Has anyone considered using the Oracle utl_smtp package in conjunction with Log4plsql ? Also, instead of fixed email recipient parameters specified in the package spec, I'm thinking of creating an admin_contact type of table that would contain the names and email addresses of the various administrators for the databases and applications. That table would contain fields that state who is the current support contact versus the backup support contacts (i.e. the current contact would be the "From" recipient, and the backups would be "CC" recipients), and possibly which schemas they are responsible for. Just some ideas. Brad ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&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...> - 2004-03-23 16:20:47
|
I am about to implement Log4plsql on a couple of databases. What I = would really like to have is the ability to automatically send an email = whenever a certain message level is logged (e.g. Fatal or Error). I = cannot use the connection to Log4j, however, because of internal policy = restrictions. Has anyone considered using the Oracle utl_smtp package = in conjunction with Log4plsql ? Also, instead of fixed email recipient parameters specified in the = package spec, I'm thinking of creating an admin_contact type of table = that would contain the names and email addresses of the various = administrators for the databases and applications. That table would = contain fields that state who is the current support contact versus the = backup support contacts (i.e. the current contact would be the "From" = recipient, and the backups would be "CC" recipients), and possibly which = schemas they are responsible for. Just some ideas. Brad |
|
From: <log...@li...> - 2004-03-19 23:40:29
|
Attached is a Zip file (renamed as log4plsql.dat to pass spam/virus
filters) with my modifications to the 3.1.2.1 version for people to
review and see what they think. =20
We needed additional PL/SQL functionality like the Log4J MDC, and we
needed the Java listener to be thread safe and highly flexible in a J2EE
App Container context. We didn't care if each instance in a cluster
started it's own listener on a pipe, as hopefully the logging would be
standardized/centralized with Log4J, but we did care that only one
listener per pipe was used in a given VM.
We also formatted and extended the DBMS_OUTPUT code a bit.
Things I've added/fixed/changed:
PMDC package
a package to add Log4J style Mapped Domain Context. Currently only
output to the Log4J pipe, not to the table or other output locations, as
there is no pattern layout concept yet.
PLOG_PIPE package
Contains a procedure for reading the next Log4Plsql pipe message and
returning the different fields as OUT parameters. This means that the
Java process only needs to make one call, not many to get each log
message, which is MUCH faster.
PLOG
Modified the pipe packing section to pass additional fields for the MDC
data (passed as two delimited strings, one for names, the other for
values, and a third field for the separator character).
The date is passed as a DATE object, instead of text, and the hundredths
of seconds are passed as a number. The Java process I've written then
reads the date as a Timestamp, gets the milliseconds, and adds
hundredths*10 to get a raw timestamp to use for the log event. This way
Log4J logs the message with the actual database timestamp it was created
with, and can still do any other date formatting you want.
The DBMS_OUTPUT code has been cleaned up and extended. A sub-block of
code was created inside the IF statement to keep the local variables
used for processing the output text local to the code that uses them,
rather than declared in the procedure header. Makes it easier to read
in my opinion. =20
We (myself and another developer who is starting to use this in our
project) have added some formatting to the DMBS_OUTPUT section to make
the result more readable in SQLPLUS and other tools.
LOG_CTX, PLOG.INIT, and PLOGPARAM now know about a DBMS_OUTPUT line wrap
length value. Messages longer than this value are output on multiple
lines. This replaces the hard-coded max value of 255 with a value that
can be session-specific or even message-specific if desired. The
default is still 255.
DBMS_OUTPUT data is logged with the header on the same line as the start
of the message. If wrapping is needed, wrapped lines are left-padded to
the width of the header. Here is an example of output:
13:33:33:09-ERROR- anonymous block this is my really long error message
str
ing that should force wrapping with
the=20
header text prepended to it.
We like this better, but it may compress log messages too much for some
people. Let me know what you think.
Java BackgroundProcess
I completely re-wrote the pipe listening portion of this to take
advantage of the new PLOG_PIPE package to get a full log message in one
call and make the whole thing robust, safe, and scalable for our
enterprise application running in an App Container such as OC4J,
WebLogic, or WebSphere.
The existing use with the standalone, runable JAR file is still
available, but if you want to integrate the background process in a
larger application there is new functionality to do so. =20
I have factory methods on the listener that enforce only one listener
per database URL/Username/PipeName combination, so you don't needlessly
start multiple listeners per pipe by accident, and added thread-safe
ways to stop/start listening on a given pipe.
The listener class DbLogListener uses a DbLogHelper instance to allow
for extensibility without needing to mess with the complex DbLogListener
class. This helper has methods for getting the Logger instance to use
for a given message and pre- and post- logging methods to customize
things like the MDC and NDC, and clean up after logging a message.
The DbLogListener can store a base Logger name to use for getting the
desired Logger instance for each message read from the pipe.
The default is the RootLogger if none is supplied.
DbLogHelper creates a default Logger name for each message from=20
DbLogListener.getRootLogger() + current message section
So by default the section name =3D logger name, if the root logger is =
the
base logger for the DbLogListener.
If you create the DbLogListener with a default Logger name of
"backgroundProcess" then all messages will use descendants of that
Logger.
Currently the Java process does not support custom levels from
Log4Plsql. I needed it to work with log messages from possibly many
databases, each of which would have it's own Log4Plsql version
installed. Dynamic Levels would have had to be read/stored by
connection, which would have added significant code overhead for very
little functionality.
We have chosen at this point to use the standard levels only, which is
what the Log4J project recommends anyway. Besides, custom levels would
need to map to some custom Level in Java, otherwise they would not be
logged, and using some sort of reflection to dynamically load Level
classes would be very expensive from a performance standpoint.
With the re-write of the Java code, there is no SQLJ dependency anymore
- I just use straight JDBC code, as there isn't that much for it to do.
The constructor that uses the XML configuration parameters does need to
find the OracleDataSource class, which is in the JDBC driver JAR
classes12.jar, and it needs the XML parser in xmlparserv2.jar.
Other classes were only modified to reference the new DbLogListener
appropriately, they were otherwise unchanged.
Feedback is welcome, I'm happy to answer any questions or field
criticisms of this code.
Greg Woolsey
Sabrix, Inc.
Lake Oswego, Oregon
USA
|
|
From: <log...@li...> - 2004-03-18 14:03:51
|
Hello Guillaume, Yes, that works in my sqlplus. It does not work as Forms 9i client side PL/SQL. For example, it doesn't work in a procedure, function, or packag= e in a Forms module Program Unit. I haven't tried it in Forms 10g. -Jerome > -----Original Message----- > From: log...@li... > [mailto:log...@li...] > Sent: Thursday, March 18, 2004 6:48 AM > To: log...@li... > Subject: RE: [log4plsql] Oracle 9i Forms > > > Jerome, > > I don't have problem with my small test case : > > > --------------------------------- > > SQL*Plus: Release 9.2.0.1.0 - Production on Je Mar 18 12:42:40 2004 > > Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. > > > Connect=DA =D3 : > Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production > With the Partitioning, OLAP and Oracle Data Mining options > JServer Release 9.2.0.1.0 - Production > > SQL> select plog.getLOG4PLSQVersion from dual; > > GETLOG4PLSQVERSION > ------------------------------------------------------------------ > -------------- > 3.1.2.1 > > SQL> exec plog.purge > > Proc=DAdure PL/SQL termin=DAe avec succ=DEs. > > SQL> DECLARE > 2 logCtx plog.log_ctx :=3D plog.init(pLEVEL =3D> plog.LALL); > 3 BEGIN > 4 plog.debug(logCtx, 'Hi there from my forms package.'); > 5 END; > 6 / > > Proc=DAdure PL/SQL termin=DAe avec succ=DEs. > > SQL> select * from vlog; > > LOG > ------------------------------------------------------------------ > -------------- > [Mar 18, 12:43:16:82][INFO][ULOG][plog.purge][Purge by user:ULOG] > [Mar 18, 12:43:21:21][DEBUG][ULOG][ anonymous block][Hi there > from my forms pack > age.] > > > SQL> > > --------------------------------- > > This test case run in yours sqlplus? > > > Regards, > Guillaume Moulard > gmo...@us... > > Project : LOG4PLSQL : Oracle Database Loggin tools > see : http://log4plsql.sourceforge.net/ > and : > http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all-info= or > http://www.mail-archive.com/log...@li... > for log...@li... > > > > -----Message d'origine----- > De : log...@li... > [mailto:log...@li...] > Envoy=E9 : mercredi 17 mars 2004 20:10 > =C0 : log...@li... > Objet : RE: [log4plsql] Oracle 9i Forms > > > > Hello, > > > > What I was trying to do is something like this in my Forms Client PL/SQ= L > > package. > > > > <code_bad> > > logCtx plog.log_ctx :=3D plog.init(pLEVEL =3D> plog.LALL); > > plog.debug(logCtx, 'Hi there from my forms package.'); > > </code_bad> > > > > However the above wouldn't compile. The following error was generated. > > > > <compile_error> > > Implementation Restriction: 'PLOG.LALL': Cannot directory access remote > > package variable or cursor. > > </compile_error> > > > > The client PL/SQL compiler does allow me to call the methods > without the log > > context. > > > > <code_good> > > plog.error('Hi there from my forms package.'); > > </code_good> > > > > If I make any more progress I'll share it on the list. > > > > Regards, > > > > Jerome Jacobsen > > > > > > > -----Original Message----- > > > From: log...@li... > > > [mailto:log...@li...] > > > Sent: Wednesday, March 17, 2004 1:23 PM > > > To: log...@li... > > > Subject: RE: [log4plsql] Oracle 9i Forms > > > > > > > > > Hi, > > > > > > I don't have a Forms PL/SQL Library for PLOG > > > > > > > > > I think you can make calls for: > > > PROCEDURE debug > > > PROCEDURE info > > > PROCEDURE warn > > > PROCEDURE error > > > PROCEDURE fatal > > > PROCEDURE log > > > > > > With a lot of different parameter. But there is no > > > procedure/function for plog.LALL > > > If you whan use LALL, is necessary to use log procedure. > > > > > > I'm very interest if you whan share yours forms library. > > > > > > > > > Regards, > > > Guillaume Moulard > > > gmo...@us... > > > > > > Project : LOG4PLSQL : Oracle Database Loggin tools > > > see : http://log4plsql.sourceforge.net/ > > > and : > > > http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all-in= fo or > > > http://www.mail-archive.com/log...@li... > > > for log...@li... > > > > > > -----Message d'origine----- > > > De : log...@li... > > > [mailto:log...@li...] > > > Envoy=E9 : mercredi 17 mars 2004 14:39 > > > =C0 : Log4PlSql > > > Objet : [log4plsql] Oracle 9i Forms > > > > > > > > > > > > How can I use this in Client Side PL/SQL in Oracle 9i Forms? I'm > > > new to both > > > > > > Forms and Log4PlSql. > > > > > > > > > > > > Do I need to somehow create a Forms PL/SQL Library for PLOG? > > > > > > > > > > > > For now I'm able to make calls to the plog.debug, etc. procedures > > > that make > > > > > > use of the default context. However when I try to reference > > > plog.LALL I get > > > > > > an error in Forms Builder: > > > > > > > > > > > > Implementation Restriction: 'PLOG.LALL': Cannot directory access remo= te > > > > > > package variable or cursor. > > > > > > > > > > > > I assume this error will occur for the other Level package variables. > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > This SF.Net email is sponsored by: IBM Linux Tutorials > > > > > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > > > > > GenToo technologies. Learn everything from fundamentals to system > > > > > > administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3D= click > > > > > > _______________________________________________ > > > > > > 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: IBM Linux Tutorials > > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > > GenToo technologies. Learn everything from fundamentals to system > > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=CCk > > > _______________________________________________ > > > 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: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > GenToo technologies. Learn everything from fundamentals to system > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&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: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=CCk > _______________________________________________ > Log4plsql-all-info mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info > log4plsq : http://log4plsql.sourceforge.net > > > |
|
From: <log...@li...> - 2004-03-18 11:48:38
|
Jerome, I don't have problem with my small test case : --------------------------------- SQL*Plus: Release 9.2.0.1.0 - Production on Je Mar 18 12:42:40 2004 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. Connect=DA =D3 : Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.1.0 - Production SQL> select plog.getLOG4PLSQVersion from dual; GETLOG4PLSQVERSION ---------------------------------------------------------------------------= ----- 3.1.2.1 SQL> exec plog.purge Proc=DAdure PL/SQL termin=DAe avec succ=DEs. SQL> DECLARE 2 logCtx plog.log_ctx :=3D plog.init(pLEVEL =3D> plog.LALL); 3 BEGIN 4 plog.debug(logCtx, 'Hi there from my forms package.'); 5 END; 6 / Proc=DAdure PL/SQL termin=DAe avec succ=DEs. SQL> select * from vlog; LOG ---------------------------------------------------------------------------= ----- [Mar 18, 12:43:16:82][INFO][ULOG][plog.purge][Purge by user:ULOG] [Mar 18, 12:43:21:21][DEBUG][ULOG][ anonymous block][Hi there from my forms= pack age.] SQL> --------------------------------- This test case run in yours sqlplus? Regards, Guillaume Moulard gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ and : http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all-i= nfo or http://www.mail-archive.com/log...@li... for log...@li... -----Message d'origine----- De : log...@li... [mailto:log4plsql-all-i= nfo...@li...] Envoy=E9 : mercredi 17 mars 2004 20:10 =C0 : log...@li... Objet : RE: [log4plsql] Oracle 9i Forms Hello, What I was trying to do is something like this in my Forms Client PL/SQL package. <code_bad> logCtx plog.log_ctx :=3D plog.init(pLEVEL =3D> plog.LALL); plog.debug(logCtx, 'Hi there from my forms package.'); </code_bad> However the above wouldn't compile. The following error was generated. <compile_error> Implementation Restriction: 'PLOG.LALL': Cannot directory access remote package variable or cursor. </compile_error> The client PL/SQL compiler does allow me to call the methods without the lo= g context. <code_good> plog.error('Hi there from my forms package.'); </code_good> If I make any more progress I'll share it on the list. Regards, Jerome Jacobsen > -----Original Message----- > From: log...@li... > [mailto:log...@li...] > Sent: Wednesday, March 17, 2004 1:23 PM > To: log...@li... > Subject: RE: [log4plsql] Oracle 9i Forms > > > Hi, > > I don't have a Forms PL/SQL Library for PLOG > > > I think you can make calls for: > PROCEDURE debug > PROCEDURE info > PROCEDURE warn > PROCEDURE error > PROCEDURE fatal > PROCEDURE log > > With a lot of different parameter. But there is no > procedure/function for plog.LALL > If you whan use LALL, is necessary to use log procedure. > > I'm very interest if you whan share yours forms library. > > > Regards, > Guillaume Moulard > gmo...@us... > > Project : LOG4PLSQL : Oracle Database Loggin tools > see : http://log4plsql.sourceforge.net/ > and : > http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all-info o= r > http://www.mail-archive.com/log...@li... > for log...@li... > > -----Message d'origine----- > De : log...@li... > [mailto:log...@li...] > Envoy=E9 : mercredi 17 mars 2004 14:39 > =C0 : Log4PlSql > Objet : [log4plsql] Oracle 9i Forms > > > > How can I use this in Client Side PL/SQL in Oracle 9i Forms? I'm > new to both > > Forms and Log4PlSql. > > > > Do I need to somehow create a Forms PL/SQL Library for PLOG? > > > > For now I'm able to make calls to the plog.debug, etc. procedures > that make > > use of the default context. However when I try to reference > plog.LALL I get > > an error in Forms Builder: > > > > Implementation Restriction: 'PLOG.LALL': Cannot directory access remote > > package variable or cursor. > > > > I assume this error will occur for the other Level package variables. > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > GenToo technologies. Learn everything from fundamentals to system > > administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= ck > > _______________________________________________ > > 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: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=CCk > _______________________________________________ > 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: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&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...> - 2004-03-17 19:10:30
|
Hello,
What I was trying to do is something like this in my Forms Client PL/SQL
package.
<code_bad>
logCtx plog.log_ctx :=3D plog.init(pLEVEL =3D> plog.LALL);
plog.debug(logCtx, 'Hi there from my forms package.');
</code_bad>
However the above wouldn't compile. The following error was generated.
<compile_error>
Implementation Restriction: 'PLOG.LALL': Cannot directory access remote
package variable or cursor.
</compile_error>
The client PL/SQL compiler does allow me to call the methods without the =
log
context.
<code_good>
plog.error('Hi there from my forms package.');
</code_good>
If I make any more progress I'll share it on the list.
Regards,
Jerome Jacobsen
> -----Original Message-----
> From: log...@li...
> [mailto:log...@li...]
> Sent: Wednesday, March 17, 2004 1:23 PM
> To: log...@li...
> Subject: RE: [log4plsql] Oracle 9i Forms
>
>
> Hi,
>
> I don't have a Forms PL/SQL Library for PLOG
>
>
> I think you can make calls for:
> PROCEDURE debug
> PROCEDURE info
> PROCEDURE warn
> PROCEDURE error
> PROCEDURE fatal
> PROCEDURE log
>
> With a lot of different parameter. But there is no
> procedure/function for plog.LALL
> If you whan use LALL, is necessary to use log procedure.
>
> I'm very interest if you whan share yours forms library.
>
>
> Regards,
> Guillaume Moulard
> gmo...@us...
>
> Project : LOG4PLSQL : Oracle Database Loggin tools
> see : http://log4plsql.sourceforge.net/
> and :
> http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all-info=
or
> http://www.mail-archive.com/log...@li...
> for log...@li...
>
> -----Message d'origine-----
> De : log...@li...
> [mailto:log...@li...]
> Envoy=E9 : mercredi 17 mars 2004 14:39
> =C0 : Log4PlSql
> Objet : [log4plsql] Oracle 9i Forms
>
>
>
> How can I use this in Client Side PL/SQL in Oracle 9i Forms? I'm
> new to both
>
> Forms and Log4PlSql.
>
>
>
> Do I need to somehow create a Forms PL/SQL Library for PLOG?
>
>
>
> For now I'm able to make calls to the plog.debug, etc. procedures
> that make
>
> use of the default context. However when I try to reference
> plog.LALL I get
>
> an error in Forms Builder:
>
>
>
> Implementation Restriction: 'PLOG.LALL': Cannot directory access remote
>
> package variable or cursor.
>
>
>
> I assume this error will occur for the other Level package variables.
>
>
>
>
>
>
>
> -------------------------------------------------------
>
> This SF.Net email is sponsored by: IBM Linux Tutorials
>
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
>
> GenToo technologies. Learn everything from fundamentals to system
>
> administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dc=
lick
>
> _______________________________________________
>
> 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: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=CCk
> _______________________________________________
> Log4plsql-all-info mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info
> log4plsq : http://log4plsql.sourceforge.net
>
>
>
|
|
From: <log...@li...> - 2004-03-17 18:23:32
|
Hi, I don't have a Forms PL/SQL Library for PLOG I think you can make calls for: PROCEDURE debug PROCEDURE info PROCEDURE warn PROCEDURE error PROCEDURE fatal PROCEDURE log With a lot of different parameter. But there is no procedure/function for p= log.LALL If you whan use LALL, is necessary to use log procedure. I'm very interest if you whan share yours forms library. Regards, Guillaume Moulard gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ and : http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all-i= nfo or http://www.mail-archive.com/log...@li... for log...@li... -----Message d'origine----- De : log...@li... [mailto:log4plsql-all-i= nfo...@li...] Envoy=E9 : mercredi 17 mars 2004 14:39 =C0 : Log4PlSql Objet : [log4plsql] Oracle 9i Forms How can I use this in Client Side PL/SQL in Oracle 9i Forms? I'm new to bot= h Forms and Log4PlSql. Do I need to somehow create a Forms PL/SQL Library for PLOG? For now I'm able to make calls to the plog.debug, etc. procedures that make= use of the default context. However when I try to reference plog.LALL I get= an error in Forms Builder: Implementation Restriction: 'PLOG.LALL': Cannot directory access remote package variable or cursor. I assume this error will occur for the other Level package variables. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dclick= _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net |
9 messages has been excluded from this view by a project administrator.
