ITPub博客

 ORAchk Health Checks for the Oracle StackORAchk replaces the popular RACcheck tool, extending the coverage based on prioritization of top issues reported by users, to proactively scan for known problems within the area of:Oracle Database...

SQLT Diagnostic Tool (Doc ID 215187.1)FAQ: SQLT (SQLTXPLAIN) Frequently Asked Questions (Doc ID 1454160.1)[@more@]SQLT Diagnostic Tool (Doc ID 215187.1)To BottomModified:15-Oct-2013Type:DIAGNOSTIC TOOLSLanguage:English简体中文日本語 In this DocumentMain Content Download SQLTXPLAIN (SQLT) What is SQLTXPLAIN (SQLT)? Installation SQLTXPLAIN Reference Material SQLTXPLAIN FAQ SQLTXPLAIN Webinars Best Practices Ask Questions, Get Help, And Share Your Experiences With SQLT Pro-Active Problem Avoidance

ADG 容灾切换--- 2013.10.16 22:30 -- 2013.10.17 06:30留个脚印 primary 站点执行了切换命令后，standby 站点切换 primary 不成功的恢复步骤。[@more@]Roll Back After Unsuccessful Switchover and Start OverFor physical standby databases in situations where an error occurred and it is notpossible to continue with the switchover, it might still be possible to revert the newphysical standby database back to the primary role by using the following steps:1. Connect to the new standby database (old primary), an

