| sqlplus / as sysdba gang [message #442562] |
Tue, 09 February 2010 02:08  |
goracle9 Messages: 124 Registered: December 2006 |
Senior Member |
|
|
Dear All,
today morning, oracle went down, when i try to connect like
ganging, i try to connect listner like
this also gang.
what could be the problem, please explain.
thanks.
|
|
|
| Re: sqlplus / as sysdba gang [message #442563 is a reply to message #442562] |
Tue, 09 February 2010 02:10   |
Michel Cadot Messages: 35397 Registered: March 2007 Location: Nanterre, France, http://... |
Senior Member Account Moderator |
|
|
I think you mean "hang", stay without answering.
1/ Try to ping the server
2/ Try to connect to the server
3/ Check if archiver destination file system is not full
4/ Check if audit file destination file system is not full
Regards
Michel
|
|
|
| Re: sqlplus / as sysdba gang [message #442567 is a reply to message #442563] |
Tue, 09 February 2010 02:23   |
goracle9 Messages: 124 Registered: December 2006 |
Senior Member |
|
|
your correct "hang", stay without answering.
when i connect the server tru putty i can connect the server is up & running, but sqlplus was gang
i reboot os/linux then oracle got connected, working fine.
in alert log no information.
please explain.
|
|
|
|
| Re: sqlplus / as sysdba gang [message #442573 is a reply to message #442569] |
Tue, 09 February 2010 02:43   |
goracle9 Messages: 124 Registered: December 2006 |
Senior Member |
|
|
thanks anyway,
i got it.
i google it for explanation
http://www.dba-oracle.com/bk_sqlplus_hang_tips.htm
is FALS
i m going to set it as TRUE.
oracle running using spfile, so i can set the parameter dynamically coreect??
alter system set log_archive_start=true;
thatnks.
regards.
|
|
|
| Re: sqlplus / as sysdba gang [message #442574 is a reply to message #442573] |
Tue, 09 February 2010 02:54   |
ramoradba Messages: 1729 Registered: January 2009 Location: AndhraPradesh,Hyderabad,I... |
Senior Member |
|
|
Quote:LOG_ARCHIVE_START
This parameter is deprecated in Oracle 10g This parameter determines if the background process ARCH is started. It can be set to either true or false. Of course, it makes no sense, if this parameter is set to true if the database is running in noarchive log mode. If ARCH is started with the database being in noarchive log mode, messages like media recovery disabled will be written into the alert.log file.
ind> select NAME||','||VALUE||','||ISDEFAULT||','||ISDEPRECATED||','||DESCRIPTION
2 from v$parameter
3 where NAME='log_archive_start';
NAME||','||VALUE||','||ISDEFAULT||','||ISDEPRECATED||','||DESCRIPTION
--------------------------------------------------------------------------------
log_archive_start,FALSE,TRUE,TRUE,start archival process on SGA initialization
1 row selected.
http://www.oracle.com/technology/obe/paa/obe-arc/html/enable_auto_arch.htm#b
sriram
[Updated on: Tue, 09 February 2010 03:00]
|
|
|
|
| Re: sqlplus / as sysdba gang [message #442586 is a reply to message #442576] |
Tue, 09 February 2010 04:01   |
ramoradba Messages: 1729 Registered: January 2009 Location: AndhraPradesh,Hyderabad,I... |
Senior Member |
|
|
Michel already answered your Question.Without the info it is very difficult to answer.
ANd whatever the link you specified has some more infomation what to do..did you check them all?
sriram
[Updated on: Tue, 09 February 2010 04:04]
|
|
|
| Re: sqlplus / as sysdba gang [message #442592 is a reply to message #442586] |
Tue, 09 February 2010 05:16  |
goracle9 Messages: 124 Registered: December 2006 |
Senior Member |
|
|
Yes Sriram.
i checked in the listener.log as the link suggested, then i found a waring message from my listener.log is
WARNING: Subscription for node down event still pending
i googled for the warning i found the linked page
http://www.ora600.be/node/1206
in that page suggesting that SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER=OFF
This changes also prevent the TNS listener hanging intermittently
but i m running database without listener.ora mean
Quote:This automatic feature is called service registration, is handled by the process monitor (PMON), and requires SERVICE_NAMES and INSTANCE_NAME to be set in the init.ora file, something you already have set by default
so i need to create a listener.ora file and can incluse the code
SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER=OFF
to come to the subject matter, i checked the listener.log
the warming WARNING: Subscription for node down event still pending
is not today, it was from 2006.
so this is not the cause of today issue.
i cant find why it happend.
[Updated on: Tue, 09 February 2010 06:12] by Moderator
|
|
|