- Community Home
- >
- HPE Community, Taiwan
- >
- HP-UX
- >
- 資料庫
- >
- Max SGA limit?
資料庫
1822456
會員
2414
線上
109642
解決方案
論壇
類別
Company
Local Language
返回
論壇
討論平台
論壇
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
討論平台
論壇
討論平台
返回
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
部落格
信息
社區語言
語言
論壇
部落格
文章選項
- 訂閱此主題的RSS 提要
- 將此主題標記為未讀
- 將主題標記為已讀
- 將主題在本帳號置頂
- 標示為書籤
- 訂閱此主題
- 列印此頁
- 將文章標記為未讀
- 標示為書籤
- 訂閱此主題
- 靜音
- 訂閱此主題的RSS 提要
- 高亮顯示此文章
- 列印此文章
- 提報不當內容
在 11-25-2005 04:01 PM
在 11-25-2005 04:01 PM
Max SGA limit?
This is Oracle 9.0.1.4 on HP Tru64 5.1B. The physical memory is 10GB. How to know the max SGA limit? Is there a solution to avoid the limit?
1則回覆 1
- 將文章標記為未讀
- 標示為書籤
- 訂閱此主題
- 靜音
- 訂閱此主題的RSS 提要
- 高亮顯示此文章
- 列印此文章
- 提報不當內容
在 11-26-2005 09:12 AM
在 11-26-2005 09:12 AM
Max SGA limit?
Hi Eric,
You can refer Metalink Note 50364.1 "SGA Sizing & OS Specifics Using tstshm" the tstshm program can be used to make sure that a user process can grab enough shared memory required to accomodate the SGA. It is also to ensure that the user process address space is sufficient to map it.
Without the '-t' argument to set the total size of SGA you require, tstshm will assume certain sizing information and use a default algorithm to present mapping statistics.
Therefore, if you are wishing to ensure that a certain size SGA is compatible with the OS (operating system) parameters and limits settings,then you need to use the
'-t' flag to specify the size of the SGA. For example:
For SGA size = 64MB = 67108864 (8192 8k pages)
N.B. Default page-size on Alpha is 8k.
On Alpha unix consider a value for shm-max = 16MB = 16777216
% setenv SHMMAX 16777216
% tstshm -t67108864
totsize = 67108864
Succeeded in attaching 4 segments with total shm of 67108864
This tells you that it needed to allocate 4 segments each of 16MB in order to meet the required 64MB SGA.
If tstshm fails, it will fail with an OS error.For example:
Consider SGA size = 1GB = 1073741824 OS settings as above.
% tstshm -t1073741824
totsize = 1073741824
Shmat error: Too many open files
shmctl: Not owner
In this case, the failure occurs because the OS parameter 'shm-seg' is set at 32 and we are trying to map more than 32 segments.
This can be seen by using the debug flag:
% tstshm -d -t1073741824
The important value can be seen by:
% tstshm -d -t1073741824 |& grep shmat |wc -l
33
It failed on the 33rd call to shmat().
Hint: '|&' pipes both stderr and stdout in 'csh'.
*Note: This program is provided as a guide for SGA sizing, it should not
be relied upon for definitive statistics on what shared memory
Oracle RDBMS allocates. Such details are undocumented.
The SHM_MAX can be set up to 4278190080 (4 GB less 16MB) as stated in Note 169706.
You can refer Metalink Note 50364.1 "SGA Sizing & OS Specifics Using tstshm" the tstshm program can be used to make sure that a user process can grab enough shared memory required to accomodate the SGA. It is also to ensure that the user process address space is sufficient to map it.
Without the '-t' argument to set the total size of SGA you require, tstshm will assume certain sizing information and use a default algorithm to present mapping statistics.
Therefore, if you are wishing to ensure that a certain size SGA is compatible with the OS (operating system) parameters and limits settings,then you need to use the
'-t' flag to specify the size of the SGA. For example:
For SGA size = 64MB = 67108864 (8192 8k pages)
N.B. Default page-size on Alpha is 8k.
On Alpha unix consider a value for shm-max = 16MB = 16777216
% setenv SHMMAX 16777216
% tstshm -t67108864
totsize = 67108864
Succeeded in attaching 4 segments with total shm of 67108864
This tells you that it needed to allocate 4 segments each of 16MB in order to meet the required 64MB SGA.
If tstshm fails, it will fail with an OS error.For example:
Consider SGA size = 1GB = 1073741824 OS settings as above.
% tstshm -t1073741824
totsize = 1073741824
Shmat error: Too many open files
shmctl: Not owner
In this case, the failure occurs because the OS parameter 'shm-seg' is set at 32 and we are trying to map more than 32 segments.
This can be seen by using the debug flag:
% tstshm -d -t1073741824
The important value can be seen by:
% tstshm -d -t1073741824 |& grep shmat |wc -l
33
It failed on the 33rd call to shmat().
Hint: '|&' pipes both stderr and stdout in 'csh'.
*Note: This program is provided as a guide for SGA sizing, it should not
be relied upon for definitive statistics on what shared memory
Oracle RDBMS allocates. Such details are undocumented.
The SHM_MAX can be set up to 4278190080 (4 GB less 16MB) as stated in Note 169706.
以上表述為作者個人觀點,不代表惠普公司,使用本網站,請遵守網站使用規則和條款
© 版权所有 2025 慧与发展有限责任合伙企业