cancel
Showing results for 
Search instead for 
Did you mean: 

Error during the SPAM update (version 7.02)

Former Member
0 Kudos

Hello,

After the installation of CRM SAP system (Windows Server + SQL Server), I need to perform an upgrade to this system, but before it, I done a kernel update to the latest version of 721 EXT (patch level 417)... everything is fine but then I try to do a SPAM/SAINT update from the version 7.02/0038 to the latest version (56).

During the SPAM update the system show me the following error during the phase IMPORT_PROPER:

The following details help you to analyze the problem:

    -   Error in phase: IMPORT_PROPER

    -   Reason for error: TP_STEP_FAILURE

    -   Return code: 0008

    -   Error message: OCS Package ALL, tp step "6", return code 0008

I checked some log files, like slog, alog, ulog and others...

- SLOG:

...

ERROR: stopping on error 8 during MOVE NAMETABS

START INFORM SAP-SYSTEM OF C01 Q      20150306111734              DDIC         SAPWD01ERP 20150306111704070  

START tp_getprots          C01 Q      20150306111734              DDIC         SAPWD01ERP 20150306111704070  

STOP  tp_getprots          C01 Q      20150306111735              DDIC         SAPWD01ERP 20150306111704070  

STOP  INFORM SAP-SYSTEM OF C01 Q      20150306111735              DDIC         SAPWD01ERP 20150306111704070  

STOP  imp all              C01   0008 20150306111735              DDIC         SAPWD01ERP 20150306111704070  

START imp all              C01        20150306114827              DDIC         SAPWD01ERP 20150306114826550  

INFO: event SAP_IMPORT_START triggered successfully

START DISTRIBUTION OF DD-O C01 S      20150306114827              DDIC         SAPWD01ERP 20150306114826550  

START tp_getprots          C01 S      20150306114827              DDIC         SAPWD01ERP 20150306114826550  

STOP  tp_getprots          C01 S      20150306114829              DDIC         SAPWD01ERP 20150306114826550  

STOP  DISTRIBUTION OF DD-O C01 S      20150306114829              DDIC         SAPWD01ERP 20150306114826550  

INFO  TBATG CONVERSION OF  C01 N      not needed                  DDIC         SAPWD01ERP 20150306114826550  

START MOVE NAMETABS        C01 6      20150306114829              DDIC         SAPWD01ERP 20150306114826550  

START tp_getprots          C01 6      20150306114829              DDIC         SAPWD01ERP 20150306114826550  

ERROR ALL                  C01 6 0008 20150306114852              DDIC         SAPWD01ERP 20150306114826550  

STOP  tp_getprots          C01 6      20150306114857              DDIC         SAPWD01ERP 20150306114826550  

STOP  MOVE NAMETABS        C01 6      20150306114857              DDIC         SAPWD01ERP 20150306114826550  

ERROR: stopping on error 8 during MOVE NAMETABS

START INFORM SAP-SYSTEM OF C01 Q      20150306114857              DDIC         SAPWD01ERP 20150306114826550  

START tp_getprots          C01 Q      20150306114857              DDIC         SAPWD01ERP 20150306114826550  

STOP  tp_getprots          C01 Q      20150306114858              DDIC         SAPWD01ERP 20150306114826550  

STOP  INFORM SAP-SYSTEM OF C01 Q      20150306114858              DDIC         SAPWD01ERP 20150306114826550  

STOP  imp all              C01   0008 20150306114858              DDIC         SAPWD01ERP 20150306114826550  

- ULOG:

...

APServiceC01 20150306104534 RFC: tp CONNECT C01 pf=\\SAPWD01ERP\sapmnt\trans\bin\TP_DOMAIN_C01.PFL -Dtransdir=\\SAPWD01ERP\sapmnt\trans  (pid=5924)

APServiceC01 20150306104535 RFC: tp IMPORT all C01 pf=\\SAPWD01ERP\sapmnt\trans\bin\TP_DOMAIN_C01.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dmainimp_proc=1 -Dwatchparallelprocesses=yes -Dparallel=0 -Dstopimmediately=1 -Dactivatemerged=yes -Dcheckmasterlang=no tag=spam -Dtransdir=\\SAPWD01ERP\sapmnt\trans  (pid=5924)

