Symptom
The inconsistency can show itself in the following ways -
- In runtime, end users see a "Page not found or not available" error when accessing the affected role. The TLN (Top Level Navigation) may also be empty:
- In User Administration, the following error can appear when working with group assignments which contain the affected role -
"An error occured while adding group assignments; to display the correct status, search for assigned groups": - In User Administration, the role is visible with a name beginning with "PCD_ROLE_PERSISTENCE" followed by an alphanumeric number:
- The symptoms are accompanied by an error similar to the following in the defaultTrace:
Error##Java###Naming exception from the pcd when trying to access the
principal ROLE.PCD_ROLE_PERSISTENCE.t+wDdtBLMvWC+Pv9qzVhy
VXRAgY=
[EXCEPTION]
{0}#1#javax.naming.NamingException: SQLException is not transient,
error code = 1, sql state = 23000
ORA-00001: unique constraint (SAPSR3DB.SYS_C004126) violated
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Read more...
Environment
- SAP NetWeaver Enterprise Portal
- Release independent
Product
SAP NetWeaver 7.0 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.0 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 2 for SAP NetWeaver 7.0 ; SAP enhancement package 3 for SAP NetWeaver 7.0
Keywords
Collaboration Detailed Navigation , KBA , BC-PIN-PCD , PCD Generic Layer Services , EP-PIN-NAV , Navigation , EP-PIN-PRT , Portal Runtime , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.