Support Package problem in Solution Manager 7 / NW 700

Hi ,
Once again I need your help. The scenario is :
I want to upgrade the SAP_BASIS from SP11 to SP16 but it is stopped at ADD-ONS_CONFLICT_ phase. Then I note down the CRT required for the SP and uncar it to /usr/sap/trans/EPS/in and uploaded via SPAM but again the SAP_BASIS stuck at same step.
Next Resetted SPAM queue --> again uncar SAP_BASIS and ST 400 --> uploaded --> tried to define the queue --> Error message "No Valid Queue for SAP Basis rel 700"
I also tried to apply ST 400 from SAINT --> start --> continue/back/load ( in this screen no add on to be applied found but all the addon SP is successfully uploaded) --> if i press continue --> error message "no add on package found"
Please guide me.
Regards,
Partha Sarathi Hazra

Not really a portal question. Maybe you should ask in one of the ABAP forums?

Similar Messages

How to download Support Package without using Solution Manager

Hello Guru,
I am planning to upgrade our Netweaver System to SP12, which is released after Apirl 2007, now SAP AG requires Solution Manager to approve the SP download request, then I can use SAP Download Manager to download basket.
Is there any way to walk around? because we don't have a configured Solution Server.
Thank you

Hi,
You can try to complain to SAP but I am very doubtful this will change their mind.
This the way SAP found to set SOLMAN mandatory. I think this is ridiculous as the customers should always be the ones making the choices and not the suppliers...
There is absolutely no added value from SOLMAN to download the support packages...
Regards,
Olivier

Error when undate solution manager from 700 to 701(700 enp1)

Hi all,
error when undate solution manager from 700 to 701(700 enp1),error:OCS package SAPKITL428 does not match the current software component vector.
My current supportstack is as follows :
SAP_ABA 700 0016 SAPKA70016
SAP_BASIS 700 0016 SAPKB70016
PI_BASIS 2005_1_700 0016 SAPKIPYM08
ST-PI 2008_1_700 0002 SAPKITLRD1
SAP_BW 700 0018 SAPKW70018
SAP_AP 700 0014 SAPKNA7014
BBPCRM 500 0012 SAPKU50012
CPRXRPM 400 0014 SAPK-40016INCPRXRPM
ST 400 0017 SAPKITL427
ST-A/PI 01L_CRM570 0000 -
ST-ICO 150_700 0017 SAPK-1507KINSTPL
ST-SER 700_2008_1 0005 SAPKITLOO5

Hi,
Because prerequisite to apply this package is not met. To apply this package below is the prerequisite which i can see in your package level is not met:
Support Packages
Package      Value
SAPKU50012      T
SAPK-70401INBICONT      T
SAPK-40013INCPRXRPM      T
SAPK-50001INCRMUIF      T
SAPKA70102      T
SAPKNA7012      T
SAPKB70101      T
SAPKB70102      T
SAPK-701DHINSAPBASIS      T
SAPKITL427
Thanks
Sunny

Problem installing SOLUTION MANAGER in db2

Dear consultans;
I have a problem installing solution manager in db2.
In phase 'Import ABAP' the sapinst shows the following message:
Execution of the command "/usr/sap/SOL/SYS/exe/run/R3load -testconnect" finished with return code 2. Output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20080826111928
/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#16 $ SAP
/usr/sap/SOL/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled May 5 2008 21:32:44
/usr/sap/SOL/SYS/exe/run/R3load -testconnect
DbSl Trace: DbSlConnect to 'SOL' as 'sapsol' failed
(DB) ERROR: db_connect rc = 256
DbSl Trace: DbSlConnect to 'SOL' as 'sapsol' failed
(DB) ERROR: DbSlErrorMsg rc = 29
/usr/sap/SOL/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20080826111930
ERROR      2008-08-26 11:19:30.422
           CJSlibModule::writeError_impl()
