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

Similar Messages

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

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 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.

EP 7.0 SP17 compatibility with BI 7.1 (EHP1)

Hi There,
We are in the process of upgrading our BW 3.5 system to BI 7.1 (7.0
EHP1).
Our Central Portal is running on EP 7.0 with Support Package 17 with
all necessary BI Java Components/SCAs and planning to use Central
Portal for BI i.e without Federated Portal.
Please clarify following with respect to upgrading BI to 7.1 and
leaving Central Portal on EP 7.0 SP17.
1) Can EP 7.0 SP17 integrate with BI 7.1 (EHP1)?
2) What are the limitations without EHP1 on EP 7.0
3) What are the limitations without Federated Portal?
We would appreciate your comments on this.
Regards
Chandu

hi,
can you look at this
[BI upgrade|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7?overridelayout=true]
Regards,
Muralidhar

Upgrade Enterprise Portal from EHP1 SP5 to EHP2 SP7

How do we upgrade from EHP1 SP5 to EHP2 SP7 ?
Can we do that directly from JSPM or i should go with ehpi ?
Just download all the files of EHP2 SP7 to EPS/in directlry and start JSPM ?
or
Upgrade EHP1 to SP5 then run PREPARE tasks from the DVD's then apply the SP's.
Let me know your thoughts.
Thanks

Hi Markus,
I've upgraded Standalone JAVA stack from EHP1 -> EHP2 and basically, what EHPI did was just call up JSPM and perform the upgrade. Therefore, is feasible to upgrade standalone JAVA system via JSPM, of cos generate XML with MOPZ.
also, from sap note 1472520:
8. Question: Can I use JSPM for applying EHPs on JAVA only systems?
Answer:
Yes. On Java standalone systems it makes more sense using JSPM as a standalone tool using 'support package stack' option instead of running EHPI. Whereas on dual stack (ABAP + Java systems) you have to use EHPI with the exception of Solution Manager systems (see SAP note 1245473 for SolMan EHP installations).
Cheers,
Nicholas Chang

RFC destination from XI ABAP engine to 4.5 B system

I tried to create an RFC destination from XI ABAP engine to 4.5 B system.
It does not work and gives an error.
<b>Error Details DETAIL: NiIGetSockName</b>
-Naveen.

Hi Naveen,
First of all try to ping 4.5B system from XI system (Through TELNET)... This is to ensure the connectivity and the access. The error is not a common error, i suppose, So better first we check the phisical connectivity...
Plz. confirm...
Regards,
Audy

Upgrade from SAP BO 3.1 SP3 to SAP BO 3.1 SP5

Hi
We are doing upgrade from SAP BO 3.1 SP3 to SAP BO 3.1 SP5, can you please help in below points
1. How much time does it take to run SP5 upgrade service pack for servers and client tools. The server need to be upgraded only on weekend, is it possible to upgrade in 1.5 days?
2. The OS is Windows 2008 server. what should be the rollback plan in case of upgrade failure ? One of server uses VM image while Production server doesnt have any VM image.
3. If BO client tools are on SP3, can they still connect to BO server components on SP5 - (for interim period when servers are upgraded first)
Thanks
anu

Hi Anu,
1. The upgarde should be completed in 1.5 days for the server and client componenets depending upon the number of servers you have in the cluster . If you are planning for upgarde do it successfully first on TEST , DEV and then proceed with PROD servers
2. The roll back plan includes thebackup of the CMS database , the filestore directory and the complete installation folder . In case of any issue , you can the place the backup . If the servers are on the VM , it is always recommeded to have the snapshot of the images before the upgrade
3. Yes, they can connect to the SP3 servers , but always recommeded to upgarde and have servers and client tools on same patch .
Thanks,
Sneha

Configuration Wizard-NW:BI-AS ABAP(Connectivity of BI and Source System): M

