SQL Server excuteBatch() problem....

Hi All,
I am trying to Bulk insert using addBatch() and excuteBatch()
which works fine.
The problem I am facing is, when I am inserting 50 queries in excuteBatch(), even
one of them fails, ( due to some foriegn key violation ) whole process stops.
Can we able to ignore all the failed ones, and proceed till the end in excuteBatch()?
I am using MS JDBC Driver for SQL Server and WL server 6.1 sp3.
any help will be really helpful..
thanks,
Arun

Arun wrote:
Hi All,
I am trying to Bulk insert using addBatch() and excuteBatch()
which works fine.
The problem I am facing is, when I am inserting 50 queries in excuteBatch(), even
one of them fails, ( due to some foriegn key violation ) whole process stops.
Can we able to ignore all the failed ones, and proceed till the end in excuteBatch()?
I am using MS JDBC Driver for SQL Server and WL server 6.1 sp3.
any help will be really helpful..
thanks,
ArunHi. Duplicate the problem in a standalone program, without weblogic code.
It sounds like a driver bug, and you should post this to the ms jdbc newsgroup.
Joe Weinstein

Similar Messages

RE: Database (SQL-SERVER) access problem

Have you used NT Control Panel/ ODBC to set up the ODBC data source name?
You have to define the data source (database) SecTrade as well as the
driver to be used (SQL Server). This can be done by selecting the Add
button on the Data Sources screen in Control Panel/ ODBC.
Hope this helps.
Sanjay Murthi
Indus Consultancy Services, Inc.
From: Administrator
Sent: Wednesday, August 13, 1997 6:49 PM
To: "'[email protected]'"
Cc: murthis; thyagarajm; thyagarm; vasasm; chandraa
Subject: Database (SQL-SERVER) access problems
MCI Mail date/time: Mon Aug 11, 1997 10:28 pm EST
Source date/time: Mon, 11 Aug 1997 19:25:34 +0530
Hi Forte-Users,
We have a setup a Sql-Server database on a NT server. In the Forte
EConsole,
we have
setup a ODBC-type Resource for this server, named SERVER2_ODBC. This NT
server
is configured as a Client Node in the active Forte environment. Note
that
Server2 is not
the Forte server, but has Forte installed. There is another NT server
which
acts as the
Forte server. NODEMGR and Sql-Server are running on SERVER2.
In our application, we have a DBSession SO with the database source
as SERVER2_ODBC, Userid=ForteInstructor. When running the application,
Forte
throws an exception, the gist of it being as follows:
USER ERROR: (This error was converted)
Failed to connect to database: SecTrade, username: ForteInstructor.
[Microsoft][ODBC Driver Manager] Data source name not found and no
default
driver specified
We have tried
1) Installing ODBC drivers on the NT server (Server2)
2) Accessing local databases from Forte clients which works fine
3) Accessing the Sql-Server database through Isqlw (Sql-Server Client
s/w) -
It works.
Could someone suggest what we should try to get rid of this problem?
Thanks for any help,
Kishore Puvvada

Rajsarawat wrote:
Dear sir/mam,
I have installed sql server 2005 (server) and on another computer installed client. It installed successfully but on client side it does not seen, from where should i start it. so please send me procedure to install sql server 2005 on both side(client and server).You have to turn on network (external to your computer) access.
Under programs->sql server look for "surface"

Crystal Report 8.5 with SQL SERVER 2005 problems

Post Author: AREVA
CA Forum: Data Connectivity and SQL
Hi All !We have some problems with Crystal Reports version 8.5 with SQL Server 2005: 1) When we want to generate a report (using data in SQL Server 2005) we have a popup message error : "impossible to loaded pdssql.dll".2) If we want to use SQL Server 2005, which Crystal Reports version we must used ? Is there any restrictions with this connectivity with 8.5 version ?Please, let me known, all informations about SQL Server 2005 and Crystal Report 8.5.Thanks for all !Best regards Anthony

