| user had different system date extracted compared with oracle [message #671503] |
Sun, 02 September 2018 22:41  |
reym21
Messages: 241
Registered: February 2010
Location: Philippines
|
Senior Member |
|
|
Gurus,
Good day!
This is the first time we encountered a user when logged in at SQLplus
had different timestamp extracted compared to Oracle user who had it correctly.
In the attached screenshot, once ORACLE user logged in, it can select the correct
sysdate/timestamp, but when said user logged-in, it can select the correct sysdate
but a delayed (of 6 hours) timestamp. The logins were done both at the same server.
The server were once administered by our contractors and was later turned-over to us.
We haven't changed any configurations to said dB server since we started managing this.
What's causing this? Thank you in advance.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: user had different system date extracted compared with oracle [message #672063 is a reply to message #671747] |
Sun, 30 September 2018 20:51  |
reym21
Messages: 241
Registered: February 2010
Location: Philippines
|
Senior Member |
|
|
Sir, sorry for this. It's been a busy month for me (trainings, preparation of TORs, etc.) and I was struck with a flu last week. Also, this had been resolved by restarting the dB server's zone.
Anyway, as instructed, below was the output:
"SQL*Plus: Release 3.3.4.0.1 - Production on Mon Oct 1 09:35:14 2018
Copyright (c) Oracle Corporation 1979, 1996. All rights reserved.
Connected to:
Oracle7 Server Release 7.3.4.5.0 - Production
With the distributed and parallel query options
PL/SQL Release 2.3.4.5.0 - Production
SQL> SELECT DISTINCT hostname FROM v$session WHERE type = 'BACKGROUND';
SELECT DISTINCT hostname FROM v$session WHERE type = 'BACKGROUND'
*
ERROR at line 1:
ORA-00904: invalid column name
SQL> exit"
Thank you very much, and again, sorry for late response.
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
