Oracle 11g OMS: Database Instance Home Tab: Page Refreshed Timezone Issue

Question

Hi all...I've searched the forums and search engines for specific information on this issue, but have not seen a viable solution so far. We have Oracle 11g Grid Control 11.1.0.1
installed on a Solaris V490 using Solaris 10, with an Oracle 11.2.0.1 database.
The Database instance Home tab for all 50+ databases shows the date and time of the 'Page Refreshed' in GMT. The OS and the Agent software both are configured
with the TZ set to US/Eastern. All other page displays e.g. Performance, Availability for Data Guard Standby etc. all show the refreshed time in EDT, it is ONLY
the Home tab for the instance that has the GMT format.
I have not seen any threads or other information that describes specifically how to correct this or even to change it. There are many related posts about the Agent
end.properties, the OS /etc/timezone configuration parameters, the TZ environment variable etc. but in my case they are all set properly.
Does anyone have any additional ideas or suggestions or knowledge about how , or even whether, this can be resolved?
Thanks!
DPH

Answer 1

sqlplus ... Connected to an idle instance.That means the database you're trying to connect with is offline, thus the:
ORA-01034: ORACLE not availableNo big surprise there, instance (that you're trying to connect with) is offline.
First, make sure the service OracleServiceXE for the database is running, see the services applet, Start/Run/services.msc and if it does not show "Started" hit the Start button with the OracleServiceXE selected.
sqlplus sys/admin@XE as sysdbaThat connection attempt uses sqlnet to the XE tnsalias. If you're on the database host the ...@XE part is not needed, better to use:
$ sqlplus /nolog
connect /as sysdba;
... Connected. #if its running
-- or use:
$ sqlplus
... username: sys as sysdba
... password ...
Connected.
-- also try
$ sqlplus system
... password: ....
Connected.
select name from v$database;
...That also assumes the environment/registry entries have been configured correctly.
tnsping XE ... Attempting to contact [tnsalias connect details] ... OK (10 msec)That tells you the listener is running. It does not mean anything more than your listener is running at the host and port specified for your tnsalias are correct. It does not attempt an actual database connection. So if the database is offline but the listener is running a tnsping will not identify that particuler "problem".
lsnrctl status ... Endpoints Summary ... PROTOCOL=tcp)(HOST=chilakamarthy)(PORT=1521)))...That bit of info also verifies the listener is running. Again, check your services.msc applet make sure the service shows Started.
Edited by: clcarter on Jun 7, 2012 2:15 PM
clarify tnsping