CUIC version 8.5.4 Date format bug?

Our contact centre is running on version 8.5.4 and even when I am logged in on the U.K. vrsion, my date formats on the Agent Skill Group 27 report are American format. It isn't the end of the world but I was curious to see if anyone else had similar issues and if there are any other bugs in the reporting that I need to be aware of?

Its working, previously it was English-US.Now I changed to English UK and its working perfectly.
Thanks Jameson for your kind support.

Similar Messages

New version of Flash, same auto format bugs

When Flash CS3 came out, the first thing I noticed when I sat
down to use it for the first time was that the ActionScript Auto
Format was unusable because of bugs that were present in it. One of
the bugs was that it would actually REMOVE parenthesis from certain
lines of code, and next to object initializations. This made it
unusable because it would constantly break programs. So pretty
much, in CS3 you had this Auto Format feature (that worked
wonderfully in previous versions of Flash) that was just there and
couldn't actually be used by anyone who was going to do any sort of
serious programming. This was pretty hard to believe being that
Auto format worked fine in previous versions of Flash (I can't
remember if it was in 8 or after 8 it broke).
So I take my time, go to the Flash CS3 bug reporter, and
report the bug.
Fast forward a few years. CS4 comes out. I immediately buy
the upgrade. What's the first thing I look at? The Auto formatter.
To my dismay, it still contains the exact same bugs it did when CS3
came out years ago. I almost felt like asking for a refund. I don't
think it's too high of an expectation for a bunch of obvious bugs
to be fixed.
Then I have to ask myself, am I the only person on planet
earth who uses the ActionScript Auto format? I used to love it to
just clean up my code and indent it. I mean right now, it's just
like "there". I don't see how anyone can actually be using it in
its current state. Adobe should either get rid of it or fix it,
preferably fix it.
I guess my question is, to anyone really, or preferably
Adobe, what's going on here? Is this ever going to be fixed? It's
not really fair that a feature that used to work perfectly has been
broken in the last two major versions of Flash. Is there any
possible way for Adobe to send down a fix for this, or is there a
way for the user to fix it on their own?
Thanks in advance.

Never mind, I chose this option:
http://fpdownload.macromedia.com/pub/flashplayer/latest/help/install_flash_player.exe
It finally allowed me to install. It is working. Adobe, I am disappointed that this update was so frustrating to install. Shame on you.

Editable and Read-Only Date Picker have different display formats -- Bug?

