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

Similar Messages

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

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.

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

Problems with Solution Manager Graphics

We are in the process of installing Solution Manager 4.0. When we go to transactions SOLUTION_MANAGER and select a solution from the Solution Overview, none of the menus or menu graphics on the lower right side of the screen display. We get a red error icon on the bottom of the screen, but no error message. Similarly, none of the graphics display under SOLMAN_DIRECTORY.
We've tried all of the actions defined in Note 834832.
- All of the BSP's were activated in SICF.
- The defaultUser alias is created.
- We know that the hostname is correct because SOLUTION_MANAGER_BSP starts.
- We've confirms that IGS is loaded and works by running an IGS test program.
- We've tested the RFC connection to IGS.
Does anyone have any ideas of how we can further tear this problem apart in order to find out where the failure is happening?
I think the defaultUser alias may be the problem. Is there some way I can verify this alias from a browser or trace its execution?

SOLUTION_MANAGER_BSP has the same problem as SOLUTION_MANAGER.
We looked at SMICM and couldn't see anything obviously wrong. Nothing obviously wrong in the log. Is there something in particular we should be looking for in SCICM?
I'm looking for some sort of log that could actually show the requests running the actual BSP's. I don't see that in SMICM.
Any further ideas would be appreciated.

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

Installation problem with Solution Manager 4.0 on Windows 2003/Oracle 10.2

