Timestamp/Date format error with Java 1.6

I'm getting this error trying to getObjects from a ResultSet query for an Oracle Lite 10G table that has colums of the TIMESTAMP or DATE type. This works fine under java 1.5. Java 1.6 seems to have broken TIMESTAMP/DATE compatibility with Oracle Lite. Are there any plans to make 10G compatible with Java 1.6? We would like to port our application from Java 1.5 to 1.6, but this is an obstacle. I suppose one work-around would be to use TO_CHAR on all the DATE fields and convert them back to java Dates programatically, but that would be a hassle.
Update: I changed the column types of the table from TIMESTAMP to DATE. The same exception occurs when calling POLJDBCResultSet.getObject() on the DATE columns. Again, this works fine under Java 1.5, but not 1.6.
java.lang.IllegalArgumentException: Timestamp format must be yyyy-mm-dd hh:mm:ss[.fffffffff]
     at java.sql.Timestamp.valueOf(Timestamp.java:194)
     at oracle.lite.poljdbc.LiteEmbResultSet.jniGetDataTimestamp(Native Method)
     at oracle.lite.poljdbc.LiteEmbResultSet.getVal(Unknown Source)
     at oracle.lite.poljdbc.POLJDBCResultSet.getTimestamp(Unknown Source)
     at oracle.lite.poljdbc.POLJDBCResultSet.getObject(Unknown Source)
     at oracle.lite.poljdbc.POLJDBCResultSet.getObject(Unknown Source)

I just found a pretty easy java work-around for this that doesn't involve changing the table column types or the SQL:
Check the column type from the ResultSetMetaData before calling ResultSet.getObject(). If the type is DATE, TIMESTAMP or TIME, call ResultSet.getString() which doesn't throw an exception. Then convert the string to a java.util.Date using java.text.SimpleDateFormat. That can then be used to instantiate a Timestamp.
This seems to work.
Message was edited by:
user490596

Similar Messages

Date Format error with af:selectInputDate

Hi ,
I am using <af:selectInputDate> in my application for one of the page.I have added <af:convertDateTime pattern="MM/dd/yyyy"/> for formatting user entered date value.i have also added valuechange listener for this component as well, just to check whether user has actually modified the value in this textfield either manually or by Date picker.
However, if user enters manually value in the textbox, say 04/09/2007, in the valuechange listener method when i have retrieved the user entered value from ValueChangeEvent object using following snippet:
code:
Date d=(java.util.Date) valueChangeEvent.getNewValue()
i could see the date in the following format when printed on console
04/09/0007
due to this incorrect format, i am facing problems in subsequent operations.
can anybody help me in understanding the reason behind the same as well as can you suggest me code changes (if any) so that i will get proper date in the listener method?
Thanks,
Shriniwas

Thanks Frank for a quick reply.
I have used the SimpleDateFormat for formatting with the pattern as, "MM/dd/yyyy" and it is working fine if user enters 4 digit year.
However, for a entry with 2 digits for a year e.g. 04/10/07 when i parse the date using SimpleDateFormat,it is giving me date as 04/10/0007.
Is there a way by means of which i could force the user to enter 4 digits for the year?
I have tried using dateStyle attribute of <af:convertDateTime> tag with 'shortish' as its value, it converts a 2 digit year into 4digit on the browser side & displays on the screen e.g. if user enters 04/10/07 it will appear as 04/10/2007 on the screen however, in value change listener method, i could see date as 04/10/0007.
Any help in this regard is highly appreciated.
Thanks in advance,
Shriniwas

Date format error in LOV with dates. Jdeveloper 11.1.1.0.1

