Transports steps after Homogeneous Copy

I'm planning to do a system copy in a few weeks time. I have done dummy runs and all is fine, but i'm unsure about the steps that are required for the transpors after the live copy.
The installation notes are very vague on this front. Is it just a case of running se06, or do I need to set up the transports domain again etc??
Thanks
Ian

You've probably already thought of this, but just as a reminder:
1) you'll have to log onto client 000 and request to be added back to the Transport domain, then activate the request on the Domain Controller (tcode stms)
2)Applied transport request level may be different between your QA & Prod. I usually down load the E070 table of QA before the refresh and compare it to the a download after the restore. Then manually add the transports to bring QA back to the transport level is was before the refresh. (May not be a concern in your landscape)

Similar Messages

Steps after sys copy

hi
ı have done homogenous sys copy
ı have 2 questions :
1-after system copy is it enough making changes using tcode scc4 for logical sys name and client roles ?
we dont use ale apps. should ı run bdls?
2- which option I should run sgen with ?
thsnks in advance

Hi
You need to perform all post system copy activites mentioned in the system copy guide @ http://service.sap.com/systemcopy
For logical system changes Refer
Change logical system names after system copy
Sgen : I would reccomend to select all components .
Regards,
Nibu Antony

Error in collecting transfer Rules in transport request after system copy

Hello,
Recently we had a system copy from Production to Test system.
We are trying to collect all the transfer rules from production in the transport request with the procedure which is given in the below link.
Re: Q: Transfer Rules after system copy
When we are trying to transport such objects, system first prompt for transportable workbench request, after specifying request once, it prompts for it again and after providing transport request number system results with message u201CSpecify a requestu201D.
Please suggest how to overcome this issue.

thats scary that you are copying your transfer rules from production to test system well if you guy sare doing it good luck..
a part from that make sure your prd is open so it allows items to be able to transport an dthere is a conenction between prd to test for transports to go through
if you have already copied all te data source to TEST, replicate them IN BWQ( your test system) then send over tranfer fules .
hope that helps.

Restoring clients after homogeneous copy

Hi...
I have a QAS system with three clients (100, 120 and 200).
I have a PRD system with just the client 100.
I was asked to perform an homogeneous copy from PRD to QAS, but to make sure clients 120 and 200 are not destroyed.
My question is:
Would a client export (SCC8) with profile SAP_RECO solve my problem?
I would first export both clients (120 and 200) with SAP_RECO, using the QAS system as the target, perform the copy, and then import the clients again through STMS. Would this work? Or is there any other way of doing this?
thanks
Antonio

Hi Antonio
If your are performing the system copy from PRD to QAS its will be comes only 100 client.
for this kindly follow the steps
1. Before starting the system copy Export the QAS client 120 & 200.
2. Perform the system copy from PRD to QAS, & Post system copy activitys
3. Create the New clients in QAS system
4. Do the Import which you already performed
BR
SS

Post processing steps after system copy

Hi experts,
Please clarify the doubts, reg my situation,
We don have our development server in synchronous with production server, so we destroyed the existing development client and copied the production client, now the new system logical name in sm30 in table T000 is MABCLNT900 and also our production server is same,as we copied it from production server, previously our development server was with MAACLNT495 which was mapped with MAQCLNT500 , R3 test sytem,
in this scenario we want run BDLS tool to change client name in both R3 and BW , Please explain step by step procedure in achieving this,
Thanks in advance

Hi,
As I understood your system landscape should look like this:
BW DEV (MAACLNT495) <-> R3 DEV (MAQCLNT500)
BW PRD (MABCLNT900) <-> R3 PRD (???)
After BW system copy you should change connections in SM59 and then use BDLS to change logical system name.
You can also use Restore function for source systems (RSA1).
Although if you copy both R/3 and BW systems at the same time it's possbile just to keep the same logical system names as they are in productive (it's easier to maintain).
Please read notes: 886102, 543715, 325470, 325525, 184322, 886102, 184971, 184447, ...
regards
Krzys

Steps for Homogeneous Copy Windows/MS SQL Server

Hi All,
I would like to get the steps/Procedure for performing a homogeneous system copy for a system that is sitting on Windows/SQL server. we have performed two upgrades on our current system and we have installed NetWeaver components.
what would be the best way of performing the system copy?
Could you please assist with the steps to follow and the documentation

