System Refresh regarding jobs

Hi,
I have a query regarding jobs. We refresh production to quality server. So this way all jobs also would be refreshed to quality from production. Now i will have all the jobs but i do not want same scheduling(as of production for my quality) and actually want the scheduling that was previously defined for my quality system jobs to be effective now after i have refreshed the system from production. So how i may do this? is there a way to take a backup of scheduling times of jobs before quality refresh so i can manitian same later having refreshed from production.
Also is there a way to completely restore the older (before refresh all jobs of quality) to quality again may this would help me to get my older scheduling?
Please let me know.
Regards,
Ashish Robinson
SAP BASIS Team
Edited by: Ashish V Robinson on Oct 5, 2011 7:43 AM

Hi Ashish,
When you are performing the system copy with PRD data.There are some pre-steps needs to taken care to avoid issues after building the target system with PRD data.
1.Disable communication between source systems ( sm59 )
2. Disable background job processing by running BTCTRNS1
3.Complete message processing in source landscape.
If your target system already exist in your landscape before going to perform the refresh with PRD data take secure information backup in your target system.
1.User master data
2.RFC tables backup.
3.Background jobs information and background job tables backup using transport of copies method.
If you follow above steps you won't face any difficulty after system copy with PRD data.
What you have to do is the secure information which you have taken in target system you need to import in your target system.
I hope it will help you.
Regards,
Kiran .V

Similar Messages

Backup of background jobs after system refresh

Hi All,
I want to know that during the system refresh how can we take the backup of the background jobs which are in "Released" state so that we can schedule them the same way after the refresh is done. Presently we are taking the screen shot of "start condition" and "step" of each and every job and then using those screenshots we are scheduling them again after the refresh is completed. It would be really helpful and time saving for us if we come to know the tables where this information is stored and also if there is any other easier way for this.
Regards,
Lovneesh

Hello,
Check the below thread. It mentions all the tables that contain batch job information.
https://scn.sap.com/thread/1709175
" Check below mentioned tables
BTCCTL,
BTCDELAY
BTCEVTJOB
BTCH1000
BTCH1010
TBTCO
TBTCP
These have all the information you need regarding background jobs, you may export these tables at the source and import them "
Check and provide feedback.
Regards,
Mudasir

Retain background jobs and its variants before system refresh activity

Hello All,
I am going to perform system refresh activity on quaity system on monday. Customer wants to retain the background jobs and its variants in the quality system. Please guide me and let me know the steps to retain the background jobs and its variants before starting the system refresh activity.
Regards
Subbu

Dear Subbu,
You have to export the TBT* Tables to retain the jobs. You can do this with R3trans:
1. Make Export file
2. Make Import file
3. Make Export in Q System before Systemcopy
4. Start Database and not SAP
5. Make Import in Q after Systemcopy
6. Start sap
1. Make Export file /tmp/export_cmd
export
file='/tmp/export_Q.dmp'
client=<your client>
delete from TBTCA
delete from TBTCB
delete from TBTCCNTXT
delete from TBTCCTXTT
delete from TBTCCTXTTP
delete from TBTCI
delete from TBTCJCNTXT
delete from TBTCJSTEP
delete from TBTCO
delete from TBTCO_V01
delete from TBTCP
delete from TBTCPV
delete from TBTCR
delete from TBTCS
delete from TBTC_SPOOLID
delete from BTCEVTJOB
select * from TBTCA
select * from TBTCB
select * from TBTCCNTXT
select * from TBTCCTXTT
select * from TBTCCTXTTP
select * from TBTCI
select * from TBTCJCNTXT
select * from TBTCJSTEP
select * from TBTCO
select * from TBTCO_V01
select * from TBTCP
select * from TBTCPV
select * from TBTCR
select * from TBTCS
select * from TBTC_SPOOLID
select * from BTCEVTJOB
2. Make Import file /tmp/import_cmd
import
file='/tmp/export_Q.dmp'
3. Make Export in Q System before Systemcopy
R3trans -w /tmp/Q_export.log /tmp/export_cmd
4. Start Database and not SAP
sqlplus "/as sysdba"
SQL> startup
or
startsap
stopsap r3
5. Make Import in Q after Systemcopy
R3trans -w /tmp/Q_import.log /tmp/import_cmd
If you want to undo this, start the export script in P system and the Import script in Q system.
Don't be afraid of the delete statement but without delete it doesn't work!
6. Start sap
startsap
Best regards
Willi Eimler

