Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff exception

Hi,
I am running a web application that connects to oracle 9i database server. I am getting the following exception whenever I access Timestamp.valueOf(object)..
java.lang.IllegalArgumentException: Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff
at java.sql.Timestamp.valueOf(Timestamp.java:160).
JDK version 1.4.
Oracle client : Oracle 10 g instant client.
Oracle server: Oracle 9i.
Can somebody help me out.
Thanks.

Hi homero,
Thanks for your inputs.
XL.DefaultDateFormat = yyyy/MM/dd hh:mm:ss z
unlike the date format mentioned in the exception (yyyy-mm-dd hh:mm:ss.fffffffff)
Moreover, yyyy-mm-dd hh:mm:ss doesnot make much sense to me; It should be yyyy-MM-dd hh:mm:ss;
I concatenated the nanoseconds precision to the formatted date string and a different exception occurred this time in system validation stage.
ERROR,02 Dec 2008 11:48:11,455,[XELLERATE.SERVER],Class/Method: tcDataObj/eventPreInsert Error :Insert permission is denied
ERROR,02 Dec 2008 11:48:11,471,[XELLERATE.SERVER],Class/Method: tcUSR/eventPreInsert Error :Mandatory fields are blank or null.
BR
Edited by: user10478011 on Dec 1, 2008 10:24 PM

Similar Messages

Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff

We have a project using TopLink 10.1.3 with WAS 6.0 and Oracle 9i. The project is experiencing the following exception. Could someone provide an insight on what could cause the error? We greatly appreciate your help.
[7/20/07 10:00:32:718 EDT] 00000023 SystemOut     O [TopLink Finer]: 2007.07.20 10:00:32.718--ServerSession(120755866)--client acquired
[7/20/07 10:00:32:718 EDT] 00000023 SystemOut     O [TopLink Finest]: 2007.07.20 10:00:32.718--ClientSession(1697994439)--Execute query ReadAllQuery(com.ford.gpd.plm.fos.bo.RepSolvedRules)
[7/20/07 10:00:32:718 EDT] 00000023 SystemOut     O [TopLink Finest]: 2007.07.20 10:00:32.718--ServerSession(120755866)--reconnecting to external connection pool
[7/20/07 10:00:32:718 EDT] 00000023 SystemOut     O [TopLink Fine]: 2007.07.20 10:00:32.718--ServerSession(120755866)--Connection(2023118535)--select a.fos005_ftr_C, a.fos007_rule_d, a.fos011_column_d, a.fos001_option_c, a.fos009_report_k, a.FOS002_PROD_TYPE_C, a.FOS002_VEH_LINE_C, a.FOS002_MODEL_YEAR_R
from FFOSV01_REP_OPT_SOLVE_RULE_VW a, FFOS020_REP_SOLVE_QUALIFIER b
where a.fos009_report_k = 3
and a.fos011_column_d in (3, 4, 5, 8, 9, 14)
and UPPER(b.fos005_qualifier_ftr_c) like UPPER('a3%')
and a.fos009_report_k = b.fos009_report_k
and a.fos013_group_d = b.fos013_group_d
and a.fos011_column_d = b.fos011_column_d
and a.fos007_rule_d = b.fos007_rule_d
--and a.fos013_report_date_s = b.fos013_report_date_s
order by a.fos005_ftr_C, a.fos011_column_d, DECODE(a.fos001_option_c, 'S', 1, 'L', 2, 'M', 3, 'O', 4, 'P', 5, 'I', 6, 'A', 7)
[7/20/07 10:00:32:749 EDT] 00000023 SystemOut     O [TopLink Warning]: 2007.07.20 10:00:32.749--ClientSession(1697994439)--java.lang.IllegalArgumentException: Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff
     at java.sql.Timestamp.valueOf(Timestamp.java:304)
     at oracle.jdbc.driver.OracleStatement.getTimestampValue(OracleStatement.java(Compiled Code))
     at oracle.jdbc.driver.OracleResultSetImpl.getTimestamp(OracleResultSetImpl.java(Compiled Code))
     at com.ibm.ws.rsadapter.jdbc.WSJdbcResultSet.getTimestamp(WSJdbcResultSet.java(Compiled Code))
     at oracle.toplink.oraclespecific.Oracle9Platform.getObjectFromResultSet(Oracle9Platform.java(Compiled Code))
     at oracle.toplink.internal.databaseaccess.DatabaseAccessor.getObject(DatabaseAccessor.java(Compiled Code))
     at oracle.toplink.internal.databaseaccess.DatabaseAccessor.fetchRow(DatabaseAccessor.java(Compiled Code))
     at oracle.toplink.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java(Compiled Code))
     at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:442)
     at oracle.toplink.threetier.ServerSession.executeCall(ServerSession.java:453)
     at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:117)
     at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:103)
     at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeSelectCall(DatasourceCallQueryMechanism.java:174)
     at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.selectAllRows(DatasourceCallQueryMechanism.java:481)
     at oracle.toplink.queryframework.ReadAllQuery.executeObjectLevelReadQuery(ReadAllQuery.java:458)
     at oracle.toplink.queryframework.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:800)
     at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:603)
     at oracle.toplink.queryframework.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:768)
     at oracle.toplink.queryframework.ReadAllQuery.execute(ReadAllQuery.java:436)
     at oracle.toplink.publicinterface.Session.internalExecuteQuery(Session.java:2062)
     at oracle.toplink.publicinterface.Session.executeQuery(Session.java:981)
     at oracle.toplink.publicinterface.Session.executeQuery(Session.java:953)
     at com.ford.it.persistence.impl.toplink.AbstractQueryStrategy.execute(AbstractQueryStrategy.java:324)
     at com.ford.it.persistence.impl.toplink.QueryImpl.execute(QueryImpl.java:138)FFOSV01_REP_OPT_SOLVE_RULE_VW is a VIEW and the reference b FFOS020_REP_SOLVE_QUALIFIER is a table with a to b as one-to-many mapping. View has a reportDate filed as DATE and the same with the b table. Java side descriptors are using the java.sql.Timestamp.
