Skip to main content

Mastering System Copy : Incremental Table conversion

Let’s talk about Incremental Table conversion , a topic which is difficult for many people to understand . I have referred this document. 



Refer this: 


In the ever-evolving realm of database management, upgrading and restructuring tables can be a nerve-wracking experience for businesses. The downtime and operational disruptions often associated with these tasks can create significant challenges. However, there's a silver lining in the form of Incremental (table) Conversion (ICNV). It's an online restructuring method that enables businesses to minimize downtime and smoothly execute the upgrade process. In this blog post, we'll embark on a journey to explore the ICNV, understanding its core concepts and discovering how it can seamlessly integrate with the upgrade tool SUM.


Understanding ICNV in an Upgrade/Update:


Imagine being faced with a critical decision during the crucial PREP_CONFIGURATION/INITSUBST phase of an upgrade. Should you consider ICNV or not? This choice holds the key to efficiency in your upgrade process. Let's explore the two options available:


Do not consider ICNV at all:

This option follows the traditional approach of performing table conversion during downtime. While it's familiar territory, it may not be the most time-effective solution.


Calculate tables for ICNV:

By selecting this option, you open the door to a more innovative path. The ICNVINIT phase in SUM evaluates ICNV candidates and kickstarts successful candidates for further processing. It's like having a knowledgeable advisor by your side, guiding you through the process.


Managing ICNV with SUM: Navigating the Upgrade Journey


Once ICNV candidates have been identified, the SUM upgrade tool steps in, acting as your trusted companion. During the ICNVREQ phase, it prompts you to initiate the transaction ICNV, seamlessly transitioning from evaluation to execution. It's like having a supportive partner who encourages you to take that first step toward a more efficient upgrade.


Key Properties of ICNV: 


  • Minimal Downtime for Table Conversion:


  • Break and Restart without Loss of Work:


  • Long-Term Operation


Benefits of ICNV: 


The benefits of ICNV extend far beyond the technical realm. Let's explore the advantages it brings:


Reduced Downtime during Upgrades


Simpler Conversion Back to SAP Standard for Modified Tables


Conversion of Large Tables during Production Operation


So Let’s see how it is done 



Step 1: Initialization - Setting the Stage for Data Transfer


During the initialization phase, you lay the foundation for the upcoming data transfer process. Follow these steps:


  • Create the target table(s) for storing the converted data.


  • This involves defining the new structure and ensuring compatibility with the existing data.


  • Set up change recording.


  • Implement a mechanism to track modifications to the original data during the conversion process.


  • This allows for automatic synchronization of changes made to the original data during the conversion.


Choose 'Control->Initialize'.


This initiates the initialization process and prepares the table for productive conversion.



   



Step 2: Data Transfer - Migrating Data to the New Structure


The data transfer phase involves moving and converting data from the table with the old structure to the table with the new structure. Follow these steps:


Start the data transfer.


Choose 'Control->Data transfer->Start' to initiate the data transfer process.

The incremental conversion program automatically determines the number and type of background processes required and selects the tables to be processed.

Stop the data transfer (if necessary).


Choose 'Control->Stop everything' to halt the data transfer and terminate running processes.


Use this option when you need to pause the process temporarily or when all processes need to be stopped.

Optimize the data transfer (if needed).


Choose 'Control->Data transfer->Optimize' to evaluate the available background processes on valid servers.

The program determines the number of processes required based on ICNV requirements and schedules additional processes if necessary.

Limit resource requirements (optional).


Set the list of application servers where ICNV processes can execute using 'Edit->Options->Server selection'.

Define the maximum number of background processes allowed for ICNV using 'Edit->Options->Number of processes'.

Define exclusion times (optional).


Use 'Control->Exclusion times' to specify periods during which data transfer should be omitted for individual tables.

This provides further control over resource allocation and allows for prioritization of critical operations.


Step 3: Switch to the New Structure - Activating the Converted Data


The switch phase involves replacing the original table with the target table, making the converted data accessible. Follow these steps:


Lock the original table.


Prevent any further changes to the data in the original table.

Convert remaining data.


Ensure that all data not yet edited by the incremental conversion program is processed and converted.

