Need to change time zone in PI 7.3 system

Hi Experts,
I want to change the time zone in PI system to CET to IST.
Kindly help.
Thanks,
Hemanth

Hi Monica,
I have changed time but when I clicked save, it prompted for customizing rquest, what should I type into following options?
1. Table Content: TTZCU
2. Request: ___________?
Regards,
Hemanth.

Similar Messages

Auto update of time when changing time zones - PLEASE help.

I travel for a living and I can't figure out how to get this 8310 to auto update the time when I fly from one time zone to another. Can anyone help me with this? Thank you so much in advance!

I'm sorry to inform you that the blackberry does not have a feature like this yet. You can read this FAQ and it will give you some tips though.
Why doesn't my time update correctly when I change Time Zones? - BlackBerryFAQ.com
You would need to set that manually and enter the meeting times in accordingly.
Sorry!

Can I set calender invite to set at the same time, even when changing time zone. for example I am in the UK have set a meeting for 10am in NYC for weds, but when getting to NYC it is still set at 10am and doen't adjust to time zone?

Can I set my Calendar invites on a IOS 7 device to set at the same time, even when changing time zones. For example I am in the UK and need to set a meeting for 10am NYC time on Wednesday, but when I reach NYC I don't want the time zones to adjust which will then adjust my meeting I set in the UK to NYC time.

Here are the individual files for those that fear the my other file of virii.
Attachments:
HASP.vi ‏88 KB
File Setup.vi ‏11 KB
Gather and Output.vi ‏149 KB

Oracle Application Server 10.1.3 R3 - Change time zone

Hii All,
I am using Oracle application Server 10.1.3 R3 Version. I have installed this application server on my windows VISTA machine. On Concole, OracleAS showing GMT time. I need to set it to Indian timezone.
I have searched a lot but not getting success.
Can anybody help me, how to change time zone ?
Regards,

have a look at this document in metalink. might be helpful . i think you to apply a patch based ( download it from metalink according to your operating system and applicaiton server versions). in my case i have download 5632264 patch ( 10.1.2.0.2 AS & AIX OS).
Timestamps & time zones - Frequently Asked Questions
Doc ID: Note:340512.1
Thanks,

Changing time zones and synching

I have changed time zones and all the information in my palm is now messed up, having switched to match the current time zone. How do I change this without doing each one individually? I will also need to do this again when I go back to my former time zone.
Thanks!
Post relates to: Zire

I understand why it did it - I just need to know if there is a way to fix it so I don't have to deal with dates/times being messed up for three months. The difference in time zones is 10 hours, so it changes things drastically - not only by a few hours. Is there anything I can do?
Thanks.
Post relates to: Zire

6300 - Changing Time Zone (GMT+1) Changes All Cale...

I have a 6300 and a calendar full of important meetings and so on.
Last weekend we went on to GMT+1 hour (British Summer Time).
Changing the time settings in the phone to "GMT+1" changes all the calendar times to +1 hour as well.
Why does the phone do this (is this dumb or what !) ?
How can I get the phone NOT to change the calendar times whilst changing the time of day ?
Good wishes to all.
Simon
Solved!
Go to Solution.