The problem is when joining the View with the Table(like in the above SQL), the Exception occurs. If we run a select from the View then we don't see this exception.
-- Haiwei

Thanks for your responses.
The developer changed the query in the Workbench to be:
SELECT DISTINCT t0.FOS001_OPTION_C, t0.FOS007_RULE_D, t0.FOS009_REPORT_K, t0.FOS011_COLUMN_D, t0.FOS013_GROUP_D, t0.FOS003_EFF_PT_IN_C, t0.FOS003_EFF_PT_OUT_C, t0.FOS013_REPORT_DATE_S, t0.FOS005_FTR_C, t0.FOS002_PROD_TYPE_C, t0.FOS002_MODEL_YEAR_R, t0.FOS002_VEH_LINE_C
FROM FFOSV01_REP_OPT_SOLVE_RULE_VW t0, FFOS020_REP_SOLVE_QUALIFIER t1
WHERE (((t0.FOS009_REPORT_K = 3)
AND (t1.FOS005_QUALIFIER_FTR_C LIKE 'A3%'))
AND (t0.FOS011_COLUMN_D in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14))
AND ((t1.FOS002_VEH_LINE_C = t0.FOS002_VEH_LINE_C)
AND ((t1.FOS013_GROUP_D = t0.FOS013_GROUP_D)
AND ((t1.FOS007_RULE_D = t0.FOS007_RULE_D)
AND ((t1.FOS009_REPORT_K = t0.FOS009_REPORT_K)
AND ((t1.FOS013_REPORT_DATE_S = t0.FOS013_REPORT_DATE_S)
AND ((t1.FOS002_PROD_TYPE_C = t0.FOS002_PROD_TYPE_C)
AND ((t1.FOS011_COLUMN_D = t0.FOS011_COLUMN_D)
AND (t1.FOS002_MODEL_YEAR_R = t0.FOS002_MODEL_YEAR_R)))))))))
order by t0.FOS005_FTR_C, t0.FOS011_COLUMN_D, DECODE(t0.FOS001_OPTION_C, 'S', 1, 'L', 2, 'M', 3, 'O', 4, 'P', 5, 'I', 6, 'A', 7)and it worked.
What happened was that when the application defined a similar join using Expression, with simplified where clause, between the View and table in the Workbench, the join worked fine. So the applicaiton updated its original query (the select part) based on the SQL generated by TopLink runtime for the join.
The project uses Oracle9Platform.
Regarding "Query executes in JDBC and returns expected result": the original query executed fine with Oracle SQL Developer.
Regarding "Does the date column you are trying to read have any time portion or is it just a date with no time portion?": the date column is of DATE database type, and has time portion.
Thanks again for your responses.
Haiwei

