Hello:

My apologies if this is posted in the wrong forum.

A correction stack was generated in Maintenance Planner while verifying a system.  Using SUM to install the correction, it fails in the "Summary and Evaluation of the Update Process".

Show-Summary.LOG

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

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

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

<!--NAME[C:\New_Sum_Car\SUM\sdt\log\SUM\SHOW-SUMMARY_04.LOG]/-->

<!--PATTERN[SHOW-SUMMARY_04.LOG]/-->

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

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

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

Sep 25, 2015 1:49:45 AM [Info  ]: The target products are:

Sep 25, 2015 1:49:45 AM [Info  ]: Runtime and downtime values will be read from C:\New_Sum_Car\SUM\sdt\..\abap\htdoc\UPGANA.XML statistics file.

Sep 25, 2015 1:49:46 AM [Info  ]: Detected minimum downtime is  seconds.

Sep 25, 2015 1:49:46 AM [Info  ]: Start date is 20150925012538

Sep 25, 2015 1:49:46 AM [Info  ]: End date is 20150925012658

Sep 25, 2015 1:49:46 AM [Info  ]: Detected runtime is 80 seconds.

Sep 25, 2015 1:49:46 AM [Error ]: The following problem has occurred during step execution: java.lang.NumberFormatException: For input string: "".

UseCaseExec.log

Thanks for your assistance.

Russ

Hi,

I'm in a process of upgrading ERP 6.0 with EHP7 to SPS 12, i have generated stack file and started the upgrade process.

But I'm stuck at initial extraction phase and SUM prompting for DVD mount points.

i have checked the SAP note 2169284 - ABAP components not calculated for NetWeaver 7.4 SP Stack 08/Business Suite 2013 SP06

The stack file contains <dvd caption="SAP NETWEAVER SR2 DVD" id=" c7a45ee0-c49b-11e3-a755-005056a214d6 " type="upgrade"...

I have provided the Kernel and all dvd's as mount in later try. but, its still asking for dvd mount point.

later with more DVD's

Please find the below log file:-

CRTRACE - location: D:\usr\sap\<SID>\SUM\abap\trc

20150927013344:CDTRACE:1:MID: Reporting mount points.

20150927013344:CDTRACE:3:Sending dispose of old mount path 'F:\51049350_10ker74'.

20150927013344:CDTRACE:3:Sending dispose of old mount path 'F:\Dump\51048524_NW74lang'.

20150927013344:CDTRACE:3:Sending dispose of old mount path 'F:\Dump\NW740SR2upgEXP'.

20150927013344:CDTRACE:3:Sending dispose of old mount path 'F:\Dump\NW740SR2instEXP'.

20150927013344:CDTRACE:3:Sending dispose of old mount path 'F:\Dump\ECCupExp1'.

20150927013344:CDTRACE:3:Sending dispose of old mount path 'F:\Dump\ECCupExp2'.

20150927013344:CDTRACE:3:Sending dispose of old mount path 'F:\Dump\ECCupExp3'.

20150927013344:CDTRACE:2:Reporting mount point 'F:\51049350_10ker74'.

20150927013344:CDTRACE:2:Reporting mount point 'F:\Dump\51048524_NW74lang'.

20150927013344:CDTRACE:2:Reporting mount point 'F:\Dump\NW740SR2upgEXP'.

20150927013344:CDTRACE:2:Reporting mount point 'F:\Dump\NW740SR2instEXP'.

20150927013344:CDTRACE:2:Reporting mount point 'F:\Dump\ECCupExp1'.

20150927013344:CDTRACE:2:Reporting mount point 'F:\Dump\ECCupExp2'.

20150927013344:CDTRACE:2:Reporting mount point 'F:\Dump\ECCupExp3'.

20150927013344:CDTRACE:2:Reporting mount point 'F:\51048902exp'.

20150927013344:CDTRACE:2:Reporting mount point 'F:\51048902_3exp2'.

20150927013346:CDTRACE:1:MID: Requesting data unit locations.

20150927013346:CDTRACE:1:Requesting data unit with attributes 'type=UPGRADE;prodtype=ERP;startrel=any' from MID.

20150927013346:CDTRACE:2:Sending kit id 'c7a45ee0-c49b-11e3-a755-005056a214d6'.

20150927013346:CDTRACE:1:Reading export kits from 'D:\usr\sap\<SID>\SUM\abap\bin\UPGKITS.XML'

MIDService - location D:\usr\sap\<SID>\SUM\sdt\log

Sep 27, 2015 1:33:46 AM [Info]: Updating storage ...

Sep 27, 2015 1:33:46 AM [Info]: Storage updated.

Sep 27, 2015 1:33:46 AM [Info]: Attaching "F:\51048902_3exp2" ...

Sep 27, 2015 1:33:46 AM [Info]: Attached "F:\51048902_3exp2"" with ID 366e04c0-5f5b-11e4-c313-005056a214d6.

Sep 27, 2015 1:33:46 AM [Warning]: inconsistent logical item

Sep 27, 2015 1:33:46 AM [Warning]: inconsistent logical item

Sep 27, 2015 1:33:46 AM [Warning]: inconsistent logical item

Sep 27, 2015 1:33:46 AM [Warning]: inconsistent logical item

Sep 27, 2015 1:33:46 AM [Warning]: inconsistent logical item

Sep 27, 2015 1:33:46 AM [Warning]: inconsistent logical item

Sep 27, 2015 1:33:46 AM [Info]: Updating storage ...

Sep 27, 2015 1:33:46 AM [Info]: Storage updated.

Sep 27, 2015 1:33:46 AM [Info]: Locating Data Unit with Kit ID c7a45ee0-c49b-11e3-a755-005056a214d6 ...

Sep 27, 2015 1:33:46 AM [Info]: Attributes:

