possible to log only JDBC connections?

Hi,

today I was asked if it's possible to log/monitor only JDBC connections?
So anyone here who can give some hints?

SYBASE 15.0.2 / 15.0.3

Regards,
Heinz

0
ISO
1/14/2011 5:25:30 PM
sybase.ase.administration 7058 articles. 2 followers. Follow

7 Replies
769 Views

Similar Articles

[PageSpeed] 51

No solutions, no recommendations, just some questions ...

More details about what you mean by 'log/monitor'?  MDA tables?  auditing?  monserver/histserver?  something else?

Do you already have a way to tell which connections are using JDBC?  or is this also something you're looking for?


Heinz M�ller wrote:
> Hi,
> 
> today I was asked if it's possible to log/monitor only JDBC connections?
> So anyone here who can give some hints?
> 
> SYBASE 15.0.2 / 15.0.3
> 
> Regards,
> Heinz
> 
0
Mark
1/14/2011 8:30:57 PM
Am 14.01.2011 21:30, schrieb Mark A. Parsons:
> No solutions, no recommendations, just some questions ...
>
> More details about what you mean by 'log/monitor'? MDA tables? auditing?
> monserver/histserver? something else?
>
> Do you already have a way to tell which connections are using JDBC? or
> is this also something you're looking for?
>
>
> Heinz M�ller wrote:
>> Hi,
>>
>> today I was asked if it's possible to log/monitor only JDBC connections?
>> So anyone here who can give some hints?
>>
>> SYBASE 15.0.2 / 15.0.3
>>
>> Regards,
>> Heinz
>>
Mark,

it's the first time that I have to deal with JDBC. I have taken a look in

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15.0.java/html/java/java32.htm 


It's not so easy to understand because I'm not familiar with JAVA.

So what I mean with "log/monitor" is if a connection to the
ASE is made by a JDBC connection I would be able to monitor that (only 
the information: clientname, ip address, username, date or something 
like that).

At the moment I don't know if there are any JDBC connections from any 
clients/applications.

BTW:
I've read in the above mentioned documentation that if Java isn't 
enabled ( sp_configure "enable java", 0 ) no JDBC connection is 
possible. Is that correct?

Heinz



0
ISO
1/14/2011 9:09:50 PM
First, the 'enable java' parameter in ASE has nothign to do with JDBC 
connections. 'enable java' allows you to use Java classes inside ASE 
itself, as procedures, functions or datatypes.
JDBC connections are TDS connections made by some client application 
that uses the JDBC interface (and jConnect as JDBC driver); the 
connection that comes into ASE is, largely, identical to a conneciton 
made by , for example, isql.

With that out of the way, it depends what you mean with "log or monitor 
JDBC conenctions". The first thing to do is to find out if a connection 
is a JDBC connection. Unfortunately, you cannot determine this by 
looking at sysprocesses: a JDBC connection looks just the same as any 
other one. Only when you know that the connection's hostname or IP 
address or program_name has a specific value that indicates  
(indirectly) that it is a JDBC connection, can you specifically test for it.
Assuming you can do this, you can then enable application tracing for 
that specific connection when it connects to ASE by means of a login 
trigger; see www.sypron.nl/quiz2009a.html#jun09 for details.

In 15.5. ESD#1, there's a feature that lets you determine whether a 
connection is a JDBC connection, but it only writes that information to 
the ASE errorlog file so it won't help you for your purpose. See my 
Techwave 2010 presentation at www.sypron.nl/downloads for details.

HTH,

Rob V.
-----------------------------------------------------------------
Rob Verschoor

Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
and Replication Server 15.0.1/12.5 // TeamSybase

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks&  Recipes for Sybase ASE" (ASE 15 edition)
"The Complete Sybase ASE Quick Reference Guide"
"The Complete Sybase Replication Server Quick Reference Guide"

rob@NO.SPAM.sypron.nl | www.sypron.nl  | Twitter: @rob_verschoor
Sypron B.V., The Netherlands  |  Chamber of Commerce 27138666
-----------------------------------------------------------------