Hello,
I'm receving the following error message while running SAPinst on step 11 Create Database:
ERROR 2007-05-31 23:20:32
CJS-00084 SQL statement or script failed. DIAGNOSIS: Error message: ORA-955 for defaultdest
OLUTION: See ora_sql_results.log and the Oracle documentation for details.
ERROR 2007-05-31 23:20:32
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
ERROR 2007-05-31 23:20:32
FCO-00011 The step runCatprocSql with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0|runCatprocSql was executed with status ERROR .
I've read the log file referenced above and did not find any additional details.
I'll post the entire log below as well:
INFO 2007-05-31 15:05:44
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.4.xml'.
INFO 2007-05-31 15:05:45
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.5.xml'.
INFO 2007-05-31 15:05:52
Execute step
Component W2K_ServicePack_Check|ind|ind|ind|ind
Preprocess of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
INFO 2007-05-31 15:06:11
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/keydb.3.xml'.
INFO 2007-05-31 15:06:11
Execute step runCatprocSql of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0.
INFO 2007-05-31 15:06:16
Removing file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\ora_query3_tmp0_1.sql.
INFO 2007-05-31 15:06:16
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\ora_query3_tmp0_1.sql.
INFO 2007-05-31 15:06:18
Switched to user: sm1adm.
INFO 2007-05-31 15:06:18
Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2007-05-31 15:07:03
Switched to user: sm1adm.
INFO 2007-05-31 15:07:06
Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
ERROR 2007-05-31 15:21:34
CJS-00084 SQL statement or script failed. DIAGNOSIS: Error message: ORA-955 for defaultdest
SQL> Rem bnainani 11/29/00 - specify compatible=8.0 for create_queue_table
SQL> Rem liwong 10/20/00 - add def$_destination.flag
SQL> Rem bnainani 11/15/00 - specify compatible=8.0 for queue table
SQL> Rem narora 09/13/00 - add comment on new def$_destination columns
SQL> Rem liwong 09/01/00 - add master w/o quiesce: fixes
SQL> Rem liwong 07/12/00 - add total_prop_time_lat
SQL> Rem liwong 06/29/00 - add total_txn_count, total_prop_time
SQL> Rem liwong 05/17/00 - add_master_db w/o quiesce
SQL> Rem jstamos 05/17/00 - add_master_db w/o quiesce
SQL> Rem elu 01/24/00 - add column apply_init to def$_destination
SQL> Rem alakshmi 12/02/99 - Bug 979398: Before-row insert trigger on
SQL> Rem def$_propagator
SQL> Rem wesmith 10/31/98 - change shape of table def$_pushed_transactions
SQL> Rem jnath 02/23/98 - bug 601972: split anonymous pl/sql blocks
SQL> Rem wesmith 01/21/98 - create def$_pushed_transactions table for
SQL> Rem server-side RepAPI
SQL> Rem nbhatt 07/27/97 - change create_queuetable -> create_queue_table
SQL> Rem nbhatt 04/21/97 - change 'TRACKING' in CREATE_QUEUE to 'DEPENDENCY
SQL> Rem nbhatt 04/21/97 - change syntax of create_queue
SQL> Rem liwong 04/16/97 - Alter view system.AQ$DEF$_AQ{CALL,ERROR}
SQL> Rem liwong 04/11/97 - Fixing defaultdest_primary typo
SQL> Rem jstamos 04/10/97 - remove unneeded indexes
SQL> Rem nbhatt 04/08/97 - change create_qtable to create_queuetable
SQL> Rem jstamos 04/04/97 - tighter AQ integration
SQL> Rem liwong 04/02/97 - Add schema_name, package_name in def$_calldest
SQL> Rem ato 03/31/97 - create_qtable interface change
SQL> Rem liwong 03/25/97 - remove batch_no from def$_tranorder
SQL> Rem liwong 02/24/97 - pctversion --> 0 for def$_aqcall, def$_aqerror
SQL> Rem liwong 02/22/97 - Remove dropping view aq$def$_aqcall
SQL> Rem ademers 02/07/97 - Remove constraint def$_calldest_call
SQL> Rem liwong 01/11/97 - drop and create aq$def$_aqcall (temporary)
SQL> Rem liwong 01/10/97 - Alter view aq$def$_aqcall
SQL> Rem liwong 01/07/97 - Alter default value for batch_no
SQL> Rem jstamos 12/23/96 - change temp$nclob col
SQL> Rem jstamos 11/21/96 - nchar support
SQL> Rem sjain 11/11/96 - Remove dummy buffer # comment
SQL> Rem asgoel 11/05/96 - Disable misc_tracking in def$_aqerror
SQL> Rem sjain 11/06/96 - deferror changes
SQL> Rem vkrishna 10/28/96 - change STORED IN to STORE AS for lob
SQL> Rem sjain 10/02/96 - Aq conversion
SQL> Rem sbalaram 09/24/96 - ARPC performance - add foreign key index
SQL> Rem jstamos 09/06/96 - rename temp$lob and temporarily change nclob
SQL> Rem sjain 09/03/96 - AQ converson
SQL> Rem ademers 08/02/96 - queue_batch default in def_destination
SQL> Rem ademers 07/29/96 - queue_batch default in def_call
SQL> Rem ademers 07/29/96 - queue_batch default
SQL> Rem jstamos 07/24/96 - add system.temp$lob
SQL> Rem sbalaram 07/22/96 - create def$_aqcall and def$_aqerror tables
SQL> Rem jstamos 06/12/96 - LOB support for deferred RPCs
SQL> Rem ldoo 06/28/96 - Comment out queue_table from def_tranorder
SQL> Rem ademers 05/30/96 - create def_origin
SQL> Rem ademers 05/28/96 - fix def_destination col names
SQL> Rem ldoo 05/09/96 - New security model
SQL> Rem sjain 05/01/96 - add seq col to def_destination
SQL> Rem ademers 04/29/96 - add batch_no, dep_scn to def_call
SQL> Rem jstamos 12/04/95 - 324303: use index to avoid sorting the queue
SQL> Rem jstamos 08/17/95 - code review changes
SQL> Rem jstamos 08/16/95 - add comments to tables
SQL> Rem wmaimone 01/04/96 - 7.3 merge
SQL> Rem hasun 01/31/95 - Modify tables. SOLUTION: See ora_sql_results.log and the Oracle documentation for details.
ERROR 2007-05-31 15:21:34
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
ERROR 2007-05-31 15:21:34
FCO-00011 The step runCatprocSql with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0|runCatprocSql was executed with status ERROR .
INFO 2007-05-31 23:06:17
An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0|runCatprocSql".
INFO 2007-05-31 23:06:18
Removing file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\ora_query3_tmp0_1.sql.
INFO 2007-05-31 23:06:18
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\ora_query3_tmp0_1.sql.
INFO 2007-05-31 23:06:18
Switched to user: sm1adm.
INFO 2007-05-31 23:06:18
Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2007-05-31 23:06:20
Switched to user: sm1adm.
INFO 2007-05-31 23:06:20
Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
ERROR 2007-05-31 23:20:32
CJS-00084 SQL statement or script failed. DIAGNOSIS: Error message: ORA-955 for defaultdest
SQL> Rem bnainani 11/29/00 - specify compatible=8.0 for create_queue_table
SQL> Rem liwong 10/20/00 - add def$_destination.flag
SQL> Rem bnainani 11/15/00 - specify compatible=8.0 for queue table
SQL> Rem narora 09/13/00 - add comment on new def$_destination columns
SQL> Rem liwong 09/01/00 - add master w/o quiesce: fixes
SQL> Rem liwong 07/12/00 - add total_prop_time_lat
SQL> Rem liwong 06/29/00 - add total_txn_count, total_prop_time
SQL> Rem liwong 05/17/00 - add_master_db w/o quiesce
SQL> Rem jstamos 05/17/00 - add_master_db w/o quiesce
SQL> Rem elu 01/24/00 - add column apply_init to def$_destination
SQL> Rem alakshmi 12/02/99 - Bug 979398: Before-row insert trigger on
SQL> Rem def$_propagator
SQL> Rem wesmith 10/31/98 - change shape of table def$_pushed_transactions
SQL> Rem jnath 02/23/98 - bug 601972: split anonymous pl/sql blocks
SQL> Rem wesmith 01/21/98 - create def$_pushed_transactions table for
SQL> Rem server-side RepAPI
SQL> Rem nbhatt 07/27/97 - change create_queuetable -> create_queue_table
SQL> Rem nbhatt 04/21/97 - change 'TRACKING' in CREATE_QUEUE to 'DEPENDENCY
SQL> Rem nbhatt 04/21/97 - change syntax of create_queue
SQL> Rem liwong 04/16/97 - Alter view system.AQ$DEF$_AQ{CALL,ERROR}
SQL> Rem liwong 04/11/97 - Fixing defaultdest_primary typo
SQL> Rem jstamos 04/10/97 - remove unneeded indexes
SQL> Rem nbhatt 04/08/97 - change create_qtable to create_queuetable
SQL> Rem jstamos 04/04/97 - tighter AQ integration
SQL> Rem liwong 04/02/97 - Add schema_name, package_name in def$_calldest
SQL> Rem ato 03/31/97 - create_qtable interface change
SQL> Rem liwong 03/25/97 - remove batch_no from def$_tranorder
SQL> Rem liwong 02/24/97 - pctversion --> 0 for def$_aqcall, def$_aqerror
SQL> Rem liwong 02/22/97 - Remove dropping view aq$def$_aqcall
SQL> Rem ademers 02/07/97 - Remove constraint def$_calldest_call
SQL> Rem liwong 01/11/97 - drop and create aq$def$_aqcall (temporary)
SQL> Rem liwong 01/10/97 - Alter view aq$def$_aqcall
SQL> Rem liwong 01/07/97 - Alter default value for batch_no
SQL> Rem jstamos 12/23/96 - change temp$nclob col
SQL> Rem jstamos 11/21/96 - nchar support
SQL> Rem sjain 11/11/96 - Remove dummy buffer # comment
SQL> Rem asgoel 11/05/96 - Disable misc_tracking in def$_aqerror
SQL> Rem sjain 11/06/96 - deferror changes
SQL> Rem vkrishna 10/28/96 - change STORED IN to STORE AS for lob
SQL> Rem sjain 10/02/96 - Aq conversion
SQL> Rem sbalaram 09/24/96 - ARPC performance - add foreign key index
SQL> Rem jstamos 09/06/96 - rename temp$lob and temporarily change nclob
SQL> Rem sjain 09/03/96 - AQ converson
SQL> Rem ademers 08/02/96 - queue_batch default in def_destination
SQL> Rem ademers 07/29/96 - queue_batch default in def_call
SQL> Rem ademers 07/29/96 - queue_batch default
SQL> Rem jstamos 07/24/96 - add system.temp$lob
SQL> Rem sbalaram 07/22/96 - create def$_aqcall and def$_aqerror tables
SQL> Rem jstamos 06/12/96 - LOB support for deferred RPCs
SQL> Rem ldoo 06/28/96 - Comment out queue_table from def_tranorder
SQL> Rem ademers 05/30/96 - create def_origin
SQL> Rem ademers 05/28/96 - fix def_destination col names
SQL> Rem ldoo 05/09/96 - New security model
SQL> Rem sjain 05/01/96 - add seq col to def_destination
SQL> Rem ademers 04/29/96 - add batch_no, dep_scn to def_call
SQL> Rem jstamos 12/04/95 - 324303: use index to avoid sorting the queue
SQL> Rem jstamos 08/17/95 - code review changes
SQL> Rem jstamos 08/16/95 - add comments to tables
SQL> Rem wmaimone 01/04/96 - 7.3 merge
SQL> Rem hasun 01/31/95 - Modify tables. SOLUTION: See ora_sql_results.log and the Oracle documentation for details.
ERROR 2007-05-31 23:20:32
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
ERROR 2007-05-31 23:20:32
FCO-00011 The step runCatprocSql with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0|runCatprocSql was executed with status ERROR .
Thanks in advnace for your help,
Glen

