求助：11g内存升级后无法启动

xteitxu

ZALBB 发表于 2022-3-21 23:00
还得先计算这两参数，kernel.shmmax,kernel.shmall kernel.shmmax（b）>= sga_max_size  kernel.shmall =ke ...

感谢福版主，有一事不明白，实例已正常启动，应该不是参数设置的问题。alert报这个错是如果是因为PGA或SG设置太小，但之前PGA与SGA的值更小，数据库都能正常运行。把内存调大后，确一直有问题。不知道我这个问题的点在哪里。求解

jieyancai

xteitxu 发表于 2022-3-21 13:12
这样配置？alter system set memory_max_target=0 scope=spfile;alter system set memory_target=0 scope=s ...

数据库运行的情况下，这样操作啊
alter system reset memory_target;
alter system reset memory_max_target;
alter system set sga_target=80G scope=spfile;
alter system set pga_aggregate_target=18G scope=spfile;
shutdown immediate
startup

ZALBB

xteitxu 发表于 2022-3-22 11:02
感谢福版主，有一事不明白，实例已正常启动，应该不是参数设置的问题。alert报这个错是如果是因为PGA或SG设 ...

/u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_cjq0_106776.trc

你把这文件的内容贴上来，我之所以建议升级，是因为11201古古怪怪的问题太多，很多故障，升级到11204就消失了，

xteitxu

jieyancai 发表于 2022-3-23 09:46
数据库运行的情况下，这样操作啊alter system reset memory_target;alter system reset memory_max_target; ...

非常感谢，能正常启动

xteitxu

ZALBB 发表于 2022-3-23 22:07
/u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_cjq0_106776.trc你把这文件的内容贴上来，我之所以建议 ...

这个trc文件里没有太重要的信息
Trace file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_cjq0_106776.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.1.0/db_1
System name:    Linux
Node name:      oracle
Release:        3.10.0-957.5.1.el7.x86_64
Version:        #1 SMP Fri Feb 1 14:54:57 UTC 2019
Machine:        x86_64
Instance name: orcl
Redo thread mounted by this instance: 1
Oracle process number: 25
Unix process pid: 106776, image: oracle@oracle (CJQ0)


*** 2022-03-20 22:05:45.829
*** SESSION ID1280.5) 2022-03-20 22:05:45.829
*** CLIENT ID) 2022-03-20 22:05:45.829
*** SERVICE NAMESYS$BACKGROUND) 2022-03-20 22:05:45.829
*** MODULE NAME) 2022-03-20 22:05:45.829
*** ACTION NAME) 2022-03-20 22:05:45.829

Setting Resource Manager plan SCHEDULER[0x3009]EFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter

*** 2022-03-20 22:06:37.075
Process J000 is dead (pid=112755 req_ver=2 cur_ver=2 state=KSOSP_SPAWNED).

*** 2022-03-20 22:06:38.079
Process J000 is dead (pid=112834 req_ver=2 cur_ver=2 state=KSOSP_SPAWNED).

*** 2022-03-20 22:06:49.079
Process J000 is dead (pid=114217 req_ver=3 cur_ver=3 state=KSOSP_SPAWNED).

*** 2022-03-20 22:06:50.080
Process J000 is dead (pid=114243 req_ver=3 cur_ver=3 state=KSOSP_SPAWNED).

*** 2022-03-20 22:07:41.085
Process J000 is dead (pid=120339 req_ver=4 cur_ver=4 state=KSOSP_SPAWNED).

*** 2022-03-20 22:07:42.086
Process J000 is dead (pid=120547 req_ver=4 cur_ver=4 state=KSOSP_SPAWNED).

*** 2022-03-20 22:07:43.087
Process J000 is dead (pid=120639 req_ver=2 cur_ver=2 state=KSOSP_SPAWNED).

maolinxie

解决了么，我理解是/etc/sysctl.conf参数据问题