The Incident Archive

For my use only don't use this without understanding what you are doing. I had a bunch of old MDS features in my menu which was causing our menu to collapse on login. (The collapse feature was set to not persist so the users had no way of fixing this). Instead of writing code or purging all settings from MDS for that page I decided on a data fix. Forgive my sql skills this was a quick and dirty. SCHEMA: ???_MDS TABLE :  MDS_ATTRIBUTES - this is where all the mds configuration is kept for each item and attribute. TABLE :  MDS_PATHS - this is where the file name for the resource you are looking for is kept. (ie page.jsff) you can also find the user in the path so you can do this for a specific user. DECLARE     v_content_id MDS_PATHS.PATH_CONTENTID%TYPE;     v_col_seq MDS_ATTRIBUTES.ATT_COMP_SEQ%TYPE;     CURSOR v_path_cursor IS       SELECT pa.PATH_CONTENTID FROM MDS_PATHS pa WHERE pa.PATH_PARTITION_ID = 3 AND PA....

This is not recommended: I really needed a document to go from status Done to status Released for a presentation on our training environment and did not have time to restore. (Our indexer was broken because we had files missing due to a db restore but no file system restore) (In the ???_OCS schema) Step 1) Find the revision   SELECT * FROM REVISIONS where ddocname = '1390427192270' Step 2) Update the revision based on did UPDATE REVISIONS SET DSTATUS = 'RELEASED', DRELEASESTATE = 'Y', DRELEASEDATE = SYSDATE where did = 109336; Now I could search for the document yay! Errors found in the logs: Universal Content Management - Content Server Indexing aborted. An error occurred during indexing. [APP: Oracle Universal Content Management - Content Server] general exception[[ intradoc.common.ServiceException: !csIndexerRenameFailedAbort         at intradoc.indexer.CommonIndexerBulkLoader.handleLoadError(CommonIndexerBulkLoader.java:614)  ...