Oracle timestamp field insert row

I created an oracle table with a timestamp data type field in it. When I test the query template that inserts the row, I set the date field with a parameter value of "19-SEP-2007 10:02:00" and it works fine.
When I set the Param value in my javascript code to the same value, I get a sql insert error telling me the column length is to long.
Does anyoen have any ideas?

BJ,
You can also use [SD] or [ED] instead of [Param.1], and set the associated StartDate or EndDate query property in the same string format as the DateFormat (default is MM/dd/yyyy HH:mm:ss). This way the datetime string will be handled by the data server properties for DatePrefix, DateSuffix, and InternalDateFormat.
SQLServer is simpler because it takes about any string that looks like a datetime wrapped with single quotes, but Oracle likes something such as TO_DATE('09/19/2007 10:02:00','MM/DD/YYYY HH24:MI:SS')
By using one of the date tokens the data server itself will take care of the replacement so something like:
INSERT INTO TABLE VALUES([SD])
will actually go to the database as:
INSERT INTO TABLE VALUES(TO_DATE('09/19/2007 10:02:00','MM/DD/YYYY HH24:MI:SS'))
The only gotcha is that you need to make sure that the DateFormat setting for the query template is how you provide the real date value. In the query template editor, select your desired date from the calendar icon and then change the dateformat drop down (notice that the start date you selected changes format accordingly).
Then if you are using html and Javascript on the client side to provide this date field to the query object it is as simple as document.APPLETNAME.getQueryObject().setStartDate(XXXX); or document.APPLETNAME.getQueryObject().setEndDate(XXXX);
An additional trick is that if you use the [ED] token and provide no values for the time settings it will default to the current time on the webserver when the query is processed. You can see this happen in an editor test by clearing out the StartDate and EndDate properties and issuing your query as: INSERT INTO TABLE VALUES([ED])
Regards,
Jeremy

Similar Messages

Oracle XE 10g - Inserted Rows visible in SQLPlus, not on web interface

