...
Start Directory via Management Tool
This is is Shawn's preferred method.
Primary Directory
| Code Block | ||
|---|---|---|
| ||
su -
su - diradmin
odselog -a # Check if there were errors before you start
cd /var/cpmaster # You MUST be in the Critical Path Data Directory of the instance you want to start |
Start the management tool,
...
| Code Block | ||
|---|---|---|
| ||
>v pid inst action fails state name options 10394 M default 0 ok odsmdsa -d"/var/cpshadow" 10395 0 restart this 0 ok odssdsa 10396 1 restart this 0 ok odssdsa 10397 0 restart this 0 ok odscomms 10398 0 restart this 0 ok odscommsi 10399 0 default 0 ok odsshadi 10400 0 restart this 0 ok odsldap3 -ldap:389 -ldaps:0 -http:0 -https:0 -charsetv2:iso8859-1 |
Shadow Directory
Repeat the above steps except the data directory changes from cpmaster to cpshadow,
| Code Block |
|---|
su -
su - diradmin
odselog -a # Check if there were errors before you start
cd /var/cpshadow # You MUST be in the Critical Path Data Directory of the instance you want to start
odsmgmt
|
Start Directory via Command Line
Primary Directory
Log into CA1.
Start the Critical Path Directory Server as the diradmin user,
...
The primary Critical Path Directory Services is now running.
Shadow Directory
Log into RS1.
Repeat the above steps except the data directory changes from cpmaster to cpshadow,
...