CJS-30023 Process call '/usr/sap/SOL/SYS/exe/run/R3load -testconnect' exits with error code 2. For details see log file(s) R3load.e
xe.log.
ERROR      2008-08-26 11:19:30.748 [sixxcstepexecute.cpp:951]
FCO-00011 The step testDatabaseConnection with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_Cr
eateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|testDatabaseConnecti
on was executed with status ERROR ( Last error reported by the step :Process call '/usr/sap/SOL/SYS/exe/run/R3load -testconnect' exi
ts with error code 2. For details see log file(s) R3load.exe.log.).
The file R3load.exe.log show the following..
(root)sidtsmp:/install/instalacion> more R3load.exe.log
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20080826111928
/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#16 $ SAP
/usr/sap/SOL/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled May 5 2008 21:32:44
/usr/sap/SOL/SYS/exe/run/R3load -testconnect
DbSl Trace: DbSlConnect to 'SOL' as 'sapsol' failed
(DB) ERROR: db_connect rc = 256
DbSl Trace: DbSlConnect to 'SOL' as 'sapsol' failed
(DB) ERROR: DbSlErrorMsg rc = 29
/usr/sap/SOL/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20080826111930
And if I do the following sentence it's finished ok
sidtsmp:db2sol 6> db2 connect to SOL
   Database Connection Information
Database server        = DB2/AIX64 9.1.4
SQL authorization ID   = DB2SOL
Local database alias   = SOL
(root)sidtsmp:/sapmnt/SOL/exe> su - db2sol
sidtsmp:db2sol 1> db2 connect to SOL user sapsol
Enter current password for sapsol:
   Database Connection Information
Database server        = DB2/AIX64 9.1.4
SQL authorization ID   = SAPSOL
Local database alias   = SOL
I reboot the server and now the sentence finished wrong.
sidtsmp:db2sol 8> db2 connect to SOL user sapsol
Enter current password for sapsol:
SQL30082N Security processing failed with reason "15" ("PROCESSING FAILURE").
SQLSTATE=08001
sidtsmp:db2sol 9>
Any suggestion?
Best regards,
Julene

Hi Julene.
Just one suggestion really,....
post the question on the Solution Manager forum
Chrs, M

XPRA_EXECUTION error while importing Support stack 8 in Solution manager 4

We have installed Solution managr 4.0 on Windows 2003 OS. We are trying to inport support stack 8, but we are getting the XPRA_EXECUTION error while importing SAPKW70009. Following is the error log
Short text
Syntax error in program "CL_RSOBJS_TYPE_MANAGER========CP ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLRSVERS" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_RSOBJS_TYPE_MANAGER========CP " in include
"CL_RSOBJS_TYPE_MANAGER========CM00G " in
line 1:
"Method "GET_TEXT_OF_SEARCH_ATTRIBUTE" does not exist. There is, howeve"
"r a method with the similar name "GET_SEARCH_ATTRIBUTES"."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "CL_RSOBJS_TYPE_MANAGER========CP
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following syntax error was found in the program
CL_RSOBJS_TYPE_MANAGER========CP :
"Method "GET_TEXT_OF_SEARCH_ATTRIBUTE" does not exist. There is, howeve"
"r a method with the similar name "GET_SEARCH_ATTRIBUTES"."
We have tried clearing the queue and restarting the import but it does not work.
Can anyone please help us with the same.

Please, i need help. I have a problem when importing SAPKB62030 on phase XPRA_EXECUTION. This is the error:
The import was stopped, since an error occurred during the phase
XPRA_EXECUTION, which the Support Package Manager is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem:
-   Error in phase: XPRA_EXECUTION
-   Reason for error: TP_STEP_FAILURE
-   Return code: 0008
-   Error message: OCS Package SAPKB62030, tp step R, return code
          0008
What can i doing?

Support Package Problem

Hi Experts,
While applying the support package of BASIS (KB70012) and ABAP (KA70012) in SAP ECC 6.0.we get the following error.
The import was stopped, since an error occurred during the phase
DDIC_ACTIVATION, which the Support Package Manager is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem:
 - Error in phase: DDIC_ACTIVATION
 - Reason for error: TP_CANNOT_CONNECT_SYSTEM
 - Return code: 0230
 - Error message: Cant create any process
