[INS-35172] Target database memory (XXMB) exceeds the systems available shared memory ({0}MB) 解决方法

 

安装Oracle 11gR2数据库,安装过程中报错:

 


[INS-35172] Target database memory (778MB)exceeds the systems available shared memory ({0}MB).

 

 

经过测试,目前系统最大能通过的内存是:632M. 如下图:

 

 

 

影响这个最大值,即632M是我们的tmpfs 文件的大小。 这个问题和我之前的blog原因类似:

Oracle11gR2 RAC ORA-00845 MEMORY_TARGET not supported on this system 解决方法

http://www.cndba.cn/Dave/article/478

 

MOS上的文档[ID 460506.1] 有说明。

 

You are tryingto use the MEMORY_TARGET feature. This feature requires the /dev/shm filesystem to be mounted for at Least <size> bytes.The /dev/shm is either notmounted or is mounted With available space less than this size.

 

[root@gg2 ~]# df -h /dev/shm

Filesystem            Size  Used Avail Use% Mounted on

tmpfs                 636M     0 636M   0% /dev/shm

 

这个文件的大小才是真正控制我们 AMM 的大小关键。找到了原因就好处理了。修改tmpfs 的大小,使其大于MEMORY_TARGET的大小就可以了。 

 

# umount tmpfs

# mount -t tmpfs shmfs -o size=3G /dev/shm

 

让以后每次重启OS 都自动mount,修改文件 /etc/fstab 将tmpfs 修改成以下值:

 tmpfs            /dev/shm        tmpfs  defaults,size=3G        0 0

 

如果直接修改/etc/fstab,通过重启OS 也可以让参数生效。

 

注意:这个size 的大小需要设置为整数。

 

[root@gg2 ~]# df -lh /dev/shm

Filesystem            Size  Used Avail Use% Mounted on

shmfs                 3.0G     0 3.0G   0% /dev/shm


修改之后就可以顺利通过安装了。

 

 

 


 

 

-------------------------------------------------------------------------------------------------------

版权所有. 文章允许转载, 但必须以链接方式注明源地址,否则追究法律责任.

QQ:492913789

Email:ahdba@qq.com

Blog:  http://www.cndba.cn/dave

Weibo:   http://weibo.com/tianlesoftware

Twitter:  http://twitter.com/tianlesoftware

Facebook: http://www.facebook.com/tianlesoftware

Linkedin: http://cn.linkedin.com/in/tianlesoftware

DBA1 群:62697716(满);   DBA2 群:62697977(满)  DBA3 群:62697850(满)  

DBA 超级群:63306533(满);  DBA4 群:83829929(满) DBA5群: 142216823(满) 

DBA6 群:158654907(满)   DBA7 群:69087192(满)  DBA8 群:172855474

DBA 超级群2:151508914  DBA9群:102954821     聊天 群:40132017(满)

--加群需要在备注说明Oracle表空间和数据文件的关系,否则拒绝申请 

