Mostrando postagens com marcador BC. Mostrar todas as postagens
Mostrando postagens com marcador BC. Mostrar todas as postagens

quinta-feira, 16 de fevereiro de 2012

languages

RSCP0018 = Check profiles for language, character sets and so on
RSCPINST = NLS (Native Language Support) settings

sábado, 11 de fevereiro de 2012

automatic start a transaction after login

in the main menu (transaction SMEN) go to EXTRAS -> SET START TRANSACTION.
This rule is stored in the table "agr_dateu"

sexta-feira, 18 de novembro de 2011

Semaphore statistics

To active it
transaction ST02 ->
buttons 'Detail Analysis Menue' ->
'Semaphores'.

The measurement is switched on automatically.

To switch it off
menu 'Settings' ->
'Monitoring Off'.

To download the list
OK-code '%PC'


terça-feira, 12 de abril de 2011

what to do at the moment of incident

Follow the below steps and try to collect the greatest number of
possible evidences:

1) Analyse from the Operating System side:
a. Is it possible to connect to the OS level?
b. Is there any CPU, IO, memory bottleneck (check with OS tools)?


2) Collect the queue status of SAP dialog instance:
a. dpmon pf= l
b. sapcontrol -nr -function ABAPGetWPTable

You should get the queue status of the instace during around 10 or
15 minutes to check if the work process are changing the status in that
timeframe or they are really hanged. For the sapcontrol you can use the
option "-repeat " (call times (-1=forever) with sec
delay) and for dpmon see the scrip of note 675778.


3) Collect queue statistics:
a. dpmon pf= d
b. sapcontrol -nr -function GetQueueStatistic

4) Collect enqueue statistics (ASCS)
a. sapcontrol -nr -function EnqGetStatistic
(as from 710)
b. transaction SM12 -> Extras -> Statistics


5) Collect process status of the instance:
a. sapcontrol -nr -function GetProcessList

If you are not sure where the problem is you should collect this
information for all available instances.


6) Collect the gateway statistics:
a. gwmon


7) Increase the trace level of work process:
a. kill -USR2
b. sapntkill -USR2 (for windows enviroment)

You can get the PID of the work process in SM50, dpmon or sapcontrol
(see item 2). This will increase the dispatcher/work process trace file
and provide further data in the trace. Call this command twice for the
PID.


8) Always SAVE the work folder with the traces:
You do find the instance work folder in
/usr/sap///work
Every incident you must save the work folder of this instance before
the restart or soon as after the start up.


9) Get the timestamps (date and hour) of all events;


10) Collecting the SAP instance parameters:
a. sapcontrol -nr -function ParameterValue
b. sappfpar all pf=LOL_DVEBMGS01_lolserver
c. transaction rspfpar

segunda-feira, 14 de março de 2011

sapcontrol webmethods list

Webmethods list:

==> Start-----------------------------------------------------------
BASIC: sapcontrol -nr -function Start
To start up the SAP instance


==> Stop [softtimeout sec]-----------------------------------------
BASIC: sapcontrol -nr -function Stop
This is a faster method stop the SAP instance.
This will kill the SAP Instance using OS commands.
The processes of the instance are terminated with a signal 9 (kill -9).
The instance shared memory is also removed (cleanipc remove).
The file kill.sap in the instance work folder is deleted.


==> Shutdown------------------------------------------------------
BASIC: sapcontrol -nr -function Shutdown
A normal shutdown of the instance
The SAP instance will be stopped in normal process.


==> RestartInstance [softtimeout sec]-----------------------------


==> StopService---------------------------------------------------


==> StartService --------------------------------------------


==> RestartService------------------------------------------------


==> ParameterValue []----------------------------------
BASIC: sapcontrol -nr -function ParameterValue
Show the instance parameters and the actual parameter value.
Without the option you do list all parameters of the instance.

The same output of: RZ11


==> GetStartProfile----------------------------------------------
BASIC: sapcontrol -nr -function GetStartProfile
Show all lines of the instance start profile

The same output of: RZ10


==> GetTraceFile------------------------------------------------


==> GetAlertTree------------------------------------------------


==> GetAlerts---------------------------------------------------


