Oracle WebCenter Sites Mirror Site Configuration issues : Error publishing Start Menu items

With Oracle WebCenter Sites , when you tried to Mirror Site Configurations from source to destination systems , you may face exceptions as given below 

Error publishing Start Menu items, -12044, [pagename=OpenMarket/Xcelerate/Admin/MirrorSitePost] Error: com.openmarket.xcelerate.commands.StartMenuDispatcher: Publish: com.openmarket.basic.interfaces.AssetException: Remote object save didn’t fire [error was -611]

You can find additional errors in both source futuretense.txt and target futuretense.txt

Theses exception could be similar to as given below

Exception on Source

 <!–FTCS|||result=failure|||reason=Failed to commit changes to catalog StartMenu|||err=-611|||command=committables|||params=|||–>

Exception on Target

[2014-02-10 16:05:09,308 EST] [ERROR] [.kernel.Default (self-tuning)’] [fatwire.logging.cs.db] SQLException executing query: insert into StartMenu (id,cs_name,cs_description,cs_assettype,cs_processform,cs_partform,cs_saform,cs_itemtype,cs_assetsubtype,fw_uid) select id,cs_name,cs_description,cs_assettype,cs_processform,cs_partform,cs_saform,cs_itemtype,cs_assetsubtype,fw_uid from tt1320480615775

java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (CSDBUSER1105.I1150985659977) violated

Possible Root Cause for Mirror Site Configuration Issue

When items are being mirrored with Mirror Site Configuration, they are deleted and recreated on the target tables, using the ID column as the key for deletion. If a record exists on target with the same name but different ID as one being published, then it will not be deleted on target, and when the one being mirrored tries to save, there is an error on target because of a unique constraint on the name.

How to resolve Mirror Site Configuration Issue

Try enabling the debug mode log levels on the source system then you can find additional information as given below in the source futuretense.txt . Try to find the relevant logs related the failed exception i.e according to the exception on the source

<!–FTCS|||result=failure|||reason=Failed to commit changes to catalog StartMenu|||err=-611|||command=committables|||params=|||–>

Failed table name is StartMenu, so look for debug information related to StartMenu items. Similarly if you observe exceotions related to CSElement look for CSElement related debug information and in the next step you would be looking for an entry in CSElement table instead of StartMenu table

Object Name: StartMenu




        ->rows to be added/updated:

        Key=1159296432909 version=null

        Key=1159296432981 version=null

        Key=1159296432977 version=null

        ->rows to be deleted:


  1. Copy all these Key’s to a notepad
  2. Using Sites-Explorer, check in Start Menu table on the source for the ids noted above. (Not all ids will be present)
  3. Get the name of the asset corresponding to ID on the source system
  4.  Using Sites-Explorer, find the records in the on the target with the same name as on the source but with different ids.(Note down the assets which have same name in both target and source system but with different ID)
    • Use the Admin UI to remove or rename the items identified in step 4, or use Sites-Explorer to rename them. Don’t delete the records using Sites-Explorer as this may leave behind some orphan records in other tables.
  5.  Run Mirror Site Configuration again.
  6. Example : In the above debug message , get the key 1159296432981
    • Search in the source systems Start Menu table for the record 1159296432981
    • Assume if the name of the Start Menu is “Find Template”
    • Go to the Target system and search for “Find Template” Start Menu item
    • If the id of the Start Menu on target is different from source and Delete this “Find Template” Start Menu from Admin UI
    • If the ID is same or if the name of the Start Menu is not available, ignore the Start Menu
    • Similarly do these steps fro all the different keys

Oracle WebCenter Sites Upgrade/Fatwire Upgrade : High Level upgrade actvities

Below are the some of the high level activities to be considered while upgrading from Fatwire 7.X to WebCenter Sites 11g. This list can be considered as high level check list for Pre & Post upgrade.

Pre Upgrade Activities

  1. Make sure there are no open DB connections
  2. Disable all publishing schedules and ensure that no publishing sessions are running
  3. For JDK 1.6, copy the jaxb-impl-2.1.12.jar
  4. Update Classpath with MSXML.jar : Missing with our scripts
  5. Update start-up scripts with XX:MaxPermSize and -Dcs.useJavaURLDecoder to false and other JVM settings
  6. Update LD_LIBRARY_PATH with CS-INSTALL\bin directory
  7. Ensure that all external data feeds and events are disabled
  8. Disable Revision Tracking for the assettypes
  9. Add the path to WebCenter Sites’ modified version of the Microsoft XML Parser (MSXML.jar in the WEB-INF/lib directory).
  • If the class path refers to another version of the Microsoft XML Parser, WebCenter Sites will fail when parsing XML.

Post Upgrade Activities

  1. Copy Property Files
  2. Create custom/shared folders
  3. Copy Image & JS Folders
  4. Apply customizations
  5. After the upgrade, attribute forms will display additional fields which are not seen on a fresh installation. To make the attribute forms consistent with those of a fresh installation, you will edit the gator.ini file by setting the mwb.externalattributes property to false
  6. Create the start menus for PageAttribute, PageDefinition, and PageFilter so these asset types can be used.
  7. Re-Register the basic asset types
  8. Re apply any customizations on basic assets
  9. Enable Revision Tracking
  10. To enable publishing of site plan assets to the delivery system, initialize the RealTime destination. Initialization
  11. Create the SitePlan asset type on delivery
  12. Enable the publishing schedules
  13. Run Upgrade Utility . Publishing of approved assets will not function correctly until the upgrade utility is run
  14. Publish assets
  15. Rerun Search Indices
  16. Enable any events
  17. Clear Client Browser caches
  18. Verify