造成胎儿停止发育的原因很多，并非每例病人都能找出确切的原因。但是有些原因是业内专家一致公认的。 　　由于染色体的数目或结构异常所致的胚胎发育不良，是流产最常见的原因，在自然流产中，遗传因素可占50%至60%。这也是一个自然淘汰的过程。导致胎儿染色体异常的原因很多，比如妈妈卵子异常，爸爸精子畸形，有毒化学物质的影响，放射线、高温等都会使胚胎染色体发生异常。 　　内分泌失调也是个重要原因。在内分泌门诊，经常会有"黄体功能不足"的患者，黄体功能不足可引起分泌期子宫内膜发育不良而致孕卵不易着床，或者卵虽然着床却早期流产。 　　孕妇感染也是导致胎停育的一个重要原因。有些比较小的病毒，比如风疹病毒、巨细胞等微小病毒，对母体不会产生什么影响，有的孕妇感染病毒后甚至没有任何症状，但对胎儿的影响可能是致命的。 　　环境污染对孕妇的影响也比较大，虽然目前还没有科学的研究数据，不过医生还是建议孕妇最好注意远离各种辐射，比如看电视最好距离两米以外等

CREATE OR REPLACEPROCEDURE 存储过程名字
(
    参数1 IN NUMBER,
    参数2 IN NUMBER
) IS
变量1 INTEGER :=0;
变量2 DATE;
BEGIN
END 存储过程名字

  BEGIN
  SELECT col1,col2 into 变量1,变量2 FROM typestruct where xxx;
  EXCEPTION
  WHEN NO_DATA_FOUND THEN
      xxxx;
  END;

CREATE OR REPLACE PROCEDURE TESTA(PARA1 IN VARCHAR2,PARA2 IN VARCHAR2) AS
BEGIN
  INSERT INTO HYQ.B_ID (I_ID,I_NAME) S (PARA1, PARA2);
END TESTA;

package com.hyq.src;

import java.sql.*;
import java.sql.ResultSet;

public class TestProcedureOne {
public TestProcedureOne() {
}
public static void main(String[] args ){
    String driver = "oracle.jdbc.driver.OracleDriver";
    String strUrl = "jdbc:oracle:thin:@127.0.0.1:1521: hyq ";
    Statement stmt = null;
    ResultSet rs = null;
    Connection conn = null;
    CallableStatement cstmt = null;

    try {
      Class.forName(driver);
      conn = DriverManager.getConnection(strUrl, " hyq ", " hyq ");
      CallableStatement proc = null;
      proc = conn.prepareCall("{ call HYQ.TESTA(?,?) }");
      proc.setString(1, "100");
      proc.setString(2, "TestOne");
      proc.execute();
    }
    catch (SQLException ex2) {
      ex2.printStackTrace();
    }
    catch (Exception ex2) {
      ex2.printStackTrace();
    }
    finally{
      try {
        if(rs != null){
          rs.close();
          if(stmt!=null){
            stmt.close();
          }
          if(conn!=null){
            conn.close();
          }
        }
      }
      catch (SQLException ex1) {
      }
    }
}
}

CREATE OR REPLACE PROCEDURE TESTB(PARA1 IN VARCHAR2,PARA2 OUT VARCHAR2) AS
BEGIN
  SELECT INTO PARA2 FROM TESTTB WHERE I_ID= PARA1;
END TESTB;

package com.hyq.src;

public class TestProcedureTWO {
public TestProcedureTWO() {
}
public static void main(String[] args ){
    String driver = "oracle.jdbc.driver.OracleDriver";
    String strUrl = "jdbc:oracle:thin:@127.0.0.1:1521:hyq";
    Statement stmt = null;
    ResultSet rs = null;
    Connection conn = null;
    try {
      Class.forName(driver);
      conn = DriverManager.getConnection(strUrl, " hyq ", " hyq ");
      CallableStatement proc = null;
      proc = conn.prepareCall("{ call HYQ.TESTB(?,?) }");
      proc.setString(1, "100");
      proc.registerOutParameter(2, Types.VARCHAR);
      proc.execute();
      String testPrint = proc.getString(2);
      System.out.println("=testPrint=is="+testPrint);
    }
    catch (SQLException ex2) {
      ex2.printStackTrace();
    }
    catch (Exception ex2) {
      ex2.printStackTrace();
    }
    finally{
      try {
        if(rs != null){
          rs.close();
          if(stmt!=null){
            stmt.close();
          }
          if(conn!=null){
            conn.close();
          }
        }
      }
      catch (SQLException ex1) {
      }
    }
}
}

}

CREATE OR REPLACE PACKAGE TESTPACKAGE  AS
TYPE Test_CURSOR IS REF CURSOR;
end TESTPACKAGE;

CREATE OR REPLACE PROCEDURE TESTC(p_CURSOR out TESTPACKAGE.Test_CURSOR) IS
BEGIN
    OPEN p_CURSOR FOR SELECT * FROM HYQ.TESTTB;
END TESTC;

package com.hyq.src;
import java.sql.*;
import java.io.OutputStream;
import java.io.Writer;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import oracle.jdbc.driver.*;


public class TestProcedureTHREE {
public TestProcedureTHREE() {
}
public static void main(String[] args ){
    String driver = "oracle.jdbc.driver.OracleDriver";
    String strUrl = "jdbc:oracle:thin:@127.0.0.1:1521:hyq";
    Statement stmt = null;
    ResultSet rs = null;
    Connection conn = null;

    try {
      Class.forName(driver);
      conn = DriverManager.getConnection(strUrl, "hyq", "hyq");

      CallableStatement proc = null;
      proc = conn.prepareCall("{ call hyq.testc(?) }");
      proc.registerOutParameter(1,oracle.jdbc.OracleTypes.CURSOR);
      proc.execute();
      rs = (ResultSet)proc.getObject(1);

      while(rs.next())
      {
          System.out.println("<tr><td>" + rs.getString(1) + "</td><td>"+rs.getString(2)+"</td></tr>");
      }
    }
    catch (SQLException ex2) {
      ex2.printStackTrace();
    }
    catch (Exception ex2) {
      ex2.printStackTrace();
    }
    finally{
      try {
        if(rs != null){
          rs.close();
          if(stmt!=null){
            stmt.close();
          }
          if(conn!=null){
            conn.close();
          }
        }
      }
      catch (SQLException ex1) {
      }
    }
}
}

有四种类型的Events:

                Immediate dumps

               Conditional dumps

               Trace dumps

               Events that change database behaviour

每一个事件都有一个号跟Oracle的错误信息是一样的.如10046和ORA-10046

每一个事件都有一个Level,可以是以下:

              范围1到10

              位标 0x01 0x02 0x04 0x08 0x10

              标识 0=off,1=on

              ID号 对象ID(object id),内存地址(memory address)

要注意的是,Events在每一个版本之间都有所改变.有一些存在的事件可能存在争议性或者已经不可用了,往往这些事件号会由新的事件所替代掉.也要注意在当前的版本中message file不一定可以反映出Events.

很多Events都会影响数据库的行为,一些测试Events极有可能导致数据库DOWN掉.所以,在没有Oracle Support的前提下,最好不要在PRO系统上做Events操作.DEV系统上如果要做Events最好先做个数据库的全备份.

Events可以在Instance一级Enabled,主要是在INIT.ORA文件中做操作:

        event='event trace name context forever, level level';

(红色部分:event指事件号.level指定事件的级别)

  一次可以Enable多个事件,可以用以下两种方式:

1.  用一个冒号隔开

     event = "10248 trace name context forever, level 10:10249 trace name context forever, level 10"

2.  两个Events分开写

    event="10248 trace name context forever, level 10"

    event="10249 trace name context forever, level 10"#一些版本的Oracle，event要一样的大小写

Events也可以在Instance一级用ALTER SYSTEM命令来Enable:

      ALTER SYSTEM SET EVENTS 'event trace name context forever, level level';

　在Instance一级用以下Disable

      ALTER SYSTEM SET EVENTS 'event trace name context off';

  Events也可以在Session一级用ALTER SESSION命令来Enable:

      ALTER SESSION SET EVENTS 'event trace name context forever, level level';

  在Session一级用以下命令Disable:

ALTER SESSION SET EVENTS 'event trace name context off';

 Events在其他的Session用ORADEBUG来Enable:

 在一个Process中实现Enable:

      ORADEBUG EVENT event TRACE NAME CONTEXT FOREVER, LEVEL level

 在某个进程中Enable:

      ORADEBUG SETORAPID 8(PID进程号)

      ORADEBUG EVENT event TRACE NAME CONTEXT FOREVER, LEVEL level

 以下命令Disable:

  ORADEBUG EVENT event TRACE NAME CONTEXT OFF

在Session中实现Enable:

  ORADEBUG SESSION_EVENT event TRACE NAME CONTEXT FOREVER, LEVEL level

在Session中实现Disable:

  ORADEBUG SESSION_EVENT event TRACE NAME CONTEXT OFF

Events也可以用DBMS_SYSTEM.SETEV包来实现Enable和Disable

    (在做之前要先从V$session视图中获得SID和Serial#)

用以下方式:EXECUTE DBMS_SYSTEM.SET_EV(SID,Serial#,event,level, '')

如EXECUTE dbms_system.set_ev (9,29,10046,8,'');

  要Disable则将level改为0,如: EXECUTE dbms_system.set_ev (9,29,10046,0,'');

Listing All Events:(列出所有可用的Events)

大部分的Events number的范围都在10000到10999.可以用以下命令Dump出所有的信息

SET SERVEROUTPUT ON

DECLARE

   err_msg VARCHAR2(120);

BEGIN

   dbms_output.enable (1000000);

   FOR err_num IN 10000..10999

   LOOP

    err_msg := SQLERRM (-err_num);

    IF err_msg NOT LIKE '%Message '||err_num||' not found%' THEN

      dbms_output.put_line (err_msg);

    END IF;

  END LOOP;

END;

/

在UNIX系统下message文件在底下目录$ORACLE_HOME/rdbms/mesg/oraus.msg

在NT系统下message文件在底下目录$ORACLE_HOME/rdbms/mesg/oraus.msg

Listing Enabled Events(列出Enabled Events)

  用以下命令列出在当前Session已经Enabled Events:

           SET SERVEROUTPUT ON

           DECLARE

               l_level NUMBER;

           BEGIN

               FOR l_event IN 10000..10999

               LOOP

                         dbms_system.read_ev (l_event,l_level);

                         IF l_level > 0 THEN

                          dbms_output.put_line ('Event '||TO_CHAR (l_event)||

                               ' is set at level '||TO_CHAR (l_level));

                         END IF;

                END LOOP;

              END;

             /

常用Events的参考:(红色的为最常用的而且对DBA比较有用的Events)

Event 10013 - Monitor Transaction Recovery------在Startup时跟踪事务恢复

           ALTER SESSION SET EVENTS '10013 trace name context forever, level 1';

Event 10015 - Dump Undo Segment Headers----在事务恢复后做Dump回退段头信息

           ALTER SESSION SET EVENTS '10015 trace name context forever, level 1';

Event 10032 - Dump Sort Statistics----Dump排序的统计信息,level 10是最详细的

            ALTER SESSION SET EVENTS '10032 trace name context forever, level 10';

Event 10033 - Dump Sort Intermediate Run Statistics--level 10

              ALTER SESSION SET EVENTS '10033 trace name context forever, level 10';

Event 10045 - Trace Free List Management Operations--跟踪Freelist

             ALTER SESSION SET EVENTS '10045 trace name context forever, level 1';

Event 10046 - Enable SQL Statement Trace---跟踪SQL,有执行计划,邦定变量和等待的统计信息,level 12最详细

           ALTER SESSION SET EVENTS '10046 trace name context forever, level 12';

级别level参考如下图:

Level Action 1 Print SQL statements, execution plans and execution statistics 4 As level 1 plus bind variables 8 As level 1 plus wait statistics 12 As level 1 plus bind variables and wait statistics

Event 10053 - Dump Optimizer Decisions---在分析SQL语句时,Dump出优化器所做的选择,级别level 1最详细

            ALTER SESSION SET EVENTS '10053 trace name context forever, level 1';

参考level:

Level	Action
1	Print statistics and computations
2	Print computations only

Event 10060 - Dump Predicates---(参考http://www.juliandyke.com/)

Event 10065 - Restrict Library Cache Dump Output for State Object Dumps-(参考http://www.juliandyke.com/)

Event 10079 - Dump SQL*Net Statistics---Dump SQL*NeT的统计信息

            ALTER SESSION SET EVENTS '10079 trace name context forever, level 2';

Event 10081 - Trace High Water Mark Changes--跟踪HWM的改变

            ALTER SESSION SET EVENTS '10081 trace name context forever, level 1';

Event 10104 - Dump Hash Join Statistics--Dump HASH JOIN的统计信息,用level 10

             ALTER SESSION SET EVENTS '10104 trace name context forever, level 10';

Event 10128 - Dump Partition Pruning Information--Dump分区表信息

               ALTER SESSION SET EVENTS '10128 trace name context forever, level level';

  Level参考

Level	Action
0x0001	Dump pruning descriptor for each partitioned object
0x0002	Dump partition iterators
0x0004	Dump optimizer decisions about partition-wise joins
0x0008	Dump ROWID range scan pruning information

在9.0.1或者后面的版本,在level 2后还需要建立如下的表:

CREATE TABLE kkpap_pruning
　　 (
　　 partition_count NUMBER,
　　 iterator VARCHAR2(32),
　　 partition_level VARCHAR2(32),
　　 order_pt VARCHAR2(12),
　　 call_time VARCHAR2(12),
　　 part# NUMBER,
　　 subp# NUMBER,
　　 abs# NUMBER
　　 );

Event 10200 - Dump Consistent Reads---Dump出一致读的信息
　　 ALTER SESSION SET EVENTS '10200 trace name context forever, level 1';
　　Event 10201 - Dump Consistent Read Undo Application
　　 ALTER SESSION SET EVENTS '10201 trace name context forever, level 1';
　　Event 10220 - Dump Changes to Undo Header--Dump出Undo头信息的改变
　　 ALTER SESSION SET EVENTS '10220 trace name context forever, level 1';
　　Event 10221 - Dump Undo Changes--Dump Undo的改变
　　 ALTER SESSION SET EVENTS '10221 trace name context forever, level 7';
　　Event 10224 - Dump Index Block Splits / Deletes--Dump索引块的Split和Delete信息
　　 ALTER SESSION SET EVENTS '10224 trace name context forever, level 1';
　　Event 10225 - Dump Changes to Dictionary Managed Extents---Dump出在Row Cache中,字典管理的Extents的改变
　　 ALTER SESSION SET EVENTS '10225 trace name context forever, level 1';
　　Event 10231--设置在做全表扫描时跳过损坏的数据块（在做EXP时，如果有坏块，

设置这个可以使EXP导出时跳过坏块，使得部分数据能可以使用）
　　 ALTER SYSTEM SET EVENTS '10231 trace name context forever,level 10';
　　Event 10241 - Dump Remote SQL Execution--Dump远程SQL语句的执行信息
　　 ALTER SESSION SET EVENTS '10241 trace name context forever, level 1';
　　Event 10246 - Trace PMON Process---只能在init.ora中做,不能用ALTER SYSTEM做
　　 event = "10246 trace name context forever, level 1"
　　Event 10248 - Trace Dispatcher Processes---在init.ora中做(9iDump到udump目录中)
　　 event = "10248 trace name context forever, level 10"
　　Event 10249 - Trace Shared Server (MTS) Processes---在init.ora中做(9iDump到udump目录中)
　　 event = "10249 trace name context forever, level 10"
　　Event 10270 - Debug Shared Cursors
　　event = "10270 trace name context forever, level 10"
　　Event 10299 - Debug Prefetching---(参考http://www.juliandyke.com/)
　　 event = "10299 trace name context forever, level 1"
　　Event 10357 - Debug Direct Path---(参考http://www.juliandyke.com/)
　　 ALTER SESSION SET EVENTS '10357 trace name context forever, level 1';
　　Event 10390 - Dump Parallel Execution Slave Statistics--(参考http://www.juliandyke.com/)
　　 ALTER SESSION SET EVENTS '10390 trace name context forever, level level';
　　Event 10391-Dump Parallel Execution Granule Allocation---
　　 (参考http://www.juliandyke.com/)
　　 ALTER SESSION SET EVENTS '10391 trace name context forever, level level';
　　Event 10393 - Dump Parallel Execution Statistics--(参考http://www.juliandyke.com/)
　　 ALTER SESSION SET EVENTS '10393 trace name context forever, level 1';
　　Event 10500 - Trace SMON Process--在init.ora中做
　　 event = "10500 trace name context forever, level 1"
　　Event 10608 - Trace Bitmap Index Creation--跟踪二位图索引
　　 ALTER SESSION SET EVENTS '10608 trace name context forever, level 10';
　　Event 10704 - Trace Enqueues--跟踪队列
　　 ALTER SESSION SET EVENTS '10704 trace name context forever, level 1';
　　Event 10706 - Trace Global Enqueue Manipulation-(参考http://www.juliandyke.com/)
　　 ALTER SESSION SET EVENTS '10706 trace name context forever, level 1';
　　Event 10708 - Trace RAC Buffer Cache--跟踪RAC的Buffer Cache
　　 ALTER SESSION SET EVENTS '10708 trace name context forever, level 10';
　　Event 10710 - Trace Bitmap Index Access--(参考http://www.juliandyke.com/)
　　 ALTER SESSION SET EVENTS '10710 trace name context forever, level 1';
　　Event 10711 - Trace Bitmap Index Merge Operation--
　　 ALTER SESSION SET EVENTS '10711 trace name context forever, level 1';
　　Event 10712 - Trace Bitmap Index OR Operation--
　　 ALTER SESSION SET EVENTS '10712 trace name context forever, level 1';
　　Event 10713 - Trace Bitmap Index AND Operation--
　　 ALTER SESSION SET EVENTS '10713 trace name context forever, level 1';
　　Event 10714 - Trace Bitmap Index MINUS Operation--
　　 ALTER SESSION SET EVENTS '10714 trace name context forever, level 1';
　　Event 10715 - Trace Bitmap Index Conversion to ROWIDs Operation--
　　 ALTER SESSION SET EVENTS '10715 trace name context forever, level 1';
　　Event 10716 - Trace Bitmap Index Compress/Decompress--
　　 ALTER SESSION SET EVENTS '10716 trace name context forever, level 1';
　　Event 10717 - Trace Bitmap Index Compaction--
　　 ALTER SESSION SET EVENTS '10717 trace name context forever, level 1';
　　Event 10719 - Trace Bitmap Index DML--
　　 ALTER SESSION SET EVENTS '10719 trace name context forever, level 1';
　　Event 10730 - Trace Fine Grained Access Predicates--
　　 ALTER SESSION SET EVENTS '10730 trace name context forever, level 1';
　　Event 10731 - Trace CURSOR Statements--
　　 ALTER SESSION SET EVENTS '10731 trace name context forever, level level';
　　Levels are:
　　Level　　Action
　　1　　      Print parent query and subquery
　　2    　　   Print subquery only
　　Event 10928 - Trace PL/SQL Execution--
　　 ALTER SESSION SET EVENTS '10928 trace name context forever, level 1';
　　Event 10938 - Dump PL/SQL Execution Statistics--
　　 ALTER SESSION SET EVENTS '10938 trace name context forever, level 1';
　　一些其他的Events：
　　ALTER SESSION SET EVENTS 'immediate trace name flush_cache';--Flush the Buffer cache
   

1).Global Area

ALTER SESSION SET EVENTS 'immediate trace name global_area level n';

1 包含PGA
2 包含SGA
4 包含UGA
8 包含indrect memory

2).Library Cache

ALTER SESSION SET EVENTS 'immediate trace name library_cache level n';

1 library cache统计信息
2 包含hash table histogram
3 包含object handle
4 包含object结构（Heap 0）

3).Row Cache

ALTER SESSION SET EVENTS 'immediate trace name row_cache level n';

1 row cache统计信息
2 包含hash table histogram
8 包含object结构

4).Buffers

ALTER SESSION SET EVENTS 'immediate trace name buffers level n';

1 buffer header
2 level 1 + block header
3 level 2 + block contents
4 level 1 + hash chain
5 level 2 + hash chain
6 level 3 + hash chain
8 level 4 + users/waiters
9 level 5 + users/waiters
10 level 6 + users/waiters

5).Buffer

ALTER SESSION SET EVENTS 'immediate trace name buffer level n';

n为某个指定block的rdba，该命令可以转储某个block在buffer中的所有版本。

6).Heap

ALTER SESSION SET EVENTS 'immediate trace name heapdump level level';

1 PGA摘要
2 SGA摘要
4 UGA摘要
8 Current call(CGA)摘要
16 User call(CGA)摘要
32 Large call(LGA)摘要
1025 PGA内容
2050 SGA内容
4100 UGA内容
8200 Current call内容
16400 User call内容
32800 Large call内容

7).Sub Heap

Oracle 9.0.1版本之前

ALTER SESSION SET EVENTS 'immediate trace name heapdump_addr level n';

若n为subheap的地址，转储的是subheap的摘要信息
若n为subheap的地址+1，转储的则是subheap的内容

Oracle 9.2.0版本之后

ALTER SESSION SET EVENTS 'immediate trace name heapdump_addr level n, addr m';

其中m为subheap的地址

n为1转储subheap的摘要，n为2转储subheap的内容

8).Process State

ALTER SESSION SET EVENTS 'immediate trace name processstate level n';

9).System State

ALTER SESSION SET EVENTS 'immediate trace name systemstate level n';

10).Error State

ALTER SESSION SET EVENTS 'immediate trace name errorstack level n';

0 Error stack
1 level 0 + function call stack
2 level 1 + process state
3 level 2 + context area

11).Hang Analysis

ALTER SESSION SET EVENTS 'immediate trace name hanganalyze level n';

12).Work Area

ALTER SESSION SET EVENTS 'immediate trace name workareatab_dump level n';

1 SGA信息
2 Workarea Table摘要信息
3 Workarea Table详细信息

13).Latches

ALTER SESSION SET EVENTS 'immediate trace name latches level n';

1 latch信息
2 统计信息

14).Events

ALTER SESSION SET EVENTS 'immediate trace name events level n';

1 session
2 process
3 system

15).Locks

ALTER SESSION SET EVENTS 'immediate trace name locks level n';

16).Shared Server Process

ALTER SESSION SET EVENTS 'immediate trace name shared_server_state level n';

n取值为1~14

17).Background Messages

ALTER SESSION SET EVENTS 'immediate trace name bg_messages level n';

n为pid+1

二.File Dumps

1).Block

Oracle 7之前

ALTER SESSION SET EVENTS 'immediate trace name blockdump level n';

n为block的rdba

Oracle8以后

ALTER SYSTEM DUMP DATAFILE file# BLOCK block#;

ALTER SYSTEM DUMP DATAFILE file#
BLOCK MIN minimum_block#
BLOCK MAX maximum_block#;

2).Tree Dump

ALTER SESSION SET EVENTS 'immediate trace name treedump level n';

