Skip to Main Content
Forums

Java Programming

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Date Parsing Issues with TZ ?

java4everMar 21 2014 — edited Mar 22 2014

Hi Experts,

  I have a date in the following String format "2013-03-28,19:37:52.00+00:00"  and post processing I am converting this to following String as per prevailing logic "2013-03-28,19:37:52.00+0000"  (This is existing code and no changes have been Made here for last few years)
And the using this SDFormat i.e  new SimpleDateFormat("yyyy-MM-dd,HH:mm:ss.Sz")   for conversion to Date Object

We are suddenly getting this exception now can't figured out what has changed ?

java.text.ParseException: Unparseable date: "2013-03-28,19:37:52.00+0000"

at java.text.DateFormat.parse(DateFormat.java:357)

Kindly suggest.

--

j4r
This post has been answered by java4ever on Mar 22 2014
Jump to Answer

Comments

Luís Gustavo Lira

Hi, did you check if this executions are using the same SQL plan hash value ?

Hesh

Hi Luis,
Thanks for your response.. Yes both the plan hash values are the same.. I have verified ASH
Regards
Hesh

Luís Gustavo Lira

In this case I would start by generating AWR Compare Period Report to try to identify relevant differences in the environment as a whole.
Check mainly in the Top Timed Events, what is consuming significant percentage of DB time and if there are big differences between the periods.
You can also:
- generate an AWR SQL Report for this specific SQL for each execution period.
- run ASH Report for this SQL to both periods
- trace the session that are running the query to collecting SQL Execution information
- run a SQL Tuning Advisor for this query to check if there is any recomendation

Hesh

Thanks Luis,
In my initial post I have posted the ASH comparison for both the dates.. I am mentioning here again, direct path reads are the difference.
What should I look into more from here? any specific information from AWR that can help me?

image.png

Regards
Hesh

Hesh

From AWR I got user I/O is different ... we are reading a huge table...

image.png

Regards
Hesh

Luís Gustavo Lira

During heavy batch periods, waits on direct path read are quite normal, but compare average wait time from both periods for direct path read to check if this indicates any issue related to I/O Performance Problems.
If possible, place the AWR Top Timed Events here as well, it can be the compare period or one of each period to check for more details and if you have other related waits.
Also check in ADDM report if there are any IO issue related.

Hesh

Thanks Luis,
As that is a heavy job we schedule that job to execute alone. When the above mentioned Insert SQL runs, there is no other SQL runs, means no other SQL executions are going on. I even verified in ASH if there are any other SQL IDs, but nothing there.
Regards
Hesh

Hesh

Hi,
Any more inputs I can get to dig more into this please? like any doc or any blogs to understand more about User I/O, PGA and 'direct path reads' ... unfortunately I am getting nowhere with this. Appreciate your help on this.

Regards
Hesh

Sridhar_Nalla

Did you check the ETL server load between 5AM and 7AM. Either load on the ETL Server or network (5AM-7AM) causing the delay in the batch execution between 5AM and 7AM.

1 - 9
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Apr 19 2014
Added on Mar 21 2014
3 comments
1,768 views