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.

Metadata accessor information was not found on this database..

5 posts in JDBC Connect (product renamed to JConnect) Last posting was on 1997-07-30 21:38:44.0Z
Adam Jack Posted on 1997-06-02 18:06:14.0Z
Message-ID: <33930B96.A82037AF@neonsoft.com>
Date: Mon, 02 Jun 1997 12:06:14 -0600
From: Adam Jack <ajack@neonsoft.com>
Organization: NEON, Inc.
X-Mailer: Mozilla 4.0b4 [en] (WinNT; I)
MIME-Version: 1.0
Subject: Metadata accessor information was not found on this database..
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Newsgroups: sybase.public.jdbcconnect
Lines: 22
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:744
Article PK: 252497

Any clues on this?

SQL Warnings...
1] SQLState : 010SJ
1] Message : Metadata accessor information was not found on this
database: Me
tadata accessor information was not found on this database
1] VendorCode : 0
java.sql.SQLException: Metadata accessor information was not found on
this datab
ase: Metadata accessor information was not found on this database
at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
at
com.sybase.jdbc.SybDatabaseMetaData.getMetaDataAccessor(SybDatabaseMe
taData.java)
at
com.sybase.jdbc.SybDatabaseMetaData.getMetaDataAccessor(SybDatabaseMe
taData.java)
at com.sybase.tds.Tds.setOption(Unknown Source)
at
com.sybase.jdbc.SybConnection.setAutoCommit(SybConnection.java)

Many thanks,

Adam


Lance Andersen Posted on 1997-06-02 20:35:53.0Z
Message-ID: <33932EA9.682A@sybase.com>
Date: Mon, 02 Jun 1997 16:35:53 -0400
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.5.1 sun4m)
MIME-Version: 1.0
To: Adam Jack <ajack@neonsoft.com>
Subject: Re: Metadata accessor information was not found on this database..
References: <33930B96.A82037AF@neonsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 40
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:739
Article PK: 252491

Hi Adam,

What you need to do is run either

$JDBC_HOME/sp/sql_server.sql

or

$JDBC_HOME/sp/sql_anywhere.sql

This installs the scripts required to obtain the metdata info.

-Lance

Adam Jack wrote:
>
> Any clues on this?
>
> SQL Warnings...
> 1] SQLState : 010SJ
> 1] Message : Metadata accessor information was not found on this
> database: Me
> tadata accessor information was not found on this database
> 1] VendorCode : 0
> java.sql.SQLException: Metadata accessor information was not found on
> this datab
> ase: Metadata accessor information was not found on this database
> at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
> at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
> at
> com.sybase.jdbc.SybDatabaseMetaData.getMetaDataAccessor(SybDatabaseMe
> taData.java)
> at
> com.sybase.jdbc.SybDatabaseMetaData.getMetaDataAccessor(SybDatabaseMe
> taData.java)
> at com.sybase.tds.Tds.setOption(Unknown Source)
> at
> com.sybase.jdbc.SybConnection.setAutoCommit(SybConnection.java)
>
> Many thanks,
>
> Adam

--
===============================================================================
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!!!
===============================================================================


Dirk Fromhein Posted on 1997-06-03 14:46:15.0Z
Message-ID: <33942E37.3FE3@watershed.com>
Date: Tue, 03 Jun 1997 10:46:15 -0400
From: Dirk Fromhein <Dirk.Fromhein@watershed.com>
Organization: Watershed Technologies, Inc.
X-Mailer: Mozilla 3.01Gold (X11; U; SunOS 5.5.1 sun4m)
MIME-Version: 1.0
To: Lance Andersen <lancea@sybase.com>
Subject: Re: Metadata accessor information was not found on this database..
References: <33930B96.A82037AF@neonsoft.com> <33932EA9.682A@sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 26
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:733
Article PK: 252484

>java.sql.SQLException: Metadata accessor information was not found on >this database: Metadata accessor information was not found on this >database

I ran the script and I still get the error.

BTW: I think the requirement for loading these stored procedures is a
poor idea, it makes for a version/maintenance nightmare. I can just
imagine going to demo one of our products on a customers database... us:
oh you have version xxx installed of the metadata scripts, you need
version xxx+n to run our product... customer: to run the demo we need to
run a script that changes stuff in our database that we might rely on
for other applications? Yeah right... the door is right over there.

In many cases the people we are going to work with probably don't even
have permission to run a ddl.

The logic belongs in the driver not in the database, if you have to
create two drivers one for Sybase 11 and one for SQL Anywhere.

Thanks,
Dirk Fromhein
df@watershed.com
http://www.watershed.com


David Clegg Posted on 1997-07-30 21:38:44.0Z
Message-ID: <33DFB464.1057E13E@sybase.com>
Date: Wed, 30 Jul 1997 14:38:44 -0700
From: David Clegg <davec@sybase.com>
X-Mailer: Mozilla 3.01 (X11; I; Linux 1.2.13 i586)
MIME-Version: 1.0
To: Dirk Fromhein <Dirk.Fromhein@watershed.com>
Subject: Re: Metadata accessor information was not found on this database..
References: <33930B96.A82037AF@neonsoft.com> <33932EA9.682A@sybase.com> <33942E37.3FE3@watershed.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 76
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:432
Article PK: 252184


Dirk Fromhein wrote:
>
> >java.sql.SQLException: Metadata accessor information was not found on >this database: Metadata accessor information was not found on this >database
>
> I ran the script and I still get the error.
>
> BTW: I think the requirement for loading these stored procedures is a
> poor idea, it makes for a version/maintenance nightmare. I can just
> imagine going to demo one of our products on a customers database...