Replace the virtual original table with the new target table.


Activate the new table definition and make it ready for use.

Reconstruct views based on the original table.


Adjust any views or dependent objects that were based on the original table to reflect the changes made during the conversion.


Step 4: Delete Entry - Finalizing the Conversion


The delete entry phase involves removing the old original data, logs, and locks, allowing modifications to the table in the R/3 Dictionary. Follow these steps:


Remove the table.


Delete the old original data, ensuring it is no longer accessible.

Clear logs and delete locks.


Remove any logs and locks associated with the table to complete the conversion process.


Notes:


1. If the incremental table conversion (ICNV) process has been initiated, it is important to note that conducting an R3LOAD homogeneous or heterogeneous system copy of SAP systems is not supported. Prior to utilizing R3LOAD, it is necessary to complete all ongoing table conversions.


2. The ICNV process employs database-specific methods that cannot be unloaded consistently by R3LOAD. Consequently, there is a potential risk of data loss if attempting to unload ICNV-related data using R3LOAD.


3. It is crucial to verify that no entries are displayed in the transaction ICNV. This ensures that there are no ongoing or pending ICNV processes that may impact system operations or subsequent actions related to table conversions.


Youtube Video to understand in detail


Conversion of tables within the cluster EDI40 is blocked by the tool


336496 - Incremental conversion of cluster tables (may have partial data loss )


1663715 - Selection of additional tables for incremental conversion


807229 - Incremental conversion fails due to activation errors
Labels:

Comments

  1. KrishnaPhilips11 September 2023 at 04:03

    It is a great website and has a nice article. I want to thank you. Good job! You guys do a great blog, custom erp company in chennai

    ReplyDelete

Post a Comment

You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with
23 comments
Read more

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/enUS/b3/903925c34a45e28a2861b59c3c5623/content.htm?no_cache=true How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need
Post a Comment
Read more

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe
3 comments
Read more

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : sap-perf.ca Let's discuss the WORKLOAD MONITOR By D
4 comments
Read more

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note
3 comments
Read more

Unlock the Power of SAP HANA Performance Optimization: A Comprehensive Guide for SAP Basis Administrators [Part 2 : Deep Dive ]

In SAP systems, the performance of the underlying database plays a crucial role in delivering a seamless user experience. SAP HANA, being an in-memory database, offers exceptional speed and agility. However, it's essential to monitor and troubleshoot potential performance bottlenecks to ensure optimal system performance. In this blog post, we will explore key areas to focus on when monitoring the SAP HANA database and provide examples of how to identify and address common performance issues. Threads : Threads in the SAP HANA database represent individual tasks that execute concurrently. Monitoring thread utilization helps identify any thread-related issues, such as high thread utilization or thread exhaustion. You can use the M_SERVICE_THREADS table to gather information about active threads and their status. For example, a high number of waiting threads may indicate resource contention or blocking situations that require investigation and optimization To retrieve  thread based on
Post a Comment
Read more

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set
7 comments
Read more

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.
1 comment
Read more

ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants. Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps. Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP. You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22 How to correct the error ? Hints are given for the keywords that may be used to search on the note system. Gather Information about the issue  Go to System > Status and Check the Basis SP level as well as info
Post a Comment
Read more

SAP application log tables: BALHDR (Application Log: Header Data) and BALDAT (Application Log: Detail Data)

  BALHDR (Application Log: Header Data): Usage : The BALHDR table stores the header information for application logs. It serves as a central repository for managing and organizing log entries. Example Data Stored: The table may contain entries for various system activities, such as error messages, warnings, or information logs generated during SAP transactions or custom programs. Columns Involved: LOGNUMBER: Unique log number assigned to each log entry. OBJECT: Identifies the object associated with the log entry (e.g., a program, transaction, or process). SUBOBJECT: Further categorizes the object. USERNAME: User ID of the person who created the log entry. TIME: Date and time when the log entry was created. ADD_OBJECT: Additional information or details related to the log entry. BALDAT (Application Log: Detail Data): Usage : The BALDAT table contains the detailed data for each log entry, linked to the corresponding entry in the BALHDR table. It stores the specific log details and me
Post a Comment
Read more