Hello
I have created a table on my oracle XE database with two varchar columns, and have a couple of hundred entries I have 'inserted' using the following sql.
@C:\Oracle_XE_Testing\insert_items.sql;
INSERT INTO item_list (items, type) VALUES ('APAC ABS Auto Related', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC ABS Credit Cards', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC ABS Government', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC ABS Mixed Leases', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC ABS Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC ABS Structured Debt', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC ABS Student Loans', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC ABS Tobacco', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC ABS Unsecured Consumer Loans', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS ABCP', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Aircraft', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Auto Related', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Credit Cards', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Government', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Mixed Leases', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Structured Debt', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Student Loans', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Tobacco', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Unsecured Consumer Loans', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS ABCP', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Aircraft', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Auto Related', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Credit Cards', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Government', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Mixed Leases', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Structured Debt', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Student Loans', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Tobacco', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Unsecured Consumer Loans', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer ABS ABCP', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer ABS Aircraft', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer ABS Auto Related', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer ABS Credit Cards', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer ABS Government', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer ABS Mixed Leases', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer ABS Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer ABS Structured Debt', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer ABS Student Loans', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer ABS Tobacco', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer ABS Unsecured Consumer Loans', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CDO CDOs of CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CDO HY Loan + Bond CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CDO IG Corporate CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CDO Market Value', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CDO Multi-Issuer of Covered Bonds', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CDO Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CDO Real Estate SF CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CDO SME CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CDO Structured Finance CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CDO Trust Preferred CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CDO CDOs of CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CDO HY Loan + Bond CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CDO IG Corporate CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CDO Market Value', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CDO Multi-Issuer of Covered Bonds', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CDO Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CDO Real Estate SF CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CDO SME CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CDO Structured Finance CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CDO Trust Preferred CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CDO CDOs of CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CDO HY Loan + Bond CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CDO IG Corporate CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CDO Market Value', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CDO Multi-Issuer of Covered Bonds', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CDO Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CDO Real Estate SF CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CDO SME CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CDO Structured Finance CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CDO Trust Preferred CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CDO CDOs of CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CDO HY Loan + Bond CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CDO IG Corporate CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CDO Market Value', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CDO Multi-Issuer of Covered Bonds', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CDO Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CDO Real Estate SF CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CDO SME CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CDO Structured Finance CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CDO Trust Preferred CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer cmbs Structured Finance CDOs', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CMBS Large Loans', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CMBS Multiborrower', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CMBS Single Borrower', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC CMBS Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS Large Loans', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS Multiborrower', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS Single Borrower', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CMBS Large Loans', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CMBS Multiborrower', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CMBS Single Borrower', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CMBS Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CMBS Large Loans', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CMBS Multiborrower', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CMBS Single Borrower', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CMBS Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC RMBS AltA RMBS', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC RMBS Buy to Let', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC RMBS Non-Conforming (Non-US)', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC RMBS Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC RMBS Prime RMBS', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC RMBS Reverse Mortgage', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC RMBS Subprime/Home Equity RMBS', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS AltA RMBS', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Buy to Let', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Non-Conforming (Non-US)', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Prime RMBS', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Reverse Mortgage', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Subprime/Home Equity RMBS', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS AltA RMBS', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS Buy to Let', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS Non-Conforming (Non-US)', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS Prime RMBS', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS Reverse Mortgage', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS Subprime/Home Equity RMBS', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer RMBS AltA RMBS', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer RMBS Buy to Let', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer RMBS Non-Conforming (Non-US)', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer RMBS Other', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer RMBS Prime RMBS', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer RMBS Reverse Mortgage', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('NorthAmer RMBS Subprime/Home Equity RMBS', 'Sctr');
INSERT INTO item_list (items, type) VALUES ('APAC ABS ANZ', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC CMBS ANZ', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC RMBS ANZ', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC ABS India/SL/Pak', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC CMBS India/SL/Pak', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC RMBS India/SL/Pak', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC ABS Japan', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC CMBS Japan', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC RMBS Japan', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC ABS Non-Japan Asia', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC CMBS Non-Japan Asia', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC RMBS Non-Japan Asia', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC ABS Other', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC CMBS Other', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC RMBS Other', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('APAC CDO CDO', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Belgium', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS Belgium', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Belgium', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS France', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS France', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS France', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Germany', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS Germany', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Germany', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Greece', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS Greece', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Greece', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Ireland', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS Ireland', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Ireland', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Italy', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS Italy', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Italy', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Netherlands', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS Netherlands', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Netherlands', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Other', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS Other', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Other', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Portugal', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS Portugal', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Portugal', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS Spain', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS Spain', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS Spain', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA ABS United Kingdom', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA CMBS United Kingdom', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA RMBS United Kingdom', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('EMEA CDO CDO', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Argentina', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CMBS Argentina', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS Argentina', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Brazil', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CMBS Brazil', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS Brazil', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Colombia', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CMBS Colombia', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS Colombia', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Mexico', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CMBS Mexico', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS Mexico', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Other', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CMBS Other', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS Other', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Panama', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CMBS Panama', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS Panama', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer ABS Peru', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CMBS Peru', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer RMBS Peru', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('LatinAmer CDO CDO', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('NorthAmer ABS United States', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CMBS United States', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('NorthAmer RMBS United States', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('NorthAmer ABS Other', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CMBS Other', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('NorthAmer RMBS Other', 'Cntry');
INSERT INTO item_list (items, type) VALUES ('NorthAmer CDO CDO', 'Cntry');When I then test query this in SQLPlus with a select * I get what I expect, when I try to look at the table on the database homepage on the web though the changes are not showing. I'm baffled as to why this is.
Would anybody have any idea what I'm doing wrong?
Thank you very much,
Jon

Hi,
Put COMMIT after the last INSERT and then try again...
Regards,

Mapping util.Date to Oracle timestamp

Tuesday, March 22, 2005
I am currently experiencing difficulty in mapping a java.util.Date
field to an Oracle TIMESTAMP column.
Here's what I see. By default, Kodo maps the date field to a DATE
column. I suppose this makes sense since Oracle's date columns
have time information that resolves to the second. In this case,
the client has a business case to store subsecond resolution,
hence the desire to store the date field in an Oracle TIMESTAMP
column.
First question: how should this be done?
Here's what I've tried. I tried setting the jdbc-type extension
for the date field to "timestamp". This setting makes no
difference, and I suspect the reason is that OracleDBDictionary
has made the mapping from TIMESTAMP to DATE.
I tried setting the jdbc-sql-type extension for the date field to
"timestamp". This makes a difference only when I drop the table.
Then the schematool's refresh action creates a table with date's
field mapped to a TIMESTAMP column. I have also gone ahead and
manually altered the table to achieve the same effect.
Once the mapping is created, I see the following behavior. Kodo
has no problem reading the TIMESTAMP column and putting the info
into the date field. It also has no problem saving non-null date
values into the TIMESTAMP column. But it does have a problem
storing a null in the date field.
Second question: what is the workaround to this problem?
The the stack dump (obtained by using the JDO Tools Library
example) follows.
Thanks in advance,
David Ezzio
enter command:
--> return book
Select the book to return:
1. book [com.ysoft.jdo.book.library.Book-354] "Gone to War" checked out:
Tue Mar 22 10:38:01 EST 2005
2. book [com.ysoft.jdo.book.library.Book-356] "Gone to Work" checked
out: Tue Mar 22 10:33:58 EST 2005
3. book [com.ysoft.jdo.book.library.Book-357] "Gone Fishing" checked
out: Tue Mar 22 10:33:58 EST 2005
4. book [com.ysoft.jdo.book.library.Book-360] "Gone Sailing" checked
out: Tue Mar 22 10:33:58 EST 2005
5. book [com.ysoft.jdo.book.library.Book-355] "Gone Hunting" checked
out: Tue Mar 22 10:33:58 EST 2005
Enter selection:
--> 2
okay
enter command:
--> commit
exception caught in command
kodo.util.FatalDataStoreException: The transaction has been rolled back.
See the nested exceptions for details on the errors that occu
rred.
at
kodo.runtime.PersistenceManagerImpl.throwFlushException(PersistenceManagerImpl.java:1262)
at
kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1122)
at
kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1005)
at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:932)
at
kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:592)
at
com.ysoft.jdo.book.library.LibraryHandler.commitTransaction(LibraryHandler.java:175)
at
com.ysoft.jdo.book.library.client.CommitTransaction.execute(Library.java:279)
at
com.ysoft.jdo.book.common.console.UserInterface.execute(UserInterface.java:196)
at
com.ysoft.jdo.book.common.console.UserInterface.pumpCommands(UserInterface.java:186)
at com.ysoft.jdo.book.library.client.Library.run(Library.java:139)
at com.ysoft.jdo.book.library.client.Library.main(Library.java:104)
NestedThrowablesStackTrace:
kodo.util.DataStoreException: Invalid column type
at
kodo.jdbc.sql.DBDictionary.newDataStoreException(DBDictionary.java:3081)
at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:77)
at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:63)
at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:43)
at
kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:89)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:445)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:193)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:95)
at
kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:609)
at
kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:153)
at
kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1122)
at
kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1005)
at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:932)
at
kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:592)
at
com.ysoft.jdo.book.library.LibraryHandler.commitTransaction(LibraryHandler.java:175)
at
com.ysoft.jdo.book.library.client.CommitTransaction.execute(Library.java:279)
at
com.ysoft.jdo.book.common.console.UserInterface.execute(UserInterface.java:196)
at
com.ysoft.jdo.book.common.console.UserInterface.pumpCommands(UserInterface.java:186)
at com.ysoft.jdo.book.library.client.Library.run(Library.java:139)
at com.ysoft.jdo.book.library.client.Library.main(Library.java:104)
NestedThrowablesStackTrace:
java.sql.SQLException: Invalid column type
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at
oracle.jdbc.driver.OracleStatement.get_internal_type(OracleStatement.java:6164)
at
oracle.jdbc.driver.OraclePreparedStatement.setNull(OraclePreparedStatement.java:1316)
at
com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
at
com.solarmetric.jdbc.PoolConnection$PoolPreparedStatement.setNull(PoolConnection.java:406)
at
com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
at
com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
at
com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
at
com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.setNull(LoggingConnectionDecorato
r.java:792)
at
com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
at kodo.jdbc.sql.DBDictionary.setNull(DBDictionary.java:950)
at
kodo.jdbc.sql.OracleDictionary.setNull(OracleDictionary.java:450)
at kodo.jdbc.sql.RowImpl.toSQL(RowImpl.java:828)
at kodo.jdbc.sql.RowImpl.flush(RowImpl.java:1039)
at kodo.jdbc.sql.RowImpl.flush(RowImpl.java:975)
at
kodo.jdbc.runtime.PreparedStatementManager.flushInternal(PreparedStatementManager.java:160)
at
kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:84)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:445)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:193)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:95)
at
kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:609)
at
kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:153)
at
kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1122)
at
kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1005)
at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:932)
at
kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:592)
at
com.ysoft.jdo.book.library.LibraryHandler.commitTransaction(LibraryHandler.java:175)
at
com.ysoft.jdo.book.library.client.CommitTransaction.execute(Library.java:279)
at
com.ysoft.jdo.book.common.console.UserInterface.execute(UserInterface.java:196)
at
com.ysoft.jdo.book.common.console.UserInterface.pumpCommands(UserInterface.java:186)
at com.ysoft.jdo.book.library.client.Library.run(Library.java:139)
at com.ysoft.jdo.book.library.client.Library.main(Library.java:104)
enter command:
-->