APServiceC01 20150306110051 RFC: tp SHOWPARAMS C01 pf=\\SAPWD01ERP\sapmnt\trans\bin\TP_DOMAIN_C01.PFL -Dtransdir=\\SAPWD01ERP\sapmnt\trans  (pid=6072)

APServiceC01 20150306110524 RFC: tp SHOWPARAMS C01 pf=\\SAPWD01ERP\sapmnt\trans\bin\TP_DOMAIN_C01.PFL -Dtransdir=\\SAPWD01ERP\sapmnt\trans  (pid=5464)

APServiceC01 20150306111704 RFC: tp SHOWPARAMS C01 pf=\\SAPWD01ERP\sapmnt\trans\bin\TP_DOMAIN_C01.PFL -Dtransdir=\\SAPWD01ERP\sapmnt\trans  (pid=5184)

APServiceC01 20150306111704 RFC: tp CONNECT C01 pf=\\SAPWD01ERP\sapmnt\trans\bin\TP_DOMAIN_C01.PFL -Dtransdir=\\SAPWD01ERP\sapmnt\trans  (pid=5184)

APServiceC01 20150306111705 RFC: tp IMPORT all C01 pf=\\SAPWD01ERP\sapmnt\trans\bin\TP_DOMAIN_C01.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dmainimp_proc=1 -Dwatchparallelprocesses=yes -Dparallel=0 -Dstopimmediately=1 -Dactivatemerged=yes -Dcheckmasterlang=no tag=spam -Dtransdir=\\SAPWD01ERP\sapmnt\trans  (pid=5184)

APServiceC01 20150306114826 RFC: tp SHOWPARAMS C01 pf=\\SAPWD01ERP\sapmnt\trans\bin\TP_DOMAIN_C01.PFL -Dtransdir=\\SAPWD01ERP\sapmnt\trans  (pid=5992)

APServiceC01 20150306114826 RFC: tp CONNECT C01 pf=\\SAPWD01ERP\sapmnt\trans\bin\TP_DOMAIN_C01.PFL -Dtransdir=\\SAPWD01ERP\sapmnt\trans  (pid=5992)

APServiceC01 20150306114827 RFC: tp IMPORT all C01 pf=\\SAPWD01ERP\sapmnt\trans\bin\TP_DOMAIN_C01.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dmainimp_proc=1 -Dwatchparallelprocesses=yes -Dparallel=0 -Dstopimmediately=1 -Dactivatemerged=yes -Dcheckmasterlang=no tag=spam -Dtransdir=\\SAPWD01ERP\sapmnt\trans  (pid=5992)

- ALOG:

...