(OIM) Timestamp format must be yyyy-mm-dd.....

Iam facing the following exception every time i try to save the user I have edited in the resouce profile
java.lang.IllegalArgumentException: Timestamp format must be yyyy-mm-dd hh:mm:ss[.fffffffff]
is there a way of editing the time stamp so that it should correspond to the afore said format?
I have tried naming one of the system cofigurations Default date and given it a keyword of rs.getDate() and a value of yyyy-mm-dd hh:mm:ss[.fffffffff]. But am still getting the same exception.

I really dont know what exaclty is the causative of this. Cause even when i do not have the date changed still, any changes that i make are not saved and the page page cannot be desplayed is displayed after clicking the save button.
But when i try to provision a new user to the resource, the provisioning is going on very well without any problems.
But when i try to edit the user's details pertaining to the resource they have been provisioned, thats when the TIMESTAMP FORMAT... issue and page cannot be desplayedarrises, .
Am using win2003 platform, and its OIM Version: 9.0.1.1561.0.
Could it be that the details after provisioning cannot be changed once provisioned?
Thanks

To convert date dd/mm/yyyy in Timestamp format

hi
I want to convert date of format dd/MM/yyyy, which get from user by PropertyUtils.getSimplePropetrty(form, "startDate"); , into Timestamp format...........
please help me in this regard.......
1904

ya mean it from java.sql.Timestamp
and also I am using getTime() method but giving
root cause:
org.apache.commons.beanutils.ConversionException: Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff
and
Caused by: java.lang.IllegalArgumentException: Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff
at java.sql.Timestamp.valueOf(Timestamp.java:160)
at org.apache.commons.beanutils.converters.SqlTimestampConverter.convert(SqlTimestampConverter.java:157)

Timestamp format error

Hi,
While using the Oraclexml classes to
write an XML document to an 8.1.5 DB I get an error oracle.xml.sql.OracleXMLSQLException: Exception
'java.lang.IllegalArgumentException:Timestamp format must be yyyy-mm-dd
hh:mm:ss.fffffffff' encountered during processing ROW element 0All prior XML
row changes were rolled back. in the XML document. The data format in the file is
09/18/00 12:00:00.

If you're using it through the commandline, use the "dateFormat" option in putXML or getXML.
If you're using the OracleXMLSave class, there is the method "setDateFormat()" that you could use. OracleXMLQuery also has one.

Trouble getting a timestamp formatted by a 'to_char' function

