strms.htm

Debian中文参考手册,系统介绍了Debian系统

<OL CLASS="LN1" TYPE="1">

<LI CLASS="LN1" TYPE="1" VALUE="1"><A NAME="1004646"></A>If the export database contains any destination queues for propagation jobs from other databases, then disable each propagation job that propagates events to the export database. You can disable a propagation job using the <CODE>DISABLE_PROPAGATION_SCHEDULE</CODE> procedure in the <CODE>DBMS_AQADM</CODE> package.
<P>


<LI CLASS="LN1" TYPE="1" VALUE="2"><A NAME="1005077"></A>Make the necessary changes to your network configuration so that the database links used by the propagation jobs you disabled in Step <A HREF="strms.htm#1004646">1</a> point to the computer running the import database.
<P>
 

<A NAME="1005088"></A>
<P CLASS="BP1">
To complete this step, you may need to re-create the database links used by these propagation jobs or modify your Oracle networking files at the databases that contain the source queues.
</P>


<LI CLASS="LN1" TYPE="1" VALUE="3"><A NAME="1004647"></A>Notify all users to stop making data manipulation language (DML) and data definition language (DDL) changes to the export database, and wait until these changes have stopped.
<P>

<LI CLASS="LN1" TYPE="1" VALUE="4"><A NAME="1004651"></A>Make a note of the current export database system change number (SCN). You can determine the current SCN using the <CODE>GET_SYSTEM_CHANGE_NUMBER</CODE> function in the <CODE>DBMS_FLASHBACK</CODE> package.
<P>
 

<A NAME="1005262"></A>
<P CLASS="BP1">
After completing this step, do not stop any capture process running on the export database. Step <A HREF="strms.htm#1005015">10</a> instructs you to use the <CODE>V$STREAMS_CAPTURE</CODE> dynamic performance view to ensure that no DML or DDL changes were made to the database after Step <A HREF="strms.htm#1004647">3</a>. The information about a capture process in this view is reset if the capture process is stopped and restarted. 
</P>

<A NAME="1005280"></A>
<P CLASS="BP1">
For the check in Step&nbsp;<A HREF="strms.htm#1005015">10</a> to be valid, this information should not be reset for any capture process. To prevent a capture process from stopping automatically, you may need to set the <CODE>message_limit</CODE> and <CODE>time_limit</CODE> capture process parameters to <CODE>infinite</CODE> if these parameters are set to another value for any capture process.
</P>


<LI CLASS="LN1" TYPE="1" VALUE="5"><A NAME="1004658"></A>If the export database is not running any apply processes, and is not propagating user-enqueued events, then start the full database export now. Make sure that the <CODE>FULL</CODE> export parameter is set to <CODE>y</CODE> so that the required Streams metadata is exported. 
<P>
 

<A NAME="1004687"></A>
<P CLASS="BP1">
If the export database is running one or more apply processes or is propagating user-enqueued events, then do not start the export and proceed to the next step.
</P>


<LI CLASS="LN1" TYPE="1" VALUE="6"><A NAME="1004666"></A>If the export database is running one or more capture processes, then wait until the applied SCN of each capture process has reached or exceeded the SCN determined in Step <A HREF="strms.htm#1004651">4</a>.
<P>
 

<A NAME="1004692"></A>
<P CLASS="BP1">
You can view the applied SCN for each capture process by querying the <CODE>APPLIED_SCN</CODE> column in the <CODE>DBA_CAPTURE</CODE> data dictionary view.
</P>


<LI CLASS="LN1" TYPE="1" VALUE="7"><A NAME="1005057"></A>If the export database has any propagation jobs that are propagating user-enqueued events, then disable these propagation jobs 	using the <CODE>DISABLE_PROPAGATION_SCHEDULE</CODE> procedure in the <CODE>DBMS_AQADM</CODE> package.
<P>

<LI CLASS="LN1" TYPE="1" VALUE="8"><A NAME="1004931"></A>If the export database is running one or more apply processes, or is propagating user-enqueued events, then start the full database export now. Make sure that the <CODE>FULL</CODE> export parameter is set to <CODE>y</CODE> so that the required Streams metadata is exported. If you already started the export in Step <A HREF="strms.htm#1004658">5</a>, then proceed to Step <A HREF="strms.htm#1004857">9</a>.
<P>

<LI CLASS="LN1" TYPE="1" VALUE="9"><A NAME="1004857"></A>When the export is complete, transfer the export dump file to the computer running the import database.
<P>