When I go through the command mode and type tp connect <sid> & tp connect <sid> pf=g:\usr\sap\trans\bin\ TP_DOMAIN_S10.PFL
Its give the following error.
G:\usr\sap\trans>tp connect S10
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
This is tp version 372.04.04 (release 700)
E-TPSETTINGS could not be opened.
EXIT
ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.
Error in TPSETTINGS: transdir not set.
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)
G:\usr\sap\trans>tp connect S10 pf=G:\usr\sap\trans\bin\TP_DOMAIN_S10.PFL
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
This is tp version 372.04.04 (release 700)
Connection to Database of S10 was successful.
punesrv02\usr\sap\trans\tmp\C071023.S10 for transport: ALL: No such file or di
rectory
punesrv02\usr\sap\trans\tmp\SLOG0743.S10.LOC: No such file or directory
PANIC --> exiting
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0212
tp finished with return code: 212
meaning:
could not access file as supposed (see dev_tp or SLOG0743.S10 for more details
Please help me.

Hi Sateesh,
It seems like your transport management system is not configured properly, Just check your CTS. is it configured properly.
Check your transport directory too.
when you imort a support patch it creates a file in this location. this message are co,img that means you transport directory is not configured properly.
\punesrv02\usr\sap\trans\tmp\C071023.S10 for transport: ALL: No such file or di
rectory
punesrv02\usr\sap\trans\tmp\SLOG0743.S10.LOC: No such file or directory
Regards
Subhash

Support desk queries on solution manager

Hi All
I have few queries on solution manager support desk functionality.
1.Is this the only way to create support desk message HELP-CREATE support desk Message from each individual system??
2.In our scenario,when we are creating the message we would like to assign component( it should be project specific component,not SAP specific component)...How to acieve this??
3.We have a requirement where the message has lot of status and fields and depending on the message processor I would like to control which status or field user should be able to view and work on...how to achieve this??
4.Need the way to send a message to the processor,as soon as his name appear as message processor.
5.I want to track all the persons involved in the message processing,how can I do this??
6.I want to use a different transaction type not the standard SLFN,so what configurations are needed??When I create a message it should automatically take properties of transaction type of newly created one??

Hello Dolores,
first of all thanks for that answer. I read it in the germany documentation help.
Here an extract:
+Anlegen von Support-Meldungen über NOTIF_CREATE
Mit der Transaktion NOTIF_CREATE können Benutzer, die in Satellitensystemen arbeiten, Meldungen anlegen und an den SAP Solution Manager versenden.
Vorgehensweise
Starten Sie Transaktion NOTIF_CREATE.
Geben Sie folgende Werte im Dialogfenster Anlegen einer Support Meldung ein:
Priorität
System/IBase-Komponente
Kurz- und Langtext
Um Anlagen anzuhängen, wählen Sie Registerkarte Anlagen.
Sichern Sie Ihre Eingaben.
Ergebnis
Sie haben eine Support-Meldung angelegt.+
Yesterday I search the internet for a note, but I didn't find one. So I'am happy now.
But now the next problem occurs. My next issue is about the SLD. The system cannot get the data from the satellites. I'am not sure, but I think our SLD isn't perfectly configuried. Do you have an "How To" or something like that?
regards
marc

Early Watch Alerts Problem in Solution Manager

Hello,
I am trying to configure EWA for my SAP R/3 systems in Solution Manager 3.2. RFC connections are working fine. EWA report that is getting generated is showing me following problem :
EarlyWatch Alert - R/3 System**********
Download Problem
We could not perform a correct analysis because essential parts of the download data are missing. The cause is probably a problem with data collection or transfer.
Recommendation: Please check the log for this session in the Service Data Control Center (execute transaction SDCC or the new SDCCN in your system). If an error entry is listed, perform the Service Preparation Check.
Implementation: To perform the Service Preparation Check, execute transaction SDCC and choose Information-> Service prep. check or if you use SDCCN create a new task 'Service Preparation Check'.
The result of Service Preparation check ( as recommended) is not throwing any error.
Can anyone help me out on this.
Regards,
Yashodhan

Hello Yashodhan Mujumdar,
we have warnings about differences in the function interface, but all works, so we ignore them.
But the missing data interface seems to be the error.
Did you read note 781680?
Do you have the newest ST-PI (2005_1_xxx SP3) and ST/A-PI (01G_xxx, this is an installation, no patch)? Do you have the right flavour of ST/A-PI?
Are ST03N and ST06 working?
Do you refresh service definitions from sapnet? Did you generate (after service refresh) on the solution manager system the includes (SPRO -> SAP Solution Manager -> Basic settings -> SAP Solution Manager System -> Operations -> Setup Service Data Control Center -> Generate Includes....
If these checks are all ok you might deactivate SDCCN both in satellite system and solution manager (SMSY -> Goto -> Solution Manager Operations -> Administration SDCCN) and activate it again.
If this doesn't work you might use the big hammer:
1) delete all the service definitions in satellite system like described in note 727998
2) delete all entries in table /BDL/_GENER (satellite system)
3) create in SolMan system a new session in order to collect and send data for this session in satellite system; if you don't see the session in the satellite system please execute there the "Maintenance Package"
4) elaborate the data for this new session in SolMan system
If all this doesn't help, open a message in sapnet
Bye
Message was edited by: Riccardo Escher

