on 09-29-2014 3:19 PM
Hi All
After updating the Portal system from SAP NW 7.02 SP3 To SP14 We have following in defaultTrace of server0
=================
#1.#82A35F219B0200760000002B015B00C2000503AC0C072987#1411412354607#com.sap.engine.core.configuration##com.sap.engine.core.configuration####8644A9FC428A11E4C37100000082
DDC2#8644a9fc428a11e4c37100000082ddc2-0#8644a9fc428a11e4c37100000082ddc2#SAPEngine_System_Thread[impl:5]_132##0#0#Error#1#/System/Server#Plain###Error occurred during D
B access: ,
=======================================================
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: ,
at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:342)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.commitConfigurationHandler(ConfigurationCache.java:1226)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.commit(ConfigurationHandlerImpl.java:919)
at com.sap.security.core.server.destinations.lib.DestinationServiceConnector.modify(DestinationServiceConnector.java:593)
at com.sap.security.core.server.destinations.lib.DestinationServiceConnector.update(DestinationServiceConnector.java:478)
at com.sap.security.core.server.destinations.io.ConfigurationManagerStorage.update(ConfigurationManagerStorage.java:98)
at com.sap.security.core.server.destinations.service.DestinationServiceImpl.updateDestination(DestinationServiceImpl.java:369)
at com.sap.security.core.client.ws.DeployableSecurityProtocol.createDestination(DeployableSecurityProtocol.java:784)
at com.sap.security.core.client.ws.DeployableSecurityProtocol.onStartApplication(DeployableSecurityProtocol.java:920)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ServiceBaseServer.setRuntimeInformation(ServiceBaseServer.java:182)
at com.sap.engine.services.webservices.server.deploy.wsclient.WSClientProtocolNotificator.onCommitStart630(WSClientProtocolNotificator.java:431)
and in default trace of server1 the following error
==================================
#1.5^H#82A35F219B02007F000367FB0132007200050368187F464D#1411120506029#com.redwood.scheduler.persistence.recovery#redwood.com/scheduler-ear#com.redwood.scheduler.persist
ence.recovery#Guest#0##EC17C4B93FE211E4C0FB00000082DDC3#ec17c4b93fe211e4c0fb00000082ddc3-0#ec17c4b93fe211e4c0fb00000082ddc3#Thread[Redwood Background Startup,5,Redwood]
##0#0#Error##Plain###Exception during recovery, will attempt recovery again SQLException (CODE=30036, STATE=99999): ORA-30036: unable to extend segment by 8 in undo tablespace 'PSAPUNDO'
PSAPUNDO is of 5 GB , and is free
Referred Note : 1867423 - java.sql.BatchUpdateException in DbReadTracker
which advices to Update the Software component FORUMS 7.02 to SP14
But in our system there is no component called FORUMS
1 . is the above error is critical
2 or is it an exception only which can be ignored
3 in my trace logs i dont have the word DbReadTracker
4 but i have the following lines
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: ,
at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:342)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.commitConfigurationHandler(ConfigurationCache.java:1226)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.commit(ConfigurationHandlerImpl.java:919)
at com.sap.security.core.server.destinations.lib.DestinationServiceConnector.modify(DestinationServiceConnector.java:593)
at com.sap.security.core.server.destinations.lib.DestinationServiceConnector.update(DestinationServiceConnector.java:478)
at com.sap.security.core.server.destinations.io.ConfigurationManagerStorage.update(ConfigurationManagerStorage.java:98)
at com.sap.security.core.server.destinations.service.DestinationServiceImpl.updateDestination(DestinationServiceImpl.java:369)
Regards/
Hi,
The error:
"unable to extend segment by 8 in undo tablespace 'PSAPUNDO'..." must be solved in your system first -
Please refer to SAP note 3155 – "Termination due to tablespace overflow"
It explains the issue and how to fix it.
In addition due to this problem, it might cause problems during deployment of the applications.
Hence it might be that you will need to redeploy the applications, or check for *.err files in the deployment folder of the portal. If there are any, then you should remove the suffix *.err, and restart the system.
For further details please refer to SAP note 1130469 - Deployment failure of PAR and EPA (EPT) files in the portal.
The problem you are facing was already reported in the SCN, and was solved. See the following thread:
It contains detailed explanations about the problem analysis.
I hope it will solve your issue as well,
Thanks & regards,
Michal Zilcha-Lang
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.