SS2K_SYSLOGINS ORA-01401 using WB for SQL server 2000

Hi there,
I've read some threads on this issue on this forum but no solution to be found.
I noticed that the NAME field on the table SS2K_SYSLOGINS has been declared as varchar2(30) and is reading the SYSLOGINS views column NAME ( as declared sysname 128 ) on SQL server 2000.
This view (based on tabel sysxtypes) is not only containing SQL-logins but also domain users and domain groups ( like "domainxxx.com\SL-DAFEHV-DB-TorqueSupervisor-Admin"
These domain name sometimes are far over 30 characters in length !!!
I download the Migration Workbench ( 10.1.0.4.0 ) and some pluging today ( from http://www.oracle.com/technology/software/tech/migration/workbench/index.html )and I'm running WB 10 and Ora 9.2 both on the same server.
How to solve this problem.
Please help me out.
Guus

Guus,
[It was a new bug, I searched the bug database but could not find something relevant]
We will migrate what we can automate, so if there is more we can automate in future send in the details. Can you send in the database as a testcase?
I had to alter the SS2K_SYSINDEXES as well and had to set the columns FIRST, ROOT, and FIRTSIAM to allow 'null' !!!That is not logged either, which surprises me.
There was an assessment tool to give you an idea of the complexity of the migration that was used internally.
>
Further more I encoutered some warning ( i will not list them all )
A) Within SQL server there are other pre-reserved words as within Oracle.I am not clear what you mean, is the parser failing on not handled reserved words like for example XML features?
B) It cannot handle hops to other databases within/on the same server ( almost the same as using other schema's within Oracle )Consolidation is one of the proposed features of the next release.
C) It cannot deal with the different authentication setup within SQL server 2000 ( databaselink.database.owner.objectname )Will note for future reference.
C2 ) Is it possible to capture related objects from different databases ( ora schema's ) when encoutering them during capture ( the master database has been queried during the capturing as well. . . ) ?You just choose which databases you want to capture the workbench does not work out what parts of database b are called by database a. It was hoped there would be better tools for reorganising schemas when you got to oracle i.e. it was hoped it was out of our scope.
D) It cannot handle;
temptablesTemptables in stored procedures are mapped to oracle temporary tables, whos structure is permanent but the data can be temporary: for example tied to the session. Unhandled temptables in particular situations are a bug.
system procedures like sp_executesql / xp_cmdshell / xp_smtp_send_mail / sp_oacreateWhile the functionality exists in oracle emulating xp_ and sp_ functions has not been done.
function such as NEWID()
user difined functionsI will note this for further reference.
calls to the filesystem ( checking / writing to / reading from / deleting files )While the functionality exists in oracle emulating these functions has not been done.
commandline call ( using xp_cmdshell )
owner prefixes ( schema call as used by Oracle )I think this is done, if it is not done in some places it is a bug.
N' parameter prefixes
and so on , and so on
Think I better skip trying "Migration Workbench" and look for an other way to handle a migration from SQL server 2000 to Oracle 92.We did provide a service to do this for a fee I am not sure if it is still going. Other tools did not seem substancially better than the workbench.
>
My next chalange is to migrate from Informix 7x to Oarcle 9.2 ( Hmmmmm )The workbench also does this, but it is not a single click automatic operation.
Please tell me [at turloch.otierney at oracle.com] if you find other products that are better. What they do better, oracle can do better next time.
It is probably not a good idea to post this information publically on this Oracle forum.
I apologise that your expectations were not met at this time.
Turloch
Message was edited by:
totierne

Similar Messages

Has anybody used the microsoft JDBC 2.0 driver for sql server 2000?

Hi,
Has anybody used the JDBC 2.0 driver for sql server 2000 downloadable from the
microsoft website?When I try using it with WL 6.1 sp1 it says it can't load the
driver.I try viewing the class file from the jar file using the jar utility it
gives an unknown Zip format error.Anybody has any solution for this ?If anybody
has managed to work with this microsoft driver i will be grateful if they provide
me with a solution.
Thanks
Thomas

