Callable Statement + SQL Server 2000

I am using the Microsoft SQl Server 2000 JDBC driver and a CallableStatement (Java). The call is to a (SELECT action) stored procedure which works fine in Query Manager with the same login params. I am getting a "Could not find stored procedure" error?? I am using the fully qualified procedure name. I have looked on TechNet for this type problem but to no avail.
Thanks
Greg

I'm getting this same problem on one of my stored procs.
Did you ever get to the bottom of your problem?

Similar Messages

Connect webdynpro callable object with ms sql server 2000

Hi all
how connect webdynpro callable object with ms sql server 2000?
How can I register on the portal as an additional connection?
thank you very much!

Thanks for your answers, Now I have the following problem, to develop this code:
try {
          InitialContext iC = new InitialContext();
          DataSource dataSource = (DataSource)iC.lookup("jdbc/ConnectionAlias");
          Connection con = dataSource.getConnection();
          java.sql.Statement stmt = con.createStatement();
          ResultSet rs = stmt.executeQuery("select * from ejemplo");
          while (rs.next()){
               com.sap.test.sql.testsql.wdp.IPrivateTestIViewView.IDatosElement
                                                         DatosElement =
                                                         wdContext.nodeDatos()
                                                         .createDatosElement();
               DatosElement.setId(rs.getString("id"));
               DatosElement.setNom(rs.getString("nom"));
               DatosElement.setNum(rs.getInt("num"));
     }catch (SQLException e) {
          wdContext.currentContextElement().setB(e.getMessage());
     }catch (Exception e){
          wdContext.currentContextElement().setB(e.getMessage());
and shows me the following exception
ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
the data that you place in the visual administrator were:
Drivers: com.sap.aii.af.jmsproviderlib (msutil.jar , mssqlserver.jar , msbase.jar)
DataSources: sap.com/JDBCConnector_MyDatasource.xml
               Name: MyDatasource
               Alias: ConnectionAlias
               DriverName: com.sap.aii.af.jmsproviderlib
               JDBC Version: 1.x
               Driver Class: com.microsoft.jdbc.sqlserver.SQLServerDriver
               Database URL: jdbc:microsoft:sqlserver://181.42.101.219:1433;DatabaseName=test
               User: sa
               Password: abcd1234
did not know the cause of the problem
thanks!

Batch statement with sql server 2000 driver

Hi,
I have been using the jdbc bridge and recently upgraded to the sql server 2000 driver. I have some code that was working correctly executing some batch commands. But with the new driver it no longer works. Its throwing errors. Can anyone help? I have tried removing the begin/end statments and that causes a different error to be thrown.
Statement s = db.createStatement();
s.addBatch("Begin");
s.addBatch("use master");
s.addBatch("EXEC sp_addlogin '" + login +"','" + loginAuth + "','testDB'");
s.addBatch("use testDB");
s.addBatch("EXEC sp_grantdbaccess '" + login + "' , '" + login + "'");
s.addBatch("End");
s.executeBatch();

I have been using the jdbc bridge and recently
upgraded to the sql server 2000 driver. i think you maybe are sol...
Statement s = db.createStatement();
s.addBatch("Begin");
s.addBatch("use master");
s.addBatch("EXEC sp_addlogin '" +
p_addlogin '" + login +"','" + loginAuth +
"','testDB'");
s.addBatch("use testDB");
s.addBatch("EXEC sp_grantdbaccess '" +
ntdbaccess '" + login + "' , '" + login + "'");
s.addBatch("End");
s.executeBatch();the documentation from microsoft reads...
for both CallableStatement and PreparedStatement
void addBatch (String)
Not Supported
Throws "invalid method call" exception.
is this the error you are seeing?

Sql server 2000 stored procs vs. prepared statements performance

Hi
I have observed that using stored procedure in sql server 2000 is much much faster than using a prepared statements. I had worked with oracle before and did not notice this much difference. I would like to use prepared statements or regular sql (for dynamic sql creation) in my apps. Does anyone have any suggestions ?.
thanks

Hi
FYI
I figured out the slowness problem in using prepared statement (db - sql server 2000)was due to the Microsoft typ4 4 jdbc driver. When I used the jdbc driver from atinav, my prepared statements worked as fast as stored procs.

General question on SQL Server 2000 to Oracle 10g

Hello all,
I just have a general question on migration from SQL Server 2000 to Oracle 10g using SQL Developer.
How does it migrate Users with proper privileges from SQL Server to Oracle? Follow the interface steps? Or should the users be created on destination Oracle side?
Thank you.

Hi,
It depends which type of migration you are making.
For a 'Standard' migration when you migrate data a 'create user' statement is created as part of the migration and you will see this in the generated code.
If you are using the 'Quick' migration option then you need to create the Oracle user or use an existing user to receive the data.
Your best option is to review the documentation available from -
http://www.oracle.com/technology/tech/migration//workbench/index_sqldev_omwb.html
or directly from -
http://download.oracle.com/docs/cd/E12151_01/index.htm
and then get back with specific questions if this does not give you the information you need.
Review the chapter -
2. Migrating Third-Party Databases
in -
Oracle® Database SQL Developer User’s Guide Release 1.5
Regards,
Mike

While executing a query in SQL Server 2000

Hi,
I am connecting to an SQL Server 2000 using class.forName method...
and i am reading the data from the queue continuously and execute an INSERT statement to a table..
but the DBAs have a trigger to perform a set of actions when a new row is inserted into that table...
once i insert a row, my program waits until those set of actions have been performed instead of just trying to read from the queue and insert another row into the table...i dont want to wait for anything...i just want to insert the data, go back to read the queue and insert more..
is there any setting that i have to make for this to happen..
tia...

hari786 wrote:
Hi,
I am connecting to an SQL Server 2000 using class.forName method...forName() loads a driver - it does not connect to anything (regardless of database.)
and i am reading the data from the queue continuously and execute an INSERT statement to a table..
but the DBAs have a trigger to perform a set of actions when a new row is inserted into that table...
once i insert a row, my program waits until those set of actions have been performed instead of just trying to read from the queue and insert another row into the table...i dont want to wait for anything...i just want to insert the data, go back to read the queue and insert more..You are out of luck then.
An insert, from the databases point of view is not complete until it is complete. Which means running the triggers.
So there is no way that any jdbc driver can stop that.
Perhaps it might help to describe your actual problem which might lead to the suggestion of other solutions.

Problem of Teststand3.1 database and microsoft SQL Server 2000 personal edition

I have a problem when using teststand database function with Microsoft sql server 2000. the error(seen in attached screenshot3.jpg) is:
"An error occurred calling 'LogResults' in 'ITSDBLog' of 'DBLog 1.0 Type Library'
An error occurred executing a statement.
Schema: Generic Recordset (NI).
Statement: UUT_RESULT.
[Microsoft][ODBC SQL Server Driver][SQL Server]unable to insert NULL value to column "ID", table "test.dbo.UUT_RESULT";This column is not alowed to be blank. INSERT Failed. Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
[Microsoft][ODBC SQL Server Driver][SQL Server]terminated.
Source: TSDBLog"
Here I listed my proceess.
1, Configure in SQL Sever, please see attached screenshot0.jpg
   a, Open SQL
   b, build a new database with the name of test
   c, import the data from "C:\Program Files\National Instruments\TestStand 3.1\Components\NI\Models\TestStandModels\Database\TestStand Results.mdb"
2, Configure Microsoft SQL sever: please see attached screenshot1.jpg
   a, Open windows Control Panel and select "Data Sources (ODBC). Under system DSN tab, add a SQL server data source
3, Configure teststand database option, see attached screenshot2.jpg
   a, configure logging option, enable
   b, configure datalink
   c, select schemas of "Generic recordset (NI)
   d, No change on the tabs of "statements" and "Columns/Parameters"
4, run an seqence file with the proess model of SequentialModel.Seq.
Attachments:
Screenshot.zip ‏425 KB

Thanks Scott,
The database function is OK now after I changed imported tables in SQL Sever.
Actually, I once tried anothor method that you refered by using the scripts
located at: <TestStand>\Components\NI\Models\TestStandModels\Database\SQL Server Create Generic Recordset Result Tables.sql. Attached is the error screenshots, please help me on this.
Thanks
Jacky
Attachments:
Error.jpg ‏59 KB

Java and MS SQL Server 2000 problem, please help

please help me. I am using java and MS SQL Server 2000, and I'm trying to access and verify the login. I'm getting the following error message: [Microsoft][ODBC SQL Server Driver]Invalid Descriptor Index
Can any please help in this regard.
String userNumber = (String)userNumField.getValue();
char[] userPasswordArray = userPasswordField.getPassword();
String userPassword = new String(userPasswordArray);
     try {
            Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
            java.sql.Connection connection = java.sql.DriverManager.getConnection("jdbc:odbc:Dikolobe_Data");
            java.sql.PreparedStatement statement = connection.prepareStatement(
                    "SELECT USER_NUMBER, USER_PASSWORD, USER_CLASS, USER_STATUS " +
                    "FROM SYS_USER " +
                    "WHERE (USER_NUMBER = ? AND USER_PASSWORD = ?);");
            statement.setString(1, userNumber);
            statement.setString(2, userPassword);
            java.sql.ResultSet result = statement.executeQuery();
            if(result.next()) {
                String userStatus = result.getString(4);
                if(userStatus.equals("logged on")) {
                    String loginErrorMessage = "User with number: " + userNumber + " is already logged on.";
                    javax.swing.JOptionPane loginErrorPane = getNarrowOptionPane(72);
                    loginErrorPane.setMessage(loginErrorMessage);
                    loginErrorPane.setMessageType(javax.swing.JOptionPane.ERROR_MESSAGE);
                    javax.swing.JDialog loginErrorDialog = loginErrorPane.createDialog(null, "Login Error");
                    loginErrorDialog.setVisible(true);
                else {
                    String userClassification = result.getString(3);
                    if(userClassification.equals("Administrator")) {
                        AdminHomePage newAdminHomePage = new AdminHomePage();
                        newAdminHomePage.setVisible(true);
                    else if(userClassification.equals("Educator")) {
                        EduHomePage newEduHomePage = new EduHomePage();
                        newEduHomePage.setVisible(true);
                    statement = connection.prepareStatement(
                            "UPDATE SYS_USER SET USER_STATUS = ? " +
                            "WHERE USER_NUMBER = ?");
                    statement.setString(1, "logged on");
                    statement.setString(2, userNumber);
                    statement.executeUpdate();
                    dispose();
            }

Doesn't the following link give you enough information?
http://www.google.com/search?q=invalid+descriptor+index
Anyway .. This error means that the given ResultSet column index which you're trying to retrieve the value from is out of the range.

Which Driver for MS SQL-Server 2000

Hello,
i need to access a MS SQL-Server 2000 and want to ask which driver you think is the best one for this problem.
I am not a big fan of using beta-Software, and i do not need the newest state-of-the-art features. Right now i also do not need Connection-Pooling.
Only a few SQL SELECT/UPDATE-Statements nothing more.
But maybe in not far away future, Conn-Pooling and Procedure-Calls could be interesting. And i think Type 3 or 4 would be the best decision.
The Software will run on NT, but i do not want to use the JDBC/ODBC-Bridge, because it is so unbelievable slow.
I am interested in WHICH DRIVER you USE, AND especially which drivers you DO NOT USE ANYMORE, and why.
It would be great, if anyone could help me, finding the best solution.
P.S.: The price of the driver: It would be good, when it is for free. But if you know a good commercial driver i am also interested in.
P.P.S: Yes, i have searched for drivers under http://servlet.java.sun.com/products/jdbc/drivers. But there are 37 different Type 3/4 drivers.

You can try the jtds project .Search for it in www.sourceforge.net. It is derived from FreeTDS JDBC driver. Both of them are Type 4 JDBC drivers. So far I have tried both of them a few years ago. And jtds is more updated (during those time, not sure what the status is right now)
Or, you can get Microsofts own JDBC driver

Query Perofmance is much more fast in SQL server 2000 than Oracle 9i

I have converted a database from SQL Server 2000 to Oracle (9.0.2).
In a stored procedure a query based on 4 tables working well in SQL Server which takes just 1 or 2 minutes to give result But in Oracle it takes 3 to 4 Hours to return the results.Although Database hit ratio is 99 plus %. In Oracle when i created indexes on 2 columns of 2 tables it just take 5 to 10 sec. But I want to get the result in less time without indexes. Because in
SQL Server it Works well without indexes.
Please reply me with some solutions or reasons
Regards
AN

Most sites have a job that runs every night to keep the statistics up to date.Really? I would be very surprised if that was the case. Firstly, many sites don't want to take the hit of running stats for a whole system each night. Secondly, I would hope that many DBAs know this statement...
Always keep up to date statistics if you want your database to be efficent. ...is wrong.
The best that can happen from refreshing the statistics every night is that it makes no difference to your application. If your application is running nicely - that is, no users are yelling at you - then your current statistics are good enough. Refreshing statistics introduces instability into the system and might lead to queries performing worse than before.
Gathering stats is not the sort of thing you want to do with a scattergun. Analyze your database once, after you've reached what is a representative data volume and then leave it alone. Only refresh statistics if you have a specific issue (user complaint) and you think stale statistics might be the cause.
Cheers, APC

Can't registerOutParameter of cursor type in SQL Server 2000

Hi, there,
I'm using SQL Server 2000 and a type 4 JDBC driver for it from JRun 3.1. I wrote a stored procedure which has a Cursor (ResultSet) as an output parameter. But I used callStmt.registerOutParameter(1, java.sql.Types.OTHER);
I got an exception:
callable stmt class: allaire.jrun.db.jdbc.base.BaseCallableStatement
java.sql.SQLException: [JRun][SQLServer JDBC Driver]The specified SQL type is not supported by this driver.
I definitely want the cursor to be an output parameter in my SQL 2000 store procedure, rather than defining a store procedure without an output Cursor parameter and then use callStmt.getResultSet();
Does any one knows a way to register an output parameter of type CURSOR in SQL Server 2000 JDBC?
I know that with in Oracle JDBC driver, you can do this:
callStmt.registerOutParameter(1, OracleTypes.CURSOR);
ButI failed to find a equivalent in SQL Server 2000 JDBC driver.
Thanks a lot.

If you found any solution to this, would you please let me know too? It'll help a tonne.

DTS Import of MDB in SQL Server 2000 Drops Memo Field Data

I have used DTS in SQL Server 2000 to import an MDB filed (MS ACCESS) of a table. When the table is imported the primary key is lost and the memo field data is completely gone.
I use the tranformation option in the DTS wizard to add the primary key and make sure the data type for the memo field is varchar and has a size of 8000. I need that large size since I am storing lots of html code.
When I preview the data I see the html code that is supposed to get imported. However, when I return all rows from the table in Enterprise Manager the field is empty.
So I tried to manually copy the data from the MS Access Database into SQL Server. Could not figure out if SQL Server has an interface like MS Access to simply copy data into a table. So I linked to the tables from MS Access to the SQL Server table.
When I opened the linked table I see the data in the description field. However, if I return the rows from within SQL Server no data is present.
I have some ASP code trying to read the data in the SQL Server table. However, nothing is returned and when I run the SQL Statement, nothing gets returned. The SQL statement returns all rows. All the other data is present but nothing in the description field.
What am I doing wrong? Any suggestions anyone, please!
TIA

It is important to know the version of MS Access. I will recomend you to use nvarchar datatype instead of varchar. May be the description field contain unicode characters.
Refer this link to understand more on datatype mapping between access source and sql server destionation.
http://blogs.msdn.com/b/ssma/archive/2011/03/06/access-to-sql-server-migration-understanding-data-type-conversions.aspx?Redirected=true
Regards, RSingh

Problem with Sensitive ResultSet in SQL Server 2000

Hi,
I am trying to use SCROLL_SENSITIVE and CONCUR_UPDATABLE ResultSet accessing SQL Server 2000. I am using JDK 1.3 and supported JDBC driver. When I tried to insert a row, I got the following message:
sp_cursor: The cursor identifier value provided (0) is not valid
Is there any setting in SQL Server that I need to configure or do I miss something in my code?
Thanks,
Andi Setiyadi
Here are my codes:
cs = connection.prepareCall("{call sp_deptInfo (?,?,?)}", ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE);
cs.setInt(1, 0);
cs.setString(2, "");
cs.setString(3, "name/orderbyid");
rs = cs.executeQuery();
rs.last();
int rows = rs.getRow();
rs.afterLast();
rs.moveToInsertRow();
rs.updateInt(1, rows + 1);
rs.updateInt(2, Integer.parseInt(parentDept));
rs.updateString(3, newDept);
rs.updateInt(4, 1);
rs.insertRow();

I am getting the resultset by calling a stored procedure. I am not changing the stored procedure itself.Database drivers create 'connections' and 'statements' which match the SQL that you pass it. You are passing it a stored proc. The only information that it has is on a stored proc. It doesn't matter where the stored proc got its info from. The stored proc doesn't return tables and indexes into tables. It returns a result set (that is what your code suggests.) That is all the information that the driver has.
Consider your stored proc might return this
select * from mytable where ....
But it could also do this
select 'value1', 'value2', ... from dual
On the java side it isn't not going to know which of the above that you did. Nor should it. And you can't update/insert into that second example.
Or at least that is how I look at it.
Your code looks like it is trying to 'update' the result set that a stored proc returned. And I simply don't see how that is possible. Or even why anyone would want to do it.

WL 6.0 using MS SQL Server 2000 - Transaction timeout when invoking stored procedure

Hi,
Facing a problem on WL6.0. We are connecting to MS SQL server 2000 using a stateless
session bean
using container managed transaction. The bean method does a few updates to the
database and also
calls a stored procedure that generates primary keys many times. This stored procedure
(SP) is running
in a transaction of its own since it has to increment a counter, update the database
and then return the
primary key.The primary key generator SP is working fine and does not lock the
database in many bean
methods.
In some methods we find that the primary key generator SP has locked the database.
We
then see a lock on the database created due to this SP in the MS SQL client. The
execution goes
into the SP and gets stuck there till the bean's transaction times out. The error
message given is
...... .. Exception Message - The transaction is no longer active
(status = Rolling Back. [Reason = weblogic.transaction.internal.TimedOutExcepti
on: Transaction timed out after 31seconds
tx = transaction=(IdHash=1746718,Name = [EJB StructMgrBeanImpl.addStructure()],X
id=10908:51e67e9d7185816a,Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=
0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '7'
for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[web
logic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[myserver]=(state
=active),properties=({weblogic.transaction.name=[EJB StructMgrBeanImpl.addStruct
ure()], weblogic.jdbc=t3://10.200.15.136:7001}))]). No further JDBC access is
al
lowed within this transaction.
What could be the potential problems in the method's code/SP that could be causing
the timeout?
Anyone faced similar problems?
Thanks in advance,
Sreeja

Hi,
Facing a problem on WL6.0. We are connecting to MS SQL server 2000 using a stateless
session bean
using container managed transaction. The bean method does a few updates to the
database and also
calls a stored procedure that generates primary keys many times. This stored procedure
(SP) is running
in a transaction of its own since it has to increment a counter, update the database
and then return the
primary key.The primary key generator SP is working fine and does not lock the
database in many bean
methods.
In some methods we find that the primary key generator SP has locked the database.
We
then see a lock on the database created due to this SP in the MS SQL client. The
execution goes
into the SP and gets stuck there till the bean's transaction times out. The error
message given is
...... .. Exception Message - The transaction is no longer active
(status = Rolling Back. [Reason = weblogic.transaction.internal.TimedOutExcepti
on: Transaction timed out after 31seconds
tx = transaction=(IdHash=1746718,Name = [EJB StructMgrBeanImpl.addStructure()],X
id=10908:51e67e9d7185816a,Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=
0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '7'
for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[web
logic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[myserver]=(state
=active),properties=({weblogic.transaction.name=[EJB StructMgrBeanImpl.addStruct
ure()], weblogic.jdbc=t3://10.200.15.136:7001}))]). No further JDBC access is
al
lowed within this transaction.
What could be the potential problems in the method's code/SP that could be causing
the timeout?
Anyone faced similar problems?
Thanks in advance,
Sreeja

Cant export worksheet when connected to MS SQL Server 2000

SQL Developer version: 1.5.1
Hello,
I have a connection to an SQL Server 2000 database. I can select data with an "order by" clause but I receive an error when I attempt to do an "Export --> xls" on the worksheet data. I dont think this was a problem prior to SQL Developer 1.5.
No export error occurs if the "order by" cluase is removed.
Here is an example of a select stmt that generates the error.
select LastName, FirstName, EmployeeID
from northwind.dbo.employees
order by LastName, FirstName
Here are the error details:
First dialog box error text: The ORDER BY clause is invalid in views, inline functions, derived tables, and subqueries, unless TOP is also specified.
Second dialog box error text (after clicking Details button):
java.lang.NullPointerException
     at oracle.dbtools.raptor.dialogs.export.ColumnPanel.addColumnsToTree(ColumnPanel.java:85)
     at oracle.dbtools.raptor.dialogs.export.ColumnPanel.showPanel(ColumnPanel.java:61)
     at oracle.dbtools.raptor.dialogs.export.ColumnPanel.<init>(ColumnPanel.java:45)
     at oracle.dbtools.raptor.dialogs.actions.TableExportAction.showPanels(TableExportAction.java:297)
     at oracle.dbtools.raptor.dialogs.actions.TableExportAction.launchDlg(TableExportAction.java:197)
     at oracle.dbtools.raptor.format.ui.ExportContextMenuListener$1.actionPerformed(ExportContextMenuListener.java:137)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
     at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
     at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
     at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000)
     at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1041)
     at java.awt.Component.processMouseEvent(Component.java:5488)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
     at java.awt.Component.processEvent(Component.java:5253)
     at java.awt.Container.processEvent(Container.java:1966)
     at java.awt.Component.dispatchEventImpl(Component.java:3955)
     at java.awt.Container.dispatchEventImpl(Container.java:2024)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
     at java.awt.Container.dispatchEventImpl(Container.java:2010)
     at java.awt.Window.dispatchEventImpl(Window.java:1774)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
The table selected from is not a view, inline function, derived table, or subquery (as the error suggests). I can work around the problem by adding "TOP nnnn" to the select statement but this shouldn't be required.
Any suggestions?
Thanks.

I confirmed that this is not a problem in SQL Developer 1.2.1.32.13. It started with 1.5. In 1.5.1.5540 I can successfully run the query and see the output in the Results tab. Only the Export has the error.

Callable Statement + SQL Server 2000

Similar Messages

Maybe you are looking for