Problem with updateRow() of resultset

When using JDBC-ODBC bridge accessing MS SQL Server 8.0.
I issue the rs.updateRow(), and receive the following error:
class java.sql.SQLException [Microsoft][ODBC SQL Server
Driver]Invalid attribute/option identifier
Any one out there have an idea ???
Jagpate

Hi Rolandpish:
I'm using the following on Windows XP Pro:
Product : Microsoft SQL Server, Version : Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
           Dec 17 2002 14:22:05
           Copyright (c) 1988-2003 Microsoft Corporation
           Enterprise Evaluation Edition on Windows NT 5.1 (Build 2600: Service Pack 1)
Driver : SQLServer, Version : 2.2.0029I haven't been able to get ResultSet.CONCUR_UPDATABLE.... how did you managed to get that accomplished (pls don't tell me it's because I'm using an Evaluation Edition).
;o)
V.V.

Similar Messages

[Execute SQL Task] Error: Executing the query "DECLARE_@XMLA nvarchar(3000) ,__@DateSerial nvarch..." failed with the following error: "Incorrect syntax near '-'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly,

Hi
DECLARE @XMLA nvarchar(3000)
, @DateSerial nvarchar(35);
-- Change date to format YYYYMMDDHHMMSS
SET @DateSerial = CAST(GETDATE() AS DATE);
--SELECT @DateSerial
Set @XMLA =
N' <Batch xmlns="http://schemas.microsoft.com/analysis services/2003/engine">
<ErrorConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2"
xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xmlns:ddl100_100="http://schemas.microsoft.com/analysisservices/2008/engine/100/100" xmlns:ddl200="http://schemas.microsoft.com/analysisservices/2010/engine/200"
xmlns:ddl200_200="http://schemas.microsoft.com/analysisservices/2010/engine/200/200">
<KeyErrorLimit>-1</KeyErrorLimit>
<KeyNotFound>IgnoreError</KeyNotFound>
<NullKeyNotAllowed>IgnoreError</NullKeyNotAllowed>
</ErrorConfiguration>
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2"
xmlns:ddl100_100="http://schemas.microsoft.com/analysisservices/2008/engine/100/100" xmlns:ddl200="http://schemas.microsoft.com/analysisservices/2010/engine/200" xmlns:ddl200_200="http://schemas.microsoft.com/analysisservices/2010/engine/200/200"
xmlns:ddl300="http://schemas.microsoft.com/analysisservices/2011/engine/300" xmlns:ddl300_300="http://schemas.microsoft.com/analysisservices/2011/engine/300/300">
<Object>
<DatabaseID>MultidimensionalProject5</DatabaseID>
<CubeID>giri</CubeID>
<MeasureGroupID>Fact Internet Sales</MeasureGroupID>
</Object>
<Type>ProcessFull</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>';
EXEC (@XMLA) At SHALL-PCAdventureWorksDw ;
iam executive the query when iam getting below error.
[Execute SQL Task] Error: Executing the query "DECLARE
@XMLA nvarchar(3000)
, @DateSerial nvarch..." failed with the following error: "Incorrect syntax near '-'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set
correctly, or connection not established correctly.
how to solve this error;
please help me

What are you trying to do? What sort of data source is SHALL-PCAdventureWorksDw?
When you use EXEC() AT, I would execpt to see an SQL string to be passed to EXEC(), but you are passing an XML string????
If you explain why you think this would work in the first place, maybe we can help you.
Erland Sommarskog, SQL Server MVP, [email protected]

: "Invalid object name '#Temp'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Hi   .
    I was creating the pass the values t in temp tables though s sis package vs2012 .
  First I was taken on executive SQL TASK.
IN EXCUTIVE SQL TASK . I was write the stored proce:
Sp;
reate procedure USP_GETEMP2333
AS
begin
Select eid,ename,dept,salary from emp
end;
create table #temp(eid int,ename varchar(20),dept varchar(20),salary int)
insert into #temp
   exec USP_GETMP02333
   go.
