Last updated on MARCH 08, 2017
Applies to:Oracle Internet Directory - Version 9.0.4 and later
Information in this document applies to any platform.
If using standard database backup and restore procedures, such as those performed by the Oracle Application Server Backup and Recovery Tool, must perform a full database backup after any of the following administrative tasks:
a. Using the bulkload bulk management tool
b. Using the catalog bulk management tool
c. Installing Oracle Internet Directory
d. Upgrading Oracle Internet Directory to a major release version or patchset
e. Installing an LDAP application against Oracle Internet Directory, such as Oracle Collaboration Suite, that modifies the cn=catalogs entry to add orclindexedattribute
If a full backup is not performed after using the bulkload bulk management tool (item a above), unrecoverable errors may arise when performing a restore.
If a full backup is not performed after any of the other four items above (items b-e), recoverable errors may arise when performing a restore.
For illustration, described below are also a couple of related scenarios:
Running OID bulk tools, i.e., bulkload.sh, or catalog.sh against an OID repository database that is using Dataguard Managed Standby results in data corruption after a switch to the standby instance.
An OID replica node's repository database was recently recovered.
Operations are now failing. The replication log oidrepld00.log shows changes moving to HIQ with message:
Conflict reason: Attempted to modify a non-existent entry
When trying to remove the entries from oidadmin (to clear them from both nodes since it was not possible to stop the servers due to production requirements), receives error:
Cannot delete user : [LDAP: error code 53 - Unwilling To Perform]
Same error if trying from command line with ldapdelete:
ldapdelete -p <OID port> -h <OID host> -D "cn=orcladmin" -w <pwd> "<user/entry DN>"
ldap_delete_s: DSA is unwilling to perform
Also unable to add new users:
User Creation Error: [LDAP: error code 1 - Operations Error]
The oid log shows:
2006/07/04:15:15:47 * ServerWorker:3 * ConnID:7274 * OpId:357 * OpName:add
[gsldaa_AddEntry]: ORA-4294967293 while adding Entry <entry DN, ie cn=testusers,cn=users,dc=mycompany,dc=com>
2006/07/04:15:15:47 * ServerWorker:3 * INFO * ServerWorker * Operation
<Note 287569.1> indicates space problems with the repository database, however, all of the tablespaces are already set to
autoextend, and confirmed that can create objects in the ODS tablespaces OLTS_*.
The ODS user also already has unlimited quotas.
After setting "Enable All Debugging" in OID, the following is reported on the OID pid log:
13:38:45 * INFO * gslsbnrNormalizeString()
Normalized value: <0f389999856d5864e0440003ba4ce25c>
13:38:45 * [gslddd_DelCatEntry]: ORA-1578: ORA-01578: ORACLE data block corrupted (file # 22, block # 3878)
ORA-01110: data file 22: '/oradata/repodb/gcats1_oid.dbf'
ORA-26040: Data block was loaded using the NOLOGGING option
Restore from a backup performed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms