3postins.htm

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

<A NAME="8347"></A>
<P CLASS="BP1">
The following example <CODE>initSALES1.ora</CODE> file shows a sample initialization parameter file for the first instance:
</P>
   
<PRE CLASS="CE1">
<A NAME="8351"></A>ifile=/u01/oracle/admin/SALES/pfile/initSALES.ora
<A NAME="8352"></A>rollback_segments=(rbs1_1, rbs1_2)
<A NAME="8353"></A>thread=1
<A NAME="8354"></A>cluster_database=true
<A NAME="8355"></A>instance_name=SALES1
<A NAME="8356"></A>
</PRE>
   
<A NAME="8795"></A>
<P CLASS="BP1">
The following example <CODE>initSALES2.ora </CODE>file shows a sample initialization parameter file for the second instance:
</P>
   
<PRE CLASS="CE1">
<A NAME="8358"></A>ifile=/u01/oracle/admin/SALES/pfile/initSALES.ora
<A NAME="8359"></A>rollback_segments=(rbs2_1, rbs2_2)
<A NAME="8360"></A>thread=2
<A NAME="8361"></A>cluster_database=true
<A NAME="8362"></A>instance_name=SALES2
<A NAME="8363"></A>
</PRE>
   
<A NAME="8827"></A>
<P CLASS="BP1">
The following example shows the contents of the <CODE>initSALES1.ora</CODE> file for the first instance after embedding the Oracle9<EM CLASS="Italic">i</EM> Real Application Clusters Guard parameter files within an existing parameter file. Make sure not to include multiple entries for the same initialization parameter. Because they are included in the embedded parameter files, the THREAD and CLUSTER_DATABASE parameters have been removed.
</P>
   
<PRE CLASS="CE1">
<A NAME="8371"></A>ifile=/u01/oracle/admin/SALES/pfile/initSALES.ora
<A NAME="8372"></A>ifile=/u01/oracle/admin/SALES/pfile/init_SALES_nodeA.ora
<A NAME="8373"></A>ifile=/u01/oracle/admin/SALES/pfile/SALES_config.pfs
<A NAME="8374"></A>ifile=/u01/oracle/admin/SALES/pfile/SALES_config_nodeA.ded.pfs
<A NAME="8375"></A>rollback_segments=(rbs1_1, rbs1_2)
<A NAME="8376"></A>
</PRE>
   
<A NAME="8815"></A>
<P CLASS="BP1">
The following example shows the contents of the <CODE>initSALES2.ora</CODE> file for the second instance after embedding the Oracle9<EM CLASS="Italic">i</EM> Real Application Clusters Guard parameter files within an existing parameter file. Make sure that you only have single entries for each initialization parameter. Because they are included in the embedded parameter files, the THREAD and CLUSTER_DATABASE parameters have been removed.
</P>
   
<PRE CLASS="CE1">
<A NAME="8378"></A>ifile=/u01/oracle/admin/SALES/pfile/initSALES.ora
<A NAME="8379"></A>ifile=/u01/oracle/admin/SALES/pfile/init_SALES_nodeB.ora
<A NAME="8380"></A>ifile=/u01/oracle/admin/SALES/pfile/SALES_config.pfs
<A NAME="8381"></A>ifile=/u01/oracle/admin/SALES/pfile/SALES_config_nodeB.ded.pfs 
<A NAME="8382"></A>rollback_segments=(rbs2_1, rbs2_2)
<A NAME="8383"></A>
</PRE>
   
<A NAME="8387"></A>
<P CLASS="BP1">
For more information about these configuration files, refer to <A HREF="append_b.htm#943366">Appendix&nbsp;B</a>.
</P>


<LI CLASS="LN1" TYPE="1" VALUE="4"><A NAME="8390"></A>Run the <CODE>catpfs.sql</CODE> script to create the required Oracle9<EM CLASS="Italic">i</EM> Real Application Clusters Guard objects in the database. 
<P>
 

<A NAME="9719"></A>
<P CLASS="BP1">
To run this script, you must have SYSDBA privileges. Run the script as follows:
</P>

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

<LI CLASS="LA2" TYPE="a" VALUE="1"><A NAME="8392"></A>Make sure that all user tables are available.
<P>

<LI CLASS="LA2" TYPE="a"><A NAME="9009"></A>Change to the <CODE>$ORACLE_HOME/pfs/admin</CODE> directory:
<P>
  
<PRE CLASS="CE2">
<A NAME="8394"></A>$ cd $ORACLE_HOME/pfs/admin
<A NAME="8395"></A>
</PRE>
  