Hi all,
This is a follow on to a previous posting about getting a Date Picker field to display read-only (Date Picker and Read-Only Condition works on LAST state of element
Now past that hurdle, I have noticed something about the date picker field when it is displays read-only. Namely, the date format is not the format selected, nor does the read-only date format comply with the format mask in the source section.
I've modified my small test app to work as intended in order to demonstrate this feature. I also opened it up so everyone can see it <blush>. You can find it here: http://htmldb.oracle.com/pls/otn/f?p=42513: Please navigate to the Update Project tab.
When a project in Program One through Four is selected (which has a Spec Committed date), the date is displayed DD-MON-YY format. When a project the other Programs (which do not have Spec Committed dates at the time of this writing) are selected, and a date value selected with the date picker, the date is displayed in the anticipated DD-MON-YYYY format.
Anyone else notice this, or have I just missed something obvious?
Thanks,
Petie

I'm not sure why this happens but to work around it I added this before header process code to the page:
execute immediate 'alter session set nls_date_format = ''DD-MON-YYYY''';
Scott

Cell data format problem

Hello,
I just began using the new version of Numbers.
I tried to make a distance-speed-time function and have it as hour, minute and second but when I switch from automatic data format to custom data format (Duration) and go to the next cell to do the same, it switch back to automatic data format and I can't have it as time but just a a number with decimals.
What can I do ?

I have a similar issue.
Every number I enter is understood by Numbers as a date.
199 becomes the date 1/1/199 00.00.00 when I try and change the auto format it jumps right back to the date.
I have to format the cell to be a number before I enter a value.
is your system language english or non english? I have a suspicion it's a locale bug (one that Apple QA should have found had they done any testing...)

Date format in OBIEE 11g is changed.

Hi,
we have installed 11.1.1.5 on linux x86-64bit machine. after that we upgraded the OBIEE 10.1.3.4.1 rpd and catalog to OBIEE 11.1.1.5.
everything was working fine at this stage.
After that we did some development in 10g ... and again upgraded the rpd and catalog to 11.1.1.5 using upgrade assistant.
but after that the date format in all the date prompts on the dashboards is changed to MM/dd/YYYY.
How to change it back to dd/MM/YYYY?

Hi Visal,
Please award points it is useful the above answer.
2. After installation the date format default : DD-MM-YYYY.
I am not sure, I think you need install patch file in this version on your server or you need to change ALTER SESSION set NLS_DATE_FORMAT = 'DD/MM/YYYY'.
I though this is bug in server version.
What server its showing this format means(Unix,Linux,AIX)?
Award points it is useful.
Thanks,
Satya

Date Format in Portal Report

Hi,
I have created a SQL Report with following select statement. Looks like portal has default format mask for date type as 'DD-MM-YY'.
If I put DD-MM-YYYY or DD-MM-RRRR in Format Mask field in Column Formatting screen, the reports generates 04-10-0002 . It should
be 04-10-2002.
select process_id, last_update_date
from obm
where process_id like (:process_id)
I tried to use the to_char function as following. But it errors ORA-06502:PL/SQL:numeric or value error. Even though it works fine in
my sqlplus session.
select process_id, to_char(last_update_date, 'DD-MM-YYYY')
from obm
where process_id like (:process_id)
Does anyone have any idea?
Thanks

Hi,
Which version of portal are you using? The error with to_char comes in 30984. This is a bug. The bug no is 2567445. A one-off has been issued. Please look in metalink for it. And for the date formatting in the column formatting section the formatting should work fine. Please check the data in your table.
Thanks,
Sharmila

Date format in Query Result Window

In recent versions on OSD (trying with V3.2.20.09 Build MAIN-09.87) I've been unable to change the date format for results shown in the query results window via the NLS settings in Preferences, it's the same for other users on v3 in my area. Can anyone advice on whether anything can be done to resolve this issue or is there a bug in recent additions of OSD
Frustrating having a result show as 01-DEC-12 and I don't know whether it's 01-DEC-2012 or our default date of 01-DEC-4712 without having to hard code a to_char in my sql which I don't want to be doing all the time to analyse my results
I have an old version 1.5.4 Build MAIN-5940 and changing the NLS settings in preferences refrects correctly in the query results window
Any advice appreciated, Thanks

Thanks, looks like it's permission, tried on a different database supposed to be the same and it works when I update the preferences or run the alter session statement. Call to my admins to get on the case
Ta
for anyone else having simular issues, help are the statements I've tried to confirm it's permissions
alter session set NLS_DATE_FORMAT = 'DD-MON-RR HH24:MI:SS'; -- Original
alter session set NLS_DATE_FORMAT = 'DD-MON-RRRR HH24:MI:SS';
commit;
SELECT *
FROM nls_session_parameters
Edited by: lakeuk on 14-Nov-2012 06:37

Wrong date format when creating a universe based on a MS Analysis cube

Hi,
When creating a universe based on a MS Analysis 2008 cube the date objects from the cube are created in the universe with CHAR format when it should be DATE format
I have tried to resolve the issue by modifying the date object in the universe with MDX but with little success.
I wonder if it is an error in the cube and that it actually should be possible to get the correct date format from the cube when creating the universe automatically in the universe design tool.
The date object is organised in a hierarchy.
Any ideas? - both to resolve the issue by using MDX in the universe object properties or in the cube.
The universe design tool is version 4.0 SP2 patch 5
/Kim

Oh I knew I was missing something. Ok version 2.
I think in general this approach would work. I assumed you are starting from 1 and resetting to 1.
There should be error handling and so forth that is not here. Probably some details need to be tweaked.
So the key thing here AFAIK is to put the sequence reset in an autonomous procedure. Exactly how to do that may need to be modified.
PS this version has a bug. After the reset needs to change the increment of the sequence back to 1.
and I left that out. oops!
/* testtrigger */
/* previously:
create table mytable (
myprimary_key number(10) primary key,
column1 number(2)
create sequence mysequence
start with 1
increment by 1
maxvalue 99
nocache;
create table mylastdate (lastdate date);
insert into mylastdate(lastdate) values (trunc(sysdate));
create or replace procedure reset_mysequence (in_correction number) is
pragma autonomous_transaction;
begin
execute immediate 'alter sequence mysequence INCREMENT BY ' || in_correction || ' MINVALUE 1';
update mylastdate set lastdate = trunc(sysdate);
commit;
end;
show errors;
create or replace trigger mytrigger
before insert on mytable for each row
declare
tmpdate number(8) := null;
lastdate_used number(8) := null;
correction number := null;
lastseq number(2) := null;
begin
if INSERTING then
tmpdate := to_number(to_char(sysdate,'YYYYMMDD'));
select to_number(to_char(lastdate,'YYYYMMDD')) into lastdate_used
from mylastdate;
select mysequence.currval into lastseq from dual;
/* when this displays in the forum it shows lt gt as nothing on the screen
so this should be lastdate not equal to tmpdate */
if lastdate_used <> tmpdate and lastseq > 1 then
correction := -(lastseq - 1);
reset_mysequence(correction);
end if;
:new.myprimary_key := (tmpdate * 100) + mysequence.nextval;
end if;
end;
show errors;
Edited by: lake on Nov 30, 2010 10:39 AM
Edited by: lake on Nov 30, 2010 10:52 AM

EA1 - Cannot Change Date Format in SQL Results

In version 1.2, I used to go to Tools > Preferences > Database > NLS Paramters and change the date format there. The change would then be reflected in the SQL results for date columns.
When I try to do the same thing in 1.5 EA1, the date format is always the same, DD-MON-RR, no matter what I put in the date format setting under NLS Paramters.
Am I missing something?
Thanks.

Just a quick post to make sure that the bug you logged takes into account all NLS parameters :), as this does not concern only dates but also timestamp formats, decimal and group separators as well, and probably all of the NLS parameters I assume.