Google calendar has resolved this problem for me by allowing Time Zone entries for Calendar items.
1. I now enter calendar entries with the local time in my Google Travel calendar.
2. I then duplicate the entry in my Google personal calendar and edit this entry to identify the destination Time Zone.
3. I then allow Google calendar to update my Outlook calendar. Entries there will show up with the destination time.
e,g. a flight departure from Madrid is scheduled for 6pm. It will show in my Google personal calendar and in my Outlook calendar as 2am the next day. It will still show in the Travel calendar as 6pm.
4. I let Ovi Suite synchronize my Nokia phone calendar with Outlook which inserts all entries with times for the appropriate time zone e.g. 2am in Madrid.
5. Now I no longer need to disable automatic Time Zone adjustment in my phone AND lie to the phone that I have NOT changed time zones whenever I change my phone clock for a new country (or Time Zone). In the Madrid example, my calendar entries while in Canada will show a 2am departure and when in Madrid will show a 6pm departure (local time).
Some benefits are:
1. Calendar times will show the local time for all entries.
2. No more calls home at 2am because I forgot the Time Zone differential.
3. No more missed appointments because I made an incorrect time adjustment.
3. Automatic Time Zone correction means my phone is always synchronized with local time. This is significant since I have observed that the phone's internal clock tends to drift. Automatic synchronization automaticallt corrects this.
Points to Consider:
1. Google is my primary calendar because I can control it's directionality.
2. Entries in my Google Travel calendar allow me to see the unadjusted times of Calendar entries, e.g. my Madrid flight is at 6pm. Since Google allows you to see multiple calendars simultaneously, I can see events with both destination and home times.
3. Google will only update one calendar to Outlook (my personal calendar) which is why the Time Zone adjusted times are updated in my Google personal calendar and then to Outlook.
4. Ovi Suite has insufficient controls on updates and sometimes will reinstall Outllok entries which have been deleted or changed. Because Outlook cannot update the Google calendars it or the Nokia calendar cannot corrupt my master calendar on Google.
5. This may not resolve all the convoluted Time Zone boundaries experience in the USA but should help.
6. Have had no problem with DST but also am not dealing with the convoluted Time Zone boundaries experience in the USA.
7. Before and currently I stll place a copy of the input data in the Description section of my Google calendar entries. These will show up in the Nokia Description unadjusted and immune from change due to outside causes.

Problem Changing Time Zones

Why does the Pre calendar change timezones automatically when traveling across the country? This is very frustrating! If I am in Los Angeles on Monday and get word of a meeting in New York at 12:00pm (noon) on Wednesday, I want to simply put the meeting into my calendar for Wednesday at noon. But after traveling across the country, my appointment for Wednesday has shifted forward 3 hours on my calendar because it thinks I had the meeting scheduled for 12:00pm WEST COAST TIME. The meeting now shows a start time of 3PM. If I change time zones again, the meeting on my calendar shifts again to reflect the change. My old palms didn't do this. The iphone doesn't do this. I think it is simply too much to ask of us to have to make time zone calculations in our heads before entering appointments. PLEASE FIX THIS ASAP.
DeltaDog
Post relates to: Pre p100eww (Sprint)
This question was solved.
View Solution.

This feature can be turned off so the time zone will not be updated but the time still will be.
If you open your launcher and then look for date and time(normally on the 3rd page). Once in here turn off "network time zone" this way the time zone will not update when traveling anywhere.

Set Time Automatically without changing time zones?

Is there a way to choose Set Time Automatically (in Settings/General/Date & Time) and not have Calendar change the times of my appointments when I change time zones?

Here's what solved my problem: NOT checking Set Time Automatically, and NOT checking Set Time Zone Automatically. Then manually selecting the proper time zone and city.
Doing that displays the correct local time, without changing iCal times.

Blackberry and changing time zones

Is there a way to make the Blackberry change according to local time zone? my other cell phones got the time from the carrier's system, and if i changed time zones the phone would display the local time it got from the tower. But the Blackberry stays on it's original time, regardless of where I am.
Steve

No, you can't change that. BlackBerrys do not automatically change with the timezone.
There are valid reasons for that, regarding the calendar and the way it adjusts the times of scheduled meetings.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Changing time zone

This isn't a Dreamweaver question but I thought someone here
might be able to help.
How do I change my server's time zone? Right now MySQL seems
to be timestamping every record with Mountain time. I would like it
to be Eastern by default.

