oracle12C rac DBCA报错 ORA-00838: Specified value of MEMORY_TARGET is too small

安装oracle发现/etc/profile和.bashrc环境变量设置有冲突,oracle用户的$ORACLE_HOME没生效

Question:  After increasing by "processes" parameter (processes 3000), I got the following ORA-00838 error at database startup time.  Note that I am on 12c and I have not set my sga_target or pga_aggregate_target parameter.  After re-setting processes=1000 the ORA-00838 error disappeared.  Why?

ORA-00838: Specified value of MEMORY_TARGET is too small, needs to be at least 3072M

ORA-01078: failure in processing system parameters

How do I correct the ORA-00838 error?

Answer:  The oerr utility  shows the cause and action for the ORA-02097:

ORA-00838: Specified value of MEMORY_TARGET is too small, needs to be at least string

Cause: The specified value of MEMORY_TARGET was less than the sum of the specified values for SGA_TARGET and PGA_AGGREGATE_TARGET.

Action: Set MEMORY_TARGET to at least the recommended value.

In this case the increase of your processes parameter was the root cause of the ORA-00838 error.  As we my know the processes parameter determines the sessions parameter that this must, in turn, indicate to Oracle that additional RAM is required to support the extra sessions.

As a workaround, of course, you can increase your memory_target parameter value.

由于安装过程中将进程数量由初始值300调到5000导致所需内存增加,保持初始值不变即可顺利安装

时间: 2024-10-22 12:34:05

oracle12C rac DBCA报错 ORA-00838: Specified value of MEMORY_TARGET is too small的相关文章

11g ASM单实例 dbca报错 prcr-1006 crs-0259 prcr-1071

11g ASM dbca报错 prcr-1006 crs-0259  prcr-1071 使用ASM方式创建单实例DB时,在运行DBCA时出现 PRCR-1006 : Failed to add resource ora.orcl.db for orcl PRCR-1071 : Failed to register or update resource ora.orcl.db PRCR-1001 : Resource ora.orcl.db does not exist 查看DBCA日志后,发现

expdp报错ora 39126

11.2.0.2,expdp报错: ORA-39126: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS []ORA-31642: the following SQL statement fails:BEGIN "SYS"."DBMS_CUBE_EXP".SCHEMA_CALLOUT(:1,0,1,'11.02.00.00.00'); END;ORA-06512: at &quo

Oracle12c启动数据库报错:ORA-01078: failure in processing system parameters

单实例oracle12102安装完成后,startup报错: [[email protected] ~]$ sqlplus "/as sysdba" SQL*Plus: Release 12.1.0.2.0 Production on Sat Sep 16 15:04:46 2017 Copyright (c) 1982, 2014, Oracle.  All rights reserved. Connected to an idle instance. SQL> startup

ORACLE dbca报错 ORA-01034:ORACLE not available

1,问题描述,dbca最后 finish的时候报错 ORA-00119: invalid specification for system parameter LOCAL_LISTENER ORA-00130: invalid listener address '(ADDRESS=(PROTOCOL=TCP)(HOST=pldb236)(PORT=1521))' ,如下图所示 2,去hosts里面添加hostname [[email protected] data]# cat /etc/host

oracle 11g rac启动报错ORA-01102: cannot mount database in EXCLUSIVE mode

启动oracle 11g rac数据库时出现以下错误,只能启动其中一个节点,另一个节点启动不了,可能是以前修改cluster_database这个参数引起的.在oralc rac架构这个参数必须设置为TRUE. 错误信息: ORA-01102: cannot mount database in EXCLUSIVE mode 解决方法: rac1节点: SQL> show parameter cluster_database; NAME                              

ORACLE 12C 三节点 RAC 安装报错 [INS-32025]

测试安装三节点Oracle 12C RAC,笔记本配置双核I5 16g内存,每台虚机分配4G 内存. 在数据库软件安装过程中,主实例异常重启,重新安装数据库软件,但是遇到报错.报错如下: [INS-32025] The chosen installation conflicts with software already installed in the given oracle home. 处理方法如下: 1.修改inventory文件 [[email protected] ContentsX

asm单机dg dbca报错ORA-01031 CRS-2676,rman restore主库控制文件报错ORA-15081

dg-> ll $ORACLE_HOME/bin/oracle -r-xr-s--x 1 oracle asmadmin 210824714 Nov 20 16:41 /u01/app/oracle/product/11.2.0/db_1/bin/oracledg-> chmod 6751 $ORACLE_HOME/bin/oracle dg-> ll $ORACLE_HOME/bin/oracle -rwsr-x--x 1 oracle asmadmin 210824714 Nov 2

Oracle 11g R2 RAC dbca新建实例报错

此oracle问题本人在论坛上作了提问http://bbs.51cto.com/thread-1167548-1.html,最后自己找到方法解决,以此博客再作记录. 环境:CentOS6.5 64位,Oracle 11g R2 11.2.0.1.0 现象:oracle rac生产环境中,已经有一个实例正常使用,有需求再建一实例. 新建实例过程中,最后步骤具体报错如下:    [Thread-829] [ 2015-09-09 11:29:42.007 CST ] [DatabaseImpl.cr

AIX 下Oracle Rac dbca建库报错 ora-7445 [PC:0x103E2AFA0]

在AIX 7100-02-03-1334 上安装Oracle Rac,grid和oracle都已安装完成.但是dbca建库的时候发现数据库crash,以下是建库时的alert.log,数据库报ora-07445报错,dbca的日志中可以发现在Create database时出错. 在mos上没有找到匹配的文档,尝试使用其他方法. /oraapp/oracle/diag/rdbms/rmbtodb/rmbtodb1/trace/alert_rmbtodb1.log MMNL started wit