Hello Kamlesh,
There is no expectation that the ActiveX viewer (RDC?) from CR8.5 will work in any version of Visual Studio .NET. There is also no expectation that the ActiveX viewer from CR8.5 will work on a machine with a 64 bit operating system.
You're using VS2008. You should migrate to the bundled edition of CR for VS2008 (v10.5), the ReportDocument object, and the .NET Windows form viewer or Web form viewer.
Sincerely,
Dan Kelleher

SQL Server driver problem

I am trying to connect to SQL Server 2000. I have JDK1.3.1_02. When I compile my applet I get the error that class sqlserver from the statement "Class.forName(com.microsoft.jdbc.sqlserver.SQLServerDriver);" not found. I have included the path in my classpath as "d:\JDBC\lib\msbase.jar;d:\JDBC\lib\msutil.jar;d:\JDBC\lib\mssqlserver.jar" where JDBC is the root directory for the driver.
Even the statement "import com.microsoft.*;" returns an error that package com.microsoft.* does not exist. What can be the problem?
Any suggestions/help appreciated!

You should be getting a different compiler error. Class.forName() requires a String argument, so your code should look like this:Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");Note the quotes around the class name. Also, your "import" statement is irrelevant in any case because that class is not in the com.microsoft package, it is in the com.microsoft.jdbc.sqlserver package.

SQL Server/JDBC Problems...

I know this topic has been posted before, and believe me I've read all of it and followed instructions at least 5 times over. But I just can't get rid of :
Got an exception!
[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
On my SQL server side:
1) My Client Network Utility and Server Network Utility both have TCP enabled and default port set to 1433
2) I've set authentication to "SQL Server and Windows" instead of just "windows".
3) For now I'm using my 'sa' account as startup which is set to "SQL Server and Windows" authentication.
4) I've disabled and then enabled TCP a bunch of times, that doesn't seem to help.
5) My SQL Server log says:
2005-02-22 10:12:12.86 server SQL server listening on Shared Memory, Named Pipes.
It should say something about TCP according to the MS SQL help, but I've had no luck with that.
I've even tried NMAP on my computer to check for open TCP ports, and 1433 doesn't show up. My guess is the problem is with SQL Server 2000 (I'm using Java 1.5.0_01 for now). Is there some kind of trick (ritual? animal sacrifice?) needed to get SQL Server to start listening on TCP? God knows I''ve tried everything short of kicking the **** out of my purchased boxed set. Please...any help in the matter would be GREATLY appreciated. Thanks

I had the same problem on my windows XP laptop.
For windows XP you need SQL Server 2000 service pack 3.
Of course you may not be using windows XP but the service pack will not hurt.

SQL Server Database Problems

I have been using SQL Server for sometime with my company's product with no
unusual problems for some time.
However, having recently installed a Forte repository on a newly setup NT
machine (Workstation 4, SP4), I have come across problems.
The code constructs a cusor which requests columns from a table. Some of those
columns are of int type but when they are retrieved, the values are completely
different to those that can be seen when writing SQL statements directly from
ISQL.
For example, 1 becomes a seven figure number.
The following code is being used to iterate through the result set and create
another string which is made from the values concatenated together :
for CurRow in 1 to outputDataSet.ActualRows do
outputDataSet.CurrentRow = CurRow;
for curCol in 1 to outputDataSet.ColumnList.Items do
outputDataSet.GetValue(curCol,Value);
if(not Value.IsNull) then
// If datetime datatype, need some conversion
if (outputDataset.columnList[curCol].DataType =
DV_DT_DATETIME ) or (outputDataset.columnList[curCol].DataType =
DV_DT_DATETIME_NULLABLE ) then
begin
tempDateTime.SetValue( Value.TextValue );
-- The user has entered an invalid Date format.
exception
when e : UsageException do
tempDateTime.DecodeValue(source=Value.TextValue,
format=dateForm);
end;
pResultData.Concat(dateForm.FormatDate(tempDateTime));
else
pResultData.Concat(Value.TextValue);
end if;
end if;
if(curCol <> outputDataSet.ColumnList.Items ) then
-- pResultData.Concat('\t');
pResultData.Concat(pDelimChar);
else
pResultData.Concat( source = '\r\n' );
end if;
end for;
end for;
This has not occurred on any other installation and the only ideas that I have
are that :
i) the ODBC driver is either the incorrect version or has been setup incorrectly
in some way
ii) there are problems with the configuration of SQL Server or NT that is
causing this problem
Does anyone have any ideas ?
Thanks,
Alex