Hello Thomas,
You may want to download the driver again and install it again.
heres a sample xml tag in the config.xml:
<JDBCConnectionPool
DriverName="com.microsoft.jdbc.sqlserver.SQLServerDriver"
InitialCapacity="3" MaxCapacity="12" Name="MSpool"
Password="{3DES}fUz1bxR0zDg=" Properties="user=uid"
Targets="myserver"
URL="jdbc:microsoft:sqlserver://mydbserver:1433"/>
ensure that you follow the instructions from Microsoft. For using 2000
driver you will need to have
Install_dir/lib/msbase.jar and Install_dir/lib/msutil.jar in addition to
Install_dir/lib/mssqlserver.jar in the CLASSPATH.
hth
sree
"Thomas" <[email protected]> wrote in message
news:3c91ec0e$[email protected]..
Hi,
Has anybody used the JDBC 2.0 driver for sql server 2000 downloadable from
the
microsoft website?When I try using it with WL 6.1 sp1 it says it can't load
the
driver.I try viewing the class file from the jar file using the jar utility
it
gives an unknown Zip format error.Anybody has any solution for this ?If
anybody
has managed to work with this microsoft driver i will be grateful if they
provide
me with a solution.
Thanks
Thomas

Using JSP & JDBC driver for SQL Server 2000 on Red Hat

I successfully have a .jsp app running on windows server 2000 using JDBC
driver for SQL Server 2000. Which I installed in order to the following
Red Hat:
http://msdn.microsoft.com/MSDN-FILES/027/001/779/install.htm
I moved the .jsp app over to the Red Hat 9 server running Tomcat, while
keeping the MS SQL 2000 on windows. The issue I have is setting up the
JDBC driver for SQL Server 2000 on the Red Hat server.
I created a folder called /usr/java/MSSQLdriver and unzipped the tar file with
the driver for SQL Server 2000. And ran the install.ksh script.
The /usr/java/MSSQLdriver/lib has the following files within it:
msbase.jar, msutil.jar, & mssqlserver.jar
I chmod 0777 each of the *.jar files.
I then went into /etc/profile.d/tomcat.sh and adding the following:
CLASSPATH=.;/opt/msSQLjdbc/lib/msbase.jar;/opt/msSQLjdbc/lib/msutil.jar;/opt/msSQLjdbc/lib/mssqlserver.jar
Each time I login and pull up the termial I get the following error:
bash: /opt/msSQLjdbc/lib/msbase.jar: cannot execute binary file
bash: /opt/msSQLjdbc/lib/msutil.jar: cannot execute binary file
bash: /opt/msSQLjdbc/lib/mssqlserver.jar: cannot execute binary file
And can't connnect to the database within the .jsp app.
Is there anyone out there using DBC driver for SQL Server 2000 on the Red Hat server?
Michael

Sorry, I needed to correct some information of where the drivers were installed.
I created a folder called /usr/java/MSSQLdriver/new and untar the Microsoft file with the driver for SQL Server 2000. I ran the install.ksh script "sh install.ksh"
installed the driver into the default directory "/opt/msSQLjdbc".
The /opt/msSQLjdbc/lib has the following files within it:
msbase.jar, msutil.jar, & mssqlserver.jar
Michael

How to load decimal values into a file using bcp in SQL Server 2000?

