SAPOSCOL Issue

Dears,
We are using SAP R/3 4.7 on Unix with Oracle 9i.Issue is that in ST06 when I click on OS log in details analysis ->Previous 24 hours i get an error message :
"Can not get OS log information for msldbci_PRD_00".
"Problem on remote host,Please check your SAPOSCOL and your CCMS agent".
In SAPOSCOL log file:
It shows error:
"Can not identify system, assume Series 800"
"Can not open /usr/sap/tmp/dev_proc fopen() failed.
Please suggest how to resolve the issue.
Deepak

Hi,
I checked that SAPOSCOL is running fine and its status shows:
Mon Aug 18 09:50:44 2008  interval  10   sec.
HP-UX MSLCIDB B.11.23 U ia64 0012175506
Collector Version:  COLL 20.85 04/03/01 620 - hpxOscol 07/2003
Date/time  18.08.2008 10:12:25       Start of Collector Mon Aug 18 09:44:43 2008#
Status report
Collector Versions
running                              COLL 20.85 04/03/01 620 - hpxOscol 07/2003
dialog                                COLL 20.85 04/03/01 620 - hpxOscol 07/2003
Shared Memory                   attached
Number of records                 3798
Active Flag                           active (01)
Operating System                HP-UX MSLCIDB B.11.23 U ia64 0012175506
Collector PID                       12429 (0000308D)
Collector                             running
Start time coll.                     Mon Aug 18 09:52:42 2008
Current Time                        Mon Aug 18 10:12:25 2008
Last write 12429 (0000308D)
Collector                              running
Start time coll.                      Mon Aug 18 09:52:42 2008
Current Time                         Mon Aug 18 10:12:25 2008
Last write access                  Mon Aug 18 10:12:16 2008
Last Read  Access                Mon Aug 18 10:08:32 2008
Collection Interval                   10 sec (next delay).
Collection Interval                   10 sec (last ).
Status                      
Collect Details  ?                   required
Refresh                                 required
Header extention structure
number of x-header      records        1
records        60
number of free com.     records        60
resulting offset to 1.data rec.        61
Trace level                             2
Collector in IDLE - mode ?              NO
become idle after 300 sec without read access.
without read access.
length of idle interval               60 sec
length of norm.interval            10 sec
Deepak