We're facing a silly problem, which no one else seems to have... ?
When creating a LOV on a date column (eg hr.employees.hiredate) populated from another DataSource (eg. hr.job_history.startDate), the Application Module is working fine when tested.
Building a jspx on top of the Datacontrol picks up the LOV defined and creates a SelectOneChoice for hiredate. But for what ever value you select, it will complain about wrong date format "Error: The date is not in the correct format".
I can see, that the "real" value selected from the SelectOneChoice is an index-value, and the "format checking code" builtin to Jdeveloper can't figure out how to get the datevalue for the selected index.
Surely it must be me, who can't see the forest for the trees?
Thanks in advance :)

Its a bit tricky - but its doable... We have to abandon the "Oracle LOV model" to make it work.
Surely its must be some kind of bug in the Oracle LOV model? ?
The way to do it is like:
In Model project:
M1: Remove List Of Value binding from Model layer (Business components). Both entity and view if declared both.
M2: Create a view for the "date list" - ie the datasource for possible values in list.
M3: Secure that format mask (hint) for all dates involved are the same.
In View project:
V1: Drop datacontrol on jspx as normal input dates.
V2:Go to bindings for the page, and add (+) a new TABLE binding (And from here an iterator) to the view containing the list.
Modify the input dates you want to be list:
V3: Select the input date and rightclick and choose "convert"
V4: Select a SelectOneChoice component
V5: Pick the right column (tree) value to show in the SelectOneChoice componet.
Switch to source view:
V6: Drop a ForEach item from the component Palette (ADF Faces -> operations) on the SelectOneChoice (easiest to drop in structure windows)
V7: Drop a Select Item from the component Palette (ADF Faces -> common components) on the SelectOneChoice (easiest to drop in structure window).
Modify the source:
V8: Insert "items" and "var" attributes in ForEach like this: +"items="#{bindings.[[Here goes the name of the New TableBinding component you made in Step V2]].rangeSet}" var="li"+
V9: Insert "value" attribute and change "label" attribute to reference your new list variable "li" like this: +label="#{li.[[here goes the name of the new TableBinding Component attribute (columnname) you made in Step V2]]}" value="#{li.Firstofmonth}"+
V10: Insert/edit any converters/validators needed for input validation.
Done....
You should end up with a SelectOnChoice definition (in your jspx file) something like this one:
+<af:selectOneChoice value="#{row.bindings.ActiveFrom.inputValue}"+
+label="#{row.bindings.ActiveFrom.label}"+
+required="#{bindings.McAccountsView1.hints.ActiveFrom.mandatory}"+
+shortDesc="#{bindings.McAccountsView1.hints.ActiveFrom.tooltip}">+
+<af:forEach items="#{bindings.FirstOfMonth1.rangeSet}" var="li">+
+<af:selectItem label="#{li.Firstofmonth}" value="#{li.Firstofmonth}" />+
+</af:forEach>+
+<af:convertDateTime pattern="dd-MM-yyyy"+
+messageDetailConvertDate="Its not possible to convert the date in {0} since its value {1} dont conform to the pattern {2}"+
+secondaryPattern="yyyy-MM-dd"/>+
+</af:selectOneChoice>+
And a binding definition (in your pagedef file) something like this one:
+<?xml version="1.0" encoding="UTF-8" ?>+
+<pageDefinition xmlns="http://xmlns.oracle.com/adfm/uimodel"+
+version="11.1.1.52.5" id="McAccounts01PageDef"+
+Package="solution">+
+<parameters/>+
+<executables>+
+<iterator Binds="McAccountsView1" RangeSize="25"+
+DataControl="dateLovEmailDataControl"+
+id="McAccountsView1Iterator" ChangeEventPolicy="ppr"/>+
+<searchRegion Binds="McAccountsView1Iterator" Criteria=""+
+Customizer="oracle.jbo.uicli.binding.JUSearchBindingCustomizer"+
+id="McAccountsView1Query"/>+
+<iterator id="FirstOfMonth1Iterator" RangeSize="10" Binds="FirstOfMonth1"+
+DataControl="dateLovEmailDataControl"/>+
+</executables>+
+<bindings>+
+<tree IterBinding="McAccountsView1Iterator" id="McAccountsView1">+
+<nodeDefinition DefName="dk.hammerJakobsen.Jdev.sample.model.McAccountsView">+
+<AttrNames>+
+<Item Value="EmployeeName"/>+
+<Item Value="Id"/>+
+<Item Value="BankAccount"/>+
+<Item Value="StellarAccount"/>+
+<Item Value="ActiveFrom"/>+
+<Item Value="ActiveTo"/>+
+</AttrNames>+
+</nodeDefinition>+
+</tree>+
+<action IterBinding="McAccountsView1Iterator" id="CreateInsert"+
+RequiresUpdateModel="true" Action="createInsertRow"/>+
+<action IterBinding="McAccountsView1Iterator" id="Delete"+
+RequiresUpdateModel="false" Action="removeCurrentRow"/>+
+<action IterBinding="McAccountsView1Iterator" id="First"+
+RequiresUpdateModel="true" Action="first"/>+
+<action IterBinding="McAccountsView1Iterator" id="Last"+
+RequiresUpdateModel="true" Action="last"/>+
+<action IterBinding="McAccountsView1Iterator" id="Find"+
+RequiresUpdateModel="true" Action="iteratorFind"/>+
+<action IterBinding="McAccountsView1Iterator" id="Execute"+
+RequiresUpdateModel="true" Action="iteratorExecute"/>+
+<action id="Commit" RequiresUpdateModel="true" Action="commitTransaction"+
+DataControl="dateLovEmailDataControl"/>+
+<action id="Rollback" RequiresUpdateModel="false"+
+Action="rollbackTransaction" DataControl="dateLovEmailDataControl"/>+
+<table IterBinding="FirstOfMonth1Iterator" id="FirstOfMonth1">+
+<AttrNames>+
+<Item Value="Firstofmonth"/>+
+</AttrNames>+
+</table>+
+</bindings>+
+</pageDefinition>+
this approach works... But... Its important to remember that the "two" values are different now. The value in the row, and the possible value from the list. When you select a new value for the row from the list, you'll have to commit the value before its in the row - even seen from Faces. You can't reference the value in the base table in a validator before the row is committed.
For the same reason I'll advise, that you only use the model in Single row view, since its can behave a bit funny in table views, where there's a lot of PPR.

