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.