The Groups container was accidentally deleted in the OID test database today and had to be re-created based on priv data in the Summit database.
\nHere are the steps we had to do to recover everything:
\n1. Recreate the Groups container.
\nExport the Groups container definition (as an LDIF command) from the OID production instance, and import it into OID test. You’ll need an LDAP browser tool to do this, like JXplorer.
\n2. Recreate all the AD groups.
\nSet the status of all the pugetsound domain groups in the privilege table to PA and run
\nprivcmd.resolve_pending_privdef on each one.
\n3. Recreate the members in the AD groups.
\nSet the status of all AD person_privilege records to PA and run privcmd.resolve_pending_privs.
\n4. Recreate the portal group container.
\nExport the portal.070109.134036.113589000 container definition (as an LDIF command) from the OID production instance, and import it into OID test. You’ll need an LDAP browser tool to do this, like JXplorer.
\n5. Recreate all the portal groups.
\nSet the status of all the portal groups in the privilege table to PA and run
\nprivcmd.resolve_pending_privdef on each one.
\n6. Recreate the members in the portal groups.
\nSet the status of all portal person_privilege records to PA and run privcmd.resolve_pending_privs.
\n7. Address any unusual configuration issues.
\nViewsFlash groups have a special setup, the administrator group is a member of the creator group, so that has to be done manually.<\/p>\n","protected":false},"excerpt":{"rendered":"
The Groups container was accidentally deleted in the OID test database today and had to be re-created based on priv data in the Summit database. Here are the steps we had to do to recover everything: 1. Recreate the Groups … Continue reading