Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

jConnect 3.0-Beta JDBC Drivers and MetaData Access

3 posts in JDBC Connect (product renamed to JConnect) Last posting was on 1997-10-15 01:02:46.0Z
Ben Cotton Posted on 1997-10-04 19:20:46.0Z
Message-ID: <3436970E.31E9889E@bear.com>
Date: Sat, 04 Oct 1997 15:20:46 -0400
From: Ben Cotton <bcotton@bear.com>
Organization: Bear Stearns & Co.
X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 5.6 sun4m)
MIME-Version: 1.0
CC: jziner@bear.com, jolly@weblogic.com, pambrose@weblogic.com, rbp@weblogic.com, bcotton@gti.net, davec@sybase.com, akogon@ix.netcom.com, gpops@warlock.bear.com
Subject: jConnect 3.0-Beta JDBC Drivers and MetaData Access
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 74
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:191
Article PK: 251943

Hi David et. al. @sybase.public.jdbcconnect,

Can anyone explain what this SQLException is grumbling about?
I am using jConnect 3.0-beta JDBC driver.


java.sql.SQLException: JZ0SJ: Metadata accessor information was not found on this database.
at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
at com.sybase.jdbc.MdaManager.loadMetaData(MdaManager.java)
at com.sybase.jdbc.MdaManager.<init>(MdaManager.java)
at com.sybase.jdbc.SybConnection.getMDA(SybConnection.java)
at com.sybase.tds.RowFormatToken.getColumnTypeName(RowFormatToken.java)
at weblogic.db.jdbc.Column.setup(Column.java:43)
at weblogic.db.jdbc.Schema.setup(Schema.java:36)
at weblogic.db.jdbc.QueryDataSet.resultSet(QueryDataSet.java:161)
at weblogic.db.jdbc.QueryDataSet.<init>(QueryDataSet.java:113)
at bear.global_price.weblogicTESTS.T3PolyMgrImpl.connectJDBC(T3PolyMgrImpl.java:98)
at bear.global_price.weblogicTESTS.T3PolyMgrImpl_Skel.execute(T3PolyMgrImpl_Skel.java:26)
at weblogic.rmi.t3client.internal.RMIRequestProxy.execute(RMIRequestProxy.java:212)
at weblogic.t3.srvr.ExecuteThread.invokeExecutable(ExecuteThread.java:131)
at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:246)

When I use the jConnect 2.1 driver, whose release notes confess to not being
fully compliant with the JavaSoft JDBC spec, I get this notification:


java.sql.SQLException: This class method has not been completed and should not be called. : getColumnTypeName
at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
at com.sybase.tds.RowFormatToken.getColumnTypeName(Unknown Source)
at weblogic.db.jdbc.Column.setup(Column.java:43)
at weblogic.db.jdbc.Schema.setup(Schema.java:36)
at weblogic.db.jdbc.QueryDataSet.resultSet(QueryDataSet.java:161)
at weblogic.db.jdbc.QueryDataSet.<init>(QueryDataSet.java:113)
at bear.global_price.weblogicTESTS.T3PolyMgrImpl.connectJDBC(T3PolyMgrImpl.java:97)
at bear.global_price.weblogicTESTS.T3PolyMgrImpl_Skel.execute(T3PolyMgrImpl_Skel.java:26)
at weblogic.rmi.t3client.internal.RMIRequestProxy.execute(RMIRequestProxy.java:212)
at weblogic.t3.srvr.ExecuteThread.invokeExecutable(ExecuteThread.java:131)
at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:246)

So, apparently, some effort has been made at Sybase bringing the jConnect 3.0-Beta version
of com.sybase.tds.RowFormatToken.getColumnTypeName() into compliance w/ the latest JDBC spec.
However, that first stack trace's message leads me to believe that this effort may not be complete.
True? Is there something I can do to pacify this exception, enabling the
MdaManager.loadMetaData() method to see the accessor information? What does 'JZOSJ' mean?
Any comments appreciated.

-Ben


Lance Andersen Posted on 1997-10-06 12:20:27.0Z
Message-ID: <3438D78B.1E42@sybase.com>
Date: Mon, 06 Oct 1997 08:20:27 -0400
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.5.1 sun4m)
MIME-Version: 1.0
To: Ben Cotton <bcotton@bear.com>
Subject: Re: jConnect 3.0-Beta JDBC Drivers and MetaData Access
References: <3436970E.31E9889E@bear.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 96
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:190
Article PK: 251942

Ben,

Please make sure that you have run the sql_server.sql script
that came with 3.0

the stored procedure sp_sql_type_name must exist as well
as the row in spt_mda containing an mdinfo value of:
COLUMNTYPENAME


If you still have a problem, please provide a simple test case
that is failing as I do not have a problem here.

thanks!

Ben Cotton wrote:
>
> Hi David et. al. @sybase.public.jdbcconnect,
>
> Can anyone explain what this SQLException is grumbling about?
> I am using jConnect 3.0-beta JDBC driver.
>
> java.sql.SQLException: JZ0SJ: Metadata accessor information was not found on this database.
> at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
> at com.sybase.jdbc.MdaManager.loadMetaData(MdaManager.java)
> at com.sybase.jdbc.MdaManager.<init>(MdaManager.java)
> at com.sybase.jdbc.SybConnection.getMDA(SybConnection.java)
> at com.sybase.tds.RowFormatToken.getColumnTypeName(RowFormatToken.java)
> at weblogic.db.jdbc.Column.setup(Column.java:43)
> at weblogic.db.jdbc.Schema.setup(Schema.java:36)
> at weblogic.db.jdbc.QueryDataSet.resultSet(QueryDataSet.java:161)
> at weblogic.db.jdbc.QueryDataSet.<init>(QueryDataSet.java:113)
> at bear.global_price.weblogicTESTS.T3PolyMgrImpl.connectJDBC(T3PolyMgrImpl.java:98)
> at bear.global_price.weblogicTESTS.T3PolyMgrImpl_Skel.execute(T3PolyMgrImpl_Skel.java:26)
> at weblogic.rmi.t3client.internal.RMIRequestProxy.execute(RMIRequestProxy.java:212)
> at weblogic.t3.srvr.ExecuteThread.invokeExecutable(ExecuteThread.java:131)
> at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:246)
>
> When I use the jConnect 2.1 driver, whose release notes confess to not being
> fully compliant with the JavaSoft JDBC spec, I get this notification:
>
> java.sql.SQLException: This class method has not been completed and should not be called. : getColumnTypeName
> at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
> at com.sybase.tds.RowFormatToken.getColumnTypeName(Unknown Source)
> at weblogic.db.jdbc.Column.setup(Column.java:43)
> at weblogic.db.jdbc.Schema.setup(Schema.java:36)
> at weblogic.db.jdbc.QueryDataSet.resultSet(QueryDataSet.java:161)
> at weblogic.db.jdbc.QueryDataSet.<init>(QueryDataSet.java:113)
> at bear.global_price.weblogicTESTS.T3PolyMgrImpl.connectJDBC(T3PolyMgrImpl.java:97)
> at bear.global_price.weblogicTESTS.T3PolyMgrImpl_Skel.execute(T3PolyMgrImpl_Skel.java:26)
> at weblogic.rmi.t3client.internal.RMIRequestProxy.execute(RMIRequestProxy.java:212)
> at weblogic.t3.srvr.ExecuteThread.invokeExecutable(ExecuteThread.java:131)
> at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:246)
>
> So, apparently, some effort has been made at Sybase bringing the jConnect 3.0-Beta version
> of com.sybase.tds.RowFormatToken.getColumnTypeName() into compliance w/ the latest JDBC spec.
> However, that first stack trace's message leads me to believe that this effort may not be complete.
> True? Is there something I can do to pacify this exception, enabling the
> MdaManager.loadMetaData() method to see the accessor information? What does 'JZOSJ' mean?
> Any comments appreciated.
>
> -Ben

--
===============================================================================
Lance J. Andersen Email: lancea@sybase.com
Sybase Technical Support Phone:(617) 564-6336
77 South Bedford Street Fax: (617) 564-6148
Burlington, MA 01803

The Dark Knight Returns!!! Let's Go Penguins!!!
===============================================================================


Ben Cotton Posted on 1997-10-15 01:02:46.0Z
Message-ID: <34441636.6B27FB08@bear.com>
Date: Tue, 14 Oct 1997 21:02:46 -0400
From: Ben Cotton <bcotton@bear.com>
Organization: Bear Stearns & Co.
X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 5.6 sun4m)
MIME-Version: 1.0
To: Lance Andersen <lancea@sybase.com>
CC: bcotton@bear.com, jziner@bear.com, rusmith@li.net, pambrose@weblogic.com, rbp@weblogic.com, jolly@weblogic.com, ec@weblogic.com, akogon@ix.netcom.com, davec@sybase.com
Subject: Re: jConnect 3.0-Beta JDBC Drivers and MetaData Access
References: <3436970E.31E9889E@bear.com> <3438D78B.1E42@sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 140
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:161
Article PK: 251915

Hi Lance,

I have run the jConnect 3.0 sql_server.sql script as specified in the
Installation guide. Indeed, the sp_sql_type_name stored procedure
exists, as well as a row in master..spt_mda w/ "COLUMNTYPENAME" as the
mdinfo column value. That said, the implications of the following
exception suggest to me that jConnect 3.0-Beta still has at least a
small ways to go before being fully compliant w/ the latest JavaSoft
JDBC specification.