It was executive correctly.
I was taken another sequence container. In the sequence container iam creating one   executive sql
In 2<sup>nd</sup> excutive sql task: sql statements is
if object_id('emp_fact_sal') is not null
drop table emp_fact_sal
select eid,ename as emp_name,sal_bar=
case when salary<=5000 then 'l'
when salary >5000 and salary<=7000 then 'm'
else
'h'
end
into emp_fact_sal from #temp.
and one falt flies it was taken to designation .
iam changing all connection properties:
in oldeb connection:
in excutive sal task properties .
delay validation is true,
and retain connection maner is also true,
and package mode is 64 bit is false.
But iwas excutive in 2<sup>nd</sup> excutive ql task .
Iam getting this type of errors,
                [Execute SQL Task] Error: Executing the query " if object_id('emp_fact_sal') is not null
drop ta..." failed with the following error: "Invalid object name '#Temp'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established
correctly.
Please help me

Arthur suggestion works but you shouldnt even be doing this on a SQL Task.
Use a data flow task. You'll have better control over the data that is being transfered and get better performance because no staging table will be used.
Just because there are clouds in the sky it doesn't mean it isn't blue. But someone will come and argue that in addition to clouds, birds, airplanes, pollution, sunsets, daltonism and nuclear bombs, all adding different colours to the sky, this
is an undocumented behavior and should not be relied upon.

Problem with GenericCatalogDAO JDBC Resultset using parameters not working

Hello
I have a problem with Petstore GenericCatalogDAO. java. The problem is the behaviour of the resultset object when retrieving data from the database.Below are two synareos one that
works (when) hard coded and one that does not work when parameter values passed into the the result set.
1. The code the WORKS.
statement = connection.prepareStatement("select a.productid , name, descn from product a, product_details b
where a.productid = b.productid and locale= 'en_US' and a.catid = 'FISH' order by name"
,ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ_ONLY);
resultSet = statement.executeQuery();
resultSet.absolute(1);
String s = resultSet.getString(1);
The code that gives me a 'exhausted resultset' error which I think means no results
String[] parameterValues = new String[] { locale.toString(), categoryID };(For example parameters are 'en_US' and 'FISH')
statement = connection.prepareStatement("select a.productid , name, descn from product a, product_details b
where a.productid = b.productid and locale=? and a.catid =? order by name"
,ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ_ONLY);
for (int i = 0; i < parameterValues.length; i++) {
statement.setString(i + 1, parameterValues[i]);
resultSet = statement.executeQuery();
resultSet.absolute(1);
String s = resultSet.getString(1);
There is obviously a problem using these named parametevalues with these preparedstatement resultset, Does anybody know anything about this and a fix for it????
Cheers. Roger

Which version of PetStore are you using?
-Larry

Problem with a Date

Hello:
I have a problem with the following:
ResultSet r= s.executeQuery("Select sysdate from dual");
String myDate=DateFormat.getDateTimeInstance().format(r.getDate(1));
The result is a string like "07/05/2002 00:00:00". The time information is always 00:00:00, and I need the correct time information.
I'm using Oracle 8i. �What's wrong?
Thks.

r.getDate(1)Try r.getTimestamp(1).

Problem with ResultSet in a loop

hi,
i have a probleme with ResultSet when, my code is bellow
ResultSet rs = stmt.executeQuery(sql);
sql="SELECT NAME FROM prestationtemp";
rs = stmt.executeQuery(sql);
String sqlDel="";
while (rs.next())
sqlDel="Delete from prestation where NAME="+rs.getString("NAME");
stmt.executeQuery(sqlDel);
the problem is that the loop iterate just once like if there is just one record, and if I remove stmt.executeQuery(sqlDel); from the loop it iterate normaly.
thanks in advance.

you will need to use 2 Statments e.g.
Statement stmt1 = connection.createStatement();
Statement stmt2 = connection.createStatement();
ResultSet rs = stmt.executeQuery(sql);
sql="SELECT NAME FROM prestationtemp";
rs = stmt1.executeQuery(sql);
String sqlDel="";
while (rs.next())
sqlDel="Delete from prestation where NAME="+rs.getString("NAME");
stmt2.executeQuery(sqlDel);
} When you reuse a Statement, any resultsets previously created are automatically closed.
Looking at your code, it seems that you only need 1 SQL call:
Delete from prestation where NAME in (SELECT NAME FROM prestationtemp)
Much more efficient!

Problem with different resultset with same data and same query in Oracle 8.1.7 and 9i

