No question at this time
DBA Top 10
1 M. Cadot 20300
2 A. Kavsek 13300
3 M. Hidayathullah ... 11400
4 B. Vroman 8500
5 P. Wisse 5900
6 T. Boles 5400
7 J. Schnackenberg 4500
8 A. Hudspith 2300
9 P. Knibbs 2200
9 K. Pagadala 2200
About
DBA-Village
Download PLATO
The free tool for auditing and tuning your database
Version 55 now available
Sep 02, 2016
The DBA-Village forum
Forum as RSS
as RSS feed
Site Statistics
Ever registered users47975
Total active users1857
Act. users last 24h3
Act. users last hour0
Registered user hits last week384
Registered user hits last month1277
Go up

Needed help to understand behaviour of sessions parameter
Next thread: Fatal NI connect error 12170
Prev thread: Problem with SQL sorting in stored procedure

Message Score Author Date
Dear Guru's, We were facing the issue of "ORA-0...... Raj Kumar Jun 19, 2017, 11:08
Dear Raj, Please check below doc,whether it hel...... Score: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 Pts Mirza Hidayathullah Baig Jun 19, 2017, 11:31
Thankyou Mirza for your help.... Raj Kumar Jun 21, 2017, 06:43
Hi Guru's Can someone please provide guidance...... Raj Kumar Jun 21, 2017, 06:44
Database Concepts Chapter 14 Memory Architectur...... Score: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 Pts Michel Cadot Jun 21, 2017, 09:08
Hi Michel, Thankyou very much for your help. ...... Raj Kumar Jun 21, 2017, 11:04

Follow up by mail Click here


Subject: Needed help to understand behaviour of sessions parameter
Author: Raj Kumar, India
Date: Jun 19, 2017, 11:08, 5 days ago
Os info: Linux
Oracle info: Oracle 11.2.0.3.0
Message: Dear Guru's,

We were facing the issue of "ORA-00020: maximum number of processes (220) exceeded" in one of our database.

After analysis we increased the processes,sessions and pga_aggregate_target,sga_target and sga_max_size values.

But After increasing the value I have noticed the below thing after bounce of the database :

sessions increase to 739 but showing 740.

sga_max_size increased to 4500M but showing as 4512M.

sga_target increased to 3800M but showing as 3808M.

Only pga_aggregate_target is showing correct value.

Please help me to understand how values were automatically increased little bit.

Thanks & Regards,
RajKumar
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Needed help to understand behaviour of sessions parameter
Author: Mirza Hidayathullah Baig, United Kingdom
Date: Jun 19, 2017, 11:31, 5 days ago
Score:   Score: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 Pts
Message: Dear Raj,

Please check below doc,whether it helps you.

https://docs.oracle.com/cd/B28359_01/server.111/b28300/changes.htm#UPGRD12581

Regards
Mirza
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Needed help to understand behaviour of sessions parameter
Author: Raj Kumar, India
Date: Jun 21, 2017, 06:43, 4 days ago
Message: Thankyou Mirza for your help.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Needed help to understand behaviour of sessions parameter
Author: Raj Kumar, India
Date: Jun 21, 2017, 06:44, 4 days ago
Message: Hi Guru's


Can someone please provide guidance on this ?


Thanks,

RajKumar
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Needed help to understand behaviour of sessions parameter
Author: Michel Cadot, France
Date: Jun 21, 2017, 09:08, 4 days ago
Score:   Score: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 Pts
Message:
Database Concepts
Chapter 14 Memory Architecture
Section Overview of the System Global Area

https://docs.oracle.com/cd/E11882_01/server.112/e40540/memory.htm#i10093

<quote>
All SGA components except the redo log buffer allocate and deallocate space in units of contiguous memory called granules. Granule size is platform-specific and is determined by total SGA size.
</quote>

You can see your instance granule size for each component in V$SGA_DYNAMIC_COMPONENTS.GRANULE_SIZE column.
Oracle allocates the component to the next granule you parametrized.

Regards
Michel
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Needed help to understand behaviour of sessions parameter
Author: Raj Kumar, India
Date: Jun 21, 2017, 11:04, 3 days ago
Message: Hi Michel,

Thankyou very much for your help.

Now its clear with your valuable help.


Thanks,
RajKumar
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here