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

Notes for Build Resilient Applications on SAP BTP with Amazon Web Services [ Week 1]

Welcome back to the next chapter in our ongoing series dedicated to unraveling the dynamic interplay between SAP Business Technology Platform (BTP) and Amazon Web Services (AWS). For those just joining us, this blog serves as an invaluable resource for individuals delving into the world of SAP BTP or seeking a comprehensive reference guide. SAP BTP, or SAP Business Technology Platform, is a comprehensive platform that brings together various essential capabilities for application development, automation, data management, analytics, planning, integration, and AI. These features are all integrated into a unified environment, making it user-friendly for both professional IT developers and citizen developers. Image Credit  Key Features of SAP BTP: Application Development: SAP BTP offers a range of tools for development. For instance, SAP Build enables low-code development, while the SAP Business Application Studio caters to core developers, providing services like document management a...
1 comment
Read more

8 Must-Know Questions About Object Store on SAP Business Technology Platform

What is the problem that Object Store solves ? Modern enterprise systems increasingly deal with massive volumes of unstructured data such as documents, logs, media files, and backups. Traditional relational databases are not optimized for such workloads. What is Object Store ? Object storage—commonly referred to as blob storage—addresses this gap by providing scalable, durable, and cost-efficient storage for unstructured data. Object storage is a storage architecture designed to manage unstructured data as discrete units called objects.  Each object consists of: Binary data (file content) : Image , File etc Metadata (descriptive attributes) : File size, Content type, Last modified timestamp, Storage class (hot, cool, archive) Unique identifier (key or URL) : unique path-like string used to locate a blob inside a bucket Unlike file systems or relational databases, object storage does not rely on hierarchical file structures or schemas. The SAP BTP Object Store service is a managed, ...
Post a Comment
Read more

Understanding SAP BTP Global Accounts, Directories, Subaccounts, and Entitlements

In SAP Business Technology Platform (BTP), organizing your resources effectively is crucial for efficient management and scalability. This blog provides a comprehensive overview of global accounts, directories, subaccounts, and entitlements within SAP BTP. What is a Global Account in SAP BTP? A global account in SAP BTP represents the contractual agreement you have with SAP. It serves as the top-level container for managing various resources, including directories, subaccounts, members, entitlements, and quotas. Within a global account, you receive entitlements and quotas for platform resources, which can be allocated to subaccounts for actual consumption. How Do Directories Function in SAP BTP? Directories in SAP BTP allow you to organize and manage your subaccounts based on your technical and business requirements. A directory can contain other directories and subaccounts, enabling you to create a hierarchical structure. This hierarchy can be up to 7 levels deep, with the global ac...
Post a Comment
Read more

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...
25 comments
Read more

KPIs for Recovery in HANA Database Administration

Introduction: In the dynamic landscape of database administration, ensuring the robustness of a system is paramount. One crucial aspect that demands meticulous attention is the recovery process following a system failure. Two key performance indicators (KPIs) stand out in this realm – Recovery Point Objective (RPO) and Recovery Time Objective (RTO) . In this technical blog, we will delve into the significance of these KPIs for HANA database administrators and explore strategies to optimize them. Recovery Point Objective (RPO): RPO is a critical metric that defines the maximum acceptable data loss in the event of a system failure . For HANA database administrators, establishing an RPO involves a careful balance between data consistency and the overhead of continuous data replication. Continuous Data Backups: To meet stringent RPO requirements, implementing continuous data backups is imperative. Utilizing HANA's native backup capabilities and integrating them with a robust backup s...
Post a Comment
Read more

Huge Multiversion Concurrency Control (MVCC) Versions in HANA

What is MVCC? MVCC is a database concurrency control method that allows multiple transactions to occur concurrently without conflicting with each other. In a nutshell, it ensures that each transaction sees a snapshot of the database at a specific point in time, even if other transactions are making changes concurrently. MVCC in SAP HANA: SAP HANA uses MVCC to manage concurrent access to data. Each transaction in HANA sees a consistent snapshot of the data at the time the transaction began. This is achieved by maintaining multiple versions of a data row, each associated with a specific transaction or point in time. The Issue of Huge MVCC Versions: Now, the term "Huge MVCC Versions" indicates a situation where there is a significant number of these versions for a particular set of data. Here's why this might become a problem: Increased Memory Usage: Each version of a data row consumes memory. As the number of versions increases, the overall memory consumption by the databas...
Post a Comment
Read more

Execute HANASitter for hang situation analysis

The SAP HANAsitter is configured to perform default checks once every hour to ascertain the online and primary status of SAP HANA. Upon confirmation, it initiates tracking procedures, which involve regular responsiveness assessments (typically every minute). If SAP HANA becomes unresponsive, the HANAsitter commences recording activities, potentially capturing call stacks of active threads, run-time dumps, index server gstacks, and/or kernel profiler traces, although, by default, no recording occurs. When SAP HANA is responsive, the script scrutinizes critical features, including a standard check for more than 30 active threads. If this threshold is exceeded, the script triggers recording. Upon completing the recording process, the script exits, with an option to be configured for restart using the command line. Setup Steps Overview: Begin by creating an SAP HANA user with the desired name (e.g., HANASITTER) and assign the CATALOG READ privilege to it. Establish a user key in the hdbuse...
Post a Comment
Read more

Deploying SAP on Google Cloud : Part 1

 Connect to Google  Connection Method To be Used for Speed Explanation Example Uses Cloud VPN Proof of Concept Variable, up to 3 Gbps Connects on-premises network to Google Cloud securely over the internet using IPsec VPN tunnels. Creating a Cloud VPN tunnel between on-premises and Google Cloud. Encrypted IPsec tunnels Dedicated Interconnect For Enterprise level connect 10 Gbps to 100 Gbps Provides a dedicated, private connection between on-premises and Google Cloud through Google's network. Provisioning a dedicated interconnect connection. Direct physical connection between on-premises and Google Cloud network infrastructure Partner Connect If you have a data center which cannot be reached to Dedicated Google facility. Variable, up to 100 Gbps Allows connecting to Google Cloud through supported service providers. Establishing a connection with a supported service provider. Utilizes service provider's network infrastructure. Configure Tunnels with Google Cloud Platform IPsec
Post a Comment
Read more

Building the Foundation of the PO System: Architecture and some terminologies

1. Loosely Coupled and Tightly Coupled Services : Loosely Coupled Services : These services interact with each other with minimal dependencies. Changes in one service don't significantly impact others. Pros include flexibility, easier updates, and better scalability. A common example in PO is when a shipping service communicates with an inventory service. Changes in the inventory service won't necessarily disrupt shipping. Tightly Coupled Services : These services are interdependent, so changes in one service can affect others. While they might provide faster communication, they can be less flexible and harder to maintain. For example, tightly coupling an order processing service with a payment service means any change in payment could ripple to order processing. 2. SOA - Service-Oriented Architecture : SOA is an architectural approach where everything is treated as a service, encapsulating specific functionality. Service Orchestration Example (Banking Transaction) : Consider ...
2 comments
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...
7 comments
Read more