Skip to Content
Author's profile photo Former Member

Error during patching of core components in NW7.3x

I had installed a NW7.31 and also an ECC6.0 EHP6 system, both on Oracle DB and while trying to patch the core components SAP_ABA, SAP_BASIS, PI_BASIS and SAP_BW, in the phase IMPORT_PROPER, i faced an error stating that some tables are missing. I tried to re-import the patches after re-setting the OCS queue but it again stopped in DDIC_ACTIVATION phase of SAP_BASIS component. Finally, i re-installed the system but there were some important post-installation, pre-patching steps that i performed which led to proper, hassle free patching.

NOTE : These steps need to be performed before you start the patch upgrades.

1) Read the central SAP Note 1597765, “Known problems with Support Packages in SAP NW 7.31 AS ABAP” and implemented the other notes that were mentioned in the central note

2) Added parameter “_USE_ZERO_COPY_IO=FALSE “

          Steps to add the parameter to the database. In my case, the DB was Oracle.

          a) Open init<DBSID>.ora file in Notepad

          b) Add parameter into the file, as 


                   Note : The parameter should be mentioned in Capitals.

          c) Save the file

          d) Shutdown Database

          e)Create sp file using p file by executing the following command in command prompt.


          f) Start Database

          g) Restart instance

          h) Delete OCS queue

                         Run OCS_RESET_QUEUE program in se37 tcode

                         Enter IV_TOOL as SPAM or SAINT, whichever is applicable and IV_FORCE as X and execute (F8)

           i) Run import again from the beginning

Thanks and Regards,

Satyam Poddar

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Divyanshu Srivastava
      Divyanshu Srivastava

      Hi Satyam,

      Why did you use _use_zero_copy_io parameter.

      I think  this internal parameter should not be changed until recommended by SAP or Oracle.



      Author's profile photo Olivier BOULET
      Olivier BOULET

      He is true, there is a specific OSS note about that parameter. you can set hidden parameter if there is an SAP recommendation (and there are many...)

      By the way you can set directly into SPFILE without going through pfile, just bounce back the DB after setting it up.

      alter system set "_USE_ZERO_COPY_IO" = false scope = spfile  sid='*';

      Oracle client programs like SAP disp+work.exe or R3trans.exe can hang on insert into tables with SecureFile LOB columns if Oracle server is running on MS Windows.

      This parameter disables the enhanced communication protocol for SecureFile LOB columns and restart the database instance.

      On 7.31 do not forget to apply the two notes before using SPAM

      1680583 - Field names for tables and views with more than 16 char.

      1678047 - COMPUTE_INT_PLUS_OVERFLOW during activation

      Author's profile photo Former Member
      Former Member

      Hi Yves,

      You are right on the point that the parameter value can be changed directly in the SPFILE as well and it is imperative that we implement the notes you have mentioned.

      There are several other notes that one can refer to in the central note 1597765.



      Author's profile photo Former Member
      Former Member

      Hi Divyanshu,

      As per the Note 1635605 - CLIENT HANGS ON INSERT INTO TABLE WITH SECUREFILE LOB, it is recommended to change the parameter as a workaround. I tried implementing the note but could not as the system had gone in an inconsistent state after getting stuck at IMPORT_PROPER stage. Changing the parameter value and then re-starting the import solved the problem.