Collecting Generic Directory Proxy Server Data

No matter the type of problem you are encountering, there is a minimum set of data that needs to be collected and, if necessary, provided to Oracle Support.

Collecting Version Information for Directory Proxy Server

The following sections describe how to collect configuration information on current and previous versions of Directory Proxy Server.

You can collect the Directory Proxy Server version information using any of the following ways:

• Use the $ dpadm -V command to get the detailed information about the Directory Proxy Server version. It displays the output similar to the following output:

  $ dpadm -V [dpadm] dpadm : 11.1.1.3.0 B2010.**** ZIP Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. [DPS] Sun Microsystems, Inc. Sun-Directory-Proxy-Server/11.1.1.3.0 B2010.****

• The version information is available in the instance-dir/logs/error file. For example, the error log displays the version information as follows:

  [30/Apr/2010:14:21:52 -0500] - STARTUP - INFO - \ Sun-Directory-Proxy-Server/11.1.1.3.0 B2010.**** started \ on host server1 in directory /local/dps

Running the dpadm Command in Verbose Mode

Running the dpadm command in verbose mode will provide information to help troubleshoot problems that occur during instance creation or deletion, data backup, and so on. Run the dpadm is verbose mode as follows:

# dpadm -v

Collecting Directory Proxy Server Configuration Information

Collect the Directory Proxy Server configuration information. This information is available in the instance-dir/logs/errors file. For example, the error log displays the configuration information as follows:

user@server1 local]$ more dps.3333/logs/errors
[31/Mar/2009:18:45:33 +0530] - STARTUP    - INFO  - \
Global log level INFO (from config)
[31/Mar/2009:18:45:33 +0530] - STARTUP    - INFO  - \
Logging Service configured
[31/Mar/2009:18:45:33 +0530] - STARTUP    - INFO  - \
Java Version: 1.5.0_12 (Java Home: /usr/jdk/instances/jdk1.5.0/jre)
[31/Mar/2009:18:45:33 +0530] - STARTUP    - INFO  - \
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
[31/Mar/2009:18:45:33 +0530] - STARTUP    - INFO  - \
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_12-b04, mixed mode)
[31/Mar/2009:18:45:33 +0530] - STARTUP    - INFO  - \
Java Heap Space: Total Memory (-Xms) = 241MB, Max Memory (-Xmx) = 241MB
[31/Mar/2009:18:45:33 +0530] - STARTUP    - INFO  - \
Operating System: SunOS/sparcv9 5.9
[31/Mar/2009:18:45:33 +0530] - STARTUP    - INFO  - \
SSL initialization succeeded.
[31/Mar/2009:18:45:33 +0530] - CONFIG     - WARN  - \
Attribute certMappingDataViewPolicy in entry \
cn=LDAPS Listener,cn=Client Listeners,cn=config missing. Using ALL_DATA_VIEW
[31/Mar/2009:18:45:33 +0530] - STARTUP    - INFO  - \
Creating 50 worker threads.
[31/Mar/2009:18:45:34 +0530] - BACKEND    - WARN  - \
Can't retrieve LDAP schema (LDAP error code: 32) \
No data view were found to process the search request.
[31/Mar/2009:18:45:34 +0530] - STARTUP    - INFO  - \

Collecting Directory Proxy Server Log Information

Collect the Directory Proxy Server logs. By default, the logs are stored in the following directory:

instance-path/logs

If you are providing this information to Oracle Support, you should also include the generic Directory Server data from the various Directory Servers involved. This generic data includes the Directory Server version and the Directory Server access, error, and audit logs. For more information about collecting the Directory Server generic information, see Collecting Generic Data.

Include generic information about any other backend servers you may be using, such as JDBC backends, a SQL database, or an Oracle database.