Big Problem With Solution Manager EHP1 ?

Dear all,
I have already installed SAP Solution Manager EHP1, after the installation sucessfuly. I check the function: Project Administration ( T code : Solar_Project_Admin), then select New project button.
The program inform that:
"Runtime Errors: Message Type Unknow
What happened:
Error in ABAP Application program
The current ABAP program "SAPLSPROJECT_SYSTEM_LANDSCAPE" had to be terminated because
it has come across a statement that unfortunately cannot be excuted.
etc
Do you know about this problem, what is the errors ?
Thanks all.

Dear all.
With Solution Manager EHP1
SAP Basis: SAPKB7001-SAPKB70016, SAPKB70101-SAPKB70102
SAP ABA: SAPKA7001-SAPK70016, SAPKA70101-SAPKA70102
Detail log as below:
Runtime Errors MESSAGE_TYPE_UNKNOWN
Date and Time 28.04.2009 16:47:15
Short text
Message type " " is unknown.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSPROJECT_SYSTEM_LANDSCAPE" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Only message types A, E, I, W, S, and X are allowed.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_UNKNOWN" " "
"SAPLSPROJECT_SYSTEM_LANDSCAPE" or "LSPROJECT_SYSTEM_LANDSCAPEU28"
"SPROJECT_SYSL_CHECK_CENTRAL_SY"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Information on where terminated
Termination occurred in the ABAP program "SAPLSPROJECT_SYSTEM_LANDSCAPE" - in
"SPROJECT_SYSL_CHECK_CENTRAL_SY".
The main program was "SAPLS_IMG_TOOL_5 ".
In the source code you have the termination point in line 29
of the (Include) program "LSPROJECT_SYSTEM_LANDSCAPEU28".

Problem with Solution Manager wanting to adjust its own instance

I have a situation where under my landscape components --> systems in SMSY where I have a "yellow" exclamation point in a box that says "newer version exists" for my existing solution manager. When I try to adjust, it doesn't let me select the system because they are on the same host. Therefore, I can't do the adjustment. What is the problem? Any ideas how I can do this adjustment? Thanks. This is very important. Thanks.,

Thanks Ragu. I've dug a little deeper and this is what is happening when I try to assign the Solution Manager instance to a logical component:
I receive an "instance
adjustment required" message for the actual solution manager instance
itself, so I had to manually set the product and set it to leading as
leading (even though there was no other solution manager instance).
This means that the solution manager system itself is set to manual
adjustment. I've gotten it to read from the SLD, but it is still acting as though it is missing a NetWeaver ABAP Server on the same host as the Solution Manager.
Here is what I do to get the above issue to reproduce:
I've done more trouble shooting and found that if I go to installed product versions in the Solution Manager System and click on Clean-up Inconsistencies, I get
the attached screenshot showing that a Product SAP NetWeaver with main instance "Application Server ABAP" is inconsistent (on the same server as the Solutiion Manager instance, the Solutioni Manager instance doesn't show up in the System landscape either). Cleaning up the inconsistency doesn't fix the problem (leaves Application Server ABAP) in place. Meaning when I try to fix the inconsistency it won't let me. Thanks for any help, I really need to figure this out. Thanks.

Ccmsping registration problem in Solution manager

hi,
I am installing CCMSPING agent to check "System Availability" from Solution Manager.
In our system ladscape we have multiple systems on sigle host. for eg) TP7 & DW1 on single host cpafisb8.
I have successfully registered the CCMSPING agent in Solman.
I have followed the Availability doc for registeration CCMSPING. Following are the major steps that i have done:
1)Download & extract CCMSAGENT from market place.
2)Configuration of Central Monitoring system.
3)Registration of CCMSPING using command u201Cccmsping -push -Ru201D.
4)Configured Availability Monitoring in Central System (i.e. Solution Manager) in RZ21.
As result i can see the stellite sytem node in RZ20 under " SAP CCMS Monitor Templates-->Availability and Performance Overview".
When i go to transaction "solman_workcenter" in tab "System Landscape management", i can see the staus of system as Green for the system i registered.
Now, the problem i facing in in transaction solman_workcenter is described as follows:
As i mentioned We have multiple systems on single host, for eg) TP7 & DW1 are on the same host "cpafisb8",
hence if CCMSPING has been registered for TP7 the status is green for DW1 too even if DW1 has no entry in RZ21.
Strange thing is DW1 was showing.
I have tried following three options to make the status correct in solman_workcenter:
1) I have maintained hostname for TP7 as "TP7.afis.chevrontexaco.net" which is alias for
hostname cpafisb8 in RZ21 & SMSY & status is correctly showing green for TP7 but still for DW1 which is not defined in RZ21, status is showing green.
2)I have unregistered the CCMSPING fron TP7. TP7 status has been changed to gray but strange thing happeneing was DW1 status was still green even no ccmsping process was running on the DW1 host.
3)I have registered the CCMSPING for TP7 with its central instance profile options using command:
ccmsping -R -push -n31 pf=/usr/chevron/TP7/profile/TP7_DVEBMGS31_cpafisb8
and agin configured TP7 in solution manager & status changed gray to green for TP7, but no change happening in DW1 status.
Can anyone please help on this strange behavior of Solman_workcenter.

