5 Troubleshooting

This chapter provides solutions to some commonly encountered problems associated with using generic technology connectors for reconciliation and provisioning. The information in this chapter is divided into the following sections:

Common Errors Encountered During Reconciliation
Common Errors Encountered During Provisioning

Common Errors Encountered During Reconciliation

The following table provides solutions to some commonly encountered problems associated with the reconciliation process.

Note:

These errors are logged only if you are using the using the Shared Drive Transport provider and the CSV Format provider.

If any of these errors occurs, then the error message is written to the application log file.

Problem Description (Error Message)	Solution
No run time provider parameters available	Use the Modify Generic Technology Connector feature of the Administrative and User Console to check the values specified for the run-time parameters. Then, retry reconciliation.
No design time provider parameters available	Use the Modify Generic Technology Connector feature of the Administrative and User Console to check the values specified for the design parameters. Then, retry reconciliation.
Staging directory location is not defined	Use the Modify Generic Technology Connector feature of the Administrative and User Console to check the value specified for the Staging Directory (Parent Data) parameter. Then, retry reconciliation.
File encoding is not defined	Use the Modify Generic Technology Connector feature of the Administrative and User Console to check the value specified for the File Encoding (Parent Data) parameter. Then, retry reconciliation.
Unique attribute for parent which would Key in child, is not defined Note: This message has not been correctly worded. The message should read as follows: "Unique attribute for parent is not defined. This attribute would serve as the reference field in the child data file, which would link each record in the child data file with a record in the parent data file."	Use the Modify Generic Technology Connector feature of the Administrative and User Console to check the value specified for the Unique Attribute (Parent Data) parameter. Then, retry reconciliation.
Archive directory location is not defined	Use the Modify Generic Technology Connector feature of the Administrative and User Console to check the value specified for the Archiving Directory parameter. Then, retry reconciliation.
Cannot process files as not even fixed-width delimiter has been defined	Use the Modify Generic Technology Connector feature of the Administrative and User Console to check if a value has been specified for one of the following parameters: Specified Delimiter Tab Delimiter Fixed Column Width Then, retry reconciliation.
No Parent files in staging directory No files available for reading	Ensure that data files are present in the directory specified as the value of the Staging Directory (Parent Data) parameter. Then, retry reconciliation.
No child data present in staging directory No files available for reading	Ensure that data files are present in the directory specified as the value of the Staging Directory (Multivalued Data) parameter. Then, retry reconciliation.
The Staging directory cannot be accessed. Either the directory path does not exist or necessary access permissions are missing	Ensure that the directories specified as parameter values have the required permissions. Refer to the "Shared Drive Transport Provider for Reconciliation" section for information about the required permissions. Then, retry reconciliation.
Data files could not be read as its File encoding is not supported.	Use the Modify Generic Technology Connector feature of the Administrative and User Console to check the value specified for the File Encoding parameter. Then, retry reconciliation.
Not able to parse metadata	Check the metadata (contents of the second row) present in the parent and child data files. There may be a problem with the delimiter used in the files. Fix the problem, and then retry reconciliation.
Not able to parse header	Check the header (contents of the first row) of the data files. There may be a problem in the format of the header. Refer to the "Shared Drive Transport Provider for Reconciliation" section for information about the header format. Fix the problem, and then retry reconciliation.
Current Record is erratic and cannot be parsed	Check the entry that is written to the application log file. It may contain errors that cannot be parsed. Fix the problem, and then retry reconciliation.

Common Errors Encountered During Provisioning

The following table provides solutions to some commonly encountered problems associated with the provisioning process.

Note:

Most of these errors are logged only if you are using the using the Web Services Transport Provider for Provisioning and the SPML Format Provider for Provisioning.

If any of these errors occurs, then the error message is displayed on the UI and written to the application log file.