Af:table filter date format : task-flow navigation issue

hi
When trying to use the date format configured on the Entity Object, with Format Type as Simple Date and Format as "dd-MM-yyyy", there seems to be a problem when using task-flows.
The approach involves an explicitly configured attributeValues binding to use in f:validator and af:convertDateTime components in the af:inputDate in the filter facet, as discussed in the forum thread "af:table filter date format"
at af:table filter date format
I used JDeveloper 11.1.1.3.0 to create the example application
in http://www.consideringred.com/files/oracle/2010/TableFilterDateFormatIssueApp-v0.03.zip
- The page filterEmp.jspx shows expected behaviour, the filter uses the configured date format and there is no problem when navigating to another page and back.
see the screencast at http://screencast.com/t/CtQ9rsVFH3k
- The page menuBTFPage.jspx allows for some navigation after using the filter resulting in the filter showing a date in the wrong format, using scenario (sc1)
-- (sc1-a) : run menuBTFPage.jspx
-- (sc1-b) : on "menu-btf : menu", click the "do go-filter-emp-btf" link
-- (sc1-c) : on "filter-emp-btf : filterEmpFragment", filter on HireDate using "10-03-2005"
-- (sc1-d) : click the "do goReturnSuccess" button
-- (sc1-e) : back on "menu-btf : menu", click the "do go-filter-emp-btf" link again
-- (sc1-f) : back on "filter-emp-btf : filterEmpFragment", see the HireDate filter value in the wrong format as "2005-03-10"
-- (sc1-g) : click the "do goReturnSuccess" button again, which results in an error "The date is not in the correct format."
see the screencast at http://www.screencast.com/t/ORHauBd3oQ
questions:
- (q1) Can the behaviour in scenario (sc1) be reproduced?
- (q2) Why is the filter value in the wrong date format in step (sc1-f)?
- (q3) What can be done to have the filter value consistently in the configured date format, so that errors as in step (sc1-g) can be avoided?
many thanks
Jan Vervecken

