Incomplete data on ST06

Question

Hello.
Kindly help me on this.
We have installed EP7.0 (Win2003 and Oracle DB). Then after resetting server battery, we found no data on ST06 for CPU, Filesys, etc.
<b>Here's the Log File at ABAP stack:</b>
Collector Versions
  running                                         COLL 20.94 700 - 20.59 NT 07/05/25
  dialog                                            COLL 20.94 700 - 20.59 NT 07/05/25
Shared Memory                                attached
Number of records                            271
Active Flag                                      active (01)
Operating System                            Windows NT 5.2.3790 SP 1 MDCSAP04 8x Intel 80158
Collector PID                                    8412 (000020DC)
AdjustTokenPrivileges failed with 1300
Collector                                          running
Start time coll.                                  Fri Jun 29 11:36:59 2007
Current Time                                     Fri Jun 29 16:26:52 2007
Last write access                              Fri Jun 29 16:26:45 2007
Last Read  Access                            Fri Jun 29 16:26:43 2007
Collection Interval                              10 sec (next delay).
Collection Interval                              10 sec (last ).
Status                                              free
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
<b>And here's the result of running sapfpar:</b>
C:\>sappfpar check pf="00"
sappfpar=>sapparam(2): fopenU("00","r"): No such file or directory
sappfpar=>No Profile used.
sappfpar=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
===========================================================
Checking profile:     <no_profile>
===========================================================
Shared memory disposition overview
===========================================================
Key:        1  Size:        2500 (   0.0 MB) System administration
Key:        2  Size:     4189244 (   4.0 MB) Disp. administration tables
Key:        3  Size:    13714400 (  13.1 MB) Disp. communication areas
Key:        4  Size:      503248 (   0.5 MB) statistic area
Key:        5  Size:        4096 (   0.0 MB) SCSA area
Key:        6  Size:   159744000 ( 152.3 MB) ABAP program buffer
Key:        7  Size:       14838 (   0.0 MB) Update task administration
Key:        8  Size:   134217828 ( 128.0 MB) Paging buffer
Key:        9  Size:   268435556 ( 256.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:    60500000 (  57.7 MB) Alert Area
Key:       14  Size:     4400000 (   4.2 MB) Presentation buffer
Key:       16  Size:       22400 (   0.0 MB) Semaphore activity monitoring
Key:       17  Size:     2678942 (   2.6 MB) Roll administration
Key:       18  Size:      917604 (   0.9 MB) Paging adminitration
Key:       19  Size:    30000000 (  28.6 MB) Table-buffer
Key:       30  Size:        3072 (   0.0 MB) Taskhandler runtime admin.
Key:       31  Size:     1806000 (   1.7 MB) Dispatcher request queue
Key:       33  Size:    10240000 (   9.8 MB) Table buffer, part.buffering
Key:       41  Size:    25010000 (  23.9 MB) DB statistics buffer
Key:       42  Size:     7232992 (   6.9 MB) DB TTAB buffer
Key:       43  Size:    32534392 (  31.0 MB) DB FTAB buffer
Key:       44  Size:     7958392 (   7.6 MB) DB IREC buffer
Key:       45  Size:     4886392 (   4.7 MB) DB short nametab buffer
Key:       46  Size:       20480 (   0.0 MB) DB sync table
Key:       47  Size:     3073024 (   2.9 MB) DB CUA buffer
Key:       48  Size:      300000 (   0.3 MB) Number range buffer
Key:       49  Size:     2968344 (   2.8 MB) Spool admin (SpoolWP+DiaWP)
Key:       51  Size:     3200000 (   3.1 MB) Extended memory admin.
Key:       52  Size:       40000 (   0.0 MB) Message Server buffer
Key:       54  Size:     4202496 (   4.0 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
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
Nr of operating system shared memory segments: 40
Shared memory resource requirements estimated
===========================================================
Total Nr of shared segments required.....:         40
Shared memory segment size required min..:  268435556 ( 256.0 MB)
Swap space requirements estimated
===========================================================
Shared memory....................:  844.6 MB
Processes........................:   27.1 MB
Extended Memory .................: 15611.0 MB
Total, minimum requirement.......: 16482.6 MB
Process local heaps, worst case..: 1907.3 MB
Total, worst case requirement....: 18390.0 MB
Errors detected..................:    0
Warnings detected................:    0
We already change the version of saposcol. Restart the server after stopping saposcol. What else should be done to bring back the data at ST06.
Thanks,
Abe

Answer 1

Abe,
Not sure what you're looking for here - EP 7.0 does not have a transaction code ST06? Are you looking to pull this information into another server? Or does your Portal have an ABAP stack?
Anyway, the issue you have here is that the files at the OS level which will store the information gathered by SAPOSCOL are not available/accessable.
When SAPOSCOL runs, it will store it's information in several files - in UNIX for example /usr/sap/tmp - and if I remember correctly the same structure on Windows platforms.
At the OS level, when you run saposcol -l /saposcol -k in a command window - do you get errors about permissions of a file in /usr/sap/tmp? Maybe a file it wants to find is not there anymore?
Looks to me like the OSCOL is running, but it's not 'saving' any information for ST06 to read.
Let me know how you do.
Cheers,
Tim