Hi Stephen,
There are two related issues that are addressed. One, some Oracle
drivers return the wrong type (Type.OTHER) for the TIMESTAMP field.
This is true for the
9.2.0.1.0 driver that ships with 9iR2. This causes an exception when
attempting to assign a null to the date field that has been mapped to a
TIMESTAMP column. Two, all of the 9i drivers (and 10g drivers) return a
type name of "TIMESTAMP(x)" where x is the precision. This confuses
Kodo's OracleDictionary which is looking for a string without the
precision characters.
Following your suggestion, the following code fixes it just fine. It is
harmless, in that all it does is do what OracleDictionary intended but
failed to do. To use it, you must add the following property
configuration to the kodo.properties file.
kodo.jdbc.DBDictionary: xxx.jdo.FixedOracleDictionary
Without the fix, Kodo does not reassign the TIMESTAMP columns to a type
of DATE. So far as I can tell, as long as the driver returns a
Types.TIMESTAMP this does not cause a failure.
This fix will be moot as soon as the bug in OracleDictionary is fixed.
What I wonder about is why does Kodo reassign type TIMESTAMP to DATE?
Why don't you treat TIMESTAMP types as TIMESTAMP types? Curious minds
want to know.
Best wishes,
David
---- code follows
package xxx.jdo;
import java.sql.*;
import kodo.jdbc.schema.*;
import kodo.jdbc.sql.*;
* Some Oracle drivers do not return the correct type for the TIMESTAMP
field.
* This class fixes this issue for Kodo 3.3. The problem (an exception
complaining
* about an invalid column type) appears when mapping a Java field
(Date for example) to
* an Oracle timestamp field, and only when attempting to set null on
the Java field.
public class FixedOracleDictionary
extends OracleDictionary
public Column[] getColumns (DatabaseMetaData meta, String catalog,
String schemaName, String tableName,
String columnName, Connection conn)
throws SQLException
// Let Kodo's OracleDictionary do its thing
Column[] cols = super.getColumns (meta, catalog, schemaName,
tableName,
columnName, conn);
// Catch the columns with a name of "TIMESTAMP(n)" and mark them
as DATE types.
// This is what the OracleDictionary intended to do, but was
foiled by the
// name which now has a precision.
for (int i = 0; cols != null && i < cols.length; i++)
String tName = cols.getTypeName();
if (tName != null && tName.startsWith("TIMESTAMP"))
cols[i].setType(Types.DATE);
return cols;
---- code ends
Stephen Kim wrote:
This is a bug (1111)with regards to specific combinations of Oracle 10
driver and db.
To work around the issue until the next relase, getColumns (...) in
OracleDictionary needs to be extended/modified to instead of doing a
strict equals () comparison to "TIMESTAMP", to instead do a startsWith
("TIMESTAMP")
David Ezzio wrote:
Tuesday, March 22, 2005
I am currently experiencing difficulty in mapping a java.util.Date
field to an Oracle TIMESTAMP column.
Here's what I see. By default, Kodo maps the date field to a DATE
column. I suppose this makes sense since Oracle's date columns
have time information that resolves to the second. In this case,
the client has a business case to store subsecond resolution,
hence the desire to store the date field in an Oracle TIMESTAMP
column.
First question: how should this be done?
Here's what I've tried. I tried setting the jdbc-type extension
for the date field to "timestamp". This setting makes no
difference, and I suspect the reason is that OracleDBDictionary
has made the mapping from TIMESTAMP to DATE.
I tried setting the jdbc-sql-type extension for the date field to
"timestamp". This makes a difference only when I drop the table.
Then the schematool's refresh action creates a table with date's
field mapped to a TIMESTAMP column. I have also gone ahead and
manually altered the table to achieve the same effect.
Once the mapping is created, I see the following behavior. Kodo
has no problem reading the TIMESTAMP column and putting the info
into the date field. It also has no problem saving non-null date
values into the TIMESTAMP column. But it does have a problem
storing a null in the date field.
Second question: what is the workaround to this problem?
The the stack dump (obtained by using the JDO Tools Library
example) follows.
Thanks in advance,
David Ezzio
enter command:
--> return book
Select the book to return:
1. book [com.ysoft.jdo.book.library.Book-354] "Gone to War" checked
out:
Tue Mar 22 10:38:01 EST 2005
2. book [com.ysoft.jdo.book.library.Book-356] "Gone to Work" checked
out: Tue Mar 22 10:33:58 EST 2005
3. book [com.ysoft.jdo.book.library.Book-357] "Gone Fishing" checked
out: Tue Mar 22 10:33:58 EST 2005
4. book [com.ysoft.jdo.book.library.Book-360] "Gone Sailing" checked
out: Tue Mar 22 10:33:58 EST 2005
5. book [com.ysoft.jdo.book.library.Book-355] "Gone Hunting" checked
out: Tue Mar 22 10:33:58 EST 2005
Enter selection:
--> 2
okay
enter command:
--> commit
exception caught in command
kodo.util.FatalDataStoreException: The transaction has been rolled
back. See the nested exceptions for details on the errors that occu
rred.
at
kodo.runtime.PersistenceManagerImpl.throwFlushException(PersistenceManagerImpl.java:1262)
at
kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1122)
at
kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1005)
at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:932)
at
kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:592)
at
com.ysoft.jdo.book.library.LibraryHandler.commitTransaction(LibraryHandler.java:175)
at
com.ysoft.jdo.book.library.client.CommitTransaction.execute(Library.java:279)
at
com.ysoft.jdo.book.common.console.UserInterface.execute(UserInterface.java:196)
at
com.ysoft.jdo.book.common.console.UserInterface.pumpCommands(UserInterface.java:186)
at
com.ysoft.jdo.book.library.client.Library.run(Library.java:139)
at
com.ysoft.jdo.book.library.client.Library.main(Library.java:104)
NestedThrowablesStackTrace:
kodo.util.DataStoreException: Invalid column type
at
kodo.jdbc.sql.DBDictionary.newDataStoreException(DBDictionary.java:3081)
at
kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:77)
at
kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:63)
at
kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:43)
at
kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:89)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:445)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:193)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:95)
at
kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:609)
at
kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:153)
at
kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1122)
at
kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1005)
at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:932)
at
kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:592)
at
com.ysoft.jdo.book.library.LibraryHandler.commitTransaction(LibraryHandler.java:175)
at
com.ysoft.jdo.book.library.client.CommitTransaction.execute(Library.java:279)
at
com.ysoft.jdo.book.common.console.UserInterface.execute(UserInterface.java:196)
at
com.ysoft.jdo.book.common.console.UserInterface.pumpCommands(UserInterface.java:186)
at
com.ysoft.jdo.book.library.client.Library.run(Library.java:139)
at
com.ysoft.jdo.book.library.client.Library.main(Library.java:104)
NestedThrowablesStackTrace:
java.sql.SQLException: Invalid column type
at
oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at
oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at
oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at
oracle.jdbc.driver.OracleStatement.get_internal_type(OracleStatement.java:6164)
at
oracle.jdbc.driver.OraclePreparedStatement.setNull(OraclePreparedStatement.java:1316)
at
com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
at
com.solarmetric.jdbc.PoolConnection$PoolPreparedStatement.setNull(PoolConnection.java:406)
at
com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
at
com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
at
com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
at
com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.setNull(LoggingConnectionDecorato
r.java:792)
at
com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
at kodo.jdbc.sql.DBDictionary.setNull(DBDictionary.java:950)
at
kodo.jdbc.sql.OracleDictionary.setNull(OracleDictionary.java:450)
at kodo.jdbc.sql.RowImpl.toSQL(RowImpl.java:828)
at kodo.jdbc.sql.RowImpl.flush(RowImpl.java:1039)
at kodo.jdbc.sql.RowImpl.flush(RowImpl.java:975)
at
kodo.jdbc.runtime.PreparedStatementManager.flushInternal(PreparedStatementManager.java:160)
at
kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:84)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:445)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:193)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:95)
at
kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:609)
at
kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:153)
at
kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1122)
at
kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1005)
at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:932)
at
kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:592)
at
com.ysoft.jdo.book.library.LibraryHandler.commitTransaction(LibraryHandler.java:175)
at
com.ysoft.jdo.book.library.client.CommitTransaction.execute(Library.java:279)
at
com.ysoft.jdo.book.common.console.UserInterface.execute(UserInterface.java:196)
at
com.ysoft.jdo.book.common.console.UserInterface.pumpCommands(UserInterface.java:186)
at
com.ysoft.jdo.book.library.client.Library.run(Library.java:139)
at
com.ysoft.jdo.book.library.client.Library.main(Library.java:104)
enter command:
-->