My recomendation is to debug the web page. Set a breakpoint by clicking on the row say probably at the page load/form load event. Press F5 to start the debug. Click F10 to step over next row multiple times until and unless you get the error message. i.e
Invalid column name 'UserId'.
The piece of code which you have posted does not contain any assignment or usage of column name "UserId", therefore post the portion of the code where the error is actually taking place.
Regards, RSingh

SQL Server 2000 problem with MII Version 12.1.8 Build(24) Reconnecting

Hi,
I have a problem using XMII Version 12.1.8 Build(24) with com.microsoft.sqlserver.jdbc.SQLServerDriver JDBC driver with SQL 2000.
The problem we have is the machine where the SQL server is installed on reboot as per schedule once a week. When the server comes back online, XMII seems to get problem to reconnect correctly. Sometimes it reconnects perfectly, sometimes not.
When it fails, the only way to fix the problem is to uncheck the 'Enabled' checkbox, then save the data server, then check the 'Enabled' checkbox, then save again.
When the reconnect issue happens, uploading messages to SAP fail 100% of time, but downloading Control Recipes from SAP works 50% of time. For example, some PO's can be processed correctly, some others not, causing data losses due to poor data buffering(buffering doesn't cover connection time out). The failed PO's are marked as 'Sent' into CO53 SAP transaction but in fact, are lost in a hole causing data losses.
See the error we get atfer the server reboot:
Unable to get a connection from the pool
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host VANASR70, port 1433 has failed. Error: "connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting... [see details]
Cannot create a connection to the database
[EXCEPTION]
com.sap.xmii.Illuminator.system.CommunicationException: Cannot create a connection to the database... [see details]
Error processing transaction com.sap.xmii.bls.engine.TransactionInstance@cee764f
[EXCEPTION]
com.sap.xmii.scheduler.CronException: PMU ERR VAN - Cannot Qry MSIDs.... [see details]
Unable to get a connection from the pool
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host VANASR70, port 1433 has failed. Error: "Connection refused. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting... [see details]
Unable to get a connection from the pool
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host VANASR70, port 1433 has failed. Error: "connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting... [see details]
The only way we have thought to workaround this problem is to develop our own buffering method into XMII workbench puting all data received from SAP or SQL insert query into an Oracle temp database. We should probably be able to fix this by this way, but it reprensents many costs and efforts, so we try to avoid this for sure.
Please, if you can provide us a patches or hints about how to fix this, it could be very appreciated because loosing data is very anoying.
Thanks a lot!
Edited by: mrmans on May 19, 2011 5:48 PM
Edited by: Michael Appleby on May 19, 2011 6:10 PM

The validation query is in place and the system works very well 99% of the time.
When the SQL server machine reboot each sunday morning, during the time the machine is rebooting, the data server lose the connection which is normal, but when the machine comes back alive(less then 10 minutes), the data server seems to stay in an 'in-between' state showing the connection status 'Running' but showing also error messages posted in the orginial post in Netweaver logs. So at first look the data server is up and running and reconnected to SQL server after the reboot, but in fact, following these errors after the SQL server machine has rebooted, some data are processed correctly from SAP (Control Recipes) and some not.
The problems looks like very similar to threadID 1596329.
Here is the data server configuration for all our 5 data servers:
Connector IDBC
ConnectorID
ConnectorType SQL
DatePrefix '
DateSuffix '
DaysRetention 7
Description VANASR70 INTERFACE with MS-SQL JDBC 3.0
Enabled T
InitCommand
InternalDateFormat yyyy-MM-dd HH:mm:ss
JDBCDriver com.microsoft.sqlserver.jdbc.SQLServerDriver
MaxRetryCount 50
Name PROF_INT_VAN
PoolMax 150
PoolSize 100
RetryInterval 60000
ServerPackage com.sap.xmii.Illuminator.connectors.IDBC
ServerURL jdbc:sqlserver://VANASR70:1433;databaseName=INTERFACE
Timeout 30
UseCount 256
UserName mii_user
ValidationQuery SELECT GETDATE()
WaitTime 60