以上fio测试出来的summary.log结果为什么不是这样的 randwrite: (g=0): rw=randwrite, bs=(R) 1024KiB-1024KiB, (W) 1024KiB-1024KiB, (T) 1024KiB-1024KiB, ioengine=libaio, iodepth=64 fio-3.7 Starting 1 process randwrite: (groupid=0, jobs=1): err= 0: pid=74671: Tue Nov 11 10:23:50 2025 write: IOPS=281, BW=282MiB/s (296MB/s)(16.6GiB/60261msec) slat (usec): min=58, max=241, avg=76.21, stdev= 8.04 clat (msec): min=5, max=500, avg=226.85, stdev=90.20 lat (msec): min=5, max=500, avg=226.92, stdev=90.19 clat percentiles (msec): | 1.00th=[ 6], 5.00th=[ 6], 10.00th=[ 6], 20.00th=[ 234], | 30.00th=[ 243], 40.00th=[ 249], 50.00th=[ 253], 60.00th=[ 259], | 70.00th=[ 266], 80.00th=[ 275], 90.00th=[ 288], 95.00th=[ 300], | 99.00th=[ 363], 99.50th=[ 384], 99.90th=[ 439], 99.95th=[ 472], | 99.99th=[ 493] bw ( KiB/s): min=188416, max=4771840, per=100.00%, avg=288905.58, stdev=413009.92, samples=120 iops : min= 184, max= 4660, avg=282.10, stdev=403.33, samples=120 lat (msec) : 10=13.29%, 20=0.02%, 50=0.04%, 100=0.08%, 250=30.44% lat (msec) : 500=56.13%, 750=0.01% cpu : usr=1.87%, sys=0.63%, ctx=15375, majf=0, minf=6 IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.2%, >=64=99.6% submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0% issued rwts: total=0,16993,0,0 short=0,0,0,0 dropped=0,0,0,0 latency : target=0, window=0, percentile=100.00%, depth=64 Run status group 0 (all jobs): WRITE: bw=282MiB/s (296MB/s), 282MiB/s-282MiB/s (296MB/s-296MB/s), io=16.6GiB (17.8GB), run=60261-60261msec Disk stats (read/write): sdb: ios=16/33902, merge=0/0, ticks=76/7628712, in_queue=7466820, util=99.93%
最新发布
11-12
解读以下log,重点关注ramdump_wpss压缩包大小:09-22 10:55:04.612 1000 1732 18358 I subsystem_ramdump: in file_path1: /sys/class/devcoredump/devcd26/failing_device/device/of_node/name. 09-22 10:55:04.612 1000 1732 18358 I subsystem_ramdump: in file_path2: /sys/class/devcoredump/devcd26/failing_device/of_node/name. 09-22 10:55:04.612 1000 1732 18358 I subsystem_ramdump: in file_path3: /sys/class/devcoredump/devcd26/failing_device. 09-22 10:55:04.612 1000 1732 18358 E subsystem_ramdump: found device name in /sys/class/devcoredump/devcd26/failing_device 09-22 10:55:04.613 1000 1732 18358 I subsystem_ramdump: open /sys/class/devcoredump/devcd26/data with fd: 5 09-22 10:55:04.613 1000 1732 18358 I subsystem_ramdump: dev_name = remoteproc-wpss-md 09-22 10:55:04.613 1000 1732 18358 E subsystem_ramdump: Directory /data/vendor/bsplog/wlan/ssr_dump/2025-09-22-10:55:04 does not exist, ret:-1, error:2 09-22 10:55:04.613 1000 1732 18358 I subsystem_ramdump: Attemping to create /data/vendor/bsplog/wlan/ssr_dump/2025-09-22-10:55:04 09-22 10:55:04.614 1000 1732 18358 I subsystem_ramdump: folder_path: /data/vendor/bsplog/wlan/ssr_dump/2025-09-22-10:55:04. 09-22 10:55:04.614 1000 1020 6340 D HypSys-LogMgrFileEventListener: [OnFileEvent] fileName: 2025-09-22-10:55:04, basePath: /data/vendor/bsplog/wlan/ssr_dump 09-22 10:55:04.614 1000 1020 1041 I HypSys-LogManagerVendor: [CheckAndClean] Start Checking /data/vendor/bsplog/wlan/ssr_dump 09-22 10:55:04.614 1000 1732 18358 I subsystem_ramdump: file_path2: /data/vendor/bsplog/wlan/ssr_dump/2025-09-22-10:55:04/ramdump_wpss_2025-09-22_10-55-04. 09-22 10:55:04.614 1000 1732 18358 I subsystem_ramdump: dump_name_buf: ramdump_wpss. 09-22 10:55:04.614 1000 1732 18358 I subsystem_ramdump: data_fd: 5 09-22 10:55:04.614 1000 1020 1041 W libc : Access denied finding property "persist.sys.abreuse.abstatus" 09-22 10:55:04.614 1000 1020 1041 D HypSys-LogManagerVendor: [isReuseOpen] isReuseOpen 0 09-22 10:55:04.614 1000 1020 1041 I HypSys-LogManagerVendor: [CheckAndClean] fullPath: /data/vendor/bsplog/wlan/ssr_dump/2025-09-22-10:53:51; reusePath: /mnt/reuse/bsplog/wlan/ssr_dump; reuseFullPath: /mnt/reuse/bsplog/wlan/ssr_dump/2025-09-22-10:53:51 09-22 10:55:04.614 1000 1020 1041 I HypSys-LogManagerVendor: [CheckAndClean] Clean Start: fileName 2025-09-22-10:53:51, fileNameList size 6, totalSize 134563222, NowTime 1758509704614(ms), MaxOffsetTime 604800000(ms), time offset 1757904904614(ms) 09-22 10:55:04.614 1000 1020 1041 W libc : Access denied finding property "persist.sys.abreuse.abstatus" 09-22 10:55:04.614 1000 1020 1041 D HypSys-LogManagerVendor: [isReuseOpen] isReuseOpen 0 09-22 10:55:04.614 1000 1020 1041 I HypSys-LogManagerVendor: [CheckAndClean] Delete File By Inital Logic. 09-22 10:55:04.609 1000 1020 1020 W LogManager: type=1400 audit(0.0:3832): avc: denied { read } for name="u:object_r:abreuse_prop:s0" dev="tmpfs" ino=107 scontext=u:r:hal_misys_vendor_default:s0 tcontext=u:object_r:abreuse_prop:s0 tclass=file permissive=0 09-22 10:55:04.609 1000 1020 1020 W LogManager: type=1400 audit(0.0:3833): avc: denied { read } for name="u:object_r:abreuse_prop:s0" dev="tmpfs" ino=107 scontext=u:r:hal_misys_vendor_default:s0 tcontext=u:object_r:abreuse_prop:s0 tclass=file permissive=0 09-22 10:55:04.617 1000 1020 1041 I HypSys-LogManagerVendor: [DeleteFileUpdateDirConfig] DeleteDirectoryOrFile succeed, removed size 19223807 bytes (18 MB) 09-22 10:55:04.617 1000 1020 1041 I HypSys-LogManagerVendor: [CheckAndClean] fullPath: /data/vendor/bsplog/wlan/ssr_dump/2025-09-22-10:54:02; reusePath: /mnt/reuse/bsplog/wlan/ssr_dump; reuseFullPath: /mnt/reuse/bsplog/wlan/ssr_dump/2025-09-22-10:54:02 09-22 10:55:04.617 1000 1020 1041 I HypSys-LogManagerVendor: [CheckAndClean] Clean Start: fileName 2025-09-22-10:54:02, fileNameList size 5, totalSize 115339415, NowTime 1758509704617(ms), MaxOffsetTime 604800000(ms), time offset 1757904904617(ms) 09-22 10:55:04.617 1000 1020 1041 W libc : Access denied finding property "persist.sys.abreuse.abstatus" 09-22 10:55:04.617 1000 1020 1041 D HypSys-LogManagerVendor: [isReuseOpen] isReuseOpen 0 09-22 10:55:04.613 1000 1020 1020 W LogManager: type=1400 audit(0.0:3834): avc: denied { read } for name="u:object_r:abreuse_prop:s0" dev="tmpfs" ino=107 scontext=u:r:hal_misys_vendor_default:s0 tcontext=u:object_r:abreuse_prop:s0 tclass=file permissive=0 09-22 10:55:04.620 1000 1020 1041 I HypSys-LogManagerVendor: [DeleteFileUpdateDirConfig] DeleteDirectoryOrFile succeed, removed size 19223814 bytes (18 MB) 09-22 10:55:04.621 root 983 983 E hypsys_system: Begin to connectTrackBinderLocked 09-22 10:55:04.621 root 983 983 E hypsys_system: reportOneTrackEvent: 31000401754 09-22 10:55:04.714 10286 11721 12033 D JavaheapMonitor: Java heap used=3M max=256M, proc: com.google.android.rkpdapp 09-22 10:55:04.715 10286 11721 12033 V JavaheapMonitor: Check java heap usage finished! Next check delay: 300000 09-22 10:55:04.813 1000 1366 1366 I Diag-Router: diag: received qrtr new client notify for cntl ch periph:3 09-22 10:55:04.813 1000 1366 1366 I Diag-Router: diag: rcvd qrtr new client on ctrl chnl for perif: 3, node: 1, port: 401d, svc: 0, ins: 0 09-22 10:55:04.813 1000 1366 1366 I Diag-Router: diag: In diag_cntl_feature_mask received feature mask from [wcnss] mask 09-22 10:55:04.813 1000 1366 1366 I Diag-Router: diag: diag_cntl_send_feature_mask: Sending feature mask to perif wcnss 09-22 10:55:04.813 1000 1366 1366 D Diag-Router: diag: queue_push_cntlq: Sending cntl pkt of len: 18 to perif: wcnss with port: node [401d: 1] 09-22 10:55:04.814 1000 1366 1366 E Diag-Router: diag: diag_cntl_process_diag_id: received diag id request ctrl pkt from perif: wcnss 09-22 10:55:04.814 1000 1366 1366 E Diag-Router: diag: diag_cntl_process_diag_id: sent diag id ctrl pkt with id: 7 for process: msm/wpss/root_pd 09-22 10:55:04.814 1000 1366 1366 D Diag-Router: diag: queue_push_cntlq: Sending cntl pkt of len: 33 to perif: wcnss with port: node [401d: 1] 09-22 10:55:04.814 1000 1366 1366 D Diag-Router: diag: diag_config_perif_buf: Config request for buffering mode: 0 peripheral:3 diag id:2 periph id:3 09-22 10:55:04.814 1000 1366 1366 D Diag-Router: diag: diag_config_perif_buf: Config request for buffering mode: 0 peripheral:3 diag id:2 periph id:3 09-22 10:55:04.814 1000 1366 1366 D Diag-Router: diag: queue_push_cntlq: Sending cntl pkt of len: 13 to perif: wcnss with port: node [401d: 1] 09-22 10:55:04.814 1000 1366 1366 D Diag-Router: diag: No mask set, skip updating empty masks to peripheral: wcnss 09-22 10:55:04.815 1000 1366 1366 I Diag-Router: diag: Connecting CMD socket to 13: 11 perif: 3 09-22 10:55:04.815 1000 1366 1366 I Diag-Router: diag: rcvd qrtr new server on cmd chnl for perif: 3, node: 1, port: 401e, svc: 4097, ins: 0 09-22 10:55:04.817 root 1280 18371 I resolv : GetAddrInfoHandler::run: {113 113 113 983153 10232 0} 09-22 10:55:04.817 root 1280 18371 I resolv : GetAddrInfoHandler::run: network access blocked 09-22 10:55:04.818 root 1280 18372 I resolv : GetAddrInfoHandler::run: {113 113 113 983153 10232 0} 09-22 10:55:04.819 root 1280 18372 I resolv : GetAddrInfoHandler::run: network access blocked 09-22 10:55:05.012 10161 6255 6369 D JavaheapMonitor: Java heap used=4M max=256M, proc: com.google.android.gms.unstable 09-22 10:55:05.013 10161 6255 6369 V JavaheapMonitor: Check java heap usage finished! Next check delay: 300000 09-22 10:55:05.013 1000 1586 1586 W binder:1586_2: type=1400 audit(0.0:3835): avc: denied { search } for name="mcd" dev="dm-57" ino=859 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:mcd_data_file:s0 tclass=dir permissive=0 09-22 10:55:05.309 1000 2494 3049 D PowerKeeperPolicy: hasAlarmRestrict uid=10161 tag=*alarm*:com.google.android.gms.gcm.ACTION_CHECK_QUEUE ret=false 09-22 10:55:05.309 1000 2494 3049 I SmartPower: com.google.android.gms.unstable/10161(6255): idle->background(2020ms) R(alarm start) adj=250. 09-22 10:55:05.309 1000 2494 3049 I SmartPower: com.google.android.gms/10161(5042): idle->background(2021ms) R(alarm start) adj=500. 09-22 10:55:05.311 1000 2494 3049 D AlarmManager: mBroadcastRefCount -> 1 09-22 10:55:05.312 1000 2494 3049 I whetstone.activity: Power Event callback listener is empty for resId=128 09-22 10:55:05.312 1000 2494 3049 D BatteryStatsManagerStub: notifyEvent for resId=128 used 0ms 09-22 10:55:05.316 1000 2494 3746 D BroadcastQueue: Logging broadcast for com.google.android.gms, stopped=false, firstLaunch=false 09-22 10:55:05.318 1000 2494 2494 D AlarmManager: mBroadcastRefCount -> 0 09-22 10:55:05.318 1000 2494 2494 D AlarmManager: mPendingIntent -> PendingIntent{4909799: PendingIntentRecord{1f2e1cb com.google.android.gms/com.google.android.gms.scheduler broadcastIntent}} 09-22 10:55:05.321 1000 2494 3746 E AlarmManager: not align this alarm: Alarm{9175a5e type 3 origWhen 580778 whenElapsed 580778 com.google.android.gms}, reason=0 09-22 10:55:05.455 10177 6143 8294 D JavaheapMonitor: Java heap used=3M max=256M, proc: com.miui.analytics 09-22 10:55:05.456 10177 6143 8294 V JavaheapMonitor: Check java heap usage finished! Next check delay: 300000 09-22 10:55:05.549 1000 8361 8421 D JavaheapMonitor: Java heap used=6M max=256M, proc: com.miui.powerkeeper 09-22 10:55:05.549 10308 8517 9990 D JavaheapMonitor: Java heap used=5M max=256M, proc: com.google.android.permissioncontroller 09-22 10:55:05.549 1000 8361 8421 V JavaheapMonitor: Check java heap usage finished! Next check delay: 300000 09-22 10:55:05.550 10308 8517 9990 V JavaheapMonitor: Check java heap usage finished! Next check delay: 300000 09-22 10:55:05.618 1073 3569 3632 D JavaheapMonitor: Java heap used=5M max=256M, proc: com.android.networkstack.process 09-22 10:55:05.618 1073 3569 3632 V JavaheapMonitor: Check java heap usage finished! Next check delay: 300000 09-22 10:55:05.658 1000 1586 1586 D MI-SF : setIdleFps choose FPS:60, mode:0 09-22 10:55:05.658 1000 1586 1586 D DisplayModeController: setDesiredMode 4630947082694737281 {mode={fps=60.00 Hz, modePtr={id=2, vsyncRate=60.00 Hz, peakRefreshRate=60.00 Hz}}, emitEvent=false, force=false} 09-22 10:55:05.659 wifi 1448 1489 E WifiHAL : wifi_get_link_stats: requestResponse Error:-5 09-22 10:55:05.659 1000 2494 3171 E WifiStaIfaceAidlImpl: getLinkLayerStats failed with service-specific exception: android.os.ServiceSpecificException: (code 7) 09-22 10:55:05.660 1000 2494 3171 D WifiClientModeImpl[20170:wlan0]: updateLinkLayerStatsRssiSpeedFrequencyCapabilities rssi=-127 TxLinkspeed=0 freq=0 RxLinkSpeed=0 09-22 10:55:05.661 1000 2494 3171 V WifiConfigManager: Updating scan detail cache freq=5745 BSSID=cc:d8:43:ca:e6:ee RSSI=-23 for "Xiaomi_F2BC-be+ax"WPA_PSK 09-22 10:55:05.661 1000 2494 3171 D WifiChannelUtilization: MTK platform ? false 09-22 10:55:05.661 1000 2494 3171 D WifiThroughputPredictor: utilization (LLS) 15 isBluetoothConnected: false final utilization: 15 09-22 10:55:05.661 1000 2494 3171 D WifiThroughputPredictor: BW: 2 RSSI: -23 Nss: 1 Mode: 5 symDur: 3600 snrDb 51 bitPerTone: 6667 rate: 433 throughput: 407 09-22 10:55:05.661 1000 2494 3171 D WifiThroughputPredictor: utilization (LLS) 15 isBluetoothConnected: false final utilization: 15 09-22 10:55:05.661 1000 2494 3171 D WifiThroughputPredictor: BW: 2 RSSI: -23 Nss: 1 Mode: 5 symDur: 3600 snrDb 51 bitPerTone: 6667 rate: 433 throughput: 407 09-22 10:55:05.662 1000 2494 3171 D WifiThroughputPredictor: utilization (LLS) 15 isBluetoothConnected: false final utilization: 15 09-22 10:55:05.662 1000 2494 3171 D WifiThroughputPredictor: BW: 2 RSSI: -23 Nss: 1 Mode: 5 symDur: 3600 snrDb 51 bitPerTone: 6667 rate: 433 throughput: 407 09-22 10:55:05.662 1000 2494 3171 D WifiThroughputPredictor: utilization (LLS) 15 isBluetoothConnected: false final utilization: 15 09-22 10:55:05.662 1000 2494 3171 D WifiThroughputPredictor: BW: 2 RSSI: -23 Nss: 1 Mode: 5 symDur: 3600 snrDb 51 bitPerTone: 6667 rate: 433 throughput: 407 09-22 10:55:05.662 1000 2494 3171 E AmlWifiScoreReportInjector: AmlWifiScoreReportInjector was cleared 09-22 10:55:05.662 1000 2494 3171 D WifiOptimizationImpl: AmlWifiScoreReportInjector.get() = null, stop reportTxBadOrRetryEvent 09-22 10:55:05.663 1000 2494 3171 D WifiScoreCard: BSSID update SIGNAL_POLL ID: 473636673 SSID: "Xiaomi_F2BC-be+ax", BSSID: cc:d8:43:ca:e6:ee, MAC: 9a:35:c7:8a:30:80, IP: /192.168.31.169, Security type: 2, Supplicant state: COMPLETED, Wi-Fi standard: 11ac, RSSI: -23, Link speed: 433Mbps, Tx Link speed: 433Mbps, Max Supported Tx Link speed: 433Mbps, Rx Link speed: 433Mbps, Max Supported Rx Link speed: 433Mbps, Frequency: 5745MHz, Net ID: 3, Metered hint: false, score: 60, isUsable: true, CarrierMerged: false, SubscriptionId: -1, IsPrimary: 1, Trusted: true, Restricted: false, Ephemeral: false, OEM paid: false, OEM private: false, OSU AP: false, FQDN: <none>, Provider friendly name: <none>, Requesting package name: <none>"Xiaomi_F2BC-be+ax"wpa2-pskMLO Information: , Is TID-To-Link negotiation supported by the AP: false, AP MLD Address: <none>, AP MLO Link Id: <none>, AP MLO Affiliated links: <none>, Vendor Data: <none> 09-22 10:55:05.663 1000 2494 3171 D WifiScoreCard: txRate: 0 txSpeed: 433 09-22 10:55:05.663 1000 2494 3171 D WifiScoreCard: network update SIGNAL_POLL "Xiaomi_F2BC-be+ax" ID: 93790497 RSSI -23 txSpeed -1 09-22 10:55:05.664 1000 2494 3171 E AmlWifiScoreReportInjector: AmlWifiScoreReportInjector was cleared
09-23
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值