Ioctl ASYNC_CONFIG error, errno = 1

数据库一直写trc,导致磁盘空间满了。

g2bh8050:hd04ehis > more hd04ehis_ora_21902.trc
/paic/g2bh8050/soft/10g1/app/oracle/admin/hd04ehis/udump/hd04ehis_ora_21902.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Partitioning, Oracle Label Security, Data Mining and Real Application Testing options
ORACLE_HOME = /paic/g2bh8050/dev/xt2/app102052/oracle/product/10.2.0
System name:    HP-UX
Node name:      g2bh8050
Release:        B.11.23
Version:        U
Machine:        ia64
Instance name: hd04ehis
Redo thread mounted by this instance: 1
Oracle process number: 0
Unix process pid: 21902, image: oracle@g2bh8050

Ioctl ASYNC_CONFIG error, errno = 1

 

看了下好像是异步IO的问题

If /dev/async is present and correctly configured, Oracle (for HP only) will use it for memory locking which is needed for async i/o for SGA memory pages via ioctl.

Oracle (for HP only) opens /dev/async successfully only if the /dev/async HP-UX device driver is properly configured for read and write.

This is irrespective of whether the DISK_ASYNCH_IO parameter is set to TRUE.

Problem is Oracle (for HP only) still uses async I/O regardless of the value of init settings
(disk_asynch_io=FALSE and filesystemio_options=none).
The parameter filesystemio_options=none doesn't work.

From the 9.2 until 10.1 version, to inactivate ASYNCH_IO with Oracle, the workaround is to:

chown bin:bin /dev/async
chmod 660 /dev/async

Note: This may impact other applications that wish to use asynch I/O.
It is recommended to shutdown Oracle database before inactivating asynch I/O.

Grant dba group the MLOCK privilege to avoid the Ioctl ASYNC_CONFIG trace file errors:

(1) # /usr/sbin/setprivgrp dba MLOCK
(2) # vi /etc/privgroup
-- This should contain dba MLOCK RTSCHED RTPRIO
(3) # cat /etc/privgroup
dba MLOCK RTSCHED RTPRIO

Since the Oracle 10.2 version, the problem is resolved as these settings stop the tracing:
disk_asynch_io=FALSE
filesystemio_options=none 

 

但是本人还有个疑问就是为啥同一台主机上,公用的同一套oracle软件,其他的库没有报这个错误?

如果哪位高手知道,请指点下小弟。

谢谢

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
IOCTL_READ_PCI_CONFIGIOCTL_WRITE_PCI_CONFIG 是用于读写PCI设备配置空间的Windows I/O控制码。 以下是它们的实现示例: ```c // 读取PCI设备配置空间 BOOL ReadPCIConfig(HANDLE hDevice, DWORD dwBus, DWORD dwSlot, DWORD dwFunction, LPVOID lpBuffer, DWORD dwBytesToRead) { // 构造PCI配置空间的地址 DWORD dwAddress = 0x80000000 | (dwBus << 16) | (dwSlot << 11) | (dwFunction << 8); // 构造输入缓冲区 PCI_CONFIG_INPUT input = {0}; input.dwAddress = dwAddress; input.dwBytesToRead = dwBytesToRead; // 构造输出缓冲区 PCI_CONFIG_OUTPUT output = {0}; // 发送IOCTL请求 DWORD dwBytesReturned = 0; BOOL bSuccess = DeviceIoControl(hDevice, IOCTL_READ_PCI_CONFIG, &input, sizeof(input), &output, sizeof(output), &dwBytesReturned, NULL); // 将结果拷贝到输出缓冲区 if (bSuccess) { memcpy(lpBuffer, output.bResult, dwBytesToRead); } return bSuccess; } // 写入PCI设备配置空间 BOOL WritePCIConfig(HANDLE hDevice, DWORD dwBus, DWORD dwSlot, DWORD dwFunction, LPCVOID lpBuffer, DWORD dwBytesToWrite) { // 构造PCI配置空间的地址 DWORD dwAddress = 0x80000000 | (dwBus << 16) | (dwSlot << 11) | (dwFunction << 8); // 构造输入缓冲区 PCI_CONFIG_INPUT input = {0}; input.dwAddress = dwAddress; input.dwBytesToWrite = dwBytesToWrite; memcpy(input.bData, lpBuffer, dwBytesToWrite); // 发送IOCTL请求 DWORD dwBytesReturned = 0; BOOL bSuccess = DeviceIoControl(hDevice, IOCTL_WRITE_PCI_CONFIG, &input, sizeof(input), NULL, 0, &dwBytesReturned, NULL); return bSuccess; } ``` 这里的 `PCI_CONFIG_INPUT` 和 `PCI_CONFIG_OUTPUT` 是自定义的结构体,定义如下: ```c typedef struct _PCI_CONFIG_INPUT { DWORD dwAddress; // PCI配置空间的地址 DWORD dwBytesToRead; // 要读取的字节数 DWORD dwBytesToWrite; // 要写入的字节数 BYTE bData[256]; // 数据缓冲区 } PCI_CONFIG_INPUT, *PPCI_CONFIG_INPUT; typedef struct _PCI_CONFIG_OUTPUT { BYTE bResult[256]; // 数据缓冲区 } PCI_CONFIG_OUTPUT, *PPCI_CONFIG_OUTPUT; ``` 在实际使用中,需要先打开一个PCI设备的句柄,然后通过该句柄调用 `ReadPCIConfig` 和 `WritePCIConfig` 函数进行读写操作。其中,`dwBus`、`dwSlot` 和 `dwFunction` 分别表示PCI设备的总线号、插槽号和功能号,`lpBuffer` 表示数据缓冲区的指针,`dwBytesToRead` 和 `dwBytesToWrite` 分别表示要读取和写入的字节数。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值