I don't think anyone is really thrilled with having to install this
stuff on the database, but I think that that is really where it
belongs. Not only do different databases need different queries
to access the same information, but different versions of the same
general product may be different (4.9 servers are VERY different
from 10.0 servers, which are somewhat different from 11.0 servers,
which will likely be different from 12.x servers). Also, the queries
that we run for some of the metadata are quite complex -- they really
need to be stored-procedures on the server so that it doesn't have
to keep parsing and optimizing them -- and you certainly don't want
every JDBC client installing a battery of temporary stprocs for these
purposes.

Most ODBC drivers use exactly this same technique for accessing
MetaData -- there are a bunch of stored procedures on each SQL Server
that ODBC drivers use. They are installed as a normal part of setting
up a database server.

We are planning to provide the setup scripts to the SQL Server and
SQL Anywhere product groups for inclusing with their products for
future releases. For the time being... sorry.

> us:
> oh you have version xxx installed of the metadata scripts, you need
> version xxx+n to run our product... customer: to run the demo we need to
> run a script that changes stuff in our database that we might rely on
> for other applications? Yeah right... the door is right over there.

There is 1 stored procedure (sp_mda) which bootstraps jConnect's
access to metadata. That stored procedure takes a "version" parameter,
so if we ever have to make changes to the Metadata stuff that aren't
completely upward compatible, we can without breaking older existing
applications.

>
> In many cases the people we are going to work with probably don't even
> have permission to run a ddl.
>
> The logic belongs in the driver not in the database, if you have to
> create two drivers one for Sybase 11 and one for SQL Anywhere.
Under that model, we'd also have to have drivers for Jaguar and
RepServer and OmniConnect and directConnect and ... every OpenServer
based gateway...

We did consider this approach but rejected it - the maintenance issues
are intractable, and the size of the class files that would have to
be downloaded every time would get enormous.

Hopefully future experiences in this area will be better for you
as more and more of our server and middle-ware products come pre-
configured with jConnect support.

dave


Lance Andersen Posted on 1997-06-03 15:06:51.0Z
Message-ID: <3394330B.48D6@sybase.com>
Date: Tue, 03 Jun 1997 11:06:51 -0400
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.5.1 sun4m)
MIME-Version: 1.0
To: Dirk Fromhein <Dirk.Fromhein@watershed.com>
Subject: Re: Metadata accessor information was not found on this database..
References: <33930B96.A82037AF@neonsoft.com> <33932EA9.682A@sybase.com> <33942E37.3FE3@watershed.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:731
Article PK: 252483

Dirk,


Enclosed is the answer from engineering which was posted earlier
within the newsgroup regarding the sql_anywhere/server.sql need.


as far as the SQL Exception that was thrown,


1. Please make sure that the correct script was run

(sql_server.sql for sql server and sql_anywhere.sql for the db
in sql_anywhere).


2. Make sure the script was for the version of jConnect that you
have installed (in case you had multiple directories).


3. If you still have a problem, enable the debugging so we can
see exactly where you died:

http://www/products/internet/jconnect/docs/prjdbc_4.htm#HEADING4-179


-lance
---------------------------------------
This IS our long-term design. The problem with hardcoding queries
to pass in at run-time is that jConnect doesn't know what kind of
server it will be connected to beforehand (SqlServer 10.0, 11.0, ...,
SQL Anywhere 5.5, Jaguar CTS, Omni-->DB2, DirectConnect-->Oracle, etc.).

The approach using sp_mda to dynamically find out how to access
metadata from a server will be easier to maintain and can be
customized by the various servers without requiring synchronized
changes in jConnect.

> I notice that you need to have stored procedures loaded on any Sybase
> database inorder to get jConnect metadata classes to work.
>
> Is this a long term solution to the JDBC metadata interfaces for
> jConnect? This seems like an unnecessary implementation - couldn't this
> be done by passing query strings at run-time? It also adds a
> configuration burden to any Sybase database that you want to use
> meta-data + JDBC + jConnect on?

We are working with our Systems Management group to make this
configuration burden lighter by providing tools for this in the
next release.

>
> If the answer about this being a long-term solution is yes, could you
> explain why this approach was taken? Can you also verify that this is a
> jdbc-compliant solution?

The JDBC standard is silent on database configuration issues.

>
> JDBC's meta-data are a great idea - I am concerned that the jConnect
> implementation lessens the usefulness of these interfaces.
>
> Thanks!
>
> Ted
>
> P.S. I hope my posting here is not a re-hash of old postings, I didn't
> see any in this vein...




Dirk Fromhein wrote:
>
> >java.sql.SQLException: Metadata accessor information was not found on >this database: Metadata accessor information was not found on this >database
>
> I ran the script and I still get the error.
>
> BTW: I think the requirement for loading these stored procedures is a
> poor idea, it makes for a version/maintenance nightmare. I can just
> imagine going to demo one of our products on a customers database... us:
> oh you have version xxx installed of the metadata scripts, you need
> version xxx+n to run our product... customer: to run the demo we need to
> run a script that changes stuff in our database that we might rely on
> for other applications? Yeah right... the door is right over there.
>
> In many cases the people we are going to work with probably don't even
> have permission to run a ddl.
>
> The logic belongs in the driver not in the database, if you have to
> create two drivers one for Sybase 11 and one for SQL Anywhere.
>
> Thanks,
> Dirk Fromhein
> df@watershed.com
> http://www.watershed.com

--
===============================================================================
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!!!
===============================================================================