Hello,
I have been using this query in oracle 8.1.7
SELECT
ID,
AREA_NO
FROM MANAGER_AREA MGR
WHERE COMPANY_ID = :id AND
(:value < (SELECT COUNT(ROWID)
FROM MANAGER_WORK MW
WHERE MW.AREA_ID = MGR.ID AND
(MW.END_WORK IS NULL OR MW.END_WORK >= SYSDATE)))
order by AREA_NO;
In the above query I want to see rows from MANAGER_AREA table depending upon date criteria in the table MANAGER_WORK and also upon the parameter :value i.e if I pass a value as 0 I get to see records for which their is atleast 1 record in MANAGER_WORK with the date criteria and if I pass -1 then I get all the records because minimum value that count(*) would give is 0. The resultset was as expected in 8.1.7.
A couple of days back I installed PERSONAL 9i to test for testing the basic functionality of our program with the same data. This query fails and irrespective whether I pass -1 or 0 it returns me same dataset which I would have got in case if I pass 0.
I do not know whether this is a bug that has got introduced in 9i. Can anybody help me with this problem. It would be difficult for me to change the parameter send to this query as the Query is called from many different places.
Thanks in advance
Amol.

I cannot use a Group by and a having statement over here. The problem with 'Group by' and 'having' clause is If I have to make a join between the two tables. When I use join then I get only rows that are linked to each other in the table.
If I use outer join to solve that problem then I have to take in consideration the other date condition. My previous query use to virtually discard the corelated query result by using -1 as the value. This will not happen in the join query.
Amol.

Problem with Updateable ResultSet

Hi,
I'm having a problem updating an updateable resultset. When I query the database using anything other than the LIKE clause, I can update the resultset just fine. As soon as I add the LIKE clause to my select query and then try to update one of the records in the resultset I get an "Error in row". The database I am using is MS Access (yes I know, not a good choice), and I am using the driver that comes built into Java. I am also running JDK 1.5_06.
I've looked to see if maybe this is a known bug, but haven't found anything related to this. Has anyone else seen this same problem? Or know of a way to get around it?
Thank you in advance.

I'm confused then... Why would I be able to update
the resultset when I select that resultset not using
the LIKE clause, but when I use the LIKE clause to
get the resultset and then try to update it in some
way, I get an error. Because the database isn't giving you an updatable cursor if you use a like apparently. It just isn't. Don't know why.
Obviously the resultset is
updateable, Obviously not.
and I have selected the right cursor type
for each parameter (TYPE_SCROLL_INSENSITIVE and
CONCUR_UPDATABALE). I am sure you are but what you ask for is not always what you get.
I understand that it is not
required for the database and/or driver to fulfill my
wishes, but it seems odd Yes it does seem a bit odd but that doesn't make it less true. To be frank with you I can't remember the last time I used an updatable result set.
It's one of these things that seem all nifty at first but it's all very quirky and resource intensive and in almost all cases was better handled by an INSERT, UPDATE or DELETE statement in the first place.
that it I am able to update
the resultset when I have not used the LIKE clause to
create it, but am unable to update it when having
created it using the LIKE clause. :shrug: Because. I couldn't tell you why it does it this way. I am sure it has something to do with how it builds the cursor... generally in MS database stuff there are dynamic and static (or fixed I can't remember the names) "keysets" for a given result set. I am mangling the terminolgy here but it doesn't really matter... the point is with MS databases the way you search combined with any clauses combined with what fields you select all effect the ending cursor types you can have. This is true for most databases really... and to make a long story short I guess that a LIKE is just making the backing keyset or whatever non updatable.
I'll try your tip
of listing all of the columns instead of using * to
see if that makes a difference.It might but don't get your hopes up.
This is a general tip you can use to try and get an updatable cursor but honestly in your case I am not sure it will help. It seems to me that you are going to have to not use LIKE.
Which means you can either give up the updatable cursor OR the like. If you have to have an updatable cursor AND the LIKE then you are going to have to do this in two steps.
Query 1 - Select the keys by LIKE
Query 2 - Select updatable cursor using the keys from query 1
But that seems terribly painful.

JDBC Resultset Problem with ORACLE 10.1.0.2