Home Page Date Format ERROR ...

I installed language support on my Portal 3.0.9.8 with 3 different languages: us, i=italian, f
but when i use the "i" language there are many problems with format date ...
in the Portal Home Page i have a message like "date format not valid"
and i have problems in the creation of the content area's items with the publish date.
Any one have an idea ???

HI All,
I have check my own data date format.
But when i tried to activate the cycle count under
Menu path:
Materials Management > Inventory Management and Physical Inventory>Physical Inventory> Cycle Counting
I will not put any date on it, that's why its weird that i get an date format error.
Where this error came from?
Thanks..

Date Format Error During Cycle Count Activation

Hi MM Guru's,
Could you kindly help me with regards to my problem?
I was trying to activate the cycle count for the newly plant i created under new company code.
But im getting a date format error?
Anyone who could help me regarding this?
Thank you in advance.

HI All,
I have check my own data date format.
But when i tried to activate the cycle count under
Menu path:
Materials Management > Inventory Management and Physical Inventory>Physical Inventory> Cycle Counting
I will not put any date on it, that's why its weird that i get an date format error.
Where this error came from?
Thanks..

Mailman - bounced "data format error" - Mailbox does not exist

Hi gurus,
All my mailing lists works great, except one of then...
Its said: a lot of messages like this, several times:
Mar 6 07:08:33 rossellimac postfix/pipe[2931]: 3F55D15F892: to=<[email protected]>, orig_to=<[email protected]>, relay=cyrus, delay=0.11, delays=0.04/0/0/0.07, dsn=5.6.0, status=bounced (data format error. Command output: alejandro: Mailbox does not exist )
Also this error:
3/6/09 8:18:20 AM lmtpunix[4844] AOD: user opts: get attributes for user: alejandro failed with error: -14479
3/6/09 8:18:20 AM lmtpunix[4844] warning: unable to post message for user: alejandro, mail is not enabled for this user
The computers halt for a minute... when I send an email to this list (general@) where "alejandro is a user"
Please, some advice... I surf the web... and not always produce error...
Thanks in advance.
Message was edited by: alopezruiz

