|
|
Application Server
|
|
|
|
Oracle Internet Directory
Replication (OID Replication)
Note on the following important terms from Oracle:
- Replica: The copy of a naming context contained within a
server is called a replica.
- Suppliers: The OID servers in the DRG (Directory
Replication Group) that hold updatable replicas or naming contexts
are called suppliers.
- Consumers: The OID servers in the DRG to which the updates
made on suppliers are propagated are called consumers.
- Directory Replication Group: A set of OID servers that
participate in the replication of a given naming context is called a
Directory Replication Group (DRG).
- Replication agreement: A special directory entry that
represents the replication relationship among the OID servers in a
DRG.
- Change log purging: After the OID Replication server
applies the changes to the consumer, the change entries are purged.
Purging of the change log entries can be done by two different
methods such as Change number based or Time based.
Setting Oracle Internet Directory Replication
To perform this configuration, you should have two different
machines. Let us named them: The MASTER and REMOTE
machines
Install complete OracleAS Infrastructure on the MASTER server with
the following setting:
(For example)
ORACLE_HOME=/u01/oracle/inframaster
ORACLE_SID=inframaster
Oracle Database Global Name=inframaster.yourhost.com
Install OracleAS Infrastructure without any of the default component
option on the REMOTE server with the following setting:
Notice that since you have not selected any component to install,
the installer will prompt you to register this installation against
an OID server. Enter the OID server host name and port number of the
MASTER server.
(For example)
ORACLE_HOME=/u01/oracle/infraremote
ORACLE_SID=infraremote
Oracle Database Global Name=infraremote.yourhost.com
Stop the OID server LDAP instance on the MASTER server:
# $ORACLE_HOME/bin/oidctl connect=inframaster.yourhost.com
instance=1 server=oidldapd flags=�-p 3060� stop
On the REMOTE server, create a wallet
# $ORACLE_HOME/bin/oidpasswd connect=infraremote.yourhost.com
create_wallet=true
Notice that you should use the password of ODS schema in the
metadata repository. The default password of the ODS schema is ods.
You can also use the orcladmin�s password.
On the MASTER server, start the OIDMON and OIDLDAP processes
# $ORACLE_HOME/bin/oidmon connect=infraremote.yourhost.com start
# $ORACLE_HOME/bin/oidctl connect=inframaster.yourhost.com
instance=1 server=oidldapd flags=�-p 3060� start
Stop the OIDMON process on the REMOTE server
# $ORACLE_HOME/bin/oidmon connect=infraremote.yourhost.com stop
Modify the tnsnames.ora file and include a net service name entry
for the REMOTE repository database in the MASTER server and the
MASTER repository database in the REMOTE server.
Assuming the service names are master and remote, try to tnsping
them.
For example:
Go to the REMOTE server and execute the following command: # tnsping
master
Go to the MASTER server and execute the following command: # tnsping
remote
Set up the ASR-based replication.
Go to the MASTER server, execute the following command:
# $ORACLE_HOME/bin/remtool �asrsetup �v
Answer to all questions. After the setup is completed, remtool will
display you the confirmation and the status of the replication
setup.
Start the OID LDAP server instances on the MASTER and REMOTE
servers.
On MASTER:
# $ORACLE_HOME/bin/oidctl connect=inframaster.yourhost.com
instance=1 server=oidldapd flags=�-p 3060� start
On REMOTE
# $ORACLE_HOME/bin/oidmon connect=infraremote.yourhost.com start
Start the OID Replication server instance on the MASTER and REMOTE
servers.
On MASTER:
# $ORACLE_HOME/bin/oidctl connect=inframaster.yourhost.com
instance=1 server=oidrepld flags=�-p 3060� start
On REMOTE:
# $ORACLE_HOME/bin/oidctl connect=infraremote.yourhost.com
instance=1 server=oidldapd flags=�-p 3060� start
To verify whether the replication is working, start ODM form both
the MASTER and REMOTE servers and wait for the entries to be
replicated from them. |
|
