| shutdown abort problem [message #62468] |
Fri, 23 July 2004 03:51  |
ulli
Messages: 24
Registered: September 1999
|
Junior Member |
|
|
Hello,
IHAC who has a SIEBEL-Application running against Oracle 9.2.0.4 database. Database is on a Sun Solaris Veritas Cluster with 2 nodes. No RAC.
Veritas Cluster Server ( VCS ) does a 'Indepth-Monitoring' of database, it means every minute VCS tries to connect to database and does a select on a table. If this connect fails VCS assummes that there is a database problem and starts to change everything to the 2nd node.
In this change-process the VCS make a shutdown abort to the database to stop all oracle processes incl. the network-server processes. AFAK this works very well, i have testet it on another node, but in this case there are newtork-processes remaining. This is our problem.
Why do these processes reamain after shutdown abort?
Are Siebel-connects something special? They use normal NET connects with TCP.
Anyone an idea?
Thanx in advance
Ulli
|
|
|
|
|
|
| Re: shutdown abort problem [message #62473 is a reply to message #62471] |
Fri, 23 July 2004 04:40  |
ulli
Messages: 24
Registered: September 1999
|
Junior Member |
|
|
yes, you are right. shutdown abort is not very recommended, but in this case the only thing that works to change the node. You can't wait for a shutdown immediate. VCS does a change of everything to the 2nd node, starts up database and so on.
Also this is not the question if it is ok or not.
Yes you are right, a shutdown abort did not stop the listener-process, but stops all network-server processes,
the so called shadow-processes or server-processes.
That are all running SQL-Net processes between client and server.
But the question in this case is, why does it leave a few connections from siebel?
ulli
|
|
|
|
|
|
| Re: shutdown abort problem [message #62475 is a reply to message #62468] |
Fri, 23 July 2004 06:23 |
ulli
Messages: 24
Registered: September 1999
|
Junior Member |
|
|
Harish wrote"problem is atributed to connection pooling.Ghost Objects exist even after they are destrroyed."
Do you mean connection pooling by Oracle or Siebel?
In Oracle we have not configured any pooling.
Ulli
|
|
|
|
| Re: shutdown abort problem [message #62477 is a reply to message #62474] |
Fri, 23 July 2004 06:34 |
ulli
Messages: 24
Registered: September 1999
|
Junior Member |
|
|
Harish wrote"problem is atributed to connection pooling.Ghost Objects exist even after they are destrroyed."
Do you mean connection pooling by Oracle or Siebel?
In Oracle we have not configured any pooling.
Ulli
|
|
|
|
| Re: shutdown abort problem [message #62515 is a reply to message #62477] |
Mon, 26 July 2004 02:33 |
Harish Shanbhag
Messages: 19
Registered: July 2004
|
Junior Member |
|
|
If Siebel uses MS-ADO/ODBC sources to connect to database
then Siebel is the culprit.
Note:
other likely sources are
if the connection are not closed, after operations are over in the program files.
Software tries to kill those conn obj once they are used, but sometimes they remain in memory for unknown reason (Bug??).
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