ok

Bex Analyser : Date Format error.

Hi All,
We are facing date format error, while running the query in Bex analyzer.
We have one column in report i.e Net Payment Date, so when we run the query in analyzer the single date like "5-6-2010 is getting swapped like 6-5-10 & year also showing two digits i.e instead of 2010 it shows 10" & date like "12-09-2010 is coming perfectly."
Means the date which is in single digit we are facing this problem like 1 to 9 & the dates which are 10 & above showing perfectly.
In RSRT the query showing proper result, so i don't think it's BI problem.
The regional setting is DD-MM-YYYY & Date separator is '-' & we don't want to change this format.
Is there any SAP note or any solution for this..??
All the replays are gr8ly appreciated.
Thanks,
Santosh

Hi Santosh,
how about web display? is it ok? for me it seems more an Excel problem, so maybe you should check if there is special formatingin this.
Regards,
Anass

Set Date Time Computer with Java in Linux OS

Dear All,
How to set date time computer with Java in linux OS?
Rgds,
Theo

There is no API for this you'd have to run an external command using Process.exec.
This is the wrong forum for general Java "how to" questions.

DATE Format Error in ODI-11g(11.1.1.3)

I am using ETL transformations in ODI-11g. There's a dominant issue regarding date formattings when I map an ODI variable (storing date) with a TGT column(datatype=date) mappings.
In all the src-tgt mappings I am formatting the date by using TO_DATE() functions. But still getting the error:
"ORA-01830: date format picture ends before converting entire input string".
A point to Note: The same ETL in other env are ruuning fine but in my new dev env it's giving this date error.
I had checked with the DBA folks and they confirmed they set equal DATE settings in all the env.
The ODI Variable is defined as an "Alphanumeric".
Tx Used: #BUSINESS_CURRENT_DT=TO_DATE('Date','YYYY-MM-DD')
Require some urgent advice...Please let me know