MySQL lets you set the timezone on a pr. session basis. Here we first view a datetime, then change time zones, then view the same datetime again:
$ mysql
mysql> use information_schema
mysql> select CREATE_TIME from TABLES where CREATE_TIME is not NULL limit 1;
+---------------------+
| CREATE_TIME |
+---------------------+
| 2010-06-10 09:37:01 |
+---------------------+
1 row in set (0.03 sec)
mysql> SET SESSION time_zone = 'America/Los_Angeles';
Query OK, 0 rows affected (0.00 sec)
mysql> select CREATE_TIME from TABLES where CREATE_TIME is not NULL limit 1;
+---------------------+
| CREATE_TIME |
+---------------------+
| 2010-06-10 00:37:16 |
+---------------------+
1 row in set (0.03 sec)
Note how the displayed datetime is different. Wouldn't it be fine to call "SET SESSION time_zone"?

2007 US Daylight Savings change time zone support in JDK 1.3

Sun has supported the 2007 US Daylight Savings change in recent versions of its JDKs 1.4 and 1.5. It has made partial Daylight Savings changes to JDK 1.3, but it's not a complete implementation like in 1.4 and 1.5, because there is no support for past/future Daylight Savings rules, only a single current set of Daylight Savings rules per time zone.
Our Java application (running in the America/New_York time zone) seems to be doomed, because the likelihood of upgrading to JDK 1.4/1.5 seems slim (we have to upgrade a third-party product first and success is seeming more and more remote), and Sun claims to be unable to fully implement the Daylight Savings change in JDK 1.3.
If any Sun Java staff can explain the reasons for being unable to implement the change in 1.3 (or at least some kind of workaround that an individual JVM user could enable), please fill me in. Any pointers on cleanly setting up a custom workaround would be valuable too.
If there are other Java users in the same situation, please fill me in on your own plans if you can. Is anybody trying to pressure Sun or other vendors for a solution? Is anybody writing their own custom workaround?
More details....
What we really need is for the default TimeZone in JDK 1.3 (America/New_York on our machines) to work regardless of whether the date/time being checked is pre-2007 or post-2007. In particular, getOffset and inDaylightTime should work for both 2006 dates and 2007 dates. The JDK should return the correct values for 2006 dates, as well as the correct values for the 2007 US DST extension dates (03/12/2007-04/02/2007 and 10/29/2007-11/05/2007). This would enable parsing and formatting using SimpleDateFormat to work correctly as well. The TimeZone and SimpleDateFormat APIs are used throughout our application.
JDK 1.3.1_19 has an interesting workaround that depends on the current system time. Prior to Jan 1 2007, it will handle 2006 dates correctly but 2007 dates wrong. After Jan 1 2007, it will handle 2007 dates correctly but 2006 dates wrong. Either way, it is always wrong for some dates.
JDK 1.4.2_13 and 1.5.0_09 both handle 2006 and 2007 dates correctly.
If JDK 1.3 will never work for 2006 and 2007 dates, then I am contemplating two workarounds:
1. Set the default TimeZone to a custom implementation as soon after JVM startup as possible.
2. Avoid the default TimeZone entirely, changing our application code to rely on explicit custom TimeZones.
Prior related Java Forum topics:
* http://forum.java.sun.com/thread.jspa?forumID=31&threadID=645874 (Java Essentials - Java Programming) winds up referencing the JDK 1.4 patch as a solution, and there is some discussion about how future/historic dates affect applications
* http://forum.java.sun.com/thread.jspa?forumID=481&threadID=735038 (Deploying - Java Upgrade) just talks about 1.4 and 1.5 patches
* http://forum.java.sun.com/thread.jspa?forumID=481&threadID=717268 (Deploying - Java Upgrade) also just talks about 1.4 and 1.5 patches
* http://forum.java.sun.com/thread.jspa?forumID=37&threadID=703214 (Specifications - Java Virtual Machine (JVM)) also just talks about 1.4 and 1.5
Related Sun Java Bug Database bugs:
* http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6471271 reports the same issue with 1.3.1_19 that I am seeing and the reporter makes the same clarification, that past/future dates don't work at all still. Sun seems to indicate that it will not fix this in 1.3.1, and the 1.3.1_19 "hack" is it for 1.3.1.
* http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6391777 refers to updates in 1.3.1_18 to address Australia DST changes, and also indicates that past/future dates (or "historic" dates) won't work at all. It gives a little more rationale behind the difficulty of implementing this for 1.3.1.
* http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4257314 refers to the fixes in 1.4 to support historic DST dates.
Other articles:
* Sun Java article http://java.sun.com/developer/technicalArticles/Intl/USDST/ refers to 1.3.1_18 as "resolving" the DST issue - this is misleading because the solution in 1.3.1_18 is not complete like that in 1.4 or 1.5
* Server Side article http://www.theserverside.com/news/thread.tss?thread_id=42212 refers to fixes in 1.4 and 1.5 for the DST issue, and the discussion about 1.3 doesn't lead anywhere
Thanks for any info or advice available,
Jim