Is it possible to insert row with timestamp field without to TO_TIMESTAMP

hello
is it possible to insert row with timestamp column without using to_timestamp unction
somthing like insert into app.master values (3,333, 'inser tmstmp', 6.7, '2010-11-10 15:14', 'f','9','2010-12-22')

784633 wrote:
hello
is it possible to insert row with timestamp column without using to_timestamp unction
somthing like insert into app.master values (3,333, 'inser tmstmp', 6.7, '2010-11-10 15:14', 'f','9','2010-12-22')If you don't like the answers in your previous thread (Re: how can i set timestamp format don't expect to get different answers just because you start a new thread.

Oracle error ORA-01461when trying to insert into an ORACLE BLOB field

I am getting Oracle error ‘ORA-01461: can bind a LONG value only for insert into a LONG column' when trying to insert into an ORACLE BLOB field. The error occurs when trying to insert a large BLOB (JPG), but does not occur when inserting a small (<1K) picture BLOB.(JPG). Any ideas?
BTW, when using a SQL Server datasource using the same code.... everything works with no problems.
ORACLE version is 11.2.0.1
The ORACLE datasource is JDBC using Oracle's JDBC driver ojdbc6.jar v11.2.0.1 (I also have tried ojdbc5.jar v11.2.0.1; ojdbc5.jar v11.2.0.4; and ojdbc6.jar v11.2.0.4 with the same error result.)
Here is my code:
<cfset file_mime = Lcase(Right(postedXMLRoot.objname.XmlText, 3))>
<cfif file_mime EQ 'jpg'><cfset file_mime = 'jpeg'></cfif>
<cfset file_mime = 'data:image/' & file_mime & ';base64,'>
<cfset image64 = ImageReadBase64("#file_mime##postedXMLRoot.objbase64.XmlText#")>
<cfset ramfile = "ram://" & postedXMLRoot.objname.XmlText>
<cfimage action="write" source="#image64#" destination="#ramfile#" overwrite="true">
<cffile action="readbinary" file="#ramfile#" variable="image_bin">
<cffile action="delete" file="#ramfile#">
<cfquery name="InsertImage" datasource="#datasource#">
INSERT INTO test_images
image_blob
SELECT
<cfqueryparam value="#image_bin#" cfsqltype="CF_SQL_BLOB">
FROM dual
</cfquery>