SQL server 2005 problem with service starting

I am having a problem starting my sqlserver service. It will not start and therefore i have no access to my sql 2005 server database. This is what in the event log. This database was working fine until i had two drives kill over in a RAID configuration.
The striping went out with a hitch and no i want to see if anyone have any ideas before i perform a restore. Do i need to run SQL server repair with the installation disk?

Well from viewing the log it looks like i am in a pickle. Since the SQL service won't start, is there a command or script to run for a database check using powershell? Since it looks like i will be doing a restore, just curious now.
2014-01-16 15:27:58.30 spid5s      Starting up database 'master'.
2014-01-16 15:27:59.81 spid5s      Error: 824, Severity: 24, State: 2.
2014-01-16 15:27:59.81 spid5s      SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:363; actual 0:0). It occurred during a read of page (1:363) in database ID 1 at offset 0x000000002d6000 in file
'W:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately.
Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
2014-01-16 15:27:59.81 spid6s      Error: 922, Severity: 14, State: 1.
2014-01-16 15:27:59.81 spid6s      Database 'master' is being recovered. Waiting until recovery is finished.
2014-01-16 15:27:59.81 spid6s      System Task System Task produced an error that was not handled. Major: 9, Minor: 22, Severity:14, State:1
2014-01-16 15:27:59.81 spid5s      Error: 3313, Severity: 21, State: 2.
2014-01-16 15:27:59.81 spid5s      During redoing of a logged operation in database 'master', an error occurred at log record ID (2369:160:2). Typically, the specific failure is previously logged as an error in the Windows Event Log
service. Restore the database from a full backup, or repair the database.
2014-01-16 15:27:59.81 spid5s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL
Server Books Online.

MS SQL Server 2000 Problem to Connect

Hi There
I have a problem with MS SQL Server 2000 with Service Pack 3 and JDBC from Microsoft
My tools are:
- Windows 2003 Server Standart Edition
- MS SQLServer 2000 with ServicePack 3
- JDBC from Microsoft with ServicePack 3
I want to connect in the database using JDBC.
At first time, I follow the example to chance the authentication of SQL
Server
http://www.banmanpro.com/support/sql2k.asp
Now, when I will try out to connect in the SQL Server, I receive this error
message
java.sql.SQLException: [Micro$oft][SQLServer 2000 Driver for
JDBC][SQLServer]Login failed for user 'Administrador'.
I'm trying to connect in SQL Server using my Windows Account, in other
words, I'm using the ADMIN account of Windows and which was registered in
the SQL Server.
In then DriverManager.getConnection line from Java, the Username and
Password is same the operation system, but I receive the error below.
Maybe Can you help me please?

You can't log in using Windows credentials using the MS driver (yes, I know that sounds kind of funny). Use jTDS for that, if you really need it (or if you encounter any other problems with the MS driver). Otherwise log in using SQL Server credentials (try with user sa and blank password if not sure).
Alin.

JDBC MS SQL Server ResultSet Problem

