Note: In normal situations for some technical reasons we should not lock users in source client. Eg: Production client. To avoid inconsistencies, the related tables are copied together with other tables. Note: Client copy tool generally uses minimum of 2-dialog work process even if you start in background. Question Why should we not transport the client data? Ans this is explained with the help of a scenario. In target system, we have set up clients whose data must not be affected.
The cross client data must not be imported into the system from outside, since the cross client data overwrites existing data so that customizing data of other clients in the target system no longer effects. Note:This authorization is related with client transports. This is the reason for locking this user in different environments.
Overwriting recording, no transports allocated. Restrictions Locked due to a client copy: This option is used while performing client copy, i. We use this option if we want to use the selected profile as default settings. Starting of copy process can be done in 2 ways. Either schedule it as a background job or start immediately. Note: In a live environment we schedule it as a background job only. Instead you can make a remote copy.
Never the less SAP continues to provide support for transport function. Therefore all text are lost in the target system, whose language exists only in target system but not in source system Steps 1 Log onto source system SCC8 2 Select a copy profile 3 Select a target system client. Note: Logon to source system in the source client with a user that has transport authorization. Thus the client transport is done. This is how local client transport is done.
Error Handling Client copies usually involve large volumes of data which places strain on CPU and storage resources of a machine. Depending on data involved and system configuration the most likely errors are given below with corrections.
Error handling in client copy and transport Error Cause Solution Remarks Write Error in Usually a table Check system log target Client space overflow to determine the problem. Extend table space and repeat entire copy process. If the written code listed is the backup is still running and you will need to wait till it ends.
By default archiving should be on. AL08, issue a system message that the system will be used in a few moments I. Go to SM02 II. Select the create option and enter the message into dialog box displayed III.
Set the expiration date and select save button These are steps to create system message b To turnoff archiving first shutdown SAP I. Type stopsap R3 III. When you receive a message instance stopped, check the system is down or not by typing ps —ef grep dw. There should be no entries visible for SID you have just stopped. Exit from SID adm V. Choose option f- archive mode VIII. Select option A toggle database log mode IX. After a few movements reply or type y once again to startup the instance XI.
The archive mode menu should now show that database log mode is off XII. Enter start SAP R , when message instance started is received check the instance is running or not by typing ps —ef grep dw and looking for SID that we have just restarted c Remove the system message if it is still valid 4 This step will be followed only UNIX OS only. Check if the process are still running by issuing a command ps —ef grep ml, mail server, if there are any process running that particular process ID needs to be stopped IV.
Background JOB Administration: 1. We mainly use background work process for long running task called batch work processors 2. Background processing is used not only for long running tasks but also for recurring tasks Ex: daily database backup or financial accounting status A background jobs consist of one or more steps a An abap program b An external command c An external program Note: every job is processed without interruption by one single background work process.
Background job can be scheduled with different priorities I. Class A highest priority II. Class B medium priority III. SAP authorization concept only specifies whether a user can call external program or not. Start criteria for background job: A job can be triggered by the following options 1 By scheduling a job on a particular data at a particular time. A Unlike classical scheduling we cannot perform individual steps with different users.
Here we can monitor different status of background jobs Status of Jobs 1 Schedule: The steps of job have already been defined however start condition must still been defined 2 Released: I. The job has been define completely defined including the start condition II. A job cannot be released without a start condition III. Only a relevant authorized user can release a job 3 Ready: the start condition of a released job has been fulfilled.
A job scheduler has placed job in the wait queue for a free background work process 4 Active: the job is currently being executed and cannot be released or changed 5 Finished: All steps of the jobs are successfully completed 6 Canceled: the job is terminated reasons for this are I. A job step is terminated with an error. Note: we can change a job status as long a job still has the status scheduled or released III. We can create a new job by copying an existing job by choosing JOB-copy Time Based Scheduling There are three options to execute a job.
Immediately 2. On a particular work day i. This means that workload is automatically distributed between the systems. The automatic selection option is being disabled in this case. Standard Jobs Standard jobs refer to background jobs that should run regularly in a production system.
After Event 2. After Job 3. Manually using SM64 2. Using an ABAP program 3. The reservation of work process for Class A jobs does not reserve any particular work process rather it ensures that a particular number of workprocess is always kept free.
By doing so, we have the option of reserving work process. It is possible to select a job group for a particular job. There are 2 options 1. By default, the job will be executed using the current user in which I have logged in. Enter a different user name if your job should not be performed using your own authorizations.
SU01 — Tcode to create users. TRFC ensures transaction like processing of steps that are originally defined. It also ensures that individual steps are processed in sequence. But the output on paper is always performed using same mechanism in two steps 1 A spool request is created 2 The spool request contains device independent print data and includes administrative info and the actual print data.
This procedure allows the user to display spool request before output. Local Printing: The spool workprocess and the OS spool are running on the same host machine. You can configure multiple spool work process for an SAP instance.
Remote Printing: With remote printing, spool work process and OS system spooler are running on different hosts. The access method for front-end printing is F.
Lock Printer in SAP system Output request for printers for which this indicator is selected are created but not transferred to the printer. Destination Host: This is used only for remote printing.
It represents the name of the host where OS system spooler is running. Host only for local printing and is calculated automatically from the spool server. This describes how output should appear on paper. Example: To perform an output on a page with letter format.
Ans Trans-Code SM51 and select the application server. Ans No. Only background and dialog work process can be modified. Q How to identify how many spool servers are available in your SAP system? Ans SM51 or SM66 and check for application server with at least one spool workprocess. Q How to make setting for an individual SAP user so that an output request is not created immediately for a spool request? Ans SU3 go to Default tab and ensure that output immediately option is not checked. Q How to find which printer is defined at OS level of your server?
Select the change button i. Device contribute step iii. Creating a remote printer: Procedure is same as local printer. Table space: One or more data files. Instance: Set of oracle background process and memory buffers form an instance. What happen when oracle instance is stored? Q: what is the size of oracle data block? What are the situations in which DBWO writes dirty blocks to disks? Ans: There 4 conditions: - When transaction is committed.
These are four predefined collections of online redo log files. Control files This file is used to start and operate database. What are the entries in co files?. It is recommended to store the files in three physically separated hard disk. This information is used during database recovery. After restart, the system performs automatic recovery. Hence online redo log files must be mirrored i.
Oracle Directory Structure in SAP In Unix all directories are present under one single tree, where as in windows all directories are present under separate drive letters.
Note: All previous versions till oracle 8i has saparch directory. Groups: 1. Note: Always assign database rates to users. Database Users: 1. Default user used by SAP to connect to database is system. Location of parameters and listener log files. Options: 1. Note: If you get an error message while calling BR tools then your version might be older.
Less than 4. Database Transaction Codes: 1. DB Schedule backups and other administrative jobs. DB To check the status and logs of all database operations. DB Overview of database system checks. Db View and maintain check conditions for database system check. DB Maintain Statistics. DB Configuration of Statistics 7. DB Database parameter overview with history. DB Table and index monitor 9.
ST Database performance monitor Ans: From Oracle 9. Starting of Database 1. Mount face: opens cofiles. Open: opens all data files and online redo log files.
Normal: Oracle waits till all users are disconnected from the database. All files are closed and database is dis mounted and instance is shutdown.
Transactional: Oracle waits till all open transactional to finish and then it disconnects users and shutdown database. Immedaite: No new connections and transaction are allowed. PMON ends all user sessions and performance roll back of any open transactions then only shutdown database. Abort: no new connection and transactional allowed. No roll back of open transactions. Users are disconnected and oracle processes are stopped.
Note: With all the above first three methods, database is shutdown in a consistent state and does not need recovery at next restart. Whereas user directory store trace files written on behalf of shadow process. A We have to perform a restore and recovery of Database. Q What are the causes for logical errors related to Database? A i Manually deleting parts of Database objects such as Rows in a table.
Q How do we verify Consistency of Oracle Database? A By performing by a logical data check. A To verify the tapes used for Database backup. Q What are the various Backup types?
Complete Backup is again divided into 2 Types 1 Full Backup:- After data backup an additional information , i. Catalog is Written into Cofile by Recovery Manager. A NO, Incremental Backup is useless. Q Why do we need to perform a preparatory run? It is recommended to perform preparatory run per one Backup cycle. Q What are the contents of tape lable after a tape is Initialized?
Q How do we verify Backups? A Verification of backups is of 2 types i Tape Verification: The files are restored file by file and compared with original files to verify if the backup is redable.
In Database instance management select option 2 to shutdown the database. In Database instance shutdown main menu select option 1 shutdown DB. Under options for shutting down the DB instance we have to choose option 1, that is close mode Default mode is immediate f.
Note: if the users are logged in to the SAP system then I cannot use immediate, normal, transactional modes, using abort mode will forcefully shutdown and will result to data loss hence never use this option so to be on the safest side always shutdown using normal mode. In each of these cases the time stamp is recorded that is data and time. Once the DB is up and running always check the status before performing any action. A It will show an error showing that SAP instance is running.
Please showdown first or use force option. Table space administration: 1. Oracle stores data in table spaces, each table space consists of one or more data files. Data files are plain files stored on local system 3. This index is used for faster access to table data and to enforce unique constrains. To meet the demand of large DB, DB designers creates partition tables and indexes.
An index segment in oracle DB used in SAP holds either all data for take that is not partitioned or all data for a partition of partitioned table.
Common table spaces: 1. Q If table space is full then what are the possibility to extend the table spaces? A Option 1: Add another data file to table space 2: Existing data file can be manually resized 3: Properties of existing data file can be changed to auto extendable Q What id the formula to increase the data files size? Q What will happen if max extents are reached? A ORA is the error forms extent reached.
If max extent is reaching it limits, then increase next extent. When extents are dripped they are marked as free and their blocks can be used by new extents, but adjacent blocks are not combined. Segment Sizes Next segment Size Max. The only disadvantage of LMTS is, always it checks for used and free space.
Increase the Table space: 1. Space management option 2 3. Extent table space option 1 4. Extend table space option 1 7. Enter 2 to select above example table Note: options for extension of table space a.
Last added file name b. Last added file size in MB c. New file to be added d. Size of the new file in MB f. Enter option 5 to change the size of new file in MB User administration II. The most common tickets 1.
First character should be there in the beginning. Steps to create User Accounts 1. Enter the user and press create button. It can contain an approval form. For example. Based on the region or department we assign the user groups. By default it will be Empty Parameter: By default based on the roles, parameter values are assigned. Eg: ESS roles i. Note: Always assign the role first and not the profile. Every role by default has its own system defined profile.
We can set the Role Validity from …. Authorization Field: Smallest unit against which a check should run. Authorization: An instance of an authorization object i. Authorization Profile: Contains instances Auth for different Auth objects.
Role: Is generated using profile generator PFCG and allows automatic generation of an authorization profile. Note: A role describes activities of a user. Need an account? Click here to sign up. Download Free PDF. Salvatore Scarrica. A short summary of this paper. Download Download PDF. Translate PDF. All rights reserved. No part of this documentation may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
SAP AG further does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP AG shall not be liable for any special, indirect, incidental, or consequential damages, including without limitation, lost revenues or lost profits, which may result from the use of these materials.
The information in this documentation is subject to change without notice and does not represent a commitment on the part of SAP AG in the future. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
All other products mentioned are trademarks or registered trademarks of their respective companies. SAP AG assumes no responsibility for errors or omissions in these materials. SAP AG1. This document describes the certification tests that have to be passed by a security product to receive the BC-SNC certificate. After installation and configuration, the test analyses the runtime behavior of the third party security software, simulating the behavior of SAP Software components that use the SNC layer.
Furthermore, the conformance to certain SAP-specific constraints on parameter values, token sizes and runtime behavior is verified.
Besides the functional test, GSSTEST simulates common configuration and usage errors caused by misspelled names for credential owners and for security context targets and logs the observed behavior into the output protocol. It is necessary that the hostnames of all these machines can be correctly resolved via DNS.
Watch the console output and trace files if required to verify the successful establishment of the connection to the database and the correct status o f the work and spool processes. If either of both types of these credentials are short-lived several hours or a few days , the procedure for automatic credentials refresh must be documented in the test report.
You only need it if the default credential cannot be used as an accepting credential. In this case, the target name is the name for the accepting credential. Examples of such options are: use of software- or hardware-based authentication, possibility to configure different cryptographic algorithms for confidentiality and integrity for SAP AG1. Although this will cause GSSTEST to abort prematurely, we need the resulting log file with the error messages that indicate the absence of valid credentials.
Verify the new settings after saving them; especially if the canonical names were actually created they are stored in the table USRACL. Activate the checkbox to enable SNC and select 'Max. Since in general the SNC names for the different application server in the same logon group will differ, the SNC name of the selected application server has to be provided by the message server at the time of login as well.
For this reason, you cannot define the SNC name in the dialog above and the field for it is grayed out. If the user was externally authenticated, the system will try to map your externally authenticated name to an account in the Web Application Server.
0コメント