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

Similar Messages

Post System Refresh Activity - BDLS run

Hi,
We have finished system refresh of a QA system from Production. We need to run BDLS now to convert the original Production logical systems to QA relevant logical systems.
I am short of understanding of this process. Can anyone please help me with the concept and process?
Thanks in advance,
Abdul

Hi Abdul Rahim Shaik,
BDLS will convert the logical system name for your PROD to QAS.
For eg:
Your source - PRDCLNT100
Your target - QASCLNT100
If you go to SCC4 in your QAS, u will see Prod logical system name for the client.
Once you run BDLS after system copy, logical system name exist in every table for PRDCLNT 100 will change to QASCLNT100.
Refer to below link for more info:
http://help.sap.com/saphelp_nw04/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/frameset.htm
Cheers,
Nicholas Chang

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.

Procedure to restart cancelled BDLS (logical system conversion) !! Urgent

Hello Experts,
I need immediate help. I started the BDLS (logical system name conversion) and it was running for about 3 days. It was about 70% complete. But because the users could not afford downtime, I cancelled the BDLS job. When I tried to restart BDLS later, it is giving an error "Logical system name already exists". Kindly note that we are on R3 4.6C environment with CRM 4.0. The BDLS conversion is on R3 4.6C QA which was refreshed from R3 4.6C prod.
My question is
1- Is there any way to restart BDLS on R3 4.6C? If so, what is the procedure?
2- The BDLS was 70% complete, before it was cancelled. So it created a new logical system name. Is it possible to delete this new logical system name without any problems?
3- Because BDLS converted 70% of the tables from old logical system name to new logical system name. There might be data inconsistency.
3a- Is there a way to reset all the converted tables to old logical system name?
3b- Is there a report or program or a procedure to reset the BDLS?
4- Will this state of having 70% of tables with new logical system name and 30% of tables having old logical system name create any problems for the data transfers and for the business?
Kindly help me in this regard as this is a very urgent issue. Points to be awarded for any kind of small help.

Thanks a ton Srikishan. I will do the same as you have said.
A couple of more questions.
1- Do I have to start this immediately now, in the morning hours, asking all the users to get disconnected or schedule it later, during the night time or on the weekend.
Will this current state of having 70% of tables with new logical system name and 30% of tables having old logical system name create any problems for the business?
2- If this there a way ( a program, a procedure) to reset changes done by BDLS?
Kindly note that due to the database being large, BDLS is taking 3 days. So I cannot do this during the week days (during business hours), I will have to reschedule this during the weekend.
Please let me know. Thanks.

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.

System refresh PRD-QUA

Experts,
We have completed the system refresh using PRD system data.
part of post processing activity using t-code BDLS and and completed the Logical system conversion.
But still we observed that in BI system still prd system logical system (as below) name available on the infoobjects, because of the some of the jobs failed at BI system.
RSA1->
Data Transfer Processes
8PB1CH0338T / PPXCLNT100 -> ZDINXXX
Please let us know how to change the all the logical system from production system to quality system.
Thanks
Malai

Hi Nick,
Thank you for the response..
Yes we have activated and ran the replication also.
its seems looks good When I check the check the datasources,
Version : active
and datasoruce as below
Datasouce for QX1CLNT100 QX1 client 100
8PB1CH0338T
ZDINCOMP_TEXT
RSDS 8PX1CH0338T
QX1CLNT100
-> IOBJ ZDINCOMP
C Din Company (Texts) TEXTS ZDINCOMP TEXTS ZDINCOMPTEXTS ZDINCOMP
But click the inforprovider it shows around 30 of them shows PX1CLNT100 logical system.
How Can i change those PX1 logical system name
Thanks
Elumalai

No Idocs were getting generated after the system Refresh

Hello Experts,
Recently my Sand box system has been refreshed with the Development system. (Its a system refresh and hence all the objects were also copied like Development).
After the refresh, we have performed the below activities --
BDLS to change the logical system
Maintained the LS in WE20
Partner Profiles from WE21 with proper settings with respect to the new logical system name. (Sand box).
RFC to myself source system and to the Flat File.
While executing a test load from Flat File the system is not able to generate any IDOCS in the system and failing with
"No Idocs generated; file system
Diagnosis
No IDocs have been created. With file systems as source systems, the IDocs are created in BI. As this did not happen, it is probable that there was a short dump in BI.
I dont see any short dumps in ST22 for this load and also any logs in SM21.
Any idea why the system is not able to generate IDOCS in the system?
We are planning to connect R/3 sandbox to BI sandbox once the Flat file load is running fine.
Thanks for your answers.
Raman