Hi KBarney
I think u have the correct data file. to make sure see the "zi" dir is backed up in ur java lib folder or not.
if u have suspicion than run the tzupdater tool again.
this tool must be run for each jre/java version on your machine separately.
I tried this on 1.4.2.13 and not on 1.5.0.10. here is the result:
C:\Program Files\Java\j2re1.4.2_13\bin>java -jar c:\tzupdater\tzupdater2006p\tzu
pdater.jar -t -v
java.home: C:\Program Files\Java\j2re1.4.2_13
java.vendor: Sun Microsystems Inc.
java.version: 1.4.2_13
JRE time zone data version: tzdata2006p
Embedded time zone data version: tzdata2006p
Validating the time zone data
Validation complete
C:\tzupdater\tzupdater2006p>java -jar tzupdater.jar test verbose
java.home: C:\Program Files\Java\jre1.5.0_10
java.vendor: Sun Microsystems Inc.
java.version: 1.5.0_10
JRE time zone data version: tzdata2006k
Embedded time zone data version: tzdata2006p
Validating the time zone data
/data/tzdata2006p.test:990: test failed: America/Managua
/data/tzdata2006p.test:1465: test failed: America/Havana
/data/tzdata2006p.test:1466: test failed: America/Havana
/data/tzdata2006p.test:1847: test failed: Cuba
/data/tzdata2006p.test:1848: test failed: Cuba
/data/tzdata2006p.test:2024: test failed: America/Campo_Grande
/data/tzdata2006p.test:2026: test failed: America/Campo_Grande
/data/tzdata2006p.test:2028: test failed: America/Campo_Grande
/data/tzdata2006p.test:2030: test failed: America/Campo_Grande
/data/tzdata2006p.test:2032: test failed: America/Campo_Grande
/data/tzdata2006p.test:2034: test failed: America/Campo_Grande
/data/tzdata2006p.test:2036: test failed: America/Campo_Grande
/data/tzdata2006p.test:2038: test failed: America/Campo_Grande
/data/tzdata2006p.test:2040: test failed: America/Campo_Grande
/data/tzdata2006p.test:2046: test failed: America/Cuiaba
/data/tzdata2006p.test:2048: test failed: America/Cuiaba
/data/tzdata2006p.test:2050: test failed: America/Cuiaba
/data/tzdata2006p.test:2052: test failed: America/Cuiaba
/data/tzdata2006p.test:2054: test failed: America/Cuiaba
/data/tzdata2006p.test:2056: test failed: America/Cuiaba
/data/tzdata2006p.test:2058: test failed: America/Cuiaba
/data/tzdata2006p.test:2060: test failed: America/Cuiaba
/data/tzdata2006p.test:2062: test failed: America/Cuiaba
/data/tzdata2006p.test:2471: test failed: America/Montevideo
/data/tzdata2006p.test:2472: test failed: America/Montevideo
/data/tzdata2006p.test:2475: test failed: America/Montevideo
/data/tzdata2006p.test:2476: test failed: America/Montevideo
/data/tzdata2006p.test:2479: test failed: America/Montevideo
/data/tzdata2006p.test:2480: test failed: America/Montevideo
/data/tzdata2006p.test:2483: test failed: America/Montevideo
/data/tzdata2006p.test:2484: test failed: America/Montevideo
/data/tzdata2006p.test:2487: test failed: America/Montevideo
/data/tzdata2006p.test:2494: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2496: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2498: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2500: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2502: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2504: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2506: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2508: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2510: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2516: test failed: BET
/data/tzdata2006p.test:2518: test failed: BET
/data/tzdata2006p.test:2520: test failed: BET
/data/tzdata2006p.test:2522: test failed: BET
/data/tzdata2006p.test:2524: test failed: BET
/data/tzdata2006p.test:2526: test failed: BET
/data/tzdata2006p.test:2528: test failed: BET
/data/tzdata2006p.test:2530: test failed: BET
/data/tzdata2006p.test:2532: test failed: BET
/data/tzdata2006p.test:2537: test failed: Brazil/East
/data/tzdata2006p.test:2539: test failed: Brazil/East
/data/tzdata2006p.test:2541: test failed: Brazil/East
/data/tzdata2006p.test:2543: test failed: Brazil/East
/data/tzdata2006p.test:2545: test failed: Brazil/East
/data/tzdata2006p.test:2547: test failed: Brazil/East
/data/tzdata2006p.test:2549: test failed: Brazil/East
/data/tzdata2006p.test:2551: test failed: Brazil/East
/data/tzdata2006p.test:2553: test failed: Brazil/East
/data/tzdata2006p.test:3451: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3452: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3453: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3454: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3455: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3456: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3457: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3458: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3459: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3460: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3461: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3462: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3463: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3464: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3465: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3466: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3467: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3468: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3469: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3470: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3471: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3791: test failed: ART
/data/tzdata2006p.test:3814: test failed: Africa/Cairo
/data/tzdata2006p.test:3844: test failed: Asia/Amman
/data/tzdata2006p.test:3848: test failed: Asia/Amman
/data/tzdata2006p.test:3852: test failed: Asia/Amman
/data/tzdata2006p.test:3856: test failed: Asia/Amman
/data/tzdata2006p.test:3860: test failed: Asia/Amman
/data/tzdata2006p.test:3887: test failed: Asia/Damascus
/data/tzdata2006p.test:3908: test failed: Asia/Gaza
/data/tzdata2006p.test:3911: test failed: Asia/Gaza
/data/tzdata2006p.test:3915: test failed: Asia/Gaza
/data/tzdata2006p.test:3919: test failed: Asia/Gaza
/data/tzdata2006p.test:3923: test failed: Asia/Gaza
/data/tzdata2006p.test:4035: test failed: Egypt
/data/tzdata2006p.test:4901: test failed: Australia/Perth
/data/tzdata2006p.test:4902: test failed: Australia/Perth
/data/tzdata2006p.test:4905: test failed: Australia/Perth
/data/tzdata2006p.test:4906: test failed: Australia/Perth
/data/tzdata2006p.test:4909: test failed: Australia/Perth
/data/tzdata2006p.test:4910: test failed: Australia/Perth
/data/tzdata2006p.test:4914: test failed: Australia/West
/data/tzdata2006p.test:4915: test failed: Australia/West
/data/tzdata2006p.test:4918: test failed: Australia/West
/data/tzdata2006p.test:4919: test failed: Australia/West
/data/tzdata2006p.test:4922: test failed: Australia/West
/data/tzdata2006p.test:4923: test failed: Australia/West
Validation tests failed.
-Ranjan