Sep 27, 2015 1:33:46 AM [Info]: prodtype=ERP

Sep 27, 2015 1:33:46 AM [Info]: startrel=any

Sep 27, 2015 1:33:46 AM [Info]: type=UPGRADE

AbapUpgradeRequest_<Server>_<Inst.No>_01 - location D:\usr\sap\<SID>\SUM\sdt\log\SUM

Sep 27, 2015 1:31:10 AM [Info  ]: Handling GetCDPath with kitid "c7a45ee0-c49b-11e3-a755-005056a214d6" attributes "type=UPGRADE;prodtype=ERP;startrel=any".

Sep 27, 2015 1:31:10 AM [Info  ]: Found 0 paths matching the request.

Sep 27, 2015 1:33:44 AM [Info  ]: Attaching mount points from tool.

Sep 27, 2015 1:33:44 AM [Info  ]: Tool asked to detach mount point F:\51049350_10ker74

Sep 27, 2015 1:33:44 AM [Info  ]: Tool asked to detach mount point F:\Dump\51048524_NW74lang

Sep 27, 2015 1:33:44 AM [Info  ]: Tool asked to detach mount point F:\Dump\NW740SR2upgEXP

Sep 27, 2015 1:33:44 AM [Info  ]: Tool asked to detach mount point F:\Dump\NW740SR2instEXP

Sep 27, 2015 1:33:44 AM [Info  ]: Tool asked to detach mount point F:\Dump\ECCupExp1

Sep 27, 2015 1:33:45 AM [Info  ]: Tool asked to detach mount point F:\Dump\ECCupExp2

Sep 27, 2015 1:33:45 AM [Info  ]: Tool asked to detach mount point F:\Dump\ECCupExp3

Sep 27, 2015 1:33:45 AM [Info  ]: Tool reported mount point F:\51049350_10ker74

Sep 27, 2015 1:33:45 AM [Info  ]: Tool reported mount point F:\Dump\51048524_NW74lang

Sep 27, 2015 1:33:45 AM [Info  ]: Tool reported mount point F:\Dump\NW740SR2upgEXP

Sep 27, 2015 1:33:45 AM [Info  ]: Tool reported mount point F:\Dump\NW740SR2instEXP

Sep 27, 2015 1:33:45 AM [Info  ]: Tool reported mount point F:\Dump\ECCupExp1

Sep 27, 2015 1:33:46 AM [Info  ]: Tool reported mount point F:\Dump\ECCupExp2

Sep 27, 2015 1:33:46 AM [Info  ]: Tool reported mount point F:\Dump\ECCupExp3

Sep 27, 2015 1:33:46 AM [Info  ]: Tool reported mount point F:\51048902exp

Sep 27, 2015 1:33:46 AM [Info  ]: Tool reported mount point F:\51048902_3exp2

Sep 27, 2015 1:33:46 AM [Info  ]: Handling GetCDPath with kitid "c7a45ee0-c49b-11e3-a755-005056a214d6" attributes "type=UPGRADE;prodtype=ERP;startrel=any".

Sep 27, 2015 1:33:46 AM [Info  ]: Found 0 paths matching the request.

help me with correct DVD and will provide as mount point for SUM during upgrade.

regards

Harika

Hi,

I know that's possible to check transport requests and detect if they contain critical objects, previously mantained in table TMSTCRI. But my question is if it's possible to block requests that contain this objects and prevent an import in the production system, for example.

Regards,

Joan

Edited by: Joan Baptista Altadill Elías on Feb 10, 2009 4:15 PM

I made the configuration in SAP Solution Mangager SP13 for crtical objects in ChaRM (TMWFLOW/CMSCONF). Everything going well with the standard procedure from SAP.
http://help.sap.com/saphelp_sm71_sp01/helpdata/de/4d/6fc4bac469569be10000000a42189b/frameset.htm

But my problem is, everything I found with this tread is between the configuration for the export. In our Landscape I need to check some critical Objects before I transport to PRD (example CI_AUFK). After I had approved the critical Objects trough the tasklist  and imported to QAS I can't this check again before the import to PRD. In my former third party tool was this an easy task, but in ChaRM I don't found this option. Has anyone an idea?

kind regards
Bruno

Noch in Deutsch, ich habe alles so konfiguriert wie beschrieben und es funktioniert auch auf der Ebene der Exportprüfung. Wir haben aber oft kritische Tabellen wie eine CI AUFK wo nur in definierten Wartungsfenstern produktiv gehen dürfen. So wäre es hilfreich dass wir vor dem Import nach P im ChaRM Beleg unter der Transportverwaltung eigentlich noch die definierten kritischen Objekte sehen würden. Dies ist ja aber nicht der Fall, da wir sie ja beim Export und Import in das QAS genehmigt hatten.

Mich würde es interessiern ob jemand die gleiche Problematik hat und wie es mit kleinem Aufwand allenfalls zu lösen wäre?

Besten Dank und Gruss

Bruno

Hi,

i would like to install a SAP  ABAP Application Server ABAP  on SAP HANA Database

They will be Deployed on separated Server  as below :

              ERP app servers on Windows

              HANA database on linux. (  a SAP appliance deliver by a hardware Partner )

During the installation of the ERP , Can the SAP ID  be the same as the HANA database ID ?

Dear Boris,

We have done rerun of export /import and this time all tables are exported and Import also performed Successfully. And in the Package checker log and Objects Checker log every thing is perfect and there is no invalid objects, but we are performing the Table checker option for Target system and we are facing the below error:

Regarding this issue I have raised a thread in NWA forum but no use didn't get any solution and we are struggling for this please check and help us

MIGCHEKER: Table cheker is not working

Dear Experts,

We have migrated our ECC6EHP4 dev system DB size:470 GB from Solaris5.10 with oracle 11.3 to RHEL6.4 with MAXDB 7.8, during migration Import we have sleeted the option interrupt installation before sap instance starts as per recommend for Table checker option and then we have started the Table cheker on target system and we are getting the below error:

./table_checker.sh -unicode -tocDirs /software/PATCHESOLD/ABAP/DATA -user SAPRQA -password sapadmin1234 -url jdbc:sapdb//localhost/RQA

+ /sapmnt/sapjvm_4/bin/java -showversion -cp ./.:./migcheck.jar:/sapdb/RQA/db/runtime/jar/sapdbc.jar com.sap.inst.lib.app.SecureStartup '' com.sap.inst.migcheck.TableChecker -unicode -tocDirs /software/PATCHESOLD/ABAP/DATA -user SAPRQA -password sapadmin1234 -url jdbc:sapdb//localhost/RQA

java version "1.4.2_34"

Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.030)

SAP Java Server VM (build 4.1.030 23.5-b02, May  9 2013 00:04:58 - 41_REL - optU - linux amd64 - 6 - bas2:196055 (mixed mode))

File not found: /sapmnt/MIGCHECK/table_checker_cmd.properties

Required system resources are missing or not available:

  Error loading JDBC driver using 'oracle.jdbc.driver.OracleDriver' class

We have followed the note 2009651 - Table Checker Tool as Part of a System Copy with R3loadand MIGCHEK Guide which is available through migchek.sar file , but we are unable to get the results. and the same I have checked in source system after export it went fine.

when we are checking in target database , it is throwing error as

Required system resources are missing or not available:

  Error loading JDBC driver using 'oracle.jdbc.driver.OracleDriver' class

For the error:Required system resources are missing or not available: we are already in NW7.01(In above note The table check procedure is supported for SAP systems based on SAP NetWeaver 7.0x and higher) so the same is working in Source system and in Target system it is showing the error.we have followed all the prerequisites in the Migration checker guide

For the Error:Error loading JDBC driver using 'oracle.jdbc.driver.OracleDriver' class, here we are trying in target database maxdb and why it is asking the oracle jdbc class

WE have cheeked the table checker option with SUM tool but that will not help us  in our case , source and target systems are not in same endain type.

The Package checker and Object checker went successfully during target import . Please help in this case how can we perform the table checker option.

Regards,

Samba

Hi All,

We are trying to upgrade our system from SAP 4.6c with AFS 3.0B to ECC 6.06 with AFS 6.6. We are struck with an error in the extraction phase (PREP_INIT/ADDON_SPEC1).

The error message refers to OSS Note 817898 and it is already implemented in the system.

The phase is struck saying Upgrade pre-requisites is not met for AFS and the upgrade cannot continue further.

Any suggestions are highly appreciated.

Thanks and Regards

Madhav

We want to apply HRSP 85-91 to our SAP system.  I went through Mopz transaction and it brought up target stack 14 (06/2015) which includes HRSP 86 & 87.  In the 'Select Stack-Dependent Files' I selected ABAP and the 'Add HR Package' tab.  This brought up all the additional HRSP that are available i.e. HRSP 87 to 92.  I selected 87 to 91.  After proceeding it went through to the download basket and I checked and the additional HRSPs were there.  The stack file was generated.

When I use the stack file in SUM SP13 and get to the 'Select Support packages you want to include' screen I don't see the additional HR packages in the Calculated Level column. Normally this is where the additional HRSP number would be and I would tick 'Take over calculated level'.  The only value in this column is for Component ST-A/PI. 

Can you please assist as to why I am not seeing the additional HRSP in the calculated column? 

Many Thanks

Shamshudin

Hello Colleagues,

during Support Package deployment with SUM for an java only system we receive following error in the last step Finalization 5.0:

java.lang.OutOfMemoryError: GC overhead limit exceeded

We aren't not able to identify the root cause for this issue.

Could someone help us here?

Many thanks in advance!

Regards,

Jochen

We want to apply HRSP 85-91 to our SAP system.  I went through Mopz transaction and it brought up target stack 14 (06/2015) which includes HRSP 86 & 87.  In the 'Select Stack-Dependent Files' I selected ABAP and the 'Add HR Package' tab.  This brought up all the additional HRSP that are available i.e. HRSP 87 to 92.  I selected 87 to 91.  After proceeding it went through to the download basket and I checked and the additional HRSPs were there.  The stack file was generated.

When I use the stack file in SUM SP14 Patch level 2 and get to the 'Select Support packages you want to include' screen I don't see the additional HR packages in the Calculated Level column. Normally this is where the additional HRSP number would be and I would tick 'Take over calculated level'.  The only value in this column is for Component ST-A/PI.

Can you please assist as to why I am not seeing the additional HRSP in the calculated column?

Many Thanks

Shamshudin

I am using the SUM latest patch level to do the Kernel Upgrade on a DUAL Stack PI 7.1 system from 7.11 to 7.21 kernel release

SUM is stuck in JAVA_RESTART_SYSTEM_ONLY phase

when I give tp-v in the main node and the app server the kernel release is 7.21 that tells me that the kernel has been upgraded

I am attaching the following log file may be it can be of help and yes by the way this is a production server I have till tonight to get it fixed help is really really appreciated

--------------------------

