Upgrading as abap 7.0 to as abap ehp1 7.01 sp5

hi all
i'm upgrading as abap 7.0 ehp1 7.01 sp5
during the phase preprocessing i get the following error
The EhP Installation program builds the shadow system from the original
one.
in the logfile TPSQLSTD.OUT
TRACE-INFO: 105: [dev trc ,00000] SELECT VERSION FROM SVERSTRACE-INFO: 106:
11 0.100363
TRACE-INFO: 107: [dev trc ,00000] DbSlRead(): table='SVERS'
21 0.100384
TRACE-INFO: 108: [dev trc ,00000] OCI-call failed with -
1=OCI_ERROR
668 0.101052
TRACE-INFO: 109: [dev trc ,00000] SQL error 942: 'ORA-00942:
table or view does no
t exist'
TRACE-INFO: 110:
10 0.101062
TRACE-INFO: 111: [dev trc ,00000] set_ocica() -> OCI or SQL
return code 942
12 0.101074
TRACE-INFO: 112: [dblink ,01299] ***LOG BZA=>table SVERS
does not exist on data
base [dblink#5 @ 1299]
TRACE-INFO: 113:
any idea
regards tom

Hi,
> 10 0.101062
> TRACE-INFO: 111: [dev trc ,00000] set_ocica() -> OCI or SQL
> return code 942
> 12 0.101074
> TRACE-INFO: 112: [dblink ,01299] ***LOG BZA=>table SVERS
> does not exist on data
> base [dblink#5 @ 1299]
> TRACE-INFO: 113:
Check SVERS table exist or not ?
Also, check SAP Note 662644 - Composite SAP Note: ORA-00942
Thanks
Sunny

Similar Messages

Hi guru's what is the upgradation in abap

1) what is upgradation in abap.please explain me.
Moderator message - Please ask a specific question - post locked
Edited by: Rob Burbank on May 15, 2009 11:38 AM

SEARCH in SCN.

Upgrading as abap 7.0 SP17 to as abap 7.01 ehp1 sp5 BI system

hi all
i'm upgrading as abap 7.0 SP17 to as abap 7.01 ehp1 sp5
during the phase preprocessing i get the following error
The EhP Installation program builds the shadow system from the original
one.
in the logfile TPSQLSTD.OUT
TRACE-INFO: 105: dev trc ,00000 SELECT VERSION FROM SVERSTRACE-INFO: 106:
11 0.100363
TRACE-INFO: 107: dev trc ,00000 DbSlRead(): table='SVERS'
21 0.100384
TRACE-INFO: 108: dev trc ,00000 OCI-call failed with -
1=OCI_ERROR
668 0.101052
TRACE-INFO: 109: dev trc ,00000 SQL error 942: 'ORA-00942:
table or view does no
t exist'
TRACE-INFO: 110:
10 0.101062
TRACE-INFO: 111: dev trc ,00000 set_ocica() -> OCI or SQL
return code 942
12 0.101074
TRACE-INFO: 112: dblink ,01299 ***LOG BZA=>table SVERS
does not exist on data
base dblink#5 @ 1299
TRACE-INFO: 113:
any idea
regards tom

Hi,
> 10 0.101062
> TRACE-INFO: 111: [dev trc ,00000] set_ocica() -> OCI or SQL
> return code 942
> 12 0.101074
> TRACE-INFO: 112: [dblink ,01299] ***LOG BZA=>table SVERS
> does not exist on data
> base [dblink#5 @ 1299]
> TRACE-INFO: 113:
Check SVERS table exist or not ?
Also, check SAP Note 662644 - Composite SAP Note: ORA-00942
Thanks
Sunny

Upgrading to ABAP 7.02

Hi all,
Can someone shed some light on the various options to upgrade from ABAP 700 to ABAP 702, preferably with their pros and cons?
Thanks and Regards,
Jinesh.

Are you talking about NetWeaver 7.0 to 7.02? If so, I would expect that you're going to 7.01 with ECC 6 EhP4 first.

Error while upgrading NW04s ABAP from sp7 to sp8

Hi,
I installed NW04s in my system and its ABAP stack is upgraded to sp7. When i was upgrading its SAP_BASIS support package to sp8, i got the following error.
Error in phase: IMPORT_PROPER
Reason for error: TP_BUFFER_INCONSISTENCY
Return code: 0008
Error message: Pkgs. in queue don"t exist in the tp buffer (e.g. SAPKB70008)
This phase imports all Repository objects and table entries. It may terminate for the following reasons:
○       TP_INTERFACE_FAILURE: The tp interface could not be called.
○       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
○       TP_STEP_FAILURE: A tp step could not be performed successfully. You can find the source of error in the relevant log, for example, in the import log.
If a tp step 6, N or S is in the termination message, it is a step independent of the transport request. The corresponding logs are contained in the log overview under the node Import steps not specific to the transport request.
You can also find these logs in the following files in the log subdirectory of your transport directory (usually /usr/sap/trans/log):
tp step 6: P<YY><MM><DD>.<SID>
tp step N: N<YY><MM><DD>.<SID>
tp step S: DS<YY><MM><DD>.<SID>
To display these files, run report RSPUTPRT or call transaction AL11.
Can anyone help me to resolve this problem?
Thanks in advance.

I have the similar problem to yours with tp_buffer_consistency at the xpra_phase when I was runing SAINT on a SAP R/3 Service Tool (RTCTOOL) with SAPKITAR19.
Shall you confirm what you have solved your problem are:
1) You have removed registers from the file /usr/sap/trans/buffer/SID which contains the troubled register, an example SAPKNNNNNN. First make a backup of that file before removing registers.
2) You have removed registers from the two tables: PAT01 (PATCH=SAPKNNNNNN), and PAT03 (PATCH=SAPKNNNNNN)
3) Invoke the trx SAINT
4) Installation package-->load package --> from application server
5) Select the uploaded SP and click the button Continue.
6) Anything else.
Appreciate in hearing from your input.
Rodolfo

