1) The document describes the process of performing a homogeneous system copy in SAP using an online/offline database backup.
2) The key steps are preparing the target system, restoring the backup to the target, creating a control file script on the source, modifying and running it on the target, and recovering the database on the target.
3) The recovery process differs depending on whether the source was using archive logging and whether archives are available to make the target current.
Oracle RAC - Standard Edition, Enterprise Edition & One NodeLeighton Nelson
This document discusses different options for choosing between Oracle Real Application Clusters (RAC), Standard Edition (SE), and RAC One Node. It provides an overview of Oracle Clusterware and RAC architectures. Standard Edition RAC supports up to 4 sockets and requires ASM, while Enterprise Edition has more scalability and supports third-party clusterware. RAC One Node provides high availability with one database instance and supports server consolidation. The document compares features and considerations for each edition and provides examples of suitable scenarios.
The document provides an overview of various administration tasks in SAP including:
1. It describes SAP architecture and instances including central instances, database instances, dialog instances, and work processes.
2. It explains how to view active servers, work processes, users, and active users using transactions codes SM51, SM50, SM04, and AL08.
3. It discusses monitoring system logs using SM21 and viewing ABAP dumps using ST22.
4. It covers checking database size, tablespaces, and datafiles using DB02.
5. It summarizes client administration tasks like creating, copying locally/remotely, deleting, exporting, and importing clients using transactions codes SCC4, S
This document discusses SAP system copy methods and processes. It describes heterogeneous and homogeneous system copies when the operating system, database system, or both change. Methods covered include client export/import, database refresh, R3Load&Jload, IMIG, and third party tools. The document outlines the architecture and processes for ABAP and Java data export/import, including package and table splitting techniques used to optimize runtimes. Post migration testing activities are also listed.
Recently SAP R 3 certified candidates are in dilemma.
They are worried whether their present efforts will be in vain for their future career as consultant.
Reason SAP will not continue their services for SAP R 3 after 2025.
I have attended sessions & seen training videos of SAP S 4 HANA too.
In which they have clearly stated that SAP R 3 knowledge is must for SAP HANA Consultant.
I explain the same by simple example : "To get Heavy Motor Vehicle Licence, you have to get first Light Motor Vehicle Licence"
This document provides an overview of different SAP BASIS work processes including dialog, background, update, enqueue, message server, gateway and spool processes. It describes the key aspects of each type of work process such as how they are used, important profile parameters, monitoring transactions, log files and more. Standard background jobs and potential issues with background jobs are also summarized.
This document provides guidance on conducting SAP license audits and measuring SAP systems for licensing purposes. It describes the process of classifying users, measuring engines, consolidating results, and transferring data to SAP. The document also defines various contractual user types and explains how to use the License Administration Workbench tool to combine measurement data.
This document discusses using events to control SAP workflow. It provides examples of how to:
- Trigger a new workflow instance using an event
- Terminate a workitem using an event
- Wait for an external event to complete part of a workflow
- Configure different types of events such as HR, status management, and change documents
- Best practices for connecting workflows to SAP systems and processes using events
This document provides instructions for installing Introscope Version 7.1 in a SAP environment. It describes installing the Introscope Enterprise Manager, enabling SAP J2EE systems with Introscope agents, optionally installing the Introscope workstation, and enabling Duet ASP.NET applications. It also covers upgrading previous Introscope versions, installing environment performance agents, and configuring WebView with SAP NetWeaver.
This document provides an overview of various SAP administration topics and transaction codes. It begins with an explanation of SAP architecture including the application, middle, and operating system layers. It then covers SAP instances, active servers, work processes, user administration, system logs, ABAP dumps, database administration using transaction codes like DB02 and BRTOOLS, and other topics like transport management, backups, and alerts. Screenshots are included to illustrate many of the transaction codes and administration tasks.
The document provides information about setting up and running a payment release process in SAP. Key points include:
1. A payment release allows you to place a block on accounting line items, check them, and then release them for payment by running a payment release. This uses the SAP Workflow component.
2. The payment release process can be set for one, two, or three levels of approval depending on configuration. It determines who can authorize releases based on criteria like document type and amount.
3. Prerequisites for payment release include defining workflow variants, document types, payment blocks, release approval groups, and paths. These are configured in Customizing and linked to the workflow models.
4
The document discusses new features in SAP HANA SPS11, including enhanced monitoring of Smart Data Access (SDA) in the SAP HANA cockpit, new SDA adapters that allow access to additional data sources using SDI adapters, an SDA adapter for SAP MII, an SDA adapter for SPARK SQL, and performance tuning techniques for SDA. SDA allows accessing remote data in SAP HANA like local tables without moving the data.
BW Adjusting settings and monitoring data loadsLuc Vanrobays
The document discusses various settings related to loading data into SAP BW, including:
1) Monitoring and adjusting data package settings to address performance issues during data loads. Large numbers of data packages or large individual package sizes can slow loads.
2) Checking transfer parameter settings for data loads from source systems into BW to ensure they are optimized.
3) Ways to split large initial data loads into smaller parallel loads to improve performance, such as using selection criteria to restrict the data per package.
Table maintenance generator and its modificationsscribid.download
This document discusses the Table Maintenance Generator in SAP and modifications that can be made. The Table Maintenance Generator is used to create programs for maintaining custom tables. It allows non-technical users to add, edit, and delete records without access to transaction codes. Events can be added to add validation and other logic when records are maintained. Maintenance screens can also be modified to customize the interface seen by users.
This document provides an overview of various SAP Basis administration transactions, including:
- SM02 to send messages to users logged into specific clients
- SM01 to lock/unlock transaction codes temporarily
- SM28 to check for errors during the SAP installation
- SM59 to maintain remote function calls for system communication
- SLICENSE to install SAP license certificates
- SCC4 to maintain client characteristics across clients
It also describes transactions for monitoring system status, work processes, users, updates, locks, batches, logs, traces, performance, database parameters, jobs, and more. The document serves as a guide to key transactions for administering and overseeing an SAP system.
The R/3 architecture guarantees integration of modules through its basis system. The basis system provides the runtime environment and defines the architectural framework. The central interfaces are the presentation interface, database interface, and operating system interface. The presentation interface controls what is shown on screens. The database interface converts between SAP and database requirements. The dispatcher manages resource allocation to work processes, which handle individual requests. Background processes run jobs at scheduled times. The layers are presentation, application, and database, with the basis system integrating them.
Sap memory management ,workload and performance analysis.pptxsweta prakash sahoo
The document discusses SAP memory management and workload analysis. It describes how SAP uses memory and buffers, and how tools like ST03N and ST06 can be used to analyze workload, memory usage, and system performance. Key points covered include the different types of SAP buffers, how to tune buffer sizes, using ST02 for buffer management, and analyzing workload, transactions, memory usage, and hardware resources using ST03N and ST06.
Troubleshooting tips and tricks for Oracle Database Oct 2020Sandesh Rao
This talk presents 15 different tips and tricks using tools to better troubleshoot and debug problems with Database , Oracle RAC and Oracle Clusterware , ASM and how to get the right pieces of data with the least of commands which today most people do manually. This session will cover tools from the Oracle Autonomous Health Framework (AHF) like Trace file Analyzer (TFA) to collect , organize and analyze log data , Exachk and orachk to perform mass best practices analysis and automation , Cluster Health Advisor to debug node evictions and calibrate the framework , OSWatcher and its analysis engine , oratop for pinpointing performance issues and many others to make one feel like a rockstar DBA.
SAP Basis Training Material | www.sapdocs.infosapdocs. info
You can download this material from http://sapdocs.info/sap/basis/download-sap-basis-training-material-pdf-book/
Get more SAP Downloads from http://sapdocs.info/
SAP Solution Manager is a central platform for implementing, operating, monitoring, and supporting SAP solutions. It provides tools, content, and access to SAP services to optimize management of SAP solutions, ensure reliability, efficient operations, ease implementation and upgrades, and enable continuous improvement. Key benefits include more reliable IT solutions, reduced costs of implementation and operations, and faster return on investment. It supports the Accelerated SAP methodology and features such as solution monitoring, a service desk, and change request management to help manage the productive environment.
This document provides instructions for installing SAP HANA software using the SAP HANA unified installer. It includes information on software components, download locations, important SAP notes, hardware and software requirements, and the installation process. The installation involves preparing the system environment, running the installer, and post-installation configuration such as starting and stopping the database, backup, security settings, and automatic startup configuration.
This document provides an overview of the SAP system and its key components. It discusses the enterprise structure in SAP which includes the highest level organizational units like company and company code. It also describes other important organizational units like sales organization, distribution channel, and division. The document explains the relationships between these different organizational units. Furthermore, it provides an introduction to master data in SAP including organizational data, customer and material master data, and document master data. It also discusses some important transaction codes and customizing tools in SAP.
SAP SD Interview Questions with Explanation Nbhati123
This document contains 75 interview questions for the SAP SD module. It begins with an introduction and table of contents. It then provides the questions, answers, and explanations for each interview question. The questions cover a wide range of SD topics including sales documents, pricing, delivery, billing, master data, and more. The document aims to help screen resources and assess their true understanding of SAP SD.
This document provides an overview of customizing settings in SAP across various modules including general settings, enterprise structure, logistics, sales and distribution, and material management. It outlines key configuration areas such as defining countries, currencies, calendars, material and plant masters, business partners, sales documents, billing, and consumption-based planning. The document contains over 340 pages detailing configuration tables and steps for setting up and assigning master and transactional data in SAP.
The document provides an overview of SAP and the implementation process. It introduces SAP as an enterprise resource planning software and discusses its architecture and modules. It then describes the roles of functional consultants, implementation partners, and company representatives in a typical SAP implementation project. The implementation process involves an AS-IS study, SHOULD-BE study, gap analysis, and business blueprints to configure SAP according to client requirements. Different server environments are used for development, testing, and production.
SAP MM Configuration Step by Step guide by Tata Mcgraw hillVenet Dheer
The document discusses the history of chocolate, from its origins in Mesoamerica to its popularity in Europe. It details how the Maya and Aztecs cultivated the cocoa bean and used it in drinks. The Spanish conquest brought cocoa and chocolate drinks to Europe, where they became a trend among the elite before mass production made chocolate accessible to the public. The document provides context on chocolate's transition from a luxury good to a global commodity.
SAP MM Configuration - Real Project Documentationsapdocs. info
Step by step configuration procedures for SAP MM module.. Screenshots, menu paths and descriptions provided
http://sapdocs.info/sap/materials-management-2/sap-mm-configuration-a-real-life-project-documentation/
Sap MM-configuration-step-by-step-guideVenet Dheer
The document outlines the detailed configuration steps taken to set up the SAP system for ITZ according to their business requirements, including defining plants, storage locations, purchasing organizations, assigning these to company codes, and configuring materials management, purchasing, inventory, and other logistics areas. Fields are assigned to selection groups and screens. Material types, numbers, texts and other attributes are defined.
This document provides an overview of different system and client copy methods available in SAP environments. It describes homogeneous system copies as copies between the same platform, and heterogeneous system copies as copies between different platforms. The main methods of performing system copies are using database backup/restore tools or SAP-provided tools like SAPInst. Client copies can be local within a system or remote between systems. Various profiles used in client copies are also outlined.
This document discusses various methods for performing database backups, including Recovery Manager (RMAN), Oracle Secure Backup, and user-managed backups. It covers key backup concepts like full versus incremental backups, online versus offline backups, and image copies versus backup sets. The document also provides instructions on configuring backup settings and scheduling automated database backups using RMAN and Enterprise Manager.
1. The document provides procedures for backing up a production server, including cloning the production server to create a backup server and daily and monthly backup procedures.
2. Key steps in cloning the production server include shutting down databases and applications, copying files to the backup server, and running scripts to configure the database and applications.
3. Daily backups involve making copies of updated database files from the production server to the backup server and reconfiguring the database. Monthly backups also update applications if any patches were applied.
The document outlines best practices for routinely backing up a production server to ensure data is not lost by maintaining a cloned backup server and regularly updating databases and applications.
This document provides instructions for installing Oracle Database Client 12c on Oracle Solaris on x86-64 systems. It describes reviewing requirements, configuring the system, installing necessary packages and patches, and performing the installation. Key steps include verifying the operating system release and packages, configuring sufficient disk space, memory and swap space, and installing required drivers before installing the Oracle Database Client software.
This document provides instructions for quickly installing Oracle Database Client 12c on Oracle Solaris on SPARC (64-bit) systems. It reviews requirements such as verifying the operating system packages and patches, configuring users and directories, and describes the installation process which includes mounting the product disc and running the Oracle Universal Installer. It also provides additional resources for more detailed installation instructions.
Percona Xtrabackup provides fully open-source, high-performance, non-blocking backups for MySQL databases. It can create full or incremental backups of InnoDB or MyISAM tables with features like parallel backups, compression, point-in-time recovery, and streaming backups. The backups can be applied using the innobackupex command line tool to restore databases efficiently.
This document discusses backup and recovery strategies for databases using Oracle Recovery Manager (RMAN). It recommends maintaining redundancy through techniques like RAID and mirroring to prevent the need for recovery. It emphasizes the importance of keeping the redundancy set that is needed for recovery on separate disks from the primary database files. It also stresses the need for frequent, redundant backups of archived redo logs to enable recovery to any point in time.
The document provides an introduction to Oracle Data Guard and high availability concepts. It discusses how Data Guard maintains standby databases to protect primary database data from failures, disasters, and errors. It describes different types of standby databases, including physical and logical standby databases, and how redo logs are applied from the primary database to keep the standbys synchronized. Real-time apply is also introduced, which allows for more up-to-date synchronization between databases with faster failover times.
This document outlines the steps to restore a production Oracle database to a development platform for testing purposes, including restoring file system directories, shutting down the development instance, restoring the server parameter file, control file, database files, and opening the database while resetting redo logs. It also discusses modifying memory parameters, building a new Oracle Enterprise Manager repository, dropping the copied database, and the importance of backup and recovery.
The document discusses database backup and recovery strategies in Oracle. It covers the different types of backups including logical, physical offline ("cold") backups, and physical online ("hot") backups. It also discusses archiving redo logs, testing backup strategies, and implications of backup methods like downtime required and recovery time. Failure scenarios like statement failure, user process failure, user error, instance failure, and media failure are also summarized. Finally, it discusses logical backups using the Oracle Export utility and parameters that can be passed to it.
Testing Delphix: easy data virtualizationFranck Pachot
The document summarizes the author's testing of the Delphix data virtualization software. Some key points:
- Delphix allows users to easily provision virtual copies of database sources on demand for tasks like testing, development, and disaster recovery.
- It works by maintaining incremental snapshots of source databases and virtualizing the data access. Copies can be provisioned in minutes and rewound to past points in time.
- The author demonstrated provisioning a copy of an Oracle database using Delphix and found the process very simple. Delphix integrates deeply with databases.
- Use cases include giving databases to each tester/developer, enabling continuous integration testing, creating QA environments with real
Shadow paging is a database recovery technique that uses two page tables - a current page table and a shadow page table. During transaction execution, updates are made to copies of pages in the shadow page table rather than directly updating pages. If a crash occurs, the database can be recovered by freeing the modified pages and using the unchanged shadow page table. Shadow paging reduces log overhead during recovery compared to log-based techniques but has disadvantages like increased data fragmentation and higher commit overhead.
This document discusses database backup and recovery strategies in Oracle. It covers different types of backups including logical, physical, online and offline backups. It emphasizes the importance of backups for recovery purposes. Different failure scenarios are described such as statement failure, user process failure, user error, instance failure and media failure. The roles of logical backups using Export and archiving redo logs are explained. Considerations for backup strategies include business needs, availability requirements, transaction volumes and read-only tablespaces. Testing backups is recommended to ensure recovery success.
This document provides release notes for Oracle9i Release 1 (9.0.1) for Linux Intel from June 2001. It outlines system requirements, kernel parameters, installation issues, and other product-related issues. Key topics covered include requirements for memory, swap space, disk space, processors, and software. It also provides minimum recommended kernel parameter settings for shared memory and semaphores.
The document discusses Unix kernel parameters that should be monitored and potentially increased after making changes to related Oracle Init.ora parameters. It provides a table matching Init.ora parameters like db_block_buffers and processes to Unix kernel parameters like shmmax and nproc. It also defines several common Unix kernel parameters and provides references on Unix configuration files where semaphores and shared memory can be set for different Unix platforms.
1. There are different levels of data recovery in SharePoint including content recovery, site recovery, and disaster recovery.
2. Content recovery involves using the recycle bin or versioning to recover documents, while site recovery recovers accidentally deleted or corrupted sites through site administrators.
3. Disaster recovery involves performing recoveries using built-in tools or external tools, and potentially migrating sites, databases, or farms to new hardware through farm administrators.
The document compares Oracle and SQL Server across several categories including performance, high availability, and new features in Oracle 11g. Key differences summarized are:
- Oracle supports real application clusters for high availability while SQL Server 2000/2005 do not support this type of clustering.
- Oracle Data Guard provides disaster recovery capabilities while SQL Server Database Mirroring has similar goals but differences in capabilities.
- New features in Oracle 11g include database replay, SQL performance analyzer, transparent tablespace encryption, flashback data archive, and SQL plan management.
Similar to 17398351 sap-system-copy-homcopyv1 (20)
UiPath Community Day Amsterdam: Code, Collaborate, ConnectUiPathCommunity
Welcome to our third live UiPath Community Day Amsterdam! Come join us for a half-day of networking and UiPath Platform deep-dives, for devs and non-devs alike, in the middle of summer ☀.
📕 Agenda:
12:30 Welcome Coffee/Light Lunch ☕
13:00 Event opening speech
Ebert Knol, Managing Partner, Tacstone Technology
Jonathan Smith, UiPath MVP, RPA Lead, Ciphix
Cristina Vidu, Senior Marketing Manager, UiPath Community EMEA
Dion Mes, Principal Sales Engineer, UiPath
13:15 ASML: RPA as Tactical Automation
Tactical robotic process automation for solving short-term challenges, while establishing standard and re-usable interfaces that fit IT's long-term goals and objectives.
Yannic Suurmeijer, System Architect, ASML
13:30 PostNL: an insight into RPA at PostNL
Showcasing the solutions our automations have provided, the challenges we’ve faced, and the best practices we’ve developed to support our logistics operations.
Leonard Renne, RPA Developer, PostNL
13:45 Break (30')
14:15 Breakout Sessions: Round 1
Modern Document Understanding in the cloud platform: AI-driven UiPath Document Understanding
Mike Bos, Senior Automation Developer, Tacstone Technology
Process Orchestration: scale up and have your Robots work in harmony
Jon Smith, UiPath MVP, RPA Lead, Ciphix
UiPath Integration Service: connect applications, leverage prebuilt connectors, and set up customer connectors
Johans Brink, CTO, MvR digital workforce
15:00 Breakout Sessions: Round 2
Automation, and GenAI: practical use cases for value generation
Thomas Janssen, UiPath MVP, Senior Automation Developer, Automation Heroes
Human in the Loop/Action Center
Dion Mes, Principal Sales Engineer @UiPath
Improving development with coded workflows
Idris Janszen, Technical Consultant, Ilionx
15:45 End remarks
16:00 Community fun games, sharing knowledge, drinks, and bites 🍻
Retrieval Augmented Generation Evaluation with RagasZilliz
Retrieval Augmented Generation (RAG) enhances chatbots by incorporating custom data in the prompt. Using large language models (LLMs) as judge has gained prominence in modern RAG systems. This talk will demo Ragas, an open-source automation tool for RAG evaluations. Christy will talk about and demo evaluating a RAG pipeline using Milvus and RAG metrics like context F1-score and answer correctness.
The History of Embeddings & Multimodal EmbeddingsZilliz
Frank Liu will walk through the history of embeddings and how we got to the cool embedding models used today. He'll end with a demo on how multimodal RAG is used.
It's your unstructured data: How to get your GenAI app to production (and spe...Zilliz
So you've successfully built a GenAI app POC for your company -- now comes the hard part: bringing it to production. Aparavi addresses the challenges of AI projects while addressing data privacy and PII. Our Service for RAG helps AI developers and data scientists to scale their app to 1000s to millions of users using corporate unstructured data. Aparavi’s AI Data Loader cleans, prepares and then loads only the relevant unstructured data for each AI project/app, enabling you to operationalize the creation of GenAI apps easily and accurately while giving you the time to focus on what you really want to do - building a great AI application with useful and relevant context. All within your environment and never having to share private corporate data with anyone - not even Aparavi.
Keynote : AI & Future Of Offensive SecurityPriyanka Aash
In the presentation, the focus is on the transformative impact of artificial intelligence (AI) in cybersecurity, particularly in the context of malware generation and adversarial attacks. AI promises to revolutionize the field by enabling scalable solutions to historically challenging problems such as continuous threat simulation, autonomous attack path generation, and the creation of sophisticated attack payloads. The discussions underscore how AI-powered tools like AI-based penetration testing can outpace traditional methods, enhancing security posture by efficiently identifying and mitigating vulnerabilities across complex attack surfaces. The use of AI in red teaming further amplifies these capabilities, allowing organizations to validate security controls effectively against diverse adversarial scenarios. These advancements not only streamline testing processes but also bolster defense strategies, ensuring readiness against evolving cyber threats.
"Building Future-Ready Apps with .NET 8 and Azure Serverless Ecosystem", Stan...Fwdays
.NET 8 brought a lot of improvements for developers and maturity to the Azure serverless container ecosystem. So, this talk will cover these changes and explain how you can apply them to your projects. Another reason for this talk is the re-invention of Serverless from a DevOps perspective as a Platform Engineering trend with Backstage and the recent Radius project from Microsoft. So now is the perfect time to look at developer productivity tooling and serverless apps from Microsoft's perspective.
Welcome to Cyberbiosecurity. Because regular cybersecurity wasn't complicated...Snarky Security
How wonderful it is that in our modern age, every bit of our biological data can be digitized, stored, and potentially pilfered by cyber thieves! Isn't it just splendid to think that while scientists are busy pushing the boundaries of biotechnology, hackers could be plotting the next big bio-data heist? This delightful scenario is brought to you by the ever-expanding digital landscape of biology and biotechnology, where the integration of computer science, engineering, and data science transforms our understanding and manipulation of biological systems.
While the fusion of technology and biology offers immense benefits, it also necessitates a careful consideration of the ethical, security, and associated social implications. But let's be honest, in the grand scheme of things, what's a little risk compared to potential scientific achievements? After all, progress in biotechnology waits for no one, and we're just along for the ride in this thrilling, slightly terrifying, adventure.
So, as we continue to navigate this complex landscape, let's not forget the importance of robust data protection measures and collaborative international efforts to safeguard sensitive biological information. After all, what could possibly go wrong?
-------------------------
This document provides a comprehensive analysis of the security implications biological data use. The analysis explores various aspects of biological data security, including the vulnerabilities associated with data access, the potential for misuse by state and non-state actors, and the implications for national and transnational security. Key aspects considered include the impact of technological advancements on data security, the role of international policies in data governance, and the strategies for mitigating risks associated with unauthorized data access.
This view offers valuable insights for security professionals, policymakers, and industry leaders across various sectors, highlighting the importance of robust data protection measures and collaborative international efforts to safeguard sensitive biological information. The analysis serves as a crucial resource for understanding the complex dynamics at the intersection of biotechnology and security, providing actionable recommendations to enhance biosecurity in an digital and interconnected world.
The evolving landscape of biology and biotechnology, significantly influenced by advancements in computer science, engineering, and data science, is reshaping our understanding and manipulation of biological systems. The integration of these disciplines has led to the development of fields such as computational biology and synthetic biology, which utilize computational power and engineering principles to solve complex biological problems and innovate new biotechnological applications. This interdisciplinary approach has not only accelerated research and development but also introduced new capabilities such as gene editing and biomanufact
This PDF delves into the aspects of information security from a forensic perspective, focusing on privacy leaks. It provides insights into the methods and tools used in forensic investigations to uncover and mitigate privacy breaches in mobile and cloud environments.
DefCamp_2016_Chemerkin_Yury-publish.pdf - Presentation by Yury Chemerkin at DefCamp 2016 discussing mobile app vulnerabilities, data protection issues, and analysis of security levels across different types of mobile applications.
Self-Healing Test Automation Framework - HealeniumKnoldus Inc.
Revolutionize your test automation with Healenium's self-healing framework. Automate test maintenance, reduce flakes, and increase efficiency. Learn how to build a robust test automation foundation. Discover the power of self-healing tests. Transform your testing experience.
Top 12 AI Technology Trends For 2024.pdfMarrie Morris
Technology has become an irreplaceable component of our daily lives. The role of AI in technology revolutionizes our lives for the betterment of the future. In this article, we will learn about the top 12 AI technology trends for 2024.
Increase Quality with User Access Policies - July 2024Peter Caitens
⭐️ Increase Quality with User Access Policies ⭐️, presented by Peter Caitens and Adam Best of Salesforce. View the slides from this session to hear all about “User Access Policies” and how they can help you onboard users faster with greater quality.
Increase Quality with User Access Policies - July 2024
17398351 sap-system-copy-homcopyv1
1. Type Handbook Document
Area SAP Basis
Topic Homogeneous System Copy using Online/Offline Database Backup
Author Huseyin Bilgen
System Copy Guides
Volume 1
Homogeneous System Copy using Online/Offline
Database Backup
By
basisconsultant.com
All Rights Reserved.
Copyright 2001-2003.basisconsultant.com Page 1 of 9
2. Type Handbook Document
Area SAP Basis
Topic Homogeneous System Copy using Online/Offline Database Backup
Author Huseyin Bilgen
Reasons for Copying a SAP System
SAP recommends that you make a system copy in order to build a test, demo, training or standby
system (Oracle and Informix: standby systems cannot be created with a system copy). You should
perform upgrades in a test system first. This way you can identify customer pecific problems which
might result from modifications. Thus, we can sort the general needs for a system copy as follow:
To create a new training system for end-user or project team education
To create a DEMO system
To create a Test system for upgrade or other purposes.
To recover a system on another machine with the same platform after a crash.
To copy large clients. If a client very large to export/import, it is better to do a system copy rather
than client transport.
If a system copy takes place between systems with same platform ( operating system and database
system ) , we call this HOMOGENEOUS SYSTEM COPY.
If The system copy takes place between systems with different platforms ( at least one of the
component must be different, OS or RDBMS ), we call this HETEROGENEOUS SYSTEM COPY.
There 3 ways of a Homogeneous System Copy in R/3 Systems.
1. Homogeneous System Copy using Online / Offline Database Backup.
2. Homogeneous System Copy using R3LOAD Procedure.
3. Homogeneous System Copy using R3COPY Procedure.
This guide is prepared for a Homogeneous System Copy using Online/Offline Database Backup.
The procedure described tested on AIX 4.3.3/Oracle 8.1.7, AIX 5.1/Oracle 8.1.7, AIX 5.1/Oracle 9.2.0
and Win2K/Oracle 8.1.7 platforms.
The command reference given in this guide is taken from a homogeneous system copy done on AIX
4.3.3/Oracle 8.1.7 platform. Differences of other platforms such as Windows will be shown in the same
sections.
Homogeneous System Copy using Online/Offline Database
Backup
This guide is prepared for a Homogeneous System Copy using Online/Offline Database Backup.
Steps for a Homogeneous system copy are briefly as below:
Preparations on Target System.
Restore Online/Offline Backup of Source System onto Target System.
Create CONTROLFILE creation script on Source System.
Modification of CONTROLFILE script and creation of CONTROLFILEs of Target System.
Recovery of Oracle Database on Target System.
Completion of System Copy
Prerequisites
Following conditions must be provided to copy a system:
Both Source and Target Systems must have Same Operating System and Database System. Also
Patch levels must be same.
You have sufficient free space for sapdata directories on target system.
For Windows systems, you have to create all drives where datafiles resides on source system.
Use most current database backup in order to shorten database creation time.
All Rights Reserved.
Copyright 2001-2003.basisconsultant.com Page 2 of 9
3. Type Handbook Document
Area SAP Basis
Topic Homogeneous System Copy using Online/Offline Database Backup
Author Huseyin Bilgen
Procedure
1. Data and Log directories on target system must be cleaned before restoring source database.
Here below are the commands to clean directories. Before this, you have to stop all SAP and
Oracle processes.
# su - <targetsid>adm
# stopsap all
# exit
# su – ora<targetsid>
# lsnrctl stop
# exit
# cd /oracle/<SID>/
# rm –rf sapdata?/*
# rm –rf origlog?/*
# rm –rf mirrlog?
# rm –rf sapreorg/*
# rm –rf saparch/*
# rm –rf saptrace/usertrace/*
# rm –rf saptrace/background/*
# rm –rf sapbackup/*
# rm –rf sapcheck/*
On Windows systems, SAP and Oracle services can be stopped via the following commandline
program after logging as <sid>adm:
ntscmgr stop SAP<SID>_<SYSNO>
ntscmgr stop SAPOSCOL
ntscmgr stop OracleService<SID>
2. You have to resize the following file systems before restore process. Take into account sizes of
source system.
/oracle/<SID>/sapdata1
/oracle/<SID>/sapdata2
/oracle/<SID>/sapdata3
/oracle/<SID>/sapdata4
/oracle/<SID>/sapdata5
/oracle/<SID>/sapdata6
/oracle/<SID>/saparch
3. After cleaning necessary file systems/directories, you have to restore most current database
backup to target system. For this, find the detail backup log (e.g. bdkxxsrh.anf) for that backup on
source system. You can determine this from back<SID>.log summary backup log file or using
DB12.
All Rights Reserved.
Copyright 2001-2003.basisconsultant.com Page 3 of 9
4. Type Handbook Document
Area SAP Basis
Topic Homogeneous System Copy using Online/Offline Database Backup
Author Huseyin Bilgen
DB12 - Backup Logs
back<SID>.log File
Copy this detailed backup log file into /oracle/<TSID>/sapbackup directory on target system. Use
BRRESTORE command below to restore the source database on target system. You can also
restore datafiles and online redolog files (if you are using offline backup) using backup tools such
as BACKFM tool of IBM TSM.
On Windows systems, while restoring source database on target system, you have to keep
same mount points for Oracle Data Directories.
For example if all of your source data directories resides on "d:>" disk
(d:oracle<SSID>sapdatax), then you have to create data dirs. at target system on "d:>" disk.
After restore process, you can change the directories. For example you can distribute sapdatax
directories on many disks. This will be mentioned in CONTROLFILE creation step later.
3.a. Mount the necessary backup volume on target system.
3.b. Use the following command to begin restore:
# su - ora<tsid>
# cd sapbackup
# brrestore -m full -b <det_log_file> -c (det_log_file= for example bdkxxsrh.anf)
At the first step of restore, system will recognize that the Oracle SID is different on target
machine (where the restore command executed) and in backup. Also, Oracle_Home
parameters in backup and in current system will be different and recognized by brrestore. But
the restore command will restore the datafiles to match current systems file system. Here is a
sample log of a restore.
All Rights Reserved.
Copyright 2001-2003.basisconsultant.com Page 4 of 9
5. Type Handbook Document
Area SAP Basis
Topic Homogeneous System Copy using Online/Offline Database Backup
Author Huseyin Bilgen
All the datafiles and online redolog files (only for Offline DB Backup) must be successfully
restored.
At this step, there are 3 probability that must be take into account for the following steps.
You are using an online database backup of source system to create target system.
You have to find and put all archive files created during online backup into target systems
archive directory to be able to recover database. You can also apply all the archives created
from the online backup start time to latest available.
You are using an offline database backup of source system which is running in
ARCHIVELOG mode to create target system.
You may find the archive files created after offline backup on source system to make database
current on target system via applying during recovery.
You are using an offline database backup of source system which is running in
NOARCHIVELOG mode to create target system.
You don't have any archive files created on source system so you don't need anything.
Those differences will be detailed in recovery step.
4. After restoring datafiles and redolog files, a scripts must be prepared on source system to create
CONTROLFILE of target system. For this you have 2 option.
4.a. You can use R3COPY program which is under "/kernel/UNIX/COMMON" directory of Kernel
CD. This program can be used only on UNIX systems. For Windows systems, "4.b" option
must be used.
Run this program by ora<sid> user on source system. After some confirmations, execute
step "(a) Source system: Generating the script CONTROL.SQL".
This will create a script named CONTROL.SQL under /oracle/<SSID>/sapreorg directory.
Copy this script into target system (any directory). This file is ready for execution and doesn't
require any modification.
4.b. SVRMGRL or SQLPLUS can create a scrpit to create controlfile using current
CONTROLFILE content. Login to source system as ora<sid> user and execute the following
SVRMGRL/SQLPLUS commands. To be able to execute following commands, database
must be at least in MOUNT mode..
All Rights Reserved.
Copyright 2001-2003.basisconsultant.com Page 5 of 9
6. Type Handbook Document
Area SAP Basis
Topic Homogeneous System Copy using Online/Offline Database Backup
Author Huseyin Bilgen
# svrmgrl
SVRMGR> connect internal
SVRMGR> alter database backup controlfile to trace;
SVRMGR> exit
As a result of this command, a trace file (e.g. ora_54764_hvd.trc ) will be created under
/oracle/<SSID>/saptace/usertrace directory. File can be determined by sorting according to
modification/creation dates (UNIX: # ls –ltr). Most current file must be cheched.
You have to edit this file to be able to use for CONTROLFILE creation on target system.
Rename file name as CONTROL.SQL
Open file to edit using VI (UNIX) or NOTEPAD (WIN).
Remove all lines before "STARTUP MOUNT" line. Delete all commented "#" lines. Also
remove all lines after CHARACTER SET WE8DEC;" line.
Change all Source SID's to Target SID via following commands.
UNIX (VI): :%s/<SSID>/<TSID>/g
WIN (NOTEPAD): CTRL+H
Change the line
CREATE CONTROLFILE REUSE DATABASE ‘SSID’ NORESETLOGS ARCHIVELOG;
as follow
CREATE CONTROLFILE REUSE SET DATABASE ‘TSID’ RESETLOGS ARCHIVELOG;
If you want to change datafile or redolog file destinations, first move the files on target
destination at OS level, then edit CONTROL.SQL file for new destinations.
If structural changes made in database on source system just after the backup restored on
target machine, differences will exists between datafiles in sapdata directories and datafiles
referenced in CONTROL.SQL file. Because CONTROL.SQL file is created for the current
status of source system, but later added files doen't exists in backup so in target system. To
overcome this problem, just delete the datafiles from CONTROL.SQL file.
If you don't know which files are created after the backup, let the problems arise during
CONTROLFILE creation command, and delete the files mentioned as error from
CONTROL.SQL and re-run creation command.
After deletion and successful creation of CONTROLFILE's on target system, you have to take
into account the following subjects:
If you are not going to recover database to the most current status using archive files, then
there is no problem.
But if you are planning to recover database to the most current status using archive files,
then deleted datafiles will be problem later while application of archive files. At this
moment, we offer you to keep datafile names you deleted during CONTROLFILE creation
and add those datafiles with the same sizes on source system after CONTROLFILE
creation.
5. After CONTROL.SQL script preparation, following commands must be run to create
CONTROLFILE of target system:
# su – ora<targetsid>
All Rights Reserved.
Copyright 2001-2003.basisconsultant.com Page 6 of 9
7. Type Handbook Document
Area SAP Basis
Topic Homogeneous System Copy using Online/Offline Database Backup
Author Huseyin Bilgen
# svrmgrl
SVRMGR> connect internal
SVRMGR> @/<path_to_file>/control.sql
You have to guarantee the successful completion of this command as follow:
SVRMGR> @control.sql
Statement processed.
SVRMGR>
6. Database will be in inconsistent status after creation of CONTROLFILE. This can be viewed by
trying to open the database.
SVRMGR> alter database open;
alter database open
*
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SVRMGR> alter database open resetlogs;
alter database open resetlogs
*
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/<hedefSID>/sapdata1/system_1/system.data1'
At this step, a recovery must be made in order to be able to use the database.
7. 3 type of recovery can be made, according to your status mentioned at the end of STEP-3. all the
recovery types must be used by "USING BACKUP CONTROLFILE" as CONTROLFILE is created
manually.
7.a. If your source system is runnig in NOARCHIVELOG mode, then you have to use the
following command to recover database.
SVRMGR> recover database using backup controlfile until cancel;
7.b. If you restored an online backup on target system and put all the archive files created since
online backup start time, use the following commands.
SVRMGR> recover database using backup controlfile;
After execution of this command, Oracle will ask for archive files to be consistent. As archive
files contains only database changes commands, you will use source system archive file on
new systems database recovery. Copy all archive files created since online backup on source
system to archive directory of target system. Archive file names are different from asked
during recovery session. You can change archive file names for target system via the
following script.
cd /oracle/<TSID>/saparch
for i in `ls|grep <SSID>`;
do
file_name=`echo $i |cut -dD -f2`;
mv $i <TSID>${file_name};
done
Alternatively you can enter file names manually as required by recovery session as follow:
SVRMGR> recover database using backup controlfile;
ORA-00279: change 44138924 generated at 03/26/2003 00:00:24 needed for thread 1
ORA-00289: suggestion : /oracle/HVS/saparch/HVSarch1_22746.dbf
All Rights Reserved.
Copyright 2001-2003.basisconsultant.com Page 7 of 9
8. Type Handbook Document
Area SAP Basis
Topic Homogeneous System Copy using Online/Offline Database Backup
Author Huseyin Bilgen
ORA-00280: change 44138924 for thread 1 is in sequence #22746
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/oracle/HVS/saparch/HVDarch1_22746.dbf
Log applied.
After application of all necessary archives (at least all the archives created during online
backup must be applied. Archives from this point can be applied to make database current),
next request for archive is cancelled via CANCEL command.
ORA-00279: change 44164157 generated at 03/26/2003 01:58:29 needed for thread 1
ORA-00289: suggestion : /oracle/HVS/saparch/HVSarch1_22754.dbf
ORA-00280: change 44164157 for thread 1 is in sequence #22754
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SVRMGR>
But recovery session must be started with the following command and cancelled again to ba
able to start database.
SVRMGR> recover database using backup controlfile until cancel;
ORA-00279: change 44164157 generated at 03/26/2003 01:58:29 needed for thread 1
ORA-00289: suggestion : /oracle/HVS/saparch/HVSarch1_22754.dbf
ORA-00280: change 44164157 for thread 1 is in sequence #22754
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SVRMGR>
Otherwise following error will arise during database opening.
SVRMGR> alter database open resetlogs;
alter database open resetlogs
*
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/oracle/HVS/sapdata1/system_1/system.data1'
To open database, use the following command:
SVRMGR> alter database open resetlogs;
Statement processed.
SVRMGR>
7.c. If you restored an offline backup on target system, you can recover database to the time of
backup completed or you can recover database to the most current status using archive files.
The archive application and statup of database is same as an online backed up database
copy in "7.b".
8. after opening database, LISTENER process must be started.
# su – ora<targetsid>
# lsnrctl start
On Windows systems, Oracle Listener is started as below:
ntscmgr start OracleOraHome817TNSListener
9. To open SAP system, use the following commands.
All Rights Reserved.
Copyright 2001-2003.basisconsultant.com Page 8 of 9
9. Type Handbook Document
Area SAP Basis
Topic Homogeneous System Copy using Online/Offline Database Backup
Author Huseyin Bilgen
# su - <targetsid>adm
# startsap
On Windows systems, Oracle Listener is started as below:
ntscmgr start SAP<SID>_<SYSNO>
ntscmgr start SAPOSCOL
ntscmgr start OracleService<SID>
startsap name=<TSID> nr=<SYSNO> SAPDIAHOST=<target systems hostname>
10. As your Hardware Key is not changed, you don't have to get additional License Key from
SAPNET. You can use previous systems (on target system, if SID is not changed) License in new
system created on target system.
11. Logon to the SAP R/3 System and goto TCODE SE06. Select "Database Copy or Migration" and
execute "Post Installation Processing".
SE06
Change all of the Source System Objects to Target System Objects as asked.
12. Delete old TMS configuration and make new configuration for TMS via STMS TCODE.
13. After all of above steps, you have completed a System Copy using Online/Offline Database
Backup.
All Rights Reserved.
Copyright 2001-2003.basisconsultant.com Page 9 of 9