n为object_id

3).Undo Segment Header

ALTER SYSTEM DUMP UNDO_HEADER 'segment_name';

4).Undo for a Transaction

ALTER SYSTEM DUMP UNDO BLOCK 'segment_name' XID xidusn xidslot xidsqn;

5).File Header

ALTER SESSION SET EVENTS 'immediate trace name file_hdrs level n';

1 控制文件中的文件头信息
2 level 1 + 文件头信息
3 level 2 + 数据文件头信息
10 level 3

6).Control file

ALTER SESSION SET EVENTS 'immediate trace name controlf level n';

1 文件头信息
2 level 1 + 数据库信息 + 检查点信息
3 level 2 + 可重用节信息
10 level 3

7).Redo log Header

ALTER SESSION SET EVENTS 'immediate trace name redohdr level n';

1 控制文件中的redo log信息
2 level 1 + 文件头信息
3 level 2 + 日志文件头信息
10 level 3

8).Redo log

ALTER SYSTEM DUMP LOGFILE 'FileName';

ALTER SYSTEM DUMP LOGFILE 'FileName'
SCN MIN MinimumSCN
SCN MAX MaximumSCN
TIME MIN MinimumTime
TIME MAX MaximumTime
LAYER Layer
OPCODE Opcode
DBA MIN FileNumber . BlockNumber
DBA MAX FileNumber . BlockNumber
RBA MIN LogFileSequenceNumber . BlockNumber
RBA MAX LogFileSequenceNumber . BlockNumber;

其中time = (((((yyyy - 1988)) * 12 + mm - 1) * 31 + dd - 1) * 24 + hh) * 60 + mi) * 60 + ss;

9).Loghist

ALTER SESSION SET EVENTS 'immediate trace name loghist level n';

1 dump控制文件中最早和最迟的日志历史项
>1 dump 2^n个日志历史项