CPU
sar, vmstat, mpstat, iostat
Memory
sar, vmstat
Disk
sar, iostat
Network
netstat
BR1049W Not enough free space in /oracle/sid/sapdata5/sr3_63
for total maximum size of all database files of tablespace PSAPSR3
located on this disk volume, missing at least 272.222 MB
-------------------------------
"Knowledge is power, but it is only useful if it is shared!"
A sample backup schedule might look like:
1. Hourly - brarchive backup of archive logs
2. Daily - brbackup backup of full database
3. Monthly - file system backup of /sapmnt/, including SAP executables and profile data, and /oracle/SID/_/dbs & network ---making sure you get Oracle/SAP init files and network files (tnsnames.ora, listener.ora,\nnames.ora, etc., though you might have relocated these files elsewhere), & /usr/sap/trans directory.
4. Quarterly - Oracle export performed to tape.
This schedule is good enough for a small system landscape with an orgnanization. If the landscape is huge, then you need to re-think about how backup is done. An integration with Oracle RMAN is good for running incremental backup. This will reduce the number of media needed for running daily full online backup - storage optimization
--------------------------------
Authorization data administrator
Authorization profile administrator
User administrator
System administrator
Database administrator
Customizing project member
ABAP developer
Workplace end user
-----------------------------------
SAP gives you standard Basis role :
SAP_BC_BASIS_ADMIN
SAP_BC_DB_ADMIN or SAP_BC_DB_ADMIN_ORA if you are using Oracle
SAP_BC_CLIENTCOPY
SAP_BC_BATCH_ADMIN
SAP_BC_TRANSPORT_ADMINISTRATOR
SAP_BC_SPOOL_ADMIN
copy that to ZSAP_BC_BASIS_ADMIN, ZSAP_BC_DB_ADMIN, ZSAP_BC_DB_ADMIN_ORA, etc. then modify that Zrole if you need to add or remove tcode and/or authorization objects. and finally assign to your consultant username.
but you have to monitor your consultant for what they did on your production server using STAD.
----------------------
#grep MemTotal /proc/meminfo - Fiziksel Ram
#grep SwapTotal /proc/meminfo - swap
#df -k /tmp - /tmp dizinindeki boş disk
#df -k - Sistemdeki boş disk alanını
# cat /etc/issue - Linux’un versiyon ve distributionu
$ rpm -q package_name - Gerekli paketlerin kurulup kurulmadığını
# uname –r -Gerekli kernel versiyonu
kernel;
Parametre Değer Dosya
semmsl semmns semopm semmni 250 32000 100 128 /proc/sys/kernel/sem
shmall 2097152 /proc/sys/kernel/shmall
shmmax Fiziksel hafızanın yarısı (bytecinsinden) /proc/sys/kernel/shmmax
shmmni 4096 /proc/sys/kernel/shmmni
file-max 65536 /proc/sys/fs/file-max
ip_local_port_range 1024 65000 /proc/sys/net/ipv4 /ip_local_port_range
semmsl, semmns, semopm, semmni #/sbin/sysctl -a | grep sem
Bu komut semaphore parametrelerin değerlerini
sıralı bir şekilde listeler
shmall, shmmax,shmni #/sbin/sysctl -a | grep shm
file-max #/sbin/sysctl -a | grep file-max
ip_local_port_range #/sbin/sysctl -a|grep ip_local_port_range
------------------------
-- Herhangi bir text editor ile, /etc/sysctl.conf ya edit edin yada yaratın ve
aşağıdaki satırları ya ekleyin yada düzeltin:
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
/etc/sysctl.conf dosyasını değistirdiksen sonra, bu değerler sisteminizi reboot
ettikten sonra aktif hale gelecektir.
SUSE sistemleri için, aşağıdaki komutu sistemin reboot olduktan sonra
/etc/sysctl.conf dosyasını okuyabilmesi için giriniz
#/sbin/chkconfig boot.sysctl on
• dba sistem grubunun yaratılması
# groupadd dba
• oracle kullanıcısının yaratılması
#useradd –s /usr/bin/ksh –g dba –d /home/oracle –m oracle
Shell limitlerini artırmak için
-- Aşağıdaki satırları /etc/security/limits.conf dosyasına ekleyin:
oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 1024
oracle hard nofile 65536
mkdir –p /…/app/oracle/product/10.1.0
chown -R oracle:dba /…/app
root kullanıcısı olarak xhost + komutunu çalıştırın
# xhost +
# su - oracle
Xwindow uygulamasının açılıp açılamadığını kontrol etmek için
xclock yada xcalc uygulamalarını çalıştırın.
Red Hat:
# mount /mnt /cdrom
SUSE :
# mount /media/cdrom
---------------------------------------
abap/buffersize : Program Buffer Size
500MB 000 1500MB 000 kb
enque/table_size
16384 96MB 000
ipc/shm_psize_10
150MB 000 000 600MB 000 000
ipc/shm_psize_40 Size of shared memory segment
124MB 000 000 250MB 000 000 byte
RSPLSE
enque/table_size or abap/shared_objects_size_MB
You can check in transactions after executing your planning functions
1. SM12 : give table name RSPLS_S_LOCK
2. SHMA: give area name as CL_RSPLS_ENQ_AREA for table RSPLS_S_LOCK_SYNC
3. LC10 : for table LCA_GUID_STR
-----------------------------------------------
ALTER DATABASE DATAFILE 'F:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF' AUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITED;
table;
begin
dbms_stats.gather_table_stats(ownname=> 'SAPSR3', tabname=> 'Ztable', partname=> NULL);
end;
index;
begin
dbms_stats.gather_index_stats(ownname=> 'SAPSR3', indname=> 'Zindex', partname=> NULL);
end;
check;
Parameters: -u / -jid CHECK20090806083734 -c -f check
statistics;
Parameters: -u / -jid STATS20090806084249 -c -f stats -t ALL
brconnect -u / -jid STATS20090806084249 -c -f stats -t ALL
--------------------------------
RSORADLD
ora102
IF ora_release < 'ORA732'. "#EC PORTABLE
MESSAGE e524. "Check only availible for Oracle release > 7.3
SET SCREEN 0. LEAVE SCREEN.
ENDIF
http://stanford.edu/dept/itss/docs/oracle/10g/server.101/b10739/toc.htm
--------------------
tu02 initSID.SAP
al11
-----------------------------------------
ST04N: Database overview