Can't you use "alter index <shema.spatial_index_name> rebuild ONLINE" ? Thanks. I could switch to "rebuild ONLINE" and see if that helps. Are there any potential adverse effects going forward, e.g. significantly longer rebuild than not using the ONLINE keyword, etc? Also wondering if spatial index operations (index type = DOMAIN) obey all the typical things you'd expect with "regular" indexes, e.g. B-TREE, etc.

CMP 2 non mandatory timestamp field in Oracle 9 release 2

Dears,
My machine holds the following:
Win XP pro SP 1
Oracle 9i release 2 DB
Jbuilder X enterprise Edition with SUN ONE App Server plugin
SUN ONE Application server platform edition update 2
They are all in the same machine (so there is no problem as issue 4707531 of using different Oracle drivers)
I connect using OCI not thin.
I got the following problem when trying to test my Session EJB that calls CMP.
SEVERE ( 4716): EJB5071: Some remote or transactional roll back exception occurredcom.sun.jdo.api.persistence.support.JDODataStoreException: Got a JDBC SQLException.
Please read the remaining error stack for more information.
NestedException: java.sql.SQLException: Invalid column typeBy tracing the problem I noticed that my code works fine if I set a timestamp field in this table, this timestamp is not mandatory.
Is it a bug in SUN ONE with Oracle 9i, or anyone have a solution?

Hi Ash,
Could you please verify that your .dbschmea file and table creation scripts are in sync. The easiest way to achieve this is to recapture the .dbschema file, repackage and redeploy.
Thanks,
Mitesh

Problem with Unicode and Oracle NCLOB fields