On 14-Jan-2011 22:09, Heinz M�ller wrote:
> Am 14.01.2011 21:30, schrieb Mark A. Parsons:
>> No solutions, no recommendations, just some questions ...
>>
>> More details about what you mean by 'log/monitor'? MDA tables? auditing?
>> monserver/histserver? something else?
>>
>> Do you already have a way to tell which connections are using JDBC? or
>> is this also something you're looking for?
>>
>>
>> Heinz M�ller wrote:
>>> Hi,
>>>
>>> today I was asked if it's possible to log/monitor only JDBC 
>>> connections?
>>> So anyone here who can give some hints?
>>>
>>> SYBASE 15.0.2 / 15.0.3
>>>
>>> Regards,
>>> Heinz
>>>
> Mark,
>
> it's the first time that I have to deal with JDBC. I have taken a look in
>
> http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15.0.java/html/java/java32.htm 
>
>
> It's not so easy to understand because I'm not familiar with JAVA.
>
> So what I mean with "log/monitor" is if a connection to the
> ASE is made by a JDBC connection I would be able to monitor that (only 
> the information: clientname, ip address, username, date or something 
> like that).
>
> At the moment I don't know if there are any JDBC connections from any 
> clients/applications.
>
> BTW:
> I've read in the above mentioned documentation that if Java isn't 
> enabled ( sp_configure "enable java", 0 ) no JDBC connection is 
> possible. Is that correct?
>
> Heinz
>
>
>

0
Rob
1/15/2011 12:30:01 PM
Am 15.01.2011 13:30, schrieb Rob V [ Sybase ]:
> First, the 'enable java' parameter in ASE has nothign to do with JDBC
> connections. 'enable java' allows you to use Java classes inside ASE
> itself, as procedures, functions or datatypes.
> JDBC connections are TDS connections made by some client application
> that uses the JDBC interface (and jConnect as JDBC driver); the
> connection that comes into ASE is, largely, identical to a conneciton
> made by , for example, isql.
>
> With that out of the way, it depends what you mean with "log or monitor
> JDBC conenctions". The first thing to do is to find out if a connection
> is a JDBC connection. Unfortunately, you cannot determine this by
> looking at sysprocesses: a JDBC connection looks just the same as any
> other one. Only when you know that the connection's hostname or IP
> address or program_name has a specific value that indicates (indirectly)
> that it is a JDBC connection, can you specifically test for it.
> Assuming you can do this, you can then enable application tracing for
> that specific connection when it connects to ASE by means of a login
> trigger; see www.sypron.nl/quiz2009a.html#jun09 for details.
>
> In 15.5. ESD#1, there's a feature that lets you determine whether a
> connection is a JDBC connection, but it only writes that information to
> the ASE errorlog file so it won't help you for your purpose. See my
> Techwave 2010 presentation at www.sypron.nl/downloads for details.
>
> HTH,
>
> Rob V.
> -----------------------------------------------------------------
> Rob Verschoor
>
> Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
> and Replication Server 15.0.1/12.5 // TeamSybase
>
> Author of Sybase books (order online at www.sypron.nl/shop):
> "Tips, Tricks& Recipes for Sybase ASE" (ASE 15 edition)
> "The Complete Sybase ASE Quick Reference Guide"
> "The Complete Sybase Replication Server Quick Reference Guide"
>
> rob@NO.SPAM.sypron.nl | www.sypron.nl | Twitter: @rob_verschoor
> Sypron B.V., The Netherlands | Chamber of Commerce 27138666
> -----------------------------------------------------------------
>
>
>
> On 14-Jan-2011 22:09, Heinz M�ller wrote:
>> Am 14.01.2011 21:30, schrieb Mark A. Parsons:
>>> No solutions, no recommendations, just some questions ...
>>>
>>> More details about what you mean by 'log/monitor'? MDA tables? auditing?
>>> monserver/histserver? something else?
>>>
>>> Do you already have a way to tell which connections are using JDBC? or
>>> is this also something you're looking for?
>>>
>>>
>>> Heinz M�ller wrote:
>>>> Hi,
>>>>
>>>> today I was asked if it's possible to log/monitor only JDBC
>>>> connections?
>>>> So anyone here who can give some hints?
>>>>
>>>> SYBASE 15.0.2 / 15.0.3
>>>>
>>>> Regards,
>>>> Heinz
>>>>
>> Mark,
>>
>> it's the first time that I have to deal with JDBC. I have taken a look in
>>
>> http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15.0.java/html/java/java32.htm
>>
>>
>> It's not so easy to understand because I'm not familiar with JAVA.
>>
>> So what I mean with "log/monitor" is if a connection to the
>> ASE is made by a JDBC connection I would be able to monitor that (only
>> the information: clientname, ip address, username, date or something
>> like that).
>>
>> At the moment I don't know if there are any JDBC connections from any
>> clients/applications.
>>
>> BTW:
>> I've read in the above mentioned documentation that if Java isn't
>> enabled ( sp_configure "enable java", 0 ) no JDBC connection is
>> possible. Is that correct?
>>
>> Heinz
>>
>>
>>
>
Rob,

