on 09-13-2014 7:43 AM
Hi Experts,
We have recently started upgrading the Portal Landscape from 7.02 to 7.4 SP level 7.After upgrade, the standard Ajax theme or customized theme is not allowing some of the users to login. It simply hangs while loading the theme.
In default trace, we are getting "pcd:portal_content/com.sap.pct/every_user/general/defaultAjaxframeworkContent/com.sap.portal.afpDesktop/frameworkPages/com.sap.portal.AFPpage/com.sap.portal.AFPResources#com%2esap%2eportal%2enavigation%2eportallauncher%2edefault.pcd%3aportal_content%2fcom%2esap%2epct%2fevery_user%2fgeneral%2fdefaultAjaxframeworkContent%2fcom%2esap%2eportal%2eafpDesktop%2fframeworkPages%2fcom%2esap%2eportal%2eAFPpage.com%2esap%2eportal%2eAFPResources,5,Managed_Application_Thread]] Error: Unexpected Exception when writing to database.
[EXCEPTION]
com.sapportals.portal.pcd.gl.PcdInconsistentUpdateException: Transaction cache is outdated for object" while assigning SAP standard or customized Ajax themes.
As per SAP Note: 1473054 , I have run Pcd consistency check and cleaned up some inconsistencies.
Also as per , I have renamed and restarted the system to recreate the com.sap folder in /usr/sap/<SID>/J00/j2ee/cluster/apps location.However issue persists.
SAP Note:1676247 is saying about these kind of issues in 7.3 version specific patch levels.
There is an OSS msg created for this issue, however SAP is not updating...
Kindly give some valuable suggestions to proceed further, if anybody has come across the same scenario...
Thanks & Best Rgds,
Kiran Sathyan.
Hi Kiran,
Did your problem resolve? I am facing the same problem- it screen just hands mid way without loading anything. I am on SAP EP 7.4 SPS 11.
Thanks,
Sonali.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Sonali,
After upgrade to higher version, and you try to login to the portal with Ajax Framework Page (AFP) it hangs with the following screen
And you see the following exception in the stack trace
Unexpected Exception when writing to database
[EXCEPTION]
com.sapportals.portal.pcd.gl.PcdInconsistentUpdateException: Transaction cache is outdated for object id 0xFAF93DC827124F01390319754B53757465A07A64. name:sqO9HRtcjSpu4Q0Md6zr60za9YI~. db time:1443614844649, read time:-1
at com.sapportals.portal.pcd.pl.transaction.ConsistentValidationTransactionListener.beforeCompletion(ConsistentValidationTransactionListener.java:133)
at com.sapportals.portal.pcd.pl.transaction.TransactionHandle.beforeCompletion(TransactionHandle.java:228)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.beforePrepare(TXR_TransactionImpl.java:589)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.commit(TXR_TransactionImpl.java:1120)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionManagerImpl.commit(TXR_TransactionManagerImpl.java:333)
at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:610)
at com.sap.transaction.TxManager.commitLevel(TxManager.java:237)
at com.sap.tc.pcd.proxies.PlTxManagerProxy.commitLevel(PlTxManagerProxy.java:151)
at com.sapportals.portal.pcd.pl.transaction.TransactionHandleWrapper.commit(TransactionHandleWrapper.java:33)
at com.sapportals.portal.pcd.gl.ucd.UcdInitialContextFactory.createUserContext(UcdInitialContextFactory.java:172)
at com.sapportals.portal.pcd.gl.ucd.UcdInitialContextFactory.getInitialContext(UcdInitialContextFactory.java:84)
at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:64)
at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:45)
at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.<init>(InitialContext.java:216)
It means you have PCD Inconsistencies that should be resolved using the PCD Inconsistencies tools.
SAP Note 1473054 - Checking database consistency for the PCD for CE 7.1 & above
The above SAP Note will be replaced in the future with a new KBA:
2225655 - PCD Check tool central note
Best Regards,
Assaf
Hello Assaf and Kiran,
we have faced the same problem after upgrade to SPS 11. We have also a customer message open for this since 4 weeks without any solution.
We have found out so far, that the error is caused by the component com.sap.portal.navigation.afp.AFPResources while generating Java script variable afpVerifierKey.
SAP Support has also asked us to check PCD consistency - but the PCD tool is broken with SPS 11 (see note 2179587).
Best Regards,
Frank
Hi Sonali,
I suggest reviewing the KBA 2225655 - PCD Check tool central note as this issue is already fixed.
This is a known issue that was fixed in the KBA, the workaroud if you do not use the KBA is:
If you are using Windows, edit the following file
\usr\sap\<SID>\<Instance ID>\j2ee\configtool\config.properties:
Make sure that you use '\\' and not '/' or '\' in the following parameters:
secstorefs.keyfile
secstorefs.secfile
secstorefs.lib
rdbms.driverLocation
I recommend following the KBA and make sure you have the fixed version of the PCD tools.
Best Regards,
Assaf
Hi Assaf,
I am SAP BASIS Consultant and replying on behalf of Sonali, i followed your instruction to start PCDchecktool, which failed with an error, to fix it i followed your instruction to change values in config.properties file and restarted the system. But still i am facing issue to run the PCDCheckTool.
Changes made in Config.profperties files.
Please find the error screenshot for your reference.
Hi,
As these are network path they should be
No restart is needed it is a standalone tool
It is better to follow this video for using PCDInconsistencies tool:
Best Regards,
Assaf
Hello Kiran,
Please attach the full stack trace of the exception. The exception depends on the flow of which application is trying to write to the PCD Simultaneously without using PCD Locks.
Based on the stack trace we can determine if it occurs from custom code or SAP code and we can proceed from there.
Best Regards,
Assaf
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
As per Note: 2060017 - Change default value of Pcd.BasicRoleFactory.UmAttributesUpdatePolicy to "lazy"
and Configuring PCD Properties - Portal - SAP Library , I have changed the property and restarted..
However issue still persists and its throwing same "PcdInconsistentUpdateException: Transaction cache is outdated for object id " message in default trace..
Best Rgds,
Kiran Sathyan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kiran
1. Have you check the any patches for NW 7.4 portal SP level 07?
2. For all the SAP Notes & KBA take about the patch of your exiting SPS, Just refer this SAP KBA based on you can refer NW 7.4 patchs
3. Have you got any reply from SAP? i thing some program bug
BR
SS
Hi Kiran
Have you refer this SAP KBA for SP patches
2060017 - Change default value of Pcd.BasicRoleFactory.UmAttributesUpdatePolicy to "lazy"
BR
SS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.