Problem Description	Solution
Response code: SPML Velocity Properties Not Read Response Description: Necessary SPML template properties could not be read.	There is a problem with the Oracle Identity Manager installation. Contact Oracle Support, and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.
Response code: SPML Template Not Read Response Description: The SPML template file was not found.	There is a problem with the Oracle Identity Manager installation. Contact Oracle Support, and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.
Response code: SPML Unknown Operation Response Description: Type of provisioning operation not in allowed set: Create, Delete, Enable, Disable, Modify, Child Table Operations.	There is a problem with the Oracle Identity Manager installation. Contact Oracle Support, and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.
Response code: SPML Provisioning Input Null Response Description: SPML provisioning input data is null.	Check if the provider parameters have been correctly specified. Check if provisioning was initiated by direct provisioning or request provisioning. Retry the procedure by using the direct provisioning option. Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning.
Response code: SPML Template Processing Error Response Description: An error in template processing for generation of SPML request occurred.	There is a problem with installation. Contact Oracle Support, and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.
Response code: SPML Provisioning Operation Name Missing Response Description: Operation name for provisioning is missing.	The generic technology connector may not have been created correctly. Try creating another connector using the same set of configurations (providers) but with fewer attributes. Try direct provisioning. Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning.
Response code: SPML Provisioning Child Name Missing Response Description: Child name is missing.	You may have been trying to perform provisioning for one particular type (for example, role or membership) of multivalued attribute when this error occurred. The connector may not have been created correctly. Try creating another connector using the same set of configurations (providers) but only one multivalued attribute, which is the one that failed the first time. Try direct provisioning. Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning.
Response code: SPML Provisioning Child Meta-Data Null Response Description: Child meta-data list is null.	You may have been trying to perform provisioning for one particular type (for example, role or membership) of multivalued attribute when this error occurred. The connector may not have been created correctly. Try creating another connector using the same set of configurations (providers) but only one multivalued attribute, which is the one that failed the first time. Try direct provisioning. Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning.
Response code: SPML Provisioning Child Meta-Data Problem Response Description: An error occurred while sorting the child meta-data list.	You may have been trying to perform provisioning for one particular type (for example, role or membership) of multivalued attribute when this error occurred. The connector may not have been created correctly. There is a problem in the order that has been set for the provisioning fields. Try creating another connector with fewer attributes for the relevant multivalued field. Try direct provisioning. After each successful round of provisioning, try adding fields one by one by performing the Manage Connector procedure. The point at which you start facing this issue again identifies the field that is not in the correct order.
Response code: SPML Provisioning Id Missing Response Description: Unique ID is missing.	You are trying to run an operation on a created user. However, the Create User operation itself may not have run successfully and the unique ID (PSO-ID) that was expected as the response was not received. Therefore, the provisioned instance data was not updated in Oracle Identity Manager. Check why this operation failed.
Response code: SPML Provisioning Target ID Missing Response Description: Unique Target ID is missing	Check the provider parameters that have been entered. TargetID may be missing.
Response code: OIM API Error Response Description: An error occurred in the OIM API layer.	Check if Oracle Identity Manager is operating correctly for other operations. Check the connectivity between the Oracle Identity Manager front end and the database. Note: This error is not related to the providers that you use.
Response code: OIM Process Form Not Found Response Description: Process form was not found in OIM	The generic technology connector may not have been created correctly. Try creating another connector using the same set of configurations. Try direct provisioning. Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning. Note: This error is not related to the providers that you use.
Response code: OIM Process Form Instance Not Found Response Description: Process form instance was not found for the specified form during update	The provisioned instance information in the Oracle Identity Manager database may have become corrupted. Try direct provisioning. If the problem persists, then there may be an issue with the generic technology connector. Create another generic technology connector by using the same set of configurations. Note: This error is not related to the providers that you use.
Response code: OIM Atomic Process Instance Not Found Response Description: Process instance found is not an atomic process	The provisioned instance information in the Oracle Identity Manager database may have become corrupted. Try direct provisioning. If the problem persists, then there may be an issue with the generic technology connector. Create another generic technology connector by using the same set of configurations. Note: This error is not related to the providers that you use.
Response code: Column Not Found Response Description: An expected column was not found in the result set	The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations. Try direct provisioning. Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning. Note: This error is not related to the providers that you use.
Response code: IT Resource Instance Not Found Response Description: IT Resource Instance was not found in OIM	The generic technology connector may not have been created correctly. Try creating another generic technology connector by using the same set of configurations. Try direct provisioning. Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning. Note: This error is not related to the providers that you use.
Response code: Version Not Found Response Description: The required process form version was not found in OIM	The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations. If you have edited an existing connector by adding a new field to an existing data set, then that operation may have failed. Try making the same change again in the connector. Note: This error is not related to the providers that you use.
Response code: Version Not Defined Response Description: The required process form version was not defined in OIM	The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations. If you have edited an existing connector by adding a new field to an existing data set, then that operation may have failed. Try making the same change again in the connector. Note: This error is not related to the providers that you use.
Response code: Web Service Not Found Response Description: Web Service not found on the target server. Check service name and IP address.	Check the service name and IP address provided in the Web service URL. If these are correct, then check if the Web service is running.
Response code: Web Service Connection Refused Response Description: Web Service connection could not be established. Check that server is running and port specified is correct.	Check if the Web service is running.
Response code: Web Service No Such Method Response Description: Unable to invoke web service method. Check operation name and parameters.	Check the operation name and parameters.
Response code: Web Service Null Parameter Value Response Description: The parameter value passed to web service is null.	Check if the provisioning process ran correctly. The Provisioning Format provider may not have run correctly and, therefore, may have generated NULL output.
Response code: Web Service HTTP Library Missing Response Description: Web Service HTTP library is missing from classpath.	There is a problem with the Oracle Identity Manager installation. Contact Oracle Support and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.
Response code: Web Service Null Result Value Response Description: Web Service result value is null.	Check if the Web service is running correctly. At present, it is generating NULL output as the response to the Oracle Identity Manager provisioning request.
Response code: Web Service Invocation Issue Response Description: An error occurred during Web Service invocation.	Check the credentials of the Web service.
Response code: Web Service Target URL Missing Response Description: Web Service target URL is missing for invocation.	Check the values of the provider parameters. The Web service URL may be missing. Modify the generic technology connector and provide this value again.
Response code: Web Service Target Method Name Missing Response Description: Web Service target method name is missing for invocation.	Check the values of the provider parameters. The Web service operation name may be missing. Modify the generic technology connector and provide this value again.
Response code: Web Service Response XML Parsing Error Response Description: An error occurred during XML parsing of the web service response.	Check if the Web service is running correctly. It is generating an SPML response that does not conform to the format specified for the Web service provider.
Response code: An error occurred during XML parsing of the web service response. Web Service Response ID Error Response Description: Unique ID is not available in the Web Service response.	Check if the Web service is running correctly. For the Create User operation, it is generating an SPML response that does not conform to the specified format. In addition, it is not returning the PSO-ID created in the target system. The provider specification for the Web Service provider expects the return of the PSO-ID field.
Response code: Web Service Protocol Connection Error Response Description: An error occurred in the Oracle-SOAP HTTP connection.	Check the service name and IP address provided in the Web service URL. If these are correct, then check if the Web service is running. Check the operation name and parameters.
Response code: Web Service Protocol Processing Error Response Description: An error occurred while calling the Oracle-SOAP API.	Check the service name and IP address provided in the Web service URL. If these are correct, then check if the Web service is running. Check the operation name and parameters.