Hi ,
Hi
BD87 Update Idocs manually.
1. When you look in the Monitor screen for the first time on a day you mostly will see some Loads that have yellow traffic lights. When you click on the lowest line of the Load (with the time of Load start) you will get the next popup screen:
2. Here you can click on the "Yes" button. The Load specification window (right side of the screen) will now be filled with data.
3. You can now start the manual processing of the IDocs. You go to the "Details" tabpage of the right window. You right click on the line with the red traffic light stating "Request IDoc : IDoc ready to be transferred to application" on the "Details" tab page of the Load. In the option menu that appears choose the option "Update manually in OLTP" (click it).
4. You will get to the next screen (which is in fact a transaction in the source system (SAP R/3) where you can update the IDoc that is send by the source system)
5. Now click the "Excecute" button on the left of the screen (or press the F8 button on your keyboard). You will get to the next screen:
6. This states that the IDoc has been passed through to BW. You return to BW by clicking the "Back" button (or pressing the F3 button on your keyboard) twice. After the first time you will see the previous screen and after that the Monitor screen again.
7. You will now see that the Status of the Load has turned to yellow or green. When it is yellow you will have to wait a little time (the execution of the Load in BW is still running) and by clicking "Refresh Details" button on the left upper side of the screen (or pressing the F8 button on your keyboard) you will see the Load turn green.
Regards,
Rahul.

BW system refresh

Hi All,
We are facing issue in system refresh.
Major Steps performed
1) restored prod db to qas.
2) before bringing up the application deleted rfc tables
3) after bringing application back imported the rfc tables back into system
4) run bdls for BW system BWPCLNT100-BWQCLNT100 but not for R3
5) created back the connection in RSA1
I got to know that we don't have to delete rfc, and run bdls for r3(source
system) too before retaining rsa1 but we missed the step, now if we run
bdls for r3 and execute rsa1 and restore and activate would it help us in
getting the desired refreshed system.
Please suggest.
thanks,
Mridul

Yes, you need to BDLS for R/3 logical system in the target BW system(once this is done run RSA1 )
Also no need to delete the RFC's ,simply you import the RFC's that were exported before refresh from the targget system.
Regards,
Srini Chapa.

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

Quality system refresh in SRM

Hi All,
After the SRM quality system refreshed with production ,what are all the settings we have to check and maintain so that we have connectivity with the backend system.
What are the RFC settings to be maintained and procedure to maintain?
Thank you
Regards,
Yshu

Hi. First set up the RFC destinations as you would normally, then run BDLS to change the logical system from the production one to your qualtity one.
Then, run program RHOMATTRIBUTES_REPLACE to change the attributes that contain logical system, you can use the sub-string checkbox to just change the first part of the attributes.
Finally check your middleware setting, you will probably need to delete the current site and create a new one pointing at the QA system.
Regards,
Dave.

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

How can we automate the Post system refresh activities

All,
Just want to know if there is a way to automate most of the post system refresh activities that were done by Basis.
Please note that i am talking about Post System refresh activities.
Appreciate your responses.
Thanks,
Giri

It all depends on what you would like to do: you keep the same SID or is it a rename?
- you could plan 1 jobs on production after event 'Zafterrefresh" with following steps:
that runs a BDLS
that does a cleanup of the spools
cleanup application logs
Trigger the event after the refresh and that starts.
Depending on your system you can run multiple jobs in //
some actions will have to be done manually:
user import
TMS config
etc

Delta Setup/Link Broke After System Refresh in Sandbox with Prod

Hi All,
   We have done the System Refresh for Sandbox with Production in BW. After that, we tried to load 0FI_GL_4 Delta and it failed with 'Queue 0FI_GL_4 is not available in the Source System' in Monitor. It means something went wrong in System Refresh process and the Delta setup broke. The 'Status' traffic light for 0FI_GL_4 DataSource is in RED in 'BW Delta Queue Maintenance' (RSA7) in R/3 system. When I display this Status (Red traffic light) it says 'There are still no parameters available for the delta transfer'.
   Since the Delta link broke, I have deleted the 0VENDOR_ATTR Master Data DataSource in RSA7 in R/3 and Initialized the Delta in BW for this 0VENDOR_ATTR and it completed successfully and now 0VENDOR_ATTR Master Data DataSource in RSA7 in R/3 is in GREEN.
   But, we have GL InfoCube which has 120 million records and if we initialize the Delta it will take atleast 7-10 days. It will take atleast 2 weeks for all the InfoCubes and ODS's.
How could we restore the Delta setup/link and the Status of the DataSources will turn into GREEN in RSA7 in R/3, PLEASE ?
Thanks in advance.

Hi,
Ask your BASIS team to run BDLS. That should take care of the problem. It'll repoint the delta queues to the correct source system. With the refesh the delta DS will point to the system it was refreshed from, hence the problem.
Cheers,
Kedar

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

BDLS in system refresh

Similar Messages

Maybe you are looking for