ALL              C01.ALL 6 0008 20150305193629          SAP_BASISSAPWD01ERP 20150305193428392  
ALL              C01.ALL Q 0000 20150305193634          SAP_BASISSAPWD01ERP 20150305193428392  
ALL              C01.ALL 6 0008 20150305200102          SAP_BASISSAPWD01ERP 20150305195903343  
ALL              C01.ALL Q 0000 20150305200107          SAP_BASISSAPWD01ERP 20150305195903343  
ALL              C01.ALL 6 0008 20150306004445          DDIC     SAPWD01ERP 20150306004241519  
ALL              C01.ALL Q 0000 20150306004448          DDIC     SAPWD01ERP 20150306004241519  
ALL              C01.ALL 6 0008 20150306093322          DDIC     SAPWD01ERP 20150306093116614  
ALL              C01.ALL Q 0000 20150306093325          DDIC     SAPWD01ERP 20150306093116614  
ALL              C01.ALL 6 0008 20150306100234          SAP_BASISSAPWD01ERP 20150306100033130  
ALL              C01.ALL Q 0000 20150306100238          SAP_BASISSAPWD01ERP 20150306100033130  
SAPKD70256       C01.ALL m 0000 20150306101345 SAPUSER  SAP_BASISSAPWD01ERP               
SAPKD70256       C01.ALL L 0004 20150306101349 SAPUSER  SAP_BASISSAPWD01ERP 20150306101328073  
SAPKD70256       C01.ALL P 0004 20150306101359 SAPUSER  SAP_BASISSAPWD01ERP 20150306101335275  
SAPKD70256       C01.ALL H 0004 20150306101438 SAPUSER  SAP_BASISSAPWD01ERP 20150306101342243  
SAPKD70256       C01.ALL A 0004 20150306101455 SAPUSER  SAP_BASISSAPWD01ERP 20150306101342243  
ALL              C01.ALL S 0008 20150306101500          SAP_BASISSAPWD01ERP 20150306101342243  
ALL              C01.ALL Q 0000 20150306101503          SAP_BASISSAPWD01ERP 20150306101342243  
ALL              C01.ALL S 0000 20150306104527          SAP_BASISSAPWD01ERP 20150306104525524  
ALL              C01.ALL N 0004 20150306104533          SAP_BASISSAPWD01ERP 20150306104525524  
ALL              C01.ALL 6 0008 20150306104610          SAP_BASISSAPWD01ERP 20150306104525524  
ALL              C01.ALL Q 0000 20150306104612          SAP_BASISSAPWD01ERP 20150306104525524  
ALL              C01.ALL S 0000 20150306111704          DDIC     SAPWD01ERP 20150306111704070  
ALL              C01.ALL 6 0008 20150306111730          DDIC     SAPWD01ERP 20150306111704070  
ALL              C01.ALL Q 0000 20150306111734          DDIC     SAPWD01ERP 20150306111704070  
ALL              C01.ALL S 0000 20150306114827          DDIC     SAPWD01ERP 20150306114826550  
ALL              C01.ALL 6 0008 20150306114852          DDIC     SAPWD01ERP 20150306114826550  
ALL              C01.ALL Q 0000 20150306114856          DDIC     SAPWD01ERP 20150306114826550 

Any tip? Can you help me please?

Best regards,

samid raif

Accepted Solutions (0)

Answers (8)

Answers (8)

Reagan
Advisor
Advisor
0 Kudos

Looking at your situation the best would be to raise an OSS message and ask the support to fix it for you, most probably they (or will ask you) will import the patch from the OS level. As this is not a recommended practice and it violates the policy I do not recommend you to do it without checking this with SAP.

Former Member
0 Kudos

Hello Reagan,

Ok Reagan.

But can you confirm please if I´m think well about this situation according to what I said to Gaurav Rana in my previous message?! The reasons, etc for this situation...


Hi Gaurav Rana,

Hum ok! So I believe those inconsistencies are related with SAP BASIS and SAP BW components as we both already discussed, related with the notification that is in sap note 1651862 (Release planning for Microsoft SQL Server 2012) and the information: "SAP EHP2 FOR SAP NETWEAVER 7.0 - SPS 11 (SAP BASIS 11, SAP BW 11)", am I right Gaurav?

If so, I must to ask you one thing, because this isn´t makes any sense for me... if I need to repeat this installation, as you recommended, I believe the same error it will appear again after I finish that new installation because the components version/patch (SAP_BASIS and SAP_BW) level it will be exactly the same, therefore the same problem it will occur when I try to update the support packages (because the SUM it will ask for the update of SPAM and it will try to install it again)!

So... I believe that is not the solution ! I believe I must install this new SAP system (SAP CRM 7.0 EHP1 - NW 7.0 EHP2) first in MS SQL Server 2008 (R2) then I can perform all the components updates (support packages update) and after that I can perform a system copy from the MS SQL Server 2008 (R2) to MS SQL Server 2012! Am I correct?

Best regards,

samid raif

Am I right or not?

Thank you,

samid raif

former_member182657
Active Contributor
0 Kudos

Hi Samid,

Yes you're correct here for the installation of SAP first on MS SQL server 2008 and than perform all SP upgrade.

Even your question is valid regarding the re installation of SAP on SQL 2012 for the re occurance of same issue.Here probably 99 % chances of getting same issue after performing all the activities again.

It would be nice to get an OSS revert on it before performing any procedure,as the issue completely related with the version of DB here.Hope SAP would suggest you better option instead of re installation on lower DB release 2008 R2.

Good luck !!

Former Member
0 Kudos

Ok Gaurav Rana