Jul 27, 2014 2:31:27 AM [Info  ]: Instance has status IN_PROGRESS.
Jul 27, 2014 2:31:27 AM [Info  ]: Instance 22 on host piapp1n1v2 has status IN_PROGRESS
Jul 27, 2014 2:31:32 AM [Info  ]: All retrieved instances : 3
Jul 27, 2014 2:31:32 AM [Info  ]: Correctly detected instance: 22 on host piapp1n1v2
Jul 27, 2014 2:31:32 AM [Info  ]: Correctly detected instance: 21 on host pidbcin2v2
Jul 27, 2014 2:31:32 AM [Info  ]: Correctly detected instance: 22 on host pidbcin2v2
Jul 27, 2014 2:31:32 AM [Info  ]: All retrieved instances from sapcontrol at http://piapp1n1v2:52213:
Jul 27, 2014 2:31:32 AM [Info  ]: Instance: hostName: piapp1n1v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:32 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 21|state: RUNNING|featuresList: GATEWAY|MESSAGESERVER|ENQUE|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:32 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:32 AM [Info  ]: Instance has status IN_PROGRESS.
Jul 27, 2014 2:31:32 AM [Info  ]: Instance 22 on host piapp1n1v2 has status IN_PROGRESS
Jul 27, 2014 2:31:37 AM [Info  ]: All retrieved instances : 3
Jul 27, 2014 2:31:37 AM [Info  ]: Correctly detected instance: 22 on host piapp1n1v2
Jul 27, 2014 2:31:37 AM [Info  ]: Correctly detected instance: 21 on host pidbcin2v2
Jul 27, 2014 2:31:37 AM [Info  ]: Correctly detected instance: 22 on host pidbcin2v2
Jul 27, 2014 2:31:37 AM [Info  ]: All retrieved instances from sapcontrol at http://piapp1n1v2:52213:
Jul 27, 2014 2:31:37 AM [Info  ]: Instance: hostName: piapp1n1v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:37 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 21|state: RUNNING|featuresList: GATEWAY|MESSAGESERVER|ENQUE|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:37 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:37 AM [Info  ]: Instance has status IN_PROGRESS.
Jul 27, 2014 2:31:37 AM [Info  ]: Instance 22 on host piapp1n1v2 has status IN_PROGRESS
Jul 27, 2014 2:31:42 AM [Info  ]: All retrieved instances : 3
Jul 27, 2014 2:31:42 AM [Info  ]: Correctly detected instance: 22 on host piapp1n1v2
Jul 27, 2014 2:31:42 AM [Info  ]: Correctly detected instance: 21 on host pidbcin2v2
Jul 27, 2014 2:31:42 AM [Info  ]: Correctly detected instance: 22 on host pidbcin2v2
Jul 27, 2014 2:31:42 AM [Info  ]: All retrieved instances from sapcontrol at http://piapp1n1v2:52213:
Jul 27, 2014 2:31:42 AM [Info  ]: Instance: hostName: piapp1n1v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:42 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 21|state: RUNNING|featuresList: GATEWAY|MESSAGESERVER|ENQUE|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:42 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:42 AM [Info  ]: Instance has status IN_PROGRESS.
Jul 27, 2014 2:31:42 AM [Info  ]: Instance 22 on host piapp1n1v2 has status IN_PROGRESS
Jul 27, 2014 2:31:47 AM [Info  ]: All retrieved instances : 3
Jul 27, 2014 2:31:47 AM [Info  ]: Correctly detected instance: 22 on host piapp1n1v2
Jul 27, 2014 2:31:47 AM [Info  ]: Correctly detected instance: 21 on host pidbcin2v2
Jul 27, 2014 2:31:47 AM [Info  ]: Correctly detected instance: 22 on host pidbcin2v2
Jul 27, 2014 2:31:47 AM [Info  ]: All retrieved instances from sapcontrol at http://piapp1n1v2:52213:
Jul 27, 2014 2:31:47 AM [Info  ]: Instance: hostName: piapp1n1v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:47 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 21|state: RUNNING|featuresList: GATEWAY|MESSAGESERVER|ENQUE|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:47 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:47 AM [Info  ]: Instance has status IN_PROGRESS.
Jul 27, 2014 2:31:47 AM [Info  ]: Instance 22 on host piapp1n1v2 has status IN_PROGRESS
Jul 27, 2014 2:31:52 AM [Info  ]: All retrieved instances : 3
Jul 27, 2014 2:31:52 AM [Info  ]: Correctly detected instance: 22 on host piapp1n1v2
Jul 27, 2014 2:31:52 AM [Info  ]: Correctly detected instance: 21 on host pidbcin2v2
Jul 27, 2014 2:31:52 AM [Info  ]: Correctly detected instance: 22 on host pidbcin2v2
Jul 27, 2014 2:31:52 AM [Info  ]: All retrieved instances from sapcontrol at http://piapp1n1v2:52213:
Jul 27, 2014 2:31:52 AM [Info  ]: Instance: hostName: piapp1n1v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:52 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 21|state: RUNNING|featuresList: GATEWAY|MESSAGESERVER|ENQUE|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:52 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:52 AM [Info  ]: Instance has status IN_PROGRESS.
Jul 27, 2014 2:31:52 AM [Info  ]: Instance 22 on host piapp1n1v2 has status IN_PROGRESS
Jul 27, 2014 2:31:57 AM [Info  ]: All retrieved instances : 3
Jul 27, 2014 2:31:57 AM [Info  ]: Correctly detected instance: 22 on host piapp1n1v2
Jul 27, 2014 2:31:57 AM [Info  ]: Correctly detected instance: 21 on host pidbcin2v2
Jul 27, 2014 2:31:57 AM [Info  ]: Correctly detected instance: 22 on host pidbcin2v2
Jul 27, 2014 2:31:57 AM [Info  ]: All retrieved instances from sapcontrol at http://piapp1n1v2:52213:
Jul 27, 2014 2:31:57 AM [Info  ]: Instance: hostName: piapp1n1v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:57 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 21|state: RUNNING|featuresList: GATEWAY|MESSAGESERVER|ENQUE|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:57 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:31:57 AM [Info  ]: Instance has status IN_PROGRESS.
Jul 27, 2014 2:31:57 AM [Info  ]: Instance 22 on host piapp1n1v2 has status IN_PROGRESS
Jul 27, 2014 2:32:02 AM [Info  ]: All retrieved instances : 3
Jul 27, 2014 2:32:02 AM [Info  ]: Correctly detected instance: 22 on host piapp1n1v2
Jul 27, 2014 2:32:02 AM [Info  ]: Correctly detected instance: 21 on host pidbcin2v2
Jul 27, 2014 2:32:02 AM [Info  ]: Correctly detected instance: 22 on host pidbcin2v2
Jul 27, 2014 2:32:02 AM [Info  ]: All retrieved instances from sapcontrol at http://piapp1n1v2:52213:
Jul 27, 2014 2:32:02 AM [Info  ]: Instance: hostName: piapp1n1v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:02 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 21|state: RUNNING|featuresList: GATEWAY|MESSAGESERVER|ENQUE|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:02 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:02 AM [Info  ]: Instance has status IN_PROGRESS.
Jul 27, 2014 2:32:02 AM [Info  ]: Instance 22 on host piapp1n1v2 has status IN_PROGRESS
Jul 27, 2014 2:32:07 AM [Info  ]: All retrieved instances : 3
Jul 27, 2014 2:32:07 AM [Info  ]: Correctly detected instance: 22 on host piapp1n1v2
Jul 27, 2014 2:32:07 AM [Info  ]: Correctly detected instance: 21 on host pidbcin2v2
Jul 27, 2014 2:32:07 AM [Info  ]: Correctly detected instance: 22 on host pidbcin2v2
Jul 27, 2014 2:32:07 AM [Info  ]: All retrieved instances from sapcontrol at http://piapp1n1v2:52213:
Jul 27, 2014 2:32:07 AM [Info  ]: Instance: hostName: piapp1n1v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:07 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 21|state: RUNNING|featuresList: GATEWAY|MESSAGESERVER|ENQUE|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:07 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:07 AM [Info  ]: Instance has status IN_PROGRESS.
Jul 27, 2014 2:32:07 AM [Info  ]: Instance 22 on host piapp1n1v2 has status IN_PROGRESS
Jul 27, 2014 2:32:12 AM [Info  ]: All retrieved instances : 3
Jul 27, 2014 2:32:12 AM [Info  ]: Correctly detected instance: 22 on host piapp1n1v2
Jul 27, 2014 2:32:12 AM [Info  ]: Correctly detected instance: 21 on host pidbcin2v2
Jul 27, 2014 2:32:12 AM [Info  ]: Correctly detected instance: 22 on host pidbcin2v2
Jul 27, 2014 2:32:12 AM [Info  ]: All retrieved instances from sapcontrol at http://piapp1n1v2:52213:
Jul 27, 2014 2:32:12 AM [Info  ]: Instance: hostName: piapp1n1v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:12 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 21|state: RUNNING|featuresList: GATEWAY|MESSAGESERVER|ENQUE|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:12 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:12 AM [Info  ]: Instance has status IN_PROGRESS.
Jul 27, 2014 2:32:12 AM [Info  ]: Instance 22 on host piapp1n1v2 has status IN_PROGRESS
Jul 27, 2014 2:32:17 AM [Info  ]: All retrieved instances : 3
Jul 27, 2014 2:32:17 AM [Info  ]: Correctly detected instance: 22 on host piapp1n1v2
Jul 27, 2014 2:32:17 AM [Info  ]: Correctly detected instance: 21 on host pidbcin2v2
Jul 27, 2014 2:32:17 AM [Info  ]: Correctly detected instance: 22 on host pidbcin2v2
Jul 27, 2014 2:32:17 AM [Info  ]: All retrieved instances from sapcontrol at http://piapp1n1v2:52213:
Jul 27, 2014 2:32:17 AM [Info  ]: Instance: hostName: piapp1n1v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:17 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 21|state: RUNNING|featuresList: GATEWAY|MESSAGESERVER|ENQUE|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:17 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:17 AM [Info  ]: Instance has status IN_PROGRESS.
Jul 27, 2014 2:32:17 AM [Info  ]: Instance 22 on host piapp1n1v2 has status IN_PROGRESS
Jul 27, 2014 2:32:22 AM [Info  ]: All retrieved instances : 3
Jul 27, 2014 2:32:22 AM [Info  ]: Correctly detected instance: 22 on host piapp1n1v2
Jul 27, 2014 2:32:22 AM [Info  ]: Correctly detected instance: 21 on host pidbcin2v2
Jul 27, 2014 2:32:22 AM [Info  ]: Correctly detected instance: 22 on host pidbcin2v2
Jul 27, 2014 2:32:22 AM [Info  ]: All retrieved instances from sapcontrol at http://piapp1n1v2:52213:
Jul 27, 2014 2:32:22 AM [Info  ]: Instance: hostName: piapp1n1v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:22 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 21|state: RUNNING|featuresList: GATEWAY|MESSAGESERVER|ENQUE|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:22 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:22 AM [Info  ]: Instance has status IN_PROGRESS.
Jul 27, 2014 2:32:22 AM [Info  ]: Instance 22 on host piapp1n1v2 has status IN_PROGRESS
Jul 27, 2014 2:32:27 AM [Info  ]: All retrieved instances : 3
Jul 27, 2014 2:32:27 AM [Info  ]: Correctly detected instance: 22 on host piapp1n1v2
Jul 27, 2014 2:32:27 AM [Info  ]: Correctly detected instance: 21 on host pidbcin2v2
Jul 27, 2014 2:32:27 AM [Info  ]: Correctly detected instance: 22 on host pidbcin2v2
Jul 27, 2014 2:32:27 AM [Info  ]: All retrieved instances from sapcontrol at http://piapp1n1v2:52213:
Jul 27, 2014 2:32:27 AM [Info  ]: Instance: hostName: piapp1n1v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:27 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 21|state: RUNNING|featuresList: GATEWAY|MESSAGESERVER|ENQUE|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:27 AM [Info  ]: Instance: hostName: pidbcin2v2|instanceNumber: 22|state: IN_PROGRESS|featuresList: ABAP|J2EE|GATEWAY|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

