cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

EHP7 SPS6 application is retaining old tablespace

Go to solution
Former Member

on ‎02-24-2015 2:10 PM

0 Kudos

Hi All,

Quick question:

EHP7 is NW 740. Past experience using SUM to carry out applications of EHP's and system upgrades has always required the creation of a new tablespace, eg. PSAPSR3740.

In this update/upgrade/enhancement of the system, I am moving from 701 NW to 740 NW, however, the checks results want the PSAP<SID>701 tablespace extended to accommodate the shadow instance preprocessing. This really doesn't seem at all right, as how will the repository switch work.

I was going to let the upgrade continue, but I'm not so sure now.......

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Reagan
Product and Topic Expert
Product and Topic Expert
‎02-24-2015 3:54 PM
0 Kudos

Hello Maria

Are you using the right stack file? The upgrade tool will provide the information about the "Target System Version" and "Current System Version" in the "Confirm Target" phase after you have supplied the stack file. What did the system display at this phase?

Could you check the content of the /<Upgrade Directory>/SUM/sdt/log/DIALOG.LOG file please?

If possible download another version of the SUM tool and restart the upgrade.

Cheers

RB

Show replies
Show replies
Former Member
‎02-24-2015 4:02 PM
0 Kudos

Hi Reagan,

Dialog .log: I have highligted in bold the target releases:

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[/sapinstall/EHP7SPS6/SUM/sdt/log/DIALOG.LOG]/-->