Hi everyone,
I'm trying to load data from a database table to a text file using bcp on SQL Server 2000. When I'm loading the decimal values, the values before the decimal are not being loaded into the file. How could I load the values before decimals?
Here are the DDLs and DMLs of what I'm trying to run:
CREATE TABLE [dbo].[Product_Sales](
[Year_of_Sale] [smallint] NOT NULL,
[Product_Type] [varchar](25) NOT NULL,
[Product_Group] [varchar](25) NOT NULL,
[Category_Type] [varchar](25) NOT NULL,
[Category_Group] [varchar](10) NOT NULL,
[Product_Count] [bigint] NOT NULL,
[Product_Amount] [decimal](19, 2) NOT NULL,
[Category_Count] [bigint] NOT NULL,
[Category_Amount] [decimal](19, 2) NOT NULL,
CONSTRAINT [PK_Product_Sales] PRIMARY KEY CLUSTERED
[Year_of_Sale] ASC,
[Product_Type] ASC,
[Product_Group] ASC,
[Category_Type] ASC,
[Category_Group] ASC
) ON [PRIMARY]
) ON [PRIMARY]
INSERT INTO [Yearly_Sales].[dbo].[Product_Sales]
VALUES(2010, 'Online', 'Web', 'Cameras', 'Electronics', 547, 0.00, 0, 0.00)
EXEC [master].[dbo].[xp_cmdshell] 'bcp "SELECT * FROM [Yearly_Sales].[dbo].[Product_Sales]" queryout D:\Yearly_Sales\Product_Sales.dat -c -T -S'
And the output I see in the file is:
2010 Online Web Cameras Electronics 547 .00 0 .00
The values before decimals are being truncated.
Thanks,
Bangaaram
Known is a DROP, Unknown is an OCEAN.

You can modify the decimal column(s) in the table to varchar type before export. But it does not look good.
alter table [dbo].[Product_Sales]
Alter column [Product_Amount] varchar(20)
alter table [dbo].[Product_Sales]
Alter column [Category_Amount] varchar(20)
Does that make any sense?
Known is a DROP, Unknown is an OCEAN.
Basically you modify the decimal column to a varchar type before you run the bcp command for export. You can modify your source table or you can modify them on the fly. It is just a workaround.
Modifying the source wouldn't be a good idea. Never do that if you can't get your desired output.
Known is a DROP, Unknown is an OCEAN.

How to establish a trusted connection with JDBC for SQL SERVER 2000

Hi!I am using jdk 1.4 and eclipse 3.3.
I create a servlet in eclipse with in-build tomcat.
When I run it ,it was working perfectlly has it was suppose to work.
In this servlet I connect to a sql 2000 database using jdbc-odbc bridge driver.
But when I tried to deploy the servlet on tomcat 5.5 manully on the same machine ,it gave me error saying
[Microsoft][SQLServer JDBC Driver][SQLServer]Login failed
for user 'sa'
I searched around some post and found that ok ,I need trusted connection
But I have 2 Questions
1). Why was in eclipse I was able to connect to the SQL server and why not in the servlet which I deployed manully on tomcat.
2). How do I create a trusted connection with JDBC for SQL server 2000
Thnaks for your help in advance.

Hi! duffymo ,QussayNajjar ,dvohra09 .
Thank for help.
The ideas are really great.
I am trying generate reports for my company.
When I used eclipse the code worked perfectly.
below is code which I used
out.println("Calling For Class Name<br>");
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
out.println("Calling For Class Name success Now calling database <br>");
1). jdbcConnection = DriverManager.getConnection("jdbc:odbc:SQLJasper");
2). jdbcConnection = DriverManager.getConnection("jdbc:odbc:Driver={SQL Server};Server=ServerName;Database=tempdb");
3). jdbcConnection = DriverManager.getConnection("jdbc:odbc:Driver={SQL Server};Server=ServerName;Database=tempdb","UID=UserName","Password=Password");
out.println("connecting to database success<br>");
I had tried to connect the database using this three way.
In 1st I tried using DSN name .
Next 2 self explainer for expert like you.
I used to 2nd variant to connect in eclipse and it worked fine.
I not an expert in java ,I just doing some research on jasperReport.
My best guest is that eclipse is using some library files of which I have no clue.
Thank's for your help,I appretiate it.
Once again thank a billion.
Sorry for the messy righting.

Thin driver for SQL server 2000

Hi,
Is there a thin driver for SQL server 2000?
If so where can i find it?
I searched the net but in vain.
thanx in advance
Partha

Did you try the search engine available at the java soft site
http://industry.java.sun.com/products/jdbc/drivers
I used this engine some time ago and found that the thin driver at http://www.inetsoftware.de was the best fit for our project.
hope this helps.
regards,
Abhishek.

JDBC driver for SQL Server 2000 with windows authentication

Does anyone know of a JDBC driver for SQL Server 2000 that supports Windows Authentication, that is that a username and password does not need to be supplied when connecting to the database.

