本帖最后由 郑全 于 2022-7-11 15:47 编辑
如题,trace文件目录产生大量的TRACE文件,文件中,包含 RDMAV_FORK_SAFE,RDMAV_HUGEPAGES_SAFE
具体文件内容如下:
*** 2022-03-23T06:17:15.868135+08:00
Required IPC RDMAV_FORK_SAFE environment not set
Required IPC RDMAV_HUGEPAGES_SAFE environment not set
Trace file D:\ORACLE\diag\rdbms\orclwin\orcl\trace\orcl_ora_15304.trc
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.9.0.0.0
Build label: RDBMS_19.9.0.0.0DBRU_WINDOWS.X64_200930.1
Windows NT Version V6.2
ORACLE_HOME = D:\oracle\product\19.9.0\db_1
Node name : HISSERVER
CPU : 32 - type 866432 physical cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:7544M/49151M, Ph+PgF:56645M/100351M
Instance name: orcl
Redo thread mounted by this instance: 1
Oracle process number: 0
Windows thread id: 15304, image:
这个是19C的一个BUG,见
set Windows Environment Variables RDMAV_FORK_SAFE and RDMAV_HUGEPAGES_SAFE as "0" to prevent the trace outputs
附:
Frequent Trace File Outputs Concerning RDMAV_FORK_SAFE Environment Variable On Windows Oracle 19c (Doc ID 2602978.1)
APPLIES TO:
Oracle Database - Standard Edition - Version 19.3.0.0.0 and later
Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and later
Microsoft Windows x64 (64-bit)
SYMPTOMS
Trace files containing following warnings are frequently generated in Windows platform.
Required IPC RDMAV_FORK_SAFE environment not set
Required IPC RDMAV_HUGEPAGES_SAFE environment not set
CHANGES
CAUSE
The RDMAV environment variables are not relevant on Windows platform, but Oracle 19c checks it and prints warnings when not set.
This is being invstigated in unpublished Bug 30284751 and the conclusion will be updated on this document once the investigation completes.
SOLUTION
As a workaround, set Windows Environment Variables RDMAV_FORK_SAFE and RDMAV_HUGEPAGES_SAFE as "0" to prevent the trace outputs.
|