EA1 - SQL History Timestamp format

Feature Request "SQL History Timestamp - NLS Date format" (Use the current NLS Date or Timestamp Format preference for formatting the Timestamp displayed in the SQL History window) is listed as Scheduled for 1.5 but has not been included.

Rakesh,
Thanks for the update. I assumed that it hadn't been done yet, as it is using a different "default" NLS date format from the results tab, which also is not picking up the NLS date format preference.

Similar Messages

4.0 EA3 - SQL History TIMESTAMP format

Timestamp in SQL history is incorrectly showing the dates. Seems like a mismatch between the Timestamp format; looks like in some case the is showing the dar as month and month as day; have some other scenarios where also the year is wrong.
This issue was also reported here: https://forums.oracle.com/thread/2593880

Hi Gary,
Is possible that it may be a "Locale" related issue, but I don't know where is the Locale value comming from, since my Windows and SQLDeveloper are in English. See screenshot... http://img822.imageshack.us/img822/5097/6jbq.jpg
Nevertheless, is true that I'm located in Spain, and in previous versions of SQL Developer, the IDE was in Spanish by default, and I had to edit the sqldeveloper.conf file, adding the following option (I like my tools in English)
AddVMOption -Duser.language=en
SQL Developer 4 is correctly showing in English without editing the file.
Regards

EA3/EA2 - SQL History Timestamp column

The formatting of the Timestamp column in the SQL History now uses the NLS Timestamp Format (yay!), but unfortunately does not cope with the seconds component of the format:
NLS Timestamp Format is DD-Mon-YYYY HH24:MI:SSXFF
Timestamp column in the SQL History displays as 25-Feb-2008 15:03:.
I assume from what has previously shown in the SQL History timestamp column (2/25/08 3:03 PM) that we do not record seconds in the SQL History timestamp. I don't really have a problem with that, but can we please trim the second and sub-second components from the format?
theFurryOne

Just to add, this specific problem has been fixed. Hiding of sec/mill-sec information is handled by ignoring 'S/F', '.X', ':X' fields . But keeping the bug open so that a more generic fix is made which will handle symbols like '#SSXFF' in time field.

SQL History not sorting by timestamp; new v4 TS format ?

I was worried that my SQL History was not accumulating post upgrade, as it did not appear as I expected.
I typically sort it by descending timestamp, but I'm finding that since installing the 4.0 production version that a different timestamp format on SQL History has taken hold, ignoring the NLS settings that I put in my preferences (which were not the default ones by the way for my territory and language, by the way).
I migrated all my settings from the previous installation I had ...sqldev4 ea3. previous migrations from v3 to v4 ea1 to v4 ea2 to v4 ea3 never disrupted my SQL History.
Now my recent entries are buried in the SQL History and won't show on top anymore, and the sorting by timestamp seems erratic making it impossible to see a chronological order of SQLs executed before and after the migration.
Is there a control for formatting the SQL History timestamps or do I need to go spelunking through xml files to alter a setting ?
Curiously,
Steve

A timestamp found inside one of my older "history.xml" files looks like this:
<timestamp><![CDATA[12/11/13 2:18 PM]]></timestamp>
A newer one looks like this:
<timestamp><![CDATA[12/17/13 20:54]]></timestamp>
It would probably give Xquery fits reconciling the different formats, sorting, eliminating older SQLs in the history according to one's preferences inside SQL Developer 4, etc.
I'm going back to the last early adopter release just to preserve history and sequence until the tool makers resolve the timestamp and the weird sort order problem.

SQL History and timestamp order

Hi, I have SQL Developer 12.84 (4.0.0.12).
Sql history forces MM/DD/RR format in Timestamp instead of NLS format: DD.MM.YYYY HH24:MI:SS.
As a consequence the sort order fails.
Played with C:\Users\<user>\AppData\Roaming\SQL Developer\SqlHistory files but each new entry ignores manual date changes and writes timestamp in strange format.
Any idea?

Already identified by developer team as:
Bug 17740406 - SQL HISTORY TIMESTAMP NOT SORTED AS DATE FOR NON-US LOCALES
Info based on: https://forums.oracle.com/thread/2601066 (why new thread)
This is important drawback in SQL Developer 4 for non US users. BTW, still not fixed in build 13.30 (4.0.0.13)

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.

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>

SQL History - returning wrong statement if history is sorted

I have searched the forum and not seen anything on this, but I have been getting the wrong SQL statement returned when I select Append/Replace.
I have statements going back to 12-Jan-06 (using 804 since 13-Jan-06, 796 since 12-Jan-06 and 715 last year), so I don't know if I have hit the aging limit or not (I think I counted 221 entries).
It seems to me that it works out the cursor position and then returns that statement number from the history - independently of resorting the history.
For example, if I sort from oldest to newest (based on timestamp) and then select the bottom statement (displays as newest) and Replace, I get the oldest statement in the worksheet. If I select the top statement (displays as oldest) and Replace, I get the newest statement in the worksheet.
This is further complicated by the fact that sorting on the Timestamp is doing an alpha-numeric sort, rather than a date sort. When sorting from oldest to newest, the bottom three timestamps are (in "oldest to newest" order) are:
1/23/06 10:58 AM
1/23/06 9:21 AM
1/23/06 9:31 AM
If I then remove the sorting, the statement returned is the correct one.

It was great to get the fix for the SQL History returning the right statement if sorted (we got it in v1184).
However v1215 still does a text sort on the TimeStamp column rather than a date sort, so 2PM comes before 9AM, etc.
Also, where is the format for the TimeStamp column coming from? As someone who doesn't live in the US and thinks that days should come before months in date formats (ie DD-Mon-YYYY), I am frustrated by yet another product that uses MM/DD/YY, despite my best efforts at telling it otherwise.

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

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 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

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

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 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.

SQL History behaviour

Can we have an option to switch to the JDeveloper behaviour for SQL History please ?
I am getting p'd off with Replace/Append in Raptor instead of just dbl-clicking on the line of SQL I want and having it replace whatever's there.

Thanks for your feedback. I haven't been able to reproduce your second issue so far, as to your first issue we will look at possible further improvements and I have filed a bug for this.
The SQL history implementation is different to JDeveloper, as we have included additonal information such as connection, timestamp, number of times executed. Are these useful to you?
Donal

EA1 - SQL History Timestamp format

Similar Messages

Maybe you are looking for