You can use the JDBC-ODBC-Bridge.
ODBC provides windows-authentication.
Hope it helps.
Freddy

*****Error in Microsoft JDBC drivers for SQL Server 2000****

hi guys,
I am getting the following error in my application. The error seems to have thrown by Microsoft JDBC drivers for SQL Server 2000
The application tries to execute the the following query when the error is thorwn:
SELECT getDate(); // getDate is a function which returns currebt date time. The error is thrown occassionally. Other times the same query is executed correctly by the application.
Can any one help with this one.
The error is:
java.lang.NullPointerException
     at com.microsoft.jdbc.base.BaseImplStaticCursorResultSet.setupTempFiles(Unknown Source)
     at com.microsoft.jdbc.base.BaseImplStaticCursorResultSet.<init>(Unknown Source)
     at com.microsoft.jdbc.base.BaseStatement.chainInServiceImplResultSets(Unknown Source)
     at com.microsoft.jdbc.base.BaseStatement.getNextResultSet(Unknown Source)
     at com.microsoft.jdbc.base.BaseStatement.commonGetNextResultSet(Unknown Source)
     at com.microsoft.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
     at com.microsoft.jdbc.base.BaseStatement.executeQuery(Unknown Source)
     at com.sanderson.tallyman.util.TallymanDB.executeQuery(Unknown Source)
     at com.sanderson.tallyman.util.TallymanDB.getCurrentDate(Unknown Source)
     at com.sanderson.tallyman.operations.interfaces.RecordUpdateControl.updateRecord(Unknown Source)
     at com.sanderson.tallyman.operations.interfaces.DebtInterfaceControl.processUpdate(Unknown Source)
     at com.sanderson.tallyman.operations.interfaces.DebtInterfaceControl.processInterface(Unknown Source)
     at com.sanderson.tallyman.operations.interfaces.InterfaceHandler$ProcessRecord.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
rgds,

Hi,
Did you ever get an answer to this? I am also having this problem.

Are there any JDBC Drivers for SQL Server 2000?

Hello Everyone,
Any news on the JDBC drivers for SQL Server 2000? I know it is not
certified yet but is there a date when it will be.
Which versions of WLS will they work with? Any help is appreciated.
Sincerely,
--Luis

Hello Michael,
Any news on the JDBC drivers for SQL Server 2000? I know it is not
certified yet but is there a date when it will be.
Which versions of WLS will they work with? Any help is appreciated.
Sincerely,
--Luis
"Michael Girdley" <[email protected]> wrote in message
news:3a6549bb$[email protected]..
Not yet, but they will appear on the web site in about two weeks.
Thanks,
Michael
Michael Girdley, BEA Systems Inc
Learning WebLogic? Buy the book.
http://www.learnweblogic.com/
"Stefano Picozzi" <[email protected]> wrote in message
news:[email protected]..
Are there any JDBC Drivers for SQL Server 2000 for Weblogic Server.

Problem Using JSQL level 4 driver for SQL Server 2000

I am having problem , connecting to my Sql Server 2000 ( deployed on Windows 2000 Professional) using Microsoft JSQL level 4 Deriver .
I am doing it with following code,
Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
     Connection conn = DriverManager.getConnection
("jdbc:microsoft:sqlserver://192.168.0.232:1433;databaseName=DBNew;user=nakhter;Password=java;");
It gives me following Exception ,
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Login failed for user 'nakhter'. Reason: Not associated with a trusted SQL Server connection.
     at com.microsoft.jdbc.base.BaseExceptions.createException Unknown Source)
     at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
     at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
     at com.microsoft.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
     at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
     at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
     at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
     at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
     at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
     at java.sql.DriverManager.getConnection(DriverManager.java:517)
     at java.sql.DriverManager.getConnection(DriverManager.java:177)
I am usign my windows authentication usrname and password .
I has tried it with user "sa" but still same exception .
Could someone help me in this regard ?

You need to switch SQL server to just use SQL Server authentication or both. The problem is that it is looking for a Windows NT account for nakhter with the password java. We get this all the time on new SQL Server installs if you just take the defaults.

