Home » RDBMS Server » Server Administration » Session increase
Session increase [message #260002] Fri, 17 August 2007 02:26 Go to next message
preet_kumar
Messages: 195
Registered: March 2007
Senior Member
How to increase the sessions and process parameter,is it possible to change it without shutting down the database?
Thanks
Re: Session increase [message #260016 is a reply to message #260002] Fri, 17 August 2007 02:49 Go to previous messageGo to next message
Michel Cadot
Messages: 64132
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
1/ It depends if you started with a pfile or a spfile.
In the former case, change the values in init.ora
In the latter case, use "alter system set ... scope=spfile;"

2/ No, they are static parameters

Regards
Michel
Re: Session increase [message #261066 is a reply to message #260016] Tue, 21 August 2007 13:04 Go to previous messageGo to next message
Mohammad Taj
Messages: 2412
Registered: September 2006
Location: Dubai, UAE
Senior Member

In the latter case, use "alter system set ... scope=spfile;" Plus bounce DB (shutdown + startup)


Regards
Taj
Re: Session increase [message #261077 is a reply to message #261066] Tue, 21 August 2007 14:18 Go to previous messageGo to next message
Michel Cadot
Messages: 64132
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
This was number 2 answer ("is it possible to change it without shutting down the database?"/"No, they are static parameters").

Regards
Michel
Re: Session increase [message #261871 is a reply to message #260002] Thu, 23 August 2007 21:34 Go to previous messageGo to next message
trantuananh24hg
Messages: 668
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
yeah!

I've encountered a problem like that, it noticed to me that "An error encountered when session limited".

Then, I've increase parameter session corresponding processes with:

Session:=(1.1*processes)+5.

And, created a procedure to kill any session with INACTIVE status.

declare
	   sv_ varchar2(10000);
	   
begin
 for zz in (
		SELECT SID, SERIAL#, USERNAME, STATUS
		FROM V$SESSION
		WHERE USERNAME IS NOT NULL
		AND STATUS = 'INACTIVE' 
 )
 loop
	 sv_  := 'alter system kill session '''||zz.sid||', '||zz.SERIAL#||'''';
	 dbms_output.put_line(sv_);
	 --execute immediate sv_;
 end loop;
 end;




And, executed the UTLLOCKT.SQL to monitor LOCK table.

At the end, with Perfstat shema user, I executed spreport.sql to view snap_shot.

What anything else can I do for monitoring?

ORaDB: 10.2.0
OS: Unix

Thank you very much!
Re: Session increase [message #261925 is a reply to message #261871] Fri, 24 August 2007 01:26 Go to previous messageGo to next message
Michel Cadot
Messages: 64132
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Then you will likeky kill almost every one.
A session is inactive when it currently does not execute something.
Between 2 statements you are inactive for Oracle.
I hope your clients type very fast on their keyboard!

Regards
Michel

[Updated on: Fri, 24 August 2007 02:39]

Report message to a moderator

Re: Session increase [message #261927 is a reply to message #260002] Fri, 24 August 2007 01:31 Go to previous message
trantuananh24hg
Messages: 668
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
Thank you, Michael!

A ha! I understand your meaning.

Previous Topic: problem in execution
Next Topic: Database migration from Solaris to Linux
Goto Forum:
  


Current Time: Wed Dec 07 20:16:19 CST 2016

Total time taken to generate the page: 0.12542 seconds