-
This question sounds stupid, but the same it's got me thinking.
In upgrade, do you have to hit ENTER at the shell after
setting the environmental variable, SID,etc. Or all need to be done in
one line? I other words, should it look like the EXAMPLE 1 or EXAMPLE 2?
EXAMPLE ONE
------------
ORACLE_HOME=/oracle/zed/news/product/8.1.6;export ORACLE_HOME
ORACLE_SID=REPORTS;export ORACLE_SID
PATH=$PATH:$ORACLE_HOME/bin;export PATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib;export LD_LIBRARY_PATH
CLASSPATH=$CLASSPATH:$ORACLE_HOME/JRE:$ORACLE_HOME/jlib
export CLASSPATH
EXAMPLE TWO
-------------
nationalnews oracle REPORTS /home/oracle
$ORACLE_HOME=;;export ORACLE_HOME
nationalnews oracle REPORTS /home/oracle
$ORACLE_SID=REPORTS;export ORACLE_SID
nationalnews oracle REPORTS /home/oracle
$PATH=$PATH:$ORACLE_HOME/bin;export PATH
nationalnews oracle REPORTS /home/oracle
$LD_LIBRARY_PATH=$ORACLE_HOME/lib;
nationalnews oracle REPORTS /home/oracle
$CLASSPATH=$CLASSPATH:$ORACLE_HOME/JRE:$ORACLE_HOME/jlib
export CLASSPATH
nationalnews oracle REPORTS /home/oracle
$
P.S.
nationalnews is the machine name.
REPORTS is the database name
O/S is SUN
-
Not sure of you're exact question, but hope the following helps.
Unix shells are line (carriage-return, line-feed) oriented. To put multiple commands on one line, separate them with semicolons ';' (as in Example 1).
Entering:
command 1; command 2
is exactly the same as entering:
command 1
command 2
To extend a command across more than one line, use a backslash '\'.
Example 1 looks fine (for Bourne or Korn).
Example 2 looks odd in that it appears to assign a value to a value. For example:
$ORACLE_SID=REPORTS
should read
ORACLE_SID=REPORTS
In general, the syntax is "VARIABLE=value; export VARIABLE" (assuming you want it be be global).
Tim