Problem using type 4 driver for SQL Server 2000

Hi..
I'm getting the following error message when i attempt to connect to SQL Server 2000:
"Cannot open user default database. Using master database instead"
I am passing the proper connection url and the user name and the password.However,my application does not connect to the SQL Server.I have tried using JTurbo and Weblogic drivers.
All tables in this database have been imported using DTS and hence have "dbo" as their owner.I do not have administrator privileges on the db server.
Is there a workaround to this problem by changing some settings for ownership of the db objects?
I have already tried using :
EXEC sp_changedbowner <username>
for databases where I am not a user and it still doesn't work for these as well.
Thanks,
Jay.

It might be in your DSN. Give that a check, it could be that the DSN has a default db selected and also a userID/Pwd that's incorrect for that db. Just thinking out loud.
B

JDBC connection for SQL Server 2000

How to connect SQL Server 2000 from java?
If i can get any sites where i can get examples also fine.
Thanks in advance
Praveen.

Developer's Daily Java Education
front page | java | perl | unix | DevDirectory
Front Page
Java
Education
Pure Java
   Articles
JDBC 101: How to connect to an SQL database with JDBC
Introduction
If you're interested in connecting your Java applets and applications to standard SQL databases like Oracle, Informix, Sybase, and others, JDBC is your ticket to paradise. The combination of Java's JDBC and standard SQL makes a simple and powerful database solution. JDBC makes the simple things easy -- without making the complex tasks too difficult either.
In this first article in our series, we'll show you step-by-step how to establish a connection from your Java programs to an SQL database using JDBC. In the process we'll show you how to connect to two different databases -- Mini SQL (mSQL), and Interbase -- just so you can see how the code changes when you switch from one database to another.
Obtaining the JDBC driver
Before you start working with JDBC, you'll need a copy of the Java JDK. If you don't have it already, you can get the JDK for free at Sun's Java web site, or it will also be included with many IDE's that you can purchase, such as JBuilder or Visual Cafe.
Once you have the JDK, the next thing you need to do is to get the correct JDBC driver for your database. In most cases the JDBC driver will be provided by your database vendor. For instance, if you purchase the Interbase database, the driver will be provided with the software, or you can obtain the most recent version at http://www.interbase.com/.
(An exception to this rule is Mini SQL, or mSQL. Because it's a very low-cost database, the JDBC driver has actually been developed by a separate group of people, led by George Reese at imaginary.com. You can download the mSQL JDBC driver from the imaginary.com web site.)
Once you have the correct JDBC driver for your database, install it according to the instructions that came with it. Installation instructions will vary somewhat for each vendor.
Establishing a connection is a two-step process
Once you have the correct JDBC driver installed, establishing a connection from your Java programs to your SQL database is pretty easy.
Regardless of whether you're trying to connect to Oracle, Sybase, Informix, mSQL, or Interbase (or any other JDBC data source), establishing a connection to an SQL database with Java JDBC is a simple two-step process:
Load the JDBC driver.
Establish the connection.
We'll show you two examples just so you can see how easy it is, and how little the code changes when you migrate from one database server to another.
A Mini SQL Example
Listing 1 provides the full source code required to establish a connection to a mSQL database on a server named "www.myserver.com".
// Establish a connection to a mSQL database using JDBC.
import java.sql.*;
class JdbcTest1 {
    public static void main (String[] args) {
        try {
            // Step 1: Load the JDBC driver.
            Class.forName("com.imaginary.sql.msql.MsqlDriver");
            // Step 2: Establish the connection to the database.
            String url = "jdbc:msql://www.myserver.com:1114/contact_mgr";
            Connection conn = DriverManager.getConnection(url,"user1","password");
        } catch (Exception e) {
            System.err.println("Got an exception! ");
            System.err.println(e.getMessage());
Listing 1: This source code example shows the two steps required to establish a connection to a Mini SQL (mSQL) database using JDBC.
An Interbase Example
Listing 2 provides the full source code required to establish a connection to an Interbase database. In this example, we're connecting to a local Interbase server (i.e., the server is running on the same PC that we're running the Java code on).
// Establish a connection to an Interbase database using JDBC.
import java.sql.*;
class JdbcTest1 {
    public static void main (String[] args) {
        try {
            // Step 1: Load the JDBC driver.
            Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
            // Step 2: Establish the connection to the database.
            String url = "jdbc:odbc:contact_mgr";
            Connection conn = DriverManager.getConnection(url,"user1","password");
        } catch (Exception e) {
            System.err.println("Got an exception! ");
            System.err.println(e.getMessage());
Listing 2: This source code example shows the two steps required to establish a connection to an Interbase database using JDBC.
What's the difference?
The difference between the two source code listings is very small, so we highlighted them in a dark blue color. The only difference between connecting to the two databases is:
The name of the JDBC driver.
The URL used to connect to the database.
Everything else in the two source code listings -- except for the comment at the top -- is identical. Here's a slightly more detailed discussion of the two differences:
1. The JDBC Driver
The name of the JDBC driver will be supplied to you by your database vendor. As you can see in the class.forName() statements, these names will vary. In the first case we're using the mSQL-JDBC driver. In the second case we're using the JDBC-ODBC Bridge driver supplied with the Interbase server.
2. The URL
The syntax of the DriverManager.getConnection() method is:
DriverManager.getConnection(String url, String username, String password);
The username and password are the normal names you use to log into your database. The URL you use will again vary with the database you use. In both examples shown, we're establishing a connection to a database named contact_mgr. (We'll use this database for all of our examples in this series of JDBC articles.)
If you stick with standard SQL commands, it can be very easy to switch from one database server to another. In fact, I've heard from several developers who are using mSQL to prototype their software (because it's so inexpensive), and then switching to another commercial vendor when it's time to take their product "live".
Conclusion
Establishing a connection to an SQL database with Java JDBC is a simple, two-step process. The process is nearly identical for all SQL databases, and the only real differences are (a) the driver name, and (b) the URL used to connect to the database. Your database vendor will provide this information in their documentation.
Resources mentioned in this article
Here are a few links to resources we mentioned in this article:
Interbase
The Mini SQL (mSQL) database
The mSQL-JDBC driver at imaginary.com
[an error occurred while processing this directive]

Question about load Microsoft JDBC driver for Sql server 2000

Hello,
I have some problem while trying load the sqlserver2000 jdbc driver
My program is a third party application and it works with the other type 4 JDBC driver well. So I tried to use Microsoft SQL server 2000 JDBC driver instead.
I installed JDBC driver and set up the classpath.
My error message is:
"Driver class 'com.microsoft.jdbc.sqlserver.SQLServerDriver' could not be loaded"
Is above message means that my classpath setup correctly but the application could not load the class or the application could not find the jar file which containes the driver class?
By the way, the third party application I was using to load this JDBC driver does not certified to use microsoft JDBC driver. But I don't think it matter?
Thanks for your help
Hui Lu

Hello,
I have some problem while trying load the
sqlserver2000 jdbc driver
My program is a third party application and it works
with the other type 4 JDBC driver well. So I tried to
use Microsoft SQL server 2000 JDBC driver instead.
I installed JDBC driver and set up the classpath.
My error message is:
"Driver class
'com.microsoft.jdbc.sqlserver.SQLServerDriver' could
not be loaded"
That is an unusual message. Presumably you did not see "NoClassDefFoundError". If you see that it means the class could not be found.
Is above message means that my classpath setup
correctly but the application could not load the class
or the application could not find the jar file which
containes the driver class?
By the way, the third party application I was using to
load this JDBC driver does not certified to use
microsoft JDBC driver. But I don't think it matter?
It could. Perhaps the app expects a certain functional level and the driver doesn't support that. And so it bails with the message that you see.
Or it could mean that you have do something special because it has its own class path, and the driver is not in that.

Microsoft jdbc driver for sql server 2000 error

I try to connect to a sql server database;
After execution of:
C:\Sun\Creator\bin\runide.exe -cp:a =.;"C:\Programmi\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar";"C:\Programmi\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar";"C:\Programmi\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar"
(where "programmi" is "Program Files" in Italian)
I can make a connection to sql server.
When I try to see the "tables" in database I have this error:
[Microsoft][SQLServer 2000 Driver for JDBC]Error setting up static cursor cache
I have tryed to found some resolution and I found only this:
http://forum.java.sun.com/thread.jsp?thread=444136&forum=48&message=2007122
Can you see if it apply on source of IDE and eventually correct?

I'm using the new version and I can't update a row
satRowSet.setDataSourceName("java:comp/env/jdbc/Northwind");
satRowSet.setCommand("SELECT * FROM dbo.Sat");
satModel.setWrappedData(satRowSet);
satRowSet.setConcurrency(java.sql.ResultSet.CONCUR_UPDATABLE);
satRowSet.setHoldability(java.sql.ResultSet.HOLD_CURSORS_OVER_COMMIT);
satRowSet.setAutoCommit(true);
satRowSet.setReadOnly(false);
satRowSet.execute();
satRowSet.next();
try{
this.satRowSet.absolute(1);
this.satRowSet.updateRow();
} catch (Exception ex) {
this.textArea1.setValue(ex.getMessage());
ex.printStackTrace();
java.sql.SQLException: [Sun][SQLServer JDBC Driver]Invalid operation for the current cursor position.
     at com.sun.sql.jdbc.base.BaseExceptions.createException(Unknown Source)
     at com.sun.sql.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.sun.sql.jdbc.base.BaseResultSet.validateCursorPosition(Unknown Source)
     at com.sun.sql.jdbc.base.BaseResultSet.getString(Unknown Source)
     at com.sun.sql.rowset.JdbcRowSetXImpl.getString(JdbcRowSetXImpl.java:842)
     at com.sun.sql.rowset.JdbcRowSetXImpl.getString(JdbcRowSetXImpl.java:941)
     at untitled.Page1.setFields(Page1.java:133)
     at untitled.Page1.beforeRenderResponse(Page1.java:147)
     at com.sun.jsfcl.app.FacesBean.beforePhase(FacesBean.java:227)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:192)
     at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:289)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:311)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:205)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:283)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:102)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:192)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:261)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:215)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:191)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:180)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:582)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
     at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
     at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
     at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:161)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
     at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:979)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:211)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:692)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:647)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:691)
     at java.lang.Thread.run(Thread.java:534)

