Note 888889

Note 888889 - Automatic checks for security notes using RSECNOTE

 

Summary

SymptomThe SAP EarlyWatch Alert report contains selected checks about "Security". Among other things, there is a check to determine whether or not selected and required security-relevant notes or HotNews have been implemented in the system. The report displays an overall status. An administrator uses the tool RSECNOTE to create the detailed evaluation of the required security-relevant notes in the system to be analyzed.

Note 1144998

Note 1144998 - Incorrect data for DataStores with option "Unique records"

 

Summary

Symptom
You activate data of a request in a DataStore object for which the option "only unique data records" has been selected.
The request to be activated contains deletion records (Delete/Reverse-Images) and change records (Before/After/New-Images) for a key.

The following symptoms may occur due to incorrect handling of deletion records:

• An inconsistent change log is updated. As a result, there are inconsistent records in the table of the active data when the request is deleted.

• Activation terminates with the error "Error during update of data records for data package [DP]".

• The deletion record is ignored, and this leads to incorrect records in the table of the active data.

Note 396647

Note 396647 - FAQ: V3 update: Questions and answers

Question 1
Update records are written to the SM13, although you do not use the extractors from the logistics cockpit (LBWE) at all.
Active datasources have been accidentally delivered in a PI patch.For that reason, extract structures are set to active in the logistics cockpit. Select transaction LBWE and deactivate the active structures. From now on, no additional records are written into SM13.
If the system displays update records for application 05 (QM) in transaction SM13, even though the structure is not active, see note 393306 for a solution.

Note 380078

Note 380078 - FAQ: BW delta queue (RSA7): Questions and answers

This note maintained here for my quick reference and for those dont have SAP Notes access :-)

Question 1:
What does the number in the 'Total' column in Transaction RSA7 mean?
Answer:
The 'Total' column displays the number of LUWs that were written in the delta queue and that have not yet been confirmed. The number includes the LUWs of the last delta request (for repeating a delta request) and the LUWs for the next delta request. An LUW only disappears from the RSA7 display when it has been transferred to the BW System and a new delta request has been received from the BW System.

Note 1407285 - Security hole in BEx tools

Note 1407285 - Security hole in BEx tools

 

Summary

SymptomThere is a security hole in BW 3.5 Frontend for SAP GUI 7.10 and BI 7.0 Frontend for SAP GUI 7.10 that allows operating system functions to be called. This means that the affected client PC may be controlled (depending on the rights of the corresponding user account). This error also allows you to access the affected PC remotely.
Other termsSecurity, BEx tools, BEx Web Application Designer (WAD), Query Designer, BEx Analyzer, Report Designer
Reason and PrerequisitesBW 3.5 Frontend for SAP GUI 7.10 and/or BI 7.0 Frontend for SAP GUI 7.10 is installed on the client PC.
Solution

Note 1418122 - Insufficient error handling in inbound processing

Note 1418122 - Insufficient error handling in inbound processing

 

Summary

SymptomDuring the inbound processing of a message, an error occurs. This error is to be transferred as a SOAP fault message in the response to the caller. If an error occurs during the setup of the SOAP fault message, the error is not transferred to the caller.
You have activated the inbound lock of the Integration Server. If a message package is transferred from cross-component business process management (ccBPM) to the Integration Server, this is not processed there, but no error is returned to ccBPM. As a result, ccBPM assumes that the messages have been processed successfully, which means that the messages are lost.
Reason and PrerequisitesThis problem is caused by an error in the source code.
SolutionImplement the correction instructions or import the
Support Package specified below.

Note 1520462 - Unauthorized call of operating system command

Note 1520462 - Unauthorized call of operating system command

 

Summary

SymptomA malicious user can execute an operating system command with a parameter string by calling a certain ABAP function because the function does not perform any authorization checks.
In SAP terminology, these calls are referred to as 'external programs' or 'external commands' (See Note 677435 also.).
Other termsExternal programs, external commands
Reason and PrerequisitesThis is caused by a design error.
A malicious user who is very familiar with SAP source code may recognize this security hole.

Note 1039393 - DATAPUMP creates corruptions in tables with LONG (RAW)

Note 1039393 - DATAPUMP creates corruptions in tables with LONG (RAW)

 

Summary

Symptom***********************************************************************
This note is issued as a Hot News. Check the note regularly for updates. Otherwise, you will not be aware of important changes regarding prerequisites, consequences and solutions. A new Hot News is not issued if a note is updated.
***********************************************************************
After you reorganize a table with a LONG or LONG RAW column using the Oracle Data Pump

• the dbv reports: "kdbchk: the amount of space used is not equal to block size"

• ora-01498 is reported when the table is accessed

• block corruptions in the relevant table are reported by R3Check (provided that this table is a cluster table)

Note 1603033 - Performance problem in Program RBDAPP01

Note 1603033 - Performance problem in Program RBDAPP01

 

Summary

SymptomPerformance Problem in the program RBDAPP01 in BDT objects
Other termsRBDAPP01 , LBUSSF00 , gt_tbz1
Reason and PrerequisitesDuring the inbound processing of idocs through program RBDAPP01 the BDT objects were called to get the business partner relationship details .
When reading the relationship details due to the improper handling of read statement in OBJAP_CHECK routine causes duplicate entries in the internal table resulting in the performance issue.
SolutionImplement the notes to resolve the issue

Note 719941

Note 719941 - CALL_FUNCTION_WAIT_ERROR in ALE environment

 

Summary

SymptomIf you have scheduled the RBDAPP01 program as background job and have maintained the relevant variant in an incorrect way, the system may issue an ABAP CALL_FUNCTION_WAIT_ERROR runtime error.
Other termsRFC, ALE, CALL_FUNCTION_WAIT_ERROR, RBDAPP01
Reason and PrerequisitesThe problem arises if the RBDAPP01 program is terminated before the responses of the sent asynchronous tasks are returned by the RFC server program.

Note 830576 - Parameter recommendations for Oracle 10g

Note 830576 - Parameter recommendations for Oracle 10g

 

Summary

SymptomThis note contains SAP's recommendations for the configuration of Oracle Database 10g.
Other terms
init.ora, SPFILE, server parameter file
Reason and PrerequisitesThis note contains SAP's recommendations for the optimal configuration of the Oracle database with Release 10g in SAP environments.

Parameter recommendations for Oracle Release 11.2 can be found in SAP Note 1431798.

Note 562388 - Runtime error "START_CALL_SICK"

Note 562388 - Runtime error "START_CALL_SICK"

 

Summary

SymptomThe following error appears in the syslog after you import one of the following kernels on Solaris machines with the operating system release 5.5.1:
"START_CALL_SICK" runtime error
Transaction termination SY 002 (inconsistency with the database:
Start transaction SICK.

The specified transaction returns the message: OS release SunOS 5.5.1 Generic_103640-29 sun4u is not supported with this kernel (45B)
Other termsSICK Solaris 5.5.1 START_CALL_SICK

Note 436685 - Blank screen when you first logon after system restart

Note 436685 - Blank screen when you first logon after system restart

Summary

SymptomWhen you first logon after restarting an SAP System, the a blank screen without menus is displayed instead of the usual logon screen (only icons for "Enter", "Create a new session", "Generate a shortcut on the desktop", "Customizing of local layout" are shown).
When you logon again, the normal logon screen appears.
Additional key wordsBEAD
Cause and prerequisitesThe internal consistency checks have detected an error in the system configuration. Until now, an error screen with an OK code message of the type "Inconsistency with database: start transaction SICK" was generated during the first login. This no longer happens (the reasons have not yet been clarified). Instead a blank screen appears.