[ 
https://issues.apache.org/jira/browse/LOG4NET-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437781#comment-17437781
 ] 

Abhishek Tiwari edited comment on LOG4NET-678 at 11/3/21, 7:38 AM:
-------------------------------------------------------------------

Its not a permission issue because other Oracle ERP system can not give every 
object excess to our application ,they are using some DB objects for there 
internal procesing .i don't understand when i am disabling log4net then  other 
System Db object which they havn't given access to our application is start 
working.


was (Author: [email protected]):
Its not a permission issue because other Oracle ERP system can not give every 
object excess to our application ,they are using some DB objects for there 
internal procesing .i don't understand when i am disabling the other System Db 
object which they havn't given access is start working.

> AdoNetAppender creating some session issue while calling procedure from 
> application which contains DB link ERP package
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-678
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-678
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 2.0.8
>         Environment: Dot Net ,Oracle 
>            Reporter: Abhishek Tiwari
>            Priority: Blocker
>             Fix For: 2.0.8, 2.1.0
>
>   Original Estimate: 0.2h
>  Remaining Estimate: 0.2h
>
> Dear Team,
> I am using log4net for Database logging in Oracle data base 
> Oracle.ManagedDataAccess.Client using C#,When i am enabling Log4net 
> AdoNetAppender then calling procedure which contains DB link package of ERP 
> data Base(different system) there are getting some session related 
> problem,when i am disabling the AdoNetAppender then its start working.Kindly 
> help .i didn't find any solution .



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to