Hi,
Thanks for he reply..
But i have already followed the process that you described or CCMSPING registration. and CCMSPING is transfering the data successully from satellite system to solution manger.
And as result of successul registration i can see the status of that satellite system as green in transaction "solman_workcenter".
But as i described earlier we have multiple systems registered on single host.for eg)SY1 & SY2 on host1
Hence even though the CCMSPING is not registred for SY2 & only registered or SY1 on host1 with RZ21 configuration in solution manager for SY1; SY2 status is also shown green in transaction solman_workcenter.
I want that only status of SY1 should be shown as green in solution manger under transaction "solman_workcenter".
I hope you understood the issue.
thanks

OCS problem in Solution manager 4.0

Hi All,
When i import sap patch for PI Basis on Solution manager 4.0,
Its imported successfully, but Status Bar in OCS shows me "is obsolete".
when i tried to Define que, I am getting msg. "OCS package SAPKIPYJ78 does not match the current"
Please suggest .
Thanks in Advance...
Regards
Gyan

thanks

Retrieve all Support Ticket Numbers from Solution Manager

Hi All,
I am developing a small custom program which is in Solution Manager version 4.0. So for that program i need to fetch all NOT CONFIRMED support tickets in to Z program.
How can i fetch all support ticket numbers ? Any function modules are exist ?
Thanks in Advance.
Regards,
Ranjith

That application comes on different server CRM.
You can't call that RFC in R/3.
You have to developed a code such that call the RFc on CRM(soultion manager server) and retrive all require data to ur server in alv.
Regards
ricky

SAP Upgrade Assitant Support Package Problem 4.7 to ECC 6

Hi all,
Doing an upgrade from 4.7E to ECC 6. Does anyone know what should be the minimum patch level to start upgrade. Basis and Abap Supp. pack is on level 60. HR is on 61. But after starting prepare, it is giving error in version check phase. It is saying Upgrade Assitant the start release configuration is not supported. SAP_ABA : 620
SAP_APPL : 470
SAP_BASIS : 620
SAP_HR : 470
Infact all the support packages are at this level however the kernel is upgraded to 640 patch level 43.
If anyone has the info please help.. If ignored the upgrade assistant ask VALCHK_INI password which searched is nowhere found.
Kindly help.
Regards,
Valvan

Hello,
Thanks Eric I had already checked and they are above what is the minimum support pack level for eg SAP_BASIS requires minimum 41 support pack level and i have installed 61. Everything is according or more than the prerequisite requirement. Is this is a database version problem. Shall i go to upgrade oracle first as of now i am on 9.2.0.6.
Regards,
Shekhar Kulkarni

Support pack 12 for solution manager 4.0

Hi,
We are on Patch level 10 and want to go to 12 on solution manager 4.0. do we need to download the patches from service market place or do we need to use the maintenance optimizer in DSWP. if so I don't see any solution manager except the satelliate systems.
Some one please let me know?
Thanks,
Chander

You need both
You Solution Manager needs to be added as system in SMSY so you will see it in Maintenance Optimizer.
The other way of downloading patches is, step to http://service.sap.com/patches, use the "Support Stack" entry, select all and put all to the download basket. Then use any system that you have in MO and "confirm" the basket and then cancel the whole procedure. Your items will be confirmed and you can download them with the Download Manager.
Markus

Support Package problem in Solution Manager 7 / NW 700

Similar Messages

Maybe you are looking for