Certain operations, like Explore/Correlate cause the following error: ERROR IM Provisioning Server - Unable to allocate Operation object.

Document ID : KB000051008
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Certain operations, like Explore/Correlate cause the following error: ERROR IM Provisioning Server - Unable to allocate Operation object. In this case, it usually follows an upgrade from 8.1SP2 to 12 or 12.5.

Solution:

This error can be caused by a few different issues. A common cause is the fact that, during the upgrade, the operations container (etadmintemp dsa) does not get loaded into the 12.5 structure. You can verify that the Operations container object exists in the Provisioning Directory by running the following ldapsearch query:

The below can be placed into a batch file and run to search for and retrieve the Operations container object. Be sure that the variables are set properly for your system, and do not include the <> brackets:

@echo off

set LDAPSEARCH_EXE="C:\Program Files\CA\Identity Manager\Provisioning
Server\bin\ldapsearch.exe"

set PROV_HOST=<HOSTNAME>
set PROV_PORT=20389
set PROV_DOMAIN=<DOMAINNAME>
set PROV_USER=<USERNAME ex:idmadmin>
set PROV_PWD=<PROVISIONING PASSWORD>

set
PROV_BIND="eTGlobalUserName=%PROV_USER%,eTGlobalUserContainerName=Global
Users,eTNamespaceName=CommonObjects,dc=%PROV_DOMAIN%,dc=eta"
set

PROV_BASE="eTOperationContainerName=Operations,eTNamespaceName=CommonObjects,dc=%PROV_DOMAIN%,dc=eta"

%LDAPSEARCH_EXE% -LLL -h %PROV_HOST% -p %PROV_PORT% -D %PROV_BIND% -w
%PROV_PWD% -b %PROV_BASE% -s base "(objectclass=*)" >
getOperationContainer.txt

If the result is:

No such object (32)
Additional information: :ETA_E_0019<RXX>, Object 'Operations' read
failed: DB Re
ad failed: No such object (ldaps://<HOSTNAME>:20391)

Then the operations object is indeed the problem. You can then run the following command to create the object:

etautil.exe -u %PROV_USER% -p %PROV_PWD% add 'eTNamespaceName=CommonObjects'
eTOperationContainer eTOperationContainerName='Operations'

Otherwise, the operations object container is not the problem. You should consult the knowledge base for similar "Unable to allocate Operation object" TECDOCS, or open an issue with CA Technologies Support.