<LI CLASS="LN1" TYPE="1" VALUE="10"><A NAME="1005015"></A>If the export database is running one or more capture processes, then ensure that all DML and DDL changes on the export database were stopped before the SCN determined in Step <A HREF="strms.htm#1004651">4</a> by completing the following steps:
<P>
 

<OL CLASS="LA2" TYPE="a">

<LI CLASS="LA2" TYPE="a" VALUE="1"><A NAME="1005020"></A>Get the current SCN using the <CODE>GET_SYSTEM_CHANGE_NUMBER</CODE> function in the <CODE>DBMS_FLASHBACK</CODE> package. This SCN will be called the new SCN.
<P>

<LI CLASS="LA2" TYPE="a"><A NAME="1005021"></A>Wait until the capture message number of each capture process has reached or exceeded the new SCN determined in Step <A HREF="strms.htm#1005020">a</a>. You can view the capture message number for each capture process by querying the <CODE>CAPTURE_MESSAGE_NUMBER</CODE> column in the <CODE>V$STREAMS_CAPTURE</CODE> dynamic performance view.
<P>

<LI CLASS="LA2" TYPE="a"><A NAME="1005025"></A>Verify that the enqueue message number of each capture process is less than or equal to the SCN determined in Step <A HREF="strms.htm#1004651">4</a>. You can view the enqueue message number for each capture process by querying the <CODE>ENQUEUE_MESSAGE_NUMBER</CODE> column in the <CODE>V$STREAMS_CAPTURE</CODE> dynamic performance view.
<P>

<A NAME="1005029"></A>
<P CLASS="BP2">
If the enqueue message number of each capture process is less than or equal to the SCN determined in Step <A HREF="strms.htm#1004651">4</a>, then proceed to Step <A HREF="strms.htm#1004856">11</a>. 
</P>

<A NAME="1005177"></A>
<P CLASS="BP2">
However, if the enqueue message number of any capture process is higher than the SCN determined in Step <A HREF="strms.htm#1004651">4</a>, then one or more DML or DDL changes were made after the SCN determined in Step <A HREF="strms.htm#1004651">4</a>, and these changes were captured and enqueued by a capture process. In this case, perform all of the steps in this section again, starting with Step <A HREF="strms.htm#1004646">1</a><A HREF="strms.htm#1004646"></a>.
</P>

<A NAME="1005052">
<DIV ALIGN="CENTER">
<P>
<TABLE CLASS="Note" BORDER="0" WIDTH="80%" CELLPADDING="0" CELLSPACING="0" dir="ltr">
<TR CLASS="Note"><TD CLASS="Note">
<HR>
<A NAME="1005047"></A><FONT FACE="Arial, Helvetica, sans-serif"><STRONG CLASS="NH">Note:</STRONG></FONT>

<A NAME="1005048"></A>
<P CLASS="NB">
For this verification to be valid, each capture process must have been running uninterrupted since Step <A HREF="strms.htm#1004651">4</a>.&nbsp;
<HR>
</TD>
</TR>


</TABLE>

<TABLE CLASS="TableNote" CELLPADDING="3" dir="ltr">
<TR CLASS="TableNote" ALIGN=LEFT VALIGN=TOP><TD CLASS="TableNote">

</TD></TR>
</TABLE>
</DIV>
</A>
 
</OL>


<LI CLASS="LN1" TYPE="1" VALUE="11"><A NAME="1004856"></A>Perform the full database import. Make sure that the <CODE>STREAMS_CONFIGURATION</CODE> and <CODE>FULL</CODE> import parameters are both set to <CODE>y</CODE> so that the required Streams metadata is imported. The default setting is <CODE>y</CODE> for the <CODE>STREAMS_CONFIGURATION</CODE> import parameter. Also, make sure no DML or DDL changes are made to the import database during the import.
<P>

<LI CLASS="LN1" TYPE="1" VALUE="12"><A NAME="1004874"></A>Let users access the import database, and shut down the export database.
<P>

<LI CLASS="LN1" TYPE="1" VALUE="13"><A NAME="1005070"></A>Enable any propagation jobs you disabled in Steps <A HREF="strms.htm#1004646">1</a> and <A HREF="strms.htm#1005057">7</a>.
<P>

<LI CLASS="LN1" TYPE="1" VALUE="14"><A NAME="1005346"></A>If you reset the value of a <CODE>message_limit</CODE> or <CODE>time_limit</CODE> capture process parameter in Step <A HREF="strms.htm#1004651">4</a>, then reset these parameters to their original settings.
<P>
 