Hi,
W store name-value pair in the Control table from where we exctract our data. Both (param name and param value) are varchars.
Well this looks pretty strange in 11g! Here's what we found out...
If you are trying to retrieve a date variable by using TO_DATE() in the refresh query the ODI Java driver (JDK 1.6) would call java.sql.timestamp and gracefully attach HH:MI:SS.NS along with the date (YYYY-MM-DD HH:MI:SS.NS). My target ia a date always..!
So, when I do: TO_DATE('20101010','YYYY-MM-DD) in the refresh query ODI stores it as '2010-10-10 00:00:00.0'
For this the Load always fails as Oracle would not be able to interpret a timestamp by suing TO_DATE()
The Java driver does this damage. However, it may be wise to store as a timestamp rather as a date if in case u do a Data capture and want the exact time credentials.
Unfortunately not a req, as of now for us so I had to chop-off the timestamp..!
Let me know if you find any other details...
Thanks.!

Report data binding error with date values

I have CF7.02 with a Microsoft Visual FoxPro 9.0 SP1 Database
that I connect to using ODBC (FoxPro Driver 6.01.8630.01). I send
my sql results to a CF Report Builder 7.02 PDF report and it works
fine. If I dump the date values before I change them, they look
like the following: {ts '2004-12-20 00:00:00'} . However I have
tried a number of ways of manipulating the date before sending it
to the report, but I continue to get errors. I don't care what
format they go to the report in, since the report reformats them
anyway. I checked to make sure that none of the dates were null.
For example <cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDateTime(#ldCFPrcInputDate#) /> yields values in the
{ts '2004-12-20 00:00:00'} format when I dump the query results to
screen. Where:
ldCFPrcInputDate = 12/20/2004
CreateODBCDateTime(ldCFPrcInputDate) = {ts '2004-12-20
00:00:00'}
ReportQuery.PrcInputDate[lcCurRow] = {ts '2004-12-20
00:00:00'}
I get the error:
Report data binding error Unable to get value for field
'prcinputdate' of class 'java.util.Date'.
coldfusion.runtime.OleDateTime -> Date
Not using the CreateODBCDate function for example <cfset
ReportQuery.PrcInputDate[lcCurRow] = #ldCFPrcInputDate# /> I
get:
Report data binding error Unable to get value for field
'prcinputdate' of class 'java.util.Date'.
java.lang.String -> Date
Here are some of my failed attempts:
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDateTime(#ldCFPrcInputDate#) />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
#ldCFPrcInputDate# />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
DateFormat(CreateODBCDate(#ldCFPrcInputDate#),'mm/dd/yyyy') />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate(DateFormat(#ldCFPrcInputDate#,'mm/dd/yyyy') />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate(DateFormat(#ldCFPrcInputDate#,'mm-dd-yyyy') />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
Trim(createODBCDateTime(ldtmpdate)) />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate({05-07-2006}) />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate('{05-07-2006}') />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate(05/07/2006) />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate('05/07/2006')/>
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate(parseDateTime('05/07/2006')) />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
parseDateTime(CreateODBCDateTime(05/07/2006)) />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
parseDateTime(CreateODBCDateTime('#ldCFPrcInputDate#')) />
<cfset ReportQuery.PrcInputDate[lcCurRow] = '{05-07-2006}'
/>
<cfset ReportQuery.PrcInputDate[lcCurRow] = '{05/07/2006}'
/>
<cfset ReportQuery.PrcInputDate[lcCurRow] = '05/07/2006'
/>
I also did some googling without success. Any help is
appreciated.

You may want to make sure that the column is not included in
the query variable list in your report cfr file.
The newest version of the Report Builder, which may be
installed on the server, no longer tolerates vars appearing in that
list of they are not in the query itselft.

Date Format ERROR - Repository Browser

Hi all,
With the repository browser I can not see any data. In the MS-DOS window (Browser Listener) I am getting the following error:
ExecSummary.getObjData() SQLJ Exception:java.sql.SQLException: ORA-01821: Date format not recognized.
I am using spanish date format (by default). Does someone know where I can change the date format?
Thanks in advance,
Victor.
Edited by: VCP on Sep 8, 2009 12:42 PM

Hi zeppo,
The regional and language options are the same as DB. I think that it is related java configuration, but I don't know exactly how it works...
Regards
Victor.

Bit stumped; data overflow error with DATETIME vs DATE or DATETIME2

I find myself in a slightly perplexing situation. In trying to replicate data to a SQLServer 2008 database I have no problems doing so for a date column on the Oracle side to either a DATE or DATETIME2 datatype on the SQLServer side. However, upon trying a DATETIME column I'm given the errors below. Essentially a -2147217887 but Goldengate marks it as a data overflow error. The thing is, a datetime2 is more like a TIMESTAMP column in Oracle and the DATETIME is essentially a DATE. Why it would work with a DATE (less precise) or DATETIME2 (more precise) yet not a DATETIME (same precision) is a bit of a head scratcher. The same defs file is used for each of the options.
Before anyone suggests using either destination datatype that works, I've no choice; it has to be a DATETIME column. The customer is always right, even when they are infuriatingly wrong.
Anyone seen this before or have any suggestions?
Thanks very much in advance!!
Cheers,
Chris
trace
10:55:36.538 (366244) * --- entering READ_EXTRACT_RECORD --- *
10:55:36.538 (366244) exited READ_EXTRACT_RECORD (stat=0, seqno=-1, rba=-1156485006)
10:55:36.538 (366244) processing record for QA1_DW_MS_MAY04.LIEN
10:55:36.538 (366244) mapping record
10:55:36.538 (366244) entering perform_sql_statements (normal)
10:55:36.538 (366244) entering execute_statement (op_type=5,AWO_CUBE.LIEN)
10:55:36.599 (366305) executed stmt (sql_err=-2147217887)
10:55:36.599 (366305) exited perform_sql_statements (sql_err=-2147217887,recs output=6018)
10:55:36.599 (366305) aborting grouped transaction
10:55:36.619 (366325) aborted grouped transaction
10:55:36.619 (366325) committing work
10:55:36.619 (366325) Successfully committed transaction, status = 0
10:55:36.619 (366325) work committed
10:55:36.619 (366325) writing checkpoint
10:55:36.619 (366325) * --- entering READ_EXTRACT_RECORD --- *
10:55:36.619 (366325) exited READ_EXTRACT_RECORD (stat=400, seqno=-1, rba=-1156490736)
ggserr.log:
2012-06-02 10:55:36 WARNING OGG-00869 Oracle GoldenGate Delivery for ODBC, lien.prm: Parameter #: 1 Data Type: 129 DB Part: 5 Length: 9 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 2 Data Type: 129 DB Part: 5 Length: 9 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 3 Data Type: 129 DB Part: 7 Length: 5 Max Length: 128 Status: 8 Precision: 128 Scale: 0 Unavailable Parameter #: 4 Data Type: 129 DB Part: 5 Length: 6 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 5 Data Type: 129 DB Part: 7 Length: 8 Max Length: 56 Status: 8 Precision: 56 Scale: 0 Unavailable Parameter #: 6 Data Type: 129 DB Part: 5 Length: 6 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 7 Data Type: 129 DB Part: 7 Length: 9 Max Length: 128 Status: 8 Precision: 128 Scale: 0 Unavailable Parameter #: 8 Data Type: 129 DB Part: 7 Length: 8 Max Length: 15 Status: 8 Precision: 15 Scale: 0 Unavailable Parameter #: 9 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 8 Precision: 23 Scale: 3 Unavailable Parameter #: 10 Data Type: 129 DB Part: 5 Length: 5 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 11 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 6 Precision: 23 Scale: 3 Data Overflow Parameter #: 12 Data Type: 129 DB Part: 7 Length: 13 Max Length: 512 Status: 8 Precision: 0 Scale: 0 Unavailable Parameter #: 13 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 8 Precision: 23 Scale: 3 Unavailable Parameter #: 14 Data Type: 129 DB Part: 7 Length: 1 Max Length: 1 Status: 8 Precision: 1 Scale: 0 Unavailable Native Error: 0, 0 State: 0, 22007 Class: 0 Source: Line Number: 0 Description: Invalid date format.
2012-06-02 10:55:36 WARNING OGG-01004 Oracle GoldenGate Delivery for ODBC, lien.prm: Aborted grouped transaction on 'AWO_CUBE.LIEN', Database error -2147217887 ([SQL error -2147217887 (0x80040e21)] Parameter #: 1 Data Type: 129 DB Part: 5 Length: 9 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 2 Data Type: 129 DB Part: 5 Length: 9 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 3 Data Type: 129 DB Part: 7 Length: 5 Max Length: 128 Status: 8 Precision: 128 Scale: 0 Unavailable Parameter #: 4 Data Type: 129 DB Part: 5 Length: 6 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 5 Data Type: 129 DB Part: 7 Length: 8 Max Length: 56 Status: 8 Precision: 56 Scale: 0 Unavailable Parameter #: 6 Data Type: 129 DB Part: 5 Length: 6 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 7 Data Type: 129 DB Part: 7 Length: 9 Max Length: 128 Status: 8 Precision: 128 Scale: 0 Unavailable Parameter #: 8 Data Type: 129 DB Part: 7 Length: 8 Max Length: 15 Status: 8 Precision: 15 Scale: 0 Unavailable Parameter #: 9 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 8 Precision: 23 Scale: 3 Unavailable Parameter #: 10 Data Type: 129 DB Part: 5 Length: 5 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable Parameter #: 11 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 6 Precision: 23 Scale: 3 Data Overflow Parameter #: 12 Data Type: 129 DB Part: 7 Length: 13 Max Length: 512 Status: 8 Precision: 0 Scale: 0 Unavailable Parameter #: 13 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 8 Precision: 23 Scale: 3 Unavailable Parameter #: 14 Data Type: 129 DB Part: 7 Length: 1 Max Length: 1 Status: 8 Precision: 1 Scale: 0 Unavailable Native Error: 0, 0 State: 0, 22007 Class: 0 Source: Line Number: 0 Description: Invalid date format ).
report:
2012-06-02 10:55:36 WARNING OGG-01004 Aborted grouped transaction on 'AWO_CUBE.LIEN', Database error -2147217887 ([SQL error -2147217887 (0x80040e21)]
Parameter #: 1 Data Type: 129 DB Part: 5 Length: 9 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable
Parameter #: 2 Data Type: 129 DB Part: 5 Length: 9 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable
Parameter #: 3 Data Type: 129 DB Part: 7 Length: 5 Max Length: 128 Status: 8 Precision: 128 Scale: 0 Unavailable
Parameter #: 4 Data Type: 129 DB Part: 5 Length: 6 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable
Parameter #: 5 Data Type: 129 DB Part: 7 Length: 8 Max Length: 56 Status: 8 Precision: 56 Scale: 0 Unavailable
Parameter #: 6 Data Type: 129 DB Part: 5 Length: 6 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable
Parameter #: 7 Data Type: 129 DB Part: 7 Length: 9 Max Length: 128 Status: 8 Precision: 128 Scale: 0 Unavailable
Parameter #: 8 Data Type: 129 DB Part: 7 Length: 8 Max Length: 15 Status: 8 Precision: 15 Scale: 0 Unavailable
Parameter #: 9 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 8 Precision: 23 Scale: 3 Unavailable
Parameter #: 10 Data Type: 129 DB Part: 5 Length: 5 Max Length: 21 Status: 8 Precision: 20 Scale: 0 Unavailable
Parameter #: 11 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 6 Precision: 23 Scale: 3 Data Overflow
Parameter #: 12 Data Type: 129 DB Part: 7 Length: 13 Max Length: 512 Status: 8 Precision: 0 Scale: 0 Unavailable
Parameter #: 13 Data Type: 129 DB Part: 5 Length: 23 Max Length: 29 Status: 8 Precision: 23 Scale: 3 Unavailable
Parameter #: 14 Data Type: 129 DB Part: 7 Length: 1 Max Length: 1 Status: 8 Precision: 1 Scale: 0 Unavailable
Native Error: 0, 0
State: 0, 22007
Class: 0
Source: Line Number: 0
Description: Invalid date format
Edited by: chris.baron on Jun 3, 2012 10:36 AM

Not sure if this helps at all...
Datetime Pairs in Oracle BI (OBIEE) - Days, Hours, Minutes, Seconds
http://www.kpipartners.com/blog/bid/83328/Datetime-Pairs-in-Oracle-BI-OBIEE-Days-Hours-Minutes-Seconds
UPDATE: Sorry... didn't see this was for GoldenGate.
Edited by: 829166 on Jun 22, 2012 7:36 AM

Date Format error while loading *.dat file to Sataging .

Hi All ,
Loading data from *.dat file in to Staging , the dat file contains data for date in 'MM-DD-YYYY' format which is String , when it loading by control file it produce the error date format is not supported .I think ti required DD-MM-YYYY format . Is their any properties to change the date format or else need to write the function for converting date format .
I am using OWb 10g Release 1 , with same DB .
Please guide me
Thanx in advance
Regards ,

Hi,
Before loading into staging, you can use Expression operator to convert the CHAR into DATE with something like this:
TO_DATE('01-02-2005','MM-DD-YYYY')
Hope this helps.

Date format error while schedule a job!

Dear all,
I am using 11gR1 on Linux OS.
I have to schedule a procedure that runs in mid night after 12:00 using dbms_scheduler.
This is the code i am writing:
begin
dbms_scheduler.create_job(
job_name => 'ATT_LATE_MIS_PRC_JOB'
,job_type => 'PLSQL_BLOCK'
,job_action => 'begin att_late_mis(1); end; '
,start_date => '16/10/2009 12:05 AM'
,repeat_interval => 'FREQ=DAILY'
,enabled => TRUE
,comments => 'Attendance MIS');
end;
and this is the error i am getting:
ORA-01843: not a valid month
ORA-06512: at line 2
I don't know how to format date for this procedure. All i need to do is to simply schedule a procedure that runs at 12:05 daily.
Thanks, Imran

misterimran wrote:
Dear all,
I am using 11gR1 on Linux OS.
I have to schedule a procedure that runs in mid night after 12:00 using dbms_scheduler.
This is the code i am writing:
begin
dbms_scheduler.create_job(
job_name => 'ATT_LATE_MIS_PRC_JOB'
,job_type => 'PLSQL_BLOCK'
,job_action => 'begin att_late_mis(1); end; '
,start_date => '16/10/2009 12:05 AM'
,repeat_interval => 'FREQ=DAILY'
,enabled => TRUE
,comments => 'Attendance MIS');
end;
and this is the error i am getting:
ORA-01843: not a valid month
ORA-06512: at line 2
I don't know how to format date for this procedure. All i need to do is to simply schedule a procedure that runs at 12:05 daily.
Thanks, ImranSee the following link
Error with dbms_scheduler.create_job
And try the following code (Haven't tested)
begin
   dbms_scheduler.create_job(
       job_name = 'ATT_LATE_MIS_PRC_JOB'
      ,job_type = 'PLSQL_BLOCK'
      ,job_action = 'begin att_late_mis(1); end; '
      ,start_date = '16-NOV-2009 12:05:00 AM'
      ,repeat_interval = 'FREQ=DAILY'
      ,enabled = TRUE
      ,comments = 'Attendance MIS');
end;
/

Date format interfering with interactive report

My APEX version is 3.1.1.00.09.
I'm using a method described elsewhere to change the global date format of my application. I have application items for a start and end date. I have two application processes, one for On Load: Before Header, the other for On Submit: After Page Submission - Before Computations and Validations. They both do:
DBMS_SESSION.SET_NLS(param => 'NLS_DATE_FORMAT', value => '''fmMM/DD/fmYY''')
Okay, all is well with that, my dates seem to stay the way I want them to. Since our upgrade I'm going through each section of my application and updating as necessary, and I particularly want to use the interactive reports. They work fine when the page is loaded, but if I change any options on the interactive report and submit it, I get an "ORA-01843: not a valid month" error. If I refresh the page, everything works as it should.
What can I do to get around this, or do I have something wrong with my method that is causing this to happen?
Chris

Hi Chris,
I tried to replicate this, but could not. Now granted, I tried this using the new "modern" method of controlling the default application date format via the new application Globalization attribute "Application Date Format". I set the Application Date Format to fmMM/DD/fmYY and my IR on EMP worked just fine.
If you can replicate this on apex.oracle.com (using Application Date Format), I'd be happy to take a look at it.
Joel

Timestamp/Date format error with Java 1.6

Similar Messages

Maybe you are looking for