SAP Knowledge Base Article - Preview

2395405 - Poor Portal Content Directory (PCD) performance


When creating, editing and opening portal content or when navigating on Portal Content Directory (PCD) content tree, the following is observed:

  • Poor performance;
  • 500 Connection timed out error exception is appearing;
  • When checking HTTP Watch Traces, calls to http://<HOST_NAME>.<DOMAIN>:<PORT>/webdynpro/resources/ are taking a very long time (several minutes). See Note 1558903 - How To Trace a Portal Scenario Using HttpWatch.
  • With CA Introscope it can be noticed in the “Transaction Tracer” a call with very long duration. Checking the “Summary View” of this call, it can be seen that a call to the Database is the culprit, using most of the time.



SAP Netweaver Enterprise Portal


SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.3


 PCD inconsistencies; inconsistencies; Check; PCD check; optimizations; PCD Cache Optimizer Tuning; PCD Cache Optimizer; PCD Cache; Update Database Statistics; Database Statistics; Database; Statistics , KBA , BC-PIN-PCD , PCD Generic Layer Services , SV-PERF-EP , SAP Enterprise Portal related performance issues , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.