标签云
asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 kfed MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-01110 ORA-01555 ORA-01578 ORA-08103 ORA-600 2131 ORA-600 2662 ORA-600 2663 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 Oracle 恢复 ORACLE恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (102)
- 数据库 (1,682)
- DB2 (22)
- MySQL (73)
- Oracle (1,544)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (159)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (7)
- Oracle ASM (67)
- Oracle Bug (8)
- Oracle RAC (53)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (28)
- Oracle备份恢复 (565)
- Oracle安装升级 (92)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (79)
- PostgreSQL (18)
- PostgreSQL恢复 (6)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (37)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (20)
-
最近发表
- 断电引起的ORA-08102: 未找到索引关键字, 对象号 39故障处理
- ORA-00227: corrupt block detected in control file
- 手工删除19c rac
- 解决oracle数据文件路径有回车故障
- .wstop扩展名勒索数据库恢复
- Oracle Recovery Tools工具一键解决ORA-00376 ORA-01110故障(文件offline)
- OGG-02771 Input trail file format RELEASE 19.1 is different from previous trail file form at RELEASE 11.2.
- OGG-02246 Source redo compatibility level 19.0.0 requires trail FORMAT 12.2 or higher
- GoldenGate 19安装和打patch
- dd破坏asm磁盘头恢复
- 删除asmlib磁盘导致磁盘组故障恢复
- Kylin Linux 安装19c
- ORA-600 krse_arc_complete.4
- Oracle 19c 202410补丁(RUs+OJVM)
- ntfs MFT损坏(ntfs文件系统故障)导致oracle异常恢复
- .mkp扩展名oracle数据文件加密恢复
- 清空redo,导致ORA-27048: skgfifi: file header information is invalid
- A_H_README_TO_RECOVER勒索恢复
- 通过alert日志分析客户自行对一个数据库恢复的来龙去脉和点评
- ORA-12514: TNS: 监听进程不能解析在连接描述符中给出的SERVICE_NAME
标签归档:ORA-21561
win平台报ORA-15055 ORA-21561错误处理—增加SharedSection值
有一套win环境的rac,不定期的异常,alert日志经常报ORA-15055 ORA-21561错误,经过分析是由于win默认的Desktop Heap Size值太小导致该问题,以此提醒各位win平台跑oracle 的朋友注意。
alert日志报错
Current log# 6 seq# 1820 mem# 0: +DATA/rac/onlinelog/group_6.3110.876059421 Thread 2 advanced to log sequence 1821 (LGWR switch) Current log# 5 seq# 1821 mem# 0: +DATA/rac/onlinelog/group_5.3109.876059417 Mon Jul 06 14:11:34 2015 WARNING: ASM communication error: op 0 state 0x0 (15055) ERROR: direct connection failure with ASM WARNING: ASM communication error: op 0 state 0x0 (15055) ERROR: direct connection failure with ASM NOTE: Deferred communication with ASM instance Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\rac\rac2\trace\rac2_arc0_276.trc: ORA-15055: 无法连接到 ASM 实例 ORA-21561: 生成 OID 失败 ORA-15055: 无法连接到 ASM 实例 ORA-21561: 生成 OID 失败 NOTE: deferred map free for map id 28882 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\rac\rac2\trace\rac2_arc0_276.trc: ORA-00313: 无法打开日志组 6 (用于线程 2) 的成员 ORA-00312: 联机日志 6 线程 2: '+DATA/rac/onlinelog/group_6.3110.876059421' ORA-17503: ksfdopn: 2 未能打开文件 +DATA/rac/onlinelog/group_6.3110.876059421 ORA-15055: 无法连接到 ASM 实例 ORA-21561: 生成 OID 失败 ARCH: Archival stopped, error occurred. Will continue retrying WARNING: ASM communication error: op 0 state 0x0 (15055) ERROR: direct connection failure with ASM WARNING: ASM communication error: op 0 state 0x0 (15055) ERROR: direct connection failure with ASM NOTE: Deferred communication with ASM instance Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\rac\rac2\trace\rac2_arc0_276.trc: ORA-15055: 无法连接到 ASM 实例 ORA-21561: 生成 OID 失败 ORA-15055: 无法连接到 ASM 实例 ORA-21561: 生成 OID 失败 NOTE: deferred map free for map id 28883 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\rac\rac2\trace\rac2_arc0_276.trc: ORA-00313: 无法打开日志组 6 (用于线程 2) 的成员 ORA-00312: 联机日志 6 线程 2: '+DATA/rac/onlinelog/group_6.3110.876059421' ORA-17503: ksfdopn: 2 未能打开文件 +DATA/rac/onlinelog/group_6.3110.876059421 ORA-15055: 无法连接到 ASM 实例 ORA-21561: 生成 OID 失败
数据库版本
SQL> select * from v$version; BANNER -------------------------------------------------------------------------------- Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production PL/SQL Release 11.2.0.3.0 - Production CORE 11.2.0.3.0 Production TNS for 64-bit Windows: Version 11.2.0.3.0 - Production NLSRTL Version 11.2.0.3.0 - Production
OS版本
SQL> host systeminfo 主机名: RAC2 OS 名称: Microsoft Windows Server 2008 R2 Enterprise OS 版本: 6.1.7601 Service Pack 1 Build 7601 OS 制造商: Microsoft Corporation OS 配置: 独立服务器 OS 构件类型: Multiprocessor Free 注册的所有人: Windows 用户
通过查询MOS,发现该问题主要是由于win的SharedSection设置不足导致,而此类问题可能还导致其他错误,如:TNS12531:TNS:cannot allocate memory。
建议:对于Microsoft Windows 平台数据库,数据库版本为Version 11.2.0.1 to 12.1.0.2的系统,根据实际情况适当增加SharedSection大小。
例如:修改\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\: SharedSection=1024,20480,1024。
这里的第二个为交互式的Desktop Heap Size,第三个是非交互式的Desktop Heap Size,我们主要修改第三个值
ORA-21561: OID generation failed故障解决
数据库无法登陆报ORA-21561: OID generation failed错误
[oracle@essc ~]$ sqlplus XIFENFEI/"www.xifenfei.com"@172.16.50.200/orcl SQL*Plus: Release 11.2.0.4.0 Production on Mon Jun 1 16:52:29 2015 Copyright (c) 1982, 2013, Oracle. All rights reserved. ERROR: ORA-21561: OID generation failed Enter user-name: ERROR: ORA-12545: Connect failed because target host or object does not exist Enter user-name: ERROR: ORA-12545: Connect failed because target host or object does not exist SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
主机名无法ping通
[root@essc ~]# ping essc ping: unknown host essc [root@essc ~]# hostname essc [root@essc ~]# more /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 172.16.10.11 app1 [oracle@essc ~]$ ifconfig eth3 Link encap:Ethernet HWaddr 00:50:56:BB:00:6B inet addr:172.16.10.30 Bcast:172.16.10.255 Mask:255.255.255.0 inet6 addr: fe80::250:56ff:febb:6b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9597 errors:0 dropped:0 overruns:0 frame:0 TX packets:4018 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1549999 (1.4 MiB) TX bytes:470158 (459.1 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:164 errors:0 dropped:0 overruns:0 frame:0 TX packets:164 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:11424 (11.1 KiB) TX bytes:11424 (11.1 KiB)
修改hosts文件
让hosts中含主机名,也就是为了主机名能够ping通
[oracle@essc ~]$ more /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 172.16.10.11 app1 172.16.10.30 essc
数据库登录测试
[oracle@essc ~]$ sqlplus XIFENFEI/"www.xifenfei.com"@172.16.50.200/orcl SQL*Plus: Release 11.2.0.4.0 Production on Mon Jun 1 16:56:39 2015 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> SQL> exit Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
具体见官方说明
Ora-21561: OID Generation Failed (Doc ID 1335327.1)
APPLIES TO: Oracle Net Services - Version 9.2.0.8 to 11.2.0.3 [Release 9.2 to 11.2] Information in this document applies to any platform. ***Checked for relevance on 14-Jan-2013*** SYMPTOMS When attempting to connect to the database using SQL*Plus or DBCA, the following error occurs intermittently: ERROR ----------------------- ORA-21561: OID generation failed CAUSE This could be caused by not having the host name for the target database fully qualified in the hosts file. To verify if you are hitting this issue, the following symptoms should be met: - ORA-21561: OID generation failed. - Hosts file has un-fully qualified entry for the target database host: 127.0.0.1 loopback localhost # loopback (lo0) name/address 10.210.9.111 dbhost In this sample, dbhost is the target db host. This is reported in an unpublished Bug 12597261: "ORA-21561 IF HOSTNAME ENVIRONMENT VARIABLE IS NOT FULLY QUALIFIED", which should be resolved as of 12G. SOLUTION Modify the hosts file to have the fully qualified host names, by adding the fully qualified domain name to the entry. 127.0.0.1 loopback localhost # loopback (lo0) name/address 10.210.9.111 dbhost.sample.com Verify that other environment and service handles are properly defined as well. If this is a Windows environment, please check : Windows: Connections Fail with ORA-12640 or ORA-21561 (Doc ID 744125.1)
再次建议:修改主机名请修改完全,具体参考:linux上安装oracle10g注意事项中修改主机名部分