Static Publishing - Starting Point Assets Can No Longer Be Published
(Doc ID 2005116.1)
Last updated on JULY 07, 2017
Applies to:Oracle WebCenter Sites - Version 220.127.116.11.0 to 18.104.22.168.0 [Release FatWire]
Information in this document applies to any platform.
Starting point assets can no longer be published, even after the affecting assets are edited/saved/approved.
In PubKeyTable table, there are entries for the starting point asset where newkey='D' and ispermanent='Y'. However, theree are no matching records in PublishedAssets table for the pubkeyid.
The queries to verify the status: (replace <assetid> with the id of the affecting starting point asset, and <targetid> with the id of the static publishing destination)
SELECT * FROM PubKeyTable pkt WHERE pkt.targetid=<targetid> AND pkt.assetid=<assetid>;
Expect 1 row returned, with newkey='D' and ispermanent='Y'.
SELECT pa.* FROM PublishedAssets pa, PubKeyTable pkt WHERE pa.pubkeyid=pkt.id AND pkt.assetid=pa.assetid AND pa.assetid=<assetid> AND pkt.targetid=<targetid>;
Expect 0 row returned.
2 possible changes have been identified that might have caused the issue:
A. The asset in question was removed as a starting point, and later on configured as a starting point again. That is, unset/reset the asset in question as a starting point.
B. The starting point asset is using a cached template that has unknowndeps, and the issue is observed after the asset is published a 2nd time.
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