Jul 27, 2014 2:32:27 AM [Info  ]: Instance has status IN_PROGRESS.
Jul 27, 2014 2:32:27 AM [Info  ]: The status of instance 22 on host piapp1n1v2 is IN_PROGRESS.
Jul 27, 2014 2:32:27 AM [Error ]: Start of instances exceeded the timeout of 7200s.
Jul 27, 2014 2:32:27 AM [Warning]: The instance could not be started. Will retry after a pause of 15 seconds.
Jul 27, 2014 2:32:42 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Could not start SAP instance with number 22.
The instance with number 22 on host piapp1n1v2 could not be started within the specified timeout.

--------------------

Thanks

APS

Error-Message from SUM-Tool:

The executable R3trans in /usr/sap/EXE/SUM/abap/exe is too old.

It needs a release date of 19.03.13 or later.

what is this -

the download of the SUM is just new (from June 2013) ?

Hi All,

We are in the process updating our system from SAP ECC 6.0 with EHP6 / AFS 6.6 to ECC 6.0 with EHP7 / AFS 6.7.

The sum tool stops at MAIN_NEWBAS/TABIM_UPG with the following error

MAIN IMPORT ERRORS and RETURN CODE in SAPI-607BGINP3A.CSM

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

4 ETW000  [     dev trc,00000]  SELECT CASE WHEN EXISTS(SELECT TOP 1 1 FROM "T439I" ) THEN 1 ELSE 0 END