Kernel upgrade having ABAP+JAVA instance

Hi team,
Can you provide the procedure how to kernel upgrade for our windows system having ABAP+JAVA instance releae version 700.
Provide the links, your replies are very helpful.
Regards
Bhaskar

Hi Bhaskar,
You can use JSPM too in this case. Otherwise if you want to do it the old fashioned way:
> Stop SAP, Database, Saprouter, listeners and all the
related services.
> The location of the kernel is /usr/sap/<SID>/SYS/exe/run
> Take a backup of the files in this location and take a
print out of the ls -ltr (This is needed to give the new files the
correct permissions)
> Overwrite all the new files to the kernel location. The
purpose is to retain the old files for which the new version is not
available.
> The permissions of the file need to be changed as they
were before.
> Restart all the processes. The kernel upgrade is
now done. System
> status will give the newer version of the kernel.>
>
disp+work
Will give the
new Kernel version.
Finding files easily: http://www.easymarketplace.de/KernelPatches.php
Regards,
hemanth

EHP4 upgrade question - ABAP Stack and EA-HR

Hi Experts,
My ABAP stack in the ECC system is at 7.01 SP3.
My EA-HR module is at 600 SP38.
We want to upgrade EA-HR to 604 (EHP4) so that we can benefit from some of the MSS functionality but the question is, what ABAP stack level do I need to be on? Is my current version ok or do I need to upgrade?
Can anyone shed light for me on this matter?
Best,
MM

Hi MM,
You can consult SDN Wiki using the following link:
http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOW%20TO%20GET%20RID%20OF%20SP%20STACK%20MISMATCH%20ISSUES
Hope it will be helpful,
Regards
Christine

Steps for upgrading kernel (ABAP+JAVA)

