Oracle® Internet Directory Administrator's Guide 10g (9.0.4) Part Number B12118-01 |
|
Addition of a Directory Node by Using the Database Copy Procedure, 6 of 7
Complete the following steps on the new node.
oratab
file appropriately for the new instance, at all database nodes. See the sample file for syntax.
Begin oratab NLDAP:/private1/oracle/app/oracle/product/8.1.6:N *:/private1/oracle/app/oracle/product/8.1.6:N End oratab
root.sh
) activities for the database as well as the Directory server.
To run shell script tools on the Windows operating system, you need one of the following UNIX emulation utilities:
Note:
http://sources.redhat.com
http://www.datafocus.com/
If you have already performed Oracle database and Directory installation on the new node, then proceed to Step 5.
initNLDAP.ora
and configNLDAP.ora
from the sponsor node (rst-sun) to the new node under the UNIX directory $ORACLE_BASE/ADMIN/NLDAP/PFILE
. Files can be copied to the new machine using tools such as FTP. Make sure the transfer mode is ASCII.
$ORACLE_HOME/DBS TO $ORACLE_BASE/ADMIN/NLDAP/PFILE
.
$ ln -s $ORACLE_BASE/admin/NLDAP/pfile/initNLDAP.ora $ORACLE_HOME/dbs/initNLDAP.ora $ ln -s $ORACLE_BASE/admin/NLDAP/pfile/configNLDAP.ora $ORACLE_HOME/dbs/configNLDAP.ora
ftp> open rst-sun Connected to rst-sun.us.oracle.com. 220 rst-sun FTP server (UNIX(r) System V Release 4.0) ready. Name (rst-sun:oracle): 331 Password required for oracle. Password: 230 User oracle logged in. ftp> cd /private1/oracle/oradata/LDAP 250 CWD command successful. ftp> binary 200 Type set to I. ftp> mget oradb.tar.Z
If the data files are huge (several gigabytes or terabytes) and the network bandwidth is low, then it may be a better idea to physically ship the compressed file on any media, such as tape or disk, from the sponsor to the new node.
newdb.sql
created under Step 6 of the sponsor node setup to the background user dump destination directory. You must transfer the file newdb.sql only in ASCII mode. For example:
$ cd /private1/oracle/app/oracle/admin/NLDAP/udump (that is::$ORACLE_BASE/admin/SID/udump) $ ftp ftp> open rst-sun ftp> cd /private1/oracle/app/oracle/admin/LDAP/udump ftp> mget newdb.sql
$ sqlplus /nolog SQL> connect /as sysdba SQL> startup nomount SQL> @newdb.sql SQL> shutdown normal SQL> startup (uncomment the parameter job_queue_process prior to startup) SQL>exit $ lsnrctl start
$ telnet rst-sun $ sqlplus /nolog SQL> connect /as sysdba SQL> startup SQL> exit $ lsnrctl start (By default listener name is LISTENER) $ exit
If the new node is created by using backup database copy of the MDS, then the master definition catalog needs to be dropped and the underlying Oracle9i Advanced Replication catalogs must be created. To drop the definition of the MDS from the Oracle9i Advanced Replication catalog on the new node and add the Oracle9i Advanced Replication catalogs, execute the following scripts.
$ cd $ORACLE_HOME/ldap/admin $ sqlplus repadmin/repadmin SQL> @ldapdropmds.sql SQL> @ldapcreindex.sql
Specify the global name of the new node when prompted.
$ ldaprepl.sh -addnode
Note: To run shell script tools on the Windows operating system, you need one of the following UNIX emulation utilities:
|
Sample LDIF file:
dn: orclagreementid=000001, cn=orclreplagreements changetype: modify add: orcldirreplgroupdsas orcldirreplgroupdsas: dsm-sun
|
![]() Copyright © 1999, 2003 Oracle Corporation. All Rights Reserved. |
|