Hi Juan,
how can you assist when the scenarios then change to the following
The configuration was carriedout on SAP version 4.7 during the 1st phase of the
implementation, using a temporary server which hosts the Dev, Prod and Database.
The 2nd phase which is coming up will involve the following activities:
   Installation of SAP ERP 2005 SR1 on the new servers (prod and Dev)
   Installation of SQL Server 2005 on the thir server
   Migration of the existing configuration data on SAP 4.7 to the new PROD and DEV
servers running SAP ERP 2005 SR1
what would be the best way to carryout this exercise?
1. install ERP 2005 and the with the help of the Functional consultants use the migration workbench
2. do a system copy, then upgrade the 4.7 to ECC 6.0

Is Recovery possible after homogeneous copy

Hi all,
my database is oracle 9i
1.I have 20 days old backup.using this backup I created a new system(by homogeneous system copy).Can I recover database using offline redolog files up to today date?
Thanks in advance
Regards
nani

yes it is possible, but you may need to rename your offline redologs so that it contains the SID.
20 days of redologs is a lot. hopefully, you have all offline redologs available and hopefully, you do not have any corrupted files...
it is better to take daily backups.

Post installation steps after SAP BW system copy

Hi!
I am about to do post processsing steps after system copy of SAP BW system.
1) One of the steps is to delete all entries from tables DBSTATHORA, DBSTAIHORA, DBSTATIORA,
DBSTATTORA.
Question: what is the way to do this?
2) During the installation I received the error within import ABAP step.
(IMP) INFO: import of D010TAB completed (4477754 rows) #20090505133631
DbSl Trace: Error 12801 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-12801 occurred when executing SQL stmt (parse error offset=0)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPSR3700 STORAGE (INITIAL 423090176 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS PARALLEL )
DbSlExecute: rc = 99
(SQL error 12801)
error message returned by DbSl:
ORA-12801: error signaled in parallel query server P000
ORA-01659: unable to allocate MINEXTENTS beyond 34 in tablespace PSAPSR3700
(DB) INFO: disconnected from DB
As solution I changed the the following lines within D010TAB.TSK:
from D010TAB~ 0 C err to D010TAB~0 C ign and
from D010TAB1 C err to D010TAB1 C ign
Question:
how to create index manually after system copy?
Thnak you very much!