Hi All,
Could you pls let me know the steps required for upgrading kernel (ABAPJAVA). For ABAP I know the steps but I am confused about (ABAPJAVA) Instance.Recently we faced issues regarding startup of java server after upgrading ABAP stack .
Regards,
Prashant

This question has been asked gazillion of times.... did you do a search before posting?.... obviously not.
Use the Search in the top-right side of the page. You'll be amazed with the amount of info available.
Regards
Juan

Need to upgrade from ABAP

Hi all,
currently working as SAP ABAP consultant and i am planning to move on to some advanced tools like SAP NETWEAVER PI or BI , CRM Technical.
Can any one suggest me the correct one and hot in market and for future purpose.
As i am vexed up with the coding
Thanks
Moved from ABAP, General.
Edited by: kishan P on Dec 28, 2010 1:02 PM

It depends on what you want to work on and what are your future plans ...
SAP NETWEAVER PI is something good to learn

SAP Upgrade issue ABAP-PI Proxy error

Hi Guys,
We have an issue in SAP R3 system after the recent SAP upgrade.
The proxy programs in R3 were using SAP Standard structure in their development.
Standard structure : SAPPLCO_LOG_ITEM_CODE (TYPE SAPPLCO_LOG)
And so after the upgrade, There seems to be a new field added in the above standard structure and hence causing mismatch between the proxy program developed internal structure to the SAP standard structure.
We come to understand that this Standard structure is being used from SAP PI, Software component SAP APPL.
So SAP PI has old SAP standard structure and SAP R3 has new standard structure with additional field.
Can you please suggest how to overcome this issue. We have also raised an OSS ticket to SAP.
Kind Regards
Rajesh.S

Hi Harald,
Thank You for the information. I was able to download SAP_APPL 6.06 content from SAP service market place. Here We have a doubt before importing the new SAP APPL content. In market place downloads under SAP_APPL 6.06 we were able to see few many database downloads with last changed at 3.04.2014.
Our EHP upgrade for SAP_APPL is 6.06 , SP level 0007. So we should download / import the highlighted content version (SAPAPPL60607) in the screenshot from market place or download / import the latest change under SAP_APPL 6.06 download patch ? Kindly let us know.
Best Regards,
Rajesh.S

Unicode upgrade of ABAP code question.

Hi gurus......
I am involved in upgradation tool...
when we are upgrading ec4 to ec6 some pgms are unicode compatable and we will get errors according to unicode format
so when we get those errors can we replace those stmts by our code
for eg.
data fld(6)
ln(8).
describe filed fld length ln.
should be replaced by
describe filed fld length ln in characer mode
like these can we change pgm according to unicode standards.
thanks pls suggest me.
Edited by: suma chandra on Dec 12, 2008 9:43 AM
Edited by: Julius Bussche on Dec 12, 2008 10:01 AM

>
suma chandra wrote:
> Hi we can update the custom pgms with uniocode standards
>
> but hw it can be done we need to know.........
Hi suma,
To make custom programs with unicode standards,
first step--> goto program attributes, then activate "Unicode checks active" checkbox.
second step--> use "UCCHECK" transaction, give your custom program name, it will displays all unicode errors and obsolete function modules(upload,download).
third step--> its more adviceble to use this transaction eventhough u fixed all errors in second step, use "SLIN" transaction, give your program name and execute, it will displays all type of errors and warnings related to that program. As per the client's scope fix the errors and warning.
I worked for over 14 upgrade projects. The above process is the standard process followed by SAP.
Still you are looking for any information related to upgrade please feel free to contact me.
Regards
Arani Bhaskar
Edited by: arani bhaskar on Feb 16, 2009 10:10 AM

Couldnt upgrade the java stack after upgrading the abap to ehp1

Hi
I have upgarded the system to ehp1 but i couldnt continue to upgarde the java stack to 18th patch.The reason is it coudlnt find the file JSPM02P-2-20002796.SCA. I couldnt find this file . i couldnt find only this file JSPM02P_4-20002796.SCA . I tried to put this file in inbox and tried to run the jspm but it is not recognizing this as a valid file and its expecting JSPM02P-2-20002796.SCA. I couldnt find this file can anyone suggest me where i could find this file.
Thanks and Regards
MA.Sreenivasan