4 ETW000                        /* R3::

4 ETW000  [     dev trc,00000]  0 T:T439I */

4 ETW000  [     dev trc,00000]  dbdsmss: DBSL103 SQL208

4 ETW000  [     dev trc,00000]  Invalid object name 'T439I'.

2EETW000 unsuccessful statement: EXEC SQL: SELECT CASE WHEN EXISTS(SELECT TOP 1 1 FROM "T439I" ) THEN 1 ELSE 0 END

1AETW000 dsql_open returned with unexpected error code 512

2EETW000 Please contact the SAP support.

1 ETP111 exit code           : "16"

As table T439I is a pool table and is not available at MS SQL Server as well..

We have upgraded R3trans, TP, dbmsslib.dll and also tried with different support package levels of the target version.

Any clue / help to resolve this will be highly appreciated.

Thanks and Regards

Madhav

Hello,

  I'm importing several Support Packages to update my Solution Manager 7.1 System up to Solution Tools ST SP14 (SAPKITL714). I used the SPAM Queue Calculator to add all the required Support Packages and extra Components.

Unfortunatelly the process stopped in the IMPORT_PROPER phase due to missing Tables.

- Error in phase:        IMPORT_PROPER

- Reason for error:    TP_STEP_FAILURE

- Return code:           0008

- Error message:       OCS Package SAPKITL714, tp step "I", return code  0008

Checking the Log FileSAPIITL714.<SID> located in /usr/sap/trans/log :

Details of the Log (too long to attach it):

…

3 ETW674Xstart import of "R3TRTABU/UI5/TREP_FILES" ...

3WETW109 table "/UI5/TREP_FILES" does not exist in nametab.

4 ETW000 no entries for /UI5/TREP_FILES will be imported in this step.

2EETW109 table "/UI5/TREP_FILES" does not exist in nametab.

3 ETW676 end import of "R3TRTABU/UI5/TREP_FILES" (warnings).

…

…

3 ETW674Xstart import of "R3TRTABU/UI5/TREP_TEXT" ...

3WETW109 table "/UI5/TREP_TEXT" does not exist in nametab.

4 ETW000 no entries for /UI5/TREP_TEXT will be imported in this step.

2EETW109 table "/UI5/TREP_TEXT" does not exist in nametab.

2EETW109 table "/UI5/TREP_TEXT" does not exist in nametab.

…

…

3 ETW674Xstart import of "R3TRTABU/UI5/TREP_TEXT_T" ...

3WETW109 table "/UI5/TREP_TEXT_T" does not exist in nametab.

4 ETW000 no entries for /UI5/TREP_TEXT_T will be imported in this step.

2EETW109 table "/UI5/TREP_TEXT_T" does not exist in nametab.

2EETW109 table "/UI5/TREP_TEXT_T" does not exist in nametab.

…

  I've found out that SAP Note 2223723 states that the SPAM Check Component Software have an error for the

Component UISAPUI5 (It should be >= SP12 for SolMan 7.1 ST SP14).   The missing tables seems to belong to the UISAPUI5 component.

  The solution in this SAP Note is to modify the Check Component Software to force to check the UISAPUI5 Component to be greather than SP 12 BEFORE applying the Support Package 7.1 SP14, but this is too late because we already have the problem in the Import_Proper phase.

What can we do to fix the error?

Should we apply SAP Note 1022755 to force the Import phase to skip the Check up for these Tables during the IMPORT_PROPER phase? Won't this be a problem later for the UISAPUI5 Component and Tables that weren't updated by this Support Package?

Should we do a system recover and start over the process?

Thanks a lot for your help!

Miguel Vizcaino
 

Hi guys

While performing a SAP BW System Upgrade and Database Migration to HANA using DMO for SUM SP14, Im facing the following issue.

It seems folder SUM\abap\exe_2nd was not created, therefore R3trans could not be found

CURRENTPHASE PREP_CONFIGURATION/SUBMOD_MIG_CHKCONNECT/DBCONNCHK_2ND

...started at 20151027121353

..finished at 20151027121353 with status ABORTED.

# Error message set: 'Executable 'R3trans' in 'K:\SUM\abap\exe_2nd' does not exist'

...begin dialog at 20151027121356.