Driver for 2pc for SQL Server 2000

Hi,Can anybody please tell me which driver to use for achieving 2pc in SQL
          Server 2000.Any free drivers as well as commercial drivers.
          Thanking in advance,
          Vikash Sharma


          Hi,
          This problem are fixed in release 4.0 of i-net OPTA.
          But there exist same problems with XADataSources in the WLS.
          for example that all Statements and ResultSets are closed on a UserTransaction.commit()
          Volker Berlin
          "Priscilla Fung" <[email protected]> wrote:
          >
          >Hi Vikash,
          >
          >We have recently tested out the Inet Opta 2000 driver for MS SQLServer,
          >and we do not certify its use in WLS yet, because it does not support
          >TMJOIN flag when associating a distributed transaction with the
          >XAResource. There is some certification efforts going on for MS
          >SQLServer, and hopefully can be concluded by Silversword (the next
          >WLS 6.0 maintenance release). Either we will work with Inet to
          >resolve the bugs/unsupported features for Inet Opta 2000 driver,
          >so that it can be used inside WLS, or we may try to certify using
          >other drivers.
          >
          >Theoretically, any 3rd party driver that supports the full JDBC
          >2.0 standard extension for distributed transactions should be supported.
          > Feel free to try out other MS SQLServer driver, and let us know
          >if it works.
          >
          >-- Priscilla Fung, BEA Systems, Inc.
          >
          >"Vikash Sharma" <[email protected]> wrote:
          >>Hi,Can anybody please tell me which driver to use for
          >>achieving 2pc in SQL
          >>Server 2000.Any free drivers as well as commercial drivers.
          >>Thanking in advance,
          >>Vikash Sharma
          >>
          >>
          >

SS2K_SYSLOGINS ORA-01401 using WB for SQL server 2000

Similar Messages

Maybe you are looking for