RV320 VPN log level

Hello
The RV320 logs are very poor to troubleshoot VPN issues, even with external syslog facility, at the maximum log level the device does not log any VPN event.
Is there a way to increase the log level?
Is there a separate syslog facility local# for VPN? 
Where to get extensive documentation about syslog facilities numbers used by RV320?
Thank you

Cisco support team is trying to fix this up, but it's not working
They managed to build a working tunnel but that's not the point, we need VPN logs, period.
It looks like the device only starts VPN log after a succesfull VPN connection, making the device impossible to setup, diagnose or monitor failed VPN connections. This is a no go.
using external syslog does not help, the only VPN related output I get in log is : 
Oct 22 12:32:18 10.0.0.254 VPN Log: [g2gips0]: [Tunnel Disconnected]
what I should get (and is a must have) would be :
2014-10-20, 05:15:31
VPN Log
[g2gips2] #11: [Tunnel Established] ISAKMP SA established
2014-10-20, 05:15:54
VPN Log
[g2gips2] #14: [Tunnel Established] sent MR3, ISAKMP SA established
2014-10-20, 05:15:55
VPN Log
[g2gips2]: cmd=up-client peer=62.176.126.28 peer_client=192.168.1.0/24 peer_client_net=192.168.1.0 peer_client_mask=255.255.255.0
2014-10-20, 05:15:55
VPN Log
ip route add 192.168.1.0/24 via 88.161.221.254 dev eth1 metric 35
2014-10-20, 05:15:55
VPN Log
iptables -t nat -I vpn -s 10.0.0.0/24 -d 192.168.1.0/24 -j ACCEPT
2014-10-20, 05:15:55
VPN Log
iptables -t nat -I vpn -s 192.168.1.0/24 -d 10.0.0.0/24 -j ACCEPT
2014-10-20, 05:15:55
VPN Log
iptables -t nat -I vpn_postrouting -s 10.0.0.0/24 -d 192.168.1.0/24 -j ACCEPT
2014-10-20, 05:15:55
VPN Log
iptables -t nat -I vpn_postrouting -o eth0 -s 192.168.1.0/24 -d 10.0.0.0/24 -j ACCEPT
2014-10-20, 05:15:55
VPN Log
[g2gips2] #15: [Tunnel Established] IPsec SA established {ESP=>0xc570a9c8 < 0xc43d09ba}
2014-10-20, 05:16:53
VPN Log
[g2gips2] #15: [Tunnel Negotiation Fail] DPD: Could not find newest phase 1 state
2014-10-20, 05:26:44
User Log
User cisco Session Expired
2014-10-20, 06:14:42
VPN Log
[g2gips2] #16: [Tunnel Established] sent MR3, ISAKMP SA established
2014-10-20, 06:14:42
VPN Log
[g2gips2] #17: [Tunnel Established] IPsec SA established {ESP=>0xc0931255 < 0xc928b34e}
2014-10-20, 06:14:42
VPN Log
[g2gips2] #16: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc570a9c8) not found (maybe expired)
2014-10-20, 07:13:34
VPN Log
[g2gips2] #18: [Tunnel Established] IPsec SA established {ESP=>0xcea6223a < 0xcfbc92ba}
2014-10-20, 07:13:34
VPN Log
[g2gips2] #16: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc0931255) not found (maybe expired)
2014-10-20, 08:12:20
VPN Log
[g2gips2] #19: [Tunnel Established] IPsec SA established {ESP=>0xcdb2138d < 0xcfa80369}
2014-10-20, 08:12:20
VPN Log
[g2gips2] #16: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xcea6223a) not found (maybe expired)
2014-10-20, 09:11:09
VPN Log
[g2gips2] #20: [Tunnel Established] IPsec SA established {ESP=>0xc5aeba36 < 0xcd182a7c}
2014-10-20, 09:11:09
VPN Log
[g2gips2] #16: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xcdb2138d) not found (maybe expired)
2014-10-20, 10:09:57
VPN Log
[g2gips2] #21: [Tunnel Established] IPsec SA established {ESP=>0xc862dbe2 < 0xc68a5a29}
2014-10-20, 10:09:57
VPN Log
[g2gips2] #16: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc5aeba36) not found (maybe expired)
2014-10-20, 11:08:45
VPN Log
[g2gips2] #22: [Tunnel Established] IPsec SA established {ESP=>0xc8c5d191 < 0xc7009873}
2014-10-20, 11:08:45
VPN Log
[g2gips2] #16: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc862dbe2) not found (maybe expired)
2014-10-20, 12:07:29
VPN Log
[g2gips2] #23: [Tunnel Established] IPsec SA established {ESP=>0xcbb5aca6 < 0xc087d294}
2014-10-20, 12:07:29
VPN Log
[g2gips2] #16: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc8c5d191) not found (maybe expired)
2014-10-20, 13:06:16
VPN Log
[g2gips2] #24: [Tunnel Established] IPsec SA established {ESP=>0xce08b895 < 0xca8ee98b}
2014-10-20, 13:06:16
VPN Log
[g2gips2] #16: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xcbb5aca6) not found (maybe expired)
2014-10-20, 14:05:03
VPN Log
[g2gips2] #25: [Tunnel Established] IPsec SA established {ESP=>0xc84ace20 < 0xc66ee4e5}
2014-10-20, 14:05:03
VPN Log
[g2gips2] #16: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xce08b895) not found (maybe expired)
2014-10-20, 14:13:46
VPN Log
[g2gips2] #26: [Tunnel Established] sent MR3, ISAKMP SA established
2014-10-20, 15:03:54
VPN Log
[g2gips2] #27: [Tunnel Established] IPsec SA established {ESP=>0xc8808731 < 0xc6aaaf12}
2014-10-20, 15:03:54
VPN Log
[g2gips2] #26: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc84ace20) not found (maybe expired)
2014-10-20, 16:02:47
VPN Log
[g2gips2] #28: [Tunnel Established] IPsec SA established {ESP=>0xc20db40f < 0xcbcbb7c5}
2014-10-20, 16:02:47
VPN Log
[g2gips2] #26: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc8808731) not found (maybe expired)
2014-10-20, 17:01:39
VPN Log
[g2gips2] #29: [Tunnel Established] IPsec SA established {ESP=>0xc8f8b88c < 0xc87177ac}
2014-10-20, 17:01:39
VPN Log
[g2gips2] #26: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc20db40f) not found (maybe expired)
2014-10-20, 18:00:24
VPN Log
[g2gips2] #30: [Tunnel Established] IPsec SA established {ESP=>0xc24edeb7 < 0xc31180a7}
2014-10-20, 18:00:24
VPN Log
[g2gips2] #26: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc8f8b88c) not found (maybe expired)
2014-10-20, 18:59:12
VPN Log
[g2gips2] #31: [Tunnel Established] IPsec SA established {ESP=>0xcf388896 < 0xcca051f9}
2014-10-20, 18:59:12
VPN Log
[g2gips2] #26: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc24edeb7) not found (maybe expired)
2014-10-20, 19:57:59
VPN Log
[g2gips2] #32: [Tunnel Established] IPsec SA established {ESP=>0xcb12a9c8 < 0xc6d3e8a4}
2014-10-20, 19:57:59
VPN Log
[g2gips2] #26: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xcf388896) not found (maybe expired)
2014-10-20, 20:56:46
VPN Log
[g2gips2] #33: [Tunnel Established] IPsec SA established {ESP=>0xcdc041c8 < 0xc69fa232}
2014-10-20, 20:56:46
VPN Log
[g2gips2] #26: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xcb12a9c8) not found (maybe expired)
2014-10-20, 21:55:36
VPN Log
[g2gips2] #34: [Tunnel Established] IPsec SA established {ESP=>0xc4f97df6 < 0xc4a67abd}
2014-10-20, 21:55:36
VPN Log
[g2gips2] #26: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xcdc041c8) not found (maybe expired)
2014-10-20, 22:12:56
VPN Log
[g2gips2] #35: [Tunnel Established] sent MR3, ISAKMP SA established
2014-10-20, 22:54:27
VPN Log
[g2gips2] #36: [Tunnel Established] IPsec SA established {ESP=>0xc3716585 < 0xc41ab42b}
2014-10-20, 22:54:27
VPN Log
[g2gips2] #35: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc4f97df6) not found (maybe expired)
2014-10-20, 23:53:13
VPN Log
[g2gips2] #37: [Tunnel Established] IPsec SA established {ESP=>0xcfc747c8 < 0xc5994856}
2014-10-20, 23:53:13
VPN Log
[g2gips2] #35: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc3716585) not found (maybe expired)
2014-10-21, 00:51:58
VPN Log
[g2gips2] #38: [Tunnel Established] IPsec SA established {ESP=>0xcf4ea957 < 0xc566c6d3}
2014-10-21, 00:51:58
VPN Log
[g2gips2] #35: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xcfc747c8) not found (maybe expired)
2014-10-21, 01:50:48
VPN Log
[g2gips2] #39: [Tunnel Established] IPsec SA established {ESP=>0xc4f4ddc5 < 0xc852f0a8}
2014-10-21, 01:50:48
VPN Log
[g2gips2] #35: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xcf4ea957) not found (maybe expired)
2014-10-21, 02:49:33
VPN Log
[g2gips2] #40: [Tunnel Established] IPsec SA established {ESP=>0xc4d14f63 < 0xc841322e}
2014-10-21, 02:49:33
VPN Log
[g2gips2] #35: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc4f4ddc5) not found (maybe expired)
2014-10-21, 03:48:17
VPN Log
[g2gips2] #41: [Tunnel Established] IPsec SA established {ESP=>0xcab61c1d < 0xc8e06d65}
2014-10-21, 03:48:17
VPN Log
[g2gips2] #35: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc4d14f63) not found (maybe expired)
2014-10-21, 04:47:10
VPN Log
[g2gips2] #42: [Tunnel Established] IPsec SA established {ESP=>0xcc4d0867 < 0xc5370a2f}
2014-10-21, 04:47:10
VPN Log
[g2gips2] #35: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xcab61c1d) not found (maybe expired)
2014-10-21, 05:45:57
VPN Log
[g2gips2] #43: [Tunnel Established] IPsec SA established {ESP=>0xcb8459a9 < 0xcab43b24}
2014-10-21, 05:45:57
VPN Log
[g2gips2] #35: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xcc4d0867) not found (maybe expired)
2014-10-21, 06:12:00
VPN Log
[g2gips2] #44: [Tunnel Established] sent MR3, ISAKMP SA established
2014-10-21, 06:44:47
VPN Log
[g2gips2] #45: [Tunnel Established] IPsec SA established {ESP=>0xc1d633d9 < 0xc5b9214f}
2014-10-21, 06:44:47
VPN Log
[g2gips2] #44: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xcb8459a9) not found (maybe expired)
2014-10-21, 07:43:37
VPN Log
[g2gips2] #46: [Tunnel Established] IPsec SA established {ESP=>0xc8a6235e < 0xc549a18d}
2014-10-21, 07:43:37
VPN Log
[g2gips2] #44: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc1d633d9) not found (maybe expired)
2014-10-21, 08:42:28
VPN Log
[g2gips2] #47: [Tunnel Established] IPsec SA established {ESP=>0xc563592a < 0xc033e13d}
2014-10-21, 08:42:28
VPN Log
[g2gips2] #44: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc8a6235e) not found (maybe expired)
2014-10-21, 09:41:12
VPN Log
[g2gips2] #48: [Tunnel Established] IPsec SA established {ESP=>0xc6c5e0b6 < 0xc9acd1e2}
2014-10-21, 09:41:12
VPN Log
[g2gips2] #44: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc563592a) not found (maybe expired)
2014-10-21, 10:40:03
VPN Log
[g2gips2] #49: [Tunnel Established] IPsec SA established {ESP=>0xc49d311a < 0xca8961e8}
2014-10-21, 10:40:03
VPN Log
[g2gips2] #44: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc6c5e0b6) not found (maybe expired)
2014-10-21, 11:38:53
VPN Log
[g2gips2] #50: [Tunnel Established] IPsec SA established {ESP=>0xc682b92b < 0xc01e3e5f}
2014-10-21, 11:38:53
VPN Log
[g2gips2] #44: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc49d311a) not found (maybe expired)
2014-10-21, 12:37:41
VPN Log
[g2gips2] #51: [Tunnel Established] IPsec SA established {ESP=>0xc0e9d4eb < 0xc0c1b26a}
2014-10-21, 12:37:41
VPN Log
[g2gips2] #44: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xc682b92b) not found (maybe expired)
2014-10-21, 13:36:29
VPN Log
[g2gips2] #52: [Tunnel Established] IPsec SA established {ESP=>0xc424276a < 0xc0467e19}

