Creating oracle wallets

compared with
Current by Karen Heidenreich
on Mar 30, 2009 14:13.


 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 1 changes. View first change.

 We need to use the version(s) of oracle in
  
 * 32 bit - /afs/slac.stanford.edu/package/oracle/f/10.2.0/i386_linux/10.2.0
 * 64 bit - /afs/slac.stanford.edu/package/oracle/e/LINUX64/10.2.0
  
 We have set up an area for storing oracle admin files and wallets in:
  
 /u/gl/glast/oracle
  
 (Currently a link to NFS space, but perhaps will change to AFS space to take advantage of AFS based access restrictions).
  
 Three subdirectories:
  
 * wallet -- For oracle wallets
 * admin -- admin files like tnsnames.ora sqlnet.ora
 * bin -- utilities, such as setup.sh and setup.csh
  
 To get oracle to use our own admin directory we need to:
  
 {noformat}
 setenv TNS_ADMIN ~glast/oracle/admin/
 {noformat}
  
 This is done but the setup scripts mentioned above, so in practice you need:
  
 {noformat}
  source /u/gl/glast/oracle/admin/setup.(c)sh
  source /u/gl/glast/oracle/bin/setup.(c)sh
 {noformat}
  
 The commands for manipulating wallets are:
  
 {noformat}
 mkstore -wrl <wallet_location> -create
 mkstore -wrl <wallet_location> -createCredential <db_connect_string> <username> <password>
 mkstore -wrl <wallet_location> -modifyCredential <db_connect_string> <username> <password>
 {noformat}
  
 (see http://download.oracle.com/docs/cd/B19306_01/network.102/b14266/cnctslsh.htm)
  
 See also: [Secure Oracle Paswords for GLAST]