"In 15.5. ESD#1, there's a feature that lets you determine whether a
connection is a JDBC connection, but it only writes that information to
the ASE errorlog file so it won't help you for your purpose."

That would be exactly what I need. I don't need any tracing of that JDBC 
process, I only need the information that someone has _established_ a 
JDBC connection ( and perhaps some info like ip address and loginname).

Ok, I'll have to wait until we migrate to 15.5.

Heinz

0
ISO
1/15/2011 1:38:32 PM
Some additional options ...

1 - if a connection can somehow be designated as a JDBC connection (eg, hostname, IP, program/app name, login) then a 
login trigger could use the 'set [clientname|clientapplname|clienthostname]' commands (eg, 'set clientapplname 
i_am_a_jdbc_connection') to set the corresponding columns in sysprocesses; it now becomes possible to run a monitoring 
process that is triggered off of sysprocesses contents

2 - most (all?) client-side JDBC applications require calls to jconnect stored procs (eg, sp_mda, sp_jdbc_%); if the DBA 
can determine that all JDBC applications make certain jconnect stored proc calls soon after connecting, said jconnect 
stored proc(s) could be modified to make an additional call to a custom stored proc; this custom stored proc could then 
perform the same actions as the login trigger (eg, app tracing ala Rob's link, 'set client%' commands ala option #1 - 
above); in the case where the jconnect proc could be called multiple times, the custom stored proc could use ACFs 
(application context functions) to insure the custom proc's core code is only executed once for the session [eg, declare 
@acf_ret int if get_appcontext('already','executed') = 'yes' return else select @acf_ret = 
set_appcontext('already','executed','yes')]

NOTE:  I have no idea if a JDBC application can function properly without calling any of the jconnect stored procs; if 
so, then obviously option #2 won't work

NOTE:  the custom proc may need to use 'set export_options' to insure certain commands (eg, app tracing 'set' commands) 
remain in force once the custom proc exits

NOTE:  access to ACFs may be granted to logins and roles; the 'grant' command must be executed in the login's default 
database

NOTE:  obviously the customized jconnect proc will need to be reloaded if/when someone reloads the standard jconnect 
stored proc definitions ... a normal caveat to using customized system procedures

3 - obviously a redesign of the JDBC application(s) which requires a custom string in the connection attributes (eg, 
program name), or a custom call to 'set client%' upon connection, would make life a bit easier for the DBA; then there's 
the issue of how well the developers can follow this standard for future JDBC applications development (and yes, this is 
most likely not doable if you have no/little say over JDBC application design and development)