Need to change time on some photos in iPhoto

Hi- I have no real experience with automator, but I think it could help me out here.
I have 1500 photos taken on a 2 week trip. I am going to put the best of them together as a slide show. The photos were taken with 5 different peoples cameras and none of the cameras were set to the same time. I would like to change the times on the photos data so that the photos will sort correctly for easy comparison. (often, all 5 people were shooting the same thing at almost the same time...) I can change the times individually in iPhoto, but that's a lot of work. 3 of the cameras are off by whole hour incriments (due to time zone varitations).
Is there a way to: select a group of photos in iPhoto, add/ subtract to the hour taken (but leave the minutes and seconds alone)?
thanks in advance for any help
Mealie
G5 ambient light Mac OS X (10.4.7) iLife 06

I emailed this question to a friend, he told me automator is "overkill" (his words) for this situation as a script will do the job. He also sent this link: http://www.joemaller.com/iphoto/
It seems to work just fine, in case anyone has the same need.
G5 ambient light Mac OS X (10.4.3)

Problem with License MAC after change Time Zone in UCCX 8.02

Hi all,
Please I need Help.
The last weekend, we changed the Time Zone in we Cluster of UCCX 8.02.
Now when entry to administration page, show a warning that says.
“The Unified CCX Systems is currently using a license that has a grace period of 30 days”
How i can solve this problem. I must go back with the change , and return time zone previous ?
Thanks
Guillermo