When I try to INSERT a new (N)CLOB into an Oracle database, all is fine until I use a non-ASCII character, such as an accented roman letter, like the "�" (that's '\u00E9') in "caf�" or the Euro Currency symbol "?" (that's '\u20AC' as a Java character literal, just in case the display is corrupted here too). This doesn't happen with "setString", but does happen when streaming characters to the CLOB; however, as Oracle or the driver refuse strings larger than 4000 characters, and as I need to support all the above symbols (and many more), I'm stuck.
Here's the background to the problem (I've tried to be detailed, after a lot of looking around on the web, I've seen lots of people with similar problems, but no solutions: I've seen and been able to stream ASCII clobs, or add small NCHAR strings, but not stream NCLOBs...).
I'm using Oracle 9.2.0.1.0 with the "thin" JDBC driver, on a Windows box (XP Pro). My database instance is set up with AL32UTF8 as the database encoding, and UTF8 as the national character set.. I've created a simple user/schema, called LOBTEST, in which I created two tables (see below).
The basic problems are :
- with Oracle and JDBC, you can't set the value of a CLOB or NCLOB with PreparedStatement's setString or setCharacterStream methods (as it throws an exception when you send more than 4000 characters)
- with Oracle, you can only have one LONG VARCHAR-type field per table (according to their documentation) and you MUST read all columns in a set order (amongst other limitations).
- with a SQL INSERT command, there's no way to set the value of a parameter that's a CLOB (implementations of the CLOB interface can only be obtained by performing a SELECT.... but obviously, when I'm inserting, the record doesn't exist yet...). Workarounds include (possibly) JDBC 4 (doesn't exist yet...) or doing the following Oracle-specific stuff :
INSERT INTO MyTable (theID,theCLOB) VALUES (1, empty_clob());
SELECT * FROM MyTable WHERE theId = 1;
...and getting the empty CLOB back (via a ResultSet), and populating it. I have a very large application, that's deployed for many of our customers using SapDB and MySQL without a hitch, with "one-step" INSERTS; I can't feasibly change the application into "three-step INSERT-SELECT-UPDATE" just for Oracle, and I shouldn't need to!!!
The final workaround is to use Oracle-specific classes, described in:
http://download-east.oracle.com/otn_hosted_doc/jdeveloper/904preview/jdbc-javadoc/index.html
...such as CLOB (see my example). This works fine until I add some non-ASCII characters, at which point, irrespective of whether the CLOB data is 2 characters or 2 million characters, it throws the same exception:
java.io.IOException: Il n'y a plus de donn?es ? lire dans le socket
     at oracle.jdbc.dbaccess.DBError.SQLToIOException(DBError.java:716)
     at oracle.jdbc.driver.OracleClobWriter.flushBuffer(OracleClobWriter.java:270)
     at oracle.jdbc.driver.OracleClobWriter.flush(OracleClobWriter.java:204)
     at scratchpad.InsertOracleClobExample.main(InsertOracleClobExample.java:61)...where the error message in English is "No more data to read from socket". I need the Oracle-specific "setFormOfUse" method to force it to correctly use the encoding of the NCLOB field, without it, even plain ASCII data is rejected with an exception indicating that the character set is inappropriate. With a plain CLOB, I don't need it, but the plain CLOB refuses my non-ASCII data anyway.
So, many many thanks in advance for any advice. The remainder of my post includes my code example and a simple SQL script to create the table(s). You can mess around with the source code to test various combinations.
Thanks,
Chris B.
CREATE TABLE NCLOBTEST (
     ID         INTEGER NOT NULL,
     SOMESTRING NCLOB,
     PRIMARY KEY (ID)
CREATE TABLE CLOBTEST (
     ID         INTEGER NOT NULL,
     SOMESTRING CLOB,
     PRIMARY KEY (ID)
package scratchpad;
import java.io.Writer;
import java.sql.Connection;
import java.sql.Driver;
import java.sql.PreparedStatement;
import java.sql.SQLException;
import java.util.Properties;
import oracle.jdbc.driver.OracleDriver;
import oracle.jdbc.driver.OraclePreparedStatement;
import oracle.sql.CLOB;
public class InsertOracleClobExample
     public static void main(String[] args)
          Properties jdbcProperties = new Properties();
          jdbcProperties.setProperty( "user", "LOBTEST" );
          jdbcProperties.setProperty( "password", "LOBTEST" );
//          jdbcProperties.setProperty("oracle.jdbc.defaultNChar","true");
          Driver jdbcDriver = new OracleDriver();
          PreparedStatement pstmt = null;
          Connection connection = null;
          String tableName = "NCLOBTEST";
          CLOB clob = null;
          try
               connection = jdbcDriver.connect("jdbc:oracle:thin:@terre:1521:orcl", jdbcProperties);
               pstmt = connection.prepareStatement("DELETE FROM NCLOBTEST");
               pstmt.executeUpdate();
               pstmt.close();
               pstmt = connection.prepareStatement(
                    "INSERT INTO "+tableName+" (ID,SOMESTRING) VALUES (?,?);"
               clob = CLOB.createTemporary(pstmt.getConnection(), true, CLOB.DURATION_SESSION);
               clob.open(CLOB.MODE_READWRITE);
               Writer clobWriter = clob.getCharacterOutputStream();
               clobWriter.write("Caf? 4,90? TTC");
               clobWriter.flush();
               clobWriter.close();
               clob.close();
               OraclePreparedStatement opstmt = (OraclePreparedStatement)pstmt;
               opstmt.setInt(1,1);
               opstmt.setFormOfUse(2, OraclePreparedStatement.FORM_NCHAR);
               opstmt.setCLOB(2, clob);
               System.err.println("Rows affected: "+opstmt.executeUpdate());
          catch (Exception sqlex)
               sqlex.printStackTrace();
               try     {
                    clob.freeTemporary();
               } catch (SQLException e) {
                    System.err.println("Cannot free temporary CLOB: "+e.getMessage());
          try { pstmt.close(); } catch(SQLException sqlex) {}
          try { connection.close(); } catch(SQLException sqlex) {}
}

The solution to this is to use a third-party driver. Oranxo works really well.
- Chris

PK with TIMESTAMP causes insert unique constraint error at DST switch

Hi,
I have a test that inserts rows in a table that has a TIMESTAMP in its PK.
When inserting rows that cross over the November DST change, it tries to insert these dates:
--- Sun Nov 02 02:00:00 EST 2008
--- Sun Nov 02 01:00:00 EST 2008
--- Sun Nov 02 01:00:00 EDT 2008
This is the output of 3 different UTC dates. We can see that there are 2 x 1am, but they differ in their DST. They are really 3 different UTC dates.
But I get this error:
--- Expected error: ORA-00001: unique constraint (DDLTEST1.SYS_C00142622) violated
But I can get around that error and can insert these same dates if I set my JVM to UTC. The inserts work so I suspect this to be a JDBC issue.
I am using the Oracle Thin driver in a spring app:
<property name="driverClassName" value="oracle.jdbc.driver.OracleDriver" />
<property name="url" value="jdbc:oracle:thin:@localhost:db" />
I can post the sample code but wonder if there is an obvious answer to this.
Note that MySql had the same problem. I fixed it by specifying the UTC timezone in the connection string, like this:
jdbc:mysql://[host]/[db]?useLegacyDatetimeCode=false&useTimezone=true&sessionVariables=time_zone='UTC'
Any idea how to get around that problem without setting JVM to UTC ?
Claude
Edited by: user2678899 on 10 juin 2009 10:09
I removed #2 work around which was wrong
Edited by: user2678899 on 10 juin 2009 10:23

Timur Akhmadeev wrote:
Hi,
I suspect this to be a JDBC issue.Nope, this is your schema design gap. It breaks the main principle of PK: to uniquely identify a row in a table always. Your PK doesn't satisfy it, since it depends on client's settings.Why is setting the JVM to UTC working ? This is the part that confuses me.
I create the 3 dates in Eastern time, then change the JVM default to UTC: the 3 inserts work.
I create the 3 dates in Eastern time, then leave the JVM to Eastern time , the 3rd insert gets the unique constraint error.
To me, the PK principle is not broken: these are 3 different UTC dates.

Insert row into database table via dynamic form -

I have developed a portlet via Portal. I used a dynamic page. I replaced the default "<ORACLE>select * from scott.emp</ORACLE>" text to call a package procedure that uses HTP.P to render the web page. My goal is to show all rows in a table and allow edits to any row, and also add a checkbox on each row to allow the user to mark for delete. I am successfully using a FOR loop and showing all of the data in a grid. My problem - How do I update and delete the data? I have a submit button with nothing behind it currently. I would ideally like to use pl/sql code to do the updates and/or deletes as marked on the page by the user, but I'm not sure how to hook the submit button to calling a procedure to execute the updates/deletes.
Any help would be appreciated -
Thanks -
Kent

Hi Patrick - Thanks for your response! I have browsed your page quickly - very informative and I will look in more detail. My form design looks as below (using a simple example with emp id and emp name columns) - perhaps this will have to change, but I wanted the user to be able to insert using html fields id_add and name_add, then update (or mark for deletion) any of the existing rows (they are rendered with for loop in pl/sql - eg, id_1/name_1, id_2/name_2, etc for each row in the table). I was hoping the submit action would call a pl/sql that would look at all rows, and then act if an update or delete were required. This makes it difficult to use parms, I believe - I may be able to change the design to show an "update row" below the current "insert row" so that, as in your example, when the user highlights a row, it populates in the update area where changes can be made, and an update button used to effect the changes to a single row at a time.
Thanks again, I appreciate your input!
Kent
______________ _________________ <insert_button>
Emp Id (textbox) Emp Name (textbox) Del_Checkbox
______________ _________________ ___ <SUBMIT_BUTTON>
------------------------- ----------------------------- ------

Import Wizard with timestamp fields

Hi there,
I'm trying to copy data with time stamp from one server to another, but I'm keep getting the following error.
Error 0xc0202048: Data Flow Task: Attempting insertion into the row version column "TimeStamp". Cannot insert into a row version column.
(SQL Server Import and Export Wizard)
Is there anyway I can deselect the timestamp field when I run the wizard?
How can I successfully transfer the data?
Thanks
regards,
Mike

Hi, I'm having the same issue even with the On Error column set to 'ignore" in the Data Type Mapping review screen.
I've also seen in the Conversion Details the comment about timestamp vs VarChar, but if I uncheck the Convert column I am unable to run the import.
There must be a way to overcome this?
Thanks
Validating (Error)
Messages
Error 0xc0202048: Data Flow Task 1: Attempting insertion into the row version column "TimeStamp". Cannot insert into a row version column.
(SQL Server Import and Export Wizard)
Error 0xc0202045: Data Flow Task 1: Column metadata validation failed.
(SQL Server Import and Export Wizard)
Error 0xc004706b: Data Flow Task 1: "component "Destination - SorContractPrice" (92)" failed validation and returned validation status "VS_ISBROKEN".
(SQL Server Import and Export Wizard)
Error 0xc004700c: Data Flow Task 1: One or more component failed validation.
(SQL Server Import and Export Wizard)
Error 0xc0024107: Data Flow Task 1: There were errors during task validation.
(SQL Server Import and Export Wizard)
[Source Information]
Source Location : E:\SYSPRO61\Temp\METSUPL.xls
Source Provider : Microsoft.Jet.OLEDB.4.0
Table: `METSUPL$`
Column: TimeStamp
Column Type: VarChar
SSIS Type: Unicode string [DT_WSTR]
Mapping file (to SSIS type): C:\Program Files (x86)\Microsoft SQL Server\100\DTS\MappingFiles\JetToSSIS.xml
[Destination Information]
Destination Location : siwerp
Destination Provider : SQLNCLI10
Table: [dbo].[SorContractPrice]
Column: TimeStamp
Column Type: timestamp
SSIS Type: byte stream [DT_BYTES]
Mapping file (to SSIS type): C:\Program Files (x86)\Microsoft SQL Server\100\DTS\MappingFiles\MSSQLToSSIS10.XML
[Conversion Steps]
Step 1: DT_WSTR to DT_BYTES
SSIS conversion file: C:\Program Files (x86)\Microsoft SQL Server\100\DTS\binn\DtwTypeConversion.xml

Adding a timestamp field to a table (MySQL database)

I've defined a field in a MySQL table as type 'timestamp'
eg. 2010-05-25 21:36:19
When I perform an insert using coldfusion, the row doesn't change the value in the timestamp automatically
Am I better creating my own timestamp field, type varchar and manually insert my timestamp values ?

No, it is a pretty bad idea to use a text field to store date-time information. It makes it much harder to do date and|or time calculations on the data.
A timestamp field does not mean you have a field that automatically inserts a timestamp on record insert and|or update. Just that you have a field that expects a 'timestamp' value which is usually a date-time value down to the millisecond precision.
You can set up the database to automatically create this value when data is inserted and|or updated, but that is more then just creating the timestamp field. And the specifics will change depending on your exact database management system. Searching the internets for information on your database managerment system of choice and auto and|or default values for fields should guide you in the correct direction.
Or you can insert timestamp data along with the other data you are inputting into the database. The now() function combined with the <cfqueryparam value="#timeData#" cfsqltype="cf_sql_timestamp"> is a useful combination to do this.

JPA @Version annotation with Timestamp and insert

Hi. I have the @Version annotation specified on a Timestamp field of my entity. The versioning works correctly as long as the Date is populated in the database, but when I insert an entity, I get a StaleObjectException. After some research, I found several references saying that the @Version attribute should not be set manually. So my question is: Does the @Version annotation initialize a Timestamp on insert by default, or is there some other annotation (eg - @Temporal or something) that has an attribute that specifies a default value on insert?
Thanks for your time.

Timur Akhmadeev wrote:
Hi,
I suspect this to be a JDBC issue.Nope, this is your schema design gap. It breaks the main principle of PK: to uniquely identify a row in a table always. Your PK doesn't satisfy it, since it depends on client's settings.Why is setting the JVM to UTC working ? This is the part that confuses me.
I create the 3 dates in Eastern time, then change the JVM default to UTC: the 3 inserts work.
I create the 3 dates in Eastern time, then leave the JVM to Eastern time , the 3rd insert gets the unique constraint error.
To me, the PK principle is not broken: these are 3 different UTC dates.

Working with TIMESTAMP fields in Excel

Please forgive me if this is a really stupid question.
I have an Oracle 10g dtabase that i am trying to connect to via ODBC in Excel.
I can get data from tables into MS Query untill i try and insert a TIMESTAMP field when all fails. The TIMESTAMP field ahave a time zone on them.
Can anyone point me in the direction of an ODBC driver which works in this situation, i have tried the standard MS driver and also the ODBC driver supplied by ORACLE.
Thanks in advance for any help.

It would be interesting to know your ODBC driver version.
Basic TIMESTAMP is supposed to be supported but TIMESTAMP WITH TIME ZONE,
TIMESTAMP WITH LOCAL TIME ZONE are not supported.
Do you get the error ORA-932 inconsistant datatypes or another error when you select your Oracle table?
So far as I remember, you can download the ODBC driver from DataDirect :
http://www.datadirect.com/products/odbc/index.ssp
The Datadirect driver seems to handle Timestamp with Time Zone.
Please try with this one and let me know your feedback.
Regards
Mireille

How to retrieve the last inserted row

This may be a question with a very known answer but I couldn't find any within this forum.
What is the proper way to retrieve the just inserted record ?
I'm accessing the DB from external Java and at this moment I use a timestamp column in order to retrieve the inserted row. So I generate an unique timestamp ('20020615184524356') which I inserted during the insert operation. I retrieve the just inserted row using "select * from fooTable where(timestamp='20020615184524356')".
Is this the general idea or am I totally wrong ?

hi Shaik Khaleel,
Just wanted to clarify my doubts regarding rowid.
Please refer the subject as "abt rowid" in previous posting and ur reply for that was
"its an unique number throughout the database, its an hexadecimal number. it assigns the rowid of the deleted row in future , but not to the immediate insertation row."
As u have mentioned the rowid of the deleted row can be assigned to a new row in future,
wont the following query fail.
select * from temp where rowid=(select max(rowid) from temp); -- in oracle. ~chandru

Not able to insert row programticaly

hi am trying to insert row to another viewObject from another viewobject programaticaly ,can somebody help me,i have recreate the problem i upload it in hostfile,am in jdeveloper 11.1.1.6.0
am geting this log error
Caused by: oracle.jbo.InvalidOwnerException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-25030. Error message parameters are {0=UamUserdetails, 1=oracle.jbo.Key[marksn ]}
     at oracle.jbo.server.EntityImpl.internalCreate(EntityImpl.java:1341)
     at oracle.jbo.server.EntityImpl.create(EntityImpl.java:1020)
     at oracle.jbo.server.EntityImpl.callCreate(EntityImpl.java:1197)
     at oracle.jbo.server.ViewRowStorage.create(ViewRowStorage.java:1152)
     at oracle.jbo.server.ViewRowImpl.create(ViewRowImpl.java:498)
     at oracle.jbo.server.ViewRowImpl.callCreate(ViewRowImpl.java:515)
     at oracle.jbo.server.ViewObjectImpl.createInstance(ViewObjectImpl.java:5714)
     at oracle.jbo.server.QueryCollection.createRowWithEntities(QueryCollection.java:1993)
     at oracle.jbo.server.ViewRowSetImpl.createRowWithEntities(ViewRowSetImpl.java:2492)
     at oracle.jbo.server.ViewRowSetImpl.doCreateAndInitRow(ViewRowSetImpl.java:2533)
     at oracle.jbo.server.ViewRowSetImpl.createAndInitRow(ViewRowSetImpl.java:2498)
     at oracle.jbo.server.ViewObjectImpl.createAndInitRow(ViewObjectImpl.java:11042)
     at worklis.view.beantest.addnew(beantest.java:138)
     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:597)
     at com.sun.el.parser.AstValue.invoke(Unknown Source)
     at com.sun.el.MethodExpressionImpl.invoke(Unknown Source)
     at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53)
     at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256)
     at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
     at org.apache.myfaces.trinidad.component.UIXCollection.broadcast(UIXCollection.java:148)
     at org.apache.myfaces.trinidad.component.UIXTable.broadcast(UIXTable.java:279)
     at oracle.adf.view.rich.component.UIXTable.broadcast(UIXTable.java:145)
     at oracle.adf.view.rich.component.rich.data.RichTable.broadcast(RichTable.java:402)
     at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:148)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:1018)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:386)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:194)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)Edited by: adf009 on 2013/02/15 4:43 PM
