Issue in Phase Prep_Integration/TOOLVERSION_EXE during EHP4
Hi,
We are having ECC 6.0. Currently i am in the process of trying to apply a technical usage (HCM) from Enhancement Package 4 support stack 3 for which i am using SAPehpi installer. During the Configuration Step in the phase Prep_Integration/TOOLVERSION_EXE it writes the following onto CHECKS.LOG file :
%BEGIN PREP_INTEGRATION/TOOLVERSION_EXE TEXT
ERROR: There are dependencies between packages
included into the procedure and the target
release kernel
The release of tool disp+work needs to be at
least 701.
Please retrieve the new tools and put the archives
to the download directory. This is described in the
documentation chapter "Preparation" section
"Filling the Download Directory".
Due to which at the end of configuration step after finishing all phases it comes out with the above error. I downloaded the latest Kernel as well as tried downloading the latest dw.sar file to 701 version unicode and copied over to download directory but still same error keeps coming.
Anyone has encountered this error before and if so kindly help me on this.
Thanks,
Murali.
This is what in my case:
ETQ399 Determining all tool versions in directory '/usr/sap/software/EHP4/EHPI/abap/exe':
4 ETQ399 2009/06/17 14:53:43: put_execute: (disp+work) forkpid:950412
2 ETQ399 TOOL-VERSION 'disp+work': EXE_DISPWORK_REL = '700'
2 ETQ399 TOOL-VERSION 'disp+work': EXE_DISPWORK_64BIT = 'ON'
2 ETQ399 TOOL-VERSION 'disp+work': EXE_DISPWORK_UNICODE = 'ON'
2 ETQ399 TOOL-VERSION 'disp+work': EXE_DISPWORK_DATE = 'Nov 18 2008 21:27:59'
2 ETQ399 TOOL-VERSION 'disp+work': EXE_DISPWORK_PATCHNUM = '185'
4 ETQ399 2009/06/17 14:53:43: put_execute: (tp) forkpid:950414
2 ETQ399 TOOL-VERSION 'tp': EXE_TP_VERSION = '372.04.40'
2 ETQ399 TOOL-VERSION 'tp': EXE_TP_REL = '700'
2 ETQ399 TOOL-VERSION 'tp': EXE_TP_PATCHNUM = '179'
4 ETQ399 2009/06/17 14:53:43: put_execute: (R3trans) forkpid:950416
2 ETQ399 TOOL-VERSION 'R3trans': EXE_R3TRANS_VERSION = '6.14'
2 ETQ399 TOOL-VERSION 'R3trans': EXE_R3TRANS_REL = '701'
2 ETQ399 TOOL-VERSION 'R3trans': EXE_R3TRANS_DATE = '20.04.09'
2 ETQ399 TOOL-VERSION 'R3trans': EXE_R3TRANS_PATCHNUM = '44'
4 ETQ399 2009/06/17 14:53:44: put_execute: (R3load) forkpid:950418
2 ETQ399 TOOL-VERSION 'R3load': EXE_R3LOAD_REL = '7.00'
2 ETQ399 TOOL-VERSION 'R3load': EXE_R3LOAD_VERSION = '1.4 [UNICODE]'
1 ETQ399 Determining all tool versions in directory '/usr/sap/software/EHP4/EHPI/abap/exenew':
4 ETQ399 2009/06/17 14:53:44: put_execute: (disp+work) forkpid:950420
4 ETQ399 2009/06/17 14:53:44: put_execute: (tp) forkpid:950422
2 ETQ399 TOOL-VERSION 'tp': NEW_TP_VERSION = '372.04.57'
2 ETQ399 TOOL-VERSION 'tp': NEW_TP_REL = '701'
2 ETQ399 TOOL-VERSION 'tp': NEW_TP_PATCHNUM = '37'
4 ETQ399 2009/06/17 14:53:44: put_execute: (R3trans) forkpid:950424
2 ETQ399 TOOL-VERSION 'R3trans': NEW_R3TRANS_VERSION = '6.14'
2 ETQ399 TOOL-VERSION 'R3trans': NEW_R3TRANS_REL = '701'
2 ETQ399 TOOL-VERSION 'R3trans': NEW_R3TRANS_DATE = '20.04.09'
2 ETQ399 TOOL-VERSION 'R3trans': NEW_R3TRANS_PATCHNUM = '44'
4 ETQ399 2009/06/17 14:53:44: put_execute: (R3load) forkpid:950426
2 ETQ399 TOOL-VERSION 'R3load': NEW_R3LOAD_REL = '7.01'
2 ETQ399 TOOL-VERSION 'R3load': NEW_R3LOAD_VERSION = '1.4 [UNICODE]'
2 ETQ399 # Map request variable 'EXE_R3TRANS_REL' to 'NEW_R3TRANS_REL'
2 ETQ399 # Map request variable 'EXE_R3TRANS_DATE' to 'NEW_R3TRANS_DATE'
1 ETQ399 Comparing DATE '05.03.09' '20.04.09' -> -115
2 ETQ399 # Map request variable 'DISPWORK_REL' to 'NEW_DISPWORK_REL'
1 ETQ207 Executing post-phase DB specific actions.
1 ETQ207 Executing post-phase OS specific actions.
4 ETQ010 Date & Time: 20090617145345
Based on the above you can see it is checking for disp+work from exe dir which is 700 and leter it is mapping 'DISPWORK_REL' to 'NEW_DISPWORK_REL' which is what my issue.....
If i extract the 701 dw.sar manually on the exe directory and run the installation the following is the output:
ETQ399 Determining all tool versions in directory '/usr/sap/software/EHP4/EHPI/abap/exe':
4 ETQ399 2009/06/17 16:13:10: put_execute: (disp+work) forkpid:3190962
4 ETQ399 2009/06/17 16:13:10: put_execute: (tp) forkpid:3190964
2 ETQ399 TOOL-VERSION 'tp': EXE_TP_VERSION = '372.04.40'
2 ETQ399 TOOL-VERSION 'tp': EXE_TP_REL = '700'
2 ETQ399 TOOL-VERSION 'tp': EXE_TP_PATCHNUM = '179'
4 ETQ399 2009/06/17 16:13:11: put_execute: (R3trans) forkpid:3190966
2 ETQ399 TOOL-VERSION 'R3trans': EXE_R3TRANS_VERSION = '6.14'
2 ETQ399 TOOL-VERSION 'R3trans': EXE_R3TRANS_REL = '701'
2 ETQ399 TOOL-VERSION 'R3trans': EXE_R3TRANS_DATE = '20.04.09'
2 ETQ399 TOOL-VERSION 'R3trans': EXE_R3TRANS_PATCHNUM = '44'
4 ETQ399 2009/06/17 16:13:11: put_execute: (R3load) forkpid:3190968
2 ETQ399 TOOL-VERSION 'R3load': EXE_R3LOAD_REL = '7.00'
2 ETQ399 TOOL-VERSION 'R3load': EXE_R3LOAD_VERSION = '1.4 [UNICODE]'
1 ETQ399 Determining all tool versions in directory '/usr/sap/software/EHP4/EHPI/abap/exenew':
4 ETQ399 2009/06/17 16:13:11: put_execute: (disp+work) forkpid:3190970
4 ETQ399 2009/06/17 16:13:11: put_execute: (tp) forkpid:1220664
2 ETQ399 TOOL-VERSION 'tp': NEW_TP_VERSION = '372.04.57'
2 ETQ399 TOOL-VERSION 'tp': NEW_TP_REL = '701'
2 ETQ399 TOOL-VERSION 'tp': NEW_TP_PATCHNUM = '37'
4 ETQ399 2009/06/17 16:13:12: put_execute: (R3trans) forkpid:1220666
2 ETQ399 TOOL-VERSION 'R3trans': NEW_R3TRANS_VERSION = '6.14'
2 ETQ399 TOOL-VERSION 'R3trans': NEW_R3TRANS_REL = '701'
2 ETQ399 TOOL-VERSION 'R3trans': NEW_R3TRANS_DATE = '20.04.09'
2 ETQ399 TOOL-VERSION 'R3trans': NEW_R3TRANS_PATCHNUM = '44'
4 ETQ399 2009/06/17 16:13:12: put_execute: (R3load) forkpid:1220668
2 ETQ399 TOOL-VERSION 'R3load': NEW_R3LOAD_REL = '7.01'
2 ETQ399 TOOL-VERSION 'R3load': NEW_R3LOAD_VERSION = '1.4 [UNICODE]'
2 ETQ399 # Map request variable 'EXE_R3TRANS_REL' to 'NEW_R3TRANS_REL'
2 ETQ399 # Map request variable 'EXE_R3TRANS_DATE' to 'NEW_R3TRANS_DATE'
1 ETQ399 Comparing DATE '05.03.09' '20.04.09' -> -115
2 ETQ399 # Map request variable 'DISPWORK_REL' to 'NEW_DISPWORK_REL'
1 ETQ207 Executing post-phase DB specific actions.
1 ETQ207 Executing post-phase OS specific actions.
Here you can see it is not even showing any version for disp+work from exe directory.
Thanks,
Murali.
Similar Messages
-
Error in CONFLICT_CHECK during EHP4 Installation
I have installed a new ERP system from the installation DVDs for ERP 6.0 EHP4 Ready. As part of the post-installations I am installing EHP4.
I have installed the newest SPAM 7.01/39 (and Basis-SPs SAPKB70104-SAPKB70106, ...)
I generated a stackfile in solman with target stack and added only Patch 21 for HR and EA-HR in phase BIND_PATCH.
During phase CONFLICT_CHECK I get:
ERROR> Conflicts found.
Check log file 'SPDA_CONFLCHK.LOG' for details.
To resolve the conflicts the current step will be repeated and you must change your Add-on or Support Package selection or add Conflict Resolution Patches (CRT).
Logfile 'SPDA_CONFLCHK.LOG': search for "EE"
2EETN219 The system found conflicts for add-on "FI-CA" release "604" (see list):
3 ETN223 Piece list "SAPKGEO01G" of already installed add-on component "IS-UT" release "600"
4 ETN225 ... has conflicts with "FI-CA" release "604" - piece list: "SAPK-604DZINFICA"
3WETN232 Conflict resolution by not installing of "FI-CA" release "604""IS-UT""600"
I don't understand the problem of EHPI: The IS-UT 600 is already in the system, and FI-CA 6.04 belongs to EHP4
Repeating the phase didn't help.....
Any ideas ?
Best regards,
Uta
Edited by: Uta Hedemann on Jun 23, 2010 9:38 PMHello Jane,
sounds really good! Thanks for your quick answer. I love SDN for its quick reactions !!!!
In the meanwhile I have opened a message in BC-EHP-INS but have no answer yet. Do you know , if there is an official SAP-note about the solution? I would like to be on the safe side.
ad a) How can I reinstall the "right "SPAM-Update 7.01/39, if it is in the system already.... ? ( I haved used the one of the newest Solman 7.0 DVD SP 19-23.
ad b) I have checked table PATEXCPT, but the entry ""R3TR,SFSW,CONV_INV" is missing. Will it be installed, if I somehow manage to reinstall the SPAM-Update ?
It would have helped a lot if a warning about a wrong SPAM-Version was in note 822379 or somewhere else. I hope, some SAP-collegue will do it later....
Best regards,
Uta -
Solman upgr 710 - Error in Config step (Phase PREP_INTEGRATION/DYNSPCADD)
Dear SAP gurus,
I am performing an upgrade Solman701 to 710 using SOLMANUP. tool. Linux/Oracle
The upgrade got stuck on Configuration step (phase PREP_INTEGRATION/DYNSPCADD) wit the following Warning:
Manual Actions:
WARNING:Your source system is secured by the SAPCryptolib.
To keep the security setting, put a SAPCryptolib archive suitable for your server platform into the download directory.
Download the SAPCryptolib from the SAP Service Marketplace as described in the SAP Note 455033 or comment out the corresponding SSF parameters at the system profile temporary during the upgrade.
I downloaded the SAPCryptolib (900000115.SAR) and put it on the download directory but when I ran the phase step/phase again it came up again the same error. I even "sapcar" it and put it on /usr/sap/trans/EPS/in but it still complains with the same error.
I also checked the note 1302772 but didtnt work either.
Anybody can give me some suggestions on how to go further?
Thanks in advance, MarcHello,
Did you try to put 'Extracted' version of .SAR file in the download directory ?
And did you just 'repeat' the phase from the same sessions of SolmanUp Or tried to stop SolmanUP and then started from the same phase ?
'I also checked the note 1302772 but didtnt work either.'
Note 1302772 is applicable only for SAP EhPi I think, not for SolmanUP.
Thanks -
ECC 6.0 EHP-4 upgrade Issue in phase MAIN SHDRUN/ALTNTAB FILL were negative
Hi Basis Expert,
while doing ECC 6.0 EHP-4 Upgrade in MAIN_SHDRUN/ALTNTAB_FILL phase we are getting the following issue please help us.
Checks after phase MAIN_SHDRUN/ALTNTAB_FILL were negative!
Last error code set: BATCH JOB RDDNT2MT FAILED: Error(s) found in the log(s), accumulated in "ALTNTFI.ELG".
We check the shadow instance is up and we can log in to the system. Check ST22 and SM21 notice no error.
Check the JOB RDDNT2MT (SM37) successfully running and all the job finish without any error.
Hope anybody can share a bit your experience on this issue. we try search the note and find the forum but no luck.
ThanksHi,
> 2EETG011 "No shadow system""(environment parameter)""auth_shadow_upgrade"
> 2EETG011 "No shadow system""DB-connect not against shadow tables !"
>
It looks from your log that shadow system is not able to connect to database. Please check your shadow system. Check below link as well:
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/ecc-6-upgrade-issue-in-phase-altntab_fill-1556272
Thanks
Sunny
Edited by: Sunny Pahuja on Oct 15, 2010 1:27 PM -
Long running ACT_UPG during EHP4 (SP-Stack 08)
During EHP4 Installation after a installation of ERP 6.0 EHP4 Ready) ACT_UPG is running , but very slowly.
In a different system (linux on intel cpu) it took only 6 hours. In my actual system it is already running since nearly 13 hours- since 08.11.2010 04:35:58 !
I compared the actually written logfile
/sapmnt/D01/EHPI/abap/tmp$ wc -l SAPAA70104.D01
588286 SAPAA70104.D01
with that one from a finished installation on linux (with lower sp-stack than 08 and older sapehpi)
There the file has 1.451.798 rows, which means that my ACT_UPG has more than the same work to do...
I have checked the shadow instance: 4 batchprocesses- only one is running with RDDMASGL since 08.11.2010 04:35:58
Add. information:
-Database and CI are on separate hosts (solaris sparc). Both are inclued in /etc/hosts.
- I used sapehpi version SAPehpi_38-10005811.SAR - SAPehpi 700 from 21.10.2010
- I have used following settings :
SAPehpiConsole.log:
Enter the maximum number of batch processes during the installation:
BATCH PROCESSES: 3
Enter the maximum number of parallel processes during uptime:
MAXIMUM UPTIME PROCESSES: 3
Enter the number of parallel import processes during downtime:
R3TRANS PROCESSES: 3
To optimize memory usage during activation, you can use the so-called
"memory-optimized activator". Do you want to use this possibility?
01) - Yes
02) * No
: No
Any ideas ?
Uta
Edited by: Uta Hedemann on Nov 9, 2010 5:34 PMproblem solved itself. ACT_UPG is finished
The corresponding logfile seems to be invalid for analyzing the runtime . Much more smaller than on the other system on linux....
/sapmnt/D01/EHPI/abap/log$ wc -l SAPAA70104.D01
617706 SAPAA70104.D01
Good luck for everybody who has also long run times!
Edited by: Uta Hedemann on Nov 9, 2010 6:26 PM -
Issue with Message Type Triggering during Inbound Delivery Creation
Hi Experts,
Hi Experts,
Currently we are facing issue with message type triggering during inbound delivery creation:
In NACE transaction for Inbound delivery we have 3 custom output types:
Pricing Procedure Used is standard one -> E10001
Z140 Inbound Delivery Create (This should get triggered when IB delivery is created)
Z141 Inbound Delivery Change (This should get triggered when IB Delivery is changed)
Z142 Inbound Delivery Delete(This should get triggered when IB Delivery is deleted).
At present if i check delivery in VL33 -> Extras -> Delivery Output
Both Z140 and Z141 are being triggered during IB delivery creation. While it should be only Z140.
Could you please suggest that are we missing any configuration in SPRO or we need to create any custom routine (requirement) to handle this?
ThanksHi,
There is no fine-tuned control for inbound delivery messages as for Purchase order. Hence I guess to meet your above requirement, you have to go for a custom solution similar to the PO fine tune control settings.
Thanks, -
Modification adjustments during Preprocessing phase in ECC6.0 EHP4 upgrade
Hello All,
We are upgrading our SAP systems from R3 4.7 to ECC 6.0 EHP4 and we are currently in the PreProcessing phase. The upgrade screen has prompted the below message
*You must now include your repository modifications
in the new SAP import.
35 modified objects are found to be adjusted and
0 objects are automatically maintained by import
of an adjustment transport bound to this procedure.
CAUTION: It is impossible to keep these modifications
after you have confirmed this query.
Do you want to make adjustments to ABAP dictionary
objects ?*
I had a few queries
1. Can we carry out the modification adjustment now in the SPDD transaction or did we have to complete it in the Configuration Phase?
2. When we login to the Shadow Instance we are unable to see any of our custom Z progams and transactions in SE38 and SE93 respectively. Is this an issue or will they be available only after the upgrade?
3. If we create the adjustments to Dictionary objects how do we flag the request for transport in SPDD transaction?
Appreciate any help in understanding the above queries and solution to proceed.
ThanksHi,
> 1. Can we carry out the modification adjustment now in the SPDD transaction or did we have to complete it in the Configuration Phase?
You have to perform SPDD now.
> 2. When we login to the Shadow Instance we are unable to see any of our custom Z progams and transactions in SE38 and >SE93 respectively. Is this an issue or will they be available only after the upgrade?
SPDD is not for your Z programs. SPDD is for if you have done changed in SAP standard objects. SPDD will show changes that you have done standard object.
> 3. If we create the adjustments to Dictionary objects how do we flag the request for transport in SPDD transaction?
>
Go to SPDD transaction and changes accordingly and add to transport request there. For more information Check SAP note 485741.
Thanks
Sunny -
Error during EHP4 - Configuration phase
Hi All ,
Im doing an EHP-4 on QAS system, last week i did EHP-4 on DEV system and it was succesful. Im using the same software but
a new XML file has been generated for QAS system. Its a Dual Stack system and now it is in JAVA phase,
JSPM_CHECK_QUEUE and it ends with an error .
I checked the log files and this is what it says
Deployment of archive G:\EHPDownloads\JSPM03_0-20002796.SCA has been rejected because it is already deploye Validation has finished with warning.
Detailed message is All selected SDAs and SCAs have already been deployed before..
Aug 6, 2009 8:21:36 PM [Warning]: com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl [Thread[main,5,main]]: Deployment of archive G:\EHPDownloads\JSPM03_0-20002796.SCA has been rejected because it is already deployed.
Aug 6, 2009 8:21:36 PM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createAndValidateQueue(JSPMSpStackQueuePreparator.java:184) [Thread[main,5,main]]: Creating jspm queue sapjup-queue from sp stack file G:\EHPDownloads\SMSDXML_QAS_20090806071823.012.xml.
Aug 6, 2009 8:26:01 PM [Error]: Exception has occurred during the execution of the phase.
Aug 6, 2009 8:26:01 PM [Error]: com.sap.sdt.jspm.unattended.RequestController.addContextInfo(RequestController.java:178) [Thread[main,5,main]]: Validation of queue sapjup-queue completed with error
JSPM version is 7.01.3.0.15. Current JSPM log directory is E:\usr\sap\QAS\DVEBMGS00\j2ee\JSPM\log\log_2009_08_06_20_21_38.
Aug 6, 2009 8:26:01 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:702) [Thread[main,5,main]]: The validation of the deploy queue was not successful.
Aug 6, 2009 8:26:01 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been completed.
Has any one seen this error before ??
Regards,
Ershad AhmedHello All,
I was able to resolve the issue
I checked the logs in \usr\sap\QAS\DVEBMGS00\j2ee\JSPM\log\log_2009_08_07_12_20_42
upon checking i found that it was searching for two kernel files which were not there .
FYI, when i downloaded the software and i checked i found that there were 2 diff kernel files, so i removed these files
and started EHP-4
To resolve this issue i had to place these files back in the download directory.
Regards,
Ershad Ahmed -
Issue in Phase Configuration during EHP5
Hello all,
We are having ECC 6.0. onUnix. I am trying to apply EHP5 SP stack 8 by using SAPehpi installer. During the Configuration Step
I get this error:
There are dependencies between packages included into the procedure and the target release kernel.
The release of tool disp+work needs to be at least 702.
*Any idea where can I download disp+work 702..* On SAP Service Marketplace?
I did find this kernel on SAP Service Marketplace but no 702?
SAP KERNEL 7.00 64-BIT UNICODE
SAP KERNEL 7.01 64-BIT UNICODE
SAP KERNEL 7.10 64-BIT UNICODE
SAP KERNEL 7.11 64-BIT UNICODE
SAP KERNEL 7.20 64-BIT UNICODE
any idea?
RegardsHello Sunny,
Thanks for reply,
I did continued after that, But I have this error on Check Phase:
I have this error from SAPehpi_troubleticket.log file:
SAPehpi broke during phase NTACT_CHK in module PREP_GENCHECKS / General checks
Error Message: No lines found in logfile matching 'PN......\.RSX'
Summary of SAPehpi:
SAPehpi Release: lmt_001
SAPehpi Version: 40.012
Start Release: 700
Target Release: 702
Summary of host system details:
SID: RSX
Host: sapux24
MS Host: sapux24
GW Host: sapux24
Start Path: /usr/sap/RSX/DVEBMGS02/exe
Kernel Path: /usr/sap/RSX/DVEBMGS02/exe
Summary of operating system details:
OS Type: HP-UX IA64
OS Version: 11.31
Summary of database details:
Database Type: ora
Database Version: 10.2.0.4.0
Summary of RFC details:
Host: sapux24
GW Host: sapux24
Client: 000
Destination: RSX
Language:
System No.: 02
And from NTCHK.LOG file I have :
CHKANT and RETURN CODE in PN400817.RSX
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETP399XRead table "M_DEBI ": pgntab call: table not found.
2AETP399 Table "M_DEBI ": unknown error -9
2EETP399XRead table "M_KRED ": pgntab call: table not found.
2AETP399 Table "M_KRED ": unknown error -9
2EETP399XRead table "M_MAT1 ": pgntab call: table not found.
2AETP399 Table "M_MAT1 ": unknown error -9
2EETP399XRead table "M_MEKK ": pgntab call: table not found.
2AETP399 Table "M_MEKK ": unknown error -9
2EETP399XRead table "M_ZPNR ": pgntab call: table not found.
2AETP399 Table "M_ZPNR ": unknown error -9
1 ETP111 exit code : "12"
I did check for this table on SE11, but there are not found. I
Any idea?
Edited by: Ejersbo Reza on Aug 17, 2011 1:31 PM -
Error in PREPARE_JSPM_QUEUE during EHP4 install
Hello,
I'm upgrading my ECC 6.0 system to ECC 6.0 EHP4. in the JAVA configuration phase PREPARE_JSPM_QUEUE I get the following error:
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/SAP_JTECHF with version 7.00.21.8 is found on the system but in the stack it is listed with version 7.00.21.0.
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/SAP_JTECHS with version 7.00.21.14 is found on the system but in the stack it is listed with version 7.00.21.0.
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/LM-TOOLS with version 7.00.21.1 is found on the system but in the stack it is listed with version 7.00.21.0.
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/CORE-TOOLS with version 7.00.22.1 is found on the system but in the stack it is listed with version 7.00.22.0.
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/SAP-JEE with version 7.00.21.8 is found on the system but in the stack it is listed with version 7.00.21.0.
I have configured the JAVA stack in the Solution Manager so the XML stack contains SP level 21 for software component SAP_JTECHS. What I donu2019t understand is how could the installer read a SP level 21.8. I didn't know the sub versions exists.
Does anyone know how to fix this problem so I could go on with the upgrade.
Kind regards,
Richard MeijnHello Richard,
check the XML file generated, on the entries for SAP_JTECHF, SAP_JTECHS, LM-TOOLS, CORE-TOOLS and SAP-JEE components.
For example:
- <software-component>
<caption>SAP_JTECHF</caption>
<ppms-number>xxxxxxxxxxxxxxxxxxx</ppms-number>
<runtime-type>J2EE</runtime-type>
<name>XXXXXXXXXXXXX</name>
<version>7.00</version>
<vendor>sap.com</vendor>
- <support-package>
<caption>SP021 for SAP_JTECHF 7.00</caption>
<name>SP021</name>
<vendor>sap.com</vendor>
<ppms-number>xxxxxxxxxxxxxxxxxxx</ppms-number>
<sp-level>021</sp-level>
<patch-level>0</patch-level>
- <archives>
You'll see on the "patch level" entry (which means the sub version you're referring to) that it should be '0' on the XML file.
The main possibility for this is that MOPZ generated the XML file incorrectly, based on the information it fetched from the SolutionManager. This issue is occuring probably because you have an outdated information or there are missing information in transaction SMSY. Check in SMSY if the Software components for the system are up to date. If not you need send the
system data to a SLD and use LANDSCAPE FETCH to update the JAVA data in SMSY. After have JAVA system components data updated in SMSY you must create a new mopz transaction. This new mopz transaction will not include wrong information in the XML file then.
(remember you need a SLD to maintain the JAVA information. You can use the SLD of the solution manager. Go to the Visual Administrator of the system that you want upgrade and in SLD Data Supplier Service, maintain the User/password/host/port of the SLD of solman and trigger the service. The SLD of solman will be updated with the JAVA information of this system and after run LANDSCAPE fetch job, SMSY will be populated with JAVA information up to date. If you created manually the JAVA instances, MOPZ will not know the SOURCE software components and this will have a big impact in the calculation as MOPZ will not know the source components version.)
Alternatively you can create a XML file manually (with the correct SP and patch levels, of course). This method is supported too, just keep in mind that if you have a ERP system that you want upgrade to EHP4 or a higher EHP version, you must
use MOPZ. If you're implementing EHP1 in Netweaver, you can use the XML file generated in the Service Marketplace without problems.
I hope all this information helps.
Best regards,
Tomas Black -
TEST IMPORT phase error?during importing the patches
Dear All,
i was importing the HR patches SAPKE60023,SAPKE60024,
SAPKE60025,SAPKE60026.In between error display PHASE TEST IMPORT ?
MESSAGE:
Error occourred in TEST_IMPORT.
All these 4 SP was in the queue.
SAPKE60023:0004RC
SAPKE60024:0004RC
SAPKE60025:0008RC
SAPKE60026:0004RC
log files is attached.
1 ETP199X######################################
1 ETP152 TESTIMPORT
1 ETP101 transport order : "SAPKE60025"
1 ETP102 system : "MRP"
1 ETP108 tp path : "tp"
1 ETP109 version and release : "372.04.29" "700"
1 ETP198
4 ETW000 R3trans.exe version 6.14 (release 700 - 14.04.08 - 10:31:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 23.05.2008 - 03:54:38
4 ETW000 control file:
sappro\sapmnt\trans\tmp\SAPKKE60025.MRP
4 ETW000 > #pid 6080 on sappro (APServiceMRP)
4 ETW000 > testimport
4 ETW000 > file='
sappro\sapmnt\trans\data\RE60025.SAP'
4 ETW000 > buffersync=no
4 ETW000 >
4 ETW000 R3trans was called as follows: R3trans.exe -w
sappro\sapmnt\trans\tmp\SAPPE60025.MRP -u 1
sappro\sapmnt\trans\tmp\SAPKKE60025.MRP
4 ETW000 active unconditional modes: 1
4 ETW000 Connected to DBMS = ORACLE --- dbs_ora_tnsname = 'MRP' --- SYSTEM = 'MRP'.
4 ETW690 COMMIT "0" "0"
4 ETW000 trace at level 1 opened for a given file pointer
4 ETW000
4 ETW000 ================== STEP 1 =====================
4 ETW000 date&time : 23.05.2008 - 03:54:39
4 ETW000 function : TESTIMPORT
4 ETW000 data file :
sappro\sapmnt\trans\data\RE60025.SAP
4 ETW000 buffersync : NO
4 ETW000 clients : as exported
4 ETW000 l.s.m. : VECTOR
4 ETW000 commit : 100000
4 ETW000 table cache : dynamic
4 ETW000
4 ETW000 Character set on this machine : 2 byte unicode little endian.
4 ETW000 Character set on the data file: ASCII (ISO 8859-1).
4 ETW000 Data file is compressed with algorithm 'L'.
4 ETW000 Export was executed on 20.12.2007 at 14:39:25 by c7eadm
3 ETW709 "700 "
4 ETW000 with R3trans version: 20.07.06 - 17:34:00
4 ETW000 Source System = AMD/Intel x86_64 with Linux on DBMS = ADABAS D --- DBNAME = 'C7E' --- SYSTEM = 'C7E'.
4 ETW000
4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd
4 ETW000 lsm during export: ALL
4 ETW000 texts in language i will be converted with codepage 1100
4 ETW000 texts in language d will be converted with codepage 1401
4 ETW000 texts in language c will be converted with codepage 1100
4 ETW000 texts in language b will be converted with codepage 1100
4 ETW000 texts in language a will be converted with codepage 1100
4 ETW000 texts in language 8 will be converted with codepage 1500
4 ETW000 texts in language 7 will be converted with codepage 1100
4 ETW000 texts in language 6 will be converted with codepage 1401
4 ETW000 texts in language 5 will be converted with codepage 1401
4 ETW000 texts in language 4 will be converted with codepage 1401
4 ETW000 texts in language 3 will be converted with codepage 8500
4 ETW000 texts in language 2 will be converted with codepage 8600
4 ETW000 texts in language 1 will be converted with codepage 8400
4 ETW000 texts in language 0 will be converted with codepage 1500
4 ETW000 texts in language W will be converted with codepage 1500
4 ETW000 texts in language V will be converted with codepage 1100
4 ETW000 texts in language U will be converted with codepage 1100
4 ETW000 texts in language T will be converted with codepage 1610
4 ETW000 texts in language S will be converted with codepage 1100
4 ETW000 texts in language R will be converted with codepage 1500
4 ETW000 texts in language Q will be converted with codepage 1401
4 ETW000 texts in language P will be converted with codepage 1100
4 ETW000 texts in language O will be converted with codepage 1100
4 ETW000 texts in language N will be converted with codepage 1100
4 ETW000 texts in language M will be converted with codepage 8300
4 ETW000 texts in language L will be converted with codepage 1401
4 ETW000 texts in language K will be converted with codepage 1100
4 ETW000 texts in language J will be converted with codepage 8000
4 ETW000 texts in language I will be converted with codepage 1100
4 ETW000 texts in language H will be converted with codepage 1401
4 ETW000 texts in language G will be converted with codepage 1700
4 ETW000 texts in language F will be converted with codepage 1100
4 ETW000 texts in language E will be converted with codepage 1100
4 ETW000 texts in language D will be converted with codepage 1100
4 ETW000 texts in language C will be converted with codepage 1401
4 ETW000 texts in language B will be converted with codepage 1800
4 ETW000 texts in language A will be converted with codepage 8700
4 ETW000 trfunction = D (patch transport)
3 ETW708 "000"
4 ETW000 switching to selective language import
4 ETW000 the following languages will be imported: DE
4 ETW000 Used Commandfile SAPKE60025 (SAPUSER/1366)
4 ETW000 ... ignoring such differences.
4 ETW000 0 entries for E070 imported (SAPKE60025).
4 ETW000 ... ignoring such differences.
4 ETW000 0 entries for E071 imported (SAPKE60025 *).
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 LANGSSFOHR_CMP_TCS lang R not imported.
4 ETW000 E071-LOCKFLAGs 000002 - 000002 updated ('3', 1 entries).
4 ETW690 COMMIT "128" "128"
4 ETW000 ... ignoring such differences.
4 ETW000 table STXFCONT: entry in DB is 32 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table REPOSRC: entry in DB is 176 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table REPOTEXT: entry in DB is 68 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table SEOCLASS: entry in DB is 32 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table SEOCLASSDF: entry in DB is 353 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table SEOCLASSEX: entry in DB is 88 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table SEOCOMPODF: entry in DB is 10548 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table SEOCOMPOEX: entry in DB is 88 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table SEOSUBCODF: entry in DB is 396 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table SEOSUBCOEX: entry in DB is 116 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table EUDB: entry in DB is 128 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table FUPARAREF: entry in DB is 228 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
2EETW165 Function "HRCCE_EXT_EMP_ATTR_CE (HRCCE_BI_CE|02)" does not fit into the existing function group "(HRCCE_CALENDAR_FUNCTIONS|05)".
2 ETW167 Please transport the whole function group.
2EETW165 Function "HRCCE_GET_EMP_ATTR_CE (HRCCE_BI_CE|03)" does not fit into the existing function group "(HRCCE_CALENDAR_FUNCTIONS|04)".
2 ETW167 Please transport the whole function group.
2EETW165 Function "HRCCE_GET_PERSONID (HRCCE_BI_CE|04)" does not fit into the existing function group "(HRCCE_CALENDAR_FUNCTIONS|06)".
2 ETW167 Please transport the whole function group.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table SPROXDAT: entry in DB is 1036 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table SPROXHDR: entry in DB is 1640 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table SPROXLPT: entry in DB is 452 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table SOTR_HEAD: entry in DB is 185 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table CUS_ACTH: entry in DB is 65 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table CUS_ATRH: entry in DB is 61 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table ENHSPOTHEADER: entry in DB is 164 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table ENHSPOTCONTRACT: entry in DB is 160 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table STXL: entry in DB is 90 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table DSYS_PHCONT_CCD2: entry in DB is 76 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table DSYS_PHCONT_ECD2: entry in DB is 76 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table DSYS_PHCONT_ECI2: entry in DB is 76 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table ROOSFIELD: entry in DB is 124 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table VARID: entry in DB is 120 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table FPCONTEXT: entry in DB is 112 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table FPLAYOUT: entry in DB is 84 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table FPLAYOUTT: entry in DB is 64 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table TTREEP: entry in DB is 176 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table TTREE_APPL: entry in DB is 184 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table T511: entry in DB is 87 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table T512W: entry in DB is 184 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table T5G01: entry in DB is 25 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table T5G_NICLIM: entry in DB is 20 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table T5KTC: entry in DB is 25 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table LTDX: entry in DB is 144 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table OBJSL: entry in DB is 180 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table T506D: entry in DB is 46 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table T511K: entry in DB is 27 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table T511P: entry in DB is 31 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
3WETW109 table "T52E_ARFC" does not exist in nametab.
3WETW109 table "T52E_ARFCT" does not exist in nametab.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
3WETW109 table "T5BX2" does not exist in nametab.
4 ETW000 ... ignoring such differences.
4 ETW000 table T5C2D: entry in DB is 44 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table T5G03: entry in DB is 17 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table T5G67: entry in DB is 19 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table T5GT2: entry in DB is 25 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table T5N1L: entry in DB is 32 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table T5N21: entry in DB is 31 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table T5N22: entry in DB is 24 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table T5N2O: entry in DB is 30 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table T5S3N: entry in DB is 19 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table T7IE3: entry in DB is 31 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 table T7IE4: entry in DB is 26 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 table T7KRTR: entry in DB is 5 bytes bigger than in file.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW000 ... ignoring such differences.
4 ETW690 COMMIT "0" "128"
4 ETW000 6801621 bytes read.
4 ETW000 Transport overhead 27.5 %.
4 ETW000 Data compressed to 9.2 %.
4 ETW000 Duration: 3 sec (2267207 bytes/sec).
3 ETW710 "0" "0"
4 ETW000 [dev trc ,00000] Fri May 23 03:54:42 2008 3256961 3.256961
4 ETW000 [dev trc ,00000] Disconnecting from ALL connections: 29 3.256990
4 ETW000 [dev trc ,00000] Disconnecting from connection 0 ... 35 3.257025
4 ETW000 [dev trc ,00000] Closing user session (con_hdl=0,svchp=02283750,usrhp=022A9C88)
4 ETW000 699 3.257724
4 ETW000 [dev trc ,00000] Detaching from DB Server (con_hdl=0,svchp=02283750,srvhp=02294FC4)
4 ETW000 854 3.258578
4 ETW000 [dev trc ,00000] Now I'm disconnected from ORACLE 774 3.259352
4 ETW000 [dev trc ,00000] Disconnected from connection 0 139 3.259491
4 ETW000 [dev trc ,00000] statistics db_con_commit (com_total=3, com_tx=2)
4 ETW000 64 3.259555
4 ETW000 [dev trc ,00000] statistics db_con_rollback (roll_total=0, roll_tx=0)
4 ETW000 66 3.259621
4 ETW000 Disconnected from database.
4 ETW000 End of Transport (0008).
4 ETW000 date&time: 23.05.2008 - 03:54:42
4 ETW000 3 warnings occured.
4 ETW000 3 errors occured.
1 ETP152 TESTIMPORT
1 ETP110 end date and time : "20080523035442"
1 ETP111 exit code : "8"
1 ETP199 ######################################
plz its urgent.....give me suggestion hoe to resolve this issue.Hi aadil mudassir .This known problem. Befor you applay SP you need to read -->
Note 822379 - Known problems with Support Packages in SAP NW 2004s AS ABAP
In this note for your problem :Symptom: If the Support Packages SAPKE60024 and SAPKE60025 are imported together in a queue, the TEST_IMPORT step returns an error for Support Package SAPKE60025. The test import log of SAPKE60025 displays the following error message:
Function HRCCE_EXT_EMP_ATTR_CE (HRCCE_BI_CE 02) does not fit into the existing function group ((HRCCE_CALENDAR_FUNCTIONS 05))
This error message recurs for two other function modules of the function groups HRCCE_BI_CE and HRCCE_CALENDAR_FUNCTIONS.
Solution: You can ignore this error by choosing 'Extras'-> 'Ignore test-import error'. The error will not occur during the later import.
Regards. -
Error in Instantiate Phase (adcrdb.sh) during adcfgclone.pl dbconfig
Hello,
I am finishing an environmental clone from PRD->TST and am running the adcfgclone.pl dbconfig (because controlfiles will not be created) portion to configure the target database. It progresses to the point of DB Application and then errors out with the below message. I have verified that the file itself exists on the target DBTier, and that the permissions are correct on the file. Has anyone seen this before, or could they recommend anything? Thanks in advance.
+[AutoConfig Error Report]+
The following report lists errors AutoConfig encountered during each
phase of its execution. Errors are grouped by directory and phase.
The report format is:
+<filename> <phase> <return code where appropriate>+
+[INSTANTIATE PHASE]+
AutoConfig could not successfully instantiate the following files:
Directory: /u01/oracle/xxxTST/db/tech_st/11.1.0/appsutil/install/xxxTST_xxxtstxx
adcrdb.sh INSTE8
AutoConfig is exiting with status 1
RC-50014: Fatal: Execution of AutoConfig was failed
Raised by oracle.apps.ad.clone.ApplyDatabaseCorrect. After searching the log file, it explains to me that adcrdb.sh is missing from the <$ORACLE_HOME>/appsutil/template directory. So, I copy the file from the Source<$ORACLE_HOME>/appsutil/template to the Target <$ORACLE_HOME>/appsutil/template directory. Immediately upon kicking off the adcfgclone.pl dbconfig again it is deleted. This is very strange. Am I missing something?
-rwxr----- 1 oracle dba 4015 Dec 19 16:18 adcrdb.sh
[oracle@x07tst00 template]$ ls -lrt adcrdb.sh
-rwxr----- 1 oracle dba 4015 Dec 19 16:18 adcrdb.sh
[oracle@x07tst00 template]$ ls -lrt adcrdb.sh
-rwxr----- 1 oracle dba 4015 Dec 19 16:18 adcrdb.sh
[oracle@x07tst00 template]$ ls -lrt adcrdb.sh
-rwxr----- 1 oracle dba 4015 Dec 19 16:18 adcrdb.sh
[oracle@x07tst00 template]$ ls -lrt adcrdb.sh
ls: adcrdb.sh: No such file or directory
[oracle@x07tst00 template]$ ls -lrt adcrdb.sh
ls: adcrdb.sh: No such file or directory
[oracle@x07tst00 template]$ ls -lrt adcrdb.sh
ls: adcrdb.sh: No such file or directory -
Cloning Issue RC-00118: Error occurred during creation of database
Friends,
I execute following scripts on source system preclone.pl dbTier &perl adpreclone.pl appsTier
then take the cold source backup and transfer on another machine for cloning but when i am executing cloning script on db tier i am getting below mention error after 50% completion. I have very limited time and i cant go back on source system for fresh backup, please help me to sort out his issue.
-------------------ADX Database Utility Finished--------------
RC-00118: Error occurred during creation of database
Raised by oracle.apps.ad.clone.ApplyDatabase
StackTrace:
java.lang.Exception: Control file creation failed
at oracle.apps.ad.clone.ApplyDatabase.doConf(ApplyData
at oracle.apps.ad.clone.ApplyDatabase.doApply(ApplyDat
at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyData
at oracle.apps.ad.clone.ApplyDBTier.<init>(ApplyDBTier
at sun.reflect.NativeConstructorAccessorImpl.newInstan
at sun.reflect.NativeConstructorAccessorImpl.newInstan
at sun.reflect.DelegatingConstructorAccessorImpl.newIn rce)
at java.lang.reflect.Constructor.newInstance(Unknown S
at oracle.apps.ad.clone.util.CloneProcessor.run(CloneP
at java.lang.Thread.run(Unknown Source)
Hopes you will support.
Regards
Irfan Ahmadplz check :
http://doganayn.blogspot.in/2013/11/rc-50004-fatal-error-occurred-in.html
Rapid Clone Failed While Running "Adcfgclone.pl dbTier": ORA-01194 and RC-00118 (Doc ID 375389.1)
Troubleshooting RapidClone issues with Oracle Applications R12 (Doc ID 603104.1)
Troubleshooting RapidClone issues with Oracle Applications 11i (Doc ID 364565.1)
Regards,
Haafiz -
SUM issue at phase specify Credentials on PI7.4 dual STACK
Hello SAP,
We are planning to apply SFTP addon using SUM .
We are getting error at phase - specify Credentials
Pls check the below error log.
An error has occurred during the execution of the Determine system release step.
You can find more information in the file
To troubleshoot the problem use the provided information. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following keywords:
DETECT input_credentials input-credentials-dialog determine-engine-release com.sap.sdt.j2ee.services.servicesimpl.EngineInfoService class com.sap.sdt.j2ee.tools.releasedetection.EngineReleaseDetectionException
VERSION_ACTION_VERSION_NULL_16.ERR:
/usr/sap/SID/DVEBMGS00/j2ee/cluster/bootstrap/scripts/version.sh[10]: /usr/sap/SID/DVEBMGS00/j2ee/cluster/bootstrap/scripts/launcher.sh: cannot execute
TroubleTicket_16.txt:
Trouble Ticket Report
Update to n/a
SID................: n/a
Hostname...........: n/a
Install directory..: /usr/sap/SID
SUM directory......: /SUM/sdt
Database...........: n/a
Operating System...: UNX
JDK version........: 1.6.0_81 SAP AG
SUM version........: 1.0.11.1
Source release.....: n/a
Target release.....: n/a
ABAP stack present.: true
An error has occurred during the execution of the Determine system release step with action input_credentials. Service com.sap.sdt.j2ee.services.servicesimpl.EngineInfoService failed with the following message:
Could not detect AS Java release.
You can find more information in the files /SUM/sdt/log/SUM/DETERMINE-ENGINE-RELEASE_16.LOG and ProcessOverview.html.
Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:
DETECT,input_credentials,input-credentials-dialog,determine-engine-release,com.sap.sdt.j2ee.services.servicesimpl.EngineInfoService,class com.sap.sdt.j2ee.tools.releasedetection.EngineReleaseDetectionException
DETERMINE-ENGINE-RELEASE_16.LOG:
<!--LOGHEADER[START]/-->
<!--HELP[Manual modification of the header may cause parsing problem!]/-->
<!--LOGGINGVERSION[2.0.7.1006]/-->
<!--NAME[/SUM/sdt/log/SUM/DETERMINE-ENGINE-RELEASE_16.LOG]/-->
<!--PATTERN[DETERMINE-ENGINE-RELEASE_16.LOG]/-->
<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->
<!--ENCODING[UTF8]/-->
<!--LOGHEADER[END]/-->
Jul 31, 2014 12:18:05 AM [Info ]: Checking AS Java release using version command.
Jul 31, 2014 12:18:05 AM [Info ]: The tool have been found in location /usr/sap/SID/DVEBMGS00/j2ee/cluster/bootstrap/scripts/version.sh.
Jul 31, 2014 12:18:05 AM [Info ]: Process ID 339, name /usr/sap/SID/DVEBMGS00/j2ee/cluster/bootstrap/scripts/version.sh has been started.
Jul 31, 2014 12:18:05 AM [Info ]: Command line: /usr/sap/SID/DVEBMGS00/j2ee/cluster/bootstrap/scripts/version.sh
Jul 31, 2014 12:18:05 AM [Info ]: Standard out: /SUM/sdt/log/SUM/VERSION_ACTION_VERSION_NULL_16.OUT
Jul 31, 2014 12:18:05 AM [Info ]: Process ID 339 has been started.
Jul 31, 2014 12:18:05 AM [Info ]: Waiting for process ID 339, name /usr/sap/SID/DVEBMGS00/j2ee/cluster/bootstrap/scripts/version.sh to finish.
Jul 31, 2014 12:18:05 AM [Info ]: Process ID 339, name /usr/sap/SID/DVEBMGS00/j2ee/cluster/bootstrap/scripts/version.sh has been finished, exit code 126.
Jul 31, 2014 12:18:05 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.j2ee.tools.releasedetection.EngineReleaseDetectionException: Could not detect AS Java release.
Return code condition success evaluated to false for process /usr/sap/SID/DVEBMGS00/j2ee/cluster/bootstrap/scripts/version.sh for action ACTION_VERSION.This is part one from the above note:
I. Change configuration for web methods protection to DEFAULT and restart:
1. Open for edit DEAFULT.PLF file from /usr/sap/(SID)/SYS/profile and set configuration:
service/protectedwebmethods = DEFAULT
2. Restart the cluster including sapstartsrv OS service:
2.1. For windows you can execute with administrator privileges following command to stop the services:
c:\> sc stop SAP[SID]_[Instance_Number]
c:\> sc stop SAP[SID]_[SCS_Instance_Number]
c:\> sc start SAP[SID]_[SCS_Instance_Number]
c:\> sc start SAP[SID]_[Instance_Number]
(SAP MMC could automatically start the services, in this case start command will produce warning "An instance of the service is already running.")
2.2. For Linux/Unix you can use stopsap/startsap commands without parameters (more info is available here : http://help.sap.com/saphelp_nwpi71/helpdata/en/47/1d6feeff6e0d46e10000000a155369/content.htm).
3. Retry update procedure step.
4. After upgrade has finished you can restore the settings in the DEFAULT.PFL profile and restart the instance and services
.Set service/protectedwebmethods = DEFAULT in default profile
stopsap -i DVEBMGS<nn>
stopsap -i SCS<nn>
startsap -i SCS<nn>
startsap -i DVEBMGS<nn>
where <nn> is your instance number
Retry failed step again.
Divyanshu -
Upgrade issue in phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE were negative
Hello Team,
Got hanged at the phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE were negative,.
Error:
Checks after phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE were negative!
Last error code set: Detected 1 aborted activities in 'PHASES.ELG'<br/> Calling 'D:\usr\sap\XXX\DVEBMGS00\exe/tp' failed with return code 13, check D:\Software\SUM\abap\log\SAPup.ECO for details
Log file says:
EXECUTING D:\usr\sap\XXX\DVEBMGS00\exe\tp.EXE "pf=D:\Software\SUM\abap\var\DEFAULT.TPP" import all XXX
This is D:\usr\sap\XXX\DVEBMGS00\exe\tp.EXE version 380.03.95 (release 738, unicode enabled)
Could not open the ICU common library.
The following files must be in the path described by
the environment variable "PATH":
icuuc50.dll, icudt50.dll, icuin50.dll [D:/depot/bas/741_REL/src/flat/nlsui0.c 1535] pid = 12148
PATH is currently set to D:\usr\sap\XXX\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\j2sdk1.4.2_24-x64\bin;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\XXX\SYS\exe\uc\NTAMD64 [D:/depot/bas/741_REL/src/flat/nlsui0.c 1538] pid = 12148
stopping on error 13 during MAIN IMPORT
tp returncode summary:
TOOLS: Highest return code of single steps was: 13
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 13
meaning:A tool used by tp got a signal from operating system
tp=>sapparam(1c): No Profile used.
tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 13 during MAIN IMPORT
SAPup> Process with PID 12212 terminated with status 13 at 20140515155156!
### Phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE:
Please help me out,..
Thank you,
Mohan Karamala.I have cancelled the upgrade and tried again,..but got hanged with the same problem,..
Please help me,. or can i raise a ticket with SAP.???
Log details:
### Phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE:
SAPup> Starting subprocess in phase 'TOOLIMP_TOOLDEL_PRE' at 20140519045354
ENV: DBMS_TYPE=mss
ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
ENV: PATH=D:\usr\sap\PS1\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\j2sdk1.4.2_24-x64\bin;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\PS1\SYS\exe\uc\NTAMD64
ENV: SAPSYSTEMNAME=PS1
ENV: dbs_mss_schema=ps1
ENV: rsdb_ssfs_connect=0
EXECUTING D:\usr\sap\PS1\DVEBMGS00\exe\tp.EXE "pf=D:\Software\SUM\abap\var\DEFAULT.TPP" import all PS1
This is D:\usr\sap\PS1\DVEBMGS00\exe\tp.EXE version 380.03.95 (release 738, unicode enabled)
Could not open the ICU common library.
The following files must be in the path described by
the environment variable "PATH":
icuuc50.dll, icudt50.dll, icuin50.dll [D:/depot/bas/741_REL/src/flat/nlsui0.c 1535] pid = 2560
PATH is currently set to D:\usr\sap\PS1\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\j2sdk1.4.2_24-x64\bin;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\PS1\SYS\exe\uc\NTAMD64 [D:/depot/bas/741_REL/src/flat/nlsui0.c 1538] pid = 2560
stopping on error 13 during MAIN IMPORT
tp returncode summary:
TOOLS: Highest return code of single steps was: 13
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 13
meaning:
A tool used by tp got a signal from operating system
tp=>sapparam(1c): No Profile used.
tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 13 during MAIN IMPORT
SAPup> Process with PID 7332 terminated with status 13 at 20140519045404!
Thank you,
Mohan Karamala.
Maybe you are looking for
-
I'm confused as to the procedure of transferring a large amount of photos and videos from my iPad Mini (iOS 8) to my iMac (latest Yosemite OS) without using wifi or Bluetooth or uploading to iCloud - I wish to transfer the files using a simple USB co
-
RF loop through failing when high eco kicks in
I took delivery of my shiny tiny G4 2100 on Friday - it's immense! However, it does seem to have a bug in its handling of RF loop through... Last night I dropped the box into standby and switched to my TV's on-board tuner. My G4 was configured for hi
-
Passing parameters by customizing worksheet portlet
Hi, is there a max on number of entries in a "parameterbox" on a worksheet portlet? Whenever we try to pass more than 90 selected values for a parameter the portlet comes up empty (it works fine in discoverer viewer/plus). Selecting a few values less
-
How to purchase gift certificates
Is it possible to purchase a gift certificate for the App Store? Exactly how to do it? Entering "gift certificates" into the "submit a question" field produces three or four discussions, all of which report the questioner is turned away without expla
-
How do I compile DWM without any "rules". Should I make a useless one, I would rather not.