I'm writing a web-app using apache tomcat. I'm using MS SQL Server 2000 as my database. I am having no problem connecting to the database, but whenever I query the database, the ResultSet that is returned never has anything in it. I've tried even the simplest select queries and i'm still getting no results. I thought it might be a problem with the JDBC Driver I've been using, but I'm using the exact same driver for SQL Squirrel Client to connect, and Squirrel Client is returning results just fine from the database. Is there something that I've forgotten in my servlet code? Here's something like what I've been using:
Connection con = DriverManager.getConnection(host, userName, password);
Statement stmt = con.createStatement();
ResultSet rs = stmt.executeQuery("select * from some_table");

If the select statement returns rows then the loop will execute... Put in some debugging output just before the while() loop, inside the loop, and immediately after the loop.
Are you ignoring exceptions?
Google for "jdbc tutorial". Take the simplest example program there that selects something. Run it as a command line program. Does it work? (Answer: yes.) Now what is different between that example program and your code?

Windows server 2003 connect to SQl server 2000 problem

my problem
D:\Myjava>java connect
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establis
hing socket.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Sou
rce)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown S
ource)
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:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at connect.getConnection(connect.java:26)
at connect.displayDbProperties(connect.java:43)
at connect.main(connect.java:79)
Error Trace in getConnection() : [Microsoft][SQLServer 2000 Driver for JDBC]Erro
r establishing socket.
1)both my sql server server and client listen the port 1433
2) on sql security -> Logins I have the user call test and password call 1234 can access to pubs
what else I need to care
Thank you

This version did not have built in service packs. You have to install it sepeartely. Check this link.
http://vyaskn.tripod.com/sqlsps.htm
Best of luck
Muhamamd Uzair Baig
JEE Application Developer
Dubai Customs.

MX7 SQL SERVER Datasource problem

hello
I installed MX7 and I do not manage to create a datasource
which
point towards my dB MSSQL SERVER on local, it posts me this:
Connection verification failed for data source: blanko
java.sql.SQLException: [Macromedia][SQLServer JDBC
Driver]Error
establishing socket. Unknown host: (local)
The root cause was that: java.sql.SQLException:
[Macromedia][SQLServer
JDBC Driver]Error establishing socket. Unknown host: (local)
under Coldfiusion server 5.5 there was the possibility of
checked “Trusted connnection” and it had no prob with
MSQLSERVER there Apparently it is necessary to work with the JDBc
drivers but I do not have any idea of how to install it I am sure
that it is a traditional error, if somebody has already encountered
the problem,
thank you to light me
thks Sam
Configuration: Windows 2003 Internet Explorer 7.0

I found why it did not recognize localhost, because I placed
(localhost) between bracket because on CF 5.5 it was the case for
(local), therefore now it recognizes apparently the localhost as
server but it is another problem now: it did not recognize the
username and password,
however I configured SQL SERVER 2005 in mixed mode and thus
I test with login: Administrator and password empty (because I
don't have password on Windows authentication) and I also test with
username: sa and my password admin but without success, here what
it indicates as error:
Connection verification failed for data source: blanko
java.sql.SQLException: [Macromedia][SQLServer JDBC
Driver]Error establishing socket. Connection refused: connect
The root cause was that: java.sql.SQLException:
[Macromedia][SQLServer JDBC Driver]Error establishing socket.
Connection refused: connect
in addition I do not know if there is a bond, (I work under
win 2003 standard edition) and according to what I read on the Net,
it may be that it is a problem of port, can be the port 1433 is not
open? If I make on DOS prompt: telnet localhost 1433 ==> failure
to connect whereas telnet localhost 80 works
I even tried to connect with
username: sa
pwd: mypwd
port: 80 (I know that 80 is the port for HTTP)
it posts the following message:
Connection verification failed for data source: blanko
java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]No
more data available to read.
The root cause was that: java.sql.SQLException:
[Macromedia][SQLServer JDBC Driver]No more data available to read
thanks for your help

Sql Server 2014 Problem

Hello,
Can anyone help me that i installed sql server 2014 after installation when i open it it is asking for server name ,how to solve this problem?

