cancel
Showing results for 
Search instead for 
Did you mean: 

java iview Runtime error after Portal SP Update

Former Member
0 Kudos

Hi all

we have updated our Netweaver 7.02 sp3 to sp14 Recently

after the update , system is up and Running ,we are able to access /nwa

but , when tried to update /irj/portal we are getting error

"Java iview Runtime "


copy Right 2002 SAP AG All Rights Reserved


An exception occured while processing your request

if the situation persists ,  please contact the system administrator

already we have followed SAP Note :  1889857 - Java iview runtime error while accessing irj/portal page after the upgrade or patching of the system

still the same error.

Kindly help on this

I know this is Might be a Generic error for portal admins

Regards

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

any Response from the community on this ?

Regards

Former Member
0 Kudos

Hi,

What is your Portal data source? Is it Web AS Java or is R/3?

If it is R/3 system, please check if R/3 system is up or not.

If it is Web AS Java, please check if J2EE_GUEST user is not locked.

If it is locked, unlock it and reset the password and restart the server if required.

Also, if this doesn't help or if you've already checked the above steps, please paste the default trace of the server.

BR,

Anurag

Former Member
0 Kudos

Hi Anurag

Thanks for the Response first

SAP has suggested the following

=============================================================

You can find this located at:

../usr/sap/<SAPSID>/<(>

<<)>J2EE_Inst_No>/j2ee/cluster/server0/log/default#.trc

- Verify the portal deployment: Go to the directories deployment, pcd,

and

pcdContent, in the following paths:

- /usr/sap/<SAPSID>/JC<instance number>/j2ee/cluster/server0/

apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment


- /usr/sap/<SAPSID>/JC<instance number>/j2ee/cluster/server0/

apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd


- /usr/sap/<SAPSID>/JC<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.


=========================================================================

we have followed the above steps and now we are taking the system restart with cleanipc


The issue :

system will be up and running

we can login to nwa


only problem is  getting the error while logging into  http://abcdefghijklm.com/irj/portal  ,

error details already posted in the thread initially.


==========================================================================



This is the error in log files


Full Message Text

Caused by: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application com.sap.portal.themes.lafservice

Caused by: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application com.sap.portal.runtime.config

.component

#82A35F219B0200620000006300C90032000503581EC49F4F#1411051891760#System.err#sap.com/irj#System.err#xDA84kk#55##466FD13F3F4311E4B01D00000082DDC2#46

6fd13f3f4311e4b01d00000082ddc2-0#466fd13f3f4311e4b01d00000082ddc2#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.core.

broker.PortalApplicationNotFoundException: Could not find portal application com.sap.portal.themes.lafservice#

any help is highly apreciated

Thanks in advance

Reagrds

0 Kudos

Hi,

According to the exception "PortalApplicationNotFoundException", it seems that the application is not deployed successfully on your system.

Did you find any *.err files under "/deployment/pcd" folder? Or under the other folders you mentioned?

The files represent portal applications, and if deployed successfully, they will end with *.bak.

The trace file mentioned: com.sap.portal.themes.lafservice & com.sap.portal.runtime.config.component – what is the suffix of those two applications in the "deployment/pcd" folder?

In case they are with *.bak, and there is no *.err in the folder any longer, you can always deploy again the EP-PSERV.SCA of the version and SP you are currently using, and check whether it solves the problem.

If there are *.err files that are being created after the restart, then you can check in the *.log file that is being generated (relevant for the specific application name), for the problem.

More details can be found in SAP note 1130469 - Deployment failure of PAR and EPA (EPT) files in the portal

Thanks & regards,

Michal Zilcha-Lang

Former Member
0 Kudos

Hi,

I've also recently faced this issue though it was not a patch upgrade scenario.

The issue was with the space of oraarch folder that got full.

My BASIS team deleted the old files and restarted the server and the issue got resolved.

So, you can also look into this direction, if the suggested approach by SAP doesn't work out .

BR,

Anurag

Former Member
0 Kudos

Hi  Michal Zilcha-Lang

You are Right


We have found the following err files in the Following Location