Welcome to the wonderful world of Cisco Licensing with 8.5 (perhaps 8.0 as well). Changes to the IP address, hostname, DNS, Time Zone, and a few other fields will change your License MAC and invalidate all licenses.
Send an email to [email protected] asking them to rehost your license for the new license mac.
Tanner

Apex 4.1 bug? Application language derived from Session changes time zone

I have created an application in Apex 4.1 and in the "Initialization PL/SQL Code" for the session (what used to be called the VPD section) I have the following code:
begin
execute immediate 'alter session set time_zone = ''+01:00''';
end;This works as expected, UNLESS the "Application Language Derived From" (under "Edit Globalization Attributes") is set to "Session", in which case the session's time zone is also affected (and not just the language, as one would expect).
This can be seen in the following simple example, which runs the above code to set the time zone, and has the language derived from "Session":
http://apex.oracle.com/pls/apex/f?p=38595
This shows
sessiontimezone = -05:00Even though the session's time_zone has been explicitly set to +01:00 with the ALTER SESSION statement.
Experimentation with the URL shows that if a p_lang parameter is passed, with a valid language identifier, for example:
http://apex.oracle.com/pls/apex/f?p=38595&p_lang=de
then the time zone is affected (showing -05:00 instead of +01:00).
However, if an INVALID time zone identifier is passed:
http://apex.oracle.com/pls/apex/f?p=38595&p_lang=xx
then the session time zone is CORRECT according to the ALTER SESSION command:
sessiontimezone = +01:00If I change the "Application Language Derived From" to something else than "Session" (for example, "Browser" or "Item Preference"), then the timezone is also correct (ie follows the ALTER SESSION command).
Running the page in debug mode confirms that the time zone is being set after my VPD/initialization code has been run:
0.01585     0.00146     ...Application session: 1671806996734123, user=nobody     4
0.01731     0.00144     ...Execute Statement: begin begin execute immediate 'alter session set time_zone = ''+01:00'''; end; end;     4
0.01875     0.00065     Session: Fetch session header information     4
0.01940     0.00073     SESSION Language (nobody): wwv_flow.g_browser_language=en maplang=en     4
0.02013     0.00059     alter session set nls_language="AMERICAN"     4
0.02071     0.00043     alter session set nls_territory="AMERICA"     4
0.02114     0.00094     NLS: CSV charset=WE8MSWIN1252     4
0.02208     0.00111     ...NLS: Set Decimal separator="."     4
0.02318     0.00062     ...NLS: Set NLS Group separator=","     4
0.02380     0.00063     ...NLS: Set g_nls_date_format="DD-MON-RR"     4
0.02443     0.00091     ...NLS: Set g_nls_timestamp_format="DD-MON-RR HH.MI.SSXFF AM"     4
0.02534     0.00066     ...NLS: Set g_nls_timestamp_tz_format="DD-MON-RR HH.MI.SSXFF AM TZR"     4
0.02600     0.00050     ...Setting session time_zone to -05:00     4
0.02650     0.00065     Setting NLS_DATE_FORMAT to application date format: dd.mm.yyyy     4
0.02715     0.00056     ...NLS: Set g_nls_date_format="dd.mm.yyyy"     4
0.02771     0.00055     ...NLS: Set g_nls_timestamp_format="DD-MON-RR HH.MI.SSXFF AM"     4
0.02827     0.00057     ...NLS: Set g_nls_timestamp_tz_format="DD-MON-RR HH.MI.SSXFF AM TZR"     4
0.02884     0.00230     NLS: Language=en     4
Conclusion: It seems to me that when the LANGUAGE is set to be derived from the "Session", this also, as a side effect, alters the session TIME ZONE, which must be a bug... ?
- Morten
http://ora-00001.blogspot.com
Edited by: mobra on Sep 24, 2011 7:14 PM