Hello,
Can anyone help me that i installed sql server 2014 after installation when i open it it is asking for server name ,how to solve this problem?
First please tell did you installed named instance or default instance. Did you installed licensed version/evaluation edition or express edition.
You always connect to SQL Server using SSMS like
Hostname\instancename. You can go to Run type cmd and in command prompt type hostname the name returned is your hostname. Instance name is name of SQL Server instance which you created with installation ( if you created one or else it will be default instance)
If it is default instance and not a SQL Express you can just type dot. Dot like
. and can connect. If it is SQL express you can connect like Hostame\SQLEXPRESS.
If it is named instance connect like Hostname\instancename.
PS: Use account which you have added as administrator while installing SQL server as shown by Javier. if you selected mixed mode authentication you can connect by SA.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

SQL Server 2005 Problem: Incorrect syntax near '{'

hi, 
 
I am using SQL Server 2005 JDBC driver from Microsoft (sqljdbc_1.0.809.102_enu.exe), there are some problem when calling stored procedure from Database Control: 
 
The following exception flow when parameters of the stored procedure were wrapped to newline : 
 
weblogic.jws.control.ControlException: ControlException on control test2005DBCtrl[Incorrect syntax near '{'.] 
 
Here is the method that generate the above exception: 
 
/** 
* @jc:sql statement:: 
* {call P_dummyProcedure 
 * ( 
 * {intValue}, {value} 
* ) 
* }:: 
*/ 
void callStoreProcedure(int intValue, String value); 
 
But if the parameters were not wrap, the method work fine: 
 
/** 
* @jc:sql statement:: 
* {call P_dummyProcedure 
 * ( {intValue}, {value} ) 
* }:: 
*/ 
void callStoreProcedure(int intValue, String value); 
 
The above problem exist when I change from SQL Sever 2000 to 2005. Both methods is ok for SQL Server 2000 (both the driver from BEA and Microsoft) 
Do any one got the above problem or know why? 
 
cheer ~
 

Wiz Cheng wrote:
hi Joe, 
 
following is a snippet of the config.xml, please see if that cover what you want ~ 
 
config.xml 
---- 
 <JDBCConnectionPool CapacityIncrement="5" 
?? ?? ?? DriverName="com.microsoft.sqlserver.jdbc.SQLServerXADataSource" 
?? ?? ?? InitialCapacity="10" MaxCapacity="100" Name="sql2005Pool" 
?? ?? ?? PasswordEncrypted="{3DES}lF9SivpaSCc=" Properties="user=sa" 
?? ?? ?? SupportsLocalTransaction="true" Targets="cgServer" 
?? ?? ?? TestConnectionsOnReserve="true" TestTableName="SQL Select 1" 
?? ?? ?? URL="jdbc:sqlserver://svr08006\\SQL2005:1533;databaseName=SBI" 
?? ?? ?? XASetTransactionTimeout="true" XATransactionTimeout="300"/> 
 
