no support for jConnect

[Jim R.]

I installed vanilla versions of ASE 15.0.2 and OSw 15.1. I setup two ASE
servers and one OSW server. I tested connectivity to the databases via ISQL
and got errors indicating no jConnect support. I ran
jConnect-6_0\sp\sql)server15_0.sql on the ASE servers to install JDBC
support. Now when I connect to the ASE servers using ISQL it functions as
expected. However, when I connect via ISQL to my OSw server I get the
jConnect support error:

"The database does not have jConnect support installed
Some functionality in ISQL will not be available"

What do I need to do to resolve that error?

thanks
Jim

[SybaseNeal]

Hello,

Are you using DBISQL, JISQL or ISQL? Because ISQL is not a jConnect
application and it does not call any of the stored procedures that
jConnect applications are required to call to get meta-data. So it
makes no sense that it would get that error.

If you are using plain old vanilla ISQL, I would need you to
enable some debug flags in OpenSwitch and post the results
here. I have been using OpenSwitch for 7 years and haven't
seen that error.

In your OpenSwitch.cfg file, enable the following DEBUG flags:
DEBUG=efhlnquvC

Then reproduce the problem and post the OpenSwitch log file here.

Thanks,
Neal

[SybaseNeal]

Hello,

Something is wrong as there should be much, much more in the
log.
Perhaps you have two DEBUG lines in your config file?

For example, DEBUG=l should have shown us the text of the
LANGUAGE and/or RPC commands the client was sending through
OpenSwitch. Yet, I only see the event handlers being
called.

And the fact that there are so many RPCs being called leads
me to believe that you were using JISQL or DBISQL. ISQL by
itself does not call any RPCs.

Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_attn:
SRV_CONNECT
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_lang:
ENTER: SRV_LANGUAGE
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_lang:
ENTER: SRV_LANGUAGE
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_lang:
ENTER: SRV_LANGUAGE
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC
Feb 29 13:31:33 2008: OSW_Test: DEBUG: spid 12: event_rpc:
SRV_RPC

[SybaseNeal]

AHhhh! That explains two things. DBISQL is probably not connecting
to the server you think it is if you have standby addressing in your
sql.ini file.

Even if you are not using standby addressing in OpenSwitch, you may
not be connecting to the OpenSwitch. I used your config file and
saw all of the expected logging. Clients must connect directly to
OpenSwitch, and then OpenSwitch will establish an outgoing connection
to ASE.

So it explains two things:
1) DBISQL is a jConnect/Java based application so it does require
that special stored procedures be installed on ASE. This would
explain why you get the "database does not have jConnect support".

2) There is a bug in DBISQL such that if you have standby addressing
in your interfaces or sql.ini file like this:

[NSTACKXP_OSWITCH]
master=TCP,NSTACKXP,7000
query=TCP,NSTACKXP,7000
master=TCP,NSTACKXP,7020
query=TCP,NSTACKXP,7020

DBISQL will connect to the last entry it finds. In your original post,
you only described setting up a single instance of OpenSwitch. Using
standby addressing is common when configuring two OpenSwitch instances
for a Mutual Aware OpenSwitch installation.

So we have a bug open for this but it has a low priority. If you are
running into it, please log a case and have this CR attached to it so
it gets a higher priority in engineering:
456094 - DBISQL connects to wrong host in interfaces file when using standby addressing

You might try opening a DOS Command prompt and test with the character
based ISQL so as to avoid these two issues with DBISQL. Once you are
able to log in and issue a "select @@servername" and you can confirm
which server you connected to. Then go back and look at the OpenSwitch
log file and see if it logged what we expected.

Thanks,
Neal

[katurian]

Did you try:

ALTER DATABASE UPGRADE JCONNECT ON

see: ASA SQL Reference - ALTER DATABASE statement