==> GetEnvironment----------------------------------------------
BASIC: sapcontrol -nr -function GetEnviroment
This will return the enviroment variable to the
actual user.

The same output of: similar comand "env" in the UX system


==> GetVersionInfo---------------------------------------------
BASIC: sapcontrol -nr -function GetVersionInfo
Return the actual version information about each service
from that instance.

The output have the format below:
Filename = File path fo that service
Versioninfo = version and patch level
Time = Date of the compilation


==> GetQueueStatistic-----------------------------------------
BASIC: sapcontrol -nr -function GetQueueStatistic
Show the Queue information of the instance.

The same output of: SM51 -> Goto -> Queue Information

The output have the format below:
Typ = Type of the queue (ex: DIA, UPD, BTC, etc)
Now = Actual number of waiting requests
High = The bigger number of requests in the queue
Max = Limit of the queue
Writes =
Reads =


==> GetProcessList-------------------------------------------
BASIC: sapcontrol -nr -function GetProcessList
This will return all services from the instance and the actual status of
each one.

The output have the format below:
name = Program name
description = Service Description
dispstatus = GRAY = unavailable, GREEN = running, YELLOW = statring
textstatus = Information about the service
starttime = Started at
elapsedtime = Time running
pid = Process ID in the Operating System


==> GetInstanceProperties------------------------------------


==> ListDeveloperTraces--------------------------------------
BASIC: sapcontrol -nr -function ListDeveloperTraces
List the developer traces found in the work folder

The same output of: ST11

The output have the format below:
filename =
size =
modtime =


==> ReadDeveloperTrace -----------------


==> ListLogFiles---------------------------------------------
BASIC: sapcontrol -nr -function ListLogFiles
List all logs from the instance.

The same output of: ST11

The output have the format below:
filename = the file of the trace
size = size of the file
modtime = last modification of the trace
format = usually text


==> ReadLogFile [ [ [ []]]]


==> AnalyseLogFiles [] [] [ ]


==> OSExecute ----


==> SendSignal -------------------------------


==> GetSystemInstanceList-----------------------------------
BASIC: sapcontrol -nr -function GetSystemInstanceList

The output have the format below:
hostname =
instanceNr =
httpPort =
httpsPort =
startPriority =
features =
dispstatus =
linux, 0, 50013, 0, 2, ABAP|GATEWAY|MESSAGESERVER|ENQUE|ICMAN, YELLOW


==> StartSystem [ALL|SCS|DIALOG|ABAP|J2EE|LEVEL []]


==> StopSystem [ALL|SCS|DIALOG|ABAP|J2EE|LEVEL [[] [softtimeout sec]]]


==> RestartSystem [ALL|SCS|DIALOG|ABAP|J2EE|LEVEL [[] [softtimeout sec]]]


==> AccessCheck ---------------------------------


==> ABAPReadSyslog-----------------------------------------
BASIC: sapcontrol -nr -function ABAPReadSyslog
List the SAP syslog entried.

The same output of: SM21

The output have the format below:
Time =
Typ =
Client =
User =
Tcode =
MNo =
Text =
Severity =
2011 02 12 20:26:46, D0, 000, SAPSYS, , A10, SAP Basis System: Initialization complete, GREEN


==> ABAPReadRawSyslog--------------------------------------


==> ABAPGetWPTable-----------------------------------------
BASIC: sapcontrol -nr -function ABAPGetWPTable
List the work process table list.
The same output of: SM50

The output have the format below:
No, Typ, Pid, Status, Reason, Start, Err, Sem, Cpu, Time, Program, Client, User, Action, Table
0, DIA, 9254, Wait, , yes, , , 0:04:50, , , , , ,
1, DIA, 9255, Wait, , yes, , , 0:00:28, , , , , ,
2, DIA, 9258, Wait, , yes, , , 0:00:21, , , , , ,


==> J2EEControlProcess
==> J2EEGetProcessList
==> J2EEGetThreadList
==> J2EEGetSessionList
==> J2EEGetCacheStatistic
==> J2EEGetApplicationAliasList
==> J2EEGetVMGCHistory
==> J2EEGetVMHeapInfo
==> StartWait
==> StopWait
==> WaitforStarted
==> WaitforStopped

