Chinaunix首页 | 论坛 | 博客
  • 博客访问: 1125933
  • 博文数量: 276
  • 博客积分: 10077
  • 博客等级: 上将
  • 技术积分: 2513
  • 用 户 组: 普通用户
  • 注册时间: 2007-08-24 20:31
文章分类

全部博文(276)

文章存档

2020年(1)

2015年(5)

2012年(2)

2011年(6)

2010年(7)

2009年(224)

2008年(31)

我的朋友

分类: Oracle

2009-04-27 09:27:05

SQL> startup upgrade

ORA-00064: object is too large to allocate on this O/S (1,7614720)
 
 
1. High value of oracle parameter PROCESSES

 The oracle parameter PROCESSES bigger than 1500 requests the allocation of big granule size.

2.  Low value of granule size.

The oracle hidden parameter "_ksmg_granule_size" is set based on the oracle sga size.

  -  sga_max_size <= 1024M then _ksmg_granule_size = 4M
  - sga_max_size > 1024M then _ksmg_granule_size = 16M

If you set a parameter that exceeds the value of the granule size that was
calculated based on the size of the sga.

You will manually have to set the parameter _ksmg_granule_size.

  - default _ksmg_granule_size is 4M

Low value of _ksmg_granule_size can prohibit the database startup.


3. The ORA-64 error could be occured even though the big "_ksmg_granule_size" was configured in
init.ora file.

   DBUA in 10.2.x strips out  the oracle hidden parameter while opening oracle database.
阅读(1403) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~