Edited by: adf009 on 2013/02/15 4:57 PM
Edited by: adf009 on 2013/02/15 7:22 PM

the code am using is below
    public void addnew(ActionEvent actionEvent) {
        // Add event code here...
        // Add event code here...
        //Code to get the bindings for TargetVO :
        Map<Object,String> mp=new HashMap<Object, String>();
                DCBindingContainer bindings2 =
                   (DCBindingContainer)BindingContext.getCurrent().getCurrentBindingsEntry();
               JUCtrlHierBinding obj = (JUCtrlHierBinding)bindings2.findCtrlBinding("UamUserdetailsView2");
               ViewObject targetVO = obj.getViewObject();
          DCBindingContainer bindings =
                   (DCBindingContainer)BindingContext.getCurrent().getCurrentBindingsEntry();
               DCIteratorBinding empIter =
                   bindings.findIteratorBinding("DeltTable1Iterator");
        //SourceVO1Iterator is the iterator under Executables section for the SourceVO1 bindings.
        RowSetIterator roleRSIters = empIter.getRowSetIterator();
        RowSetIterator rs1 = roleRSIters.getRowSet().getViewObject().createRowSetIterator(null);
        rs1.first();
               NameValuePairs nvp = null;
               String username = null;
        while (rs1.hasNext()) {
                           Row r = rs1.next();
                   nvp = new NameValuePairs();
                  // nvp.setAttribute("organisationid", r.getAttribute("organisationid"));
                   nvp.setAttribute("Organisationid", getorgid());
                   System.out.println("printedorgid" +getorgid());
                   nvp.setAttribute("Username",r.getAttribute("Username"));
                   nvp.setAttribute("Username1",r.getAttribute("Username"));
                   nvp.setAttribute("Firstname",r.getAttribute("Firstname"));
                   nvp.setAttribute("Surname",r.getAttribute("Surname"));
                   nvp.setAttribute("Emailaddress",r.getAttribute("Emailaddress"));
                   // username = (String)r.getAttribute("Username");
                   System.out.println("prininstead " + nvp);
                 // targetVO.createAndInitRow(nvp);
                    r = targetVO.createAndInitRow(nvp);
                    targetVO.insertRow(r);
                    //createAndInitRow(AttributeList nvp);
        //Row row = targetVO.createAndInitRow(nvp);
          //      targetVO.insertRow(row);
               rs1.closeRowSetIterator();
               targetVO.getApplicationModule().getTransaction().commit();
    }i have re-created the problem i upload in this hostfile,you can have the whole picture of what am trying to do
http://www.4shared.com/zip/RaZ07PWS/createRow.html
Edited by: adf009 on 2013/02/15 7:36 PM
Edited by: adf009 on 2013/02/15 7:38 PM
Edited by: adf009 on 2013/02/15 8:01 PM

Oracle timestamp field insert row

Similar Messages

Maybe you are looking for