My Oracle Support Banner

New profiles are missing on other nodes (Doc ID 2720832.1)

Last updated on DECEMBER 18, 2023

Applies to:

Oracle WebCenter Content - Version and later
Information in this document applies to any platform.


Opened Configuration Manager applet on node1 and created new profile.  The profile links are visible in the Search/Checkin drop downs. 

However, the new profile is missing on other nodes:


The issue was resolved after opening the new profile again in Configuration Manager and clicking OK (no changes necessary).  Then, published schema. 

The profile links became available in Search/Checkin drop downs and the profile was displayed in Configuration Manager.  Checkins were also successful using new profile.


Please see below testcase for further details.

1. Login into CS native UI on node1 as admin (e.g., http://<node1>:16200/cs).  Navigate to Administration -> Admin Applets

2. Open Configuration Manager

3. In Information Fields tab, click on IdcProfile. Then click Edit Values.  Create a trigger value (e.g., TestProfile1) 

4. Create a rule called Rule1 to be used by the profile. 

5. Create profile Test1Profile


6. On node1, reload the page or navigate to http://<node1>:16200/cs

7. Verify the new profile link Test1 Profile is seen in the Search/Checkin drop downs.  If not, then publish schema in Configuration Manager.  You may also have to clear browser cache (e.g., CTRL+F5).

8. Login into CS native UI on node2 (e.g., http://<node2>:16200/cs) as admin.

9. Verify the profile link Test1 Profile is missing in the Search/Checkin drop downs.  Even try publishing schema in Configuration Manager and clearing browser cache (e.g., CTRL+F5).  The profile link is still missing.

10. On node2, navigate to Administration -> Admin Applets.  Open Configuration Manager and click on Profiles tab.  Verify the new profile Test1Profile doesn't exist there either.

Close Configuration Manager on node2.


11. On node2 (e.g., http://<node2>:16200/cs), the new profile is available in the checkin page however.  Navigate to New Check-In -> Standard Check-in.  Try checking in content on node2 using the new profile and it will fail due to missing profile. 


The same checkin request will be successful on node1 however.

12. Resolve the missing profile issue by doing the following on either node using any profile.  Example below was done on node1 where the new profile was created.

13. On node2 (e.g., http://<node2>:16200/cs), checkins still fail however using the new profile.  Still get the "Value not found in allowed list of options for field 'Profile'" error.  Published schema from Configuration Manager and was able to checkin content using new profile.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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