When you download the files, be sure to select "Save As File", which next to the "Add to Download Basket" button. Copy that SPStab.xml file to your EPS/in directory. Without that, it won't recognize the files even if they are there.

Upgrade from ERP 5.0 to ERP 6.0 EHP 4 SP5 - phase START_SHDI_FIRST

operating system: iSeries V6R1
(this one is probably for Volker Güldenpfennig...a Happy New Year from Germany!)
SID: AP4
instance number normal: 00
instance number shadow: 08
hostname: ap400c
error in phase MAIN_SHADOW/START_SHDI_FIRST:
shadow instance does not start
effect: The subsystem R3_08 ist started immediately but no process at all appears in WRKACTJOB.
The upgrade program hangs for about 5 minutes and then shows the error message below.
SAP note 525677 is already known but does not help.
error message:
To analyse the errors during start of shadow instance,
       view files 'STARTSFI.LOG' and 'DEVTRACE.LOG'
       in directory '/usr/sap/AP4/upg/abap/log'
       Repeat phase until shadow instance is started
       and you can log on instance number '08'.
STARTSFI.LOG:
BUT: The file DEVTRACE does not exist at all !!!
From previous upgrades I knew that this phase brings quite some trouble so I already did this:
- giving special right *ALLOBJ to user AP408 and AP4ADM (with WRKUSRPRF)
- SAP note 1168235, page 9: file /usr/sap//upg/abap/SYS/global/ms_acl_info
    1.) deleted
    2.) qualified hostname (HOST=ap400c.apetito.de) used
    3.) (HOST=*) used
Before restarting the phase I always ended the subsystem as QSECOFR with ENDSBS SBS(R3_08) OPTION(*IMMED).
showipc 08 shows no entries.
THIS IS THE INTERESTING PART!!!
After some deeper investigation I found this:
In /usr/sap/AP4/upg/abap/bin/SHADOW.TPP there are these lines:
AP4/startsap    = /usr/sap/AP4/upg/abap/AP4/homeshd/ap4adm/startsap SID(AP4) INSTANCE(08) PROFILE
('/usr/sap/AP4/upg/abap/AP4/SYS/profile/START_DVEBMGS08_ap400c') DVEBMGS08
AP4/stopsap     = /usr/sap/AP4/upg/abap/AP4/homeshd/ap4adm/stopsap SID(AP4) INSTANCE(08) WAIT(*YES) WAITTIME(600) DVEBMGS08
but the directory .../homeshd/ap4adm does not exist all (sounds very UNIX-like to me).
I changed the SHADOW.TPP file and used "/usr/sap/AP4/upg/abap/exe/startsap" and "/usr/sap/AP4/upg/abap/exe/stopsap"
but this file seems to be created every time this phase starts.
So I copied the two programs "startsap" and "stopsap" from /usr/sap/AP4/upg/abap/exe to the manually created directory
/usr/sap/AP4/upg/abap/AP4/homeshd/ap4adm
Any ideas? (Maybe the R3INLPGM sucks...?)
Kind regards
Rüdiger Höckel
Edited by: Rüdiger Höckel on Jan 8, 2010 5:39 PM