Hello
I have a problem with Petstore GenericCatalogDAO. java. The problem is the behaviour of the resultset object when retrieving data from the database.Below are two synareos one that
works (when) hard coded and one that does not work when parameter values passed into the the result set.
1. The code the WORKS.
statement = connection.prepareStatement("select name from employee where a.name ='SMITH' order by name"
,ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ_ONLY);
resultSet = statement.executeQuery();
resultSet.absolute(1);
String s = resultSet.getString(1);
The code that gives me a 'exhausted resultset' error which I think means no results
String[] parameterValues = new String[] { "SMITH" };
statement = connection.prepareStatement("select name from employee where a.name =? order by name ",
ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ_ONLY);
for (int i = 0; i < parameterValues.length; i++) {
statement.setString(i + 1, parameterValues);
resultSet = statement.executeQuery();
resultSet.absolute(1);
String s = resultSet.getString(1);
There is obviously a problem using these named parametevalues with these preparedstatement resultset, Does anybody know anything about this and a fix for it????
Cheers. Roger

Roger,
It's probably a mistake you made when posting your code, but your query string is incorrect it should be either:
select name from employee where name = 'SMITH' order by nameor
select a.name from employee a where a.name = 'SMITH' order by a.nameIn other words you have prefixed a column with a table alias but have not indicated a table alias in the query.
Also, shouldn't your code be:
for (int i = 0; i < parameterValues.length; i++) {
statement.setString(i + 1, parameterValues[ i ]);
}Or was the "[ i ]" part giving you trouble? (Since "[ i ]" -- without the spaces -- is treated as a text-formatting tag.)
While I didn't try your specific query, I have no problem using "PreparedStatment"s with parameters.
What is your environment? Mine is:
Oracle 10g (10.1.0.4) database on Linux (Red Hat)
JDK 1.4.2
ojdbc14.jar JDBC driver (latest version)
Good Luck,
Avi.

Problems with MDM 5.5 SP05 Portal Content - ResultSet iView

Hello Experts,
We are having problems with standard iViews from MDM 5.5, more specific with ResultSet iView. We created an iView using English as default browsers language but our client wanted it in Portuguese, so in the MDM Repository both languages were defined and used in MDM Data Manager, when passed to the Portal iView an error occur, but only in a ResultSet iView from the MDM Portal Content, the others iViews (itemDetails, PicklistSearch, etc...) are shown in Portuguese, and we cannot figure out why it works fine in English and not in Portuguese. We left the default language defined by clients browser. Below Im sending the LOG, which by the way, doesn't help much, but I put it also here. Any ideas of what should I do ?
LOG ERROR:
java.lang.IllegalArgumentException: unknown format type at
We are using Portal 7.0 SPS11 and MDM 5.5 SP05 - Portal Content in a Win2003/Oracle server each.

Alex,
sorry to disturb you with this issue, can you explain me basic steps in order to setup standard MDM iviews from the portal?
I mean, I have already installed all standard mdm business content, and also have configured system and aliases in the portal to connect to my mdm repositories. Those system/aliases are working propperly.
But, when I try to preview standard MDM iviews/pages I got several JAVA errors in trace logs.
Specific iviews are: Item Details, Show products, etc..any iview execution fails.
So, am I missing something?, do i have to create a specific user in portal?, assign specifi roles or groups???.
Platform is: nw2004s SR2, SP11, MDM content 5.5
Thank you in advance.

Problem with scrollable resultset of oracle

I encountered problom like this:
when I use
s=createStatement(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY);
and getString of a resultset,I get the right data.
However ,when I use
s= createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY);
and getString of a ResultSet ,
if the type of the field is Date,then get right data.
if it is char or varchar2,then i get some thing like
0x313233,
all has been found in win2000&solaris
with oracle 8.1.6
thanks a lot!

Hello,
We've got the same problem.
It comes from the National Character Set of Oracle Database.
With WE8ISO8859P1, no problem with using this parameters.
But with WE8ISO8859P9, we have some hexadecimal return.
I don't know if it's works with another Character set, but with this, It doesn't work.
We're trying to find a solution. Because change the character set is not one.
Good luck.

Problem with JDBC resultset

Hello everyone:
I'm using JDBC to connect to SQL Server, normally after executeQuery();, it should return me a opened BaseResultSet in order that i can read datas by stream(next(), getColumn(),etc...) but sometimes it returns a BaseResultSet closed. (I detected it during the debugging by checking the value of the property "closed" in the object returned ), in this case it refused all the following operations with the exceptions "ResultSet has been closed".
Does that sound normal? How to solve it ?
Thanks a lot!!!!