Rob V [ Sybase ] wrote:
> First, the 'enable java' parameter in ASE has nothign to do with JDBC 
> connections. 'enable java' allows you to use Java classes inside ASE 
> itself, as procedures, functions or datatypes.
> JDBC connections are TDS connections made by some client application 
> that uses the JDBC interface (and jConnect as JDBC driver); the 
> connection that comes into ASE is, largely, identical to a conneciton 
> made by , for example, isql.
> 
> With that out of the way, it depends what you mean with "log or monitor 
> JDBC conenctions". The first thing to do is to find out if a connection 
> is a JDBC connection. Unfortunately, you cannot determine this by 
> looking at sysprocesses: a JDBC connection looks just the same as any 
> other one. Only when you know that the connection's hostname or IP 
> address or program_name has a specific value that indicates  
> (indirectly) that it is a JDBC connection, can you specifically test for 
> it.
> Assuming you can do this, you can then enable application tracing for 
> that specific connection when it connects to ASE by means of a login 
> trigger; see www.sypron.nl/quiz2009a.html#jun09 for details.
> 
> In 15.5. ESD#1, there's a feature that lets you determine whether a 
> connection is a JDBC connection, but it only writes that information to 
> the ASE errorlog file so it won't help you for your purpose. See my 
> Techwave 2010 presentation at www.sypron.nl/downloads for details.
> 
> HTH,
> 
> Rob V.
> -----------------------------------------------------------------
> Rob Verschoor
> 
> Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
> and Replication Server 15.0.1/12.5 // TeamSybase
> 
> Author of Sybase books (order online at www.sypron.nl/shop):
> "Tips, Tricks&  Recipes for Sybase ASE" (ASE 15 edition)
> "The Complete Sybase ASE Quick Reference Guide"
> "The Complete Sybase Replication Server Quick Reference Guide"
> 
> rob@NO.SPAM.sypron.nl | www.sypron.nl  | Twitter: @rob_verschoor
> Sypron B.V., The Netherlands  |  Chamber of Commerce 27138666
> -----------------------------------------------------------------
> 
> 
> 
> On 14-Jan-2011 22:09, Heinz M�ller wrote:
>> Am 14.01.2011 21:30, schrieb Mark A. Parsons:
>>> No solutions, no recommendations, just some questions ...
>>>
>>> More details about what you mean by 'log/monitor'? MDA tables? auditing?
>>> monserver/histserver? something else?
>>>
>>> Do you already have a way to tell which connections are using JDBC? or
>>> is this also something you're looking for?
>>>
>>>
>>> Heinz M�ller wrote:
>>>> Hi,
>>>>
>>>> today I was asked if it's possible to log/monitor only JDBC 
>>>> connections?
>>>> So anyone here who can give some hints?
>>>>
>>>> SYBASE 15.0.2 / 15.0.3
>>>>
>>>> Regards,
>>>> Heinz
>>>>
>> Mark,
>>
>> it's the first time that I have to deal with JDBC. I have taken a look in
>>
>> http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15.0.java/html/java/java32.htm 
>>
>>
>> It's not so easy to understand because I'm not familiar with JAVA.
>>
>> So what I mean with "log/monitor" is if a connection to the
>> ASE is made by a JDBC connection I would be able to monitor that (only 
>> the information: clientname, ip address, username, date or something 
>> like that).
>>
>> At the moment I don't know if there are any JDBC connections from any 
>> clients/applications.
>>
>> BTW:
>> I've read in the above mentioned documentation that if Java isn't 
>> enabled ( sp_configure "enable java", 0 ) no JDBC connection is 
>> possible. Is that correct?
>>
>> Heinz
>>
>>
>>
> 
0
Mark
1/15/2011 2:51:31 PM
So if your JDBC applications are calling any of the jconnect stored procs, said jconnect proc(s) could be modified (via 
a call to a custom proc) to dump the desired connectivity info (from sysprocesses or monProcessLookup) into a 
audit/history table.