Rudiger,
Hello from cold Minnesota, USA! We are also upgrading from ERP2004 to ERP 6.0 EHP 4 SP4 on IBM i V6R1 and had a similar START_SHDI_FIRST issue that may be relevant to your problem.
As in your post no shadow system jobs appeared in WRKACTJOB and no DEVTRACE file was created. After after some time an RFC category message was shown in the upgrade GUI but turned out not relevent for us.
A QZSHSH control job launches two (2) SBMJOB commands calling R3INLPGM with parameters to start the shadow instance. In our case these SBMJOB commands were failing because the SAPINLPGM program invoked by this process wasn't found in library SAP<SID>70UP. I copied the missing SAPINLPGM program from library SAP<SID>70U to SAP<SID>70UP and restarted the upgrade GUI and the shadow instance then started as expected without further issue.
If this doesn't solve the problem try temporarily changing your shadow instance ("R3_08") job description (*JOBD) in R3<SID>400 to better trace the failing SBMJOB commands--> CHGJOBD JOBD(R3_08) .... LOG(4 00 SECLVL) LOGCLPGM(YES). Then rerun the upgrade GUI and after the "start failure" message appears check the QEZJOBLOG (or your default) outqueue for the SBMJOB process SAPSTART and SAPSTRSRV joblogs and see why these are not launching correctly.
Also should you run into the "Symbol o4_getpwnam (number xxx) not exported..." obscure error updating tp and retrans to current patch levels in the ECC5 (640) system took care of that issue for us.
HTH and best of luck with your upgrade(s) :>
Scott

Upgrade from ERP 5.0 to ERP 6.0 EHP 4 SP5 phase KX_SWITCH_1

operating system: iSeries V6R1
SID: AP4
instance number normal: 00
instance number shadow: 08
hostname: ap400c
non-unicode system
kernel 6.40 non-unicode -> 7.01 non-unicode
error in phase MAIN_SHADOW/KX_SWITCH_1:
Last error code set:
Error message CPF0006 running 'LODSAPKRN DEV(STMF) MNTPNT(UPG '/usr/sap/AP4/SYS/exe/run') KRNLIB(SAPAP470U) APYR3KRN(NO) USERDEF(NO) ONESTEP(*NO) STATFILE('/usr/sap/AP4/upg/abap/log/APYSAPKRN.LOG')'
note: The mentioned log file is NOT created.
I have uploaded the relevant logs here:
http://www.mediafire.com/?knzmiwgkmzn
Log file KX_SW1.LOG doesn't say that much,
more interesting is file KX_SW1.SAV in which you can see
that the kernel library has been filled with lots of files.
The detail error message can only be seen directly on the iSeries
when looking at the detailed job log of the SAPUP process:
BuildO4affileFromDir: Could not process PASE.SAR successfully.
BuildLibFromDir: Error creating IFS file container in targetlib.
LodSapKit: PANIC: Could not finish library SAPAP470U.
Failed to load first part of SAP kernel.
and before...
a STOPSAPCL
SAPCAR: file 'STOPSAPCL' is inaccessible (broken link)
Then I tried to run the LODSAPKRN command manually as user AP4OFR
but now this user cannot log on anymore:
R3AP4400/R3INLPGM: Cannot determine kernel library for SID AP4 (A.....dd) .
As listed in my previous message (error in START_SHDI_FIRST)
I copied the program SAPINLPGM from library SAP70UP.
After the new error occured I tried the following steps without success:
copied the program R3INLPGM from library SAP<SID>70U to SAP<SID>70UP
on the kernel DVD (that I copied to hard disc) I replaced the files SAPEXEDB.SAR and SAPEXE.SAR (old patch from 2009-04-01)
with SAPnet patch #66
because of SAP note 1178421 I also exchanged ILE.SAR with SAPnet patch #74 at these locations:
   /usr/sap/trans/media/51036769/DATA_UNITS/K_701_N_OS400_PPC64/DBINDEP
and the extracted files ILE_TOOLS (130.492 KB) and iletools (33 KB) at these locations:
   /usr/sap/AP4/upg/abap/exe and /usr/sap/AP4/upg/abap/exenew
Kind regards from Germany,
   Rüdiger Höckel
Edited by: Rüdiger Höckel on Jan 14, 2010 11:05 AM