java.sql.SQLException: ZZ00A: This class method has not been completed
and should not be called. isSearchable
at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
at
com.sybase.tds.RowFormatToken.isSearchable(RowFormatToken.java)
at weblogic.db.jdbc.Column.setup(Column.java:51)
at weblogic.db.jdbc.Schema.setup(Schema.java:36)
at
weblogic.db.jdbc.QueryDataSet.resultSet(QueryDataSet.java:161)
at weblogic.db.jdbc.QueryDataSet.<init>(QueryDataSet.java:113)
at
bear.global_price.weblogicTESTS.T3PolyMgrImpl.connectJDBC(T3PolyMgrImpl.java:99)
at
bear.global_price.weblogicTESTS.T3PolyMgrImpl_Skel.execute(T3PolyMgrImpl_Skel.java:26)
at
weblogic.rmi.t3client.internal.RMIRequestProxy.execute(RMIRequestProxy.java:212)
at
weblogic.t3.srvr.ExecuteThread.invokeExecutable(ExecuteThread.java:131)
at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:246)

Do you guys anticipate implementing the
com.sybase.tds.RowFormatToken.isSearchable() method before jConnect-3.0
is released GA?

Thanks,

-Ben

Lance Andersen wrote:
>
> Ben,
>
> Please make sure that you have run the sql_server.sql script
> that came with 3.0
>
> the stored procedure sp_sql_type_name must exist as well
> as the row in spt_mda containing an mdinfo value of:
> COLUMNTYPENAME
>
> If you still have a problem, please provide a simple test case
> that is failing as I do not have a problem here.
>
> thanks!
>
> Ben Cotton wrote:
> >
> > Hi David et. al. @sybase.public.jdbcconnect,
> >
> > Can anyone explain what this SQLException is grumbling about?
> > I am using jConnect 3.0-beta JDBC driver.
> >
> > java.sql.SQLException: JZ0SJ: Metadata accessor information was not found on this database.
> > at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
> > at com.sybase.jdbc.MdaManager.loadMetaData(MdaManager.java)
> > at com.sybase.jdbc.MdaManager.<init>(MdaManager.java)
> > at com.sybase.jdbc.SybConnection.getMDA(SybConnection.java)
> > at com.sybase.tds.RowFormatToken.getColumnTypeName(RowFormatToken.java)
> > at weblogic.db.jdbc.Column.setup(Column.java:43)
> > at weblogic.db.jdbc.Schema.setup(Schema.java:36)
> > at weblogic.db.jdbc.QueryDataSet.resultSet(QueryDataSet.java:161)
> > at weblogic.db.jdbc.QueryDataSet.<init>(QueryDataSet.java:113)
> > at bear.global_price.weblogicTESTS.T3PolyMgrImpl.connectJDBC(T3PolyMgrImpl.java:98)
> > at bear.global_price.weblogicTESTS.T3PolyMgrImpl_Skel.execute(T3PolyMgrImpl_Skel.java:26)
> > at weblogic.rmi.t3client.internal.RMIRequestProxy.execute(RMIRequestProxy.java:212)
> > at weblogic.t3.srvr.ExecuteThread.invokeExecutable(ExecuteThread.java:131)
> > at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:246)
> >
> > When I use the jConnect 2.1 driver, whose release notes confess to not being
> > fully compliant with the JavaSoft JDBC spec, I get this notification:
> >
> > java.sql.SQLException: This class method has not been completed and should not be called. : getColumnTypeName
> > at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
> > at com.sybase.tds.RowFormatToken.getColumnTypeName(Unknown Source)
> > at weblogic.db.jdbc.Column.setup(Column.java:43)
> > at weblogic.db.jdbc.Schema.setup(Schema.java:36)
> > at weblogic.db.jdbc.QueryDataSet.resultSet(QueryDataSet.java:161)
> > at weblogic.db.jdbc.QueryDataSet.<init>(QueryDataSet.java:113)
> > at bear.global_price.weblogicTESTS.T3PolyMgrImpl.connectJDBC(T3PolyMgrImpl.java:97)
> > at bear.global_price.weblogicTESTS.T3PolyMgrImpl_Skel.execute(T3PolyMgrImpl_Skel.java:26)
> > at weblogic.rmi.t3client.internal.RMIRequestProxy.execute(RMIRequestProxy.java:212)
> > at weblogic.t3.srvr.ExecuteThread.invokeExecutable(ExecuteThread.java:131)
> > at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:246)
> >
> > So, apparently, some effort has been made at Sybase bringing the jConnect 3.0-Beta version
> > of com.sybase.tds.RowFormatToken.getColumnTypeName() into compliance w/ the latest JDBC spec.
> > However, that first stack trace's message leads me to believe that this effort may not be complete.
> > True? Is there something I can do to pacify this exception, enabling the
> > MdaManager.loadMetaData() method to see the accessor information? What does 'JZOSJ' mean?
> > Any comments appreciated.
> >
> > -Ben
>
> --
> ===============================================================================
> Lance J. Andersen Email: lancea@sybase.com
> Sybase Technical Support Phone:(617) 564-6336
> 77 South Bedford Street Fax: (617) 564-6148
> Burlington, MA 01803
>
> The Dark Knight Returns!!! Let's Go Penguins!!!
> ===============================================================================

--
-Ben