on 10-06-2009 2:01 AM
While running the EHP1SP3 upgrade for PI 7.1 we are getting an error in the downtime phase.
Looking at the deploy* log and trc I see error codes "ERROR CODE DPL.DBC.*" and the classic ORA-01658 unable to extend PSAPSR3DB. At the same time the oracle alert log gives us this error.
The problem is the SAPehpi deployment tries to continue and gets to phase DEPLOY_ONLINE_DEPL, at this phase the j2ee engine tries to start but can't as not all required components have been deployed due to the tablespace issue. There for the system is unstable and SAPehpi can't be continued or reset.
We are using SAPehpi_11-10007378.SAR SAPehpi version but it doesn't appear to pick up the space issue on the checks phase.
Has anyone else had this issue?
We are now restoring and starting again with additional space on PSAPSR3DB to confirm this is 100% the issue.
We have run the upgrade on or sandpit environment with success and our PI team very happy with EHP1 SP3 711.
Hi Dave,
> Looking at the deploy* log and trc I see error codes "ERROR CODE DPL.DBC.*" and the classic ORA-01658 unable to extend >PSAPSR3DB. At the same time the oracle alert log gives us this error.
>
When you got this error in log that time tablespace was full ?
If yes, then increase the space and then try.
Thanks
Sunny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Yes the table space is full at this point. However after you add the space the SAPehpi process can't continue as the j2ee engine files are half deployed and at this stage the SAPEHpi tries to start the j2ee instance for an online deployment.
Possible bug that this tablespace doen't appear in the checks phase.
Have you experienced this?
Regards Dave
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.