CUA & solution manager
Hi Experts,
I have difference modules implemented for my client like ECC,HSCM,SRM,PI ect..... with huge landcale and clients want to gr for CUA. My query is can we use Solution Manager as a CUA for managing all the security related task centrall for all above mentioned system?
Have any one of you come across the GRC CUA option and what is the best practise for CUA?
Please provide me with document if you have any for any of the option.
Thanks,
Security consultant
Hi,
You could use your solman as a CUA system (in the same productive client or in a seperate client of solman). But this means that your solman would by a HA system, in case restart needed, the whole landscape will be impacted......
By the way, CUA would be totally replaced by IDM in the future because of his limit ( only manage abap systems, no workflow....)
I would not recommend any CUA implementation in the landscape. Hope this helps you.
BRs,
jiamin pan
Similar Messages
-
Delete the old CUA and build a new CUA on the Solution Manager
Hello together,
I'm about to delete the old CUA and build a new CUA on the Solution Manager.
The users are in multiple systems almost the same.
This raises the following questions:
If I export the printers from the old CUA in a file and import into the new CUA (Solution Manager, then the printer can be administered directly in Solman?
Furthermore, if I depended on the second or third child System and attached to the new CUA, the user description data are not overwritten, as bsp: with the description data of the last-connected system?
By delete the CUA child system in which users are blocked. Can you handle it?
I thank you in advance
Mirsad> If I export the printers from the old CUA in a file and import into the new CUA (Solution Manager, then the printer can be administered directly in Solman?
-->the assignment of printers, not the printers themselves of course....
> Furthermore, if I depended on the second or third child System and attached to the new CUA, the user description data are not overwritten, as bsp: with the description data of the last-connected system?
If you mean adress data, already existing adresses are not overwritten. Such users will show up in scug as 'identical' or different' and can be handled accordingly.
> By delete the CUA child system in which users are blocked. Can you handle it?
Users without assignement to the central system get a global lock if the cua is removed in the central system. They still exist in usr02 in the central system, but with the global lock flag as indication, that they existed only for adminstrative means. The local lock flags in the child systems stay untouched. So if you take over these users into the new CUA they get the correct lock flag form the child system.
b.rgds, Bernhard -
We have SAP CUA on Solution manager 4.0
Hi,
We have SAP CUA on solution manager 4.0,SAP BASIS component 700. Do you know what is the latest Support pack and version for solution manager and what is netweaver identity management.Which one is better for CUA environment
Thanks and Regards
Yakoob.Hi,
Netweaver Identity Management (IdM) should replace SAP Central user administration (CUA) somewhere in the future. As far as I know SAP still supports CUA but doesn't develop further enhancements for it, because they see IDM as the new product. So when you still want to work with CUA then you can create a new one on your new SolMan and you have to move the administration to this one.
Regards, Basti -
Completely remove CUA from Solution Manager
Hi All
I currently have an issue with our Solution Manager system, once of our Basis team has attempted to implement the CUA on solution manager, however this has obviously gone wrong at some point and now we have a huge collection of users in our solution manager system and a massive amount of alerts in our Work Centre.
Is there anyway I can remove this and get some of the config out?
Any help would be great
Thanks
PhilHi,
users, which had no system assignement to your central system (existedphysically only in child systems) got locked by running rsdelcua in your central system. Just check the change logs for today (date of deletion of the CUA) of your users. All users who got the lock flag at the time rsdelcua had been run, don't need access to your former central system and could be removed.
b.rgds, Bernhard
oh, that is what the result-section of the a.m. link says....
sorry.
Edited by: Bernhard Hochreiter on Mar 19, 2010 10:35 AM -
System Monitoring with Solution Manager Ehp1
Hi,
I'm Tomas Piqueres, and I'm working in a VAR SAP with Solution Manager.
Recently, we installed Solution Manager Ehp1 and we are trying to configure it for System Monitoring. When I worked with Solution Manager SP17 I used to go to transaction RZ21 to add the system I wanted to monitoring and then put the SID and RFCs of the system.
Now with Solution Manager Ehp1, when I create the system in transaction RZ21, first I have to set the Component Type to Be Monitored and then the SID, Message Server Logon Group, the client and user are set automatically, and the password I've set to user CSMREG.
when I fill all the entries, I can see the RFCs used for the monitoring of the system. Those RFCs are set automatically:
<SID>_RZ20_COLLECT
<SID>_RZ20_ANALYZE
I can't edit those RFCs, so I have to create it manually. I check that RFCs destination works fine and both pass the authorization test, so when I try to save the system at transaction RZ21, I see the following errors:
<SID>_RZ20_COLLECT_123539Error when opening an RFC connection
Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection
Error during remote call of SALC function: Error when opening an RFC connection
Error during remote call of RFC1 function: Error when opening an RFC connection
I've been looking for information about those errors and how to monitoring with Solution Manager Ehp1, but I haven't found anything usefull.
Please, Could you help me?
Thanks and regards,
Tomas.Tomas,
I need to configure EWA from my Solman system and I completed the steps (defining and creation of RFC destinations to the target systems from my Solman system). I downloaded the lates ccmsagent file from the market place based my target system configurations.
Herewith attaching the logs while I'm trying to check the profile parameter.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sappfpar check pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
== Checking profile: /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
***WARNING: Unexpected parameter: DIR_EPS =/usr/sap/trans/EPS/----
***WARNING: Unexpected parameter: SAPSECULIB =/usr/sap/TQA/SYS/exe/run/libsapsecu.o
***WARNING: Unexpected parameter: abap/buffersize_part1 =1200000
***WARNING: Unexpected parameter: auth/auth_number_in_userbuffer =5000
***WARNING: Unexpected parameter: dbs/io_buf_size =100000
***WARNING: Unexpected parameter: rsau/local/file =/usr/sap/TQA/DVEBMGS30/log/audit/audit_++++++++
***WARNING: Unexpected parameter: rsau/selector1/class =35
***WARNING: Unexpected parameter: rsau/selector1/severity =2
***WARNING: Unexpected parameter: rsdb/rclu/cachelimt =0
***ERROR: Size of shared memory pool 40 too small
================================================================
SOLUTIONS: (1) Locate shared memory segments outside of pool 40
with parameters like: ipc/shm_psize_<key> =0
SOLUTION: Increase size of shared memory pool 40
with parameter: ipc/shm_psize_40 =1472000000
Shared memory disposition overview
================================================================
Shared memory pools
Key: 10 Pool
Size configured.....: 642000000 ( 612.3 MB)
Size min. estimated.: 637597428 ( 608.1 MB)
Advised Size........: 640000000 ( 610.4 MB)
Key: 40 Pool for database buffers
Size configured.....: 1048000000 ( 999.4 MB)
Size min. estimated.: 1468229308 (1400.2 MB)
Advised Size........: 1472000000 (1403.8 MB)
Shared memories inside of pool 10
Key: 1 Size: 2500 ( 0.0 MB) System administration
Key: 4 Size: 523648 ( 0.5 MB) statistic area
Key: 7 Size: 14838 ( 0.0 MB) Update task administration
Key: 8 Size: 67108964 ( 64.0 MB) Paging buffer
Key: 9 Size: 134217828 ( 128.0 MB) Roll buffer
Key: 11 Size: 500000 ( 0.5 MB) Factory calender buffer
Key: 12 Size: 6000000 ( 5.7 MB) TemSe Char-Code convert Buf.
Key: 13 Size: 200500000 ( 191.2 MB) Alert Area
Key: 16 Size: 22400 ( 0.0 MB) Semaphore activity monitoring
Key: 17 Size: 2672386 ( 2.5 MB) Roll administration
Key: 30 Size: 37888 ( 0.0 MB) Taskhandler runtime admin.
Key: 31 Size: 4806000 ( 4.6 MB) Dispatcher request queue
Key: 33 Size: 39936000 ( 38.1 MB) Table buffer, part.buffering
Key: 34 Size: 20480000 ( 19.5 MB) Enqueue table
Key: 51 Size: 3200000 ( 3.1 MB) Extended memory admin.
Key: 52 Size: 40000 ( 0.0 MB) Message Server buffer
Key: 54 Size: 20488192 ( 19.5 MB) Export/Import buffer
Key: 55 Size: 8192 ( 0.0 MB) Spool local printer+joblist
Key: 57 Size: 1048576 ( 1.0 MB) Profilparameter in shared mem
Key: 58 Size: 4096 ( 0.0 MB) Enqueue ID for reset
Key: 62 Size: 85983232 ( 82.0 MB) Memory pipes
Shared memories inside of pool 40
Key: 2 Size: 31168040 ( 29.7 MB) Disp. administration tables
Key: 3 Size: 114048000 ( 108.8 MB) Disp. communication areas
Key: 6 Size: 1064960000 (1015.6 MB) ABAP program buffer
Key: 14 Size: 28600000 ( 27.3 MB) Presentation buffer
Key: 19 Size: 90000000 ( 85.8 MB) Table-buffer
Key: 42 Size: 13920992 ( 13.3 MB) DB TTAB buffer
Key: 43 Size: 43422392 ( 41.4 MB) DB FTAB buffer
Key: 44 Size: 8606392 ( 8.2 MB) DB IREC buffer
Key: 45 Size: 6558392 ( 6.3 MB) DB short nametab buffer
Key: 46 Size: 20480 ( 0.0 MB) DB sync table
Key: 47 Size: 13313024 ( 12.7 MB) DB CUA buffer
Key: 48 Size: 300000 ( 0.3 MB) Number range buffer
Key: 49 Size: 3309932 ( 3.2 MB) Spool admin (SpoolWP+DiaWP)
Shared memories outside of pools
Key: 18 Size: 1792100 ( 1.7 MB) Paging adminitration
Key: 41 Size: 25010000 ( 23.9 MB) DB statistics buffer
Key: 63 Size: 409600 ( 0.4 MB) ICMAN shared memory
Key: 64 Size: 4202496 ( 4.0 MB) Online Text Repository Buf.
Key: 65 Size: 4202496 ( 4.0 MB) Export/Import Shared Memory
Key: 1002 Size: 400000 ( 0.4 MB) Performance monitoring V01.0
Key: 58900130 Size: 4096 ( 0.0 MB) SCSA area
Nr of operating system shared memory segments: 9
Shared memory resource requirements estimated
================================================================
Nr of shared memory descriptors required for
Extended Memory Management (unnamed mapped file).: 64
Total Nr of shared segments required.....: 73
System-imposed number of shared memories.: 1000
Shared memory segment size required min..: 1472000000 (1403.8 MB)
System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)
Swap space requirements estimated
================================================
Shared memory....................: 2050.4 MB
..in pool 10 608.1 MB, 99% used
..in pool 40 999.4 MB, 140% used !!
..not in pool: 34.4 MB
Processes........................: 716.8 MB
Extended Memory .................: 8192.0 MB
Total, minimum requirement.......: 10959.2 MB
Process local heaps, worst case..: 1907.3 MB
Total, worst case requirement....: 12866.5 MB
Errors detected..................: 1
Warnings detected................: 9
After checking the profile parameter I tried to run sapccm4x in /run directory but got the below error and I'm not able tomove further.
Pls have a look at these two and let me know what could I do to proceed further.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sapccm4x -R pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO: CCMS agent sapccm4x working directory is /usr/sap/TQA/DVEBMGS30/log/sapccm4x
INFO: CCMS agent sapccm4x config file is /usr/sap/TQA/DVEBMGS30/log/sapccm4x/csmconf
INFO: Central Monitoring System is [SMP]. (found in config file)
additional CENTRAL system y/[n] ? :
INFO: found ini file /usr/sap/TQA/DVEBMGS30/log/sapccm4x/sapccmsr.ini.
INFO:
CCMS version 20040229, 64 bit, multithreaded, Non-Unicode
compiled at Jun 28 2010
systemid 324 (IBM RS/6000 with AIX)
relno 6400
patch text patch collection 2010/1, OSS note 1304480
patchno 335
INFO Runtime:
running on saptqa01 AIX 3 5 00069A8FD600
running with profile /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO profile parameters:
alert/MONI_SEGM_SIZE = 200000000
alert/TRACE = 1
SAPSYSTEM = 30
SAPSYSTEMNAME = TQA
SAPLOCALHOST = saptqa01
DIR_CCMS = /usr/sap/ccms
DIR_LOGGING = /usr/sap/TQA/DVEBMGS30/log
DIR_PERF = /usr/sap/tmp
INFO:
pid 4165682
INFO: Attached to Shared Memory Key 13 (size 200141728) in pool 10
INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for application server saptqa01_TQA_30, created with version CCMS version 20040229, 64 bit single threaded, compiled at Oct 3 2008, kernel 6400_20020600_254, platform 324 (IBM RS/6000 with AIX)]
segment status ENABLED
segment started at Tue Sep 14 09:35:56 2010
segment version 20040229
ERROR: Shared Memory misconfiguration ==> can not monitor SAP application server saptqa01_TQA_30
Dispatcher Admin Shared Memory (Key 01) and CCMS Shared Memory (Key 13) both in pool 10.
Please change configuration with profile parameters
ipc/shm_psize_01 = -<different pool nr>
xor
ipc/shm_psize_13 = -<different pool nr>
EXITING with code 1 -
User synchronization issue between Active Directory and Solution manager.
Requirement:
Synchronize the users between Active directory and solution manager system.
<u>What we did:</u>
1. Created RFC connection (LDAP_RFC) for LDAP connector.
2. Created new LDAP connector that utilize the RFC (LDAP_RFC).
3. Created new logical LDAP Server(CUA).Here we have to maintain the connection
details to the physical directory.
4. We maintained the communication user that is used by the LDAP connector to bind the LDAP Directory Server.
5. In transaction LDAPMAP specific SAP data fields, we mapped to the desired
directory attributes.
6. Testing from LDAP transaction working fine. We are able to see the attributes and
values from Active directory.
<b><u>Issue:</u></b>
When executed the program RSLDAPSYNC_USER for user synchronization from t-code se38 with below selection .
LDAP Server = CUA (created earlier)
LDAP Connector = LDAP_RFC (RFC connection created created ealier)
In the tab: (Object that exist both in the directory and in the Database:)
Selected: Compare Time Stamp.
In the tab: (Objects the only exist in the Directory.)
Selected : Create in Database.
In the tab(Objects that only Exist in the Database:
Selected: Ignore Object.
Result from the report shows that connection to LDAP server is fine and 0(zero) objects in Directory.
The program does not create any new user in the Solution Manager system.
Any help on this issue greatly appreciated.
Thanks & Regards,
Harishwhere did you see this error ? is there anymore details.
i think the account you are using for Sync does not have Replicate Directory Changes permission in AD. follow below article and give Replicate directory changes permission.
http://technet.microsoft.com/en-us/library/hh296982(v=office.15).aspx
Thanks, Noddy -
How to start the Solution Manager Implementation
Hi Gurus , I am in Solution manager implemnetation project , and i wanted built the exsisted landscape into Solman so any one can help me out in this like where to and how to start.
Hi Gurus, i wanted to implement these concepts
Configuring Solution Manager
Configuring Solution Manager
1) Solution Monitoring
a SAP EarlyWatch Alert
a1 Setting-Up EarlyWatch Alerts Y
a2 Manually Executing Downloads Y
a3 Create Report and Display Session Details Y
a4 Save, Retrieve and Archive EarlyWatch Alert Y
b Service Level Reporting
b1 Service Level Reporting Change Mode Y
b2 Maintain General Settings Y
b3 Specify Systems and Contents for Service Level Report Y
b4 Select Business Processes for the Service Level Report Y
b5 Select Business Processes from the Business Process Monitoring Y
b6 Process Service Level Report Data Manually Y
b7 Create Service Level Report Y
b8 Create, Save and Archive Service Level Report Manually Y
b9 Process Service Level Report Session Y
b10 Send E-Mail Automatically Y
b11 KPI Calculation Y
2 Configuring Alert Monitor
Central System Administration (Part of ALERT Monitor)
c2.1 MTE Classes and Attribute Groups Y
c2.2 Methods Y
c2.3 Operating the Alert Monitor Y
c2.4 Actions in the Alert Monitoring Tree Y
c2.5 Selecting Nodes in the Alert Monitoring Tree Y
c2.6 Elements of the Alert Monitor Y
c2.7 General Properties of Monitoring Tree Elements Y
c2.8 Properties of Monitoring Objects and Attributes Y
c2.9 Customizing the Alert Monitor Y
c2.10
Changing Properties in the Alert Monitoring Tree
Y
c2.11
Changing Properties in Customizing Transaction RZ21
Y
c2.12
Triggering a Heartbeat Alert if No Values Are Reported
Y
c2.13
Changing the Frequency of Method Execution
Y
c2.14 Defining, Releasing, and Transporting Methods
Y
c2.15
Assigning Methods to MTE Classes or Individual MTEs
Y
c2.16 Assigning Methods to MTE Classes or Individual MTEs Y
c2.17
Editing Monitors and Monitor Sets
Y
c2.18
Creating and Editing Monitor Sets
Y
c2.19 Transporting Monitor Sets and Monitor Definitions Y
c2.20 Copying, Renaming, and Deleting Monitors Y
c2.21 Creating and Changing Monitors Y
c2.22 Rule Node: Rule Description and Use Y
c2.23 Defining Monitors with the DEFINE_R3_SYSTEMS/GET_MTE_BY_CLASS Ru Y
c2.24 Defining Monitors with the Rule GET_MTE_BY_CLASS_AND_OPTIONS Y
c2.25 Defining Monitors with the Rule GET_MTE_BY_CLASS_AS_VIRTUAL Y
c2.26 Copying a Monitoring Properties Variant Y
c2.27 Create Monitoring Properties Variant Y
c2.28 Change Monitoring Properties Variant Y
c2.29 Activating a Monitoring Properties Variant Y
c2.30 SAP-DEFAULT Y
c2.31 Creating a New SAP-DEFAULT Variant Y
c2.32 Monitoring Multiple Systems Y
c2.33 Monitoring Multiple Systems: Defining RFC Connections Y
c2.34 Monitoring SAP R/3 3.x Systems Y
c2.35 Creating the CSMREG User Y
c2.36 Monitoring Multiple Systems with an Identical System ID Y
c2.37 System Groups in the Alert Monitor Y
c2.38 Deactivating and Reactivating Monitoring Tree Elements Y
c2.39 Deleting and Restoring Nodes in the Alert Monitoring Tree Y
c2.40 Display Options of the Alert Monitor Y
c2.41 Saving and Resetting the Layout of a Monitor Y
c2.42 Extending the Shared Memory Area Y
c2.43 Setting Up a Central Data Cache Y
c2.44 Configuring the Caches of the Monitoring Architecture Y
c2.45 Working with All-Clears (Green Alerts) Y
c2.46 Displaying the History of the Threshold Values of Performance No Y
c2.47 Availability Monitoring with CCMSPING Y
c2.48 Installing Availability Agent CCMSPING Y
c2.49 Changing the Monitoring Frequency and Timeouts of CCMSPING Y
c2.50 Adding Systems to the Availability Monitoring Manually Y
c2.51 Finding and Correcting Errors with CCMSPING Y
c2.52 Configuring Availability Monitoring Y
c2.53 Creating and Changing Monitoring Rules Y
c2.54 Changing Monitoring Setting of Servers and Groups Y
c2.55 Using Multiple CCMSPING Agents Y
c2.56 Creating and Changing a Monitoring Pause Y
c2.57 Monitoring System Groups with CCMSPING Y
c2.58 Availability and Performance Overview Monitor Y
c2.59 Monitoring Log Files with CCMS Agents Y
c2.60 Structure of the Log File Template of the Log File Agent Y
c2.61 Example Log File Templates Y
c2.62 Logfile Monitoring Monitor Y
c2.63 Monitoring Selected Processes with SAPOSCOL Y
c2.64 Monitoring Response Times of Transactions or Clients Y
c2.65 Monitoring Database Tables with the Alert Monitor Y
c2.66 Self-Monitoring of the Alert Monitor Y
c2.67 Selected Alert Monitor Methods Y
c2.68 Forwarding Alerts to Alert Management (ALM) Y
c2.69 Interpreting a Text Attribute as File Name/URL and Display Content Y
c2.70 Displaying a Subtree as ALV Grid Control Y
c2.71 Defining an Automatic Alert Notification Y
c2.72 Auto-Reaction Method: Execute Operating System Command Y
c2.73 Setting Up Central Auto-Reaction Methods Y
c2.74 Installing CCM4X Y
c2.75 Activation in the background,if the Host restarts Y
c2.76 Creating RFC Connection Y
c2.77 Copying File from Solution manager to agents Y
c2.78 Copying version for SAPCCM4X Y
c3 Central User Administartion(CUA)
c3.01 Create manaintain landscape Y
c3.02 Creating RFC Y
c3.03 Create Logical clinets in SM1 Y
c3.04 Field distribution parameters Y
c3.05 Transfering users from child system Y
2 Service Desk
a Set-Up Message Creation in Web Browser Y
b Create support messages with NOTIF_CREATE Y
c Process Messages in Service Desk Y
d Search for Solutions to Support Messages Y
e Copy Support Message into Solution Database Y
f Forward Support Message to SAP Y
g WebClient Interaction Center Y
h Create Messages with Interaction Center WebClient Y
i Process Messages in the Interaction Center WebClient Y
j Service Desk for IT Service Providers Y
k Using an External Service Desk Y
l Connect an External Service Desk Y
m Service Desk Customizing Error Analysis Y
it's very high prioriety
Cheers -
Solution Manager's Dispatcher is STOP.
Hi Experts,
I have installed Solution manager successfully on windows 2003.
On the same Server I have successfully installed ERP 2005.Now Solution manager's Dispatcher is STOP,where ERP 2005 is running successfully. If anybody know the solution please help me out.
Points would be rewarded for the same.
Thanks n Regards
Ajit KeshriHi Markus
Here is log dev_w0
trc file: "dev_w0", trc level: 1, release: "700"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, MJ
B
B Mon Apr 21 15:15:01 2008
B create_con (con_name=R/3)
B Loading DB library 'E:\usr\sap\DEV\DVEBMGS00\exe\dboraslib.dll' ...
B Library 'E:\usr\sap\DEV\DVEBMGS00\exe\dboraslib.dll' loaded
B Version of 'E:\usr\sap\DEV\DVEBMGS00\exe\dboraslib.dll' is "700.08", patchlevel (0.73)
B New connection 0 created
M sysno 00
M sid DEV
M systemid 562 (PC with Windows NT)
M relno 7000
M patchlevel 0
M patchno 111
M intno 20050900
M make: multithreaded, Unicode, 64 bit, optimized
M pid 5372
M
M kernel runs with dp version 229000(ext=109000) (@(#) DPLIB-INT-VERSION-229000-UC)
M length of sys_adm_ext is 576 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 5372) [dpxxdisp.c 1301]
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M
M Mon Apr 21 15:15:02 2008
M DpShMCreate: sizeof(wp_adm) 8880 (1480)
M DpShMCreate: sizeof(tm_adm) 5584592 (27784)
M DpShMCreate: sizeof(wp_ca_adm) 24000 (80)
M DpShMCreate: sizeof(appc_ca_adm) 8000 (80)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080
M DpShMCreate: sizeof(comm_adm) 552080 (1088)
M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
M DpShMCreate: sizeof(slock_adm) 0 (104)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm) 0 (72)
M DpShMCreate: sizeof(vmc_adm) 0 (1864)
M DpShMCreate: sizeof(wall_adm) (41664/36752/64/192)
M DpShMCreate: sizeof(gw_adm) 48
M DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000F270050, size: 6264768)
M DpShMCreate: allocated sys_adm at 000000000F270050
M DpShMCreate: allocated wp_adm at 000000000F272150
M DpShMCreate: allocated tm_adm_list at 000000000F274400
M DpShMCreate: allocated tm_adm at 000000000F274460
M DpShMCreate: allocated wp_ca_adm at 000000000F7C7B30
M DpShMCreate: allocated appc_ca_adm at 000000000F7CD8F0
M DpShMCreate: allocated comm_adm at 000000000F7CF830
M DpShMCreate: system runs without slock table
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 000000000F8564C0
M DpShMCreate: allocated gw_adm at 000000000F856540
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 000000000F856570
M DpShMCreate: allocated wall_adm at 000000000F856580
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation view
X <EsNT> Using memory model view.
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M ThInit: running on host visu1
M
M Mon Apr 21 15:15:03 2008
M calling db_connect ...
C Prepending E:\usr\sap\DEV\DVEBMGS00\exe to Path.
C Oracle Client Version: '10.2.0.1.0'
C Client NLS settings: AMERICAN_AMERICA.UTF8
C Logon as OPS$-user to get SAPSR3's password
C Connecting as /@DEV on connection 0 (nls_hdl 0) ... (dbsl 700 110706)
C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
C 0 UTF8 1 00000000138620C0 00000000081DB600 00000000081DCE28
C Attaching to DB Server DEV (con_hdl=0,svchp=00000000081DCCE8,svrhp=0000000013881118)
C Starting user session (con_hdl=0,svchp=00000000081DCCE8,srvhp=0000000013881118,usrhp=00000000081DBE18)
C
C Mon Apr 21 15:15:04 2008
C Now '/@DEV' is connected (con_hdl 0, nls_hdl 0).
C *** ERROR => ORA-1403 when accessing table SAPUSER
[dbsloci.c 11295]
C Disconnecting from connection 0 ...
C Closing user session (con_hdl=0,svchp=00000000081DCCE8,usrhp=00000000081DBE18)
C Now I'm disconnected from ORACLE
C Try to connect with default password
C Connecting as SAPSR3/<pwd>@DEV on connection 0 (nls_hdl 0) ... (dbsl 700 110706)
C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
C 0 UTF8 1 00000000138620C0 00000000081DB600 00000000081DCE28
C Starting user session (con_hdl=0,svchp=00000000081DCCE8,srvhp=0000000013881118,usrhp=00000000081DBE18)
C Now 'SAPSR3/<pwd>@DEV' is connected (con_hdl 0, nls_hdl 0).
C Database NLS settings: AMERICAN_AMERICA.UTF8
C Database instance DEV is running on VISU1 with ORACLE version 10.2.0.1.0 since 20080421
B
B Mon Apr 21 15:15:05 2008
B Connection 0 opened (DBSL handle 0)
B Wp Hdl ConName ConId ConState TX PRM RCT TIM MAX OPT Date Time DBHost
B 000 000 R/3 000000000 ACTIVE NO YES NO 000 255 255 20080421 151502 VISU1
M db_connect o.k.
M ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,.sar,.gif
I
I Mon Apr 21 15:15:14 2008
I MtxInit: 0 0 0
M SHM_PRES_BUF (addr: 0000000016100050, size: 4400000)
M SHM_ROLL_AREA (addr: 000007FFF3290050, size: 61440000)
M SHM_PAGING_AREA (addr: 0000000016540050, size: 32768000)
M SHM_ROLL_ADM (addr: 000000000B1C0050, size: 615040)
M SHM_PAGING_ADM (addr: 000000000FE00050, size: 525344)
M ThCreateNoBuffer allocated 544152 bytes for 1000 entries at 000000000FE90050
M ThCreateNoBuffer index size: 3000 elems
M ThCreateVBAdm allocated 12176 bytes (50 server) at 000000000FF20050
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation view
X ES initialized.
B db_con_shm_ini: WP_ID = 0, WP_CNT = 6, CON_ID = -1
B dbtbxbuf: Buffer TABL (addr: 000000001D920160, size: 30000000, end: 000000001F5BC4E0)
B dbtbxbuf: Buffer TABLP (addr: 000000001F5C0160, size: 10240000, end: 000000001FF84160)
B dbexpbuf: Buffer EIBUF (addr: 000000001FF90170, size: 4194304, end: 0000000020390170)
B dbexpbuf: Buffer ESM (addr: 00000000203A0170, size: 4194304, end: 00000000207A0170)
B dbexpbuf: Buffer CUA (addr: 00000000207B0170, size: 3072000, end: 0000000020A9E170)
B dbexpbuf: Buffer OTR (addr: 0000000020AA0170, size: 4194304, end: 0000000020EA0170)
B dbtran INFO (init_connection '<DEFAULT>' [ORACLE:700.08]):
B max_blocking_factor = 5, max_in_blocking_factor = 5,
B min_blocking_factor = 5, min_in_blocking_factor = 5,
B prefer_union_all = 0, prefer_join = 0,
B prefer_fix_blocking = 0, prefer_in_itab_opt = 1,
B convert AVG = 0, alias table FUPD = 0,
B escape_as_literal = 1, opt GE LE to BETWEEN = 0,
B select * =0x0f, character encoding = STD / <none>:-,
B use_hints = abap->1, dbif->0x1, upto->2147483647, rule_in->0,
B rule_fae->0, concat_fae->0, concat_fae_or->0
B
B Mon Apr 21 15:15:15 2008
B ***LOG BZA=> table APSRV does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
B Didn't get a server group from table APSRV, rc = 32
B ***LOG BZA=> table TBTCO does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
L *** ERROR => BtcMrkZombies: db_rsql-call failed, rc: 32 [btcclean.c 572]
B
B Mon Apr 21 15:15:16 2008
B ***LOG BZA=> table USR41 does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
M SecAudit(RsauInit): Start init of Security Audit Log for first wp.
M SecAudit(RsauCreateShm): New block for Security Audit Log allocated in SCSA
M SecAudit(RsauCreateShm): SCSA memory usage: SecAudit = 1160, total = 3064
M SecAudit(RsauShmInit): SCSA size................ = 4096
M SecAudit(RsauShmInit): addr of SCSA............. = 000000000AF10050
M SecAudit(RsauShmInit): addr of RSAUSHM.......... = 000000000AF107C0
M SecAudit(RsauShmInit): addr of RSAUSLOTINFO..... = 000000000AF10800
M SecAudit(RsauShmInit): addr of RSAUSLOTS........ = 000000000AF1080C
M SecAudit(RsauShmInit): SHM version.............. = 5
M SecAudit(RsauShmInit): SHM Slot version......... = 2
M SecAudit(RsauShmInit): RSAU active.............. = 0
M SecAudit(RsauShmInit): number of slots possible. = 10
M SecAudit(RsauShmInit): number of slots requested = 2
M SecAudit(RsauShmInit): number of slots used..... = 2
M SecAudit(RsauShmInit): user selection........... = 0
M SecAudit(RsauShmInit): max size of one file..... = 0 KB
M SecAudit(RsauShmInit): max size of all files.... = 102400 KB
M SecAudit(RsauGetCurrentProfile): Init of shared memory completed
M SecAudit(RsauGetCurrentProfile): Security Audit Log not active
M SsfSapSecin: automatic application server initialization for SAPSECULIB
N SsfSapSecin: Looking for PSE in database
N SsfPseLoad: started...(path=E:\usr\sap\DEV\DVEBMGS00\sec, AS=visu1, instanceid=00)
B ***LOG BZA=> table SSF_PSE_H does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
N *** ERROR => SsfPseLoad: db_rsql94 - RS_FETCH on SSF_PSE_H failed with rc=32 [ssfxxpse.c 767]
N SsfPseLoad: ended (0 of 0 sucessfully loaded, 0 checked...
B ***LOG BZA=> table CVERS does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
B *** ERROR => Buffer loading failed: {fcode=225, rc=32, cnt=0, table='CVERS'}
[dbrsbuf.c 1784]
B ***LOG BZA=> table CVERS does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
B ***LOG BZA=> table T002C does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
B ***LOG BZA=> table T002 does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
B *** ERROR => Buffer loading failed: {fcode=225, rc=32, cnt=0, table='T002'}
[dbrsbuf.c 1784]
N MskiCreateLogonTicketCache: Logon Ticket cache created in shared memory.
N MskiCreateLogonTicketCache: Logon Ticket cache pointer registered in shared memory.
B ***LOG BZA=> table PATCHHIST does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
M CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M CCMS: AlMsUpload called by wp 0.
M CCMS: AlMsUpload successful for E:\usr\sap\DEV\DVEBMGS00\log\ALMTTREE.DAT (219 MTEs).
B
B Mon Apr 21 15:15:17 2008
B ***LOG BZA=> table TCP00 does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
G Codepage converter switched to reinitialize state.
M ***LOG R19=> ThInit, rscpi_init ( codepages 000008) [thxxhead.c 1741]
M *** ERROR => .--============--
. [thxxhead.c 910]
M *** ERROR => | RSCP - Error | [thxxhead.c 910]
M *** ERROR => | Error from: Codepage handling (RSCP) | [thxxhead.c 910]
M *** ERROR => | code: 8 RSCPEIO Some I/O error. | [thxxhead.c 910]
M *** ERROR => | Codepage converter switched to reinitialize state. | [thxxhead.c 910]
M *** ERROR => | module: rscpmc no: 133 line: 1355 T100: TS004 | [thxxhead.c 910]
M *** ERROR => | TSL01: CQD | [thxxhead.c 910]
M *** ERROR => `----
' [thxxhead.c 910]
S *** init spool environment
S initialize debug system
T Stack direction is downwards.
T debug control: prepare exclude for printer trace
T new memory block 0000000013A97C00
S
S Mon Apr 21 15:15:18 2008
S spool kernel/ddic check: Ok
S using table TSP02FX for frontend printing
S 1 spool work process(es) found
S frontend print via spool service enabled
S printer list size is 150
S printer type list size is 50
S queue size (profile) = 300
S hostspool list size = 3000
S option list size is 30
S found processing queue enabled
S found spool memory service RSPO-RCLOCKS at 000000002A1C00D0
S doing lock recovery
S setting server cache root
S found spool memory service RSPO-SERVERCACHE at 000000002A1C02F0
S using messages for server info
S size of spec char cache entry: 297032 bytes (timeout 100 sec)
S size of open spool request entry: 2272 bytes
S immediate print option for implicitely closed spool requests is disabled
A
A -PXA--
A PXA INITIALIZATION
A PXA: # fragments > # work processes => using less fragments
A System page size: 4kb, total admin_size: 5432kb, dir_size: 5404kb.
A Attached to PXA (address 000007FFF6D30050, size 150000K)
A abap/pxa = shared protect gen_remote
A PXA INITIALIZATION FINISHED
A -PXA--
A
B ***LOG BZA=> table SRTM_ACT does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
A ***Error in abrtm.c: DB-Error 32 opening table SRTM_ACT.
A ABAP ShmAdm initialized (addr=000007FF4FF13000 leng=20955136 end=000007FF5130F000)
A >> Shm MMADM area (addr=000007FF503ECDB0 leng=244096 end=000007FF50428730)
A >> Shm MMDAT area (addr=000007FF50429000 leng=15622144 end=000007FF5130F000)
A RFC Destination> destination visu1_DEV_00 host visu1 system DEV systnr 0 (visu1_DEV_00)
A RFC Options> H=visu1,S=00,d=2,
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A RFC Destination> DB RC = 2
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A RFC Destination> DB RC = 2
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A RFC Destination> DB RC = 2
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A RFC Destination> DB RC = 2
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A RFC Destination> DB RC = 2
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A RFC Destination> DB RC = 2
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A RFC Destination> DB RC = 2
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A RFC Destination> DB RC = 2
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
B ***LOG BZA=> table RFCDES does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A RFC Destination> DB RC = 2
A RFC FRFC> fallback activ but this is not a central instance.
A
A RFC rfc/signon_error_log = -1
A RFC rfc/dump_connection_info = 0
A RFC rfc/dump_client_info = 0
A RFC rfc/cp_convert/ignore_error = 1
A RFC rfc/cp_convert/conversion_char = 23
A RFC rfc/wan_compress/threshold = 251
A RFC rfc/recorder_pcs not set, use defaule value: 2
A RFC rfc/delta_trc_level not set, use default value: 0
A RFC rfc/no_uuid_check not set, use default value: 0
A RFC rfc/bc_ignore_thcmaccp_retcode not set, use default value: 0
A RFC Method> initialize RemObjDriver for ABAP Objects
B ***LOG BZA=> table CVERS does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A *** ERROR => No hotpackage number found [abload3.c 14145]
B ***LOG BZA=> table CVERS1 does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
B *** ERROR => Buffer loading failed: {fcode=225, rc=32, cnt=0, table='CVERS1'}
[dbrsbuf.c 1784]
B ***LOG BZA=> table CVERS1 does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A *** ERROR => isSubReleaseActive: unexpected code from db_setget: 2 [abload3.c 13997]
M ThrCreateShObjects allocated 6352 bytes at 000000000FFD0050
M
M Mon Apr 21 15:15:19 2008
M ThVBStartUp: restart pending update requests
B ***LOG BZA=> table V_LNAMES does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
B Couldn't read table V_LNAMES, rc = 32
B ***LOG BZA=> table VBHDR does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
M *** ERROR => ThVBMarkOldRq: db_rsql(RS_UPDATE) failed, rc: 32 [thxxvb.c 12316]
B ***LOG BZA=> table VBHDR does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
M *** ERROR => ThVBSearchEntries: db_rsql(RS_UPDATE) failed, rc: 32 [thxxvb.c 9908]
B ***LOG BZA=> table VBHDR does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
M *** ERROR => ThVBSearchEntries: db_rsql(RS_UPDATE) failed, rc: 32 [thxxvb.c 9908]
B ***LOG BZA=> table VBHDR does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
M *** ERROR => ThVBSearchEntries: db_rsql(RS_UPDATE) failed, rc: 32 [thxxvb.c 9908]
B ***LOG BZA=> table VBHDR does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
M *** ERROR => ThVBSearchEntries: db_rsql(RS_UPDATE) failed, rc: 32 [thxxvb.c 9908]
B ***LOG BZA=> table VBHDR does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
M *** ERROR => ThVBMark: db_rsql(RS_FETCH) failed, rc: 32 [thxxvb.c 4916]
N SsfSapSecin: putenv(SECUDIR=E:\usr\sap\DEV\DVEBMGS00\sec): ok
N SsfSapSecin: PSE E:\usr\sap\DEV\DVEBMGS00\sec\SAPSYS.pse found!
N
N =================================================
N === SSF INITIALIZATION:
N ===...SSF Security Toolkit name SAPSECULIB .
N ===...SSF trace level is 0 .
N ===...SSF library is E:\usr\sap\DEV\DVEBMGS00\exe\sapsecu.dll .
N ===...SSF hash algorithm is SHA1 .
N ===...SSF symmetric encryption algorithm is DES-CBC .
N ===...sucessfully completed.
N =================================================
N MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.
N MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.
M JrfcVmcRegisterNativesDriver o.k.
W =================================================
W === ipl_Init() called
B ***LOG BZA=> table IACFL does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
W ITS Plugin: Path dw_gui
W ITS Plugin: Description ITS Plugin - ITS rendering DLL
W ITS Plugin: sizeof(SAP_UC) 2
W ITS Plugin: Release: 700, [7000.0.111.20050900]
W ITS Plugin: Int.version, [33]
W ITS Plugin: Feature set: [14]
W ===... Calling itsp_Init in external dll ===>
W === ipl_Init() returns 0, ITSPE_OK: OK
W =================================================
E Enqueue Info: rdisp/wp_no_enq=1, rdisp/enqname=<empty>, assume visu1_DEV_00
E Replication is disabled
E EnqCcInitialize: local lock table initialization o.k.
E EnqId_SuppressIpc: local EnqId initialization o.k.
E EnqCcInitialize: local enqueue client init o.k.
M MBUF info for hooks: MS component UP
M ThSetEnqName: set enqname by server list
M ThISetEnqname: enq name = >visu1_DEV_00 <
E
E *************** EnqId_EN_ActionAtMsUpHook ***************
E Hook on upcoming Ms (with EnqSrv), get auth EnqId and check it locally
E
E *************** ObjShMem_CheckAuthoritativeEnqId ***************
E Checking authoritative EnqId from EnqSrv into ObjShMem
E ObjShMem_CheckAuthoritativeEnqId: ObjShMem ...
E EnqId.EnqTabCreaTime = -999
E EnqId.RandomNumber = -999
E ReqOrd.TimeInSecs = -999
E ReqOrd.ReqNumberThisSec = -999
E ObjShMem_CheckAuthoritativeEnqId: ObjShMem ...
E EnqId.EnqTabCreaTime = -999
E EnqId.RandomNumber = -999
E ReqOrd.TimeInSecs = -999
E ReqOrd.ReqNumberThisSec = -999
E ObjShMem_CheckAuthoritativeEnqId: EnqId is initial in ShMem
E ObjShMem_CheckAuthoritativeEnqId: Overwrite incoming auth EnqId, continue
E EnqId inscribed into initial ObjShMem: (ObjShMem_CheckAuthoritativeEnqId)
E -SHMEM--
E EnqId: EnqTabCreaTime/RandomNumber = 21.04.2008 15:15:19 1208771119 / 4560
E ReqOrd at Srv: TimeInSecs/ReqNumberThisSec = 21.04.2008 15:15:19 1208771119 / 2
E ReqOrd at Cli: TimeInSecs/ReqNumberThisSec = 21.04.2008 15:15:19 1208771119 / 1
E Status: STATUS_OK
E -
B ***LOG BZA=> table TSPSVI does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
S *** ERROR => -
> db_rtab Error 2, table TSPSVI, action rspogdio_update [rspogdio.c 424]
B ***LOG BZA=> table TSPSVI does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
S *** ERROR => -
> db_rtab Error 2, table TSPSVI, action rspogdio_insert [rspogdio.c 424]
B ***LOG BZA=> table TSPSV does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
S *** ERROR => -
> db_rtab Error 2, table TSPSV, action rspogdio_read [rspogdio.c 424]
B ***LOG BZA=> table TSPSVI does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
S *** ERROR => -
> db_rtab Error 2, table TSPSVI, action rspogdio_read [rspogdio.c 424]
M ThActivateServer: state = STARTING
L BtcSysStartRaise: Begin
L Raise event SAP_SYSTEM_START with parameter <visu1_DEV_00 >
L BtcSysStartRaise: End
B
B Mon Apr 21 15:15:21 2008
B ***LOG BZA=> table TCP0C does not exist on database R/3 [dbtran#11 @ 7494] [dbtran 7494 ]
B *** ERROR => Buffer loading failed: {fcode=225, rc=32, cnt=0, table='TCP0C'}
[dbrsbuf.c 1784]
B ***LOG BZA=> table TCP0C does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
A
A Mon Apr 21 15:15:22 2008
A ** RABAX: level LEV_RX_C_STACK completed.
A ** RABAX: level LEV_RX_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_INTERFACES entered.
A ** RABAX: level LEV_RX_INTERFACES completed.
A ** RABAX: level LEV_RX_GET_MESS entered.
A ** RABAX: level LEV_RX_GET_MESS completed.
A ** RABAX: level LEV_RX_INIT_SNAP entered.
A ** RABAX: level LEV_RX_INIT_SNAP completed.
A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_SN_C_STACK failed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_RX_WRITE_SNAP completed.
A ** RABAX: level LEV_RX_SET_ALERT entered.
A ** RABAX: level LEV_RX_SET_ALERT completed.
A ** RABAX: level LEV_RX_COMMIT entered.
A ** RABAX: level LEV_RX_COMMIT completed.
A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A ** RABAX: level LEV_RX_RESET_PROGS entered.
A ** RABAX: level LEV_RX_RESET_PROGS completed.
A ** RABAX: level LEV_RX_STDERR entered.
A Mon Apr 21 15:15:22 2008
A
A ABAP Program ????????????????????????????????????????.
A Source Line 0.
A Error Code DBIF_RTAB_ILLEGAL_CALL.
A Module $Id: //bas/700_REL/src/krn/runt/ablocale.c#3 $ SAP.
A Function SetTextEnv Line 507.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
B ***LOG BZA=> table TCP0C does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
A ** RABAX: level LEV_RX_C_STACK completed.
A ** RABAX: level LEV_RX_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_INTERFACES entered.
A ** RABAX: level LEV_RX_INTERFACES completed.
A ** RABAX: level LEV_RX_GET_MESS entered.
A ** RABAX: level LEV_RX_GET_MESS completed.
A ** RABAX: level LEV_RX_INIT_SNAP entered.
A ** RABAX: level LEV_RX_INIT_SNAP completed.
A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_SN_C_STACK failed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_RX_WRITE_SNAP completed.
A ** RABAX: level LEV_RX_SET_ALERT entered.
A ** RABAX: level LEV_RX_SET_ALERT completed.
A ** RABAX: level LEV_RX_COMMIT entered.
A ** RABAX: level LEV_RX_COMMIT completed.
A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A ** RABAX: level LEV_RX_RESET_PROGS entered.
A ** RABAX: level LEV_RX_RESET_PROGS completed.
A ** RABAX: level LEV_RX_STDERR entered.
A Mon Apr 21 15:15:22 2008
A
A ABAP Program ????????????????????????????????????????.
A Source Line 0.
A Error Code DBIF_RTAB_ILLEGAL_CALL.
A Module $Id: //bas/700_REL/src/krn/runt/ablocale.c#3 $ SAP.
A Function SetTextEnv Line 507.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
A ** RABAX: end no http/smtp
A ** RABAX: end RX_BTCHLOG|RX_VBLOG
A Error DBIF_RTAB_ILLEGAL_CALL occured. P1=[RTAB/RD /TCP0C ] P2=TCP0C .
A
S
S Mon Apr 21 15:15:23 2008
S server @>SSRV:visu1_DEV_00@< appears or changes (state 1)
B ***LOG BZA=> table TCP0C does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
A ** RABAX: level LEV_RX_C_STACK completed.
A ** RABAX: level LEV_RX_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_INTERFACES entered.
A ** RABAX: level LEV_RX_INTERFACES completed.
A ** RABAX: level LEV_RX_GET_MESS entered.
A ** RABAX: level LEV_RX_GET_MESS completed.
A ** RABAX: level LEV_RX_INIT_SNAP entered.
A ** RABAX: level LEV_RX_INIT_SNAP completed.
A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_SN_C_STACK failed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_RX_WRITE_SNAP completed.
A ** RABAX: level LEV_RX_SET_ALERT entered.
A ** RABAX: level LEV_RX_SET_ALERT completed.
A ** RABAX: level LEV_RX_COMMIT entered.
A ** RABAX: level LEV_RX_COMMIT completed.
A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A ** RABAX: level LEV_RX_RESET_PROGS entered.
A ** RABAX: level LEV_RX_RESET_PROGS completed.
A ** RABAX: level LEV_RX_STDERR entered.
A Mon Apr 21 15:15:23 2008
A
A ABAP Program ????????????????????????????????????????.
A Source Line 0.
A Error Code DBIF_RTAB_ILLEGAL_CALL.
A Module $Id: //bas/700_REL/src/krn/runt/ablocale.c#3 $ SAP.
A Function SetTextEnv Line 507.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
A ** RABAX: end no http/smtp
A ** RABAX: end RX_BTCHLOG|RX_VBLOG
A Error DBIF_RTAB_ILLEGAL_CALL occured. P1=[RTAB/RD /TCP0C ] P2=TCP0C .
A
S server @>SSRV:visu1_DEV_00@< appears or changes (state 1)
B ***LOG BZA=> table TCP0C does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
A ** RABAX: level LEV_RX_C_STACK completed.
A ** RABAX: level LEV_RX_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_INTERFACES entered.
A ** RABAX: level LEV_RX_INTERFACES completed.
A ** RABAX: level LEV_RX_GET_MESS entered.
A ** RABAX: level LEV_RX_GET_MESS completed.
A ** RABAX: level LEV_RX_INIT_SNAP entered.
A ** RABAX: level LEV_RX_INIT_SNAP completed.
A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_SN_C_STACK failed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_RX_WRITE_SNAP completed.
A ** RABAX: level LEV_RX_SET_ALERT entered.
A ** RABAX: level LEV_RX_SET_ALERT completed.
A ** RABAX: level LEV_RX_COMMIT entered.
A ** RABAX: level LEV_RX_COMMIT completed.
A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A ** RABAX: level LEV_RX_RESET_PROGS entered.
A ** RABAX: level LEV_RX_RESET_PROGS completed.
A ** RABAX: level LEV_RX_STDERR entered.
A Mon Apr 21 15:15:23 2008
A
A ABAP Program ????????????????????????????????????????.
A Source Line 0.
A Error Code DBIF_RTAB_ILLEGAL_CALL.
A Module $Id: //bas/700_REL/src/krn/runt/ablocale.c#3 $ SAP.
A Function SetTextEnv Line 507.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
B ***LOG BZA=> table TCP0C does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
A ** RABAX: level LEV_RX_C_STACK completed.
A ** RABAX: level LEV_RX_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_INTERFACES entered.
A ** RABAX: level LEV_RX_INTERFACES completed.
A ** RABAX: level LEV_RX_GET_MESS entered.
A ** RABAX: level LEV_RX_GET_MESS completed.
A ** RABAX: level LEV_RX_INIT_SNAP entered.
A ** RABAX: level LEV_RX_INIT_SNAP completed.
A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_SN_C_STACK failed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_RX_WRITE_SNAP completed.
A ** RABAX: level LEV_RX_SET_ALERT entered.
A ** RABAX: level LEV_RX_SET_ALERT completed.
A ** RABAX: level LEV_RX_COMMIT entered.
A ** RABAX: level LEV_RX_COMMIT completed.
A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A ** RABAX: level LEV_RX_RESET_PROGS entered.
A ** RABAX: level LEV_RX_RESET_PROGS completed.
A ** RABAX: level LEV_RX_STDERR entered.
A Mon Apr 21 15:15:23 2008
A
A ABAP Program ????????????????????????????????????????.
A Source Line 0.
A Error Code DBIF_RTAB_ILLEGAL_CALL.
A Module $Id: //bas/700_REL/src/krn/runt/ablocale.c#3 $ SAP.
A Function SetTextEnv Line 507.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
S
S Mon Apr 21 15:15:41 2008
S server @>SSRV:visu1_DEV_00@< appears or changes (state 1)
S server @>SSRV:visu1_DEV_00@< appears or changes (state 1)
B
B Mon Apr 21 15:16:11 2008
B ***LOG BZA=> table TCP0C does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
A ** RABAX: level LEV_RX_C_STACK completed.
A ** RABAX: level LEV_RX_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_INTERFACES entered.
A ** RABAX: level LEV_RX_INTERFACES completed.
A ** RABAX: level LEV_RX_GET_MESS entered.
A ** RABAX: level LEV_RX_GET_MESS completed.
A ** RABAX: level LEV_RX_INIT_SNAP entered.
A ** RABAX: level LEV_RX_INIT_SNAP completed.
A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_SN_C_STACK failed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_RX_WRITE_SNAP completed.
A ** RABAX: level LEV_RX_SET_ALERT entered.
A ** RABAX: level LEV_RX_SET_ALERT completed.
A ** RABAX: level LEV_RX_COMMIT entered.
A ** RABAX: level LEV_RX_COMMIT completed.
A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A ** RABAX: level LEV_RX_RESET_PROGS entered.
A ** RABAX: level LEV_RX_RESET_PROGS completed.
A ** RABAX: level LEV_RX_STDERR entered.
A Mon Apr 21 15:16:11 2008
A
A ABAP Program ????????????????????????????????????????.
A Source Line 0.
A Error Code DBIF_RTAB_ILLEGAL_CALL.
A Module $Id: //bas/700_REL/src/krn/runt/ablocale.c#3 $ SAP.
A Function SetTextEnv Line 507.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
B
B Mon Apr 21 15:16:21 2008
B ***LOG BZA=> table TCP0C does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
A ** RABAX: level LEV_RX_C_STACK completed.
A ** RABAX: level LEV_RX_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_INTERFACES entered.
A ** RABAX: level LEV_RX_INTERFACES completed.
A ** RABAX: level LEV_RX_GET_MESS entered.
A ** RABAX: level LEV_RX_GET_MESS completed.
A ** RABAX: level LEV_RX_INIT_SNAP entered.
A ** RABAX: level LEV_RX_INIT_SNAP completed.
A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_SN_C_STACK failed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_RX_WRITE_SNAP completed.
A ** RABAX: level LEV_RX_SET_ALERT entered.
A ** RABAX: level LEV_RX_SET_ALERT completed.
A ** RABAX: level LEV_RX_COMMIT entered.
A ** RABAX: level LEV_RX_COMMIT completed.
A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A ** RABAX: level LEV_RX_RESET_PROGS entered.
A ** RABAX: level LEV_RX_RESET_PROGS completed.
A ** RABAX: level LEV_RX_STDERR entered.
A Mon Apr 21 15:16:21 2008
A
A ABAP Program ????????????????????????????????????????.
A Source Line 0.
A Error Code DBIF_RTAB_ILLEGAL_CALL.
A Module $Id: //bas/700_REL/src/krn/runt/ablocale.c#3 $ SAP.
A Function SetTextEnv Line 507.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
A ** RABAX: end no http/smtp
A ** RABAX: end RX_BTCHLOG|RX_VBLOG
A Error DBIF_RTAB_ILLEGAL_CALL occured. P1=[RTAB/RD /TCP0C ] P2=TCP0C .
A
B
B Mon Apr 21 15:17:11 2008
B ***LOG BZA=> table TCP0C does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
A ** RABAX: level LEV_RX_C_STACK completed.
A ** RABAX: level LEV_RX_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_INTERFACES entered.
A ** RABAX: level LEV_RX_INTERFACES completed.
A ** RABAX: level LEV_RX_GET_MESS entered.
A ** RABAX: level LEV_RX_GET_MESS completed.
A ** RABAX: level LEV_RX_INIT_SNAP entered.
A ** RABAX: level LEV_RX_INIT_SNAP completed.
A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_SN_C_STACK failed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_RX_WRITE_SNAP completed.
A ** RABAX: level LEV_RX_SET_ALERT entered.
A ** RABAX: level LEV_RX_SET_ALERT completed.
A ** RABAX: level LEV_RX_COMMIT entered.
A ** RABAX: level LEV_RX_COMMIT completed.
A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A ** RABAX: level LEV_RX_RESET_PROGS entered.
A ** RABAX: level LEV_RX_RESET_PROGS completed.
A ** RABAX: level LEV_RX_STDERR entered.
A Mon Apr 21 15:17:11 2008
A
A ABAP Program ????????????????????????????????????????.
A Source Line 0.
A Error Code DBIF_RTAB_ILLEGAL_CALL.
A Module $Id: //bas/700_REL/src/krn/runt/ablocale.c#3 $ SAP.
A Function SetTextEnv Line 507.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
B
B Mon Apr 21 15:17:21 2008
B ***LOG BZY=> unexpected return code 103 calling SEL [dbsynseq#1 @ 527] [dbsynseq0527 ]
B ***LOG BZY=> unexpected return code 2 calling sync_read [dbsync#4 @ 2176] [dbsync 2176 ]
B *** ERROR => collect_new : unexpected returncode 512
[dbsync.c 1222]
B ***LOG BZY=> unexpected return code 103 calling DbSlBegRea [dbsynseq#1 @ 426] [dbsynseq0426 ]
M *** ERROR => ThExeDdlog: db_clean_ddlog [thxxtool.c 1981]
B ***LOG BZA=> table TCP0C does not exist on database [dbtrtab#6 @ 3887] [dbtrtab 3887 ]
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
A ** RABAX: level LEV_RX_C_STACK completed.
A ** RABAX: level LEV_RX_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_INTERFACES entered.
A ** RABAX: level LEV_RX_INTERFACES completed.
A ** RABAX: level LEV_RX_GET_MESS entered.
A ** RABAX: level LEV_RX_GET_MESS completed.
A ** RABAX: level LEV_RX_INIT_SNAP entered.
A ** RABAX: level LEV_RX_INIT_SNAP completed.
A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_SN_C_STACK failed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_RX_WRITE_SNAP completed.
A ** RABAX: level LEV_RX_SET_ALERT entered.
A ** RABAX: level LEV_RX_SET_ALERT completed.
A ** RABAX: level LEV_RX_COMMIT entered.
A ** RABAX: level LEV_RX_COMMIT completed.
A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A ** RABAX: level LEV_RX_RESET_PROGS entered.
A ** RABAX: level LEV_RX_RESET_PROGS completed.
A ** RABAX: level LEV_RX_STDERR entered.
A Mon Apr 21 15:17:21 2008
A
A ABAP Program ????????????????????????????????????????.
A Source Line 0.
A Error Code DBIF_RTAB_ILLEGAL_CALL.
A Module $Id: //bas/700_REL/src/krn/runt/ablocale.c#3 $ SAP.
A Function SetTextEnv Line 507.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed. -
Monitor Systems From Solution Manager 4.0
Hi Dear Gurus,
I have recently Instaled SOLMAN 4.0 on windows with Mysql. I have configured the Maintainence optimizer and now its working fiine.
From my organization requirement they want to monitor ERP and BW systems from solution manager.
Can any one please tell me how to start regarding this.
And one more question is i am just wondering Central User Admin is different installation or we have to configure SOLMAN 4.0 to use CUA.
Many thanks for your time.
Kind Regards,
Vamsi.Hi,
You first need to Setup landscape and create RFCs
[Data Collection|https://websmp109.sap-ag.de/~sapidb/011000358700004860052004E.sim]
[Create Systems|https://websmp109.sap-ag.de/~sapidb/011000358700000894082006E.sim]
[Create RFCs|https://websmp109.sap-ag.de/~sapidb/011000358700002912202006E.sim]
[Assign Logical Components|https://websmp109.sap-ag.de/~sapidb/011000358700002912242006E.sim]
Then Create Solution,
Then Setup Solution Monitoring
[Setup|https://websmp109.sap-ag.de/~sapidb/011000358700006936062005E.sim]
[Monitoring Graphic|https://websmp109.sap-ag.de/~sapidb/011000358700006939872005E.sim]
[Exhaustive very good tutor|https://websmp109.sap-ag.de/~sapidb/011000358700005479192006E.sim]
This will solve your problem.
Feel free to revert back.
--Ragu
Edited by: Raguraman C on Jan 16, 2008 4:31 AM -
How to take Solution Manager Roles in ECC 6.0?
If I want some PFCG Roles from Solution Manager to ECC 6.0 then what is the easiest way should I used CUA (and select Solution Manager) as a system or what? I will be very thankful who ever will show me the right way. thanks in Advance
Hi
You can do the same in 2 Ways.
1) Make a list of all roles which are required and create TR for these and move it to ECC System.
2) Form PFCG ,download all the roles in bulk and upload the same in ECC System
Thanks & Regards,
Sandeep Alapati -
Setup and Configuration for a Solution Manager instance
I am setting up a Solution Manager instance for a client in Australia.
Currently there is no reference client that I am aware of in Australia for Solution Manager. So this is extremely important to get it right. Also I am an independent contractor, so I am unable to call on any in-house experts from a consulting firm for help.
So I am looking for answers from some experts who have done this before.
Had some training on Solution Manager back in 2002.
Our client wants to setup the solution manager instance to monitor 9 SAP instances
- 3 R/3, DEV, Q/A, PROD
- 3 BI, DEV, Q/A, PROD
- 3 Enterprise Portal, DEV, Q/A, PROD
Solution Manager is running in a separate instance for all those listed above.
In addition to the above the client would also like to user the service desk function of Solution Manager for in-house support of SAP, and push to service desk request onto their support partner and/or SAP directly.
Question:
1) Is it better to use the Solution Manager client 001 or create a separate client for the customer?
2) How would you as the expert configure the service desk component to push service desk requests to the support partner (a 3rd party Service Desk Tool or another Solution Manager instance), and allow the customer to choose to send the request direct to SAP?
3) The client would also like to use the Solution Manager Instance as the CUA environment, is this advisable?
Kind Regards
David CooperHello David,
Please find th answers below:
1. You should use a separate client for solution manager rather than using a standard one
2. You should configure your solution manager as the service desk for all type of support requests.Solution manager can send your requests to SAP and vice-vera.Why do you a third part tool and waste money of the client.Solution manager can do all for you very effectively
3.sure you should configure solution manager as CUA environment,there are no issues with that
Let me know of any questions
Rohit -
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. -
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. -
Implementing the Enterprise Support in Solution Manager
Hi Experts,
Can anybody tell me what are the pre requisites to implement Enterprise support in solution manager?
Also let me know what are steps involved in implementing the enterprise support.
Thanks in Advance
HariHello Hari,
In order to implement Enterprise Support your organization should registered as a Value Added Reseller(VAR) with SAP. You can get all the required documentation under https://websmp104.sap-ag.de/solutionmanager --> Information for VARs, ASPs and AHPs which is in the left hand side of the page. However, you need to have a S-user ID of the VAR.
The following are the steps need to perform in implementing the Enterprise Support firmly known as Service Desk for VARs.
1. SAP Solution Manager basic settings (IMG)
a) Initial Configuration Part I
b) Maintain Profile Parameters
c) Maintain Logical Systems
d) Maintain SAP Customer Numbers
e) Initial Configuration Part II
1) Activate BC Set
a) Activate Service Desk BC Set
b) Activate Issue Monitoring BC set
c) Set-up Maintainance optimizer
d) Change online Documentation Settings
e) Activate Solution Manager Services
f) Activate integration with change request Managemnt
g) Define service desk connection in Solution Manager
2)Get components for SAP Service Market place
a) Get SAP Components
3) Get Service Desk Screen Profile
a)generate Business Partener Screen
4)Copy By price list
a)activate Service Desk BC Set
b)Activate Issue Monitoring BC set
c)Set-up Maintainance optimizer
f) Business Add-In for RFC Connections with several SAP customers
g) Business Add-In for RFC Connection of Several SAP Cust. no.
h) Set-Up SAP Support Connection for Customers
i) Assign S-user for SAP Support Portal functionality
j) Schedule Background Jobs
k) Set-Up System Landscape
l) Create Key Users
m) Create Message Processor
2. Multiple SAP Customer Numbers
a) Business Add-In for RFC Connections with several SAP customer numbers
b) Set-Up SAP Support Connection for Customers
3. Data transfer from SAP
a) Data Transfer from SAP
4. Create u201COrganizationu201D Business Partner
5. Service Provider function (IMG)
a) Business Add-In for RFC Connections with several SAP customer numbers
b) Business Add-In for Text Authorization Check
c) Activate BC Set for Service Provider
d) Activate Text Types
e) Adjust Service Desk Roles for Service Provider Menu
6. Service Provider: Value-Added Reseller (VAR)
a) Business Add-In to Process Actions (Post-Processing Framework)
b) Activate BC Sets for Configuration
c) Create Hierarchy and Product Category
d) Set-Up Subcategories
e) Create Business Partner as Person Automatically
f) Set-Up Automatic Confirmation of Messages
g) Maintain Business Partner Call Times
h) Set-Up Incident Management Work Center
7. Work Center (Web UI)
a) Activate Solution Manager Services
b) Assign Work Center Roles to Users
Hope it helps.
Regards,
Satish. -
Install Solution Manager in RedHat Enterprise 6 with Oracle 11
Hello ,
In the marketplace-PAM, RedHat Enterprise 6 is not listed as approved for EHP1 Solution Manager 7.0 64 bit (unicode) with Oracle.
Does anyone have any information on this subject?
Has anyone installed the Solution Manager 7.0/Oracle with RedHat Enterprise 6?
tksYes, you are correct. Apart from PAM, following Note confirms this. RHEL 6 is not supported yet for Oracle, is in planning stage.
Note 1565179 - SAP software and Oracle Linux
Thanks
Maybe you are looking for
-
Apple Mini DisplayPort to VGA Adapter flickers
I have 2 Samsung SyncMaster 23 in, HD Displays connected to my Mac Mini. The Display connected via the Mini DP to VGA adapter flickers erratically. This started happening after installing the latest upgrade of OSX Mountain Lion. I called Apple suppor
-
HT201272 How do I redownload a purchased song to my iTunes on my computer
I recently purchased Mya Fallen EP. There are four (4) tracks on this EP. The last track plays about 2:29 then it just stops. The track is 4:05. How do I redownload the track? Or is their something wrong with file on your end?
-
BGM: Master Warranty sort field
Hi all, I have search all over the place in order to know the function of the "Sort Field" in the Master Warranty. If I do have several counters, it stated that I can set priorities of my warranty counters by using free defined sort field. But how do
-
Problems with assembly update in Biztalk production server
Hi. I'm facing a problem I cannot solve about an update in one of the resources of an application in Biztalk production server. Suddenly a bug in an application that receives messages through an external web service appeared. To find out where the bu
-
How do I fix this issue? some time it works and the other times I get the cross hair