Did you close the underlying Statement or Connection objects? It might come back empty (e.g., next() returns false), but it should not come back already closed.
- Saish

Problems with ResultSet

I'm working with Application Server WebLogic 5.1.
In my Servlet or JSP why can't I invoke the ResultSet methods getRow, afterLast, beforeFirst
when the method next works?
My error message is:
Servlet failed with Exception java.lang.AbstractMethodError

those methods can only be used with a "scrollable" ResultSet. If your ResultSet was not created as a scrollable resultset, these methods can't be used. Another reason could be that your driver does not support the scrollable resultset. Post the statement/resultset code so that we can give you more accurate advice.
Jamie

Problem with JDBC

Hi, sorry but in other forum nobody answer my question.
the probles is using JDBC 2.0, my cod is:
Statement c = conn.createStatement();
Statement =conn.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
ResultSet rest = n.executeQuery("select * from t_prueba");
rest.last();
rest.updateBlob("C", null);
rest.updateRow();
rest.close();c.close();conn.close();
at time to execute this code, i have this error:
java.sql.SQLException: Operaci�n no v�lida para el juego de resultados de s�lo lectura: updateBlob
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:124)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:161)
at oracle.jdbc.driver.BaseResultSet.updateBlob(BaseResultSet.java:482)
at oracle.jdbc.driver.OracleResultSet.updateBlob(OracleResultSet.java:1230)
at mypackage3.Conversor.leerImagenBase64(Conversor.java:51)
at mypackage3.Conversor.main(Conversor.java:77)
why is this problem if i using ResultSet.CONCUR_UPDATABLE in my statement.
i 'm using jdeveloper 10.1.2 whith j2se 1.4.2_04
please anyone can help me please
tanks
alex

There are numerous problems with what you posted.
1) Do you mean to use updateNull and not what you are doing?
2) As mentioned why would you not do this in an UPDATE query? Even if you get this to work arbitrary moving around in a result set that you don't even need along with bad practices like SELECT * is just bad all around.
3) Further as mentioned what you are trying to do is not supported (obviously) by your driver/database etc. Just because you ASK for a scrollable updatable cursor does not mean that you get one. You ask for one but obviously that error message says that the cursor is read only. For the benefits of others it says (more or less) "invalid operation on read only result set : updateBlob"
Possibly you will have to use a forward only cursor to make it updateable... I don't know consult the Oracle docs. Or better yet don't do it this way.

Memory problems with PreparedStatements

Driver: 9.0.1 JDBC Thin
I am having memory problems using "PreparedStatement" via jdbc.
After profiling our application, we found that a large number oracle.jdbc.ttc7.TTCItem objects were being created, but not released, even though we were "closing" the ResultSets of a prepared statements.
Tracing through the application, it appears that most of these TTCItem objects are created when the statement is executed (not when prepared), therefore I would have assumed that they would be released when the ResultSet is close, but this does not seem to be the case.
We tend to have a large number of PreparedStatement objects in use (over 100, most with closed ResultSets) and find that our application is using huge amounts of memory when compared to using the same code, but closing the PreparedStatement at the same time as closing the ResultSet.
Has anyone else found similar problems? If so, does anyone have a work-around or know if this is something that Oracle is looking at fixing?
Thanks
Bruce Crosgrove

From your mail, it is not very clear:
a) whether your session is an HTTPSession or an application defined
session.
b) What is meant by saying: JSP/Servlet is growing.
However, some pointers:
a) Are there any timeouts associated with session.
b) Try to profile your code to see what is causing the memory leak.
c) Are there references to stale data in your application code.
Marilla Bax wrote:
hi,
we have some memory - problems with the WebLogic Application Server
4.5.1 on Sun Solaris
In our Customer Projects we are working with EJB's. for each customer
transaction we create a session to the weblogic application server.
now there are some urgent problems with the java process on the server.
for each session there were allocated 200 - 500 kb memory, within a day
the JSP process on our server is growing for each session and don't
reallocate the reserved memory for the old session. as a work around we
now restart the server every night.
How can we solve this problem ?? Is it a problem with the operating
system or the application server or the EJB's ?? Do you have problems
like this before ?
greetings from germany,

Problem with updateRow() of resultset

Similar Messages

Maybe you are looking for