1 ) /usr/sap/xxxxxxx/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment    

-------No err Files in this location


2)/usr/sap/xxxxxxx/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd

Two err files in this location -----

com.sap.portal.runtime.application.rfcengine.par.err  and

gcwebservice.par.err


3)/usr/sap/xxxxxxx/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcdContent

Four err files in this location ---

     com.sap.netweaver.coll.DetailedNav.epa.err

     com.sap.netweaver.coll.CollaborationRoomTemplatesParts.epa.err

     com.sap.netweaver.coll.CollaborationContent.epa.err

     sap.com~caf~eu~gp~content~portal.epa.err

=========================================================================

As per SAP , we have removed the *err file extensions of above all the  files and Taken the Restart of the SAP System , but the issue not Resolved

Question to Michal Zilcha-Lang

=============================

1) Do we need to anything extra apart from the above steps

2)Also in the above steps we are only checking the server0 locations, Do we need to check the server1 locations for the above as well  in the 3 locations

3)Do we need to deploy the EP-PSERV Again

4)At the moment am unable to provide the prefix names of the components

com.sap.portal.themes.lafservice &

com.sap.portal.runtime.config.component

Thank you Michal Zilcha-Lang  and Anurag for your Responses


Regards

Former Member
0 Kudos

Hi,

Yes, it's definitely worth a try to look for those *.err files in other server nodes as well.

Else, you can also search for *.err files at the OS level and you'll get to know the various locations, if they're present. Restart the server after you rename the files.

If this still doesn't work out and you find no *.err files, then deploy EP-PSERV again.

Let us know the results.

BR,

Anurag

0 Kudos

Hi again,

Basically the deployment of the portal applications is done to the file system on server0.

Eventually all that the deployment of the SCA does is to extract all the *.par files under the deployment folder (pcd – for the *.par applications & pcdContent – for the EPA files).

Then a restart is needed in order for the portal applications and the content to be deployed on the portal.

After a successful deployment, the files are added with a suffix *.bak.

In case of failure in the deployment, the suffix is *.err and there is also a *.log file that explains why the deployment of the specific application failed.

If you deleted the suffix of *.err, restarted the system, and they were created again, then you should check what the problem is.

As I explained, there should be also *.log files generated, so you can check what was the reason for the failure.

Regarding com.sap.portal.themes.lafservice & com.sap.portal.runtime.config.component – what do you mean that you couldn't provide the prefix? Does it mean that they don't exist at all?

If applications are missing, then maybe the EP-PSERV.SCA was not deployed successfully.

In that case, you can always deploy this SCA again (as long as it is the same version – just mark in the deployment  - "deploy with any version"), and check whether a deployment and then the restart solve the problem.

Thanks & regards,

Michal

Former Member
0 Kudos

Hi Anurag , Hi Michal Zilcha-Lang  and Hi all

in the location 

/usr/sap/xxxxxxx/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd


we  have the files   (following are the complete file names including suffix and  prefix)


com.sap.portal.runtime.config.component.par.log   

com.sap.portal.themes.lafservice.par.log  

both the above  log  files contain the following error

Caused by: com.sapportals.portal.pcd.pl.PlRuntimeException: SQLException is not transient, error code = 30036, sql state = 99999

Batch rolled back. Caused by java.sql.BatchUpdateException: ORA-30036: unable to extend segment by 8 in undo tablespace 'PSAPUNDO'

/usr/sap/xxxxxxx/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcdContent

Also in  the above location the following log contain the  PSAPUNDO error

com.sap.portal.iviewcatcherrender.ept.log

com.sap.portal.remoteproducerregistrationeditor.ept.log

com.sap.portal.syncerrors.ept.log

com.sap.portal.umeenduserremoteusermappingwd.ept.log

Original exception:

PcdRuntimeException: SQLException is not transient, error code = 30036, sql state = 99999

Batch rolled back. Caused by java.sql.BatchUpdateException: ORA-30036: unable to extend segment by 8 in undo tablespace 'PSAPUNDO'

=====================================================================