In the XML file both kernels were included (HDB and SQL)

-<software-component>

<caption>SAP KERNEL 7.42 64-BIT UNICODE</caption>

<ppms-number>67837800100200025031</ppms-number>

<runtime-type>OS</runtime-type>

<name>KRNL64UC</name>

<version>7.42</version>

<vendor>sap.com</vendor>

-<support-package>

<caption>SP200 for SAP KERNEL 7.42 64-BIT UNICODE</caption>

<name>SP200</name>

<vendor>sap.com</vendor>

<ppms-number>73554900101100010982</ppms-number>

<sp-level>200</sp-level>

<patch-level>200</patch-level>

-<archives>

-<os-set os="LINUX_X64">

-<db-set db="DBINDEP">

<archive-name os="LINUX_X64" patch-level="200" db="DBINDEP">SAPEXE_200-20012215.SAR</archive-name>

</db-set>

-<db-set db="HDB">

<archive-name os="LINUX_X64" patch-level="200" db="HDB">SAPEXEDB_200-20012231.SAR</archive-name>

</db-set>

</os-set>

-<os-set os="NT_X64">

-<db-set db="DBINDEP">

<archive-name os="NT_X64" patch-level="200" db="DBINDEP">SAPEXE_200-20012222.SAR</archive-name>

</db-set>

-<db-set db="MSS">

<archive-name os="NT_X64" patch-level="200" db="MSS">SAPEXEDB_200-20012221.SAR</archive-name>

</db-set>

</os-set>

</archives>

</support-package>

</software-component>

-<software-component>

Anyone does not if this is a SUM error or understand why the exe_2nd folder was not created?

Best

Martin

Hi Guys,

I have a issue migration key.

My goal:

Windows ERP 6 EHP7 with MSSQL to Linux HANA migration. So I generated the key in SMP, but its not take the key.

Please suggest me to resolve the issue.

Thanks

Srini T

Dear HANA Experts, We have BI production server with SID-BIP & BI Quality server with SID-BIQ. HANA databse's SID for BIP system is HAP HANA databse's SID for BIQsystem is HAQ HAP's hostname - ajihanaprd HAQ's hostname - ajihanatst HAP instance number is 00 HAQ instance number is 01 We did HANA DB recovery : We restored HAP's backup on HAQ Recovery was successful without any issue. As per standard step, Now I need to run following command. hdbuserstore -u adm set default : I have tried following combination of above commands, but nothing worked (R3trans -d gives error 0012). Since its bit urgent, so it would be great if you can help me to fix this issue as earliest as possible. On Windows Application Server Host Logged in with user biqadm cd usr/sap/BIQ/hdbclient And executed following commands. Command using HAQ & SYSTEM hdbuserstore -u HAQadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SYSTEM HIThana4us hdbuserstore -u SAPServiceHAQ SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SYSTEM HIThana4us Command using HAQ & system hdbuserstore -u HAQadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 system HIThana4us hdbuserstore -u SAPServiceHAQ SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 system HIThana4us Command using HAQ & SAPBIP hdbuserstore -u HAQadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SAPBIP ajinomoto hdbuserstore -u SAPServiceHAQ SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SAPBIP ajinomoto Command using HAQ & sapbip hdbuserstore -u HAQadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 sapbip ajinomoto hdbuserstore -u SAPServiceHAQ SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 sapbip ajinomoto Command using haq & SYSTEM hdbuserstore -u haqadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SYSTEM HIThana4us hdbuserstore -u SAPServicehaq SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SYSTEM HIThana4us Command using haq & system hdbuserstore -u haqadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 system HIThana4us hdbuserstore -u SAPServicehaq SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 system HIThana4us Command using haq & SAPBIP hdbuserstore -u haqadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SAPBIP ajinomoto hdbuserstore -u SAPServicehaq SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SAPBIP ajinomoto Command using haq & sapbip hdbuserstore -u haqadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 sapbip ajinomoto hdbuserstore -u SAPServicehaq SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 sapbip ajinomoto Command using BIQ & SYSTEM hdbuserstore -u BIQadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SYSTEM HIThana4us hdbuserstore -u SAPServiceBIQ SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SYSTEM HIThana4us Command using BIQ & system hdbuserstore -u BIQadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 system HIThana4us hdbuserstore -u SAPServiceBIQ SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 system HIThana4us Command using BIQ & SAPBIP hdbuserstore -u BIQadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SAPBIP ajinomoto hdbuserstore -u SAPServiceBIQ SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SAPBIP ajinomoto Command using BIQ & sapbip hdbuserstore -u BIQadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 sapbip ajinomoto hdbuserstore -u SAPServiceBIQ SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 sapbip ajinomoto Command using biq & SYSTEM hdbuserstore -u biqadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SYSTEM HIThana4us hdbuserstore -u SAPServicebiq SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SYSTEM HIThana4us Command using biq & system hdbuserstore -u biqadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 system HIThana4us hdbuserstore -u SAPServicebiq SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 system HIThana4us Command using biq & SAPBIP hdbuserstore -u biqadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SAPBIP ajinomoto hdbuserstore -u SAPServicebiq SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 SAPBIP ajinomoto Command using biq & sapbip hdbuserstore -u biqadm SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 sapbip ajinomoto hdbuserstore -u SAPServicebiq SET DEFAULT ajihanatst.sapeuroamerica.ajinomoto.com:30015 sapbip ajinomoto Regards, Sunil Maurya

Hi guys

While running DMO for SUM Im facing the following error.

Job completes successfully after 3 seconds, but SUM shows it as an error.

SUM version is SP14

Any idea what does mean that message?

PREP_SETUP/RUN_GENPUTTBSHD

1EETQ399 Last error code set is: No new lines found in logfiles.