Jgen Pfeiffer wrote:>
> Hi!
>
> I am about to do post processsing steps after system copy of SAP BW system.
>
> 1) One of the steps is to delete all entries from tables DBSTATHORA, DBSTAIHORA, DBSTATIORA,
> DBSTATTORA.
> Question: what is the way to do this?
Simply run
TRUNCATE TABLE <table_name>;
for each of those tables.
Make sure to either logon as SAP<SID> or provide the owner of the tables with the statement.
> 2) During the installation I received the error within import ABAP step.
> (IMP) INFO: import of D010TAB completed (4477754 rows) #20090505133631
> DbSl Trace: Error 12801 in exec_immediate() from oci_execute_stmt(), orpc=0
> DbSl Trace: ORA-12801 occurred when executing SQL stmt (parse error offset=0)
> (DB) ERROR: DDL statement failed
> (CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPSR3700 STORAGE (INITIAL 423090176 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS PARALLEL )
> DbSlExecute: rc = 99
> (SQL error 12801)
> error message returned by DbSl:
> ORA-12801: error signaled in parallel query server P000
> ORA-01659: unable to allocate MINEXTENTS beyond 34 in tablespace PSAPSR3700
> (DB) INFO: disconnected from DB
>
> As solution I changed the the following lines within D010TAB.TSK:
> from D010TAB~ 0 C err to D010TAB~0 C ign and
> from D010TAB1 C err to D010TAB1 C ign
>
> Question:
> how to create index manually after system copy?
The problem here was the large INITIAL size clause.
If there is enough freespace at all in the tablespace this should work:
CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPSR3700 NOLOGGING COMPUTE STATISTICS PARALLEL;
If I'm not wrong, the second index is just vice versa:
CREATE UNIQUE INDEX "D010TAB~1" ON "D010TAB" ( "TABNAME", "MASTER" ) TABLESPACE PSAPSR3700 NOLOGGING COMPUTE STATISTICS PARALLEL;
In general it is really not a good idea to skip the creation of unique indexes...
regards,
Lars

Inconsistant transport requests after local client copy

Dear experts,
our IT department just made a local client copy with profile SAP_ALL, by which all the transport requests had been copied, too, including quite a lot of workbench and customizing orders in status changeable. I'm supposed to do some basic setup and cleanup in the new client, but I'm confronted with problems like objects being locked in orders/requests that cannot be changed in the new client, as they belong to the original source client.
How can I get rid of those inconsistencies? I'd preferred the new client without transports and without locked objects. Is it really necessary that I clean up this mess manually? Would it have been better to clean this up before the client copy? Or could we just do the client copy with another profile in order to avoid those problems?
Thanks for your appreciated help
Andreas

Hello,
Transports are NEVER part of a client copy.
In fact all the data of your transports is stored in tables that are client independent (E07* tables).
This means that you can view (not edit) always all transports from all clients in a specific system.
When you want to edit or release a transport the source client is important (in which client was the transport originally created).
This is stored in table E070C for all transports and can not be overruled.
So I recommend that you don't clean anything related to transports after a client copy because this will also impact the other clients !
Success.
Wim

Problems Delta Extractor after Homogeneous Source System Copy

Hi,
We have R/3 system landscape HUD, HUQ, HUP. And we have BW system landscape BWD and BWP.
We connect BWD to HUQ and BWP to HUP.
We made a homogeneous system copy from HUP to HUQ.
We haven´t made any homogeneous system copy from BWP to BWD.
We have applied the next OSS note after source system copy:
325525 Copying and renaming systems in a BW environment
184322 Procedure after DB copy of BW source system
184754 Procedure after BW database copy.
But we have problems in our BW Development (BWD), and we have the next Dump "MESSAGE_TYPE_X" when we can change any delta infopacket, the next text are from Dump:
"MESSAGE_TYPE_X" C
"SAPLRSS1 " or "LRSS1F11 "
"RSM1_CHECK_FOR_DELTAUPD"
I think that the problem is about inconsistencies between RSSDLINIT/SEL tables in BW side and ROOSPRMSC/F tables in R/3 side.
Please could you tell how can i solve this Dump, because i can restrart and initial and delta packet for different Datasource and i can´t do anything.
Thanks in advanced,

Hi,
We are upgrading our R/3 system from 4.7 to Ecc 6.
While copying database tables we are using Clinet Carrier tool which is considering only clinet dependent tables. Hence we are loosing our BW delta queue entries in RSA7 of ugraded system.
We found ROOSPRMSC and ROOSPRMSF tables and copying these 2 tables may resolve the issue and We copied and delta went fine.But we are not sure of only these are the tables to be considered.
Please let us know what are the relevent tables to be considered to make the Delta to work while copying Data base tables from one system to another.
Thanks in Advance
Regards,
R@ngzz

Logical System Name after System Copy

Hello,
I have three questions about the logical system name after system copy.
Q1) When I change SID D22 to S11 during system copy,
do I have to change the logical system name of all clients in the target system? The target system is used for test, and the landscape has S11 and Virtial system. The target system S11 does not communicate with the source system D22.
Q2) If the answer for Q1 is YES, is it correct that the following procedure for changing logical system name?
1.Tr-CD:BD54
Add new logical system name for all clients in the target system.
2.Tr-CD:SCC4
As for all clients, select new logical system name with F4 help.
Q3) If the answer for Q1 is YES, do I have to add new RFC connection entries with SM59 for all clients in the target system?
I refer to the guide "Homogeneous and Heterogeneous
System Copy for SAP Systems Based
on SAP Web Application Server
ABAP 6.40 SR1".
thanks,
Keishi

Hi Keishi,
As a good and ideal practice the answer to your first question Q1 is yes. Infact I would say that in case you are using ALE then it is must
For Q2 there has to be an additional step which is most important one. Running BDLS transaction which would allow you to change logical systems in relevant tables from the one of source system to target system.
For Q3 the answer is agaain yes and you can have two approaches>
1. manually recreate all the RFC destinations after sys. copy.
2. Export all the RFC destination data relevant tables before system copy and then reimport them after sys. copy.
Regards.
Ruchit.

Livecache 7.5 homogeneous copy to already existing maxdb 7.5

I am trying to do homogeneous copy of scm4.1 system which has livecache into a system where maxdb 7.6(for content server) is already there. Can somebody suggest what changes are required for such situation.
original server:
dbmcli>version
OK
version,os,dbroot,logon,code,swap
"7.5.0","UNIX","/sapdb/TLX/db",True,ASCII,1