Now my question is , do we need to re-deploy all the software components , since we do not know exactly which component has to be redeployed

What does the ORA-30036: unable to extend segment by 8 in undo tablespace 'PSAPUNDO' represent  (also am searching on this)

did any one face this kind of issue , and what is the solution for it ,

Thanks in advance

Former Member
0 Kudos

Hi Michal Zilcha-Lang 

I did not see your response now , before i respond to Anurag , Please find it. also find my update on suffix of the files

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

in the location

/usr/sap/xxxxxxx/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd


we  have the files   (following are the complete file names including suffix and  prefix)


com.sap.portal.runtime.config.component.par.log  

com.sap.portal.themes.lafservice.par.log 

both the above  log  files contain the following error

Caused by: com.sapportals.portal.pcd.pl.PlRuntimeException: SQLException is not transient, error code = 30036, sql state = 99999

Batch rolled back. Caused by java.sql.BatchUpdateException: ORA-30036: unable to extend segment by 8 in undo tablespace 'PSAPUNDO'

/usr/sap/xxxxxxx/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcdContent

Also in  the above location the following log contain the  PSAPUNDO error

com.sap.portal.iviewcatcherrender.ept.log

com.sap.portal.remoteproducerregistrationeditor.ept.log

com.sap.portal.syncerrors.ept.log

com.sap.portal.umeenduserremoteusermappingwd.ept.log

Original exception:

PcdRuntimeException: SQLException is not transient, error code = 30036, sql state = 99999

Batch rolled back. Caused by java.sql.BatchUpdateException: ORA-30036: unable to extend segment by 8 in undo tablespace 'PSAPUNDO'

=====================================================================

Now my question is , do we need to re-deploy all the software components , since we do not know exactly which component has to be redeployed

What does the ORA-30036: unable to extend segment by 8 in undo tablespace 'PSAPUNDO' represent  (also am searching on this)

did any one face this kind of issue , and what is the solution for it ,

Thanks in advance

Former Member
0 Kudos

Hi all

In the location

/usr/sap/xxxxx/JCxxx/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcdContent

In the file

sap.com~caf~eu~gp~content~portal.epa.log

We have following error

com.sap.portal.transport.deploy.IncompleteDeploymentException: The archive /usr/sap/xxxxx/JCxx/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployme

nt/pcdContent/sap.com~caf~eu~gp~content~portal.epa could not be deployed completely. Import failed for 44 of 59 objects. [pcd:portal_content/com.sap.pct/platform_add_on

s/GPContent: Import failed.

SQLException is not transient, error code = 30036, sql state = 99999

ORA-30036: unable to extend segment by 8 in undo tablespace 'PSAPUNDO'

, pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.folders.pages/com.sap.caf.eu.gp.pages.adhoc_rt: Import failed.

SQLException is not transient, error code = 30036, sql state = 99999

Batch rolled back. Caused by java.sql.BatchUpdateException: ORA-30036: unable to extend segment by 8 in undo tablespace 'PSAPUNDO'

Please suggest here , Do I need re-deploy all the software component again

also we have in PSAPUNDO 14gb free space ,

Do I need to make Autoextend as ON and deploy the components with option (deploy with any version)

Regards

0 Kudos

Hi,

The error in the logs describes that there is a problem with table space.

Please refer to SAP note 3155 – "Termination due to tablespace overflow"

It explains the issue and how to fix it.

After fixing the DB problem –

If you have only few *.err files, then you can just remove the suffix *.err, so that they will end with *.par/*.epa, and restart the system.

Please also delete the *.log files that correspond to the specific application/package, and check whether they are created again, or if problem is resolved.

If many applications or content are missing, or not properly deployed, you can just deploy the relevant SCAs again.

Thanks & regards,

  Michal

Former Member
0 Kudos

Hi Michal Zilcha-Lang

1. We have extended or given around 30 GB Space to PSAPUNDO

2. We have taken backup and removed all files from the above mentioned 3 locations

3  Redeployed all the components with force deploy option from JSPM

Issue Solved , we are able to login to irj/portal

Thank you for valuable feedbacks , Also Thank you Anurag