Solution manager 7.1 SP04 dump
Dear Experts,
I am getting follwing abap dump after configuring managed system in Solution manager.
I have already implemented SAP central note for Solman 7.1 SPS 04. Please suggest me how to resolve this issue as i am getting morethan 5000 dumps a day.
Regards,
Cinu
Hi Sinu,
Refer below note also,
1680556 - E2E Root Cause Analysis causes "CREATE_DATA_UNKNOWN_TYPE
Regards
K.N
Similar Messages
-
SOlution Manager Installation, LOAD JAVA DUMP
Hello Guys,
I just have had the same problem on HP-UX 11.11 with SAP-DB. Installation stuck on at LOAD JAVA DUMP.
Solution:
Use JAVA SDK Version 1.4.2.09 AND NOT version 1.4.2.10 !!!
This may fix the problem rapid in our enviroment. It takes me 1.5 half day to fix it.
Regards
Michael HeynSame problem here, but linux 32-bit with MaxDB....
Solution Manager 4.0 SR3....
Last entry in jload.log:
31.10.07 13:59:50 com.sap.inst.jload.Jload dbImport
INFO: trying to create table J2EE_CONFIGENTRY
31.10.07 13:59:50 com.sap.inst.jload.Jload dbImport
INFO: table J2EE_CONFIGENTRY created
Last Entry in IMPORT.sta:
T:CAF_UM_RELGR_WORDS:DATA INSERT OK 30.10.07 16:03:15
T:J2EE_CONFIG:METADATA CREATE OK 30.10.07 16:03:17
T:J2EE_CONFIG:DATA INSERT ERR 30.10.07 16:03:17
T:J2EE_CONFIGENTRY:METADATA CREATE OK 30.10.07 16:03:17
Java uses 99% of the cpu since 22 hours.....
DB is up and running....enough space....
java version 1.4.2_10
Any suggestions ? -
Solution Manager 7.1 SP04 - Job SAP_COLLECTOR_FOR_PERFMONITOR
Dear Experts
I got an issue with some differences between what SolMan Setup did and SAP Note 966309 for TCOLL in SAP_BASIS 700 - 702 sais.
SolMan Setup creates the job SAP_COLLECTOR_FOR_PERFMONITOR with the following step in working client 001:
1 RSCOLL00 ABAP SOLMAN_BTC EN
According to SAP Note 966309, this job is supposed to run as user DDIC (or any other with same rights) in client 000. On top, there are a lot of differences between SAP Note 966309 and the content of TCOLL.
Would you change TCOLL according to this SAP Note or would you hang on what SolMan Setup did?
Thanks for short answer.
Regards, MichaelMichael,
This note is clear regarding the client and user:Note 16083 - Standard jobs, reorganization jobs
and this note is release independent.
If you check using RTCCTOOL you'll be able to see a recommendation regarding TCOLL:
7. [Note 12103 ] Collectors and TCOLL
Description Planning table TCOLL for SAP workload collectors for 700 (note 966309 )
Implementation Press the lights icon to get the detailed check log.
Add missing entries to table TCOLL using ST03N > Expert Mode > Collector
and Performance DB > Performance Monitor Collector > Execution Times.
Schedule RSCOLL00 as an hourly batch job if not scheduled.
"schedule standard jobs" steps is required if the jobs are not scheduled already:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Basic+Configuration
"In the activities schedule Background jobs and standard jobs different jobs are scheduled. The Background job that are scheduled are jobs for the housekeeping of SAP Solution Manager. The standard jobs are the same jobs as the jobs scheduled in transaction SM36 --> u201EStandard Jobs" and schedules jobs for general SAP housekeeping. Please make sure that the jobs are not already scheduled in SM36 before executing this activity. "
Cheers,
Diego. -
Define Service Desk Destination in the Solution Manager System (Dump creen)
hi,
in SPRO when i click on Define Service Desk Destination in the Solution Manager System
i got dump screen with the error below
any help?
Runtime Errors SAPSQL_EMPTY_TABNAME
Except. CX_SY_DYNAMIC_OSQL_SYNTAX
Date and Time 13.07.2008 14:05:57
Short text
A dynamically specified FROM clause has an unexpected format.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSHI2" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX', was not
caught in
procedure "STREE_READ_NODE_GENER" "(FUNCTION)", nor was it propagated by a
RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
The running ABAP program attempted to execute an Open SQL statement in
which a FROM clause was specified dynamically in the field "TABLE_NAME". In
this
FROM clause, either a table name after a join operator is missing, or an
alias name after the key name "AS". The field "TABLE_NAME" could be empty as
well.
regardsHi,
I am facing the same problem. What is SP15 ?
Is there any SAP Note that can be applied to correct this ?
Thanks. -
Dump (Raise exception) in Solution Manager
Hi experts ,
We are getting dumps from Satellite system into the Solution manager system. And the user respossible for the dump
is ALERT_<SID of Satellite System>. All the RFC have been checked . Central Auto reaction methods are assigned from
Solution manager to Satellite system. And checked that Auto reaction methods are not responsible for dump
SOLMAN_CEN_ALERT Destination is also checked in Satellite system.
Please assist
DUMP Details :
A RAISE statement in the program "CL_ABAP_TYPEDESCR=============CP" raised the
| exception
| condition "TYPE_NOT_FOUND".
| Since the exception was not intercepted by a superior
| program, processing was terminated.
User and Transaction
| Client.............. 100
| User................ "ALERT_SID"
| Language Key........ "E"
| Transaction......... " "
| Transactions ID..... "XXXXXXXXXXXXXXXXXXXXXXX"
| Program............. "CL_ABAP_TYPEDESCR=============CP"
| Screen.............. "SAPMSSY1 3004"
| ScreenLine.........2
| Information on caller of Remote Function Call (RFC):
| System.............. "SID"
| Database Release.... 700
| Kernel Release...... 700
| Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
| Call Type........... "synchron and transactional (emode 0, imode 0)"
| Inbound TID.........." "
| Inbound Queue Name..." "
| Outbound TID........." "
| Outbound Queue Name.." "
| Client.............. 100
| User................ "WF-BATCH"
| Transaction......... " "
| Call Program........."SAPLSALRT_CREATE_LOCAL"
| Function Module..... "SALERT_CREATE"
| Call Destination.... "SOLMAN_CEN_ALERT"
| Source Server....... "Satellite System hostname"
| Source IP Address... "XX.XX.XX.XX"
Source Code Extract
|Line |SourceCde
| 53| read table admin_tab from admin_tab_line into admin_tab_line.
| 54| if sy-subrc = 0.
| 55| p_descr_ref ?= admin_tab_line-ref->get( ).
| 56| if p_descr_ref is bound.
| 57| return.
| 58| endif.
| 59| delete table admin_tab from admin_tab_line.
| 60| endif.
| 61|* create new descr object
| 62| case admin_tab_line-kind.
| 63| when kind_elem.
| 64| raise event create_elemdescr
| 65| exporting xtype = admin_tab_line-xtype.
| 66| when kind_ref.
| 67| raise event create_refdescr
| 68| exporting xtype = admin_tab_line-xtype.
| 69| when kind_struct.
| 70| raise event create_structdescr
| 71| exporting xtype = admin_tab_line-xtype.
| 72| when kind_table.
| 73| raise event create_tabledescr
| 74| exporting xtype = admin_tab_line-xtype.
| 75| when kind_class.
| 76| raise event create_classdescr
| 77| exporting xtype = admin_tab_line-xtype.
| 78| when kind_intf.
| 79| raise event create_intfdescr
| 80| exporting xtype = admin_tab_line-xtype.
| 81| when others.
| 82|* all others are erros
|>>>>>| raise type_not_found.
| 84| endcase.
| 85| endcase.
86
| 87| create object admin_tab_line-ref exporting oref = returning_ref.
| 88| insert admin_tab_line into table admin_tab.
| 89| p_descr_ref = returning_ref.
| 90| clear returning_ref.
91
| 92|endmethod.
KamalHi Kamal,
I recommend to open a ticket for SAP with the runtime error attached.
Best regards,
Andreas -
The detection of short dump in the Solution Manager
Hi,
In my project, Batch are processing every night In the CRM system.
IF any error was occurred, alert email will be sent by the system, however,
when the "short dump" was occurred unexpectedly,the system can't detect it and email was not able to be sent.
Therefore I want to detect the "short dump" in the "Solution Manager".
Who can tell me that Is there any standard service/function which can handle this in the "Solution Manager" ?
regards
TakahiroHi,
Please check below URL and notes, hope it helps.
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/2c/abb2e7ff6311d194c000a0c93033f7/content.htm
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/05c80724d63836e10000000a42189b/frameset.htm
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e3eeb4a8-0b01-0010-bd99-f4a700a49d32?quicklink=index&overridelayout=true
note 553953
note 784752
Regards,
Deepanshu -
Error in Import Java Dump phase while installing SAP solution Manager 7.1
Hi,
While installing SAP solution manager 7.1 I am getting the below error during the phase "Import Java Dump".
An error occurred while processing option SAP Solution Manager 7.1 > SAP Systems > MS SQL Server > Central System > Central System( Last error reported by the step : Execution of JLoad tool 'C:\j2sdk1.4.2_17-x64\bin\java.exe -classpath "C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\MSS\CENTRAL\AS\install\sharedlib\launcher.jar" -showversion -Xmx1024m com.sap.engine.offline.OfflineToolStart com.sap.inst.jload.Jload "C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/MSS/CENTRAL/AS/install/lib/iaik_jce.jar;C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/MSS/CENTRAL/AS/install/sharedlib;D:/usr/sap/SPT/SYS/exe/uc/NTAMD64/mssjdbc/sqljdbc.jar" -sec SPT,jdbc/pool/SPT,
smn/sapmnt/SPT/SYS/global/security/data/SecStore.properties,
smn/sapmnt/SPT/SYS/global/security/data/SecStore.key -dataDir "D:/SAP SOLMAN/Java Components/51040039\DATA_UNITS\SOLMAN_JAVA_EXPORT_JDMP" -job "C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\MSS\CENTRAL\AS\IMPORT.XML" -log jload.log' aborts with return code 1. SOLUTION: Check 'jload.log' and 'C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/MSS/CENTRAL/AS/jload.java.log' for more information.
JLOAD.JAVA log details below
java version "1.4.2_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, mixed mode)
Jload R 7.12 V 0 A 0
Jload -sec SPT,jdbc/pool/SPT,
smn/sapmnt/SPT/SYS/global/security/data/SecStore.properties,
smn/sapmnt/SPT/SYS/global/security/data/SecStore.key -dataDir D:/SAP SOLMAN/Java Components/51040039\DATA_UNITS\SOLMAN_JAVA_EXPORT_JDMP -job C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\MSS\CENTRAL\AS\IMPORT.XML -log jload.log
Connecting to database
Couldn't connect to DB
com.sap.inst.common.exception.DBConnectionException: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect
at com.sap.inst.common.db.DBConnection.connect(DBConnection.java:157)
at com.sap.inst.jload.Jload.main(Jload.java:222)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
at com.sap.inst.common.db.DBConnection.connectViaSecureStore(DBConnection.java:111)
at com.sap.inst.common.db.DBConnection.connect(DBConnection.java:151)
... 6 more
An error occured during execution. Please consult SAP note 942766 for first steps on troubleshooting the problem.
I have gone thru with the notes and it didn't help me much.
I have used J2SDK 1.4.2_17 nad JCE_Policy-1.4.2 files.
Please let me know where IO went wrong.
Thanks in advance.
SaiHi,
1. Did you select java path (Export CD/DVD) while intsallation? Check once again.
2. Add JAVA_HOME = Java path in environment variable.
3. What is the exact error, you got it, post error here.
Regards,
Srini Nookala -
Error in Import JAVA DUMP phase in Solution Manager installation.
Hi,
when i am installing Solution manager i am getting error in import java dump phase on windows and oracle database. i installed java 1.4.2_09 . plz anybody give the solution. Its very urgent.
Thanks,
Venkat.Hi,
1. Did you select java path (Export CD/DVD) while intsallation? Check once again.
2. Add JAVA_HOME = Java path in environment variable.
3. What is the exact error, you got it, post error here.
Regards,
Srini Nookala -
EWA on solution manager - short dumps
Hi there
I've setup EWA on solution manager for Remote System BWQ, all test etc went fine, but as soon as I start service processing on solman to retrieve the data, a short dump is create as follows:
Short text
Syntax error in program "RDSVASAEA_ROOT_____________049 ".
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASAEA_ROOT_____________049
" in include "RDSVASAEA_ROOT_____________049 " in
line 87:
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
could anyone please assist me with this.
Regards,
StephanHi
So i tried to implement the above mentioned notes, but to update the solution manager stack, i have to use maintenance optimizer to approve the stack...
I have added solution manager 7.0 to the solution overview, and can select it from 'Plan Maintenance' window.. but as soon as i try and go to the second step, another short dump is created.
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_SOCM_NOT_IMPLEMENTED
Date and Time 13.06.2008 09:25:45
|Short text |
| An exception occurred that was not caught. |
|What happened? |
| The exception 'CX_SOCM_NOT_IMPLEMENTED' was raised, but it was not caught |
| anywhere along |
| the call hierarchy. |
| |
| Since exceptions represent error situations and this error was not |
| adequately responded to, the running ABAP program |
| 'CL_CHM1_CHANGE_REQU_INSTANCE==CP' has to be |
| terminated. |
i then looked at Notes:
Note 851496 - Exception: CX_SOCM_NOT_IMPLEMENTED missing implementation
Note 849690 - BC Set Change Management
But none of them seem relevant to our SOLMAN. -
Create a Support Message in Production system showing up in Solution Manage
Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
PaulHi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role. -
Setting up EarlyWatch in Solution manager
Hi Guys
I am trying to configure Early Watch in solution manager(System Id u2013SOL , Installation No - 0020306432) for an satellite system (System Id -DEV u2013Installation No : 0020181089).
I have followed all the configuration steps listed below :
1. Configuration RFCs to market place SAPOSS and to satellite Systems and RFC Back to solution manager. All RFC like SAPOSS and Back has been tested from SDCCN (Solution manager and satellite system)
2. Configured SDCCN in solution manager and in satellite system except u201CGenerate Includes for Service data control centeru201D in SPRO of solution manager as this process is getting time out and not letting us to generate all the includes
3. Activated Service data Control center locally and assign solution manager as u2018Master system for allu2019.
4. Activated SDCCN in satellite system(DEV) ,Created Earlywatch Service in Solution manager for DEV system and also created/Started u2018Refresh Sessionu2019 in SDCCN of DEV(Satellite system)
5. This successfully shows me Early watch link in u2018Waitingu2019 Status in solution manager.
6. I click on u2018Start Service Processingu2019 to Schedule/Run u201CSM:EXEC SERVICESu201D background job .
Problem : Background job u201CSM:EXEC SERVICESu201D get cancelled after some time and throws a Dump which is pasted below.
Dump shows that an include u2018/1CAGTF/IF_LOGFUNC_000393u2019 is missing which should have been generated while activating the includes for SDCCN in SPRO of solution manager.
I found includes from u2018/1CAGTF/IF_LOGFUNC_000001u2019 to u2018/1CAGTF/IF_LOGFUNC_000353u2019 in the system as it seems that not all include have been generated .
*Could you please help me to provide some SAP note so that I would be able to generate all the includes . *
DUMP
Runtime Errors SYNTAX_ERROR
Date and Time 24.05.2008 00:01:02
Short text
Syntax error in program "RDSVASAEW_ROOT_____________073 ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASAEW_ROOT_____________073
" in include "RDSVASAEW_ROOT_____________073 " in
line 96:
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
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 "RDSVASAEW_ROOT_____________073
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
RDSVASAEW_ROOT_____________073 :
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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.
System environment
SAP-Release 700
Application server... "mslsol"
Network address...... "192.168.193.154"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 10
Shortdump setting.... "full"
Database server... "MSLSOL"
Database type..... "ORACLE"
Database name..... "SOL"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 29 2006 00:18:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.2.0) "
Patch level. 75
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 29266272
Heap.... 0
Page.... 24576
MM Used. 24845128
MM Free. 236264
User and Transaction
Client.............. 600
User................ "BASISA"
Language key........ "E"
Transaction......... " "
Program............. "SAPLDSVAS_PROC"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLDSVAS_PROC" - in "EXECUTE".
The main program was "RDSMOPBACK_AUTOSESSIONS ".
In the source code you have the termination point in line 2146
of the (Include) program "LDSVAS_PROCCD0".
The program "SAPLDSVAS_PROC" was started as a background job.
Job Name....... "SM:EXEC SERVICES"
Job Initiator.. "BASISA"
Job Number..... 00384300
Source Code Extract
Line
SourceCde
2116
ls_stdparameter-versnr = po_ctnode->versnr.
2117
ls_stdparameter-grp = po_ctnode->grp.
2118
ls_stdparameter-id = po_ctnode->id.
2119
ls_stdparameter-reference_versnr = po_ctnode->reference_versnr.
2120
ls_stdparameter-reference_grp = po_ctnode->reference_grp.
2121
ls_stdparameter-reference_id = po_ctnode->reference_id.
2122
else.
2123
ls_stdparameter-grp = pf_grp.
2124
ls_stdparameter-versnr = pf_versnr.
2125
ls_stdparameter-reference_grp = pf_grp.
2126
ls_stdparameter-reference_versnr = pf_versnr.
2127
endif.
2128
2129
Formroutinen aufrufen
2130
loop at actseq
2131
into ls_actrel
2132
where exec_time = pf_exec_time.
2133
check ls_actrel-exec_time ne gf_exec_time_event
2134
or ( ls_actrel-exec_time = gf_exec_time_event and
2135
ls_actrel-event = pf_event ).
2136
call function 'DSVAS_CDMNT_FORM_NAME'
2137
exporting
2138
pf_container_type = 'A'
2139
pf_form_number = ls_actrel-action
2140
importing
2141
pf_form_name = lf_form_name.
2142
perform (lf_form_name)
2143
in program (program)
2144
using ls_stdparameter
2145
if found.
>>>>>
endloop.
2147
endmethod. "execute
2148
2149
Collect_Known_Events
2150
method collect_known_events.
2151
data: ls_actseq type line of ltype_action_sequence_table,
2152
lf_event type dsvasactseq-event.
2153
2154
loop at actseq into ls_actseq
2155
where ( exec_time = gf_exec_time_event and
2156
event ne space )
2157
or exec_time = gf_exec_time_1
2158
or exec_time = gf_exec_time_2
2159
or exec_time = gf_exec_time_3
2160
or exec_time = gf_exec_time_modus_close.
2161
if ls_actseq-exec_time = gf_exec_time_event.
2162
read table pt_events with table key table_line = ls_actseq-event
2163
transporting no fields.
2164
if sy-subrc ne 0.
2165
insert ls_actseq-event into table pt_events.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
30
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
DSWP: Execute rule set
SY-MSGTY
E
SY-MSGID
FL
SY-MSGNO
046
SY-MSGV1
DSVAS_TOOLS_PACKAGE_GET
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080524
SY-UZEIT
000049
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
11 FORM SAPLDSVAS_PROC LDSVAS_PROCCD0 2146
EXECUTE
10 METHOD SAPLDSVAS_PROC LDSVAS_PROCCD0 2142
LCL_ACTION_SEQUENCE=>EXECUTE
9 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1741
LCL_CHECK_TREENODE=>EXECUTE
8 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1792
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
7 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1806
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
6 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 2025
LCL_SESSION=>EXECUTE
5 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 1582
LCL_SESSION=>CONTEXT_INSTANCES_CREATE
4 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 1995
LCL_SESSION=>EXECUTE
3 FUNCTION SAPLDSVAS_PROC LDSVAS_PROCU02 303
DSVAS_PROC_SESSION_OPEN
2 METHOD CL_DSMOP_SOLUTION=============CP CL_DSMOP_SOLUTION=============CM01P 184
CL_DSMOP_SOLUTION=>START_PERIODIC_SERVICES
1 EVENT RDSMOPBACK_AUTOSESSIONS RDSMOPBACK_AUTOSESSIONS 72
START-OF-SELECTION
Chosen variables
Name
Val.
No. 11 Ty. FORM
Name EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PO_CTNODE
|
| 2000D000 |
| E0001C00 |
| PF_GRP |
| |
| 22222222222222222222 |
| 00000000000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| PF_VERSNR |
| 00000 |
| 33333 |
| 00000 |
| 00000 |
| 00000 |
| <%_L02E>-EXEC_TIME |
| ??? |
| ?????? |
| ?????? |
| <%_L02F> |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| LS_ACTREL-EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| GF_EXEC_TIME_EVENT |
| E |
| 4 |
| 5 |
| 0 |
| 0 |
| SYST-REPID |
| SAPLDSVAS_PROC |
| 5454455455554422222222222222222222222222 |
| 310C43613F02F300000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| LS_ACTREL-EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY-SAPRL+0(4) |
| 70 |
| 33 |
| 70 |
| 00 |
| 00 |
| LS_ACTREL-ACTION |
| 108 |
| 333 |
| 108 |
| 000 |
| 000 |
| LF_FORM_NAME |
| ACTION_108 |
| 44544453332222222222222222222222 |
| 1349FEF1080000000000000000000000 |
| 00000000000000000000000000000000 |
| 00000000000000000000000000000000 |
| ME->PROGRAM |
| RDSVASAEW_ROOT_____________073 |
| 5455454455544555555555555553332222222222 |
| 243613157F2FF4FFFFFFFFFFFFF0730000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| LS_STDPARAMETER |
| EA6000000000255###ESESSION 00047EA_ROOT |
| 4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222 |
| 516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No. 10 Ty. METHOD |
| Name LCL_ACTION_SEQUENCE=>EXECUTE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PO_CTNODE |
|
2000D000
E0001C00
PF_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_VERSNR
00000
33333
00000
00000
00000
<%_L02E>-EXEC_TIME
<%_L02F>
I
4
9
0
0
LS_ACTREL-EXEC_TIME
I
4
9
0
0
LS_ACTREL-EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_ACTREL-ACTION
108
333
108
000
000
LF_FORM_NAME
ACTION_108
44544453332222222222222222222222
1349FEF1080000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
ME->PROGRAM
RDSVASAEW_ROOT_____________073
5455454455544555555555555553332222222222
243613157F2FF4FFFFFFFFFFFFF0730000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_STDPARAMETER
EA6000000000255###ESESSION 00047EA_ROOT
4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222
516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 9 Ty. METHOD
Name LCL_CHECK_TREENODE=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
GF_EXEC_TIME_ATTRIBUTES
a
6
1
0
0
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME
|
| 2000D000 |
| E0001C00 |
| GT_OPEN_SESSIONS |
| Table IT_3668[1x44] |
| FUNCTION-POOL=DSVAS_PROCDATA=GT_OPEN_SESSIONS |
| Table reference: 1911 |
| TABH+ 0(20) = 807E0D3E000000000000000077070000540E0000 |
| TABH+ 20(20) = 010000002C000000FFFFFFFF0417010010040000 |
| TABH+ 40( 8) = 10000000A4318001 |
| store = 0x807E0D3E |
| ext1 = 0x00000000 |
| shmId = 0 (0x00000000) |
| id = 1911 (0x77070000) |
| label = 3668 (0x540E0000) |
| fill = 1 (0x01000000) |
| leng = 44 (0x2C000000) |
| loop = -1 (0xFFFFFFFF) |
| xtyp = TYPE#000007 |
| occu = 16 (0x10000000) |
| access = 4 (ItAccessHashed) |
| idxKind = 0 (ItIndexNone) |
| uniKind = 1 (ItUnique) |
| keyKind = 3 (user defined) |
| cmpMode = 8 (cmpManyEq) |
| occu0 = 1 |
| groupCntl = 0 |
| rfc = 0 |
| unShareable = 0 |
| mightBeShared = 0 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind = 0 |
| isUsed = 1 |
| isCtfyAble = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi = 0xC0AB0D3E |
| pgHook = 0x00000000 |
| idxPtr = 0x78F10D3E |
| shmTabhSet = 0x00000000 |
| id = 2504 (0xC8090000) |
| refCount = 0 (0x00000000) |
| tstRefCount = 0 (0x00000000) |
| lineAdmin = 16 (0x10000000) |
| lineAlloc = 16 (0x10000000) |
| shmVersId = 0 (0x00000000) |
| shmRefCount = 1 (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook = Not allocated |
| collHook = Not allocated |
| ext2 = Not allocated |
| >>>>> 2nd level extension part <<<<< |
| tabhBack = Not allocated |
| delta_head = Not allocated |
| pb_func = Not allocated |
| pb_handle = Not allocated |
| GF_EXEC_TIME_BEFORE_REPORT_GEN |
| R |
| 5 |
| 2 |
| 0 |
| 0 |
| GF_EXEC_TIME_INIT |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| ME->INITIALIZED |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| GF_EXEC_TIME_AFTER |
| A |
| 4 |
| 1 |
| 0 |
| 0 |
| ME->ACTSEQ |
|
2000D000
C0003C00
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME->HAS_TABLES
X
5
8
0
0
SYST
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
SY-REPID
SAPLDSVAS_PROC
5454455455554422222222222222222222222222
310C43613F02F300000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHECK_TABLES
|
| 2000D000 |
| 3000CC00 |
| No. 8 Ty. METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME->DYNAMIC |
| X |
| 5 |
| 8 |
| 0 |
| 0 |
| ME |
|
2000D000
E0001C00
GF_SESSION_DEF_TYPE_MORE_DEV
L
4
C
0
0
ME->ACTIVE
X
5
8
0
0
GF_SESSION_DEF_TYPE_VERSION
V
5
6
0
0
ME->CON
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHILD_CONDSEQ
F0000000
F0000000
GF_CONTEXT_SESSION
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->CHILDREN
Table[initial]
LO_TNODE
|
| F0000000 |
| F0000000 |
| %_ARCHIVE |
| |
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No. 7 Ty. METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME |
|
2000D000
F0000C00
ME->CHILD_CONDSEQ
|
| F0000000 |
| F0000000 |
| ME->CHILDREN |
| Table IT_3674[26x8] |
| DATA=CHILDREN
Table reference: 1919
TABH+ 0(20) = 68550D3E00000000000000007F0700005A0E0000
TABH+ 20(20) = 1A00000008000000800100000417010030080000
TABH+ 40( 8) = 10000000C1288001
store = 0x68550D3E
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 1919 (0x7F070000)
label = 3674 (0x5A0E0000)
fill = 26 (0x1A000000)
leng = 8 (0x08000000)
loop = 384 (0x80010000)
xtyp = TYPE#000029
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 4 (cmpSingleEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xB0B10D3E
pgHook = 0xF0882E3E
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 2508 (0xCC090000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 48 (0x30000000)
lineAlloc = 48 (0x30000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
LO_TNODE
|
| 2000D000 |
| E0001C00 |
| LO_CTNODE |
|
2000D000
E0001C00
%_SPACE
2
0
0
0
No. 6 Ty. METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
SESSION
5455444222
35339FE000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME->GLOBAL_CHECK_GRP |
| EA_ROOT |
| 44554452222222222222 |
| 51F2FF40000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| ME->GLOBAL_VERSNR |
| 00047 |
| 33333 |
| 00047 |
| 00000 |
| 00000 |
| ME->CHECK_TREE |
|
2000D000
F0000C00
GF_EXEC_TIME_MODUS_CLOSE
W
5
7
0
0
ME->RAISED_EVENTS
Table[initial]
GF_EXEC_TIME_LOGICAL_COMPLETE
L
4
C
0
0
No. 5 Ty. METHOD
Name LCL_SESSION=>CONTEXT_INSTANCES_CREATE
LT_ZOMBIES
Table[initial]
LS_CTREL-TREENODE
F0000000
F0000000
LO_ZOMBIE
|
| F0000000 |
| F0000000 |
| LT_NEW_CONINS |
| Table IT_3670[1x100] |
| FUNCTION-POOL=DSVAS_PROCCLASS=LCL_SESSIONMETHOD=CONTEXT_INSTANCES_CREATEDATA=LT_NEW_CONINS |
| Table reference: 1920 |
| TABH+ 0(20) = 90C50D3E30F3DE3D0000000080070000560E0000 |
| TABH+ 20(20) = 0100000064000000080100000417010060140000 |
| TABH+ 40( 8) = 01000000C1248401 |
| store = 0x90C50D3E |
| ext1 = 0x30F3DE3D |
| shmId = 0 (0x00000000) |
| id = 1920 (0x80070000) |
| label = 3670 (0x560E0000) |
| fill = 1 (0x01000000) |
| leng = 100 (0x64000000) |
| loop = 264 (0x08010000) |
| xtyp = TYPE#000094 |
| occu = 1 (0x01000000) |
| access = 1 (ItAccessStandard) |
| idxKind = 0 (ItIndexNone) |
| uniKind = 2 (ItUniqueNon) |
| keyKind = 1 (default) |
| cmpMode = 2 (cmpSingleMcmpR) |
| occu0 = 1 |
| groupCntl = 0 |
| rfc = 0 |
| unShareable = 0 |
| mightBeShared = 1 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind = 0 |
| isUsed = 1 |
| isCtfyAble = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi = 0x08AB0D3E |
| pgHook = 0x00000000 |
| idxPtr = 0x00000000 |
| shmTabhSet = 0x00000000 |
| id = 2505 (0xC9090000) |
| refCount = 0 (0x00000000) |
| tstRefCount = 0 (0x00000000) |
| lineAdmin = 1 (0x01000000) |
| lineAlloc = 1 (0x01000000) |
| shmVersId = 0 (0x00000000) |
| shmRefCount = 1 (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook = 0xB0F0BE3D |
| collHook = 0x00000000 |
| ext2 = 0x00000000 |
| >>>>> 2nd level extension part <<<<< |
| tabhBack = Not allocated |
| delta_head = Not allocated |
| pb_func = Not allocated |
| pb_handle = Not allocated |
| <LFS_CONINS> |
| SESSION |
| 54554442222222222222222222222222222222222222222222 |
| 35339FE0000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| ME |
|
90006000
4000B000
<LFS_CONINS>-CON
SESSION
5455444222
35339FE000
0000000000
0000000000
<LFS_CONINS>-INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
GF_EXEC_TIME_BEFORE
B
4
2
0
0
No. 4 Ty. METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
2222222222
0000000000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME |
|
90006000
4000B000
ME->LOGICAL_COMPLETE
2
0
0
0
GF_EXEC_TIME_COMPLETE
C
4
3
0
0
ME->COMPLETE
2
0
0
0
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
000000000000000000000000000000
000000000000000000000000000000
No. 3 Ty. FUNCTION
Name DSVAS_PROC_SESSION_OPEN
PF_HANDLE_TO_USE
0
0000
0000
PF_MAX_TREE
2
0
0
0
PF_MODE
C
4
3
0
0
PS_SESSION_NUMBER
EA6000000000255
443333333333333
516000000000255
000000000000000
000000000000000
PF_HANDLE
1
0000
1000
PF_HIDE_TREE
2
0
0
0
PF_MODE_USED
2
0
0
0
PF_NEXT_CHECK_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_NEXT_CHECK_ID
00000
33333
00000
00000
00000
PF_NEXT_CON
2222222222
0000000000
0000000000
0000000000
PF_NEXT_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PT_ERRORS
Table[initial]
PT_FRONTEND_TREE[]
Table[initial]
PF_LANGUAGE
E
4
5
0
0
<%_TABLE_DSVASSESSADMIN>
LF_BUNDLE_VERSNR
00038
33333
00038
00000
00000
DSVASRESULTSGEN-CLUSTR
0
00
00
PS_SESSION_NUMBER-SESSNO
6000000000255
3333333333333
6000000000255
0000000000000
0000000000000
LS_OPEN_SESSIONS-SESSION
|
| 90006000 |
| 4000B000 |
| LO_SESSION |
|
90006000
4000B000
LS_OPEN_SESSIONS
EA6000000000255C####k#
4433333333333334009060
51600000000025531040B0
0000000000000000000000
0000000000000000000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_SESSDEFGEN-MULTI_USERPlease replace the Service Definitions in your SAP Solution Manager
system as described in SAP Note 727998.
As of SAP Solution Manager 7.0 (= 4.0) Support Package Stack 15 (which
includes ST-PI 700_2005_1 SP06) you can trigger the required steps
within transaction SDCCN:
Menu Utilities -> Maintain Service Definitions ->
Select 'Delete and Replace Service Definitions -> Confirm this
selection-> Confirm that you want to delete the definitions -> Confirm
that a new task 'Service Definition Refresh' was created
Take a note of the task id -> Review the log for this task id when it
is completed. You should not see any errors for either the update
of a Service Definitions table or the generation of any re-import
include.
Reschedule SM:EXEC SERVICES and the reported dump will no longer
occur. -
SM:SELFDIAGNOSIS background job getting failed in Solution manager
Hi All,
SM:SELFDIAGNOSIS background job getting failed in Solution manger server :
Job Log:
2-22-2012 16:44:02 Job started 00 516 S
2-22-2012 16:44:02 Step 001 started (program RDSWP_SELF_DIAGNOSIS, variant &0000000000324, user ID BASISUSER) 00 550 S
2-22-2012 16:45:07 Internal session terminated with a runtime error (see ST22) 00 671 A
2-22-2012 16:45:07 Job cancelled 00 518 A
ST22: Dump:
Runtime Errors ITAB_DUPLICATE_KEY
Date and Time 02-22-2012 16:45:07
Short text
A row with the same key already exists.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" 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
An entry was to be entered into the table
"\CLASS=CL_DSWP_SD_DIAGNOSE_CONSISTENT\METHOD=CHECK_USERS_BP\DATA=LT_USCP"
(which should have
had a unique table key (UNIQUE KEY)).
However, there already existed a line with an identical key.
The insert-operation could have ocurred as a result of an INSERT- or
MOVE command, or in conjunction with a SELECT ... INTO.
The statement "INSERT INITIAL LINE ..." cannot be used to insert several
initial lines into a table with a unique key.
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:
"ITAB_DUPLICATE_KEY" " "
"CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" or "CL_DSWP_SD_DIAGNOSE_CONSISTENTCM00M"
"CHECK_USERS_BP"
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.
KIndly Suggest to resolve the above issue
Thanks
NekkalapuHI,
Deatils:
SAP EHP 1 for SAP Solution Manager 7.0
SAP_ABA 701 0006 SAPKA70106
SAP_BASIS 701 0006 SAPKB70106
PI_BASIS 701 0006 SAPK-70106INPIBASI
ST-PI 2008_1_700 0002 SAPKITLRD2
CRMUIF 500 0004 SAPK-50004INCRMUIF
SAP_BW 701 0006 SAPKW70106
SAP_AP 700 0019 SAPKNA7019
BBPCRM 500 0016 SAPKU50016
BI_CONT 704 0007 SAPK-70407INBICONT
CPRXRPM 400 0016 SAPK-40016INCPRXRP
ST 400 0024 SAPKITL434
ST-A/PI 01M_CRM570 0000 -
ST-ICO 150_700 0009 SAPK-15079INSTPL
ST-SER 701_2010_1 0002 SAPKITLOS2
Thanks
Nekkalapu -
Background job failing - ECC 6.0, Solution Manager 7.0
Dear All,
Four days back, I have installed the Solution Manager 7.0 and ECC 6.0 on
HPUX IA64 hardware with database as Oracle 10.2.0.2.0 (Unicode).
In both server, latest kernel patch has been applied.
The Support package versions are (both server):
KERNEL (Release 700) 146
SAP_BASIS 0014
SAP_ABA 0014
PI_BASIS(2005_1_700) 0014
ST-PI 0005
SAP_BW 0016
While checking the the jobs from SM37, in both the server,
I am observing that following jobs are always failing with
same reason:
SAP_COLLECTOR_FOR_PERFMONITOR
=============================
Date Time Message text Message class Message no. Message type
========== ======== ====================================================================== ============= =========== ============
15.05.2008 06:25:12 Job started 00 516 S
15.05.2008 06:25:12 Step 001 started (program RSCOLL00, variant , user ID BGDUSER) 00 550 S
15.05.2008 06:25:18 Clean_Plan:Cleanup of DB13 Plannings DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:started by RSDBPREV on server gcbeccd DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:Cleaning up jobs of system RD3 DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:finished DB6PM 000 S
15.05.2008 06:25:18 Database system not supported S1 101 S
15.05.2008 06:25:36 ABAP/4 processor: DBIF_DSQL2_SQL_ERROR 00 671 A
15.05.2008 06:25:36 Job cancelled 00 518 A
SAP_REORG_UPDATERECORDS
=======================
Date Time Message text Message class Message no. Message type
========== ======== ===================================================================== ============= =========== ============
14.05.2008 00:31:01 Job started 00 516 S
14.05.2008 00:31:01 Step 001 started (program RSM13002, variant SAP&001, user ID BGDUSER) 00 550 S
14.05.2008 00:31:01 Reorganization of update date not allowed in batch 15 100 A
14.05.2008 00:31:02 Job cancelled 00 518 A
SAP_WP_CACHE_RELOAD_FULL
========================
Date Time Message text Message class Message no. Message type
========== ======== ============================================================================================ ============= =========== ============
15.05.2008 00:30:11 Job started 00 516 S
15.05.2008 00:30:11 Step 001 started (program RWP_RUNTIME_CACHE_RELOAD, variant SAP&RELOAD_ALL, user ID BGDUSER) 00 550 S
15.05.2008 00:30:11 No component system chosen URL_GEN_MSGS 031 E
15.05.2008 00:30:11 Job cancelled after system exception ERROR_MESSAGE 00 564 A
Please help to resolve this issue.
Thanks in advance.
Regards
Sudip GhoshHi Markus,
Thanks for the reply.
Below is the dump:
======
======
Runtime Errors DBIF_DSQL2_SQL_ERROR
Date and Time 15.05.2008 06:25:36
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error 3113 occurred in the current database connection "DEFAULT".
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.
How to correct the error
Database error text........: "ORA-03113: end-of-file on communication channel"
Database error code........: 3113
Triggering SQL statement...: "FETCH NEXT "
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
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:
"DBIF_DSQL2_SQL_ERROR" " "
"RSORAVSH" or "RSORAVSH"
"FILL_DBVSE"
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.
System environment
SAP-Release 700
Application server... "gcbeccd"
Network address...... "10.10.4.158"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 15
Shortdump setting.... "full"
Database server... "gcbeccd"
Database type..... "ORACLE"
Database name..... "RD3"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 1117216
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 695792
MM Free. 400816
User and Transaction
Client.............. 000
User................ "BGDUSER"
Language key........ "E"
Transaction......... " "
Transactions ID..... "482B8A4C89F0442BE10000000A0A049E"
Program............. "RSORAVSH"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSORAVSH" - in "FILL_DBVSE".
The main program was "RSORAVSH ".
In the source code you have the termination point in line 48
of the (Include) program "RSORAVSH".
The program "RSORAVSH" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "BGDUSER"
Job Number..... 05251100
Source Code Extract
Line
SourceCde
18
INCLUDE STRUCTURE v_system_event_struc.
19
DATA: END OF v_system_event_tab .
20
21
check sy-dbsys(3) = 'ORA' .
22
23
Get the new snapshots
24
25
PERFORM fill_dbvse TABLES v_system_event_tab.
26
27
28
Get the old snapshots from database table MONI
29
30
startday = sy-datum - days_to_keep .
31
32
33
Save new data now (otherwise these data will be selected twice)
34
35
CONCATENATE 'SYSEVENT' sy-datum sy-uzeit INTO monikey .
36
37
EXPORT sy-datum
38
sy-uzeit
39
v_system_event_tab
40
TO DATABASE moni(db) ID monikey .
41
42
*& Form FILL_DBVSE
43
44
FORM fill_dbvse TABLES v_system_event_tab.
45
date = sy-datum .
46
time = sy-uzeit .
47
EXEC sql performing append_v_system_event .
>>>>>
select event,
49
total_waits,
50
total_timeouts,
51
time_waited * 10,
52
average_wait * 10
53
into :v_system_event_struc
54
from v$system_event
55
ENDEXEC .
56
ENDFORM. " FILL_DBVSE
57
58
59
*& Form APPEND_V_SYSTEM_EVENT
60
61
FORM append_v_system_event.
62
v_system_event_tab-date = date .
63
v_system_event_tab-time = time .
64
65
MOVE-CORRESPONDING v_system_event_struc TO v_system_event_tab.
66
APPEND v_system_event_tab .
67
ENDFORM. " APPEND_V_SYSTEM_EVENT
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
16
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Report for Collecting Data from V$SYSTEM_EVENT Hourly
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080515
SY-UZEIT
062520
SY-XPROG
RSDBRUNT
SY-XFORM
%_INIT_PBO_FIRST
Active Calls/Events
No. Ty. Program Include Line
Name
2 FORM RSORAVSH RSORAVSH 48
FILL_DBVSE
1 EVENT RSORAVSH RSORAVSH 25
START-OF-SELECTION
Chosen variables
Name
Val.
No. 2 Ty. FORM
Name FILL_DBVSE
SY-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
V_SYSTEM_EVENT_STRUC
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222222222222222220000000000000000
0000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
%_SPACE
0
0
2
0
SY
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
No. 1 Ty. EVENT
Name START-OF-SELECTION
SY-LDBPG
SAPDB__S
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
SY-DBSYS+0(6)
ORA
000
000
454
F21
SYST
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
V_SYSTEM_EVENT_TAB[]
Table[initial]
V_SYSTEM_EVENT_TAB
00000000000000 ################
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333322222222222222222222222222222222222222222222222222222222222222220000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
SY-DATUM
20080515
00000000
00000000
33333333
20080515
DAYS_TO_KEEP
30
0001
000E
STARTDAY
00000000
00000000
00000000
33333333
00000000
MONIKEY
0000000000000000000000
0000000000000000000000
2222222222222222222222
0000000000000000000000
SY-UZEIT
062520
000000
000000
333333
062520
SYST-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
MONI-CLUSTR
0
00
00
MONI
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222220022000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ExecuteCall"
of the SAP kernel, in line 1190 of the module
"//bas/700_REL/src/krn/runt/abexsql.c#2".
The internal operation just processed is "DSQL".
Internal mode was started at 20080515062520.
Internal call code.........: "[DBDS/NEW DSQL]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0) 0x4000000003b2b450 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
(1) 0x4000000004d2c470 Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
(2) 0x4000000004d32160 ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
(3) 0x40000000047b51e0 Z10abdbdserriPKtiS0_P9DS_HEADERS0_iPv + 0x470 [dw.sapRD3_DVEBMGS00]
(4) 0x4000000003d777f0 Z11ExecuteCallv + 0x11f0 [dw.sapRD3DVEBMGS00]
(5) 0x4000000003d7e7b0 Z8abjdsqlv + 0x1b0 [dw.sapRD3_DVEBMGS00]
(6) 0x400000000402f190 Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
(7) 0x4000000003f53bc0 Z9abxeventPKt + 0x3c0 at abrunt1.c:339 [dw.sapRD3_DVEBMGS00]
(8) 0x4000000003d9f210 Z8abtriggv + 0x110 at abrunt1.c:58 [dw.sapRD3_DVEBMGS00]
(9) 0x4000000003d9ebe0 ab_run + 0xc0 [dw.sapRD3_DVEBMGS00]
(10) 0x4000000001caa820 N_ab_run + 0x20 at dymainstp.c:4739 [dw.sapRD3_DVEBMGS00]
(11) 0x4000000001cb40f0 dynpmcal + 0x3f0 at dymainstp.c:2281 [dw.sapRD3_DVEBMGS00]
(12) 0x4000000001caf260 dynppai0 + 0xcb0 at dymainstp.c:1107 [dw.sapRD3_DVEBMGS00]
(13) 0x4000000001cb1ec0 dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
(14) 0x4000000001c9dff0 dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
(15) 0x4000000001fea460 Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
(16) 0x4000000001fb54e0 TskhLoop + 0x5520 at thxxhead.c:3945 [dw.sapRD3_DVEBMGS00]
(17) 0x4000000001faae40 ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
(18) 0x4000000001569ec0 DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
(19) 0x4000000002c10630 nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
(20) 0x4000000002c105c0 main + 0x60 [dw.sapRD3_DVEBMGS00]
(21) 0xc00000000002be30 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
RSORAVSH
0
30.03.2005
10:21:59
19456
E
1
Prg
SAPMSSY0
1
17.12.2007
15:41:05
92160
E
2
Prg
SAPMSSYD
1
12.09.2006
11:33:31
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
8192
E
4
Prg
RSDBRUNT
0
17.12.2007
16:04:40
254976
E
5
Typ
RSSCR
0
30.03.2005
10:21:45
5120
6
Prg
RSDBSPBL
0
30.03.2005
10:21:58
72704
E
7
Prg
SAPDB__S
0
30.03.2005
10:22:01
19456
E
8
Prg
RSDBSPMC
0
12.09.2006
11:25:01
79872
E
9
Typ
DDSHDESCR
0
03.09.1997
03:05:16
4096
10
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
11
Prg
SAPLSABE
11
09.09.2004
14:18:36
13312
E
12
Prg
SAPLSECU
12
17.12.2007
15:31:45
87040
E
13
Typ
RSSUBINFO
0
14.10.1999
22:01:03
3072
14
Prg
SAPLSTUP
14
17.12.2007
15:29:58
74752
E
15
Prg
SAPLCNDP
15
11.09.2007
15:24:45
195584
E
16
Prg
SAPLSCNT
16
18.02.2005
14:16:06
30720
E
17
Prg
SAPSHDTV
16
05.01.2005
16:26:16
33792
E
18
Prg
SAPFGUICNTL
1
18.02.2005
14:15:08
24576
E
19
Prg
SAPLOLEA
19
11.09.2007
11:17:30
96256
E
20
Prg
SAPLSGUI
20
17.12.2007
15:41:05
84992
E
21
Prg
SAPLSTTM
21
05.07.2005
13:10:18
69632
E
22
Prg
SAPLSBDC
22
17.12.2007
15:30:54
44032
E
23
Prg
SAPLSFES
23
17.12.2007
16:04:40
260096
E
24
Prg
SAPLTHFB
24
17.12.2007
15:41:05
394240
E
25
Typ
WPINFO
0
26.02.1999
14:49:01
6144
26
Prg
SAPLURFC
26
17.12.2007
15:37:35
22528
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
29
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
30
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
31
Typ
SYST
0
09.09.2004
14:18:12
31744
32
Typ
MONI
0
31.03.2004
16:41:21
5120
Directory of Application Tables
Name Date Time Lngth
Val.
Program RSORAVSH
SYST 09.09.2004 14:18:12 00004612
\0\0\0\0\0\x0010\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
MONI . . : : 00002944
\0\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
71
PAR2
03
0000
0014
002B
RSORAVSH
37
73
PAR2
03
0000
0015
002D
RSORAVSH
37
75
PAR2
03
0000
0016
0026
RSORAVSH
37
77
00
0000
RSORAVSH
37
78
PERP
00
0002
RSORAVSH
44
79
PERP
1C
0000
RSORAVSH
44
80
PERP
04
0000
RSORAVSH
44
81
mvqk
10
0005
0044
04EC
RSORAVSH
45
83
mvqk
0C
0005
0054
052E
RSORAVSH
46
85
DSQL
00
0017
RSORAVSH
48
86
DSQL
01
0018
RSORAVSH
48
87
DSQL
04
0025
RSORAVSH
48
>>>>>
DSQL
16
0025
RSORAVSH
48
89
BRAN
05
0004
RSORAVSH
48
90
perf
00
000A
RSORAVSH
48
91
PERP
80
0000
RSORAVSH
48
92
BRAX
00
FFFC
RSORAVSH
48
93
DSQL
23
0000
RSORAVSH
48
94
ENDF
00
0000
RSORAVSH
56
95
00
0000
RSORAVSH
56
===========
===========
Please check and advise.
Also, I am trying to search for the note 6083 in market place, but not getting the same.
Please advise.
Thanks & Regards
Sudip -
Solution manager 7.1 installation in ECC 6.0 landscape
Dear All,
I am planning to install solman 7.1 SP04 in my landscape where the managed systems are running on ECC 6.0. SP 07(PRD, DEV,...).
Is it fine to start installation with current landscape or i need to upgrade the ECC version.
Any documents available regarding the technical system patch level requirements for Solution manager 7.1 installation.
Please suggest.Hi Jithu,
Pls refer below links,
Solution Manager installation 7.1
SAP Solution Manager 7.1 – SAP Help Portal Page
Dia Agent Connect To system in solman 7.1 sp10
Regards
K.N -
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".
Maybe you are looking for
-
Hi guys. I am a java programmer for a couple of years now but I could never learn regular expressions in this or any other language. My problem is that I want to use String's replaceAll method to replace all HTML structures from a string. Actually, I
-
Hi, we basically have an on-line job application that we need to be sent to us via e-mail notification every time a user submits a response, not with the raw data output from the form fields like the current e-mail notification setting allows, but as
-
Dear All, This problem is troubling me for the past 1 month. I am completely unable to proceed. I want my Oracle 9i AS to run on Linux Box. I have linuk 8.0 and Oracle 9.0.3 AS (J2EE & Webcache Disk1 alone). The first time when I tried to install 9.0
-
I have a MobileMe account that has my Web Gallery already posted to it... I have switched MobileMe accounts and now I want those same published photo albums published to my NEW MobileMe account. How can I get it to publish to this new account without
-
CC subscription won't let me start CS Apps
My subscription to CC ended a few days ago and I have since been unable to start any of my CS6 apps. I get a subscription box telling me that I need to renew my sub. I have uninstalled everything Adobe from my system and used their tool to clean the