<LI CLASS="LA2" TYPE="a"><A NAME="8396"></A>Use SQL*Plus to connect to the database as the SYS user and run the <CODE>catpfs.sql</CODE> script, where<EM CLASS="Italic"> sys_password</EM> is the password(for example, <CODE>CHANGE_ON_INSTALL</CODE>) :
<P>
  
<PRE CLASS="CE2">
<A NAME="8397"></A>$ sqlplus 'SYS/<EM><CODE>sys_password</CODE></EM> AS SYSDBA'
<A NAME="8398"></A>SQL&gt; @catpfs.sql
<A NAME="8399"></A>
</PRE>
  
<A NAME="8947"></A>
<P CLASS="BP2">
The <CODE>catpfs.sql</CODE> script creates the following:
</P>
 

<UL CLASS="LA3">

<LI CLASS="LA3" TYPE="SQUARE"><A NAME="8948"></A>Oracle9<EM CLASS="Italic">i</EM> Real Application Clusters Guard user
<P>

<LI CLASS="LA3" TYPE="SQUARE"><A NAME="8949"></A>CUSTOMER_QUERY package for Oracle Heartbeat Monitor
<P>

<LI CLASS="LA3" TYPE="SQUARE"><A NAME="8950"></A>ORAPING_CONFIG and ORAPING_HEARTBEAT tables for Oracle Heartbeat Monitor
<P>

<LI CLASS="LA3" TYPE="SQUARE"><A NAME="8951"></A>PFS$ORAPING_CONFIG and PFS$ORAPING_HEARTBEAT views for Oracle Heartbeat Monitor
<P>

<LI CLASS="LA3" TYPE="SQUARE"><A NAME="8956"></A>PFS_UP_<EM><CODE>INSTANCE_NAME</CODE></EM> tables for the Oracle instance monitor
<P>
</UL>

<A NAME="8400"></A>
<P CLASS="BP2">
The following example shows output from the <CODE>catpfs.sql</CODE> script:
</P>
  