Heinz M�ller wrote:
> Am 15.01.2011 13:30, schrieb Rob V [ Sybase ]:
>> First, the 'enable java' parameter in ASE has nothign to do with JDBC
>> connections. 'enable java' allows you to use Java classes inside ASE
>> itself, as procedures, functions or datatypes.
>> JDBC connections are TDS connections made by some client application
>> that uses the JDBC interface (and jConnect as JDBC driver); the
>> connection that comes into ASE is, largely, identical to a conneciton
>> made by , for example, isql.
>>
>> With that out of the way, it depends what you mean with "log or monitor
>> JDBC conenctions". The first thing to do is to find out if a connection
>> is a JDBC connection. Unfortunately, you cannot determine this by
>> looking at sysprocesses: a JDBC connection looks just the same as any
>> other one. Only when you know that the connection's hostname or IP
>> address or program_name has a specific value that indicates (indirectly)
>> that it is a JDBC connection, can you specifically test for it.
>> Assuming you can do this, you can then enable application tracing for
>> that specific connection when it connects to ASE by means of a login
>> trigger; see www.sypron.nl/quiz2009a.html#jun09 for details.
>>
>> In 15.5. ESD#1, there's a feature that lets you determine whether a
>> connection is a JDBC connection, but it only writes that information to
>> the ASE errorlog file so it won't help you for your purpose. See my
>> Techwave 2010 presentation at www.sypron.nl/downloads for details.
>>
>> HTH,
>>
>> Rob V.
>> -----------------------------------------------------------------
>> Rob Verschoor
>>
>> Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
>> and Replication Server 15.0.1/12.5 // TeamSybase
>>
>> Author of Sybase books (order online at www.sypron.nl/shop):
>> "Tips, Tricks& Recipes for Sybase ASE" (ASE 15 edition)
>> "The Complete Sybase ASE Quick Reference Guide"
>> "The Complete Sybase Replication Server Quick Reference Guide"
>>
>> rob@NO.SPAM.sypron.nl | www.sypron.nl | Twitter: @rob_verschoor
>> Sypron B.V., The Netherlands | Chamber of Commerce 27138666
>> -----------------------------------------------------------------
>>
>>
>>
>> On 14-Jan-2011 22:09, Heinz M�ller wrote:
>>> Am 14.01.2011 21:30, schrieb Mark A. Parsons:
>>>> No solutions, no recommendations, just some questions ...
>>>>
>>>> More details about what you mean by 'log/monitor'? MDA tables? 
>>>> auditing?
>>>> monserver/histserver? something else?
>>>>
>>>> Do you already have a way to tell which connections are using JDBC? or
>>>> is this also something you're looking for?
>>>>
>>>>
>>>> Heinz M�ller wrote:
>>>>> Hi,
>>>>>
>>>>> today I was asked if it's possible to log/monitor only JDBC
>>>>> connections?
>>>>> So anyone here who can give some hints?
>>>>>
>>>>> SYBASE 15.0.2 / 15.0.3
>>>>>
>>>>> Regards,
>>>>> Heinz
>>>>>
>>> Mark,
>>>
>>> it's the first time that I have to deal with JDBC. I have taken a 
>>> look in
>>>
>>> http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15.0.java/html/java/java32.htm 
>>>
>>>
>>>
>>> It's not so easy to understand because I'm not familiar with JAVA.
>>>
>>> So what I mean with "log/monitor" is if a connection to the
>>> ASE is made by a JDBC connection I would be able to monitor that (only
>>> the information: clientname, ip address, username, date or something
>>> like that).
>>>
>>> At the moment I don't know if there are any JDBC connections from any
>>> clients/applications.
>>>
>>> BTW:
>>> I've read in the above mentioned documentation that if Java isn't
>>> enabled ( sp_configure "enable java", 0 ) no JDBC connection is
>>> possible. Is that correct?
>>>
>>> Heinz
>>>
>>>
>>>
>>
> Rob,
> 
> "In 15.5. ESD#1, there's a feature that lets you determine whether a
> connection is a JDBC connection, but it only writes that information to
> the ASE errorlog file so it won't help you for your purpose."
> 
> That would be exactly what I need. I don't need any tracing of that JDBC 
> process, I only need the information that someone has _established_ a 
> JDBC connection ( and perhaps some info like ip address and loginname).
> 
> Ok, I'll have to wait until we migrate to 15.5.
> 
> Heinz
> 
0
Mark
1/15/2011 2:55:56 PM
That's a good point, actually. One such a proc could be sp_mda.