Problem Description

Solution

Response code:

SPML Velocity Properties Not Read

Response Description:

Necessary SPML template properties could not be read.

There is a problem with the Oracle Identity Manager installation. Contact Oracle Support, and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.

Response code:

SPML Template Not Read

Response Description:

The SPML template file was not found.

Response code:

SPML Unknown Operation

Response Description:

Type of provisioning operation not in allowed set: Create, Delete, Enable, Disable, Modify, Child Table Operations.

Response code:

SPML Provisioning Input Null

Response Description:

SPML provisioning input data is null.

Check if the provider parameters have been correctly specified.

Check if provisioning was initiated by direct provisioning or request provisioning. Retry the procedure by using the direct provisioning option.

Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning.

Response code:

SPML Template Processing Error

Response Description:

An error in template processing for generation of SPML request occurred.

There is a problem with installation. Contact Oracle Support, and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.

Response code:

SPML Provisioning Operation Name Missing

Response Description:

Operation name for provisioning is missing.

The generic technology connector may not have been created correctly. Try creating another connector using the same set of configurations (providers) but with fewer attributes. Try direct provisioning.

Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning.

Response code:

SPML Provisioning Child Name Missing

Response Description:

Child name is missing.

You may have been trying to perform provisioning for one particular type (for example, role or membership) of multivalued attribute when this error occurred.

The connector may not have been created correctly. Try creating another connector using the same set of configurations (providers) but only one multivalued attribute, which is the one that failed the first time. Try direct provisioning.

Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning.

Response code:

SPML Provisioning Child Meta-Data Null

Response Description:

Child meta-data list is null.

You may have been trying to perform provisioning for one particular type (for example, role or membership) of multivalued attribute when this error occurred.

Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning.

Response code:

SPML Provisioning Child Meta-Data Problem

Response Description:

An error occurred while sorting the child meta-data list.

You may have been trying to perform provisioning for one particular type (for example, role or membership) of multivalued attribute when this error occurred.

The connector may not have been created correctly. There is a problem in the order that has been set for the provisioning fields. Try creating another connector with fewer attributes for the relevant multivalued field. Try direct provisioning. After each successful round of provisioning, try adding fields one by one by performing the Manage Connector procedure. The point at which you start facing this issue again identifies the field that is not in the correct order.

Response code:

SPML Provisioning Id Missing

Response Description:

Unique ID is missing.

You are trying to run an operation on a created user. However, the Create User operation itself may not have run successfully and the unique ID (PSO-ID) that was expected as the response was not received. Therefore, the provisioned instance data was not updated in Oracle Identity Manager. Check why this operation failed.

Response code:

SPML Provisioning Target ID Missing

Response Description:

Unique Target ID is missing

Check the provider parameters that have been entered. TargetID may be missing.

Response code:

OIM API Error

Response Description:

An error occurred in the OIM API layer.

Check if Oracle Identity Manager is operating correctly for other operations. Check the connectivity between the Oracle Identity Manager front end and the database.

Note: This error is not related to the providers that you use.

Response code:

OIM Process Form Not Found

Response Description:

Process form was not found in OIM

The generic technology connector may not have been created correctly. Try creating another connector using the same set of configurations. Try direct provisioning.

Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning.

Note: This error is not related to the providers that you use.

Response code:

OIM Process Form Instance Not Found

Response Description:

Process form instance was not found for the specified form during update

The provisioned instance information in the Oracle Identity Manager database may have become corrupted. Try direct provisioning.

If the problem persists, then there may be an issue with the generic technology connector. Create another generic technology connector by using the same set of configurations.

Note: This error is not related to the providers that you use.

Response code:

OIM Atomic Process Instance Not Found

Response Description:

Process instance found is not an atomic process

The provisioned instance information in the Oracle Identity Manager database may have become corrupted. Try direct provisioning.

If the problem persists, then there may be an issue with the generic technology connector. Create another generic technology connector by using the same set of configurations.

Note: This error is not related to the providers that you use.

Response code:

Column Not Found

Response Description:

An expected column was not found in the result set

The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations. Try direct provisioning.

Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning.

Note: This error is not related to the providers that you use.

Response code:

IT Resource Instance Not Found

Response Description:

IT Resource Instance was not found in OIM

The generic technology connector may not have been created correctly. Try creating another generic technology connector by using the same set of configurations. Try direct provisioning.

Refer to Oracle Identity Manager Administrative and User Console Guide for information about direct provisioning.

Note: This error is not related to the providers that you use.

Response code:

Version Not Found

Response Description:

The required process form version was not found in OIM

The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations. If you have edited an existing connector by adding a new field to an existing data set, then that operation may have failed. Try making the same change again in the connector.

Note: This error is not related to the providers that you use.

Response code:

Version Not Defined

Response Description:

The required process form version was not defined in OIM

Note: This error is not related to the providers that you use.

Response code:

Web Service Not Found

Response Description:

Web Service not found on the target server. Check service name and IP address.

Check the service name and IP address provided in the Web service URL. If these are correct, then check if the Web service is running.

Response code:

Web Service Connection Refused

Response Description:

Web Service connection could not be established. Check that server is running and port specified is correct.

Check if the Web service is running.

Response code:

Web Service No Such Method

Response Description:

Unable to invoke web service method. Check operation name and parameters.

Check the operation name and parameters.

Response code:

Web Service Null Parameter Value

Response Description:

The parameter value passed to web service is null.

Check if the provisioning process ran correctly. The Provisioning Format provider may not have run correctly and, therefore, may have generated NULL output.

Response code:

Web Service HTTP Library Missing

Response Description:

Web Service HTTP library is missing from classpath.

There is a problem with the Oracle Identity Manager installation. Contact Oracle Support and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.

Response code:

Web Service Null Result Value

Response Description:

Web Service result value is null.

Check if the Web service is running correctly. At present, it is generating NULL output as the response to the Oracle Identity Manager provisioning request.

Response code:

Web Service Invocation Issue

Response Description:

An error occurred during Web Service invocation.

Check the credentials of the Web service.

Response code:

Web Service Target URL Missing

Response Description:

Web Service target URL is missing for invocation.

Check the values of the provider parameters. The Web service URL may be missing. Modify the generic technology connector and provide this value again.

Response code:

Web Service Target Method Name Missing

Response Description:

Web Service target method name is missing for invocation.

Check the values of the provider parameters. The Web service operation name may be missing. Modify the generic technology connector and provide this value again.

Response code:

Web Service Response XML Parsing Error

Response Description:

An error occurred during XML parsing of the web service response.

Check if the Web service is running correctly. It is generating an SPML response that does not conform to the format specified for the Web service provider.

Response code:

An error occurred during XML parsing of the web service response. Web Service Response ID Error

Response Description:

Unique ID is not available in the Web Service response.

Check if the Web service is running correctly. For the Create User operation, it is generating an SPML response that does not conform to the specified format. In addition, it is not returning the PSO-ID created in the target system. The provider specification for the Web Service provider expects the return of the PSO-ID field.

Response code:

Web Service Protocol Connection Error

Response Description:

An error occurred in the Oracle-SOAP HTTP connection.

Check the service name and IP address provided in the Web service URL. If these are correct, then check if the Web service is running. Check the operation name and parameters.

Response code:

Web Service Protocol Processing Error

Response Description:

An error occurred while calling the Oracle-SOAP API.

Check the service name and IP address provided in the Web service URL. If these are correct, then check if the Web service is running. Check the operation name and parameters.