<PRE CLASS="CE2">
<A NAME="8401"></A>Enter the PFS software owner [Default: OPS$ORACLE]:ops$oracle
<A NAME="8402"></A>
<A NAME="8403"></A>Dropping ops$oracle..
<A NAME="8404"></A>DROP USER ops$oracle CASCADE
<A NAME="8405"></A>          *
<A NAME="8406"></A>ERROR at line 1:
<A NAME="8407"></A>ORA-01918: user 'OPS$ORACLE' does not exist
<A NAME="8408"></A>
<A NAME="8409"></A>Creating ops$oracle..
<A NAME="8410"></A>User created.
<A NAME="8411"></A>
<A NAME="8412"></A>Grant succeeded.
<A NAME="8413"></A>
<A NAME="8414"></A>Below are the list of online tablespaces in this database.
<A NAME="8415"></A>Decide which tablespace you wish to create the PFS tables and
<A NAME="8416"></A>indexes.  It is NOT recommended to use the system tablespace
<A NAME="8417"></A>for storing PFS objects.
<A NAME="8418"></A>
<A NAME="8419"></A>TABLESPACE_NAME
<A NAME="8420"></A>------------------------------
<A NAME="8421"></A>INDX
<A NAME="8422"></A>TEMP
<A NAME="8423"></A>TOOLS
<A NAME="8424"></A>USERS
<A NAME="8425"></A>RBS
<A NAME="8426"></A>
<A NAME="8427"></A>Specify ops$oracle user's default tablespace:users
<A NAME="8428"></A>
<A NAME="8429"></A>User altered.
<A NAME="8430"></A>
<A NAME="8431"></A>Specify ops$oracle user's temporary tablespace:temp
<A NAME="8432"></A>
<A NAME="8433"></A>User altered.
<A NAME="8434"></A>
<A NAME="8435"></A>Creating Customer Query Package...
<A NAME="8436"></A>
<A NAME="8437"></A>Specify owner of the customer query table:scott
<A NAME="8438"></A>
<A NAME="8439"></A>Specify customer query table:emp
<A NAME="8440"></A>
<A NAME="8441"></A>Connected.
<A NAME="8442"></A>
<A NAME="8443"></A>Grant succeeded.
<A NAME="8444"></A>
<A NAME="8445"></A>Connected.
<A NAME="8446"></A>
<A NAME="8447"></A>Creating synonym for the customer query table...
<A NAME="8448"></A>Specify synonym for customer query table:emp
<A NAME="8449"></A>DROP SYNONYM emp
<A NAME="8450"></A>             *
<A NAME="8451"></A>ERROR at line 1:
<A NAME="8452"></A>ORA-01434: private synonym to be dropped does not exist
<A NAME="8453"></A>
<A NAME="8454"></A>Synonym created.
<A NAME="8455"></A>
<A NAME="8456"></A>Creating CUSTOMER_QUERY package
<A NAME="8457"></A>
<A NAME="8458"></A>Package created.
<A NAME="8459"></A>
<A NAME="8460"></A>Package body created.
<A NAME="8461"></A>
<A NAME="8462"></A>Creating tables and views for Oracle heartbeat monitor.
<A NAME="8463"></A>DROP PUBLIC SYNONYM pfs$oraping_config
<A NAME="8464"></A>                    *
<A NAME="8465"></A>ERROR at line 1:
<A NAME="8466"></A>ORA-01432: public synonym to be dropped does not exist
<A NAME="8467"></A>
<A NAME="8468"></A>DROP PUBLIC SYNONYM pfs$oraping_heartbeat
<A NAME="8469"></A>                    *
<A NAME="8470"></A>ERROR at line 1:
<A NAME="8471"></A>ORA-01432: public synonym to be dropped does not exist
<A NAME="8472"></A>
<A NAME="8473"></A>DROP PUBLIC SYNONYM oraping_heartbeat
<A NAME="8474"></A>                    *
<A NAME="8475"></A>ERROR at line 1:
<A NAME="8476"></A>ORA-01432: public synonym to be dropped does not exist
<A NAME="8477"></A>
<A NAME="8478"></A>DROP VIEW pfs$oraping_config
<A NAME="8479"></A>*
<A NAME="8480"></A>ERROR at line 1:
<A NAME="8481"></A>ORA-00942: table or view does not exist
<A NAME="8482"></A>
<A NAME="8483"></A>DROP VIEW pfs$oraping_heartbeat
<A NAME="8484"></A>*
<A NAME="8485"></A>ERROR at line 1:
<A NAME="8486"></A>ORA-00942: table or view does not exist
<A NAME="8487"></A>
<A NAME="8488"></A>DROP TABLE oraping_config
<A NAME="8489"></A>           *
<A NAME="8490"></A>ERROR at line 1:
<A NAME="8491"></A>ORA-00942: table or view does not exist
<A NAME="8492"></A>
<A NAME="8493"></A>DROP TABLE oraping_heartbeat
<A NAME="8494"></A>           *
<A NAME="8495"></A>ERROR at line 1:
<A NAME="8496"></A>ORA-00942: table or view does not exist
<A NAME="8497"></A>
<A NAME="8498"></A>Table created.
<A NAME="8499"></A>1 row created.
<A NAME="8500"></A>
<A NAME="8501"></A>Commit complete.
<A NAME="8502"></A>
<A NAME="8503"></A>Table created.
<A NAME="8504"></A>
<A NAME="8505"></A>Table altered.
<A NAME="8506"></A>1 row created.
<A NAME="8507"></A>Commit complete.
<A NAME="8508"></A>View created.
<A NAME="8509"></A>View created.
<A NAME="8510"></A>Synonym created.
<A NAME="8511"></A>Synonym created.
<A NAME="8512"></A>Synonym created.
<A NAME="8513"></A>View created.
<A NAME="8514"></A>View created.
<A NAME="8515"></A>Creating tables and views for Oracle instance monitor.
<A NAME="8516"></A>
<A NAME="8517"></A>Specify instance_name for instance on PFS_HOSTA: prod1
<A NAME="8518"></A>DROP TABLE pfs_up_prod1
<A NAME="8519"></A>           *
<A NAME="8520"></A>ERROR at line 1:
<A NAME="8521"></A>ORA-00942: table or view does not exist
<A NAME="8522"></A>
<A NAME="8523"></A>Table created.
<A NAME="8524"></A>1 row created.
<A NAME="8525"></A>
<A NAME="8526"></A>Specify instance_name for instance on PFS_HOSTB: prod2
<A NAME="8527"></A>DROP TABLE pfs_up_prod2
<A NAME="8528"></A>           *
<A NAME="8529"></A>ERROR at line 1:
<A NAME="8530"></A>ORA-00942: table or view does not exist
<A NAME="8531"></A>
<A NAME="8532"></A>Table created.
<A NAME="8533"></A>1 row created.
<A NAME="8534"></A>
<A NAME="8535"></A>NOTE:
<A NAME="8536"></A>catpfs complete. Please check catpfs.log for any errors.
<A NAME="8537"></A>
</PRE>
   
</OL>


<LI CLASS="LN1" TYPE="1" VALUE="5"><A NAME="8538"></A>To ensure that the Oracle9<EM CLASS="Italic">i</EM> Real Application Clusters database is functioning properly, shut down and start up all Oracle instances manually. 
<P>
 