Rob V.


On 15-Jan-2011 15:55, Mark A. Parsons wrote:
> So if your JDBC applications are calling any of the jconnect stored 
> procs, said jconnect proc(s) could be modified (via a call to a custom 
> proc) to dump the desired connectivity info (from sysprocesses or 
> monProcessLookup) into a audit/history table.
>
> Heinz M�ller wrote:
>> Am 15.01.2011 13:30, schrieb Rob V [ Sybase ]:
>>> First, the 'enable java' parameter in ASE has nothign to do with JDBC
>>> connections. 'enable java' allows you to use Java classes inside ASE
>>> itself, as procedures, functions or datatypes.
>>> JDBC connections are TDS connections made by some client application
>>> that uses the JDBC interface (and jConnect as JDBC driver); the
>>> connection that comes into ASE is, largely, identical to a conneciton
>>> made by , for example, isql.
>>>
>>> With that out of the way, it depends what you mean with "log or monitor
>>> JDBC conenctions". The first thing to do is to find out if a connection
>>> is a JDBC connection. Unfortunately, you cannot determine this by
>>> looking at sysprocesses: a JDBC connection looks just the same as any
>>> other one. Only when you know that the connection's hostname or IP
>>> address or program_name has a specific value that indicates 
>>> (indirectly)
>>> that it is a JDBC connection, can you specifically test for it.
>>> Assuming you can do this, you can then enable application tracing for
>>> that specific connection when it connects to ASE by means of a login
>>> trigger; see www.sypron.nl/quiz2009a.html#jun09 for details.
>>>
>>> In 15.5. ESD#1, there's a feature that lets you determine whether a
>>> connection is a JDBC connection, but it only writes that information to
>>> the ASE errorlog file so it won't help you for your purpose. See my
>>> Techwave 2010 presentation at www.sypron.nl/downloads for details.
>>>
>>> HTH,
>>>
>>> Rob V.
>>> -----------------------------------------------------------------
>>> Rob Verschoor
>>>
>>> Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
>>> and Replication Server 15.0.1/12.5 // TeamSybase
>>>
>>> Author of Sybase books (order online at www.sypron.nl/shop):
>>> "Tips, Tricks& Recipes for Sybase ASE" (ASE 15 edition)
>>> "The Complete Sybase ASE Quick Reference Guide"
>>> "The Complete Sybase Replication Server Quick Reference Guide"
>>>
>>> rob@NO.SPAM.sypron.nl | www.sypron.nl | Twitter: @rob_verschoor
>>> Sypron B.V., The Netherlands | Chamber of Commerce 27138666
>>> -----------------------------------------------------------------
>>>
>>>
>>>
>>> On 14-Jan-2011 22:09, Heinz M�ller wrote:
>>>> Am 14.01.2011 21:30, schrieb Mark A. Parsons:
>>>>> No solutions, no recommendations, just some questions ...
>>>>>
>>>>> More details about what you mean by 'log/monitor'? MDA tables? 
>>>>> auditing?
>>>>> monserver/histserver? something else?
>>>>>
>>>>> Do you already have a way to tell which connections are using 
>>>>> JDBC? or
>>>>> is this also something you're looking for?
>>>>>
>>>>>
>>>>> Heinz M�ller wrote:
>>>>>> Hi,
>>>>>>
>>>>>> today I was asked if it's possible to log/monitor only JDBC
>>>>>> connections?
>>>>>> So anyone here who can give some hints?
>>>>>>
>>>>>> SYBASE 15.0.2 / 15.0.3
>>>>>>
>>>>>> Regards,
>>>>>> Heinz
>>>>>>
>>>> Mark,
>>>>
>>>> it's the first time that I have to deal with JDBC. I have taken a 
>>>> look in
>>>>
>>>> http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15.0.java/html/java/java32.htm 
>>>>
>>>>
>>>>
>>>> It's not so easy to understand because I'm not familiar with JAVA.
>>>>
>>>> So what I mean with "log/monitor" is if a connection to the
>>>> ASE is made by a JDBC connection I would be able to monitor that (only
>>>> the information: clientname, ip address, username, date or something
>>>> like that).
>>>>
>>>> At the moment I don't know if there are any JDBC connections from any
>>>> clients/applications.
>>>>
>>>> BTW:
>>>> I've read in the above mentioned documentation that if Java isn't
>>>> enabled ( sp_configure "enable java", 0 ) no JDBC connection is
>>>> possible. Is that correct?
>>>>
>>>> Heinz
>>>>
>>>>
>>>>
>>>
>> Rob,
>>
>> "In 15.5. ESD#1, there's a feature that lets you determine whether a
>> connection is a JDBC connection, but it only writes that information to
>> the ASE errorlog file so it won't help you for your purpose."
>>
>> That would be exactly what I need. I don't need any tracing of that 
>> JDBC process, I only need the information that someone has 
>> _established_ a JDBC connection ( and perhaps some info like ip 
>> address and loginname).
>>
>> Ok, I'll have to wait until we migrate to 15.5.
>>
>> Heinz
>>