Hi friends,
I´m configuring the (NW: BI - AS ABAP (Connectivity of BI and Source System): Maintain) in NWA using Configuration Wizard.
But there is the error in step (NW: BI - AS ABAP (Connectivity of BI and Source System): Maintain > Scenario UI: NW_BI_ABAP_DEFAULT > Scenario Process: Abap Server Integration to BI > Configuration Process > Configuration Unit: Initialize > Config Unit BI System: Initialize > Customizing: Assign Logical System to Client > Write Customizing data to Table T000)
Below error log:
*Write Customizing data to Table T000*
Description:
Exception in step "WriteProfile_1223390220410"
Exception details : com.sap.tc.lm.ctc.metamodel.exception.ActionExecuteException: Exception during the import of the profile!
State
Step finished with error
Support Information
Type of Action
WriteProfile
Debug Events
WriteProfile:Write Customizing data to Table T000
Library: sap.com/tclmconfig~bs
SourcePath ./com_sap_nw_bi_abap_default_maintain/ext_12064772269223/ext_1206447991146/Process_1207123636083/proc_1196064316796/Process_1204300420808/proc_1204300371034/WriteProfile_1223390220410
Time 2011/11/03 at 15:36:57
Schema content/NetWeaver/Common/Customizing/Clients/T000.xsd
Type : View Maintenance
Input
<TABLE_T000 xmlns:expr="http:/sap.com/ctc/expressions"><T000><MANDT>100</MANDT><LOGSYS>SOLCLNT100</LOGSYS></T000></TABLE_T000>
Schema
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:vma="http://www.sap.com/ctc/vma"
elementFormDefault="qualified"> <xsd:element name="TABLE_T000" type="TABLE_T000"></xsd:element> <xsd:complexType name="TABLE_T000"> <xsd:sequence> <xsd:element name="T000" type="T000"> <xsd:annotation> <xsd:appinfo
source="http://www.sap.com/ctc"> <vma:vmacontext table="T000" isupdate="false"/> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> <xsd:complexType name="T000"> <xsd:sequence> <xsd:element name="MANDT" type="xsd:string"> <xsd:annotation> <xsd:appinfo source="http://www.sap.com/ctc"> <vma:vmaproperty column="MANDT"/> </xsd:appinfo>
</xsd:annotation> </xsd:element> <xsd:element name="LOGSYS" type="xsd:string"> <xsd:annotation> <xsd:appinfo source="http://www.sap.com/ctc"> <vma:vmaproperty column="LOGSYS"></vma:vmaproperty> </xsd:appinfo> </xsd:annotation> </xsd:element
</xsd:sequence> </xsd:complexType> </xsd:schema>
Destination parameters
user : SOLMAN_ADMIN
password : % secure content %
host : cdsolman
sysnr : 01
client : 100
language : en
Stack Trace
Caused by: com.sap.tc.lm.ctc.cul.api.CULServiceException: Exception during the import of the profile!
     at com.sap.tc.lm.ctc.cul.serviceimpl.writeProfile.CULServiceWriteProfileImpl.writeProfile(CULServiceWriteProfileImpl.java:98)
     at com.sap.tc.lm.ctc.cul.serviceimpl.process.WriteProfileControllerImpl.execute(WriteProfileControllerImpl.java:160)
     ... 16 more
Caused by: com.sap.tc.lm.ctc.cul.cpi.context.ConfigurationBrokerException: <Localization failed: ResourceBundle='com.sap.tc.lm.ctc.cul.cpi.CPIResourceBundle', ID='xml_parsing_exception', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key xml_parsing_exception
     at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:79)
     at com.sap.tc.lm.ctc.cul.serviceimpl.writeProfile.CULServiceWriteProfileImpl.writeProfile(CULServiceWriteProfileImpl.java:95)
     ... 17 more
Caused by: com.sap.tc.lm.ctc.provider.vmaprovider.exceptions.VMAProviderBaseException: Incorrect XML
     at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.getDocument(VMAUtil.java:349)
     at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.setXmlValue(VMAUtil.java:250)
     at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeContext(JCOProfileExecutorImpl.java:310)
     at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeChildNode(JCOProfileExecutorImpl.java:183)
     at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeProfile(JCOProfileExecutorImpl.java:129)
     at com.sap.tc.lm.ctc.provider.vmaprovider.VMAWriteProfile.writeProfile(VMAWriteProfile.java:59)
     at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:144)
     at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:73)
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)(:main:, row=1, col=637) -> com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
     at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
     at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:76)
     at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.getDocument(VMAUtil.java:341)
Caused by: com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)
     at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:209)
     at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207)
     at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143)
All the others steps were finished successfully
Only this step is with error. I don´t know that to do.
Regards,
Ricardo Arriado
Edited by: Ricardo Arriado on Nov 4, 2011 6:24 PM

Hi,
Please double check the JCO user and the authorization.
Or
Apply these two notes, it should resolve ur issue
1493124 CTC: Check table existence before table whitelist
1471762 CTC: Automated Configuration:
Hope this helps u.
Best Regards
Vijay K

HT1338 How can I upgrade my MacBook Pro from OS X 10.5.8 to most recent Operating System ?

How can I upgrade my MacBook Pro from OS X 10.5.8 to most recent Operating System ?
I just bought a Ipad Air and realized than my MacPro does not support Icloud.

Upgrade Paths to Snow Leopard, Lion, Mountain Lion, or Mavericks
You can upgrade to Mountain Lion or Mavericks from Lion or directly from Snow Leopard. Mountain Lion can be downloaded from the Mac App Store for $19.99. To access the App Store you must have Snow Leopard 10.6.6 or later installed.
Upgrading to Snow Leopard
You can purchase Snow Leopard through the Apple Store: Mac OS X 10.6 Snow Leopard — Apple Store (U.S.). The price is $19.99 plus tax. You will be sent physical media by mail after placing your order.
After you install Snow Leopard you will have to download and install the Mac OS X 10.6.8 Update Combo v1.1 to update Snow Leopard to 10.6.8 and give you access to the App Store. Access to the App Store enables you to download Mountain Lion if your computer meets the requirements.
     Snow Leopard General Requirements
       1. Mac computer with an Intel processor
       2. 1GB of memory
       3. 5GB of available disk space
       4. DVD drive for installation
       5. Some features require a compatible Internet service provider;
           fees may apply.
       6. Some features require Apple’s iCloud services; fees and
           terms apply.