<A NAME="9066"></A>
<P CLASS="BP1">
For example, enter the following commands where <EM><CODE>INIT.ORA_parameter_file</CODE></EM> is the name of the initialization file as defined by the PFILE variable in the <CODE>PFS_</CODE><EM CLASS="Italic">ORACLE_SERVICE</EM><CODE>_User.def</CODE> definition file.
</P>
   
<PRE CLASS="CE1">
<A NAME="9070"></A>$ sqlplus "/ as sysdba"
<A NAME="9071"></A>SQL&gt; STARTUP pfile=<EM CLASS="Italic">INIT.ORA_parameter_file
</EM><A NAME="9072"></A>
</PRE>
   
<A NAME="9073"></A>
<P CLASS="BP1">
The definition file is located in the  <CODE>$ORACLE_HOME/pfs/</CODE><EM CLASS="Italic">DB_NAME</EM><CODE>/include</CODE> directory for non-OFA compliant installations and in the <CODE>$ORACLE_BASE/admin/</CODE><EM CLASS="Italic">DB_NAME</EM><CODE>/pfs/include</CODE> directory for OFA compliant installations.
</P>
</OL>

<A NAME="8545"></A>
<!--TOC=h1-"8545"-->
<H2 CLASS="H1"><FONT FACE="Arial, Helvetica, sans-serif" COLOR="#330099"> Post-Installation Tasks for the root User</FONT></H2>


<!--/TOC=h1-->
<A NAME="8546"></A>
<P CLASS="BP">
Perform the following steps as the <CODE>root</CODE> user:
</P>
   
<A NAME="8554">
<DIV ALIGN="CENTER">
<P>
<TABLE CLASS="Note" BORDER="0" WIDTH="80%" CELLPADDING="0" CELLSPACING="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note">
<TR CLASS="Note"><TD CLASS="Note">
<HR>
<A NAME="8549"></A><FONT FACE="Arial, Helvetica, sans-serif"><STRONG CLASS="NH">Note:</STRONG></FONT>

<A NAME="8552"></A>
<P CLASS="NB">
Perform the tasks described in <A HREF="3postins.htm#8225">"Post-Installation Tasks for the oracle User"</a> before starting the tasks described in this section.
<HR>
</TD>
</TR>


</TABLE>


</DIV>
</A>
   
<OL CLASS="LN1" TYPE="1">

<LI CLASS="LN1" TYPE="1" VALUE="1"><A NAME="8555"></A>To ensure that the <CODE>oracle</CODE> user's environment is available to the <CODE>root</CODE> user, log in as the <CODE>oracle</CODE> user and enter the following command:
<P>
    
<PRE CLASS="CE1">
<A NAME="8556"></A>$ su root
<A NAME="8725"></A>
</PRE>
    

<LI CLASS="LN1" TYPE="1" VALUE="2"><A NAME="8727"></A>Set the ORACLE_SERVICE and DB_NAME environment variables to the appropriate values. 
<P>

<LI CLASS="LN1" TYPE="1" VALUE="3"><A NAME="8560"></A>If you have created a database manually, ensure that the system configuration is reflected in the <CODE>oratab</CODE> file. The <CODE>oratab</CODE> file is located in the <CODE>/var/opt/oracle</CODE> directory for Solaris and in the <CODE>/etc</CODE> directory for AIX, HP, and Tru64.
<P>
 

<A NAME="8561"></A>
<P CLASS="BP1">
Add an entry for each server instance on the system using the following format:
</P>
   
<PRE CLASS="CE1">
<A NAME="8562"></A>DB_NAME:ORACLE_HOME:N
<A NAME="8563"></A>
</PRE>
   
<A NAME="8564"></A>
<P CLASS="BP1">
In this example <CODE>N</CODE> indicates that the database should not be started at reboot time. Always enter the <CODE>N</CODE> option so that Oracle9<EM CLASS="Italic">i</EM> Real Application Clusters Guard can control startup and shutdown of the database.
</P>


<LI CLASS="LN1" TYPE="1" VALUE="4"><A NAME="8571"></A>Change to the <CODE>$ORACLE_HOME/pfs/setup</CODE> directory and register the Oracle9<EM CLASS="Italic">i</EM> Real Application Clusters Guard Packs with the cluster by running the <CODE>createpacks</CODE> script
<P>
 

<A NAME="8969"></A>
<P CLASS="BP1">
Ensure that the DB_NAME, ORACLE_SERVICE, ORACLE_HOME, and if necessary, the ORACLE_BASE environment variables are set correctly before running the script.
</P>