quarta-feira, 11 de agosto de 2010

Trace file's rotation and system restart

You have lost the trace file to perform an anlysis on the system behavior after an error/crash/hung situation.

Every system restart, the trace files are overwritten.
When you start the instance, all files from the services (message
server, dispatcher, work process, ICM and others) are truncated and only
the actual log status information are writen.

But, before truncate the actual trace files, the system create a backup
of this trace file with the .old extension.

Although exist the mechanism to create a backup of the trace file, if
you restart the system more than one time, the .old trace file will be
overwritten too.

A good pratice is make a copy of the work directory before the start up.

segunda-feira, 2 de agosto de 2010

Parameter changes without restart

If you need to change some memory parameters but you cannot restart the instance, have solution.
You can change the parameters from RZ11 and run the remport RSMEMORY.

610965 Parameter in RZ11 cannot be switched

quinta-feira, 29 de julho de 2010

java start up

To start up the java stack in a dualstack system or only java.

jcontrol -DSAPSTART=1 pf=/usr/sap/xxx/SYS/profile/xxx_DVEBMGS00_dostname

This is the same than as sapcontrol.

quarta-feira, 7 de julho de 2010

Error in monitoring information

If you are not able to see the statistics information from ST03/ST03N, this can be a error in the timezone configuration.
Please note that the time can been seen at diffenret levels:

1. Operating System Time (or) System time
2. Time zone at Client level whcih is client dependent
3. User time zone whcih can be set using tocde SU3

Make sure if the timezone between the clients and operation system are the same.

926290 SWNCCOLL: SAP workload NW collector collects no data
741734 Incorrect times due to the time zone settings
481835 Analyzing the time zone settings
198411 Current data and information about time zones

terça-feira, 6 de julho de 2010

monitoring updates SM13

To monitoring the failed updates in SM13 you should go to
RZ20 ->
SAP CCMS Technical Expert Monitors ->
All Contexts on Local Application Server ->
Update
UpdateServices
Old Update Record

Select this MTE and click in Proprerties.
In the performance Attribute have the thresholds that will be compared
with the last 24 hours, the the number of the update is around the
threshoulds, the new alert will be created.

sexta-feira, 18 de junho de 2010

Operating system

AIX
1)
instfix -ik

2) to get the memory consuption for a specific process.
You should get the INUSE output and multiply for 4096 to get the value in bytes:
svmon -P (to analyse a specific process)

svmon -G (to analyse the total memory)
svmon -Pnsm (to analyse the top process)

ps auxw  | sort -r +3  (process sort by memory consuption)

svmon -Pt15 | perl -e 'while(<>){print if($.==2||$&&&!$s++);$.=0 if(/^-+$/)}'



SOLARIS

1) to analyse the memory usage for each process:
/usr/bin/ps -eo 'zone user pid ppid vsz rss args'


WINDOWS
1) to find a specific string in a OUTPUT:
netstat -an | findstr LISTEN

2) to list process from prompt line
tasklist

3) services
sc qc


HP-UX

memory statistics:
ps -el | sort -rnk10 
will list all processes on the system, sorted by the SZ column.

quinta-feira, 17 de junho de 2010

NIPING tests

#Name resolution
niping -v -H

# With option -L 6048000 the test will run for 7 days.
niping -c -H -B 10000 -D 100 -L 6048000

#niping as server
niping -s -I 0 -T NIPING_SERVER_TRACE

#niping as client
niping -c -H -X3 -B 10 -D 30 -T NIPING_CLIENT_TRACE

500235