We have trouble getting a timestamp formatted by a 'to_char' function and a 'group by'
for a count. By assigning the result of the to_char function to an attribute and
grouping on that attribute, we try to get the frequency of an event.
What happens is a non predictable 'IllegalArgumentException' on
'Timestamp.class' while getting the timestampvalue.
We make use of a scrollablecursor as you can see in the stacktrace.
java.lang.IllegalArgumentException: Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff
at java.sql.Timestamp.valueOf(Timestamp.java:160)
at oracle.sql.CHAR.timestampValue(CHAR.java:567)
at oracle.jdbc.driver.ScrollableResultSet.getTimestamp(ScrollableResultSet.java:658)
at oracle.toplink.oraclespecific.Oracle9Platform.getObjectFromResultSet(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.getObject(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.fetchRow(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.cursorRetrieveNextRow(Unknown Source)
at oracle.toplink.queryframework.ScrollableCursor.retrieveNextObject(ScrollableCursor.java:512)
at oracle.toplink.queryframework.ScrollableCursor.loadNext(ScrollableCursor.java:357)
at oracle.toplink.queryframework.ScrollableCursor.hasNext(ScrollableCursor.java:233)
After restarting the application server there is a chance that the query returns
with the expected results. But most of the times it just returns the above
mentioned exception.
I don't see the logic in the apparently random parsing of the value.
The column in the database is a timestamp, but that the reason why i'm using the
to_char method.

This is a bug in TopLink with ReportQuery. Please report this is Oracle technical support. Basically TopLink is converting to the attribute type, but should not be if a function was applied to the expression.
To workaround the issue you can use getField(/) in the expression instead of get(/) (using the database field name instead of the class attribute name).

For date attribute search, the format must be mm/dd/yyyy

Hello.
The manual "Oracle® Secure Enterprise Search Administrator's Guide 10g Release 1" says that when searching on date attributes, the format must be mm/dd/yyyy.
For our users it is more natural to use the format dd/mm/yyyy so in order to reduce the risk of users not finding what they are looking for, I would like to know if there is a way to use the dd/mm/yyyy format instead.
Regards,
Brian Nielsen

Being based in Europe as well, I understand this problem.
Unfortunately I don't think there's a way around it.
I have previously requested that this problem should be fixed, but I've now formally raised a bug for this issue - bug number 10163778.
I can't promise a quick fix, but hopefully we will get one in a future release.

JHS-00114: Date $CURRENT_DATE$ must be of format MM-dd-yyyy

I am using jheadstart 10.1.2.2(build 32) in jdeveloper 10.1.2.1.0(build 1913).
I need to display current date for a date field as a default value when inserting new rows.
I set $CURRENT_DATE$ in default display value for that date field. The default value(todays date) is displayed only on a tabel(multi row insert is allowed) and on a form(single row insert) I get the above error JHS-00114: Date 2007-01-02 14:18:37.0 must be of format MM-dd-yyyy.
The problem with multirow insert on a table even though it displays default value is user has to fill in other mandatory fields in the row since jheadstart thinks that user already started entering new row.
It's ok for me if the default value is displayed properly on either table or form.
Thanks for any help.
Lavanya.

Whenever you are in PM:
sys@sid1> l
1* select to_char(sysdate, 'MM/DD/YYYY HH12:MI:SS AM') from dual
sys@sid1> /
TO_CHAR(SYSDATE,'MM/DD
07/09/2007 01:22:48 PM
1 row selected.
My time is 1:22:48 PM here. Even though I put AM in the to_char format, it noticed it was PM and changed it.

Problem with date format "dd-MM-yyyy"

hi all,
i am using jdev 10.1.3.2
My application ADF Swing app.
in my database i have a table employee which contains "birthday".
my problem is that i must use date format"dd-MM-yyyy".
i added this format into "formatinfo.xml" file.
than i choose it in my EO.
i create a form which contains employees.
for example i have an employee with a birthday=25-10-1970
in my text field if user puts "1970-10-25"'which is not the best format) he will have a correct result "25-10-1970"
but if user puts "25-10-1970" he will have as result "21-02-0031" which is not the real value.
please help me.
thanks.
PS: i did some research before posting but i didn't find yet

Rouz,
Did you try what i said before?
* Open you EntityObject
* Expand the attribute tree
* Choose your DOB attribute
* Choose the Control hints pane on the right
* Choose Formater: Simple date format
* Choose Format mask dd-MM-yyyy
Run your application and try it.
This is how i change the format and it works perfectly.
I uses the correct format to show the date and it enables me to edit the date using the format mask dd-MM-yyyy
Edit: I just tried it myself. I can only reproduce it by removing my mask. Ergo, the application expects the default american format yyyy-MM-dd. By entering a date in the format dd-MM-yyyy the framework will convert it to yyyy-MM-dd and you'll end up with 0031-02-21.
CONCLUSION follow the steps i discribed above to set your mask and you'll be fine.
Message was edited by:
Smolders Johan

SQL * Loader : Load data with format MM/DD/YYYY HH:MI:SS PM

Please advice how to load data with format MM/DD/YYYY HH:MI:SS PM into an Oracle Table using SQL * Loader.
- What format should I give in the control file?
- What would be the column type to create the table to load data.
Sample data below;
MM/DD/YYYY HH:MI:SS PM
12/9/2012 2:40:20 PM
11/29/2011 11:23:12 AM
Thanks in advance
Avinash

Hello Srini,
I had tried with the creation date as DATE datatype but i had got an error as
ORA-01830: date format picture ends before converting entire input stringI am running the SQL*LOADER from Oracle R12 EBS front-end.
the contents of my control file is
LOAD DATA
INFILE "$_FileName"
REPLACE
INTO TABLE po_recp_int_lines_stg
WHEN (01) = 'L'
FIELDS TERMINATED BY "|"
OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
INDICATOR                POSITION(1) CHAR,
TRANSACTION_MODE          "TRIM(:TRANSACTION_MODE)",
RECEIPT_NUMBER               "TRIM(:RECEIPT_NUMBER)",
INTERFACE_SOURCE          "TRIM(:INTERFACE_SOURCE)",
RECEIPT_DATE               "TO_CHAR(TO_DATE(:RECEIPT_DATE,'MM/DD/YYYY'),'DD-MON-YYYY')",
QUANTITY               "TRIM(:QUANTITY)",
PO_NUMBER               "TRIM(:PO_NUMBER)",
PO_LINE_NUMBER               "TRIM(:PO_LINE_NUMBER)",
CREATION_DATE               "TO_CHAR(TO_DATE(:CREATION_DATE,'MM/DD/YYYY HH:MI:SS AM'),'DD-MON-YYYY HH:MI:SS AM')",
ERROR_MESSAGE                   "TRIM(:ERROR_MESSAGE)",
PROCESS_FLAG                    CONSTANT 'N',
CREATED_BY                      "fnd_global.user_id",
LAST_UPDATE_DATE                SYSDATE,
LAST_UPDATED_BY                 "fnd_global.user_id"
{code}
My data file goes like
{code}
H|CREATE|123|ABC|12/10/2012||||
L|CREATE|123|ABC|12/10/2012|100|PO12345|1|12/9/2012 2:40:20 PM
L|CORRECT|123|ABC|12/10/2012|150|PO12346|2|11/29/2011 11:23:12 AM{code}
Below is the desc of the table
{code}
INDICATOR             VARCHAR2 (1 Byte)
TRANSACTION_MODE        VARCHAR2 (10 Byte)
RECEIPT_NUMBER             NUMBER
INTERFACE_SOURCE        VARCHAR2 (20 Byte)
RECEIPT_DATE             DATE
QUANTITY             NUMBER
PO_NUMBER             VARCHAR2 (15 Byte)
PO_LINE_NUMBER             NUMBER
CREATION_DATE             TIMESTAMP(0)
ERROR_MESSAGE             VARCHAR2 (4000 Byte)
PROCESS_FLAG             VARCHAR2 (5 Byte)
CREATED_BY             NUMBER
LAST_UPDATE_DATE        DATE
LAST_UPDATED_BY             NUMBER     {code}
Thanks,
Avinash

Timestamp Format

Hi Gurus,
I have a double field which stores date values and i have another double fiels which stores time.Now i need to concat both these and cast it to timestamp.The problem which i am facing is with the Format of timestamp.I am unable to specify the format neither in answers nor in RPD.Thw syntax which i am using is as follows cast(cast("date value"||"time vale") as char ( 18 ) ) as timestamp format 'yyyymmddhhmmss').If i dnt specify any format answers return an error saying Invalid timestamp.please help

"set nls_timestamp_format = 'YYYY-MM-DD
HH24:MI:SS.FF1'"
Could this be done at database level.If this can be
done using some parameter files,what exactly has to
be done?yes, it is done at the database level when you create your database. it is done at the instance level with the NLS_TIMESTAMP_FORMAT parameter and it is modifyable at the session level too.
SQL> select type,parameter,value from (
2 select 'NLS_DATABASE_PARAMETERS' type,parameter,value from NLS_DATABASE_PARAMETERS
3 union all
4 select 'NLS_INSTANCE_PARAMETERS',parameter,value from NLS_INSTANCE_PARAMETERS
5 union all
6 select 'NLS_SESSION_PARAMETERS',parameter,value from NLS_SESSION_PARAMETERS
7 )
8 where parameter='NLS_TIMESTAMP_FORMAT'
TYPE                    PARAMETER                      VALUE
NLS_DATABASE_PARAMETERS NLS_TIMESTAMP_FORMAT           DD.MM.RR HH24:MI:SSXFF
NLS_INSTANCE_PARAMETERS NLS_TIMESTAMP_FORMAT
NLS_SESSION_PARAMETERS NLS_TIMESTAMP_FORMAT           DD.MM.YYYY HH24:MI:SS.FFMessage was edited by:
Laurent Schneider
you cannot change the "database" level after db creation, but you can modify the "instance" level by specifying the parameter in your parameter file

Timestamp format for SQL Server data

Hi all,
I put this question on the PL/SQL forum but got no answer yet. Could anyone help me with the timestamp format for a timestamp data from SQL Server? I have this in the xml from SQL server,
2006-06-20T00:00:00-05:00
and I need to make it a date or timestamp data type in Oralce. I have looked at the docs and could not find the correct format for this. Please note there is a T in the middle and I don't know why it is there and what it is for.
Thanks.
Ben

Actually the date is in the only form that is valid in the XML Schema spec and the RFC that the datetime formats are allowed to be in per the XML schema spec...
The way to decode is to a timestamp with timezone
SQL> select to_timestamp_Tz('2006-06-20T00:00:00-05:00','YYYY-MM-DD"T":HH24:MI:SSTZH:TZM') from dual;
TO_TIMESTAMP_TZ('2006-06-20T00:00:00-05:00','YYYY-MM-DD"T":HH24:MI:SSTZH:TZ
20-JUN-06 12.00.00.000000000 AM -05:00
SQL>

Timestamp formats that include literal data in quotes

Is there an alternate way to specify literal text in timestamp formats, other than to quote it with double quotes? I am trying to work around a bug in SQLDeveloper (described below).
The formats I am using are:
timestamp: YYYY-MM-DD"t"HH24:MI:SS.FF6
timestamp tz: YYYY-MM-DD"t"HH24:MI:SS.FF6TZH:TZM
These formats work fine in sqlplus and in my application:
SQL> alter session set nls_timestamp_format = 'YYYY-MM-DD"t"HH24:MI:SS.FF6';
Session altered.
But when I use these them in the Database->NLS Parameters section in Preferences, I get the following error:
ORA-02248: invalid option for ALTER SESSION
If I remove the "t" from the middle, there are no errors in SQLDeveloper and the formats work correctly in the sql worksheet.
SQLDeveloper: 1.1.2.25 on Windows XP Pro
Oracle server: 9.2.0.5.0, 64bit running on Solaris
Thanks,
Philip

Hi JW,
if you want to track changes, implement the how-to paper about "line-items" (see SAP Service Marketplace). BPS layout will always show the latest data (price) and to show the history, you can use a simple BW query with drill-down on the timestamp.
Regards
Marc
SAP NetWeaver RIG

Database level setting for timestamp format

Is there any way by which I could set the timestamp format for a database
Something similar to timestamp sesion setting like
alter session set nls_timestamp_format = 'YYYY-MM-DD HH24:MI:SS.FF1'

You can define NLS parameters at the instance level in the parameters file. But any redefinition at the client side will overcome this.

SEVERE: Message: [-3050]: Invalid timestamp format:ISO(input position 2)

Hello!
I'm installing a AS JAVA 2004S with EP/EP-CORE and BI_JAVA and got following error during Java Load step. (The installation successfully creates and loads about 1000 tables prior the error).
Regards,
Fredrik
serverXX:/usr/sap/TPQ/ciinst # more jload.java.log
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20061124 (JIT enabled)
J9VM - 20061121_1035_LHdSMr
JIT - r7_level20061020_1803)
May 24, 2007 11:39:52 AM com.sap.inst.jload.Jload main
INFO: Jload -sec TPQ,jdbc/pool/TPQ,/usr/sap/TPQ/SYS/global/security/data/SecStore.properties,/usr/sap/TPQ/SYS/global/security/data/Se
cStore.key -dataDir /a_stage/51032257/JAVA_EXPORT/JDMP -job /usr/sap/TPQ/ciinst/IMPORT.XML -log jload.log
May 24, 2007 11:39:53 AM com.sap.inst.jload.db.DBConnection connectViaSecureStore
INFO: connected to TPQ on jdbc/pool/TPQ
May 24, 2007 11:39:53 AM com.sap.inst.jload.JobStatus readStatus
INFO: trying to read status file /usr/sap/TPQ/ciinst/IMPORT.sta
May 24, 2007 11:39:53 AM com.sap.inst.jload.JobStatus readStatus
INFO: commencing restart
May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload dbImport
INFO: trying to delete from table BC_UDDI_PARAM
May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload dbImport
INFO: BC_UDDI_PARAM deleted
May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload dbImport
SEVERE: DB Error during import of BC_UDDI_PARAM
May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload printSQLException
SEVERE: Message: [-3050]: Invalid timestamp format:ISO(input position 83)
May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload printSQLException
SEVERE: SQLState: I3050
May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload printSQLException
SEVERE: ErrorCode: -3050
May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload dbImport
INFO: trying to delete from table BC_XMLA_COL
May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload dbImport
INFO: BC_XMLA_COL deleted
May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload dbImport
SEVERE: DB Error during import of BC_XMLA_COL
May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload printSQLException
SEVERE: Message: [-3050]: Invalid timestamp format:ISO(input position 2)
May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload printSQLException
SEVERE: SQLState: I3050
May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload printSQLException
SEVERE: ErrorCode: -3050
May 24, 2007 11:39:53 AM com.sap.inst.jload.db.DBConnection disconnect
INFO: disconnected
serverXX:/usr/sap/TPQ/ciinst #

Hi
yes, I had the same issue and I found a solution.
You need to request a patch for BUG 9212862 (already corrected in WLS 10.3.3) and do the follwing:
javax.xml.ws.BindingProvider provider = (javax.xml.ws.BindingProvider)port;
java.util.Map context = provider.getRequestContext();
context.put(weblogic.wsee.jaxrpc.WLStub.POLICY_COMPATIBILITY_PREFERENCE, weblogic.wsee.jaxrpc.WLStub.POLICY_COMPATIBILITY_MSFT);
This will cause the SecurityMessageArchitect class of WLS to not send the SecurityTokenReference in the Soap security header.
Please note that is evidently a non-comformity to the specs of microsoft:
Please give a look at
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf (8.3 Signing Tokens)
and also at:
http://www.oasis-open.org/committees/download.php/16768/wss-v1.1-spec-os-SAMLTokenProfile.pdf
(3.4 Identifying and Referencing Security Tokens)
A SAML key identifier reference MUST be used for all (local and remote) references to SAML 1.1
assertions. [...]
All conformant implementations MUST be able to process SAML assertion references occurring in a
<wsse:Security> header or in a header element other than a signature to acquire the corresponding
assertion. A conformant implementation MUST be able to process any such reference independent of the
confirmation method of the referenced assertion.
It follows that the .NET 3.5 is a non conformat implementation: I would gladly know which is the position of Microsoft on that.
ciao
carlo

Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff exception

Similar Messages

Maybe you are looking for