Hello Giridhara, Sorry for the delay.
A) As I understood after you run the last step (point 3) of the note 457425,
      you are able to connect to the liveCache with superdba user &
     in DBMGUI :: Instance -> Configuration -> Database Administrators,
     you could see now two users control & superdba.
After you run::
dbmcli -d <database_name> -u <dbm_user>,<password> load_systab -u <sysdba_user>,<password> -ud <domain_user_password>
( the loading system tables could be done, when livecache is in 'online'
Or 'warm' mode. )
=> the upc files were maintained with the superdba, domain users data.
=>
You will see 3 users with the command:
dbmcli -d <database_name> -u <dbm_user>,<password> user_getall
B) The SAPR3 user is the standard liveCache user, it's SQL user & you should be able to connect to the database using SQLStudio of dbmcli command::
      dbmcli -d <database_name> -u control,<password>
      <enter>
      dbmcli on <database_name> >sql_connect sapr3,<sapr3-pwd>
      <enter>
     dbmcli on <database_name> >sql_release
    dbmcli on <database_name> >exit
C) Please review the SAP note 877203.
D) "Brief description of the user types'" in database is available in the SAP note 25591
&& see the documentation at
http://maxdb.sap.com/currentdoc/default.htm -> Basic Information
-> Glossary -> User ->
< -> See also: Concepts of the Database System, Users, Authentication and Authorizations < -> Changing the Passwords of Standard Users > >
Thank you and best regards, Natalia Khlopina

HOMOGENEOUS COPY(Oracle procedure)

Hi All,
After completing homogeneous copy thru oracle procedure everything was fine ..
server was running fine but after restarting the server once it goes down.
do anyone know what steps we have to do after doing homogeneous copy??
do i need to upgrade or anything else?
Regards,
Rohit

Hi guys,
I m posting this answer little late ....After doing the homogeneous copy (oracle procedure) we have to run one script "ORADBUSR.SQL" ...my server is working fine now..it may helpful for someone else who will do homogeneous copy through oracle procedure...
Cheers!!!
Rohit

User password problem in RFC after system copy

HEllo,
we have a problem in ECC6.0 after system copy (refresh QUAL system by PRD data).
BEfore doing this copy, we export RFC data (SM59 tables) of our QUAL system and after the refresh we reimport these RFC in our QUAL system. We don't want RFC comming from productive system.
After this reimport, RFC configuration is ok but we have a problem with RFCuser password. In the password box we have "inconsistent"...
Have you an idea to reimport succesfully these informations ?
Thanks
lionel

Hello,
We performed another refresh yesterday. But unfortunatly it was not working. Password are still inconsistent.
This are exactly way we perform it:
Before restoring DB :
export table via R3trans for tables:
RFCDES, RFCDOC, RFCATTRIB, RFCCHECK, RFCDESSECU, RFCSYSACL, RFCTRUST, RFCCMC, RFCGO, SXRFC, IBSSI_RFCDEST, PARAMVALUE, RSECACTB where ident LIKE '___/RFC%'
export users via scc8
Restore DB, truncate upper rfc tables, import rfc Tables
Check SM59 => inconsistent
Migrate Secstore => still inconsistent
Import Users via transport generated by scc8
run scc7 as post actions
Tuncatate/re-import rfc tables
Check SM59 => inconsistent
Migrate Secstore => still inconsistent
What else could be done ?
We have a lot of RFC. so re-enter all password is really a hudge task ..
Thanks a lot for help

Which is better Remote Client Copy or Homogenous copy

Hi All
I have a task to synchronize the ECC Production server with devlopment server
For this I have two option :
1. Remote client copy from Production to Development
2. Implementing homogenous copy(oracle procedure) of production server and then remove the existing development server.
I want to know your expert view with which one should I go with, as I have seen many times that whenever I do remote client copy it gives error in test phase the following tables error. so I am not sure wherther I just go with clent copy or not.
What things should keep in mind before doing it before doing homogenous copy?
Thankx in Advance
Regards
Vinay Paul

Hi All
Is there any solution for below if I decide to go with Oracle Procedure of system copy. Because we have to provide this to one of our client as there production and Development server are out of Sink.
1. Retaining the development history
2. Retaining the transports history.
I came to know that the above thing is possible but I have no idea how.
Thankx in advance
Regards
Vinay Paul
Edited by: Vinay Paul on Jan 16, 2008 1:48 PM

Transports steps after Homogeneous Copy

Similar Messages

Maybe you are looking for