SAP Basis
ORACLE Shared Pool Size
Note 690241 – The Shared SQL Area in the Shared Pool and large SQL Stmnts SPS = (cpus / 4 * 350 MB) + (cache / 1024 * 5) + 300 MB
Не работает st03
Не работает st03. Одна из возможных причин – неверно настроенная таймзона. Проблема описана в нотах: Note 926290 – SWNCCOLL: SAP workload NW collector collects no data Note 741734 – Incorrect times due to the time zone settings С помощью транзакции STZAC необходимо выставить правильную тайм-зону.
/sdf/rsoradld_new TIMEOUT and oracle dictionary statistics
We have long runtimes of the program /sdf/rsoradld_new during the data collection for the EarlyWatch Alert. This results in a timeout. Read Note 1247198 – /SDF/RSORADLD_NEW timeout In our case timeout occured on V$VIEW. Solution: Note 984955 – Timeout with selection of V$-Views Note 838725 – Oracle dictionary statistics and system statistics BRCONNECT command to create Oracle dictionary statistics: OS> brconnect -u / -c -f stats -t oradict_stats When you use this call, BRCONNECT internally calls the two procedures GATHER_DICTIONARY_STATS and GATHER_FIXEC_OBJECTS_STATS. Creating Oracle system statistics (NOWORKLOAD) using brconnect $ brconnect -u / -c -f stats -t system_stats Creating Oracle … Continue Reading
Unable to log on to system xxx in language yyy with user PIRWBUSER
After the initial setup I receive the error message “Unable to log on to system xxx in language yyy with user PIRWBUSER” in the Runtime Workbench (RWB). Why this? Answer: The logon language yyy is not activated in the ABAP system. Start transaction I18N and activate the language. Language activation is a separate post installation task that should have been executed before the CTC initial setup
AI_RUNTIME_JCOSERVER – Timeout while waiting for a connection to be established
Symptom In trace files dev_rfc* we have error: **** Trace file opened at 20120523 133135 MSK, by disp+work **** Versions SAP-REL 711,0,152 RFC-VER U 3 1297884 MT-SL ======> CPIC-CALL: ‘ThSAPOCMINIT’ : cmRc=27 thRc=677 Timeout while waiting for a connection to be established ABAP Programm: CL_MAPPING_XMS_PLSRV3=========CP (Transaction: ) User: PIAFUSER (Client: 001) Destination: AI_RUNTIME_JCOSERVER (handle: 1, , ) Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1730 CPIC-CALL: ‘ThSAPOCMINIT’ : cmRc=27 thRc=677 Timeout while waiting for a connection to be established DEST =AI_RUNTIME_JCOSERVER HOST =%%RFCSERVER%% PROG =AI_RUNTIME_SID Solution 1. How describe in this docs http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce601d35700783e10000000a42189d/frameset.htm Increase server count to 10 for AI_RUNTIME_JCOSERVER. 2. Note … Continue Reading
Размер файлов подробной статистики stat
Чтобы ограничить количество и общий размер файлов подробной статистики, используемой только в транзакции STAD, измените параметр профиля stat/max_files Note 6833 – Deleting statistics file, size of statistics file
IcfGetDTFromTaskHandler: ThEppGetRootContextIdAsXuuid failed with (98)!
Symptom In dev_w* files you get errors: IcfGetDTFromTaskHandler: ThEppGetRootContextIdAsXuuid failed with (98)! Solution: Implement the latest kernel for your release. The error will not occur with the latest kernel patch.
sm21 – Invalid parameter ObjTooLar transferred to database interface
При возникновении ошибки Invalid parameter ObjTooLar transferred to database interface в журнале sm21 следует обратиться к ноте Note 520684 – Runtime error “EXPORT_BUFFER_NO_MEMORY”
STMS Status of Importing Queue (Request Does Not Match Component Version)
With Version SAP_BASIS 702 a new feature was added to the TMS system, tp was checking the component version of the transport which was released and the component version of the system where the transport was going to be imported. If there was a difference, this difference was highlighted in the import queue (transaction stms_import) and if you tried to import the transport, the import would stop with a warning message about the difference in the SAPCOMPONENT versions. You have error import status “Request does not match component version”. Solution: Set STMS profile parameter : SP_TRANS_SYNC = OFF This can … Continue Reading
Минимальные требования для установки систем SAP
Минимальные требования к аппаратному обеспечению для установки систем SAP Для установки SAP ERP 2005 Сервер CPU min 2 x 3 ГГц RAM min 6 Гб HDD min 130ГБ LAN min Ethernet 100 Mbit/s Для установки SAP MDM 5.5 Сервер CPU min 2 x 3 ГГц RAM min 4 Гб HDD min 70ГБ LAN min Ethernet 100 Mbit/s Для установки SAP Netweaver 7.3 BW ABAP Сервер CPU min 2 x 3 ГГц RAM min 4 Гб HDD min 70ГБ LAN min Ethernet 100 Mbit/s Для установки SAP SAP Netweaver PI 7.1 Сервер CPU min 2 x 3 ГГц RAM min 8 … Continue Reading