I understand! Thank you very much for all your help.

Best regards,

samid raif

manumohandas82
Active Contributor
0 Kudos

Hi Armenio ,

In case your plan is to reinstall , try the following

If there is a backup just before you started  SPAM   restore the db ( ie restore the db upto the point in time you upgraded the kernel )

After check for the tables for consistency . If there are issues then believe Re-install should be the best option.

Also Individually dont update the SPAM , make sure that you use SUM tool  and   SPAM will be automatically taken care of in one of the steps.

Thanks,

Manu

former_member182657
Active Contributor
0 Kudos

Hi Samid,

Thanks for sharing the logs,as i only required P150306.C01 log file for further analysis & found


Retcode 1: error in DDL statement for "OCS_CP_E071

Retcode 1: SQL-error "15016-The default 'str_default' does not exist."

Which strengthens my suspect of inconsistencies between database & the ABAP dictionary here,that's why i suggested you earlier SAP Notes to check with any inconsistencies.

Unfortunately you need to repeat the installation to overcome the issue.

Before this i would suggest you to raise an SAP OSS for the issue,as per my opinion last is to repeat the installation.( Completely an issue with DB ).

Regards,

Gaurav

Former Member
0 Kudos

Hi Gaurav Rana,

Hum ok! So I believe those inconsistencies are related with SAP BASIS and SAP BW components as we both already discussed, related with the notification that is in sap note 1651862 (Release planning for Microsoft SQL Server 2012) and the information: "SAP EHP2 FOR SAP NETWEAVER 7.0 - SPS 11 (SAP BASIS 11, SAP BW 11)", am I right Gaurav?

If so, I must to ask you one thing, because this isn´t makes any sense for me... if I need to repeat this installation, as you recommended, I believe the same error it will appear again after I finish that new installation because the components version/patch (SAP_BASIS and SAP_BW) level it will be exactly the same, therefore the same problem it will occur when I try to update the support packages (because the SUM it will ask for the update of SPAM and it will try to install it again)!

So... I believe that is not the solution ! I believe I must install this new SAP system (SAP CRM 7.0 EHP1 - NW 7.0 EHP2) first in MS SQL Server 2008 (R2) then I can perform all the components updates (support packages update) and after that I can perform a system copy from the MS SQL Server 2008 (R2) to MS SQL Server 2012! Am I correct?

Best regards,

samid raif

former_member182657
Active Contributor
0 Kudos

Hi Samid,

Suggested previous notes were to locate any inconsistencies between database & the ABAP dictionary in the system.


Column names in each table must be unique. Column name

> 'DACT_SUBSET' in table 'PATHISTORY' is specified more than

> once.

Yes you're correct about that you're not performing a system copy here, as this is a completely fresh installation & even i checked also ,but the message under SM21 could not be ignored here ( A one suspect not ignorable ).

So to deep analysis i would check the log file from location /usr/sap/trans/log/P<Datum>.<SID>


ERROR: stopping on error 8 during MOVE NAMETABS

If possible kindly share the log file as this file contains complete info of activation of Nametab & could locate the main issues during the phase.

Hope you'll also agree here.

Regards,

Gaurav

Former Member
0 Kudos

Hello Gaurav Rana,

I sent to you attached to this message some log files that I see in /usr/sap/trans/log

(I will post the continuation of this message with more 3 log files due to the restrictions in attach the files here in SCN).

Can you check those log files please?

Best regards,

samid raif

Former Member
0 Kudos

This post is the continuation of my previous message.

A add here more 3 log files from the location /usr/sap/trans/log

Can you check please?

Thank you,

samid raif

former_member182657
Active Contributor
0 Kudos

Hi,


Database error 2705 at EXE

> Column names in each table must be unique. Column name

> 'DACT_SUBSET' in table 'PATHISTORY' is specified more than

> once.

Could you check once with SAP Note  1676665 - Setting up Microsoft SQL Server 2012  & found

something like

Errors occur when using SPAM following a system copy. 

These errors can be one or more of the following:


Tables OCSCCOMPAT and OCSSPCOMPR are inconsistent

  "Error 15016: The default 'str_default' does not exist"  Cannot insert the value NULL into column 'DACT_SUBSET', table '...PATHISTORY'; column does not allow nulls. INSERT fails."

