Scribd
Upload
14 views11 pages

Procedure Import Client

This document outlines the procedure for importing a client into a SAP system, including creating a backup client, setting the database to No Archivelog mode, and executing the import process. It details the steps for preparing files, logging into the ECC client, and performing post-import actions such as deleting specific users and changing the database back to Archivelog mode. The document emphasizes the importance of monitoring the job status and ensuring the database is properly configured before and after the import.

Uploaded by

ramesh bandari bandari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
14 views11 pages

Procedure Import Client

This document outlines the procedure for importing a client into a SAP system, including creating a backup client, setting the database to No Archivelog mode, and executing the import process. It details the steps for preparing files, logging into the ECC client, and performing post-import actions such as deleting specific users and changing the database back to Archivelog mode. The document emphasizes the importance of monitoring the job status and ensuring the database is properly configured before and after the import.

Uploaded by

ramesh bandari bandari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 11

Client Import

This procedure describes steps to follow in order to import a client in a SAP system.

Create backup client for 100


a. Client 600 is created
b. Import client 100 into 600

Schedule in background job


Change the password to master password, and check remote login  OK
We can check on SCC3 that the job is running

We should set the database to No Archivelog mode to avoid FS full during the client
copy
mrs-dv-00708:de1adm 2> sqlplus "/as sysdba"

SQL*Plus: Release 11.2.0.4.0 Production on Thu Jul 31 15:42:09 2014

Copyright (c) 1982, 2013, Oracle. All rights reserved.

Connected to an idle instance.

SQL> startup nomount;

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

ORACLE instance started.

Total System Global Area 1202630656 bytes

Fixed Size 2245792 bytes

Variable Size 603982688 bytes

Database Buffers 587202560 bytes

Redo Buffers 9199616 bytes

SQL> alter database mount;

Database altered.

SQL> alter database noarchivelog;

Database altered.

Import client
Put the provided files in the transport directories:
mrs-dx-00108:de1adm 73> pwd
/sapcd/ImportECC
mrs-dx-00108:de1adm 72> unzip CMA_client_300.zip
Archive: CMA_client_300.zip
inflating: KT01791.W73
inflating: KX01791.W73
inflating: RX01791.W73
inflating: RT01791.W73
mrs-dx-00108:de1adm 74> ls
CMA_client_300.zip KT01791.W73 KX01791.W73
RT01791.W73 RX01791.W73
mrs-dx-00108:de1adm 80> cp /sapcd/ImportECC/K*
/usr/sap/trans/cofiles
mrs-dx-00108:de1adm 81> cp /sapcd/ImportECC/R*
/usr/sap/trans/data
Logon ECC client 100

STMS > import overview > refresh the buffer to find exported requests →import Queue
of target

Client → start import.


The import has finished. but the our users were overwritten , Support users were created
after the import :

Connect using SAP* ( delete form the database ) and launch the post processing steps.

delete from SAPSR3.usr02 where bname = 'SAP*' and mandt = '100';

SCC7:
After the import of the client, our users are created.

Set the database to Archive log mode.

alter database archivelog;

check database status : DB02  OK

You might also like