Similar Messages

  • SAPOSCOL not reporting CPU and paging values

    Hi there,
    I am trying to test Wily introscope using the EP Agent plug-in for SAPOSCOL with XI 3.0 SP21 running under Windows XP. It appears that for whatever reason no values are captured by SAPOSCOL for CPU utilisation and memory usage (e.g. Pages in / sec, pages out / sec). However Swap information is captured and reported correctly. I have verified this using SAPOSCOL -d (with dump cpu and dump memory). I have also tested this using PI 7.0 under Windows XP where it works fine. All values are reported correctly.
    Is there any OS dependency (e.g. missing dlls) or a Windows service not activated that may cause this problem. I also tried using the SAPOSCOL of the PI 7.0 system which didn't make a difference. Therefore I believe it is an environment specific issue rather than a SAPOSCOL issue.
    Any help is appreciated.
    Dieter Bauer

    Hello Dieter,
    fine to hear the problem is solved!
    One additional hint for all people who face the same problem but don't have the time or don't feel like downloading the resource kit: simply check the registry as described in <a href="http://service.sap.com/sap/support/notes/688131">note 688131</a>: Windows: missing data in ST06/OS06.
    Regards, Michael

  • ST06 show negative Physical mem free

    Dear Guru,
    When I look into ST06 - Operating System Monitor, table Memory, it shows that Physical mem free is negative, "1-".
    Here's the screenshot:
    Could anyone please advice, how to fix this one via RZ10 - Edit Profiles; which parameters should I look up to?
    And how big should I put in?
    Our server specification:
    OS/database: AS/400 with DB2
    CPU: 2 cores
    Memory: 32 GB
    Thank you.
    Best Regards,
    Ady Purnama

    Hi,
    Are the sapservices running especially oscol process.
    May be the sap note and below links might help
    SAP Note : - 189072 - ST06/OS06: No data or incorrect data displayed
    link - http://wiki.scn.sap.com/wiki/display/NWTech/How+to+analyse+the+missing+performace+data+situation+and+how+to+check+SAPOsCol+issues
    Regards,
    Nikhil

  • SAPOSCOL not running in MS Cluster

    Hi, gurus:
    We have a problem with SAPOSCOL in a SAP ECC 6.0 system (SAP ECC 6.0 + NetWeaver 7.00 + Oracle 10.2 + Windows Server 2003 R2 Enterprise x64 Edition) running over a MS cluster:
    Transactions OS06/ST06 shows no data, and they show an info message wich states: SAPOSCOL not running ? (shared memory not available ). When we checked this issue, we noticed that, in fact, there is no sapcoscol.exe task running in any node.
    But when we try to start the service (both using microsoft services console and cmd commands) although we can see the process running in the node which owns all the resources, SAP seems not notice that. The information system shows in ST06>Operating System Collector>Status is the following:
    iinterval             0             sec.
    Collector Version:
    Date/time             05.09.2008 16:55:01
    Start of Collector
    Status report
    Collector Versions                         
      running                                   COLL 20.95     700     - 20.64     NT 07/10/17
      dialog                                   COLL 20.95     700     - 20.65     NT 08/02/06
    Shared Memory                              attached
    Number of records                         575
    Active Flag                              active     (01)
    Operating System                         Windows NT     5.2.3790 SP     2 BL-SAP2 4x AMD64 Level 1
    Collector PID                              0 (00000000)
    Collector                                   not running (process ID not found).
    Start time coll.                              Thu Jan 01     01:00:00 1970
    Current     Time                              Fri Sep 05     16:55:01 2008
    Last write access                         Mon Sep 01     11:28:23 2008
    Last Read  Access                         Fri Sep 05     15:54:00 2008
    Collection Interval                         10     sec     (next delay).
    Collection Interval                         10     sec     (last ).
    Status                                   read
    Collect     Details                         required
    Refresh                                   required
    Header Extention Structure                    
    Number of x-header          Records          1
    Number of Communication     Records          60
    Number of free Com.          Records          60
    Resulting offset to     1.data rec.               61
    Trace level                                   3
    Collector in IDLE -     mode ?               NO
      become idle after     300     sec     without     read access.|
      Length of     Idle Interval                    60     sec
      Length of     norm.Interval                    10     sec
    But saposcol.exe is running with a certain PID in the same note than SAP and Oracle under user sapservice<sid>
    We have tried to run saposcol in several ways (as, I have noted before: from microsoft service console, from cmd line using "net start saposcol", using the saposcol under C:\WINDOWS\SapCluster and the one under
    F:\usr\sap\PRD\sys\exe\run, fom the two nodes, accessing the cluster through several IPs...) and tried the commands saposcol -c and saposcol -k but we cannot get the saposcoll run. Moreover, we haven't found any log information. The only log we (and SAP) could find is the one located in C:\WINDOWS\SapCluster\dev_coll.
    This log remain frozen at September 1st:
          SAPOSCOL version  COLL 20.95 700 - 20.64 NT 07/10/17, 64 bit, multithreaded, Non-Unicode
          compiled at   Feb  3 2008
          systemid      562 (PC with Windows NT)
          relno         7000
          patch text    COLL 20.95 700 - 20.64 NT 07/10/17
          patchno       146
          intno         20050900
          running on    BL-SAP2 Windows NT 5.2 3790 Service Pack 2 4x AMD64 Level 15 (Mod 65 Step 3)
    12:04:16 01.09.2008   LOG: Profile          : no profile used
    12:04:16 01.09.2008   LOG: Saposcol Version  : [COLL 20.95 700 - 20.64 NT 07/10/17]
    12:04:16 01.09.2008   LOG: Working directory : C:\WINDOWS\SAPCLU~1
    12:04:16 01.09.2008   LOG: Allocate Counter Buffer [10000 Bytes]
    12:04:16 01.09.2008   LOG: Allocate Instance Buffer [10000 Bytes]
    12:04:17 01.09.2008   LOG: Shared Memory Size: 71898.
    12:04:17 01.09.2008   LOG: Connected to existing shared memory.
    12:04:17 01.09.2008   LOG: MaxRecords = 575 <> RecordCnt + Dta_offset = 614 + 61
    12:04:22 01.09.2008 WARNING: WaitFree: could not set new shared memory status after 5 sec
    12:04:22 01.09.2008 WARNING: Cannot create Shared Memory
    Kernel Info:
    Kernel release    700
    Compilation        NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00
    Sup.Pkg lvl.       146
    ABAP Load       1563
    CUA load           30
    Mode                opt
    Can anyone shed some light on the subject?
    Thank you very much and kind regards
    Edited by: Jose Enrique Sepulveda on Sep 6, 2008 2:10 AM

    Dear bhaskar:
    Thanks for your reply. We have considered balancing the system to the other node or reboot the system to free resources, in order to re-create the shared memory, but in the past, the balancing process (move resources from one node to the other) has caused problems. Since this is a critical system, stopping (or balancing) is not an option right now, and updating the kernel requires an ABAP stack reboot plus the kernel change : any changes in system configuration requires a longer approval/planning process than a reboot.
    Moreover, the OS collecting system and its display in OS06/ST06 has worked fine until now.
    Does anyone knows if a reboot has solved this kind of problem in a similar situation?
    Thanks in advance
    José Enrique

  • SAP Netweaver 7.0 installation - serious issue (startsap db n4sadm)

    Hi,
    We are trying to setup SAP Netweaver 7.0 (Test Drive x-86 edition) on Fedora 12. We have successfully ran the "install.sh" file. The DB2 instance gets installed and we are able to start it as 'db2n4s' user using the 'db2start' command (we could as well stop using db2stop).
    But, we are facing issues when we start the db2 instance as prescribed by the SAP Netweaver installation guide for the following command.
    n4shost:n4sadm 52> startsap db n4shost
    Checking db6 db Database
    ABAP Database is not available via R3trans
    Starting SAP-Collector Daemon
    expand: write error: Broken pipe
    expand: write error
    * This is Saposcol Version COLL 20.94 700 - v2.00, Intel x86 with Linux, 2007/02/16
    * Usage:  saposcol -l: Start OS Collector
    *         saposcol -k: Stop  OS Collector
    *         saposcol -d: OS Collector Dialog Mode
    *         saposcol -s: OS Collector Status
    * Starting collector (create new process)
    saposcol on host pwc01 started
    Running /usr/sap/N4S/SYS/exe/run/startdb
    SQL1042C  An unexpected system error occurred.  SQLSTATE=58004
    Activate database failed
    R3trans connect failed
    DB startup failed
    Details of our DB2 instance
    [db2n4s@]$ ./db2licm -l
    Product name:                     "DB2 Enterprise Server Edition"
    License type:                     "CPU"
    Expiry date:                      "Permanent"
    Product identifier:               "db2ese"
    Version information:              "9.1"
    Annotation:                       "-3;(_c)"
    Features:
    DB2 Database Partitioning:        "Licensed"
    DB2 Performance Optimization ESE: "Not licensed"
    DB2 Storage Optimization:         "Licensed"
    DB2 Advanced Access Control:      "Not licensed"
    DB2 Geodetic Data Management:     "Not licensed"
    Homogeneous Federation for DB2:   "Licensed"
    DB2 Pure XML ESE:                 "Not licensed"
    Thanks,
    Sriram

    Thanks for your quick reply.
    I actually went ahead one step in the problem. Now i am getting the following message when i try to start the sap.
    n4shost:n4sadm 55> startsap db n4shost
    Warning: Could not found virtuell host in ifconfig list
    Checking db6 db Database
    ABAP Database is not available via R3trans
    Starting SAP-Collector Daemon
    expand: write error: Broken pipe
    expand: write error
    * This is Saposcol Version COLL 20.94 700 - v2.00, Intel x86 with Linux, 2007/02/16
    * Usage:  saposcol -l: Start OS Collector
    *         saposcol -k: Stop  OS Collector
    *         saposcol -d: OS Collector Dialog Mode
    *         saposcol -s: OS Collector Status
    * Starting collector (create new process)
    saposcol on host pwc01 started
    Running /usr/sap/N4S/SYS/exe/run/startdb
    11/10/2010 14:17:12     0   0   SQL1063N  DB2START processing was successful.
    SQL1063N  DB2START processing was successful.
    Database activated
    R3trans connect failed
    DB startup failed
    Also i did the R3trans -d and have attached the log.
    4 ETW000 R3trans version 6.14 (release 700 - 11.04.07 - 14:28:00).
    4 ETW000 unicode enabled version
    4 ETW000 ===============================================
    4 ETW000
    4 ETW000 date&time   : 10.11.2010 - 14:19:38
    4 ETW000 control file: <no ctrlfile>
    4 ETW000 R3trans was called as follows: R3trans -d
    4 ETW000  trace at level 2 opened for a given file pointer
    4 ETW000  [dev trc     ,00000]  Wed Nov 10 14:19:38 2010                              83  0.000083
    4 ETW000  [dev trc     ,00000]  db_con_init called                                    21  0.000104
    4 ETW000  [dev trc     ,00000]  create_con (con_name=R/3)                             29  0.000133
    4 ETW000  [dev trc     ,00000]  Loading DB library '/usr/sap/N4S/SYS/exe/run/dbdb6slib.so' ...
    4 ETW000                                                                              35  0.000168
    4 ETW000  [dev trc     ,00000]  load shared library (/usr/sap/N4S/SYS/exe/run/dbdb6slib.so), hdl 0
    4 ETW000                                                                             191  0.000359
    4 ETW000  [dev trc     ,00000]  Library '/usr/sap/N4S/SYS/exe/run/dbdb6slib.so' loaded
    4 ETW000                                                                              21  0.000380
    4 ETW000  [dev trc     ,00000]  function DbSlExpFuns loaded from library /usr/sap/N4S/SYS/exe/run/dbdb6slib.so
    4 ETW000                                                                              27  0.000407
    4 ETW000  [dev trc     ,00000]  Version of '/usr/sap/N4S/SYS/exe/run/dbdb6slib.so' is "700.08", patchlevel (0.107)
    4 ETW000                                                                              85  0.000492
    4 ETW000  [dev trc     ,00000]  function dsql_db_init loaded from library /usr/sap/N4S/SYS/exe/run/dbdb6slib.so
    4 ETW000                                                                              24  0.000516
    4 ETW000  [dev trc     ,00000]  function dbdd_exp_funs loaded from library /usr/sap/N4S/SYS/exe/run/dbdb6slib.so
    4 ETW000                                                                              27  0.000543
    4 ETW000  [dev trc     ,00000]  New connection 0 created                              18  0.000561
    4 ETW000  [dev trc     ,00000]  0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
    4 ETW000                                                                              27  0.000588
    4 ETW000  [dev trc     ,00000]  db_con_connect (con_name=R/3)                         20  0.000608
    4 ETW000  [dev trc     ,00000]  find_con_by_name found the following connection for reuse:
    4 ETW000                                                                              21  0.000629
    4 ETW000  [dev trc     ,00000]  0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
    4 ETW000                                                                              25  0.000654
    4 ETW000  [dev trc     ,00000]  DB2 library successfully loaded DB2 library '/db2/db2n4s/sqllib/lib32/libdb2.so' successfully loaded
    4 ETW000                                                                            7545  0.008199
    4 ETW000  [dev trc     ,00000]  RLIMIT_STACK: current=10485760, max=0                 40  0.008239
    4 ETW000  [dev trc     ,00000]  DB6 (DB2 UDB) UNICODE database interface 700.08 [opt]
    4 ETW000                                                                              23  0.008262
    4 ETW000  [dev trc     ,00000]  DB6 shared library (dbdb6slib) patchlevels            15  0.008277
    4 ETW000  [dev trc     ,00000]    (0.8) DB6: V8.2.2 optguidelines in OPEN SQL (note 150037)
    4 ETW000                                                                              22  0.008299
    4 ETW000  [dev trc     ,00000]    (0.8) Support of SDBUPDEXCL (note 847616)           14  0.008313
    4 ETW000  [dev trc     ,00000]    (0.9) DB6: use export file for dbdb6slib (note 835135)
    4 ETW000                                                                              21  0.008334
    4 ETW000  [dev trc     ,00000]    (0.9) DB6: Core in getAndBindSQLDA (note 833183)
    4 ETW000                                                                              30  0.008364
    4 ETW000  [dev trc     ,00000]    (0.10) DB6: link dbdb6slib.dll on windows with libdb6.obj (note 761159)
    4 ETW000                                                                              22  0.008386
    4 ETW000  [dev trc     ,00000]    (0.10) DB6: DUPLICATE_KEY on MERGE -> repeat (note 851474)
    4 ETW000                                                                              21  0.008407
    4 ETW000  [dev trc     ,00000]    (0.15) DB6: wrong CAST for short string ABAP type (note 861905)
    4 ETW000                                                                              22  0.008429
    4 ETW000  [dev trc     ,00000]    (0.17) DB6: special characters in sidadm passwd (note 865839)
    4 ETW000                                                                              21  0.008450
    4 ETW000  [dev trc     ,00000]    (0.21) DB6: no SAP_INFO comments (note 873889)
    4 ETW000                                                                              22  0.008472
    4 ETW000  [dev trc     ,00000]    (0.22) DB6: hints: get correlation names from view texts (note 868888)
    4 ETW000                                                                              20  0.008492
    4 ETW000  [dev trc     ,00000]    (0.23) DB6: hints: get correlation names from view texts (note 868888)
    4 ETW000                                                                              22  0.008514
    4 ETW000  [dev trc     ,00000]    (0.26) DB6: DB6_DBSL_CLP_COMMAND STRING_BAD_REF (note 883402)
    4 ETW000                                                                              22  0.008536
    4 ETW000  [dev trc     ,00000]    (0.27) DB6: activate value compression (note 886231)
    4 ETW000                                                                              20  0.008556
    4 ETW000  [dev trc     ,00000]    (0.28) DB6: optimization guidelines on views part 2 (note 868888)
    4 ETW000                                                                              22  0.008578
    4 ETW000  [dev trc     ,00000]    (0.30) DB6: no SQL trace for SQLCancel (note 892111)
    4 ETW000                                                                              21  0.008599
    4 ETW000  [dev trc     ,00000]    (0.33) DB6: append SAP_TA comment (note 873889)
    4 ETW000                                                                              22  0.008621
    4 ETW000  [dev trc     ,00000]    (0.34) DB6: activate value compression with quoted names (note 886231)
    4 ETW000                                                                              21  0.008642
    4 ETW000  [dev trc     ,00000]    (0.36) DB6: Repeat isolated DDL statements after SQL0911 (note 901338)
    4 ETW000                                                                              22  0.008664
    4 ETW000  [dev trc     ,00000]    (0.41) DB6: add V9 to list of supported DB2 releases (note 912386)
    4 ETW000                                                                              23  0.008687
    4 ETW000  [dev trc     ,00000]    (0.50) DB6: reread passwords for secondary connections (note 931742)
    4 ETW000                                                                              22  0.008709
    4 ETW000  [dev trc     ,00000]    (0.52) DB6: double quote table names in optguidelines (note 868888)
    4 ETW000                                                                              33  0.008742
    4 ETW000  [dev trc     ,00000]    (0.54) DB6: error handling in DBSL CLP (note 940260)
    4 ETW000                                                                              22  0.008764
    4 ETW000  [dev trc     ,00000]    (0.69) DB6: technical support of DB2 CLI driver (note 962892)
    4 ETW000                                                                              23  0.008787
    4 ETW000  [dev trc     ,00000]    (0.73) DB6: log table name on TRUNCATE failure (note 970743)
    4 ETW000                                                                              22  0.008809
    4 ETW000  [dev trc     ,00000]    (0.79) DB6: column type XML in index size calculation (note 982993)
    4 ETW000                                                                              27  0.008836
    4 ETW000  [dev trc     ,00000]    (0.82) DB6: CAST for SSTRING data types (note 989568)
    4 ETW000                                                                              21  0.008857
    4 ETW000  [dev trc     ,00000]    (0.86) DB6: long runtimes for R3szchk (note 1000847)
    4 ETW000                                                                              22  0.008879
    4 ETW000  [dev trc     ,00000]    (0.88) DB6: patch collection Dec 06 (note 1005574)
    4 ETW000                                                                              22  0.008901
    4 ETW000  [dev trc     ,00000]    (0.96) DB6: patch collection Jan 07 (note 1017852)
    4 ETW000                                                                              22  0.008923
    4 ETW000  [dev trc     ,00000]    (0.97) DB6: CLP commands with DB2 CLI Driver (note 1024102)
    4 ETW000                                                                              21  0.008944
    4 ETW000  [dev trc     ,00000]    (0.99) DB6: SUBSTITUTE VALUES with FAE statements (note 1028779)
    4 ETW000                                                                              21  0.008965
    4 ETW000  [dev trc     ,00000]    (0.107) DB6: patch collection Apr 07 (note 1047194)
    4 ETW000                                                                              31  0.008996
    4 ETW000  [dev trc     ,00000]  Supported features:                                   16  0.009012
    4 ETW000  [dev trc     ,00000]  ..retrieving configuration parameters                 19  0.009031
    4 ETW000  [dev trc     ,00000]  ..done                                                70  0.009101
    4 ETW000  [dev trc     ,00000]  Running with UTF-8 Unicode                            15  0.009116
    4 ETW000  [dev trc     ,00000]  *** ERROR in DB6Connect[dbdb6.c, 1634] CON = 0 (BEGIN)
    4 ETW000                                                                           31472  0.040588
    4 ETW000  [dev trc     ,00000]  &+     DbSlConnectDB6( SQLConnect ): [IBM][CLI Driver] SQL30082N  Security processing failed with reason "15" ("PROCESSIN
    4 ETW000                                                                              25  0.040613
    4 ETW000  [dev trc     ,00000]  &+     G FAILURE").  SQLSTATE=08001                                                                               
    4 ETW000                                                                              23  0.040636
    4 ETW000  [dev trc     ,00000]  &+                                                                               
    4 ETW000                                                                              25  0.040661
    4 ETW000  [dev trc     ,00000]  &+                                                                               
    4 ETW000                                                                              24  0.040685
    4 ETW000  [dev trc     ,00000]  &+                                                                               
    4 ETW000                                                                              22  0.040707
    4 ETW000  [dev trc     ,00000]  *** ERROR in DB6Connect[dbdb6.c, 1634] (END)          26  0.040733
    4 ETW000  [dbdb6.c     ,00000]  *** ERROR => DbSlConnect to 'N4S' as 'sapn4s' failed
    4 ETW000                                                                              60  0.040793
    2EETW169 no connect possible: "DBMS = DB6                              --- DB2DBDFT = 'N4S'"
    Thanks,
    Sriram

  • Saposcol, Solaris 10 and zones

    We are running a bunch of instances on Solaris 10 x86_64 in zones. Everything works great (including ZFS) but one issue is there:
    saposcol always "sees" the full machine, means e. g. CPU usage is displayed not on a per-zone basis but only once for all zones.
    Are there any plans on extending saposcol to support zone-specific data (such as IBM has recently done with AIX-micropartitioning and/or LPARS)? It would greatly improve resource management on those systems.
    Markus

    Yup i do see em at unix lvl.
    Filesystem             size   used  avail capacity  Mounted on
    /                       20G   6.8G    13G    35%    /
    /archivos              1.9G   2.0M   1.9G     1%    /archivos
    /dev                    20G   6.8G    13G    35%    /dev
    /dvds                   39G   6.6G    32G    17%    /dvds
    /sapdb/PRD/db          962M   167M   737M    19%    /sapdb/PRD/db
    /sapdb/PRD/logbackups
                           4.9G   5.0M   4.9G     1%    /sapdb/PRD/logbackups
    /sapdb/data            1.9G    62M   1.8G     4%    /sapdb/data
    /sapdb/programs        962M   208M   696M    24%    /sapdb/programs
    /sapmnt/PRD            1.9G   686M   1.2G    36%    /sapmnt/PRD
    /usr/sap/PRD           7.9G   754M   7.1G    10%    /usr/sap/PRD
    /usr/sap/trans         1.9G   414M   1.5G    22%    /usr/sap/trans
    proc                     0K     0K     0K     0%    /proc
    ctfs                     0K     0K     0K     0%    /system/contract
    swap                    31G   296K    31G     1%    /etc/svc/volatile
    mnttab                   0K     0K     0K     0%    /etc/mnttab
    /platform/sun4u-us3/lib/libc_psr/libc_psr_hwcap2.so.1
                            20G   6.8G    13G    35%    /platform/sun4u-us3/lib/libc_psr.so.1
    /platform/sun4u-us3/lib/sparcv9/libc_psr/libc_psr_hwcap2.so.1
                            20G   6.8G    13G    35%    /platform/sun4u-us3/lib/sparcv9/libc_psr.so.1
    fd                       0K     0K     0K     0%    /dev/fd
    swap                    31G     0K    31G     0%    /tmp
    swap                    31G    56K    31G     1%    /var/run
    and saposcol is running with root user.
    Message was edited by:
            Daniel Esteban Rajmanovich

  • SAPOSCOL File system monitor does not show all drives (OS06 / ST06 / OS07)

    Hi everyone,
    Iu2019m facing an issue with certain drives not being monitored in saposcol / CCMS Filesystem monitor after ECC6 upgrade.
    I can only see 3 drives.
    The following errors are showing up in saposcol log.
    01:05:15 26.01.2010   LOG: Allocate Instance Buffer [10000 Bytes]
    01:05:47 26.01.2010   LOG: Shared Memory Size: 69672.
    01:05:47 26.01.2010   LOG: Shared Memory was created by process:2836
    01:05:50 26.01.2010   LOG: Collector daemon started
    01:05:50 26.01.2010   LOG: read coll.put Tue Jan 26 00:59:12 2010
    01:05:50 26.01.2010   LOG: Collector PID: 2836
    01:06:00 26.01.2010   LOG: Process Monitoring active.
    01:06:00 26.01.2010   LOG: searching for Process Monitoring Templates in C:\usr\sap\PRFCLOG\dev_proc
    01:06:00 26.01.2010   LOG: searching for Process Monitoring Templates in C:\usr\sap\PRFCLOG\procmon\
    01:06:00 26.01.2010   LOG: The following processes will be monitored:
    01:08:01 26.01.2010   LOG: InitFsysData: PX_fsys_anz 4 > PX_fsys_anz_max 3
    01:08:01 26.01.2010   LOG: only retrieving data for 3 logical disks
    01:08:01 26.01.2010   LOG: PX_fsys_name[3]: L:    not logged!
    01:12:42 26.01.2010   LOG: InitFsysData: PX_fsys_anz 8 > PX_fsys_anz_max 3
    01:12:42 26.01.2010   LOG: only retrieving data for 3 logical disks
    01:12:42 26.01.2010   LOG: PX_fsys_name[3]: L:    not logged!
    01:12:42 26.01.2010   LOG: PX_fsys_name[4]: J:    not logged!
    01:12:42 26.01.2010   LOG: PX_fsys_name[5]: M:    not logged!
    01:12:42 26.01.2010   LOG: PX_fsys_name[6]: N:    not logged!
    01:12:42 26.01.2010   LOG: PX_fsys_name[7]: O:    not logged!
    01:12:52 26.01.2010   LOG: InitFsysData: PX_fsys_anz 9 > PX_fsys_anz_max 3
    01:12:52 26.01.2010   LOG: only retrieving data for 3 logical disks
    01:12:52 26.01.2010   LOG: PX_fsys_name[3]: L:    not logged!
    01:12:52 26.01.2010   LOG: PX_fsys_name[4]: J:    not logged!
    01:12:52 26.01.2010   LOG: PX_fsys_name[5]: M:    not logged!
    01:12:52 26.01.2010   LOG: PX_fsys_name[6]: K:    not logged!
    01:12:52 26.01.2010   LOG: PX_fsys_name[7]: N:    not logged!
    01:12:52 26.01.2010   LOG: PX_fsys_name[8]: O:    not logged!
    01:17:51 26.01.2010   LOG: InitFsysData: PX_fsys_anz 8 > PX_fsys_anz_max 3
    01:17:51 26.01.2010   LOG: only retrieving data for 3 logical disks
    01:17:51 26.01.2010   LOG: PX_fsys_name[3]: J:    not logged!
    01:17:51 26.01.2010   LOG: PX_fsys_name[4]: M:    not logged!
    Does anyone know where this parameter is set? (PX_fsys_anz_max)
    Greatly appreciate any help.
    Regards,
    Ahmad M.

    Hi Bhavik,
    I tried patching the saposcol service but still no luck.
    I was using patchno 32, now patchno 55. I read and followed all the steps in the notes you provided but still can't resolve the issue. I even cleared all the dev_coll and log files after patching. Below is the output of the logfile. Same error.
    10:14:40 29.01.2010   LOG: Shared Memory Size: 427422.
    10:14:40 29.01.2010   LOG: Connected to existing shared memory.
    10:14:40 29.01.2010   LOG: MaxRecords = 654 <> RecordCnt + Dta_offset = 3968 + 61
    10:14:40 29.01.2010   LOG: CountDynParts 225 records for RT_DISK
    10:14:40 29.01.2010   LOG: CountDynParts 75 records for RT_FSYS
    10:14:40 29.01.2010   LOG: CountDynParts 33 records for RT_CPU
    10:14:40 29.01.2010   LOG: CountDynParts 75 records for RT_LAN
    10:14:40 29.01.2010   LOG: Disk 9 Fsys 3 Cpu 8 Lan 3
    10:14:40 29.01.2010   LOG: AdaptDynParts
    10:14:40 29.01.2010   LOG:           from shm    computed
    10:14:40 29.01.2010   LOG: CPU  max:        8           8
    10:14:40 29.01.2010   LOG: LAN  max:        3          50
    10:14:40 29.01.2010   LOG: FSYS max:        3          50
    10:14:40 29.01.2010   LOG: DISK max:        9          50
    10:14:40 29.01.2010   LOG: InitFsysData: PX_fsys_anz 5 > PX_fsys_anz_max 3
    10:14:40 29.01.2010   LOG: only retrieving data for 3 logical disks
    10:14:40 29.01.2010   LOG: PX_fsys_name[3]: Q:    not logged!
    10:14:40 29.01.2010   LOG: PX_fsys_name[4]: L:    not logged!
    10:14:40 29.01.2010   LOG: /* validation records  */ 20
    10:14:40 29.01.2010   LOG: /* disks * 25          */ + PX_disk_anz_max * 25 = 9 * 25 = 225
    version
          SAPOSCOL version  COLL 20.95 701 - 20.68 NT 09/03/27, 64 bit, multithreaded, Non-Unicode
          compiled at   Aug 10 2009
          systemid      562 (PC with Windows NT)
          relno         7010
          patch text    COLL 20.95 701 - 20.68 NT 09/03/27
          patchno       55
          intno         20020600
          running on    MYBWESSPRD01 Windows NT 5.2 3790 Service Pack 1 8x AMD64 Level 15
    Regards,
    Ahmad M.
    Edited by: EAC EAC on Jan 29, 2010 10:54 AM

  • Error while starting saposcol - Segmentation fault

    Hello Experts,
    We are facing issues while starting saposcol on one of the application servers of our central prod system.
    The exe directory is NFS mounted from DB server on all the application servers and saposcol runs fine on them. Hence there is no issue with the file permissions, sticky bit etc.
    Initially we thought it was a memory release issue. But the problem persists even after system restart.
    We have tried starting it via sidadm user and root. but the error remains. We are getting following error during starting it.
    16:31:40 15.03.2010   LOG: Effective User Id is root
    Segmentation fault(coredump)
    file permission:
    -rwsr-x---    1 root     sapsys      2558385 Jun 07 2009  saposcol
    Please help!!
    Thanks,
    Anup Thatte

    HI Anup,
    I Hope you are starting saposcol properly..If you are still facing issue please grant more permission for saposcol executable. Atleast execute permission for everyuse. How about verifying permission with different host where its runnign perfectly.
    > saposcol -h
    Saposcol Usage:
    start Saposcol:
    saposcol  [-l] [pf=complete name of saposcol profile] [-t[level]] [-z]
    stop Saposcol:
    saposcol -k [pf=complete name of saposcol profile] [-t[level]] [-z]
    show Saposcol Status:
    saposcol -s [pf=complete name of saposcol profile] [-t[level]] [-z]
    thanks
    ashish

  • EWA Report Issue: No complete data is populated in EWA report

    Hi All,
    I am facing a problem where in, the generated EWA  report for our XI system is not poplated with the complete data. This problem is there from past 2 months and before that this EWA report for XI system was duly generated with full and correct data.
    There has been no changes in the recent time and all of a sudden this problem erupt. May any one help me in diagnosing this problem and solving it? Help is greatly appreciated.
    Should there be any queries, please do ask me.
    Waiting for your kind replies.
    Regards,
    Faisal

    Hi Faisal,
    Last time I asked you if the Red flag was gone.
    You are saying the ABAP data is missing.
    This would mean there is a Rated EWA report missing the ABAP instance data.
    Does this mean it is a dual stack and the Java data is present.
    EWA is a pretty straight forward process, so if you follwo the process, you can usually narrow down where the problem has occurred.
    If ABAP data is missing in a generated EWA report, the first place to look for that missing data is in the service session.
    You can view the service session by clicking the eye glasses under tha activity column in DSWP, or entering the session number in transaction DSA. If the data is mssing, then it never got to solution manger from the managed system, so you would then check the RFC functions and the RFC user has a valid logon, THere would be no point checking SM:EXEC:SERRVICES, or authorizations if the data is not int he service session.
    If the data is in the service session and is missing, then it would be in the processing of the session into a Word ot HTML document, not the processing of the service session, because it would be processed and rated already by SM:EXEC SERVICES..
    I had explained that you create an EWA and it is scheduled in DSWP > Solution Monitoring > Earlywatch Alert
    it creates a service session, with a number and a tree. This is determined by the defintions in SMSY and the mapping to the DMD. It is scheduled for a date and time. On the managed system via RFC throught the maintenance package task in SDCCN or perhaps a scheduled refresh session taask, runs and via RFC to SOlman, logs on with the RFC use (SM*_BACK) and gets the
    session numbers of unprocessed servies sessions for that SID. If it can't open the service session, it will just find not sessions to refresh. If it can, then an EWA task is created that will prepare a transport with the collected data. So if the collectors have issues, data won't be available. ST-A/PI and ST-PI are involved on colelction of data and preparation for transport on managed systems. But there is also SAPOSCOL and ST03 and ST06 that need to be checked. The SDCCN EWA task log. Then it sends the data back to Solman via the RFC and either the single Flask or the red flag will then turn to 2 flasks indicating the data is ready to be processed by SM:EXEC SERVICES. SM:EXEC SERVICES processes the session, populates it, and rates it.
    Then you can look at the session in DSA o DSWP, you can geerate the report in Word or HTML.
    So this is the process.flow overview. And it helps to know where it gets to in the flow to determine where something went missing or if it was ever there at all.SM:EXEC SERVICES doesn't colelc the data. So if it processes a service session the user had the authorizations. If the data is not int he service session its because it was never passed to Solution manage.
    Iif the data is in thd service session, but missing from the report, then the issue is likely with ST-SER, or perhaps SCU.update has not been applied.
    I suspect that the data is not in the service session and you are still having issues. Is the EWA still red flagged? Yes or No?
    If yes, then you still have an issue where no ABAP data was sent via SDCCN to Solman. If no, then likely there is an issue with
    collection, where data is being sent, but some data is missing, and this could be due to errors that have not been addressed in the SDCCN task logs. Or it could be problems wit SDCCN service definitions, and may need to be replaced.
    I hope tis helps.
    Regards,
    Paul

  • AIX - Oracle - Saposcol error log WARNING: SNAPDISK hdisk0 RESETING

    Dear all,
    I've this error log on ST06- OS Collector - Log Files
    14:24:40 25.02.2009   LOG: INFO: saposcol's shared memory size is 3692752.                                                           
    14:24:40 25.02.2009   LOG: INFO: saposcol is NOT running with EXTSHM=ON.                                                             
    14:24:40 25.02.2009   LOG: Shared Memory was created by process:942318                                                               
    14:24:40 25.02.2009   LOG: ==== Collector submitted. This is the parent process after fork.=====                                     
    14:24:43 25.02.2009   LOG: ==== Collector submitted. This is the child process after fork()=====                                     
    14:24:46 25.02.2009   LOG: Collector started - Version: COLL 20.87 640 - AIX v4.20 5L-64 bit 040309                                  
    14:24:47 25.02.2009   LOG: read put-file Wed Feb 25 10:06:30 2009                                                                    
    14:24:47 25.02.2009   LOG:  Collector PID: 958488                                                                               
    23:01:42 25.02.2009 WARNING: SNAPDISK:          hdisk0   > RESETING                                                                  
    23:01:42 25.02.2009 WARNING: SNAPDISK:         Prev rblks:     180724  Curr rblks:     182308                                        
    23:01:42 25.02.2009 WARNING: SNAPDISK:         Prev wblks:     172336  Curr wblks:     652648                                        
    23:01:42 25.02.2009 WARNING: SNAPDISK:         Prev xfers:      29582  Curr xfers:      37728                                        
    23:01:42 25.02.2009 WARNING: SNAPDISK:         Prev time:       12312  Curr time:       15237                                        
    23:01:42 25.02.2009 WARNING: SNAPDISK:         kb/s: 10642  ops/s: 359  util: 129  secs: 22.640    > RESETING                        
    23:01:42 25.02.2009 WARNING: SNAPDISK:          hdisk1   > RESETING                                                                  
    23:01:42 25.02.2009 WARNING: SNAPDISK:         Prev rblks:     169501  Curr rblks:     171341                                        
    23:01:42 25.02.2009 WARNING: SNAPDISK:         Prev wblks:     174376  Curr wblks:     654320                                        
    23:01:42 25.02.2009 WARNING: SNAPDISK:         Prev xfers:      23540  Curr xfers:      31712                                        
    23:01:42 25.02.2009 WARNING: SNAPDISK:         Prev time:       11425  Curr time:       14359              
    This system is on AIX 5.3 64 bit and Oracle 9 with ECC 5.0. This system was hung yesterday, when we try to restart Oracle and SAP, it was stuck again in saposcol start phase. But when we restart whole server with init command, the sap system can be started normally, but recently i found this error message in the saposcol log file. Before the server hung incident, the saposcol log file also display this kind of error.
    I just wonder, what is Warning: SNAPDISK about? is there any relationship with this error and the server hung incident. I search with the keyword but i found very minimum information....              
    Is it really need to start saposcol with environment variable EXTSHM = ON?
    Please kindly advise..
    Big thanks
    Fendhy.

    >
    Ongko Fendhy wrote:
    > Hi Mark,
    >
    > Thanks for replying..
    >
    > 1.) So i just can ignore this kind of warning. Btw this warning displayed so frequently. Still i can ignore it?
    >
    > 2.) Because it show a warning LOG: INFO: saposcol is NOT running with EXTSHM=ON everytime i start the saposcol so i think it is may be needed to set the EXTSHM env variable.
    >
    > 3.) The process stop on starting saposcol phase, so the rest of the startsap sequence never got executed
    >
    > Thanks a lot.
    Hi Fendhy,
    1) Yes, to the best of my knowledge you may ignore it. However if the warning indeed is so very frequent, then it would be good if you reported it in a SAP support message. I understand that SAP was working on making the code more intelligent in dealing with this kind of numeric quirks, so there might be a more recent saposcol version that gets rid of the problem.
    2) This message is purely informational. You could actually set EXTSHM=ON on a 64-bit platform but there would not be any practical benefit apart from no longer getting the INFO message in the log. Since EXTSHM is ignored with 64-bit, it cannot normally be the cause of the problem that you encountered.
    3) In that case there might be a specific issue with saposcol, which does not affect the database and SAP instance. If possible you might try reproducing the problem by starting saposcol separately with a higher trace level, e.g. "saposcol -l -t2 -z". If the hang occurs and the saposcol trace doesn't make you any wiser, you can also try monitoring the saposcol PID with "truss" (truss -p <pid>)
    Hope this helps,
    Mark

  • SAPOSCOL has been stopped in PROD CI

    Dear all,
    saposcol has been stopped in Prod CI server iand Prod APP1 & APP2 are working .
    when i try to start SAPOSCOL i got the below error .
    PRDCIXI:irpadm 4> saposcol -l
    -l
    open logfile '/usr/sap/tmp/dev_coll.tmp' failed... use stderri
    19:22:29 15.03.2010 ERROR:  cannot open log file /usr/sap/tmp/dev_coll.tmp
    19:22:29 15.03.2010 ERROR:  Make sure directory /usr/sap/tmp exists or specify D
    IR_PERF
    19:22:29 15.03.2010 ERROR:  in profile and run saposcol pf=<profile>
    how can i make up SAPOSCOL
    and what reason it has been stopped .
    kindly suggest
    Regards

    > open logfile '/usr/sap/tmp/dev_coll.tmp' failed... use stderri
    > 19:22:29 15.03.2010 ERROR:  cannot open log file /usr/sap/tmp/dev_coll.tmp
    > 19:22:29 15.03.2010 ERROR:  Make sure directory /usr/sap/tmp exists or specify D
    Hi,
    This is common error and just permission issue.
    As it says, go to /usr/sap dirctory and check the existence of tmp directory.
    if tmp is not present, create it with <sidadm:sapsys permission.
    if tmp is present, then give 777 to all of it's content i.e. from root user
    cd /usr/sap/
    chmod -R 777 tmp
    => in case you do not want to touch all of tmp's content then just give 777 to /usr/sap/tmp/dev_coll.tmp
    and start saposcol from sidadm using saposcol -l
    Cheers !!!
    Ashish

  • SAPOSCOL Stops automatically

    Hi All,
    In one of the Application Server SAPOSCOL was not running and in ST06 we were not able to see ne data ,when I checked in c:\usr\sap\prfclog directory and checked dec_coll log I found that dev_proc file was missing so I manually created it manually,and restarted the SAPOSCOL service after that our issue got resolved but next day when I checked the SAPOSCOL service it was not running and nothing was getting displayed in ST06 again I started the SAPOSCOL manually and ST06 started showing the data.Why this is happening?
    What could be the reason behind this?
    Regards,
    Prashant

    Hi All,
    I checked all the errors in eventvwr since last time I started the SAPOSCOL.
    1) SAP BASIS SYSTEM: OS call SiPeekPendconn failed(error no. 10060)
    2) Windows cannot unload your classes registry file
    3) SAP BASIS SYSTEM: Conn. to user lost terminal 256
    4) SAP BASIS SYSTEM: OS call recv. failed (error no. 10054)
    5) Windows can not determine the user or computer name domain either does not exist or could not be contacted)
    6) SAP service SAPWP_02 has been stopped successfully
    7) SAP service SAPWP_02 has been started successfully
    8) SAP BASIS SYSTEM: Call of function GwRead failed -RC006
    Pls suggest what should I do now to resolve this issue.
    Regards,
    Prashant

  • SMD Setup - saposcol problem

    Hello Gurus,
    We have done the SMD and willy setup for our MDM system (Non Abap).
    The problem we  are facing is saposcollector data is not visible in willy web view.
    While looking into the agent application log we see following error
    "Warning    com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAPOsCol not running because status is PERMANENT_ERROR"
    We are using solman system 7.0 EHP1, SMD Agent 7.01, MDM system 7.1. Saposcol verion 700 patch-159 64 bit.
    Need your help to resolve the issue related to oscol and have the oscol data available in willy webview.
    Regards
    Manoj

    Hi Manoj,
    please keep in mind that the saposcol on the satellite system and the saposcol of the SMD Agent on the same sattelite system has to be synchronized.
    It means you should have the same version, the lastest one, on the satellite system. You do not need to change the version of saposcol on SMD server.
    After changing the version of saposcol of the SMD Agent, you have to restart the agent or reboot the applications via SMD -> Diagnostics Administration -> Managed System -> Agent Administration, click on the corresponding SMD agent and select Reboot Agent.
    Please check also that the management modules not based on an old version:
    In general there are 2 possibilities:
    1. Upgrade the Management Module
    2. Upgrade of the entire Enterprise Managers
    Regards,
    Shyam.

  • Saposcol is not running.

    I am logging through <sid>adm & try to start the saposcol it gives the following error.
    pp6adm> saposcol -l
    -l
    open logfile '/usr/sap/tmp/dev_coll.tmp' failed... use stderri
    13:40:28 22.05.2009 ERROR:  cannot open log file /usr/sap/tmp/dev_coll.tmp
    13:40:28 22.05.2009 ERROR:  Make sure directory /usr/sap/tmp exists or specify DIR_PERF
    13:40:28 22.05.2009 ERROR:  in profile and run saposcol pf=<profile>
    I am working on portal( only java engine),unix environment.Please give me details steps to start the saposcol as i am new to unix.
    Regards
    Nilesh Shete.

    Hi Nilesh,
    The setting of saposcol shoule be like this
    -rwsr-xr-x 1 root sapsys . . . .. saposcol
    Have u upgraded your SAP Kernel ?
    Its pointing to permissions issue.
    Try this.
    As a root user..
    chown root saposcol icmbnd
    chmod 4755 saposcol icmbnd
    then..
    As a <sid>adm user, try to start saposcol.
    saposcol -l
    Also, make sure to remove the dev_coll.put file (if it is created...) ,after taking backup of /usr/sap/tmp/* .
    Regards
    Bhavik G. Shroff

  • Saposcol is running intermittently

    Good Day Experts,
    Can you guide me on how to solve the issue we are facing in SAPOSCOL? The situation is this, after startfing the saposcol using this command "saposcol -l" it works fine then while checking on st06 data is there. However, after few minutes and refreshing st06 the data seems gone and I am getting this error "SAPOSCOL not running Shared Memory not available".  And what I did after is that I logged off from SAP and log in again and SAPOSCOL works fine again. However after few minutes of refreshing the data in st06 seems gone again.
    What I noticed is that SAPOSCOL is running intermittently in SAP.
    Regards,

    Hi James,
    Look into SAP Note 548699 - FAQ: OS collector SAPOSCOL
    7th point will help you in removing/releasing shared memory
    Regards
    Nick Loy

Maybe you are looking for