Restore periodic batch job after system refresh

Hi all
I am going to do a system refresh and is there anyway to restore my periodic batch jobs after the system refresh or i need to reschedule all of them manually.Thanks in advance.

You'll need to do them manually.
Regards
Juan

CUA - System Refresh

Hello,
I am new to CUA and need help in determining the pre and Post steps for CUA during the System Refresh. The System Refresh is performed on the Child System and after the Refresh my original users and Role assignments have to overwrite the users and Role Assignments of the Copying System.How do I retain my original User data ?
Are their any guidelines to this process ?
I am researching oss and forums,and so far I don't have any clear procedure.
thanks,
Farah

Hello Farah,
I think by system refresh you mean system copy.
From system copy perspective follwing steps need to be taken:
pre copy steps:
1. Disconnect CUA. Please go to the child system. Go to TRANSACTION BD64 and delete the ALE model view for CUA.
Subsequently go to parent system. Then to transaction SCUA. In menu bar go to Distribution model and then to Delete. Choose the radiobutton Child System and then give the logical name of the child system.
Post system copy activties:
1. in case the system copy has been performed from parent system of CUA to child system then go to child system and then goto BD64. Delete the exisitng ALE model for CUA. If parent system is not the source system of CUA you can ignore this step. Next Login to parent system. Go to SCUA then change mode and then add the logical system name of child system to it.Next go to SCUG and do user master reconcilliation.for this double click on child system and then under do transfer users wherver it is available.
Frankly these are ideal steps after system copy ahich I follow since there is not much disparity in user master data across systems in my CUA. So even if system copy happens the user master data in child system remains more or less the same.
If at all there is a minor difference I adjust it through SU01 or SU10. However in case there is a major difference then you it becomes a bit complicated. reasons being system copy wil overwrite entire stuff. Whether it is CUA or any other data. Say for example a child role exisits in child system but is not in the source system of system copy then it wont be present after system copy. if there are such issues then let us know. May be we can think
something. otherwise this approach should do the job for you.
Please award points if you found the anwers useful.
regards.
Ruchit.

System Refresh Precautions?

Hi,
During system refresh, are all types of data - master data, transaction data as well as <b>customising data</b> get refreshed from prouduction environment?
Could you please suggest what is best way to get back project specific new customising data on a refreshed environment? Is there some sap recommended best practice on this.
regards,
Karthik

Hi Please go through. This will give you exhaustive information. After refresh we used this to get back the required system specific customizations.
     Refresh from PR1 to QA1
1.     Before the copy
     Note down customer key, Installation number and license key - Done
     LICENSE system: QA1
     Customer key: L1985917776
     Expiration_date: 99991231
     Installation no: 0020065063
     Key: GKRZ25H353129JYX8HCJRS13
     Productid: R3_ORA
license useable ***
(directory: \usr\sap\QA1\SYS\exe\run)
(run command: saplicense show)
Team Involved: SAPDBA
     Download RFC tables - To be done
Tables rfcattrib, rfcdes and rfcdoc have been exported using sapdba on QA1 and the corresponding files are kept in a new temporary directory: /oracle/QA1/rfc_dest. After the system copy, these files have to be moved from /oracle/QA1/rfc_dest to /oracle/QA1/sapreorg and then the tables can be imported into QA1, to revert back to the RFC destination information as it is now.
Steps : 1)login with oraqa1
           2) type sapdba
           3) select e - Export/import
Perform this step two days before the scheduled refresh.
Team Involved: SAPDBA
     Backup user master records in QA1 - To be done
Procedure : login to QA1 400.
Execute Transaction code: SCC8 (CLIENT EXPORT)
Selected profile: SAP_USER
Target system: QA1/DV1(safety backup)
Perform this step two days before the scheduled refresh.
Team Involved: SAPDBA
     Compare filesystem spaces - Done
Team Involved: SAPDBA
     Compare transports To be done
Team Involved: SAPDBA
     OPERATION MODES(RZ04) Done
Existing QA1 operation modes.
Team Involved: SAPDBA
     Successful backup of PR1 To be done
A successful offline backup has been scheduled on *** and that backup will be restored on to QA1 by the Unix team.
Team Involved: USTO
     System messages/E-mails To be done
SM02- CREATE A TEST MESSAGE IN PR1
Two days before the scheduled refresh perform this step.
Team Involved: SAPDBA
     Delete the existing datafiles on QA1 To be done
