on 08-08-2007 4:57 AM
Dear support,
We are getting dump compute_bcd_overflow while executing transaction ST06 and we also tried to restart SAPOSCOL but still problem exist. We cannot take restart as it is productive system.
Please let me know the reason for the same.
Hello,
may be saposcol has some wrong values in its shared memory.
Did you check it? Are you running up to date version of saposcol?
you can try to clean up SHM like described in
<a href="https://service.sap.com/sap/support/notes/189072">Note 189072 - ST06/OS06: No data or incorrect data displayed</a>
best regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
G:\usr\sap\PRD\D02\exe>saposcol -d
**************************************************************************
This is Saposcol Version COLL 20.77 02/05/06 46D - 20.35 NT 02/12/09
Please use 'help' to see the usage.
**************************************************************************
Collector > dump cpu
dump cpu
cpus: 0
usr: 0% sys: 0% idle: 0% = 0% (true idle) + 0% (io-wait)
ldavg1: 9776742.98 ldavg5: 38192.96 ldavg15: 0.00
int/s: 0 sysc/s: 0 cs/s: 0
h: 6 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h: 7 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h: 8 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h: 9 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:10 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:11 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:12 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:13 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:14 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:15 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:16 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:17 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:18 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:19 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:20 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:21 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:22 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:23 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
ya infact i have found one perfmon.exe under C:\windows\system32
and when i executed and then + button added CPU and memory and it is giving correct data , i am able to analyse many things,
What i think , as saposcol service was not executing on those 2 application servers from more than month now, this transaction ST06 working properly in all other Apps servers except these 2. And as now services are started on those 2 servers now , it is not able to compute and display all months data on screnen and is giving dump as "compute_bcd_overflow" and i think the solution would be to restart all apps servers along with CI and DB instance , means complete shutdown and restart of Production system would give solution.
So what you suggess i need to replace SAPOSCOL version by latest one while R3 system is running as per note . But client will ask me same version on all 5 Apps servers running fine , then whats up with these 2 servers where it was not running from long time. If it is problem with version , then why it is working for other Apps ???
thanks for commands but those are already there with note , but could you please tell me why does coll.put require , whats the use for coll.put does it collect values ?
Also if follow this procedure
stop saposcol service
saposcol -d
kill
leave
exit
delete coll.put,
saposcol -l
Now what should i do next .
I have given this command before and again i am going
G:\usr\sap\PRD\D02\exe>saposcol -d
**************************************************************************
This is Saposcol Version COLL 20.77 02/05/06 46D - 20.35 NT 02/12/09
Please use 'help' to see the usage.
**************************************************************************
Collector > dump cpu
dump cpu
cpus: 0
usr: 0% sys: 0% idle: 0% = 0% (true idle) + 0% (io-wait)
ldavg1: 9776742.98 ldavg5: 38192.96 ldavg15: 0.00
int/s: 0 sysc/s: 0 cs/s: 0
h: 6 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h: 7 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h: 8 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h: 9 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:10 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:11 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:12 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:13 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:14 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:15 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:16 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:17 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:18 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:19 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:20 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:21 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:22 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
h:23 C0 u/s/i(i/w): 0/ 0/ 0( 0/ 0) int/h: 0 sysc/h:
0 cs/h: 0
User | Count |
---|---|
89 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.