While Running 'db2ldif -s' to Export the Suffix, Error is Generated in Directory Server 5.2: "DEBUG - conn=-1 op=-1 msgId=-1 - ERROR 2: There is no backend instance to export from".
(Doc ID 1368968.1)
Last updated on AUGUST 03, 2013
Applies to:Oracle Directory Server Enterprise Edition - Version 5.2 to 5.2 SP6 [Release 5.0]
Information in this document applies to any platform.
***Checked for relevance on 03-Aug-2013***
When running db2ldif -s to export the suffix, error is output:
The backend database suffix is defined in the dse.ldif and in the console. In the dse.ldif it is defined under cn=mapping tree,cn=config in this format: cn="<suffix>",cn=mapping tree,cn=config
When the -s switch is specified in db2ldif and db2ldif.pl, the export will fail as follows:
- In 5.2 patch 6 when double quotes encapsulate the suffix in the dse.ldif and in the db2ldif command.
- In 5.2 patch 4 when the value of -s is not a backend database suffix. For example: ou=people,dc=example,dc=com
NOTE: The backend database suffix can be exported through the 5.2 console.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!