<!--PATTERN[DIALOG.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Feb 23, 2015 12:06:16 PM [Info  ]: Waiting for input in dialog WelcomeDialog type Composite.

Feb 23, 2015 12:06:18 PM [Info  ]: Processing input in dialog WelcomeDialog type Composite.

Feb 23, 2015 12:06:18 PM [Info  ]: Dialog WelcomeDialog has been confirmed.

Feb 23, 2015 12:06:18 PM [Info  ]: Dialog type InfoText with dialog name SUM Info displays dialog text <html>

<b>The Software Update Manager supports the following processes for ABAP, Java and dual-stack systems:</b><br/>

<ul>

<li>Release upgrade</li>

<li>Enhancement Package installation or update</li>

<li>Support Package Stack update</li>

<li>Single component updates and patches</li>

<li>Correction of Installed Software Information</li>

</ul>

Before you continue with this process, we recommend that you read SAP Note 1981278 which contains the latest release information about the Software Update Manager including a detailed list of supported processes.<br/>

<br/>

<b>Detected SAP NetWeaver system</b><br/>

</html>.

Feb 23, 2015 12:06:18 PM [Info  ]: Dialog type InfoText with dialog name SYSTEM_INFO displays dialog text <html><body>

<table>

<tr>

  <td title="System Technology">System Technology</td>

  <td title="ABAP system"><b>   ABAP system</b></td>

</tr>

<tr>

  <td title="System ID">System ID</b></td>

  <td title="XR3"><b>   XR3</b></td>

</tr>

<tr>

  <td title="System Directory">System Directory</td>

  <td title="/usr/sap/XR3"><b>   /usr/sap/XR3</td>

</tr>

</table>

</body>

</html>.

Feb 23, 2015 12:06:18 PM [Info  ]: Dialog WelcomeDialog variable handler has been updated.

Feb 23, 2015 12:06:18 PM [Info  ]: Dialog WelcomeDialog has been confirmed.

Feb 23, 2015 12:06:19 PM [Info  ]: Waiting for input in dialog UserCredentialsDialog type Composite.

Feb 23, 2015 12:06:19 PM [Info  ]: In dialog SIDADM_PWD variable /J2EE/SIDAdminUser/Password labeled Password has been set.

Feb 23, 2015 12:06:34 PM [Info  ]: In dialog SIDADM_USR the value of variable /J2EE/SIDAdminUser/UserName labeled User Name has been set to value of variable xr3adm.

Feb 23, 2015 12:06:34 PM [Info  ]: In dialog SIDADM_PWD variable /J2EE/SIDAdminUser/Password labeled Password has been set.

Feb 23, 2015 12:06:34 PM [Info  ]: In dialog SIDADM_PWD variable /J2EE/SIDAdminUser/Password labeled Password has been set.

Feb 23, 2015 12:06:34 PM [Info  ]: Processing input in dialog UserCredentialsDialog type Composite.

Feb 23, 2015 12:06:34 PM [Info  ]: In dialog SIDADM_USR the value of variable /J2EE/SIDAdminUser/UserName labeled User Name has been set to value of variable xr3adm.

Feb 23, 2015 12:06:34 PM [Info  ]: In dialog SIDADM_PWD variable /J2EE/SIDAdminUser/Password labeled Password has been set.

Feb 23, 2015 12:06:34 PM [Info  ]: Dialog UserCredentialsDialog has been confirmed.

Feb 23, 2015 12:06:34 PM [Info  ]: Dialog type InfoText with dialog name ExtraInfo displays dialog text <html>

<b>Authentication Mechanism</b>

</html>.

Feb 23, 2015 12:06:34 PM [Info  ]: Dialog type InfoText with dialog name ExtraInfo displays dialog text <html>

Software Update Manager needs to setup the correct authentication mechanism for using sapcontrol executable. This is required to control your SAP system during maintenance.

</html>.

Feb 23, 2015 12:06:34 PM [Info  ]: Dialog type InfoText with dialog name ExtraInfo displays dialog text <html>

Alternatively, if SUM requires user credentials to use functions of sapcontrol executable, enter the <b>xr3adm</b> credentials below: <br>

</html>.

Feb 23, 2015 12:06:34 PM [Info  ]: Dialog type InfoText with dialog name ValidateCredentialsInfo displays dialog text <html>In case the user credentials are supplied they will be verified when you choose <i>Next</i>.</html>.

Feb 23, 2015 12:06:34 PM [Info  ]: Dialog type InfoText with dialog name ExtraInfo displays dialog text <html>

<p><b>Additional Information</b><br>

In case you provide user credentials, it is <b>mandatory</b> that you perform the update process by specifying the xr3adm user. Entering another user in the field above, even if that user is authorized to operate the process, might cause severe errors and failure.

<br>

If your system is part of a Windows domain, you must enter the full user name preceded by the domain name. The syntax is as follows: <i>domain</i>\xr3adm. For more information, see SAP Note 927637.

</html>.

Feb 23, 2015 12:06:34 PM [Info  ]: Dialog UserCredentialsDialog variable handler has been updated.

Feb 23, 2015 12:06:34 PM [Info  ]: Dialog UserCredentialsDialog has been confirmed.

Feb 23, 2015 12:06:39 PM [Info  ]: Waiting for input in dialog DefineTargetDialog type Composite.

Feb 23, 2015 12:07:09 PM [Info  ]: In dialog TargetOptions the value of variable stack labeled <HTML><BODY><B>Stack configuration file (XML)</B></BODY></HTML> has been set to value of variable true.

Feb 23, 2015 12:07:09 PM [Info  ]: In dialog TargetOptions the value of variable inbox labeled <HTML><BODY><B>Manually prepared directory</B></BODY></HTML> has been set to value of variable false.

Feb 23, 2015 12:07:09 PM [Info  ]: In dialog INBOXDIR the value of variable INBOXDIR labeled   has been set to value of variable /sapinstall/EHP7SPS6/stack_for_slm.xml.

Feb 23, 2015 12:07:09 PM [Info  ]: Processing input in dialog DefineTargetDialog type Composite.

Feb 23, 2015 12:07:09 PM [Info  ]: In dialog TargetOptions the value of variable stack labeled <HTML><BODY><B>Stack configuration file (XML)</B></BODY></HTML> has been set to value of variable true.

Feb 23, 2015 12:07:09 PM [Info  ]: In dialog TargetOptions the value of variable inbox labeled <HTML><BODY><B>Manually prepared directory</B></BODY></HTML> has been set to value of variable false.

Feb 23, 2015 12:07:09 PM [Info  ]: In dialog INBOXDIR the value of variable INBOXDIR labeled   has been set to value of variable /sapinstall/EHP7SPS6/stack_for_slm.xml.

Feb 23, 2015 12:07:09 PM [Info  ]: Dialog DefineTargetDialog has been confirmed.

Feb 23, 2015 12:07:09 PM [Info  ]: Dialog type InfoText with dialog name Empty Line displays dialog text <null>.

Feb 23, 2015 12:07:09 PM [Info  ]: Dialog type InfoText with dialog name Dialog Description displays dialog text <html>Select the target version definition for your system

</html>.

Feb 23, 2015 12:07:09 PM [Info  ]: Dialog type InfoText with dialog name Empty Line displays dialog text <null>.

Feb 23, 2015 12:07:09 PM [Info  ]: Dialog type InfoText with dialog name Stack_Label displays dialog text Stack file or Directory.

Feb 23, 2015 12:07:09 PM [Info  ]: Dialog type InfoText with dialog name Dialog Description displays dialog text <html><br>Check the currently installed software components and their versions according to SAP Note 1533222</html>.

Feb 23, 2015 12:07:09 PM [Info  ]: Dialog DefineTargetDialog variable handler has been updated.

Feb 23, 2015 12:07:09 PM [Info  ]: Dialog DefineTargetDialog has been confirmed.

Feb 23, 2015 12:07:20 PM [Info  ]: Waiting for input in dialog ConfirmTargetDialog type Composite.

Feb 23, 2015 12:07:36 PM [Info  ]: In dialog KeywordInput the value of variable KEYWORD labeled Keyword        has been set to value of variable 1750819.

Feb 23, 2015 12:07:36 PM [Info  ]: Processing input in dialog ConfirmTargetDialog type Composite.

Feb 23, 2015 12:07:36 PM [Info  ]: In dialog KeywordInput the value of variable KEYWORD labeled Keyword        has been set to value of variable 1750819.

Feb 23, 2015 12:07:36 PM [Info  ]: Dialog ConfirmTargetDialog has been confirmed.

Feb 23, 2015 12:07:36 PM [Info  ]: Dialog type InfoText with dialog name Confirm Info displays dialog text

<html>Read the SAP Notes referenced in the Software Update Manager guide for your target system version and enter the keyword available in SAP Note 1981278 .

</html>.

Feb 23, 2015 12:07:36 PM [Info  ]: Dialog type InfoText with dialog name ONE_LINE_OF_SPACE displays dialog text <html>

<br></html>.

Feb 23, 2015 12:07:36 PM [Info  ]: Dialog type InfoText with dialog name TARGET_STATE displays dialog text

<html><body>

<table>

<tr>

  <td>New Product Version(s)       <br></td>

  <td><b>EHP7 FOR SAP ERP 6.0<br>SAP ERP 6.0<br>SAP GTS 10.1<br>SAP NETWEAVER 7.4<br>SAP LT REPLICATION SERVER 2.0<br></b></td>

</tr>

</table>

</body>

</html>.

Feb 23, 2015 12:07:36 PM [Info  ]: Dialog type InfoText with dialog name INITIAL_STATE displays dialog text

<html><body>

<table>

<tr>

  <td>Current Product Version(s)  <br></td>

  <td><b>EHP4 FOR SAP ERP 6.0 / NW7.01<br>SAP ERP 6.0<br>SAP GTS 10.0<br>SAP LT REPLICATION SERVER 2.0<br></b></td>

</tr>

</table>

<table>

<tr>

  <td><i>Note that the version information is acquired from the stack.xml file.</i></td>

</tr>

</table>

</body>

</html>.

Feb 23, 2015 12:07:36 PM [Info  ]: Dialog type InfoText with dialog name TWO_LINES_OF_SPACE displays dialog text <html>

</br></br>

</html>.

Feb 23, 2015 12:07:36 PM [Info  ]: Dialog type InfoText with dialog name Stack Info displays dialog text <html>

For more information (including the respective SP stack levels), see <a target="_blank" href="http://strsap03.corp.cjclark.com:4239/TargetSystemVersionReport.html">TargetSystemVersionReport.html</a>.</html>

.

Feb 23, 2015 12:07:36 PM [Info  ]: Dialog type InfoText with dialog name Confirme message displays dialog text <html><br>

Confirm the selected target version definition by choosing <i>Next</i>.</html>

.

Feb 23, 2015 12:07:36 PM [Info  ]: Dialog ConfirmTargetDialog variable handler has been updated.

Feb 23, 2015 12:07:36 PM [Info  ]: Dialog ConfirmTargetDialog has been confirmed.

I only created one stack.xml file for the current server as we are in proof of concept at the moment.

I am using the latest version of SUM, which is what came down with maintenance optimizer.

Reagan
Product and Topic Expert
Product and Topic Expert
‎02-24-2015 4:19 PM
0 Kudos

The system displays the target version correctly and in that case I would use a different SUM tool and see how it goes. The tablespace should be PSAPSR3740 as far as I have seen. This looks more likely an issue with the SUM tool.

Former Member
‎02-24-2015 4:24 PM
0 Kudos

Trying patch level 3, which was fine with HR EHP7 update, will update in 2 days (which is how long it takes to get to that point )

manumohandas82
Active Contributor
‎02-24-2015 4:25 PM
0 Kudos

Hi Maria ,

Can you post the contents of the table TAORA and IAORA

Thanks ,

Manu

Former Member
‎02-25-2015 4:54 PM
0 Kudos

Hi Reagan,

Space checks have come back requesting extension of PSAP<SID>701 instead of asking for creation of PSAP<SID>740 with SUM10SP12_3-20006540.SAR package. Originally I was using SP12_6.

TAORA contents

  TABART  TABSPACE                         PCTINC OFREELIST OFREEGROUP OPCTFREE OPCTU

  APPL0   PSAPDR3                          0000   001       01         10       40

  APPL1   PSAPDR3                          0000   001       01         10       40

  APPL2   PSAPDR3                          0000   001       01         10       40

  CLUST   PSAPDR3                          0000   001       01         10       40

  DDIM    PSAPDR3                          0000   001       01         00       60

  DFACT   PSAPDR3                          0000   004       01         10       60

  DODS    PSAPDR3                          0000   004       01         00       60

  POOL    PSAPDR3                          0000   001       01         10       40

  SDIC    PSAPDR3                          0000   001       01         10       40

  SDOCU   PSAPDR3                          0000   001       01         10       40

  SLDEF   PSAPDR3                          0000   001       01         10       40

  SLEXC   PSAPDR3                          0000   001       01         10       40

  SLOAD   PSAPDR3                          0000   001       01         10       40

  SPROT   PSAPDR3                          0000   001       01         10       40

  SSDEF   PSAPDR3                          0000   001       01         10       40

  SSEXC   PSAPDR3                          0000   001       01         10       40

  SSRC    PSAPDR3                          0000   001       01         10       40

  TEMP    PSAPDR3                          0000   001       01         10       40

  USER    PSAPDR3USR                       0000   001       01         10       40

  USER1   PSAPDR3USR                       0000   001       01         10       40

  USER2   PSAPDR3USR                       0000   001       01         10       40

  USER3   PSAPDR3USR                       0000   001       01         10       40

  USER4   PSAPDR3USR                       0000   001       01         10       40

  USER5   PSAPDR3USR                       0000   001       01         10       40

  USER6   PSAPDR3USR                       0000   001       01         10       40

  USER7   PSAPDR3USR                       0000   001       01         10       40

  USER8   PSAPDR3USR                       0000   001       01         10       40

  USER9   PSAPDR3701                       0000   001       01         10       40

IAORA Contents

TABART  TABSPACE                       PCTINC OFREELIST OPCT

APPL0   PSAPDR3                        0000   001       10

APPL1   PSAPDR3                        0000   001       10

APPL2   PSAPDR3                        0000   001       10

CLUST   PSAPDR3                        0000   001       10

DDIM    PSAPDR3                        0000   001       10

DFACT   PSAPDR3                        0000   004       10

DODS    PSAPDR3                        0000   004       10

POOL    PSAPDR3                        0000   001       10

SDIC    PSAPDR3                        0000   001       10

SDOCU   PSAPDR3                        0000   001       10

SLDEF   PSAPDR3                        0000   001       10

SLEXC   PSAPDR3                        0000   001       10

SLOAD   PSAPDR3                        0000   001       10

SPROT   PSAPDR3                        0000   001       10

SSDEF   PSAPDR3                        0000   001       10

SSEXC   PSAPDR3                        0000   001       10

SSRC    PSAPDR3                        0000   001       10

TEMP    PSAPDR3                        0000   001       10

USER    PSAPDR3USR                     0000   001       10

USER1   PSAPDR3USR                     0000   001       10

USER2   PSAPDR3USR                     0000   001       10

USER3   PSAPDR3USR                     0000   001       10

USER4   PSAPDR3USR                     0000   001       10

USER5   PSAPDR3USR                     0000   001       10

USER6   PSAPDR3USR                     0000   001       10

USER7   PSAPDR3USR                     0000   001       10

USER8   PSAPDR3USR                     0000   001       10

USER9   PSAPDR3701                     0000   001       10

Former Member
‎03-12-2015 11:39 AM
0 Kudos

The issues is the contents in TAORA and IAORA. To allow PSAPDR3740 to be requested by SUM for the upgrade, PSADR3701 needed to be assigned TABART SLDEF, SLEXC, SSDEF and SSEXC. This required the removal of those designations against PSAPDR3, and the removal of USER9 assignment to PSAPDR3701. SAP note 541542 details what should be what.

Thanks for all your help.

Answers (8)

Answers (8)

manumohandas82
Active Contributor
‎02-24-2015 3:43 PM
0 Kudos

Yes . I too agree with Guarav .

At the start the SUM is checking for the existing Tablespace  as X already exists it is looking for PSAP<SID>701 .

Extend the tabelspace and proceed

Thanks ,

Manu

Show replies
Show replies
Former Member
‎02-24-2015 3:55 PM
0 Kudos

There is no PSAPDR3701X tablespace, more over the target version for EHP7 SPS6 is 740. So why am I not being asked to create PSAPDR3740?

former_member182657
Active Contributor
‎02-24-2015 3:32 PM
0 Kudos

I would suggest you to kindly extend the existing table space PSAPDR3701 as per SAP log screen ( from snap shot shared) & continue the phase as well.

Regards,

Gaurav

Show replies
Show replies
former_member182657
Active Contributor
‎02-24-2015 3:26 PM
0 Kudos

Hi Maria,

Could you check with SAP Note  1805195 - Handling and troubleshooting of tablespaces during Upgrades, EhPs and SPs updates

& can follow from same

Consideration about SPAM and SAINT





When applying SPs or installing ABAP Add-Ons via SPAM/SAINT, new tablespaces are not created. The exception comes when you do such operations using SUM is used. On this case, a shadow instance is created with a new tablespace, but without modifying its release. How? Simple: by adding character 'X' on the end of the tablespace.


Example: there is a tablespace named PSAPDEV701, for a NW ABAP-only system, on 701 version, SP stack 10. You apply SP stack 15 using SUM. The tool will create a tablespace named PSAPDEV701X and by the end your SP update, you will have a NW ABAP-only system on 701 level, SPS15 and with tablespaces ending with 'X', like PSAPDEV701X (also PSAPDEVX for the app tables and PSAPDEVUSR1X, PSAPDEVUSR2X... for the customer Z tables).


What happens on the next SPS imlpementation via SUM? The tool will create a new tablespace again, however this time without the 'X' character. Following our example above, if you then go from SPS15 to SPS20 via SUM, by the end of the process you'll have tablespace PSAPDEV701  (and also PSAPDEV for the app tables and PSAPDEVUSR1, PSAPDEVUSR2... for the customer Z tables).

Upgrading a system with tablespaces ending in 'X'



If your system went by a SP implementation via SUM, as exampled above, resulting in tablespaces like PSAPDEV701X, PSAPDEVX, PSAPDEVUSR1X and PSAPDEVUSR2X and now it will be upgraded to a new release, the new tablespaces created will not hold the 'X' character. By the end of the upgrade, the tablespaces will be named as PSAPDEV731, PSAPDEV, PSAPDEVUSR1 and PSAPDEVUSR2.

Regards

Show replies
Show replies
Former Member
‎02-24-2015 3:52 PM
0 Kudos

Not using SPAM or SAINT, Using SUM

former_member182657
Active Contributor
‎02-24-2015 3:20 PM
0 Kudos

If possible can you share DBFPLUSD.RES for analysis.

Show replies
Show replies
manumohandas82
Active Contributor
‎02-24-2015 3:19 PM
0 Kudos

Hi Maria ,

Please read the following Note

1848753 - SUM 1.0: exchange tablespace (e.g. PSAPSR3702X) handling during release upgrade/update



2. The name, content and usage of the so called exchange tablespace depends on the execution of SUM.

We take as an example the release Netweaver 7 EHP 2:

The first time the SUM installs NW 7.0 EHP2 on NW 7.0  it will create the tablespace PSAPSR3702 (or PSAP<SID>702), because of SAP_BASIS will be on 702 level.

   - if SUM will be used a second time to install Support package stacks, SAP_BASIS   level remain on  702, so  the tablespace that will be created will be SAPSR3702X, because SAPSR3702 already exists.

   - if SUM will be used a third time to install Support package stacks, SAP_BASIS level remain on 702, so the tablespace that will be created will be SAPSR3702, because SAPSR3702X already exists.


Thanks ,

Manu

Show replies
Show replies
Former Member
‎02-24-2015 3:38 PM
0 Kudos

Hi Manu,

This is the first time SUM will have been executed on this system. Problem is we are going from 701 to 740, but not getting the 740 tablespace requested at the appropriate check point in the SUM program.

Thanks for the suggestion

former_member182657
Active Contributor
‎02-24-2015 3:14 PM
0 Kudos

Could you share check result logs as well as SAPup.log

Show replies
Show replies
Former Member
‎02-24-2015 3:26 PM
0 Kudos

DBFPLUSD.RES only contains what is on the Check Results snapshot.

Content of the SAPup.log moved to file

SAPup.log.zip
former_member189797
Active Contributor
‎02-24-2015 3:04 PM
0 Kudos

Hi,

Also share the current tablespace layout.

Regards,
Gaurav

Show replies
Show replies
Former Member
‎02-24-2015 3:13 PM
0 Kudos

For added information: the initial system was 6.40 install in 2005, upgraded to 7.01 in 2010.

Checks results:

Tablespace structure

Previous experience has also shown that if it is only a support package stack being applied you still get a request for a new tablespace with and X suffix.

former_member182657
Active Contributor
‎02-24-2015 3:01 PM
0 Kudos

Hi Maria,



checks results want the PSAP<SID>701 tablespace extended to accommodate the shadow instance preprocessing.

Could you share the complete log details or snap shot for this specific phase ?

Regards,

Gaurav

Show replies
Show replies
Former Member
‎02-24-2015 3:06 PM
0 Kudos

Which log would you like?

Ask a Question