Similar Messages

  • RV320 VPN Connection - ignoring Delete SA payload: PROTO_IPSEC_ESP SA

    I have RV320 (Serial Number: NKS17161863 Firmware Version: v1.1.1.19 (2014-12-01, 12:38:04)) 
    and Two RV130:
    RV130 #1 
    System Name: router8E6AAF
    Firmware Version: 1.0.1.3
    Serial Number: CCQ18391LCX
    RV130 # 2
    System Name: router8E6A58
    Firmware Version: 1.0.1.3
    Serial Number: CCQ18391LC4
    The VPN Server is RV320 and the setting is
    http://i.imgur.com/a2iKNVT.png
    The Settings on RV130’s is:
    http://i.imgur.com/ly3bB2Z.png 
    http://i.imgur.com/AB1ImwU.png
    And Log is sending me errors 
    2015-04-03, 11:10:19 VPN Log [g2gips2] #361: [Tunnel Established] sent QI2, IPsec SA established {ESP=>0xd2c697fd < 0xc996e19a}
    2015-04-03, 11:12:34 VPN Log [g2gips0] #362: [Tunnel Established] ISAKMP SA established
    2015-04-03, 11:26:04 ALLOW UDP 91.196.8.139:500 -> 95.51.168.122:500 on eth2
    2015-04-03, 11:26:04 VPN Log [g2gips0] #363: [Tunnel Established] IPsec SA established {ESP=>0x33533382 < 0xc3fbe46e}
    2015-04-03, 11:26:04 VPN Log [g2gips0] #362: [Tunnel Authorize Fail] ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0x96a8668e) not found (maybe expired)
    I thing the last Record is the problem. Can you help me?

    I found an answer.
    The message is informational in nature and is not the cause of any problems. the routers run Linux and use the open source codebase....
    "When an IPsec SA is about to expire *swan sends a delete SA notification
    to the peer. Since the same IPsec SA is also about to expire on the
    peer side, often the peer is a little faster and has already deleted
    the IPsec SA itself. Thus when the delete SA message arrives, the IPsec SA
    doesn't exist anymore and the warning below is issued in the log.
    If you want to study the SA renewal and deletion mechanism in detail
    you can do this by activating the following debug option
       ipsec whack --debug-lifecycle"
    https://lists.openswan.org/pipermail/users/2004-September/002128.html
    In my case, the ISP is Comcast and they were filtering UDP packets, causing the issue. A call to their business tech support and an explanation of our need to use an IPSEC VPN  tunnel which uses UDP resolved the problem.
    The Cisco VPN routers (RV325 & RV320) work great and I haven't had any problems since. There is excellent tech support from Cisco, you just have to follow their procedures and register the serial numbers of your devices. They helped me even without a service contract, but I purchased one anyway. It's only $56 for a 3 year support agreement at CDW.
    Hope that helps.

  • RV320 VPN over USB1

    I setup the RV320 and am using the USB1 interface until I get my permanent WAN interface ordered.  I can get to the internet with no issues.  I setup EasyVPN and PPTP but cannot get access remotely into the VPN.  I setup an access rule to allow ALL traffic from USB1 into the network. I also created a user in the User management page. 
    When trying to connect with the Cisco VPN Client I get the following in the router log file:
    Aug 1 13:42:04 2013
    VPN Log
    packet from 70.155.120.114:22520: [Tunnel Authorize Fail] no connection has been authorized with policy=PSK+AGGRESSIVE+XAUTHPSK+XAUTHSERVER
    Aug 1 13:42:04 2013
    Connection Accepted
    IN=ppp3000 OUT= MAC= SRC=70.155.120.114 DST=166.156.174.130 DMAC=45:00:03:7f:95:8c SMAC=00:00:6d:11:a0:b5 LEN=895 TOS=0x00 PREC=0x00 TTL=109 ID=38284 PROTO=UDP SPT=22520 DPT=500 LEN=875
    When trying to connect via PPTP I get the following error at the client:
    Error 678: The remote computer did not respond.
    What am I missing?
    Does the USB1 interface allow remote access?
    Thanks

    Just an update.   Finally on my 3rd RV320 I was able to get the current firmware loaded w/o the unit locking up.  I used XP instead of Win7 this time just in case that was the problem.
    I did get the SSL VPN to function over the USB1 modem.  No luck still with EasyVPN or PPTP.
    My SSL VPN drops me into VLAN4 with address of 192.168.4.x.  I can PCAnywhere to a PC on that VLAN and from there get to devices on VLAN3 (192.168.3.x) which is my mgmt VLAN by creating some access rules for that one PC we connect remotely into.
    I've tried various rules to let me get directly to the mgmt VLAN direct from the remote PC but have not had any luck.  Any thoughts on what to try?  I have InterVLAN routing turned on for VLAN3 and VLAN4.  I need access to devices on both VLANs so it's not just a matter of changing the SSL remote users ip to 192.168.3.x.

  • Esy VPN log

    I have configured Easy VPN on Cisco 1751 router, clients are logging via cisco vpn client from windows xp/2000,power MAC & Redhat Linux. i wanted to see the logging information of the users like at what time the user has logged-in & logged-out, then the public IP address from which he tried logging-in etc... how do i do that?
    any one would be highly appreciated.
    also is there any client for Intel MAC?

    Diane
    I have limited experience with the 3005 concentrator. But with other 3000 concentrators that I have worked with you can configure the logging level for the various reports. It sounds like your logging level is set to not provide much detail (and minimize volitility of the log file). Perhaps you can experiment with changing the logging level (higher numbers represent more detail) and see if you get more of what you are looking for.
    Having said that I am not sure that the concentrator log messages (at any level) are goig to be very helpful about why webmail did not work. And my experience is that even at greater level of detail they are not real helpful about why an individual user got disconnected.
    Good luck.
    HTH
    Rick

  • How do I set the logging level with the plug-in 1.4

    I am writing an applet that will be hosted in the plug-in version 1.4. I'd like to set up some logging statements using the java.util.logging API. I have successfully got it to print out log messages, but it is not printing anything below level INFO. How can I set it up to print out log statements at the FINEST level?

    If you are using the default logger for logging from the applet, the default log level from the logging.properties file in your JRE lib directory is the place. There is an entry
        .level= INFO In this file. You can modify this entry.
    This is a a roundabout way of achieving it. since we are modifying the default log level here, it will be used by other java applications as well. I am looking for a better solution.

  • Error while Changing log level in Agentry 6.0.44.1

    Hi ,
    I am trying to change the log level from the Agentry Administration client, but i am getting the below error message.
    And it is showing any option to change the log levels for users. How can I change log level for users also.
    How can I resolve this error.
    Regards,
    Shyam

    Shyam,
    This is fixed or planned fixed in 6.0.46 Agentry Server (supposed to be available anytime soon in the Service Marketplace - it was submitted already to the SMP team). The fix was in SMP 2.3 and SMP 3.0 but it was ported back to the Agentry 6.0.X release. If you have no access to the Agentry 6.0.X patches this means that your SAP License is preventing you from downloading it. You may need to contact the SAP CIC (customer interaction center) group.
    Or you can do the manual setup for a workaround for now.
    SAP KBA article: 2048202 - AgentryGUI does not allow to change log settings - Not all setttings were successfully changed.
    Regards,
    Mark Pe
    SAP Senior Support Engineer (Mobility)

  • Setting log level of an appender

    I have 2 appenders in my logger.
    mergeLogger.addAppender( consoleAppender );
    mergeLogger.addAppender( fileAppender );
    to set the log level I use logger.setLevel( XX ) but this applies to all appenders
    Is it possible to set the logging level for each appender to different levels?

    Have you read the log4j documentation?

  • Setting logging level

    Hello folks;
    Is there a way to set the logging threshold for log messages sent to
    the weblogic log? I see where to adjust logging threshold for the
    standard out, but this level doesn't seem to affect the threshold for
    messages getting to the physical logfile. Unlike the log4j classes
    that seem to back up weblogic's logging ( I checked this out by
    looking in the weblogic.jar file); there are no methods for setting
    the logging threshold on weblogic's log classes.
    Cheers-

    I was mistaken about the log4j stuff being used under the covers.
    However, changing the logging threshold does not seem to affect
    messages sent to the log for my server. I just tested this again by
    setting the log level to "CRITICAL" in the console. Sure enough the
    messages sent to the standard out console are affected, but the
    messages sent to the physical log are not affected. I still get Info,
    Notice, etc messages there--- but nearly no messages to the standard
    out console.
    This was done on version 7.0 of weblogic.
    Cheers--
    "Jane Sampson" <[email protected]> wrote in message news:<3e5a84b4$[email protected]>...
    Hi Steve,
    If you set the logging level in the Logging tab on Server Configuration, it
    DOES affect the level of messages that are logged to both stdout and the
    physical log. Are you sure you are looking at the correct log file?
    Also, none of the weblogic classes use log4j. What version did you find
    log4j classes included in the weblogic.jar??
    Jane
    BEA Support

  • Could you tell me what's the meaning of the logfile-path and log-level?

    we are running an productive xml database. but it is not stable now. Sometime it would report resource conflict error while you access xmldb via http protocol. I read the database logs and listener logs, but no abnormal message could be found. So, I want to find more information from the xmldb logs. While I run select DBMS_XDB.cfg_get().getclobval() from dual, I found that there are several logfile-path and log-level tags and I guess that these would be xmldb logs. Does anyone know what's the meaning of these tags?

    I wondered about that one often too. I didn't have a chance yet to investigate (but maybe Mark will elaborate a little here), my guess is that it / or will be a possibility to enable tracing regarding the protocols or servlets.
    Though It look like if you enable it it will trace to the XML file defined in the xdbconfig.xml. I also guess that (because there is also a XSD counterpart) that one could create an resource that streams the errors into a XDB ftp or http or ... xmltype table based on these settings.
    This would be great because it would mature the protocol server regarding functionality. You could enable the tracing and see what happens. Until now the documentation doesn't give much extra insight...
    <!-- FTP specific -->
    <element name="ftpconfig">
    <complexType><sequence>
    <element name="ftp-port" type="unsignedShort" default="2100"/>
    <element name="ftp-listener" type="string"/>
    <element name="ftp-protocol" type="string"/>
    <element name="logfile-path" type="string" default="/sys/log/ftplog.xml"/>
    <element name="log-level" type="unsignedInt" default="0"/>
    <element name="session-timeout" type="unsignedInt" default="6000"/>
    <element name="buffer-size" default="8192">
    <simpleType>
    <restriction base="unsignedInt">
    <minInclusive value="1024"/> <!-- 1KB -->
    <maxInclusive value="1048496"/> <!-- 1MB -->
    </restriction>
    </simpleType>
    </element>
    <element name="ftp-welcome-message" type="string" minOccurs="0"
    maxOccurs="1"/>
    </sequence></complexType>
    </element>
    <!-- HTTP specific -->
    <element name="httpconfig">
    <complexType><sequence>
    <element name="http-port" type="unsignedShort" default="8080"/>
    <element name="http-listener" type="string"/>
    <element name="http-protocol" type="string"/>
    <element name="max-http-headers" type="unsignedInt" default="64"/>
    <element name="max-header-size" type="unsignedInt" default="4096"/>
    <element name="max-request-body" type="unsignedInt" default="2000000000"
    minOccurs="1"/>
    <element name="session-timeout" type="unsignedInt" default="6000"/>
    <element name="server-name" type="string"/>
    <element name="logfile-path" type="string"
    default="/sys/log/httplog.xml"/>
    <element name="log-level" type="unsignedInt" default="0"/>
    <element name="servlet-realm" type="string" minOccurs="0"/>
    ...etc...

  • ODI Log Level

    Hi,
    I am looking for a description of ODI Log Levels.
    I know that the log level controls the details of the log output in ODI operator, but does exists some more detailed documentation about it?
    I would need information like what details are shown in which log level.
    Thanks in advance!
    Cheers,
    H.

    It is important to understand that the way odi works, it uses the "log" to drive all executuions. When you start a scenario, it copies eachof the steps of the scenarios into the execution log with the session ID, and wih a status of Waiting. As it executes each, it marks it as being executed, and when complete, marks it as completed (in or or successfully). When it has executed all the steps, it will go back to the log and selectively delete the entries there. When you execute the scenario, you execute it with a log-level of 0-5, and ODI will basically delete all entries in the log with a level > your chosen level. If you inspect the steps of a KM, Procedure etc, you will see that each has a log-level associated with it. This is what will decide if it is to be kept or not.
    If the session ends in failure, it will keep all the entries.

  • Eclipselink log levels issue with weak references

    Hi all,
    Is it possible to get null pointer exceptions if the log level in eclipselink is set to FINEST and you are logging a weak reference probably in a IdentityWeakReferenceMap and getting a null pointer exception because the weak ref has been garbage collected ?
    -Prashanth.

    I am getting Nullpointer exception when I set log level to FINER or FINEST in persistence.xml.
    DisRootEntityRef entity which is seen in below log has week reference in erml.
    Here is the exception full trace:
    EL Warning: 2010-05-31 17:06:52.328--UnitOfWork(19025200)--Thread(Thread[)--java.lang.NullPointerException
    at oracle.communications.platform.entity.impl.DisRootEntityRefDAO.getRootEntity(DisRootEntityRefDAO.java:300)
    at oracle.communications.platform.entity.impl.DisRootEntityRefDAO.getToString(DisRootEntityRefDAO.java:591)
    at oracle.communications.platform.entity.impl.DisRootEntityRefDAO.toString(DisRootEntityRefDAO.java:584)
    at java.text.MessageFormat.subformat(MessageFormat.java:1246)
    at java.text.MessageFormat.format(MessageFormat.java:836)
    at java.text.Format.format(Format.java:140)
    at java.text.MessageFormat.format(MessageFormat.java:812)
    at org.eclipse.persistence.internal.localization.EclipseLinkLocalization.buildMessage(EclipseLinkLocalization.java:77)
    at org.eclipse.persistence.internal.localization.TraceLocalization.buildMessage(TraceLocalization.java:30)
    at org.eclipse.persistence.logging.AbstractSessionLog.formatMessage(AbstractSessionLog.java:801)
    at org.eclipse.persistence.platform.server.ServerLog.log(ServerLog.java:71)
    at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:2571)
    at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3664)
    at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3636)
    at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3612)
    at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3534)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.logDebugMessage(UnitOfWorkImpl.java:5397)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerExistingObject(UnitOfWorkImpl.java:3874)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerExistingObject(UnitOfWorkImpl.java:3844)
    at org.eclipse.persistence.queries.ObjectBuildingQuery.registerIndividualResult(ObjectBuildingQuery.java:362)
    at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildWorkingCopyCloneNormally(ObjectBuilder.java:588)
    at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObjectInUnitOfWork(ObjectBuilder.java:549)
    at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:489)
    at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:441)
    at org.eclipse.persistence.queries.ObjectLevelReadQuery.buildObject(ObjectLevelReadQuery.java:635)
    at org.eclipse.persistence.queries.ReadAllQuery.registerResultInUnitOfWork(ReadAllQuery.java:838)
    at org.eclipse.persistence.queries.ReadAllQuery.executeObjectLevelReadQuery(ReadAllQuery.java:464)
    at org.eclipse.persistence.queries.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:997)
    at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:670)
    at org.eclipse.persistence.queries.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:958)
    at org.eclipse.persistence.queries.ReadAllQuery.execute(ReadAllQuery.java:432)
    at org.eclipse.persistence.queries.ObjectLevelReadQuery.executeInUnitOfWork(ObjectLevelReadQuery.java:1021)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2858)
    at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1225)
    at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1207)
    at org.eclipse.persistence.internal.indirection.QueryBasedValueHolder.instantiate(QueryBasedValueHolder.java:85)
    at org.eclipse.persistence.internal.indirection.QueryBasedValueHolder.instantiate(QueryBasedValueHolder.java:75)
    at org.eclipse.persistence.internal.indirection.DatabaseValueHolder.getValue(DatabaseValueHolder.java:83)
    at org.eclipse.persistence.internal.indirection.UnitOfWorkValueHolder.instantiateImpl(UnitOfWorkValueHolder.java:161)
    at org.eclipse.persistence.internal.indirection.UnitOfWorkValueHolder.instantiate(UnitOfWorkValueHolder.java:230)
    at org.eclipse.persistence.internal.indirection.DatabaseValueHolder.getValue(DatabaseValueHolder.java:83)
    at org.eclipse.persistence.indirection.IndirectList.buildDelegate(IndirectList.java:237)
    at org.eclipse.persistence.indirection.IndirectList.getDelegate(IndirectList.java:397)
    at org.eclipse.persistence.indirection.IndirectList$1.(IndirectList.java:525)
    at org.eclipse.persistence.indirection.IndirectList.listIterator(IndirectList.java:524)
    at org.eclipse.persistence.indirection.IndirectList.iterator(IndirectList.java:488)
    at oracle.communications.platform.persistence.impl.PomsArrayList.iterator(PomsArrayList.java:598)
    at oracle.communications.platform.entity.impl.DisResultGroupDAO.getRootEntities(DisResultGroupDAO.java:765)
    at oracle.communications.integrity.scanCartridges.sdk.RootEntityLoaderImpl.(RootEntityLoaderImpl.java:37)
    at oracle.communications.integrity.scanCartridges.sdk.BaseDiscrepancyDetectionController.init(BaseDiscrepancyDetectionController.java:71)
    at oracle.communications.integrity.scanCartridges.sdk.BaseDiscrepancyDetectionController.invoke(BaseDiscrepancyDetectionController.java:41)
    at oracle.communications.integrity.cartridges.ciscoextensioncartridge.detectionplugins.ciscodiscrepancydetectionsample.CiscoDiscrepancyDetectionSampleMessageDrivenBean.onMessage(CiscoDiscrepancyDetectionSampleMessageDrivenBean.java:109)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy343.onMessage(Unknown Source)
    at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
    at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
    at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
    at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
    at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
    at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    oracle.communications.integrity.cartridges.ciscoextensioncartridge.detectionplugins.ciscodiscrepancydetectionsample.CiscoDiscrepancyDetectionSampleMessageDrivenBean
    java.lang.NullPointerException
    at oracle.communications.platform.entity.impl.DisRootEntityRefDAO.getRootEntity(DisRootEntityRefDAO.java:300)
    at oracle.communications.platform.entity.impl.DisRootEntityRefDAO.getToString(DisRootEntityRefDAO.java:591)
    at oracle.communications.platform.entity.impl.DisRootEntityRefDAO.toString(DisRootEntityRefDAO.java:584)
    at java.text.MessageFormat.subformat(MessageFormat.java:1246)
    at java.text.MessageFormat.format(MessageFormat.java:836)
    at java.text.Format.format(Format.java:140)
    at java.text.MessageFormat.format(MessageFormat.java:812)
    at org.eclipse.persistence.internal.localization.EclipseLinkLocalization.buildMessage(EclipseLinkLocalization.java:77)
    at org.eclipse.persistence.internal.localization.TraceLocalization.buildMessage(TraceLocalization.java:30)
    at org.eclipse.persistence.logging.AbstractSessionLog.formatMessage(AbstractSessionLog.java:801)
    at org.eclipse.persistence.platform.server.ServerLog.log(ServerLog.java:71)
    at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:2571)
    at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3664)
    at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3636)
    at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3612)
    at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3534)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.logDebugMessage(UnitOfWorkImpl.java:5397)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerExistingObject(UnitOfWorkImpl.java:3874)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerExistingObject(UnitOfWorkImpl.java:3844)
    at org.eclipse.persistence.queries.ObjectBuildingQuery.registerIndividualResult(ObjectBuildingQuery.java:362)
    at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildWorkingCopyCloneNormally(ObjectBuilder.java:588)
    at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObjectInUnitOfWork(ObjectBuilder.java:549)
    at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:489)
    at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:441)
    at org.eclipse.persistence.queries.ObjectLevelReadQuery.buildObject(ObjectLevelReadQuery.java:635)
    at org.eclipse.persistence.queries.ReadAllQuery.registerResultInUnitOfWork(ReadAllQuery.java:838)
    at org.eclipse.persistence.queries.ReadAllQuery.executeObjectLevelReadQuery(ReadAllQuery.java:464)
    at org.eclipse.persistence.queries.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:997)
    at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:670)
    at org.eclipse.persistence.queries.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:958)
    at org.eclipse.persistence.queries.ReadAllQuery.execute(ReadAllQuery.java:432)
    at org.eclipse.persistence.queries.ObjectLevelReadQuery.executeInUnitOfWork(ObjectLevelReadQuery.java:1021)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2858)
    at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1225)
    at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1207)
    at org.eclipse.persistence.internal.indirection.QueryBasedValueHolder.instantiate(QueryBasedValueHolder.java:85)
    at org.eclipse.persistence.internal.indirection.QueryBasedValueHolder.instantiate(QueryBasedValueHolder.java:75)
    at org.eclipse.persistence.internal.indirection.DatabaseValueHolder.getValue(DatabaseValueHolder.java:83)
    at org.eclipse.persistence.internal.indirection.UnitOfWorkValueHolder.instantiateImpl(UnitOfWorkValueHolder.java:161)
    at org.eclipse.persistence.internal.indirection.UnitOfWorkValueHolder.instantiate(UnitOfWorkValueHolder.java:230)
    at org.eclipse.persistence.internal.indirection.DatabaseValueHolder.getValue(DatabaseValueHolder.java:83)
    at org.eclipse.persistence.indirection.IndirectList.buildDelegate(IndirectList.java:237)
    at org.eclipse.persistence.indirection.IndirectList.getDelegate(IndirectList.java:397)
    at org.eclipse.persistence.indirection.IndirectList$1.(IndirectList.java:525)
    at org.eclipse.persistence.indirection.IndirectList.listIterator(IndirectList.java:524)
    at org.eclipse.persistence.indirection.IndirectList.iterator(IndirectList.java:488)
    at oracle.communications.platform.persistence.impl.PomsArrayList.iterator(PomsArrayList.java:598)
    at oracle.communications.platform.entity.impl.DisResultGroupDAO.getRootEntities(DisResultGroupDAO.java:765)
    at oracle.communications.integrity.scanCartridges.sdk.RootEntityLoaderImpl.(RootEntityLoaderImpl.java:37)
    at oracle.communications.integrity.scanCartridges.sdk.BaseDiscrepancyDetectionController.init(BaseDiscrepancyDetectionController.java:71)
    at oracle.communications.integrity.scanCartridges.sdk.BaseDiscrepancyDetectionController.invoke(BaseDiscrepancyDetectionController.java:41)
    at oracle.communications.integrity.cartridges.ciscoextensioncartridge.detectionplugins.ciscodiscrepancydetectionsample.CiscoDiscrepancyDetectionSampleMessageDrivenBean.onMessage(CiscoDiscrepancyDetectionSampleMessageDrivenBean.java:109)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy343.onMessage(Unknown Source)
    at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
    at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
    at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
    at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
    at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
    at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

  • How to change log level in log4j at runtime

    Hi,
    I have a small requirement where the default log level is info, but if the user wants to invoke the Java program with debug level, the Debug should start off. I am trying to achieve this using this code..
              Logger root = Logger.getRootLogger();
              root.setLevel(Level.DEBUG);
              log.debug("This is debug");When I do this, the debug statement at the end does not print.
    Then I thought may be the root logger level is not propagated after the initialization at start up, so I tried this
              log.setLevel(Level.DEBUG);
              log.info("This is info");
              log.debug("This is debug");
              log.info("Log level is " + log.getLevel());
              log.info(log.isDebugEnabled());The info statement prints "this is info" then the next info statement prints "log level is DEBUG" the next statement prints true but the intermediate debug statement does not print.
    I have done this before in a Web app and it works just fine. I do not understand what is going on. Can someone please help me understand this.

    I am not really familiar with Log4J, but in java.util.logging you define both a loglevel on the logger and the Handler that is actually responsible for outputting. A quick look on the Log4J sites shows that those are called 'appenders' in Log4J. So you might want to look if your appender is actually configured to output DEBUG-level statements.

  • How to set more detail log level for http

    Hi,
    With Java Enterprise System 2003 I want to see when a user login to the Messenger Express in the http log. How could I set a log level so I can see this?
    I do not know the the default log level for http and I would like to set a log level that show me more information
    could this be the command?
    configutil -o logfile.http.loglevel -v level Information

    configutil -o logfile.http.loglevel -v Information
    would be the correct command to set the log level to "information".
    Other valid levels include, "debug", "notice" (this is the default), "warning".
    You have t restart the webmail daemon to make this take effect.
    stop-msg http; start-msg http

  • Logging Level

    hi,
    I have been following the below perf tuning url:
    http://www.oraclebidwh.com/2010/02/performance-tuning-in-obiee/
    I have been reviewing section3, regarding turing off logging, it states the following:
    +3) Turning off Logging+
    Logging can affect in performance  of  Oracle BI Server and can create large log files. Logging can be used in problem solving and trouble shooting problematic queries.  So when it is necessary then only set logging level to 0 to 2. Set log level greater than 2 is not recommended by Oracle.
    investigating via the admin tool, using security manager
    Manage > Security > Security manager
    We have some OBIEE users that have logging levels set at 2, some set at 3, some set at 4, and some set at 5.
    As an example, PUBLIC user is set at 4, Administrator is set at 5.
    Also, in the 10.1.3.4 docs http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31770.pdf , on page 216 it states:
    NOTE: Logging levels greater than 2 should be used only with the assistance of Technical Support.
    So with having logging levels of 3, 4 , & even 5 will it cause performance issues?
    I'd be very grateful of the advice.
    & thanks in advance

    >
    So with having logging levels of 3, 4 , & even 5 will it cause performance issues?
    I'd be very grateful of the advice.
    & thanks in advanceYes, the BI-server will have to a lot of write actions to the server disk. This means it will have to 'wait' several times during the execution until the logbuffer is written to disk
    regards
    John
    http://obiee101.blogspot.com/
    http://obiee11g.com/

  • The problem about  the Log Level

    Hi everyone,
    The Log Level of Oracle Application Server includes NULL,Severe,Warning,Info,Config,fine,finer,finest.
    Which log level is the highest ?
    I want to get more message about My Esb instances,How to set the log level ?

    finest is the highest level logging and can either be turned on for all logs or just specific logs within the Enterprise manager.

Maybe you are looking for