l         If you forgot to set the DISPLAY environment variable (e.g. export DISPLAY=oracleserver:0.0) , or if you forgot to give the remote console - your Oracle Server - authority to display X information on your desktop PC (e.g. xhost +oracleserver ), you will get the following error:
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
In this case, I always had to kill runInstaller which was still running in the background! If you don''''t do this, runInstaller will not completely come up any more and you will not see any error messages that runInstaller is having problems.
You might also want to clean up /tmp/OraInstall (9.0.1):
rm -rf /tmp/OraInstall

l         When runInstaller starts to configure the tools ("Configuration Tools"), the "Oracle Net Configuration Assistant" will sometimes hang. Simply stop the Assistant and restart it, or continue the installation. When the rest of the installation is finished, do a "Retry" for "Oracle Net Configuration Assistant". This always worked for me.

l         When the system stops to respond during the Oracle installation, in particular during the database creation, then it is probably because you don''''t have enough RAM or enough swap space. I noticed that the whole system will not respond (or "hang") for several minutes when I did not have enough swap space. If this happens, simply wait until the system starts to respond again.

l         The Oracle installation also runs make etc. In a production environment you might not have compilers and other development packages installed. Therefore make sure you have temporarily the following packages installed: gcc, cpp, egcs, egcs-c++, glibc-devel, kernel-headers. (I''''m not sure though if all of these packages have to be on the system during the Oracle installation.)

l         If for any reason the Oracle installation didn''''t finish successfully, you might want to clean up the following files and directories before you restart over again:
rm -rf /etc/oraInst.loc /etc/oratab /tmp/OraInstall
/tmp/<OtherOracleOwnedFiles>
$ORACLE_BASE/*

15，Startup and Shutdown of Oracle 9i Database

       sqlplus:

svrmgrl is not supported any more. You can now do everything with sqlplus.

E.g., to startup the database, execute the following commands:
       dba$ sqlplus /nolog
       SQL> connect / as sysdba
       SQL> startup

The slash connects you to the schema owned by SYS.  So in this example we are saying that we want to connect to the schema owned by SYS with the privilege SYSDBA. SYSDBA gives you the following privileges:
 sysoper privileges WITH ADMIN OPTION
 create database
 recover database until

$ORACLE_HOME/bin/dbstart and $ORACLE_HOME/bin/dbshut :

You can also use $ORACLE_HOME/bin/dbstart to startup the database, and $ORACLE_HOME/bin/dbshut to shutdown the database. You can place $ORACLE_HOME/bin/dbstart into the /etc/rc.d/rc.local boot script to automatically bring up the database at system boot time. To get $ORACLE_HOME/bin/dbstart and $ORACLE_HOME/bin/dbshut working, you need to change the third field for your Oracle SID in /etc/oratab from "N" to "Y".

E.g. for the Oracle SID "test" I changed the line in /etc/oratab from
test:/opt/oracle/product/9.2.0:N
to read
test:/opt/oracle/product/9.2.0:Y

For 9.2.0, I also had to copy the init file for my SID "test" from /opt/oracle/admin/test/pfile to $ORACLE_HOME/dbs to get dbstart and dbshut working:
cp /opt/oracle/admin/test/pfile/inittest.ora.642002224936 $ORACLE_HOME/dbs/inittest.ora
But first check if your init file already exists in $ORACLE_HOME/dbs.

上一页  [1] [2] [3]