<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ArcSDE Trace client login in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/arcsde-trace-client-login/m-p/156263#M8752</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;ArcSDE supports tracing (SDETRACE variable), but that's a client library command &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;logging capability (only mentioned due to probability of free text search hits).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;To track down a rogue application server client, you should just need to look in the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;application server's logs.&amp;nbsp; A rogue Direct Connect client would log to it's own SDEHOME,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;so you'd need to search for all clients (which is a tad harder), but Oracle should be able&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;to log these connection failures, so the Oracle logs might give more infomation&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 20 Sep 2012 10:49:42 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2012-09-20T10:49:42Z</dc:date>
    <item>
      <title>ArcSDE Trace client login</title>
      <link>https://community.esri.com/t5/data-management-questions/arcsde-trace-client-login/m-p/156262#M8751</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Does anybody knows how can I see from what machines clients are logging to ArcSDE?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We have a strange problem. Changed password for an account and somewhere there still is a user or service with the old password and off course the account becomes locked in Oracle very frequently. I don't know where can I find client machines of failed loggins&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank You &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Andrei Gosman&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Sep 2012 08:13:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/arcsde-trace-client-login/m-p/156262#M8751</guid>
      <dc:creator>AndreiGosman</dc:creator>
      <dc:date>2012-09-20T08:13:50Z</dc:date>
    </item>
    <item>
      <title>Re: ArcSDE Trace client login</title>
      <link>https://community.esri.com/t5/data-management-questions/arcsde-trace-client-login/m-p/156263#M8752</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;ArcSDE supports tracing (SDETRACE variable), but that's a client library command &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;logging capability (only mentioned due to probability of free text search hits).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;To track down a rogue application server client, you should just need to look in the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;application server's logs.&amp;nbsp; A rogue Direct Connect client would log to it's own SDEHOME,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;so you'd need to search for all clients (which is a tad harder), but Oracle should be able&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;to log these connection failures, so the Oracle logs might give more infomation&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Sep 2012 10:49:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/arcsde-trace-client-login/m-p/156263#M8752</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2012-09-20T10:49:42Z</dc:date>
    </item>
  </channel>
</rss>