1 ETQ201 Entering upgrade-phase "PREP_SETUP/RUN_GENPUTTBSHD" ("20151028020319")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '00', GwService = 'sapgw00' Client = '000'

4 ETQ399 Environment variables:

4 ETQ399   dbs_mss_schema=bwx

1 ETQ206 Executing pre-phase DB specific actions 0/1.

1 ETQ200 Executing actual phase 'PREP_SETUP/RUN_GENPUTTBSHD'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[0] = 'RS_GENERATE_PUTTB_SHD'

2 ETQ399 Arg[1] = 'SAP_TMPLOG'

2 ETQ399 Arg[2] = ''

2 ETQ399 Arg[3] = 'RS_GENERATE_PUTTB_SHD\.$(SAPSID)'

2 ETQ399 Arg[4] = '5'

2 ETQ399 Arg[5] = 'PUTTB_SHD generation'

1 ETQ399 Using error summary log 'GENPUTTBSHD.ELG'.

1 ETQ399 Expanded phase arguments:

2 ETQ399 Arg[3] = 'RS_GENERATE_PUTTB_SHD\.BWX'

4 ETQ265 Starting report "RS_GENERATE_PUTTB_SHD" with variant "SAP_TMPLOG" in batch

1 ETQ359 RFC Login to: System="BWX", AsHost="UYCLS143" Nr="00", GwHost="UYCLS143", GwService="sapgw00"

2 ETQ232 RFC Login succeeded

4 ETQ010 Date & Time: 20151028020319 

1 ETQ233 Calling function module "SUBST_START_REPORT_IN_BATCH" by RFC

2 ETQ373 parameter "IV_ABORT_ON_ERROR" = ""

2 ETQ373 parameter "IV_AUTHCKNAM" = "DDIC"

2 ETQ373 parameter "IV_BATCHHOST" = "UYCLS143"

2 ETQ373 parameter "IV_JOBNAME" = "RS_GENERATE_PUTTB_SHD"

2 ETQ373 parameter "IV_REPNAME" = "RS_GENERATE_PUTTB_SHD"

2 ETQ373 parameter "IV_SCHEDEVER" = " "

2 ETQ373 parameter "IV_VARIANTTEXT" = "Gen. PUTTB_SHD from PUTTBX"

2 ETQ373 parameter "IV_VARNAME" = "SAP_TMPLOG"

2 ETQ373 parameter "IV_LANGUAGE" = "E"

2 ETQ399 Table TT_REPORTPARAM (#1):

3 ETQ399 "LOG_DIR","P","","","tmp",""

2 ETQ373 parameter "IV_BATCHINSTANCE" = ""

1 ETQ234 Call of function module "SUBST_START_REPORT_IN_BATCH" by RFC succeeded

4 ETQ010 Date & Time: 20151028020319 

2 ETQ373 parameter "EV_JOBCOUNT" = "05031900"

2 ETQ374 parameter "EV_STARTRC" = "0"

2 ETQ374 parameter "EV_VARIWRC" = "0"

4 ETQ311 Batch job "RS_GENERATE_PUTTB_SHD" with job count "05031900" scheduled

2 ETQ399 20151028020319: Job RS_GENERATE_PUTTB_SHD jobcount 05031900 still running...

1 ETQ359 RFC Login to: System="BWX", AsHost="UYCLS143" Nr="00", GwHost="UYCLS143", GwService="sapgw00"

2 ETQ232 RFC Login succeeded

4 ETQ010 Date & Time: 20151028020324 

1 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC

2 ETQ373 parameter "JOBNAME" = "RS_GENERATE_PUTTB_SHD"

2 ETQ373 parameter "JOBCOUNT" = "05031900"

2 ETQ373 parameter "IV_VERIFY" = " "

1 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded

4 ETQ010 Date & Time: 20151028020324 

2 ETQ373 parameter "JOBSTATUS" = "F"

2 ETQ374 parameter "RC_CHECK" = "0"

2 ETQ373 parameter "JOBENDDATE" = "20151028"

2 ETQ373 parameter "JOBENDTIME" = "050322"

4 ETQ263 Batchjob "RS_GENERATE_PUTTB_SHD" finished successfully

2 ETQ399 Phase RUN_GENPUTTBSHD is now finalizing...

2 ETQ399 Phase RUN_GENPUTTBSHD: Finalize OK

4 ETQ010 Date & Time: 20151028020325 

1EETQ399 Last error code set is: No new lines found in logfiles.

1EETQ203 Upgrade phase "RUN_GENPUTTBSHD" aborted with errors ("20151028020325")

Hi all,

I thought I'd download the latest version of SUM as recommended by SAP to upgrade our Solman system from 4 to 7.1.  However when it gets to the Extraction phase 5.2 it complains about missing file CPRXRPM400.SAR even though that isn't in the Stack XML file.  When I give it a file of that name from K-40001INCPRXRPM.SAR it then asks for SAP_BASIS701.SAR!

What gives?  It's almost like it's trying to do a different upgrade.  Step 4 Confirm Target is correctly showing New Product Version(s) as SAP SOLUTION MANAGER 7.1 (ABAP) SAP SOLUTION MANAGER 7.1 (JAVA).

I'm at a loss as to what's going on here and might end up going back to the previous SP13 which didn't do this.

Any ideas?

Thanks

Craig

UPDATE

I found the issue, turns out that in the log ASKDOWNLOAD.LOG just before it errored about the file being missing, it referred to an old stack xml file from 2013.   Once I renames all old stack xml files to .old and continued it resolved the problem.  Hope this helps anyone also experiencing this issue.  Seems to be a bug if you ask me.

Hi experts,

We are planning to migraton oracle to hana s4.

Currently we have ecc6.0 ehp7 with Oracle 11.2.0.3 on linux 6.5.

Please help me how to proceed.

I already checked some documents on scn and need dmo ( sum) tool.

Regards,

Vivek