Hi Arie,
When you are setting the language to derived from session you actually declare that you are working in a dynamic environment – per session – and not in a static one. Using the Initialization PL/SQL Code is very static as the same code is executed for every database session.I was using a fixed time zone value in the ALTER SESSION to demonstrate the bug/problem... in real life, the actual time zone is derived dynamically based on a user profile stored in the database.
APEX 4.0 introduced the Automatic Time Zone under the Globalization tab. By default it’s set to No but setting it to Yes will allow you to use your local time zone (as derived from your browser) with whatever language derived setting you choose, including per session with the *&p_lang* parameter.The key point is that LANGUAGE has nothing to do with TIME ZONEs, and vice versa. People speak English (and Spanish, and French, and Chinese for that matter) all over the world. You cannot determine a user's time zone based on the chosen language.
You're telling me to enable "Automatic Time Zone" to work around an unwanted side effect from changing the language setting. Sorry, but that just sounds like bad advice to me.
If you want to use session derived language, however the local time zone settings are not good for you, you can still change them with a Before Header and After Submit PL/SQL processes and an appropriate alter session statement, on a per page base. The APEX engine will not ignore a page based session setting.Why should I have to do this for every page when the "VPD" Section (now called "Initialization PL/SQL Code") is made for this purpose?
If you look at the help text in the Apex builder for that section, it actually says that:
The code entered here need not pertain to VPD/FGAC and may not be related to security at all.
Any code that needs to be executed at the earliest point in a page request can be placed here.
For example, the following code sets the database session time zone for every page request:
BEGIN
   EXECUTE IMMEDIATE 'alter session set time_zone = ''Australia/Sydney'' ';
END;So I hope the demonstrated behavior is not intentional, but a bug, and I'm hoping Joel sees it the same way.
- Morten
http://ora-00001.blogspot.com

Problems with auto-scale vertical charts when change time zones

I have built an application that utalizes Vertical Strip Charts. Basiclly, XY Charts that are filled with 100 points of data each loop cycle. To get the Time portion of it I use the Get Dat/Time in Seconds Function and then typecast it to a double. I have built the application and installed in on several PC in my same time zone no problem, but when I send it to someone in the UK on GMT time the strip chart does not update correctly. The scaling is off. The interesting thing is the most recent time on the chart is correct and is updating correctly, but the time at the top of the graph is not correct. Any suggestions or thoughts would be appreaciated.

Can you post a copy of this application, or an example that would demonstrate this? If you change your timezone on your computer to UK's timezone and restart LabVIEW (which is necessary for the change to take affect in LV), do you see this behavior?
Jarrod S.
National Instruments

Need to change time zone in PI 7.3 system

Similar Messages

Maybe you are looking for