What do you see in ora_sql_result.log? (the last lines containing the error)?
Markus

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?

Problem starting with solution manager

hi guy, i have a problem with Solution Manager version 4.0 During an istallation of support package I had a network problem and the system went down fore some minutes. After that, is not possible logon on system. I try startsap and is ok, db seem up but is not possible connect by sapgui.
These are some errors that I can find in workdir
Tue Jan 27 15:08:51 2009
ERROR => GwIConnect: GwRead to SAPSM01 / 3301 failed, rc: NIETIMEOUT [gwxx_m
t.c    473]
***LOG S90=> SAP_CMREGTP2, GwIConnect ( 223) [r3cpic_mt.c 9618]
ERROR => ErrTrace: no error info available [err_mt.c     1507]
Connect_PM TPNAME=IGS.SM1, GWHOST=SAPSM01, GWSERV=3301
no SAP ErrInfo available
>TS> Tue Jan 27 15:10:51 2009
T:4398099755584 ======> Connect to SAP gateway failed
Connect_PM TPNAME=IGS.SM1, GWHOST=SAPSM01, GWSERV=3301
no SAP ErrInfo available
System is a Suse/Linux ppc64, with MaxDB as database
Please help me!!
hi guy, i have a problem with Solution Manager version 4.0 During an istallation of support package I had a network problem and the system went down fore some minutes. After that, is not possible logon on system. I try startsap and is ok, db seem up but is not possible connect by sapgui.
These are some errors that I can find in workdir
Tue Jan 27 15:08:51 2009
ERROR => GwIConnect: GwRead to SAPSM01 / 3301 failed, rc: NIETIMEOUT [gwxx_m
t.c    473]
***LOG S90=> SAP_CMREGTP2, GwIConnect ( 223) [r3cpic_mt.c 9618]
ERROR => ErrTrace: no error info available [err_mt.c     1507]
Connect_PM TPNAME=IGS.SM1, GWHOST=SAPSM01, GWSERV=3301
no SAP ErrInfo available
>TS> Tue Jan 27 15:10:51 2009
T:4398099755584 ======> Connect to SAP gateway failed
Connect_PM TPNAME=IGS.SM1, GWHOST=SAPSM01, GWSERV=3301
no SAP ErrInfo available
System is a Suse/Linux ppc64, with MaxDB as database
Please help me!!

