Error When Updating Database Design in Configuration Manager: "Error updating database design. Unable to update content item extended fields table design. Unable to execute service (null) and function updateCollectionMetaTable"
(Doc ID 1463813.1)
Last updated on DECEMBER 15, 2017
Applies to:Oracle WebCenter Content - Version 10.1.3.3.1 to 10.1.3.5.0 [Release 10gR3]
Information in this document applies to any platform.
An error is thrown when trying to Update Database Design in Configuration Manager after adding a new field. In this example, the new field added was xtest3, but any new field generates the same error. The error references a different field (xDeptResource in this example) and has always referenced that field. Despite the error the new field is added and shows up on the New Checkin page.
The error in Configuration Manager is:
After this, when new content is checked in, you get an error stating "Could not find the parameter 'xtest3'". The xtest3 field no longer exists in Configuration Manager and is no lonmger on the New Checkin page. The only way you are able to work around this is to add the xtest3 field back in. Once you create the new field named xtest3 again, content can be checked in without error.
You've republished all the schema options, cleared the cache and cookies, and tried on IE and Firefox, all with the same results.
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