The synchronizeUserInformation Script Fails for user GUIDs that have special characters: Encountered[<userid>_=<user_GUID>] as one of the values. It does not conform to userName_=_oldGuid_=_newGuid format (Doc ID 3010666.1)

Last updated on SEPTEMBER 12, 2024

Applies to:

Symptoms

Running the synchronizeUserInformation script fails with the following error for user GUIDs that have special characters: 

ERROR

 Note we don't support binary GUIDs but you need to run the synchronizeUserInformation script to update the GUID once the GUIDs in the external LDAP have been fixed to return ASCII value. 

STEPS 

1. Run the following command to create a mapping file of users whose GUID has changed, that is, the GUID currently stored for a user in WebCenter Portal, does not match the GUID that is stored for the same user in the identity store.
   
   
   synchronizeUserInformation(appName='webcenter', operationType='RENAME_GUID_CREATE_MAPPING_FILE', fileName='GUIDMappingFile.properties', component='ALL', dbVendor='Oracle', dbHostNPort='<HOST:PORT>', dbName='<DATABASE_NAME>', dbSchemaName='<WEBCENTER_SCHEMA>',verbose='true')
    
   Provide the password for the webcenter schema when prompted.

   Review the generated GUIDMappingFile.properties file.
   Confirm you see users with GUIDs split in 2 or more lines as follows:
   
   

   <userid>_=_<part_of_old_guid_here>
   <part_of_old_guid_here>
   <part_ofold_guid_here>_=_<New_User_GUID_in_ASCII>

    

2. Run the following command to synchronize the user GUIDs.
   
   
   synchronizeUserInformation(appName='webcenter', operationType='RENAME_GUID_FROM_MAPPING_FILE', fileName='GUIDMappingFile.properties', component='ALL', dbVendor='Oracle', dbHostNPort='<HOST:PORT>', dbName='<DATABASE_NAME>', dbSchemaName='<WEBCENTER_SCHEMA>',verbose='true')
    
   Provide the password for the webcenter schema when prompted.
   
   When running the script you will see this error for the affected users:
   
   
   Encountered[<userid>_=_<part_of_old_guid_here>
   <part_of_old_guid_here>
   <part_ofold_guid_here>] as one of the values. It does not conform to userName_=_oldGuid_=_newGuid format. Processing ignored for this entry 

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.