如何诊断ORA-125XX连接问题

ORA-12560

以下这个Action Script是我收集的在解决ORA-125XX(如ORA-12560)这类网络链接故障时的一些思路,主要包括 现有的网络配置(client & server side)、监听日志、SQLNET Client trace等信息– How to troubleshooting ORA-125** connection issues:

 

 

# CHECK FIREWALL, WINDOWS FIREWALL , ANTI-Virus Software First ! ping hostname tnsping TNS trcroute TNS telnet <hostname> <port>

tracert hostname

client side sqlplus scott/tiger@TNS

& server side sqlplus scott/tiger@TNS

cat /etc/hosts cat /etc/resolv.conf cat /etc/nsswitch.conf ipconfig . . . → Read More: 如何诊断ORA-125XX连接问题

ORA-01075,ORA-09925 Read-only file system问题一例

OEL 5.7 + ORACLE RAC 11.2.0.2 在运行过程中系统监控台出现journal commit I/O error的信息:

SQL> oradebug Message from syslogd@ at Fri Oct 14 21:17:08 2011 … vrh1 kernel: journal commit I/O error [root@vrh1 ~]# tail /var/log/messages Oct 14 21:02:49 vrh1 kernel: [Oracle OKS] ODLM hash size 62500 Oct 14 21:02:49 vrh1 kernel: OKSK-00004: Module load succeeded. Build information: (LOW . . . → Read More: ORA-01075,ORA-09925 Read-only file system问题一例

解决ORA-14098分区交换索引不匹配错误

上周在客户一套BRM系统上执行分区交换Exchange Partition操作的时候出现了ORA-14098错误,该错误是由于分区表上的LOCAL分区索引与非分区表上的索引不匹配造成的,我们来看一下这个错误:

[oracle@rh2 ~]$ oerr ora 14098 14098, 00000, “index mismatch for tables in ALTER TABLE EXCHANGE PARTITION” // *Cause: The two tables specified in the EXCHANGE have indexes which are // not equivalent // *Action: Ensure that the indexes for the two tables have indexes which // follow this rule // For every non . . . → Read More: 解决ORA-14098分区交换索引不匹配错误

ksvcreate: Process creation failed故障一例

今天上午接到电话,用户反映一套10.2.0.4的数据库出现用户无法登录的症状,随即在家里连上VPN远程支持,登上主机以后尝试测试操作系统认证登录和远程登录,发现已经能够正常登录了;为了了解起因,去查看了告警日志alert.log,发现在11:00左右出现大量的ksvcreate:process creation failed错误,具体错误日志如下:

Wed Mar 23 10:00:17 2011 Process m000 died, see its trace file Wed Mar 23 10:00:17 2011 ksvcreate: Process(m000) creation failed Wed Mar 23 10:01:18 2011 Process m000 died, see its trace file Wed Mar 23 10:01:18 2011 ksvcreate: Process(m000) creation failed Wed Mar 23 10:02:19 2011 Process m000 died, see its . . . → Read More: ksvcreate: Process creation failed故障一例

Fractured block found during backing up datafile

一套AIX上的10.2.0.3系统,在rman备份期间告警日志出现如下记录:

======================= alert log record ============================ Hex dump of (file 35, block 1087687) in trace file /oracle/product/10.2.0/admin/MS/udump/ms_ora_103548.trc Corrupt block relative dba: 0x08d098c7 (file 35, block 1087687) Fractured block found during backing up datafile Data in bad block: type: 6 format: 2 rdba: 0x08d098c7 last change scn: 0×0006.44443e06 seq: 0×1 flg: 0×06 spare1: 0×0 spare2: 0×0 . . . → Read More: Fractured block found during backing up datafile

single quote needed in expdp query?

如果在使用数据泵时不采用parfile参数文件的话,query参数指定的查询条件是需要使用单引号括起来的,而当使用parfile时则不需要加上单引号,加上后反而会出现LPX-314: an internal failure occurred错误:

[maclean@rh2 mesg]$ expdp maclean/maclean directory=dump tables=estimate_me query=estimate_me:”where t1<2000″ Export: Release 10.2.0.4.0 – 64bit Production on Tuesday, 02 November, 2010 22:32:33 Copyright (c) 2003, 2007, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 – 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing . . . → Read More: single quote needed in expdp query?

No way to disable datapump estimate?

昨天晚上去客户现场配合一个导入导出作业;这是一套Solaris 10上的10.2.0.1系统,导出采用expdp数据泵工具,需要导出的数据源是一张大小在120G左右的单表,该表存放了最近一年的数据,实际导出时只需要最近三个月的数据,所以使用了QUERY参数,并指定了并行度为2。 该导出作业之前未经测试过,语句也是临时写的,实际执行导出工作时发现在评估阶段(estimate phase)耗费了大约十多分钟的时间,estimate默认使用blocks模式,即通过计算对象段占用的数据库块来预估dumpfile的大小;此外还有statistics模式通过对象的统计信息来推算导出文件的大小:

The block method of estimate is the least accurate. We investigate how many blocks were allocated for the storage segments for the tables specified. If the table had been recently analyzed, the estimate=statistics would be the most accurate. So remember, it is important to generate statistics before calculating the estimate using . . . → Read More: No way to disable datapump estimate?