Hi Saba,
Hope you are doing good.
Please verify the portal deployment: Go to the directories deployment,
pcd, and pcdContent, in the following paths:
- /usr/sap/<SAPSID>/J<instance number>/j2ee/cluster/server0/
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment
- /usr/sap/<SAPSID>/J<instance number>/j2ee/cluster/server0/
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd
- /usr/sap/<SAPSID>/J<instance number>/j2ee/cluster/server0/
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcdContent
-Look for files with the extension *.err
-If you find any, rename the *.err files, remove the err extension so
the files extension become
*.ept or *.par. Then, restart the J2EE Engine and ensure that the
extension are changed to *.bak.
Note that ".err" is a sign that it is not deployed
Once the above is done, such issues can also be caused due to inconsistencies and it will be worthwhile to run the force bootstrap once:
1)
Stop the j2ee server. Under cluster directory (/usr/sap/<SID>/J<nr>/cluster) rename server0 and subsequent nodes to ".old" respectively. The intention here is to create a backup of the existing files. Do not rename
the bootstrap folder as this is needed for the sync process.
2)
Change bootstrap.properties file to ensure it has element.resynch=force as per SAP note 710663.
3)
Restart the J2EE Engine. The new server folders should be created during the bootstrapping and this is a time consuming process as all the contents of the server nodes will be syched with the DB content.
4)
Remove the element.resynch=force property or change it to element.resynch=detect which is the default setting.
Please do the above steps and let me know the result.
Thank you!
_____________
Kind Regards,
Hemanth
SAP AGS