REMINDER: SID = AP4
in /tmp are two files: SAPEXE.SAR and SAPEXEDB.SAR (SAPnet kernel 701 64bit non-unicode patch #66)
Manually building the kernel library SAPAP470U from scratch is successfull:
as user QSECOFR:
CLRLIB SAPAP470U
CLRLIB QTEMP
ADDLIBLE SAPUP
LODSAPKRN DEV(STMF) MNTPNT('/tmp') KRNLIB(SAPAP470U) USERDEF(YES) LIST('/tmp/parts')
EDTLIBL   (-> remove SAPUP from list, only kernel library in list is SAPAP470U)
FIXR3OWNS LIB(SAPAP470U) OBJ(*ALL)
APYSAP TYPE(*KERNEL) SID(AP4) DSTLIB(SAPAP470U)
NOW the user AP4OFR is able to log on again!
repeating the phase KX_SWITCH_1 leads to this error in process SAPup (iSeries joblog):
(maybe there is a way to ignore the phase???)
Objekt TS000065D7 in R3400 Art *OUTQ wurde gelöscht.
BuildO4affileFromDir: SAPCAR error message processing
/usr/sap/AP4/SYS/exe/run/PASE.SAR:
spooled file: QPRINT -
a KERNELLIB
SAPCAR: error creating file object for XDNXDAAPI (error 100).
Eigentumsrecht für Objekt TS000065D7 in R3400 Art *OUTQ geändert.
Objekt TS000065D7 der Art *OUTQ in Bibliothek R3400 erstellt.
Eigentumsrecht für Objekt GETOBJINF in QTEMP Art *USRSPC geändert.
Verbindung hinzugefügt.
Eigentumsrecht für Objekt GETOBJINF in QTEMP Art *USRSPC geändert.
Eigentumsrecht für Objekt TS000000 in QTEMP Art *USRSPC geändert.
2 Sätze in Datei X26071 in QTEMP kopiert.
Eigentumsrecht für Objekt GETOBJINF in QTEMP Art *USRSPC geändert.
1 Einträge gelöscht. 0 Einträge nicht gelöscht.
Objekt TS000065D7 in R3400 Art *OUTQ wurde gelöscht.
BuildO4affileFromDir: SAPCAR error message processing
/usr/sap/AP4/SYS/exe/run/PASE.SAR:
spooled file: QPRINT -
a KERNELLIB
SAPCAR: error creating file object for XDNXDAAPI (error 100).
Aktuelles Verzeichnis geändert.
BuildO4affileFromDir: Could not process PASE.SAR successfully.
BuildLibFromDir: Error creating IFS file container in targetlib.
LodSapKit: PANIC: Could not finish library SAPAP470U.
Failed to load first part of SAP kernel.
Im Befehl ist ein Fehler aufgetreten.

How to upgrade from Solman 7.0 to 7.0 EHP1?

Hi,
In the SAP note 1169247, it talks about doing the upgrade from 7.0 to EHP1 using SAINT and JSPM. But in the Upgrade Guide SAP Enhancement Package 1 for Solution Manager 7.0 - UNIX Oracle˝, it talks about running the upgrade using an Upgrade MAster DVD.
1. Now is this the same as the EHP installer? If so, why is it not mentioned anywhere in the upgrade guide that we have to use EHPI? If not, what is this Upgrade Master installer?
2. Should I use SAINT/JSPM for the upgrade to solman 7.01?
Your answers to these questions will be highly appreciated.
Thanks,
Ajay

Hi Ajay,
I had the same question a few day's ago.
The difference between these two methods are the word updarte and upgrade.
If you are on Solman 7.0 you have to do a update with SPAM/SAINT.
If you are on Solman 3.0 or something you have to do a upgrade with the master dvds. You can read this on one of the first sites of the upgrade guide.
So you have to use SPAM/SAINT, and the Update Guide for EHP1 Using SPAM/SAINT will help you.
[Update Guide on Marketplace|https://websmp101.sap-ag.de/~sapidb/011000358700000427772009E.PDF]
Regards
Tobias

Upgrading as abap 7.0 to as abap ehp1 7.01 sp5

Similar Messages

Maybe you are looking for