Login as qa1adm and execute stopsap
Login as oraqa1 and execute:
lsnrctl stop
rm rf sapdata?/*
Team Involved: SAPDBA
2.     The copy To be done
Copy all the datafiles from /oracle/PR1/sapdata? To /oracle/QA1/sapdata?
Owner, group and permissions of the new files/directories to be maintained as before
Copy Command: rcp p /oracle/PR1/sapdata*   Sierra: /oracle/QA1/sapdata*
(NOTE: If errors occur when restoring/copying the sapdata on the target system, the complete restore/copying has to be repeated.)
Team Involved: UNIX FOF/USTO
3.     After the copy To be done
     Creating the control file on PR1 To be Done
Login as pr1adm and execute the following in svrmgrl
connect internal
alter database backup controlfile to trace;
exit
FILE created under the following Location: \ORACLE\PR1\saptrace\usertrace\ <pr1_ora_xxxx>.trc chose the latest run
ftp the file onto desktop
Team Involved: SAPDBA
     Edit the control file To be done
Here is the edited control file:
Team Involved: SAPDBA
     Creating the control file on QA1 - To be done
Login as oraqa1 ftp the file to /oracle/QA1 and execute the following in svrmgrl
connect internal
@control.sql
alter database open resetlogs;
lsnrctl start
exit
Login as qa1adm and execute startsap
Team Involved: SAPDBA
     Post system copy activities
     License installation - to be done
Login with user qa1adm
Goto /usr/sap/QA1/SYS/exe/run
command: saplicense install
     Installation check (Transaction SICK)
     SE06 > Database Copy or Migration > Post Installation Processing
     Delete entries from tables: DBSTATHORA, DBSTAIHORA, DBSTATIORA, DBSTATTORA, MONI, PAHI, OSMON, DBSNP, SDBAH, SDBAD, SDBAP, SDBAR, DDLOG, TPFET, TLOCK and TPFHT
     Initial SAP consistency check (Transaction SM28)
     Database consistency check (Transaction DB02)
     Server check (Transaction SM51)
     TMS configuration
      Logon to the SAP R/3 System and goto TCODE SE06. Select "Database Copy or Migration" and execute "Post Installation Processing".
      Delete old TMS configuration and make new configuration for TMS via STMS TCODE.
     Logical system set-up and BDLS
Delete logical system for client 400 after system refresh and create new logicalsystem and assigned to client 400.
After refresh: LOGSYS400(logical system for client 400)
Delete this logical system and create new logical system
New logical system: QA1CLNT400 (logical system same before refresh in QA1)
     ITS and Bugseye settings
     RFC destinations as per Appendix (import the exported tables and then delete the temporary directory /oracle/QA1/rfc_dest)
     Logon load balancing(Transaction SMLG)
     Instance profiles
Import profiles from active servers using RZ10
Save and Activate instance profile. And restart the sap services.
     CCMS configuration
     Housekeeping jobs
     Background jobs(daily jobs)
     Application jobs
     Printer/spool/TemSe set-up
     User administration
    The transports are imported implicitly in post processing with transaction
SCC7.
     Transport sequence number set-up
     Mass transport and Support package/patch application.
Re-import transports to QA1 from DV1 which are not available in PR1.
     Manual configuration
     Create the rest of the clients:
o     400     UAT/OAT Live Copy
New client 340 to be created with the following settings.
Source client: 400
Target client :340
Profile: SAP_UCSV
COPY MODE: local copy
Team Involved: SAPDBA

System refresh from Production to Quality

Hi,
We are going for system refresh from Production to Quality. We are at SAP NetWeaver 2004s with 700 release and at 0021 level. Our data base system is DB6 with the release 09.07.0000
I understand that there is a note 886102 available for the system copy. But I would like to know how that had been practically implemented from your ready documents like
1. What would be the BI consultant role during the refresh (I mean where do we involve at). I have seen many links related to this but nothing answer my question, so please don't give me links available.
2. How to identify tables that need to be copied and restored to retain the correct source systems for data/info sources.
3. What should be the BI consultant task before refresh?
4. What should be the BI consultant task post refresh?
5. What are issues faced post refresh in quality system.
I request, the consultant who had worked on these refresh can provide me correct solution.
Thanks in advance.
Regards.
Raj

Our prerefresh activities included
Inform security team to do no user or authorisation changes for quality during the refresh.
Set message in development to not release any transports anymore and set message in quality to inform users in quality not to manually import transports into quality and also not approve transports for production. This ensures no transports get moved to quality and production.
Switch off cyclic import all job (like TMS_0000000038TMS_TP_IMPORT) and the cyclic RSTMS_DIST_APPROVED_REQUESTS job
Prepare list of transports for re-import to quality after refresh and give this to BASIS.
Post refresh activities included
Tcodes SM37, SM35 and SP01. Check that BASIS had set all released jobs to status "Susp/Released"
"All jobs are in 'Susp/Released' state. Set them all to 'Scheduled ' as follows:
- Run report BTCTRNS2 to change all to 'Released'.
- Immediately use SM37 to change all to 'Scheduled' "
IF ANY ARE NEEDED. Remember to change Exec Target in any job you need to release.
"Schedule RSTMS_DIST_APPROVED_REQUESTS to run at x:29 and x:59 - so every 30 minutes.
Please schedule with DDIC as step user (and not your own user-id)."
Check the STMS_QA and import queues to be sure that the tranports are correct- no extra ones during refresh???
Once happy with the above request that Basis schedule the auto import to run every 30 minutes
First ensure that BDLS has finished and system is ready for use.
Post refresh issues faced in production
Many reinit issues
ACR issues.
Master data issues.

Adding transports to import queue after System Refresh

Hello All,
Every time we do system refresh from PRD to Sandbox as a part of post refresh activity we need to import all the transports which are in the import queue of PRD(which are not yet imported to PRD) to our Sandbox.
But its a tedious job, as in the import queue many old transports which are still not yet imported to PRD will b there.
So may b around 150+ transport requests in the import queue of PRD, which we need to add those manually from path
Extras---->other requests -
> Add. doing same for 150 times. cant even imagine dat work.
So my question is, Is there any way to get the replica of import queue of PRD to Sandbox.
Some where i read like transport buffer in the path /usr/sap/trans/buffer/<SID> of the system will have list of all transports in the import queue.
So can i copy dat file and replace SID with Sandbox SID and place it in the Sandbox under same path.
Please suggest or give me a correct solution.
Regards,
Ravi

Thanks a lot for your reply.
I had read about using script like tp addtobuffer inorder to add the transports to the import queue some time back.
But forwarding transports is a new method i got to know here which even looks easy too. It would be great if any 1 tell me how forwarding works.
Also it would b fine if who all uses this method of forwarding to add transports to import queue do reply about any problems faced while forwarding requests.
Bcoz in our landscape , transport route is as below
Dev to QA and Sandbox then from QA transports will move to Production.
So after refresh forwarding Transports from PRD to Sandbox, how does this work. Please share your suggestions.
Regards,
Ravi

Post System Refresh Activity

Hi All,
I did system refresh ( from PRD to QAS , platform Windows 2008 R2 and MSsql) the system was up and running fine. The system was absolutely fine for one day and the day after the DB crashed , not sure what happened, is there a way i can find the logs through which i can come to know what exactly happened. Also post refresh when i was trying to run BDLS , the job was getting cancelled , the job log showed there is another conversion already running , when i checked the tables the conversion had already happened . Please tell me can running BDLS which cancelled many times could be the cause for the DB crash, if yes where can i find the logs for this , if not what else could have happened that the DB crashed . Thanks for your responses in advance.
Regards
Mrigank Aditya

Hi Nainesh,
Thanks for the message , yes system is up and running fine , the DB team did a restore of Production data on Quality again , and i did the post refresh activities again , the issue what had happened last time was we were doing simultaneous refresh of two systems at a time , BI prod to BI qas and ECC prd to ECC qas , we had found a list of tables in BDLS which gets updated when we run BDLS and we run those tables only , unfortunately the files got exchanged , the ECC tables should have run on ECC machine and BI tables should have run on BI machine which didn't happen and it happened the other way round BI tables where run on ECC machine , due to which BDLS failed and the job got cancelled many times, which impacted the whole system conversion and logical update , which crashed the DB( i exactly don't know the reason what happened internally , still searching for it ) . At present the machine is up and running fine.
Regards
Mrigank Aditya

SRM - System Refresh (Post Refresh steps)

Hi,
Can anyone tell me the steps to execute after SRM system refresh using file copy method ?
Thanks & Regards,
Jag

I have seen this somewhere in the forum: See if this helps you
BDLS: Convertion of logical system (SRM).
Check entry in table TWPURLSVR.
Check RFC connections (R/3 and SRM)
SPRO, check or set the following points:
Set up Distribution Model and distribute it
Define backend system
Define backend sytem per product category
Setting for vendor synchronization
Numbe ranges
Define object in backend sytem
Define external services (catalogs)
Check WF customizing: SWU3, settings for tasks
SICF: maintain the service BBPSTART, SAPCONNECT
SE38:
Run SIAC_PUBLISH_ALL_INTERNAL
Run BBP_LOCATIONS_GET_ALL
Update vendor BBPUPDVD
Check Middleware if used.
Run BBP_GET_EXRATE.
Schedule jobs (bbp_get_status2, clean_reqreq_up)
Convert attributes with RHOM_ATTRIBUTE_REPLACE
BR
Muthu

Unable to login in EP 6.0 after system refresh

After performing the system refresh of EP 6.0, completed the post system copy steps.
Imported the new certificated as well, when I try to login the page is getting refresh but remains on the same page.
please help me what could be the reason.

Hi Abdul.
I think you have selected the Algorithm as RSA, which is the default one.<br />
Please change it to DSA and hope the issue will be solved.
Regards,
Satish

Logical System Conversion after system refresh failed

Hello,
Logical System Conversion after system refresh couldn't complete as the printer was locked. This job was run in the background. In SM37, the job log of RBDLSMAP shows as job finished, but it took only 40 seconds. Now I see that the logical system got changed(Converted) in the client settings scc4 but I know that this client being a production client and would run for couple of hours. Here is the job log information.
02/18/2009 16:09:33 Job started                                                                     00           516          S
02/18/2009 16:09:33 Step 001 started (program RBDLSMAP, variant &0000000000000, user ID ABCD)      00           550          S
02/18/2009 16:09:33 Output device PRN1 is locked in the SAP system                                  PO           349          I
02/18/2009 16:10:19 Job finished                                                                    00           517          S
When try to rerun bdls again, it shows that it is already available and it says "The new logical system name is already assigned to the current client".
Any suggestions on this?
Thanks,
Mahesh

Hi ,
Rerun the BDLS again as this took very little time.
When you try to run again it popsup message saying it already exists just delete that and again put the Logical system name and run it will run that time.
May be while scheduling the job you gave for spool I am not sure why is it looking for Printer which is locked.
Thanks.

How to handle the CRM Middleware after system refresh?

Guys,
We are using CRM 5.0 & R/3 4.6C. We have the middleware configured and set up. We finished all inital loads & delta loads are activated as well. The system works perfectly.
Now for some reason the client wants to refresh the R/3 system. (Basically they are copying over the R/3 Dev system to refresh the R/3 Sandbox system. Our connection is currently between the 2 sand box systems) What impact will this have on the CRM system? Will it cause mass delta downloads? I have already referred to notes 588701 & 765018. Any additional information or watch outs will be appreciated.
Secondly what's the best practice do a refresh in the future? Is there a SAP recomendation on how to go about with system refresh when CRM & R/3 are connected?
ARP

Hello ARP,
as always: It depends what to do:
a) do you have a CRM DEV System available? If possible you should get the connection working over there and then do a Landscape Copy of the R/3 DEV + CRM DEV to the Sandbox Landscape.
b) Let them copy the R/3 DEV to the R/3 Sandbox. Then use the Data Integrety Manager (Transaction SDIMA) to get the missing Customers, Transactions exchanged.
In the future they normally have to do a Landscape Copy.
Regards
Gregor

Steps for System Refresh for ABAP + JAVA stack

Hi friends,
I am newbie to SAP BASIS adminstration. There is a system refresh activity planned shortly.
Can someome pls let me know the steps for system refresh of ABAP + JAVA stack??
regards,
Ambarish.

Please check [systemcopy@SDN|System Copy and Migration] and [guides|http://service.sap.com/instguidesnw] according to your release.

BDLS in system refresh

HI all
I did a system refresh of BI .After running BDLS the logs in BDLS shows success. But logical systems are not getting converted.When I checked in SLG1it shows no coversion has taken place. Can any one help me to proceed further and change my logical system
Regards
-aj_

> Oh ok thanks but this was already done. what I mean to tell is If I run BDSL it is showing successful .When I check BDLS logs in SLG1 it is showing error. WHy this happens and what can be done?
Without knowing the error that you see how should we help you?
Markus

System Refresh regarding jobs

Similar Messages

Maybe you are looking for