Upgrading to Lion
If your computer does not meet the requirements to install Mountain Lion, it may still meet the requirements to install Lion.
You can purchase Lion by contacting Customer Service: Contacting Apple for support and service — this includes international calling numbers. The cost is $19.99 (as it was before) plus tax. It's a download. You will get an email containing a redemption code that you then use at the Mac App Store to download Lion. Save a copy of that installer to your Downloads folder because the installer deletes itself at the end of the installation.
     Lion System Requirements
       1. Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7,
           or Xeon processor
       2. 2GB of memory
       3. OS X v10.6.6 or later (v10.6.8 recommended)
       4. 7GB of available space
       5. Some features require an Apple ID; terms apply.
Upgrading to Mountain Lion or Mavericks
To upgrade to Mountain Lion or Mavericks you must have Snow Leopard 10.6.8 or Lion installed. Purchase and download Mountain Lion or Mavericks (Free) from the App Store. Sign in using your Apple ID. Mountain Lion is $19.99 plus tax. The file is quite large, over 4 GBs, so allow some time to download. It would be preferable to use Ethernet because it is nearly four times faster than wireless.
     OS X Mountain Lion — System Requirements
       Macs that can be upgraded to OS X Mountain Lion
         1. iMac (Mid 2007 or newer) — Model Identifier 7,1 or later
         2. MacBook (Late 2008 Aluminum, or Early 2009 or newer) —
             Model Identifier 5,1 or later
         3. MacBook Pro (Mid/Late 2007 or newer) — Model Identifier 3,1 or later
         4. MacBook Air (Late 2008 or newer) — Model Identifier 2,1 or later
         5. Mac mini (Early 2009 or newer) — Model Identifier 3,1 or later
         6. Mac Pro (Early 2008 or newer) — Model Identifier 3,1 or later
         7. Xserve (Early 2009) — Model Identifier 3,1 or later
To find the model identifier open System Profiler in the Utilities folder. It's displayed in the panel on the right.
Are my applications compatible?
         See App Compatibility Table — RoaringApps.
     For a complete How-To introduction from Apple see Upgrade to OS X Mountain Lion.

I upgraded to Mavericks and now some of my utilities --- such as disk utility and system information no longer work.

I upgraded to Mavericks and now some of my utilities --- such as disk utility and system information no longer work. I find Disk Utility useful and would like to have it. Doesn't Makericks include

Boot into your recovery partition (restart, hold down ⌘R until you see the Apple logo), and use Disk Utility to repair your hard drive. Repair permissions too while you're there. OS X: About OS X Recovery
If that doesn't work, I'd reinstall Mavericks over your current installation.

Creating ABAP proxy on a 6.2 system

I've been trying to get my head round how ABAP proxies work, and I've got as far as realising I need to create an ABAP proxy on a system running WAS 6.2.
The problem is that it doesn't seem to work - although SPROXY appears to be ok, there is apparently no way it can connnect to the Integration repository. Digging around in the code seems to reveal that it's somewhat out of date - it constructs the wrong url to get at the IFR for a start.
Is there something that's supposed to be installed so that SPROXY can communicate with the IFR on our XI system?

Hi,
have u applied,
1) APPINT 200_620 patch
2) WebAs 6.20 kernel patch level 1253
Also u should configure ur SAP System to communicate with XI server.Check the followign program to test if your SAP system is configured preperly to connect to XI Server...?
1.Check/maintain with report: SPROX_CHECK_IFR_ADDRESS
2.Check with report SPROX_CHECK_HTTP_COMMUNICATION
3.Check with report SPROX_CHECK_IFR_RESPONSE
4.Check with report SPROX_CHECK_IFR_CONNECTION
By the way u can refer to the weblog.. creating ABAP Client Proxies in WebAs6.40 system.
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Cheers,
Siva Maranani.

Why can't I send my files. Asking me to upgrade, but upgrading not needed. Even if i do try to upgrade it won't advance. What's up??? Is your system down???

Why can't I send my files. Asking me to upgrade, but upgrading not needed. Even if i do try to upgrade it won't advance. What's up??? Is your system down???

Hi anthony yerger,
Please let me know what Acrobat and OS version are you using.
How are you trying to send your PDF files?
If possible, please share the screenshot of the error message so that I can analyze it at my end.
Regards,
Anubha

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

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

Similar Messages

Maybe you are looking for