SitePlan Tree (also known as Site Tree or Site Navigation) sometimes gets corrupted and it is a tedious job for developers to find a breakthrough to find an exact Page asset(s) from hundreds of them that are causing the issue. This blog will help you discover and walk through a new feature in 12c Support Tools that is undocumented by Oracle.
Page assets are visible in SitePlan Tree where the user can open and view them in web mode perspective. However, Page assets are not searchable through Contributor UI search, causing an error. See Screenshot 1 and Error Log below.
Root cause Analysis:
- If there are Page entries that don’t have reference in the SitePlan Tree.
- If the SitePlan Tree row contains a Page reference to an invalid Parent.
What causes SitePlan Tree corruption?
- It is possible that two or more users may have attempted to modify the SitePlan (or by saving Page assets) at the same time, which may have corrupted it.
- Executing improper SQL statements over System tables like Page, SitePlanTree, AssetPublication, AssetRelationTree, or SitePlan, etc.
- Though unavoidable, it is observed that this behavior is also one of the common side effects post-upgrade from 11g to 12c.
Oracle WebCenter Sites 12c provides an OOTB Utility through its Support Tools that will help diagnose and fix this issue.
Where is the VerifySitePlanTree Utility?
Path: Support Home -> Assets -> Verify SitePlanTree
Pre-requisite: Support Tools is installed on the instance where the issue has occurred and the user is logged in.
In Screenshot 2 below, there are 4 missing Page references and 3 invalid Page parent references. Check mark the appropriate rows and click “Fix” to resolve the respective corrupted records.
Below are operation fixes page assets that were successfully created and searchable through contributor UI but are not visible in SitePlan. In this case (see Screenshot 3), the asset has an entry in Page table but does not hold any reference to the SitePlanTree table. After selecting the respective corrupted records and clicking “Submit,” this utility creates an entry to SitePlanTree to resolve the issue.
The below operation (see Screenshot 4) fixes any invalid parent references. For example, the same Page asset may have two different Pages as its children with the same rank OR a Page might hold a deleted Page as its parent, etc. After selecting the respective corrupted records and clicking “Submit,” the utility moves such Page assets to the Unplaced section.
The corrupted SitePlan(s) and Page asset search issues in Contributor UI can be resolved using the new Oracle WebCenter Sites 12c VerifySitePlanTree Utility, which will save you a lot of time and effort.
Do you need help with any other errors or issues? Contact us today to let Inspired ECM’s experienced consultants keep your WebCenter Sites systems running successfully.