ORA-00824: cannot set sga_target due to existing internal settings

Posted on 2010-06-18 17:04  blackcat  阅读(1640)  评论(0编辑  收藏  举报

前线数据库,说是有问题,让我看看。

我上去看了下,觉得SGA给的太小气了,于是调整sga_target到sga_max_size的值。

突然莫名其妙的数据库停止了。很是神奇。

看了下alter,没发现异常居然,于是startup,坏了,报错: ORA-00824: cannot set sga_target due to existing internal settings

怀疑可能是我修改的参数值最后各个组件的和大于sga_target了,于是一一修改,但是还是不行。

google了下,

原来是oracle的问题。

 当时重现的话,默认安装后,一直有人使用oem的bs版本管理,然后我create pfile form spfile之后,数据库当掉。

检查pfile,其中有一段:

db_block_buffers=13332

 

哦,想起来了,一个oracle的问题。

找了下,果然。

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2 to 10.2
This problem can occur on any platform.

Symptoms

Startup of 10g Database Instance fails with ORA-00824 Error

SQL> connect / as sysdba
Connected to an idle instance.
SQL> startup
ORA-00824: cannot set sga_target due to existing internal settings

Cause

If you enable automatic SGA Management by setting SGA_TARGET >0 and also have db_block_buffers(Obsolete parameter) in your parameter file (pfile/spfile)

Startup of Database fails with ORA-00824 Error

Solution

A) Either you need to disable the Automatic SGA Mangement by setting SGA_Target=0


==OR==

B) Replace the db_block_buffers parameter with db_cache_size parameter

STEPS TO RESOLVE

1. Make an OS copy of the spfile if you do not have a pfile for this database
2. Edit the copy of the spfile to remove the binary stuff before the first parameter
3. Remove the binary stuff after the last parameter.
4. Edit parameters needed to be changed.
5. Save the file and note name and location.
6. Start sqlplus and connect / as sysdba
7. Issue startup pfile = '<full path and file name of file just updated>'
8. Create spfile from pfile.

Errors

ORA-824cannot set sga_target due to existing internal settings

 

 于是删除这个参数,startup。

 

Copyright © 2024 blackcat
Powered by .NET 9.0 on Kubernetes