| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Directory Server Enterprise Edition Troubleshooting Guide 11g Release 1 (11.1.1.5.0) |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Directory Server Enterprise Edition Troubleshooting Guide 11g Release 1 (11.1.1.5.0) |
1. Overview of Troubleshooting Directory Server Enterprise Edition
2. Troubleshooting Installation and Migration Problems
3. Troubleshooting Replication
4. Troubleshooting Directory Proxy Server
5. Troubleshooting Directory Server Problems
Getting the Core and Shared Libraries
Examining a Core File on Solaris
Troubleshooting an Unresponsive Process
Symptoms of an Unresponsive Process
Collecting Data About an Unresponsive Process
Analyzing Data About a Unresponsive Process: an Example
Troubleshooting Drops in Performance
Possible Causes of a Drop in Performance
Collecting Data About a Drop in Performance
Collecting Disk, CPU, and Memory Statistics
Collecting Consecutive Process Stacks on Solaris
Analyzing Data Collected About a Performance Problem
Analyzing the Access Log Using the logconv Command
Identifying Capacity Limitations: an Exercise
Troubleshooting an Active Hang
Possible Causes of an Active Hang
Collecting and Analyzing Data About an Active Hang
Troubleshooting a Passive Hang
Possible Causes of a Passive Hang
Collecting and Analyzing Data About a Passive Hang
Possible Causes of a Memory Leak
Collecting Data About a Memory Leak
Analyzing Memory Leaks Using the libumem Library
6. Troubleshooting Data Management Problems
7. Troubleshooting Identity Synchronization for Windows
8. Troubleshooting DSCC Problems
9. Directory Server Error Log Message Reference
This section describes how to troubleshoot an inaccessible database
The Directory Server database may be inaccessible for one of the following reasons:
Database corruption
index corruption
Shared region file corruption
Missing change log
Corrupted change log
Database offline, for example it is being reimported
Missing transaction log
# instance-name/logs/errors*
|