<JDBCTxDataSource JNDIName="JNDI_SQL_2005" Name="JNDI_SQL_2005" 
?? ?? ?? PoolName="sql2005Pool" Targets="cgServer"/> 
 
 
Thanks ~ 
WizOk, please recreate the pool, telling the console to use the BEA driver for MS.
when it shows you the pool properties, it should show you a URL, something like:
"jdbc:bea:sqlserver://......". Please then edit the URL to add this to the end:
;spyAttributes=(log=(file)spy.log, so the URL looks like
jdbc:bea:sqlserver://......;spyAttributes=(log=(file)spy.log)
Or just make the pool, and then edit the config file.
You should then see the config entry look something like this:
<JDBCConnectionPool CapacityIncrement="5"
DriverName="weblogic.jdbcx.sqlserver.SQLServerDataSource"
InitialCapacity="10" MaxCapacity="100" Name="sql2005Pool"
PasswordEncrypted="{3DES}lF9SivpaSCc=" Properties="user=sa"
SupportsLocalTransaction="true" Targets="cgServer"
TestConnectionsOnReserve="true" TestTableName="SQL Select 1"
URL="jdbc:bea:sqlserver://......"
XASetTransactionTimeout="true" XATransactionTimeout="300"/>
Then please alter the URL line so it's like:
URL="jdbc:bea:sqlserver://......;spyAttributes=(log=(file)spy.log)"
This will generate a file in the server directory called spy.log.
Then when the server boots, please then run the code that would
have caused the problem, as simply as possible, and then send
me the spy.log file.
thanks,
Joe

SQL Server JDBC Problem - Exception vs. Empty ResultSet

I just uploaded and installed the latest pre-release build (123667). Win2K
platform.
There is something very wrong with the MS SQL Server JDBC behavior now.
If you Select * from a table which exists but is empty, the code raises an
exception like:
weblogic.jdbc.mssqlserver4.TdsException: Statement.executeQuery - No result
sets
were produced by 'SELECT recordHandle, record, recordState FROM JMSStore'
This is a big change. Normally JDBC returns an empty ResultSet. Cloudscape
still works fine, I havent test any other drivers yet.
This is also affecting EJB deployment -- Many beans in the examples provided
with the product fail to deploy with an error because of this JDBC exception
change. (Yes I'm sure the required tables are in my SQL*Server database,
I've been running the beta for a month now).
Help!

Sorry. My fault i sent you the WLS51 stuff. heres the driver again. Let me
know if any prblem with this one.
sree
"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
news:[email protected]...
If I put your mssqlserver4v70.jar file first in the classpath in the
startWebLogic script, it doesn't boot:
C:\bea\wlserver6.1>"C:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpat
h .;
.\lib\mssqlserver4v70.jar;.\lib\weblogic_sp.jar;.\lib\weblogic.jar -Dweblogi
c.Do
main=ejbbook -Dweblogic.Name=myserver "-Dbea.home=C:\bea"
"-Djava.security.polic
y==C:\bea\wlserver6.1/lib/weblogic.policy" -Dweblogic.management.password=we
blog
ic weblogic.Server
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised: java.lang.NoSuchMethodError
java.lang.NoSuchMethodError
at
weblogic.management.internal.ConfigurationMBeanImpl.<clinit>(Configur
ationMBeanImpl.java:80)
at weblogic.management.Admin.initialize(Admin.java:214)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:354)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
>
Putting it at the end doesn't work, of course.. Still uses jDriver classes
in weblogic.jar.
Did you package too many things in this .jar file? It is a lot biggerthan
4v65.jar and I see some "common" and "boot" classes in it..
-Greg
"Sree Bodapati" <[email protected]> wrote in message
news:[email protected]...
Yep QA found this problem and the fix will go into the GA. I am
attaching
a
new driver for you , please let me know if you see any problem with this
driver.
regards
sree
"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
news:[email protected]...
Problem goes away if I take the old version of the jDriver for SQL
Server
from the original beta 61 install and place it in the classpath in
front
of
the new weblogic.jar before booting.. Empty tables return empty
results
sets again, EJBs deploy, etc.
Please tell me QA found this problem and it is not going to be in theGA
release..
-Greg
"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
news:[email protected]...
I just uploaded and installed the latest pre-release build (123667).Win2K
platform.
There is something very wrong with the MS SQL Server JDBC behavior
now.
If you Select * from a table which exists but is empty, the coderaises
an
exception like:
weblogic.jdbc.mssqlserver4.TdsException: Statement.executeQuery - Noresult
sets
were produced by 'SELECT recordHandle, record, recordState FROM
JMSStore'
This is a big change. Normally JDBC returns an empty ResultSet.Cloudscape
still works fine, I havent test any other drivers yet.
This is also affecting EJB deployment -- Many beans in the examplesprovided
with the product fail to deploy with an error because of this JDBCexception
change. (Yes I'm sure the required tables are in my SQL*Server
database,
I've been running the beta for a month now).
Help!
[mssqlserver4v70.jar]

SQL Server excuteBatch() problem....

Similar Messages

Maybe you are looking for