Oracle RAC Background processes[@more@]RAC Background Processes:1. Lock Monitor Processes ( LMON)2. Lock Monitor Services (LMS)3. Lock Monitor Daemon Process ( LMD)4. LCKn ( Lock Process)5. DIAG (Diagnostic Daemon)1. Lock Monitor Processes ( LMON)It Maintains GCS memory structures.Handles the abnormal termination of processes and instances.Reconfiguration of locks & resources when an instance joins or leaves the cluster are handled by LMON ( During reconfiguration LMON generate the trace fil

Oracle Database Fails to Start with Error ORA-12547 [ID 1307075.1][@more@]Oracle Database Fails to Start with Error ORA-12547 [ID 1307075.1]To BottomModified:Nov 30, 2012Type:PROBLEMStatus:PUBLISHEDPriority:3Comments (0)In this DocumentSymptomsCauseSolutionApplies to:Oracle Server - Enterprise Edition - Version 11.2.0.2 and laterInformation in this document applies to any platform.***Checked for relevance on 17-Oct-2012*** Symptoms1. When attempting to startup database,the following error occurs

DBWR_IO_SLAVES [@more@]DBWR_IO_SLAVESIf it is not practical to use multiple DBWR processes, then Oracle provides a facility whereby the I/O load can be distributed over multiple slave processes. The DBWR process is the only process that scans the buffer cache LRU list for blocks to be written out. However, the I/O for those blocks is performed by the I/O slaves. The number of I/O slaves is determined by the parameter DBWR_IO_SLAVES.DBWR_IO_SLAVES is intended for scenarios where you cannot use m

From Tom[@more@]Submitted on 11-Oct-2012 9:48 Central time zoneTom's latest followup | Bookmark | BottomLast updated 11-Oct-2012 17:01You AskedTom, We are moving from older version of Oracle to new verion 11.2.0.3. The DBA's want to load 11.2.0.3 on dev and set compatibility to 10. whatever. then put 11.2.0.3 on production and set compability tha same. After this is working they want to increase compaibilty to 11.2 in dev and if it works out, they will do the same on production. They want to do

时间 2012.10.25 08:50 -- 2012.10.25 11:10emc 存储故障，导致 11.2.0.2 linux RAC 数据库停机[@more@]一大帮领导站在身后督战，太锻炼人了。

DBV-00201: Block, DBA 1175408467, marked corrupt for invalid redo application [@more@]问题：　　　一个朋友在做数据库异机恢复时，整个 restore , recover 过程都顺利进行，数据库也可以正常 open 。 但是他对一些数据文件执行 dbv 时报以下错误。DBV-00201: Block, DBA 1175408467, marked corrupt for invalid redo application DBV-00201: Block, DBA 1175408468, marked corrupt for invalid redo application DBV-00201: Block, DBA 1175408469, marked corrupt for invalid redo application DB

SPB[@more@]手工把 plan 改为 accepted 状态；只有处于 accepted 状态的 plan 才可能被用来执行 sql :variable v_sql_handle varchar2(30);variable v_plan_name_full varchar2(30);variable v_plan_name_index varchar2(30);exec :v_sql_handle := 'SYS_SQL_0993bcb3526c1c35';exec :v_plan_name_full := 'SQL_PLAN_a8qny22gsbtd494ecae5c';exec :v_plan_name_index := 'SQL_PLAN_a8qny22gsbtd40893a4b2';variable v_report clob;exec :v_report := DBMS_SPM.EVOLVE_SQL_PLAN_BASELINE(sql_handle => :v_sql_handle);prin

adrciADR uses what it refers to as a flood-controlled incident system, whereby itallows only a certain number of incidents under a problem to log diagnostic data.By default, ADR allows 5 diagnostic data dumps per hour for a single problem. If anincident occurs 20 times but all the incidents are connected to the same problem,you have to report to Oracle Support only one incident. Flood-controlled incidentreporting ensures that numerous incidents pertaining to the same problem don’toverwhelm th

C:Documents and Settingsadmin>rman target system/oracle@acrac恢复管理器: Release 10.2.0.1.0 - Production on 星期五 9月 7 12:19:59 2012Copyright (c) 1982, 2005, Oracle. All rights reserved.RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-00554: 内部恢复管理器程序包初始化失败RMAN-04005: 目标数据库中存在错误:ORA-01031: insuffici

http://candon123.blog.51cto.com/704299/420303[@more@]

http://www.mhprofessional.com/downloads/products/0071496823/0071496823_errata.txt[@more@]

在 disable flashback data archive 后，数据库产生大量归档日志，最后通过关闭重起数据库来解决。[@more@]通过以下命令把当前在线日志文件dump 出来： SQL> alter system dump logfile '/oradata/SFRAC/onlinelog/o1_mf_1_1PP7b3bt4_.log'; System altered. SQL> 以下是 dump 出文件的部份内容： Trace file /u01/app/oracle/diag/rdbms/sfrac/sfrac1/trace/sfrac1_ora_27254.trc Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production With the Parti

dbms_scheduler ps -ef|grep ora_j|kill -9 `awk {'print $2'}`[@more@]SQL> exec dbms_scheduler.disable(name=>'INSERT_TEST_JOB',force=>true); PL/SQL procedure successfully completed.SQL> SQL> select job_name ,state from user_scheduler_jobs2 ; JOB_NAME STATE------------------------------ ---------------INSERT_TEST_JOB DISABLEDSQL> SQL> exec dbms_system.set_sql_trace_in_session(32,1633,true);PL/SQL procedure successfully completed.SQL>select * from v$lock where id1=76777;

from : http://blog.tanelpoder.com/2009/08/13/alter-system-kill-session-and-ora-00031-session-marked-for-kill/#more-391[@more@]I’m sure you are all familiar with this situation:SQL> alter system kill session '152,33'; alter system kill session '152,33' * ERROR at line 1: ORA-00031: session marked for killThe session trying to issue the kill will hang for 60 seconds and then return this “session marked for kill” message. And the target session does not get killed at all.So why is that?Th

该参数对 add column 没有效果，add column 一直处于等待状态。[@more@]

bash-3.2# lsattr -E -l sys0 -a maxuprocmaxuproc 128 Maximum number of PROCESSES allowed per user Truebash-3.2# chdev -l sys0 -a maxuproc=8192sys0 changedbash-3.2# lsattr -E -l sys0 -a maxuprocmaxuproc 8192 Maximum number of PROCESSES allowed per user True执行完了，通过以下命令重启listenersrvctl stop listener -n nodenamesrvctl start listener -n nodename相关命令：ulimit -aulimit -Ha[@more@]What does an ORA-4030 mean?This error indicates that the oracle server process is unable to allocate more me

11G Dbconsole 在启动时报以下错误:WARN http: snmehl_connect: connect failed to (ehrprod:1158): Connection refused (error = 111)解决办法是查找emagent的进程，kill掉，再启，最后终于OK了。[oracle@ehrprod persistence]$ ps -ef | grep emagentoracle 19843 1 0 14:03 pts/0 00:00:09 /u01/oracle/product/10.2.0.1/bin/emagentoracle 29162 15448 0 17:04 pts/1 00:00:00 grep emagent[oracle@ehrprod persistence]$ kill -9 19843[@more@]