</OL>

<A NAME="1005360"></A>
<!--TOC=h1-"1005360"-->
<H2 CLASS="H1"><FONT FACE="Arial, Helvetica, sans-serif" COLOR="#330099"> Documentation Corrections</FONT></H2>


<!--/TOC=h1-->
<A NAME="1005361"></A>
<P CLASS="BP">
The following are corrections to the <EM CLASS="Italic">Oracle9i Streams</EM> document:
</P>

<UL CLASS="LB1">

<LI CLASS="LB1" TYPE="DISC"><A NAME="1005365"></A>In Chapter 2, "Streams Capture Process", in the "Datatypes Captured" section, the following sentence on page 2-7 is incorrect: "The capture process raises an error if it attempts to capture DML changes to a table that contains a column of an unsupported datatype."
<P>

<A NAME="1005389"></A>
<P CLASS="BP1">
This sentence should be replaced with the following:
</P>

<A NAME="1005392"></A>
<P CLASS="BP1">
The capture process raises an error when it finds a change that satisfies one of its rules to a column with a datatype that is not listed. If, however, a DML statement changes certain columns in a row, but does not change columns that cannot be captured by the capture process, then the capture process captures the changes resulting from the DML statement without raising an error. When the capture process raises an error, it writes the LCR that caused the error into its trace file, raises an ORA-00920 error, and becomes disabled.
</P>

<LI CLASS="LB1" TYPE="DISC"><A NAME="1005436"></A>In Chapter 2, "Streams Capture Process", in the "Types of DML Changes Captured" section, the following sentence in the note on page 2-8 is incomplete: "The capture process cannot capture DML changes made to index-organized tables or object tables."
<P>

<A NAME="1005437"></A>
<P CLASS="BP1">
This sentence should be replaced with the following:
</P>

<A NAME="1005454"></A>
<P CLASS="BP1">
The capture process cannot capture DML changes made to temporary tables, index-organized tables, or object tables.
</P>

<LI CLASS="LB1" TYPE="DISC"><A NAME="1005418"></A>In Chapter 4, "Streams Apply Process", in the "Types of DDL Changes Ignored by an Apply Process" section, the following sentence in the note on page 4-20 is incorrect and should be removed: "An apply process only applies captured DDL LCRs. It ignores user-enqueued DDL LCRs." An apply process can apply valid, user-enqueued DDL LCRs.
<P>

<A NAME="1005416"></A>
<P CLASS="BP1">

</P>
</UL>






<!-- Start Footer -->
</DIV>

<DIV CLASS="OUTD">
<HR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD VALIGN="BOTTOM" WIDTH="33%">
<TABLE CELLSPACING="0" CELLPADDING="0">
<TR>
<TD ALIGN="CENTER"><A HREF="sqlrf.htm"><IMG SRC="larrow.gif" ALT="Go to previous page" BORDER="0" HEIGHT="30" WIDTH="40"></A></TD>

<TD ALIGN="CENTER"><A HREF="arpls.htm"><IMG SRC="rarrow.gif" ALT="Go to next page" BORDER="0" HEIGHT="30" WIDTH="40"></A></TD>
    
</TR>
</TABLE>
</TD>
<TD ALIGN="CENTER" WIDTH="34%">
<font size="-2">Copyright &copy; 2002 Oracle Corporation.</font>
<BR>
<FONT SIZE="-2">All Rights Reserved.</FONT>
</TD>
<TD VALIGN="BOTTOM" ALIGN="RIGHT" WIDTH="33%"> 
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="144">
<TR>





<TD ALIGN="CENTER" VALIGN="TOP" WIDTH="25%"><A HREF="toc.htm"><IMG SRC="conticon.gif" ALT="Go To Table Of Contents" BORDER="0" HEIGHT="30"
WIDTH="30"><BR>
<FONT SIZE="-2">Contents</FONT></A></TD>
<TD ALIGN="CENTER" VALIGN="TOP" WIDTH="25%"><A HREF="index.htm"><IMG SRC="indxicon.gif" ALT="Go To Index" BORDER="0" HEIGHT="30"
WIDTH="30"><BR>
<FONT SIZE="-2">Index</FONT></A></TD>

</TR>
</TABLE>
</TD>
</TR>
</TABLE>
  
</DIV>

</BODY>
</HTML>