Search
BWFreak - Journey to the center of Business Intelligence

Category: 'SAP General'

While checking the BW load today, I found one delta load was several hours late and was still running in the afternoon. It was doing one single query on TRFCQOUT table.
Checked execution plan, and found it was using a wrong index. Tried re-calculate table stats, index stats, and re-index.
The issue was solved by rebuilding indexes.
There’s [...]

Check sm37, jobs are “Cancelled”
All jobs scheduled in DB13 terminated during the initialization phase.
Check sm21

TemSe input/output to unopened file
Error 28 for write/read access to a file. File = /usr/sap/[SID]/SYS/global/

Check filesystem /usr/sap/[SID]/. There are still some space left, but can’t create new files using “cat > filename”, which indicates that I am running out of inodes.
Looks like [...]

Redwood Cronacle job chain connection error

Posted on March 29th, 2009

BW job chain in Redwood Cronacle failed with the following errors:
ORA-03113: end-of-file on communication channel
JCS-00215: in statement RSOJ_EXECUTE_JOB
ORA-03114: not connected to ORACLE
JCS-00215: in statement RSO_ROLLBACK
JCS-00371: attempting recovery of ORACLE error 3114 by reconnecting
JCS-00372: reconnection attempt 1 now commencing
JCS-00376: reconnection succeeded
ORA-20800: JCS-02263: failed to unlock script (code 4)
ORA-06512: at “SYSJCS.LCK”, line 152
ORA-06512: at “SYSJCS.JCS”, line 5794
ORA-06512: [...]

Delete session after error 061

Posted on March 16th, 2009

Error 061 (R47 / 061 syslog message)  is system log message.
It happens when SAP disconnects a frontend session caused by security program changes (firewall, anti-spyware, TuneUp, ncleaner, CCleaner, etc.)
, network issues (Windows TCP parameters), and other windows background activities.
The activities outside of SAP can cause slowness of the SAP fronend programs, as a result, the session’s response [...]

SAP crash due to signal 33 (AIX)

Posted on November 15th, 2008

Work processes received Signal 33
Message server stopped, gateway errors, oracle tried to roll back whatever database was doing and failed, and in st22, we got Run-time error “SYSTEM_NO_ROLL” 
This is caused by running out paging space.
Solution:
For 64 bit systems, SAP recommends at least 20GB swap area. Increased swap, the error never happened again.
See Note 1121904 – SAP on AIX: Recommendations [...]

The job SAP_COLLECTOR_FOR_NONE_R3_STAT is designed to collect non ABAP Statistic Data in/for a central repository.
If any errors, you can see errors from slg1.
Determination of component from SCR failed
Diagnosis
The system cannot determine the components for which the component collector is to be started. The cause is missing data in the CCMS System Component Repository (SCR). Either [...]

WF_LOG_XXXXXXX_[CLIENT] FILES

Posted on September 8th, 2008

WF_LOG files are under /sapmnt/<SID>/global directory. 
 They can be deleted using t-code, scheduled job or OS level.
T-code: SWU10 – delete obsolete workflow tracefiles
SM36 – program name – RSWTTR02
Old files can be deleted at OS level.
They are created if the trace is turned on for workflow processes. If no workflow on the system,  check to see whether [...]

Where to find Oracle parameter

Posted on August 12th, 2008

Use BRTools. 
$ORACLE_HOME/dbs/init[SID].ora and spfile[SID].ora
 T-code: st04 — top menu — goto — setup — parameter changes — active parameters
In sqlplus, for init parameters.
SHOW PARAMETERS
V$PARAMETER
For hidden parameters (use/change carefully!!)
SELECT X.KSPPINM NAME, DECODE(BITAND(KSPPIFLG/256, 1), 1, ‘TRUE’, ‘FALSE’) SESMOD, DECODE( BITAND(KSPPIFLG/65536, 3), 1, ‘IMMEDIATE’, 2, ‘DEFERRED’, 3, ‘IMMEDIATE’, ‘FALSE’ ) SYSMOD, KSPPDESC DESCRIPTION FROM SYS.X_$KSPPI X WHERE X.INST_ID = [...]

Learning OLTP side of SAP

Posted on June 15th, 2008

For the last several days, I got an opportunity to actively study what R3/ERP functionals do on OLTP side and how SD/MSD work.  Instead of infoObj, infoPackage and InfoCube… it’s t-code, program, and table.
I enjoy the process of trying to figure it out; I am happy that it helps me understand BW data and business process better… however, I can see it’s not [...]

TemSe and Spool

Posted on June 7th, 2008

TemSe: TemSe Data Store, for temporary sequential data; that is, objects that are not normally permanently held in the system are stored in the TemSe.
The spool system uses the TemSe to store output data temporarily. You can set whether the spool data is to be stored by TemSe in the SAP database or in the [...]