quinta-feira, 13 de janeiro de 2011

Shared Memory Areas

1 "System administration "
2 "Disp. administration tables "
3 "Disp. communication areas "
4 "statistic area "
5 "SCSA area "
6 "ABAP program buffer "
7 "Update task administration "
8 "Paging buffer "
9 "Roll buffer "
10 "Pool "
11 "Factory calender buffer "
12 "TemSe Char-Code convert Buf. "
13 "Alert Area "
14 "Presentation buffer "
15 "Document administration "
16 "Semaphore activity monitoring"
17 "Roll administration "
18 "Paging adminitration "
19 "Table-buffer "
20 "Unused1 "
21 "Unused2 "
22 "Unused3 "
23 "Unused4 "
24 "Unused5 "
25 "Unused6 "
26 "Unused7 "
27 "Unused8 "
28 "Unused9 "
29 "Unused10 "
30 "Taskhandler runtime admin. "
31 "Dispatcher request queue "
32 "unknown segment "
33 "Table buffer, part.buffering "
34 "Enqueue table "
35 "Sap-Communication BK/EDI "
36 "Performance monitoring "
37 "Fast SEM ADM on MPE & AS400 "
38 "Event ADM on AS400 "
39 "Queue ADM on AS400 "
40 "Pool for database buffers "
41 "DB statistics buffer "
42 "DB TTAB buffer "
43 "DB FTAB buffer "
44 "DB IREC buffer "
45 "DB short nametab buffer "
46 "DB sync table "
47 "DB CUA buffer "
48 "Number range buffer "
49 "Spool admin (SpoolWP+DiaWP) "
50 "Pool 50 "
51 "Extended memory admin. "
52 "Message Server buffer "
53 "Extended memory test tool "
54 "Export/Import buffer "
55 "Spool local printer+joblist "
56 "Application statistics "
57 "Profilparameter in shared mem"
58 "Enqueue ID for reset "
59 "Enqueue table extension AS400"
60 "Enqueue table addition AS400"
61 "Extended memory only on AS400"
62 "Memory pipes "
63 "ICMAN shared memory "
64 "Online Text Repository Buf. "
65 "Export/Import Shared Memory "
66 "Enqueue Replication Shadow "
67 "ICRouter HTTP Client Table "
68 "JControl Administration "
69 "JControl Administration "
70 "java area "
71 "ITS Events "
72 "ITS Mutexe "
73 "CCMS Extended Alert Area "
74 "VMC Lite Admin "
75 "VMC Lite ES "
76 "Ext. Segment Administration "
77 "Ext. Memory Administration "
78 "Ext. Global Memory Admin "
79 "JStart static instance info "
80 "JStart dynamic data "
81 "Security Audit Log "
82 "Web Disp EUID Table "
83 "ABAP Coverage Analyzer "
101 "Performance monitoring "
102 "Performance monitoring V01.0 "
103 "Global spool storage "
108 "Network monitoring "
121 "SCSA area "

quarta-feira, 22 de setembro de 2010

HTTPWatch traces

1. Install the free version of HTTPWatch 6.x (http://www.httpwatch.com)
on your Internet Explorer.

2. Start the browser, start the HTTPWatch, click on 'Record' button,
and please reproduce the issue.

3. On finish 'Save' the contents of HTTPWatch as a .hwl file
(Please note: Exporting as CSV or XML is not so helpful, so please use
the default save option).

4. Save .hwl file to this message.

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.

sexta-feira, 21 de maio de 2010

Make last versions

STARTSAP and STOPSAP scripts
#809477 startsap and stopsap <= SAP WebAs 640, 700/701 and 710/711

CPS (REDWOOD)
#1257610 How to download SAP CPS for NetWeaver 7.0 and 7.01

quinta-feira, 29 de abril de 2010

triks

Transactions, Reports and Function Module:

- To ping a remote IP addres = OS01. Report RSHOST14
- Perform commands in the OS level = report RSBDCOS0
- See the work process trace file = SM50 and w
- Check the last trace file changed = ST11
- Change the application server = SM51 and twice in the appl
- Send message for an user logged = Function Module TH_POPUP

R3:
- Ctrl & + = open a new session
- Ctrl Shift F8 = go to command bar
-