A customer asked to us why IDM created a lot of invalid procedures. See the Attachment (Ignore the owners BGIS94 and BGIST4).
For example:
| OBJECT NAME | OBJECT TYPE |
|---|
| ARCHIVEBYEVENTID | PROCEDURE |
| ARCHIVEBYID | PROCEDURE |
| ARCHIVEBYROWID | PROCEDURE |
| ARCHIVEBYTASKID | PROCEDURE |
| ARCHIVETASKPERSISTENCE | PROCEDURE |
These procedures have invalid references, to inexisting tables or Schemas.
Customer asked if it is safe to delete those objects.
ANSWER:
This may happen sometimes, with no clear reason. Usually it happens when IDM is using different databases for each datasource at its first startup.
There is a simple way to ensure that you have only valid objects, that is recreating the archive database tables and procedures:
When IDM goes through its startup procedure it checks to see if the task persistence and archive tables exist and are up-to-date. If it finds that the tables are missing it will automatically create them! This is how the tables were initially created after IDM was first installed.
Therefore, you can...
(1) Stop Identity Manager and delete all the existing archive tables and procedures,
(2) Verify that your archive datasource points to the correct DB location, and
(3) Then restart Identity Manager.
The Identity Manager startup procedure will create the necessary Archive tables and procedures.