hi
First a short summary of relevant aspects of service request 3-2190488381:
- development has reviewed bug 10193260
- development identified some code where a pattern was not applied and started fixing the problem
- out of the blue, development asked "Will clearing out the filter field completely when moving out of ataskflow be an acceptable behavior ?"
- I pointed out some concerns (even in a phone call with development), but development did not see any alternative not "perceived to be very risky because of the current design", so the question whether the clearing-all-filter-fields approach would be acceptable became superfluous.
- following this, bug 10193260 suddenly became an enhancement request (for reasons I still don't understand)
- a workaround was suggested (for behaviour not perceived as a bug), "Clearing the search fields during taskflow exit in the backing bean (in the app)." for which I also received a modified version of my example application TableFilterDateFormatIssueApp-v0.04.zip with an implementation of the suggested workaround
As an exercise to try an understand the suggested workaround (an because my example application seemed to have been modified using the currently yet-to-be-released JDeveloper 11.1.1.4.0) I re-implemented it in the example application
at http://www.consideringred.com/files/oracle/2010/TableFilterDateFormatIssueApp-v0.05.zip
It has a filter-emp-workaround-btf task-flow with a method-call activity on a managed-bean method, responsible for clearing the search fields, resulting in behaviour where the error "The date is not in the correct format." does not occur,
as can be seen in the screencast at http://screencast.com/t/Nq7TkkRQ
public void clearFilterFields()
    BindingContainer vBindingContainer =
      BindingContext.getCurrent().getCurrentBindingsEntry();
    DCBindingContainer vDCBindingContainer = (DCBindingContainer)vBindingContainer;
    DCDataControl vDCDataControl = vDCBindingContainer.getDataControl();
    ApplicationModule vApplicationModule = vDCDataControl.getApplicationModule();
    ViewObject vViewObject = vApplicationModule.findViewObject("EmployeesVOVI");
    ViewCriteriaManager vViewCriteriaManager = vViewObject.getViewCriteriaManager();
    vViewCriteriaManager.clearViewCriterias();
    vViewObject.clearCache();
}Because the managed-bean method requires access to the ADF Model binding layer to get to the View Object instance used for the filtered table, the method-call activity has a page element configured in DataBindings.cpx referring to the same usageId as the page element for the page fragment showing the filtered table. So that both the method-call and view activity depend on one and the same Binding Container (e.i. PageDef file).
The method-call activity, responsible for clearing the search fields, would need to be called before each task-flow-return activity.
As there can be multiple view activities with multiple filtered tables in a bounded task-flow, would that result in multiple method-call activities responsible for clearing search fields (all to be called before each task-flow-return activity)?
It looks like a more general/generic approach is desirable for the suggested workaround to be feasible.
- (q5) Does the suggested workaround imply (as bug 10193260 is not a bug) that all bounded task-flows with filtered tables should implement it to avoid errors about formatting?
thanks
Jan

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.

TES 6.1.x - custom date format

In 5.3.1. I was able to create my own custom dates. In 6.1 I create the format, click on Add Custom Format - click OK. When I go back to Variables - System Variables - System Date - Date Format I expect to see it in the list so I can select it, but it's not - I have to do all the steps all over again. Is this some kind of bug or is just me?

Weird
I am going from base 6.1.0.133 release to the March bundle
After applying the bundle, according to the read me I think I should be at:
Master 6.1.0.198
Client Manager which I assume = TESPlugin and TESWebClient
From logs
Client Manager
Client Manager version: 6.1.0.138
Java version: 1.6.0_43
Java Virtual Machine version: 20.14-b01
TIDAL Enterprise Scheduler: version 6.1.0.189
Java version: 1.6.0_43
Java Virtual Machine version: 20.14-b01
Adapter Host: version 6.1.0.133
Java version: 1.6.0_43
Java Virtual Machine version: 20.14-b01
Client Manager version: 6.1.0.138
Java version: 1.6.0_43
Java Virtual Machine version: 20.14-b01
Master
TIDAL Enterprise Scheduler: version 6.1.0.189
Java version: 1.6.0_43
Java Virtual Machine version: 20.14-b01
Adapter Host
Adapter Host: version 6.1.0.133
Java version: 1.6.0_43
Java Virtual Machine version: 20.14-b01
Job Adapters
JDBC Adapter 2.1.0.192 <-- I don't see this in March bundle (is there another bundle?
All my other adapters seem to be correct based on readme.
Any tricks I am missing I replaced all the files in the appropriate area w/ services stopped and restarted

Export Date format

Hi,
I have just installed the last sql developer release (1.5.1.5440) and i have a problem to export date. For information, I am connected to a Oracle 10g DB on windows.
I have set the same NLS_PARAMETERS from the sql developer 1.2 version, but i have not the same result.
Here is a date export with sqldeveloper 1.2 below :
Insert into VALEURS (ID_VALEUR,DATE_CREATION) values (189,to_date('2008/01/28','DD/MM/RR'),null,null);
Here is a date export with the last sqldeveloper release below :
Insert into VALEURS (ID_VALEUR,DATE_CREATION) values (189,to_date('2008-01-28','DD/MM/RR'),null,null);
I have not found yet the parameter to set. Please, help me.

Hi,
This is as reported on
Re: SQL Dev 1.5 Export Wizard can't export dates?
Current workaround is changing the Date Format of the export script manually using Find - Replace to follow SQL Dev's format (Note : the time information will be set to 00:00:00 as if no timestamp given on the insert script).
Or wait until the team find and fix this bug on the next release.
Regards,
Buntoro

Data format inconsistency problem on Discoverer 4i plus and Desktop 4.1

I encountered 'data format inconsistency' problem when using
Discoverer 4i plus web version vs Desktop version 4.1 to run the
same report :-
The result returned by Desktop version is as following:-
Employee Count Percent Employee Count
Mgt 202 18%
Occ 891 81%
Other 1 0%
Percent 1094 100%
The result returned by 4i web version is like the following:-
Employee Count Percent Employee Count
Mgt 202 18%
Occ 891 81%
Other 1 0%
Percent 109400% 100%
Pls note that the Employee count column is 1094 in Desktop
version whereas in web version it's 109400%
After I export the data to Ms Excel, I obtained below result :-
Employee Count Percent Employee Count
Mgt 202 0.184644
Occ 891 0.814442
Other 1 0.000914
Percent 1094 1
I would like to know if this is Oracle Discoverer bug or it's a
known issues ?
Pls advise.
Thanks in advance.

Hi Discoverer Technical Team,
Could u pls response to that issue ?
Thanks and regards.

Invalid data format on EXPORTING table to SQL-FLAT FILE (Insert type)

Hi there!
Writing from Slovenia/Europe.
Working with ORACLE9i (standard version) on Windows XP with SQL-deloper 1.0.0.015.
FIRST SQL.-DEVELOPER IS GOOD TOOL WITH SOME MINOR ERRORS.
1.) Declare and Insert data EXAMPLE
drop table tst_date;
create table tst_date (fld_date date);
insert into tst_date values (sysdate);
insert into tst_date values (sysdate);
2.) Retriving date with SQLPLUS
SQL> select to_char(fld_date,'DD.MM.YYYY HH24:MI:SS') FROM TST_DATE;
23.10.2006 11:25:23
23.10.2006 11:25:25
As you see TIME DATA IS CORRECT.
When I EXPOPRT data TO SQL-insert type I got this result IN TST_DATE.SQL file:
-- INSERTING into TST_DATE
Insert into "TST_DATE" ("FLD_DATE") values (to_date('2006-10-23','DD.MM.RR'));
Insert into "TST_DATE" ("FLD_DATE") values (to_date('2006-10-23','DD.MM.RR'));
As you seel I lost TIME DATA.
QUESTION!
HOW CAN I SET PROPER DATE FORMAT IN SQL-DEVELOPER BEFORE I EXPORT DATA TO FLAT FILE.
Best regards, Iztok from SLOVENIA
Message was edited by:
DEKUS

A DATE-Field, is a DATE-Field and not a
DATE-TIME-Field.
The export-tool identifies a DATE-Field and exports
the data into date-format.This is not true. Oracle DATE fields include a time element.
To the original poster - I believe this is a bug in the current version.
See this thread for possible workarounds Bad Export format --- BUG ???
Message was edited by:
smitjb

CUIC version 8.5.4 Date format bug?

Similar Messages

Maybe you are looking for