In this case the system copy was made without bringing the source system first up to the required SAP_BASIS SP level required for SQL Server 2012. Do not attempt to repair the system by creating defaults or some other manual action.  The source system must be updated with the required SP level, and the system copy must be repeated!

Here may be any inconsistencies presents in between Database & the dictionary,I suggest you to refer SAP Note   1248769 - Inconsistency between database and ABAP Dictionary      & follow recommendation from the same to process further.

Regards,

Gaurav

Former Member
0 Kudos

Hello Gaurav,

Regarding the sap note 1676665 (Setting up Microsoft SQL Server 2012) I see this:

"In this case the system copy was made without bringing the source system first up to the required SAP_BASIS SP level required for SQL Server 2012"

First of all this was not a system copy, it was a SAP installation that I performed yesterday!

In fact the SAP_BASIS component is the SAP_BASIS 702 (patch level 3).

"...the required SAP_BASIS SP level required for SQL Server 2012".

I checked the sap note 1651862 (Release planning for Microsoft SQL Server 2012) and I read in this sap note this information:

"SAP EHP2 FOR SAP NETWEAVER 7.0 - SPS 11 (SAP BASIS 11, SAP BW 11)"

As I said above the SAP_BASIS and BW components of my SAP system is the version 702 (patch level 3)!

So... I believe that I must have the SAP_BASIS and BW with the patch level 11, am I right?

If so this doesn´t have any sense, because the PAM (service.sap.com/pam) inform that is possible to install this SAP system (CRM 7.0 EHP1 (SAP NW 7.0 EHP2)) in a Windows Server 2008 (R2) on a database MS SQL Server 2012 without problems!

And other thing... how can I perform the update of those components without perform a SPAM/SAINT update before?! For me it has no logic!


Any tips?


Thank you,

samid raif

manumohandas82
Active Contributor
0 Kudos

Hi Samid

"Error 15016: The default 'str_default' does not exist" occurs during SPAM following an installation.

SPAM was applied in error, SUM must be used to apply the support packages to bring the system to a supported level on SQL Server 2014.

If any error occurs during SPAM which was executed following an installation, then the installation must be repeated!

After that SUM must be used to apply the support packages.

This is from SAP Note 1966701 - Setting up Microsoft SQL Server 2014 - Not relevant to you maybe

Believe you need to raise the issue with SAP and keep us updated

Thanks ,

Manu

Sriram2009
Active Contributor
0 Kudos

Hi Samid

Could you check this SAP Note  and implement

1574258 - DROP COLUMN on previously added table column fails

BR

SS

Former Member
0 Kudos

Hello Sriram,

Why you recommended that sap note if I don´t have any error related with the Symptom and/or the issue that is described in that sap note!? Where/Why you concluded that...?!

Thank you,

samid raif

venkata_emandi
Participant
0 Kudos

Hello,

Try deleting the file from /usr/sap/trans/SID/signature.smf and try to update SPAM again.

Make sure TP is latest and running.

Thanks

venkata

Former Member
0 Kudos

Hello venkata emandi,

I don´t have any <SID> directory inside of /usr/sap/trans directory as you can see in the following image... so where is that file signature.smf !?

I´m using the latest TP version available in marketplace (patch level 416) from the kernel version 721 EXT UC 64.

BR,

samid raif

Former Member
0 Kudos

did you "confirm the queue" from the last import ?

Also, you may try to import with old kernel to see if its an issue kernel version.

Regards,

VS

manumohandas82
Active Contributor
0 Kudos

Hi Samid ,

Is there any Dumps in the system  ( ST22 )  or any more clue from SM21

Thanks ,

Manu

Former Member
0 Kudos

Hello,

In ST22 I don´t see any errors... I only see in SM21:

Database error 2705 at EXE

> Column names in each table must be unique. Column name

> 'DACT_SUBSET' in table 'PATHISTORY' is specified more than

> once.

This is a CRM 7.0 EHP1 (SAP NW 7.0 EHP2) in a windows server 2008 (r2) on a database MS SQL Server 2012!

Any tips?

Kind regards,

samid raif