hi,
there is anyone who can help me?
Many Thanks
Fabrizio

Solution Manager EWA - cannot create session in satellite system

"Hi,
I want to configure EWA self service using Solman 4.0. I succesfully did the following :
a. Maintained SMSY and create the required trusted RFC connections from SM to satellite system. All connection and authorization passed in SM59. I used SAP_ALL/SDCCN_ALL role and assigned objects S_RFC*.
b. Assigned the system to a logical system.
c. Created the a new solution and activate "Solutions Monitoring > Earlywatch Alert"
d. Activated and maintained required RFC in SDCCN in satallite system.
My problem is that the create EWA alert request (Red Flag with a specific session number ) coulnd be pass to the satelitte system even though all the trusted RFC and authorization is set. When i execute the SESSION_REFRESH in the satellite system, the session is not created.
Did I miss out any steps. Can any one share any help ?
FYI, there is no connection to SAPOSS yet, so i did not manage to run RTCCTOOL completed, but i doubt this is required for EWA self service."
I have the same problem as Solution Manager EWA - cannot create session in satellite system
tried all of solutions, but it does not help... Created the CM (high) for SAP, but get 1 response for 1 week from them:(

Dear Sapbcer,
Have you tried the following option :
Execute SMSY and from the Server entry Execute the "Read System Data Remote" option in change mode.
Save the data captured and then try using Refresh Session Task from SDCCN of the satellite system. Do select the RFC for Solution Manager while performing this task.
Hope this helps.
Regards
Amit

Error on install Solution Manager : Jcmon(error 4). No space left on device

Hi
I am having a problem installing Solution Manager 7.0 EHP1- AIX 6.1 DB2 9.7
During the unpacking phase error:
FCO-00011 The step unpack with step key was executed with status ERROR (Last error Reported by the step: Execution of the command "/ tmp/sapinst_exe.4325530.1325543592/SAPCAR-x-v-i-r / usr / sap / SMG / SYS / exe / run-f / MidiasInstall / IMKernel/DATA_UNITS/K_701_U_AIX_PPC64/DBINDEP/SAPEXE.SAR, "finished with return code 4. Output
<html> <head> </ head> <body> An error occurred while processing option EhP1 SAP Solution Manager 7.0> SAP Systems> IBM DB2 for Linux, UNIX, and Windows> Central System> Central System (Reported by the last step error: Execution of the command "/ tmp/sapinst_exe.4325530.1325543592/SAPCAR-x-v-i-r / usr / sap / SMG / SYS / exe / run-f / MidiasInstall/IMKernel/DATA_UNITS/K_701_U_AIX_PPC64 / DBINDEP / SAPEXE.SAR, "finished with return code 4. Output:
Sapce: processing archive / MidiasInstall/IMKernel/DATA_UNITS/K_701_U_AIX_PPC64/DBINDEP/SAPEXE.SAR (version 2.01)
x jcmon
Sapce: error writing to / usr / sap / SMG / SYS / exe / run / jcmon (error 4). No space left on device).
Note: I downloaded the newest sapinst but not resolved.
SAPinst build information:
abi version: 722
make variant: 720_REL
build: 1296039
compile time: 26 Dec 2011 02:46:25
Media used:
51041320 - DB2 9.7 - Client
51041317_1 DB2 9.7 - RDBMS
51040438 - Export
51040437 - Installation Master
51040439 - Java SW Comp
51040584 - Kernel
Filesystem GB blocks Free% Used Iused% Iused Mounted on
/ dev/hd2 5:00 49 709 2.76 45% 8% / usr
/ dev/fslv00 15:00 15:00 15 1% 1% / usr / sap / SMG
any idea ?

Hi,
The /usr/sap file system looks fine.
Could you also check the file space on the /tmp file system? This is usually less and SAPInst can fill this up very quickly.
Ideal to create a seperate SAPInst directory rather than use the default /tmp/sapinst_instdir.
Regards,
Srikishan

Solution manager key for installing ecc 6.0 on window 2003, oracle 10g

Hi,
I am installing ecc6.0 on windows 2003 platfrom with 10g oracle database. I have problem providing solution manager key during installtion in the window.
my db hostname is : deleted
sap system id : deleted
central instance number: deleted
can any one help me please.
Thank you
Edited by: Eric Brunelle on Feb 8, 2010 7:53 AM

> I am installing ecc6.0 on windows 2003 platfrom with 10g oracle database. I have problem providing solution manager key during installtion in the window.
>
> my db hostname is : deleted
> sap system id :deleted
> central instance number: deleted
It is illegal to provide keys here.
You have to install a solution manager first before you can install an ERP 6.0 system - or open an OSS call if your Solution Manager is not (yet) available.
Markus

EP 7 systems in Solution Manager 7 for EWA activation

Dear Expert,
Greetings from Partha.
I need to include our EP 7 systems in Solution Manager 7 for EWA activation. Current lanscape scenario
Solution Manger 7.00 Installed
EP 7.00 Installed
No central SLD configured and all the system have local SLD.
1. As per the installtion guide & SAP notes we need to install
a> SM Diagnostics Agent & Wilo Introscope in Solution Manager (manging system).
b> Diagnostics Agent in every manged system(s).
For managing system we can download Diagnostics Agent installation DVDs from SAP Service Marketplace
at: http://service.sap.com/swdc --> Download --> SAP Support Packages --> Entry by Application Group
--> SAP Technology Components --> SAP SOLUTION MANAGER --> SAP SOLUTION MANAGER 7.0
--> Entry by Component --> Agents for Managed systems --> DIAGNOSTICS AGENT 7.11
--> <choose operating system of managed>
Our Solution Manager 7 is already installed and @SPS 17. My question is
1. Can we use the same file for SMD installtion in Solution Manger or we need to download it from some other area ?
If it is different then kindly let me know what are the DVDs to be downloaded and from where?
2. In our Managed System SMD installtion we have decided for
--> Installation Strategy as Direct Solution Manager Registration
But what strategy we should take for SMD installation on Sol Man 7 that is
Local SLD (wrt Sol Man) Registration or Direct Solution Manager Registration
3. What is the need for the SAP Host Agent Installattion ? Is it mandatory ?
Help will be appreciated.
Regards,
Partha

1. As per the installtion guide & SAP notes we need to install
a> SM Diagnostics Agent & Wilo Introscope in Solution Manager (manging system).
b> Diagnostics Agent in every manged system(s).
For managing system we can download Diagnostics Agent installation DVDs from SAP Service Marketplace
at: http://service.sap.com/swdc --> Download --> SAP Support Packages --> Entry by Application Group
--> SAP Technology Components --> SAP SOLUTION MANAGER --> SAP SOLUTION MANAGER 7.0
--> Entry by Component --> Agents for Managed systems --> DIAGNOSTICS AGENT 7.11
--> <choose operating system of managed>
Our Solution Manager 7 is already installed and @SPS 17. My question is
1. Can we use the same file for SMD installtion in Solution Manger or we need to download it from some other area ?
If it is different then kindly let me know what are the DVDs to be downloaded and from where?
Check the pdf attached in note 1234387 - Inst. 7.1 EhP1 - Diagnostics Agent installation
If you have SP17, you must follow note 1357812 and install Diagnostics Agent 7.01 SR1
2. In our Managed System SMD installtion we have decided for
--> Installation Strategy as Direct Solution Manager Registration
But what strategy we should take for SMD installation on Sol Man 7 that is
Local SLD (wrt Sol Man) Registration or Direct Solution Manager Registration
It doesn't matter what strategy you'll decide. You could decide Direct Solution Manager registration
3. What is the need for the SAP Host Agent Installattion ? Is it mandatory ?
As you have solution Manager SP17, you can't install Saphostagent 7.11 and for this reason you can't use SAphostagent.
Agent 7.01 => No Saphostagent
Agent 7.11 => Must install saphostagent
Agent 7.20 => Already have SAPhostagent installed

How to remove Production System from Solution manager.

Hi All,
We have Three system landscape and solution manager installed.
All the system are managed by Solution manager.
here we are looking to remove the Production System from Solution manager.
as in case if is there any problem in solution manager then we are not dependent on it.
things will work directly on Production system.
Could you please let us know the procedure to remove the system from solution manager.
Please let us know if is there any document provided by SAP.

Hi,
Have you implemented charm,ccms monitoring or any other functionalities?
if yes,.Delete the sytem from tms domain. and TR route needs to be adjusted, if you are using ccms, remove the agent details from RZ21 also.
Does your production system data coming from SLD?
if yes, Delete the entry from SLD
if both the answer is no.
1.delete RFC from SOLMAN to the production systems.
2. delete the production system using SMT2 transaction.
3. Remove system rom SMSY from SOLMAN.
Thanks,
Jansi

Ccmsping registration problem in Solution manager

Similar Messages

Maybe you are looking for