-- 
Dear Sybase user,

I am currently unable to respond to the specific question(s) which you have sent me. Due to the ever increasing number of questions I am receiving, I currently simply don't have the time to answer detailed individual questions.
Please post your question to one of the ASE-related newsgroups so that the ASE community can participate/benefit.
These newsgoups are comp.databases.sybase (Usenet), as well as various newsgroups on Sybase's own news server (forums.sybase.com).
Also, please provide sufficient technical details (error messages, actual queries, query plans, etc.) about your problem.
Try the Sybase FAQ at http://www.isug.com/Sybase_FAQ/, which contains answers to many questions about ASE.

Kind regards,

Rob Verschoor

If you don't want to use X Windows, you could try "sybinit4ever", a free tool which uses only an ASCII interface to create a new ASE server. It can be downloaded from http://www.sypron.nl/si4evr.html

See the
ASE reference manual / System Administration Guide / Transact-SQL user's guide
This / These books can be viewed or downloaded as PDF files from the Sybase website http://www.sybase.com/support/manuals/ . For more details how to get there, see http://www.sypron.nl/sybbooks.html .

For more information on the background of this problem, as well as a solution, see http://www.sypron.nl/idgaps.html .

.... syntax and description are in the ASE Quick Reference Supplement, which you can download from http://www.sypron.nl/ase_qref.html (for a better version, see my book -- www.sypron.nl/qr).


To use dynamic SQL, you need at least ASE version 12.0, which has the "execute immediate" feature for this. In earlier versions of ASE you can simulate some types of dynamic SQL though; for more information, see http://www.sypron.nl/dynsql.html and http://www.sypron.nl/dynsqlcis.html .

For more information about Sybase Certification Exams, see http://www.sypron.nl/certtips.html .

The ASE Performance and Tuning Guide contains a lot fo info about this topic. You can download this manual from http://sybooks.sybase.com/as.html .

HTH,

Rob V.
-----------------------------------------------------------------
Rob Verschoor

Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
and Replication Server 15.0.1/12.5 // TeamSybase

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks&  Recipes for Sybase ASE" (ASE 15 edition)
"The Complete Sybase ASE Quick Reference Guide"
"The Complete Sybase Replication Server Quick Reference Guide"

rob@NO.SPAM.sypron.nl | www.sypron.nl  | Twitter: @rob_verschoor
Sypron B.V., The Netherlands  |  Chamber of Commerce 27138666
-----------------------------------------------------------------

0
Rob
1/15/2011 4:28:53 PM
Reply: