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.

Similar Messages

Help for Job BDLS - Logical System Conversion aftrer System Refresh

hi SAP Basis Gurus,
We have restored production data to test system. After that we are doing Logical System conversion - Renaming of Logical System Names. For that we are running BDLS job. The program used is IBDLS2LS.
Now one job is running for more than 200000 seconds. Job is doing "Sequential Read" on table ZARIXCO40. The following has been updated in the jobs log:
01.02.2008 10:20:06 Processing table ZARIXCO40
02.02.2008 01:59:56 Processing table ZARIXCO40
02.02.2008 22:26:44 Processing table ZARIXCO40
02.02.2008 23:04:05 Processing table ZARIXCO40
So as per above log, it looks like job got stuck in loop for table 01.02.2008 10:20:06 Processing table ZARIXCO40.
The oracle Session is showing following SQL Statement:
SELECT
/*+
FIRST_ROWS
FROM
"ZARIXCO40"
WHERE
"MANDT" = :A0 AND "LOGSYSTEM" = :A1 AND ROWNUM <= :A2#
~
Execution Plan is :
~
Execution Plan
Explain from v$sql_plan: Address: 00000003A2FD5728 Hash_value: 2772869435 Child_number: 0
SELECT STATEMENT ( Estimated Costs = 4.094.270 , Estimated #Rows = 0 )
        3 COUNT STOPKEY
            2 TABLE ACCESS BY INDEX ROWID ZARIXCO40
              ( Estim. Costs = 4.094.270 , Estim. #Rows = 32.799.695 )
                1 INDEX RANGE SCAN ZARIXCO40~0
                  ( Estim. Costs = 418.502 , Estim. #Rows = 65.599.390 )
                  Search Columns: 1
~
Table has been analyzed today. See the details below:
~
Table   ZARIXCO40
Last statistics date                  02.02.2008
Analyze Method              mple 16.623.719 Rows
Number of rows                        65.599.390
Number of blocks allocated             2.875.670
Number of empty blocks                     7.912
Average space                                934
Chain count                                    0
Average row length                           313
Partitioned                                   NO
UNIQUE     Index   ZARIXCO40~0
Column Name                     #Distinct
MANDT                                          1
KOKRS                                         14
BELNR                                  2.375.251
BUZEI                                      1.000
~
Index used for this table is also analyzed today:
~
UNIQUE     Index   ZARIXCO40~0
Column Name                     #Distinct
MANDT                                          1
KOKRS                                         14
BELNR                                  2.375.251
BUZEI                                      1.000
Last statistics date                  02.02.2008
Analyze Method              mple 24.510.815 Rows
Levels of B-Tree                               3
Number of leaf blocks                    418.499
Number of distinct keys               65.480.722
Average leaf blocks per key                    1
Average data blocks per key                    1
Clustering factor                     40.524.190
~
Can you please let me know what could be the issue and how to resolve this issue so that job gets completed. Normally this job runs for 1,00,000 seconds. I can not afford to cancel this job and run again.
Any help is Highly appreciated,
Thanks
Best Regards,
Basis CK

Hi Markus,
The stastics of the table is already updated today. After that also it is not going faster. It is doing "Sequential Read" for more than 5 hours and then one update is issued. And in the job log, all other tables are preocess only once, only this table is selected to processed 4 times which is very abnormal.
01.02.2008 07:43:59 Processing table ZARIXCO11
01.02.2008 07:45:36 Processing table ZARIXCO16
01.02.2008 10:17:20 Processing table ZARIXCO21
01.02.2008 10:20:06 Processing table ZARIXCO26
01.02.2008 10:20:06 Processing table ZARIXCO29
01.02.2008 10:20:06 Processing table ZARIXCO33
01.02.2008 10:20:06 Processing table ZARIXCO37
01.02.2008 10:20:06 Processing table ZARIXCO40
02.02.2008 01:59:56 Processing table ZARIXCO40
02.02.2008 22:26:44 Processing table ZARIXCO40
02.02.2008 23:04:05 Processing table ZARIXCO40
~
I guess this will keep on going like this and not sure when it gets complete. Any other thing you can suggest which help to resolve the issue.
Thanks
Best Regards,
Basis CK

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.

Logical System Conversion issue

Hi All,
BW (DW100) is connected to two clients say DE100 and DE200. Some of the objects in BW are pointing to DE100 and some of the objects are pointing to DE200.
Now we planned to make all the objects pointing/connect to source system DE200 not to DE100. The objects pointing to DE100 are created in DW100 in Release 1 and objects ( Release 2 ) pointing to DE200 are moved from another system development system.
What is the best approach to make it more stable because some of the objects are used in DE100 and some of the objects are used in DE200 . In process chain, we have infopackage and DTP connected to DE100 and for some objects connected to DE200.
What we planned means first run the BDLS from DE100 ( old Logical system ) to DE200 ( New Logical system ) and re-traanspotr the TR ( Release 2 ) to DE200.
COuld you please advise here what should be the best approach?
TIA

Completely depends on the way the production system exists - if it exists with a single client, then life is easy.
You might have connections to a BW system from source system with two clients. But if the target system has only one client, then you can just transport the Transport requests from both of these clients to the target system.
Meanwhile you can transport the TR's from BW system which connects to 2 clients to a target system with one client. But you need to maintain the proper details in source system conversion table in the target BW system, else the transports will fail at the import step.
Regards,
Thejas K

Logical System Name changing

Dear Team,
We had upgraded BI system from 3.0B to BI 7.0. At the time of upgrade dev
copy(shadow system) logical system was not changed because most of the data is coming from ETL. Now we want to test the extraction from R/3 Dev.
R/3 Dev is already connectwed to BW dev 3.0B, Now we need to test
extraction from R/3 Dev to BW dev copy server( NW2004SR1 ).
Here we are facing a problem with Logical system. While upgrading the
same logical sys was copied to BW dev copy.
What is the procedure to change the existing logical system name in BW
dev copy and establish connectivity with R/3 dev?
what is the impact if we run BDLS transaction.
Thanks& Regards,
Satish.K.Neni

Hi Satish,
Go to transaction SALE -> Basic settings -> Logical systems -> execute "Define logical system" to create a new logical system -> then execute "Assign Logical System to Client"
That should solve your problem
Regards
Juan
Please reward with points if helpful

How to change name of a logical system

Hi SDN,
I am trying to customizing intial download data transfer from ECC to CRM. But in outbound queue of ECC it is showing an error of SYSFAIL with description of logical system name changed. Given note 558701.
But I don't know old name of logical system.
1) Can you guys please help how to find the old logical system name there are many logical systems defined in my system.
2) and how to change it?

Hi Ravi,
Since logical system name is changed sombody in past must have ran BDLS to conver logical system name.
Check tcode SLG1, this tcode will tell you whether there were any logical system conversion done in Past, if it is done then it will tell you from which old logical system its converted to new one. So you can find out old logical system name.
Once you find out old logical system run BDLS again. It might possible BDLS ran unsuccessfully last time.

Logical system same in DEV/QAS/PRD for ALE

Hi friends,
We haven't used ALE but now need to set it up. Problem is, DEV and QAS are copies of PRD so all three have the same logical system name. I read about how using bdls to rename the logical system can create inconsistencies and am worried it can ruin our transport system.
Appreciate your comments, thanks & best regards.
Claudio

Using BDLSS in comaprsion to BDLS - logical systems can also be converted remotely in all partner system.
Please refer: SAP notes
544509 - ALE: Converting the name of the "logical system"
121163 - BDLS: Converting logical system names
1478123 - FAQ: Source system
Divyanshu

Not converting the logical system through BDLS

Hi Experts,
I did the system copy of BI system from production to developemnt
To change the logical system in RSA1 --> Source systems
I have choose client role as test in scc4 and in tcode BDLS i have given the old logical system name new logical system name
after completing the job RBDLSMAP i checked in the RSA1 there is no change in logical sytem
i got the following message
SM37 log
Job started
Step 001 started (program RBDLSMAP, variant &0000000000005, user ID ABCD)
Logical system name ABC500-1 does not match SAP's recommendation
Job RBDLSMAP no longer exists
Converted table: 'RSSTATMANSTATUS'; number of changes: ''
Converted table: 'RSSTATMANSTATDEL'; number of changes: ''
Converted table: 'RSSTATMANREQMAP'; number of changes: ''
Converted table: 'RSSTATMANREQMDEL'; number of changes: ''
Converted table: 'RSSTATMANPSA'; number of changes: ''
Converted table: 'RSMDATASTATE_EXT'; number of changes: ''
Job finished
Spool log
Table Name                Field Name       Number of Relevant Entries    Number of Converted Entries
/BI0/ABP_CUST00*          LOGSYS                              0                              0
/BI0/ABP_CUST40*          LOGSYS                              0                              0
/BI0/ABP_VEND00*          LOGSYS                              0                              0
/BI0/ABP_VEND40*          LOGSYS                              0                              0
/BI0/ACDS_DS0400*         LOGSYS                              0                              0
/BI0/ACDS_DS0440*         LOGSYS                              0                              0
/BI0/ACDS_DS0500*         LOGSYS                              0                              0
/BI0/ACDS_DS0540*         LOGSYS                              0                              0
/BI0/ACLM_DS0300*         CLM_FISY                            0                              0
                          LOGSYS                              0                              0
/BI0/ACLM_DS0340*         CLM_FISY                            0                              0
                          LOGSYS                              0                              0
/BI0/ACLM_DS0600*         CLM_FISY                            0                              0
                          LOGSYS                              0                              0
/BI0/ACLM_DS0640*         CLM_FISY                            0                              0
                          LOGSYS                              0                              0
/BI0/ACRM_CMGL00*         LOGSYS                              0                              0
/BI0/ACRM_CMGL40*         LOGSYS                              0                              0
/BI0/ACSM_LINK00*         LOGSYS                              0                              0
/BI0/ACSM_LINK40*         LOGSYS                              0                              0
/BI0/AGN_BP00*            GN_PAR_LSY                          0                              0
/BI0/AGN_BP40*            GN_PAR_LSY                          0                              0
/BI0/AGN_CONV00*          LOGSYS                              0                              0
/BI0/AGN_CONV40*          LOGSYS                              0                              0
Could any body help me in this
Thanks & Regards,
Arun

Hi experts,
I have done the system copy form Production to Developement.
Transfermations and DTP(Data transfer process) are still connected from Produciton R3 which should be from developemnt R3.
I have tryied to change the logical sytem name through BDLS. But the logical system name is not changed
i got the job log which is in above conversation in my thread.
Please let me know how to change the logical system name in Transfermations and DTP in RSA1
Thanks & Regards,
Arun

Conversion of Logical systems

Dear All,
we are in the process of coverting exsisting logical system name into new one thru BDLS.Please throw some suggestions on what are asll the areas should we take care, areas get modified like programs, rfc etc.Please reply asap
Thanks in advance
Umesh k

after a system refresh, if your logical system is using a generic name such as BW-SYS instead of BWP-001, you can change the RFC connection hostname in SM59 and stop there.
if you must change the logical system name because it it SID specific, then you must run BDLS. It can run in 2 hours... or 3 days. this depends on hardware specs and size of DB.
to help you make it run faster and in parallel, read the interesting blog about BDLS at /people/hari.peruri/blog/2006/11/01/execute-conversion-of-logical-system-names-bdls-in-short-time-and-in-parallel--intermediate

BI 7.0, BDLS is not converting all logical systems for datasources

Hello all,
We have refreshed an ECC system, and during the post steps in BI, we were running into issues.
We've ran BDLS to convert the logical system from ECCCLNTXXX to ECCCLNTYYY, but it's was not converting for several datasources.
One in particular was causing several problems, and terminating the conversion.
0FC_CI_01. It is still hanging on to the old logical system. BDLS terminates with the following information:
Short text:
Active version of emulated 3.x DataSource 0FC_CI_01 cannot...
Basically, the exact symptom of Note 936644.
Eventually, through a series of trials, we discovered we could assign non-active sourcesystem/logical system combinations to the objects. As a result, we deleted the source systems entirely, ran BDLS to the ECCCLNTYYY, then recreated the sources.
This finally worked. What I need now is a root cause. Why would BI refuse to change the logical system of an object to an active one, but have no problem with an inactive?

Mike,
After running BDLS, you need to replicate the source system in BW, change the contents of the target host and fields for all R/3 and Data Mart(note 184754). Update the target BW system name in table T000 using SM30. Change logical system name in all BW tables using BDLS (note 325525)
Refer to the below doc for detail. Also refer to note 886102.
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/805eefcd-5428-2d10-c0ab-dc27a95b2c81?quicklink=index&overridelayout=true]
Below note talks about similar issue.
How to change all infosources to the new source system automatically
Hope this helps.

Conversion of logical System Name

Hi,
I have read somewhere that Conversion of logical System Name is part of BW System check Before go live. Can someone explain the purpose of it.
Thanks in advance
krish

Hi,
There are two different activities related to this, if you have done the system copy then for changing the logical system name we will run BDLS transaction. Check the below link for more information,
[http://help.sap.com/saphelp_nw70/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/content.htm]
But if you want to move the source system dependent objects from one system to another system then we maintain the source system and target system mapping in target system.
For transport method you can maintain the system names as suggested by Gaurav and you can check that in table RSLOGSYSMAP or you can directly maintain entries in this table.
Regards,
Durgesh.

BDLS updating logical systems in CIF models?

Hi
The BDLS tool can be used to update logical system names in systems. As I understand this tool is often used when copying systems (Production system to Q system for instance).
In a situation where you copy the productive system to the Q system:
Does anyone know if BDLS is capable of updating the logical systems in the generated CIF models that you get copied from the productive system? In this case you'd get a big chunk of models that point to the wrong logical name. If you could get the target system changed in the generated model then you could save a lot of time in generating and activating models.
Any comments much appreciated
Simon

Hi,
I am not too sure if this thread is followed. I was looking for some info where we had a similar issue recently when we did a production refersh to Quality and all our integration model variants are pointing to our production system.
Our basis team has taken all the necessary steps like BDLS etc, but we had this issue. I dropped a message to SAP and they gave a report name RCIFVARIANTCHANGE to change the logical system name from old one to the new one for CIF variants.
Thanks,
Murali

TDMS - conversion of logical systems

Hello,
during execution of activity "Assign Logical system names in receiver systems" I got empty list. Normally I was getting whole list of logical systems for both sender and receiver system. And now I have nothing...with message "No logical system name maintained for Receiver Systems".
Of course I checked BD54 and all entries are there, both systems are open, both on SP15.
Any suggestions from anyone?
cheers
Michal

You can also cross-check in table TBDLS or txn BDLS.

Conversion of logical system name fails

Hi,
when trying to transport a transformation on BW7 the logical conversion name is failing. When i check the setup (on rsa1 menu "Conversion of logical system names") it seams to be ok on source and target system.
Any tips to solve this ?
thx in advance

Hi,
when you are not maiantained the logical systems properly , then you will get that error when you are transporting the objects
in Bi production system ( to which server you are moving objects) in that you should maiantain the all logical systems as below
1) for examaple BI deve --- BI prd
one logical systm should be bi Dev to BI prd
2) ECC production connected to BOI production
Then one more logical assignment ECC prd to BI prd
normally those two you are maintained i think so.
but when you are moving the objects from the BI development to Bi production
the daat sources are pertaining to the ECC developmet
so that ECC deve to BI Dev ( here there is no problem)
when those daat source s you are moving to production it shows error
because that ECC deve Data source logical system should be changed to BI production
so you main tain one more logical system ECC dev to ECC PRD
in your BI system
Then try reimport the same.
Thansk & Regarsd,
sathish

Conversion of logical system names

Hi
Must the Conversion of logical system names be set up in each client.
I.e in the BW production client do I have to go and setup what the conversion is between before the transport and after the transport.
Also if I then go into this view and want to add my conversion detail, and the system doesn't exist (in table) do I have to create the entries in Dev and Transport it through?
Corne

Hi Corne,
If the correct entries don't exist in the underlying tables, you have maintain it in SPRO.
The entry in the table is cross client. hence it has to be done in Dev.
Go to SPRO -> SAP Netweaver -> Business Intelligence -> Links to Other Source Systems -> General Connection Settings
-> Define Logical System
1. To create a logical system, choose Edit -> New Entries.
2. Enter a name for the logical system that you want to create.
3. Enter a description of the logical system.
If you want to cange this entry:
a) Select the appropriate line.
b) Choose Edit -> Change field contents.
c) Enter the new text.
d) Choose Replace.
4. Save your entries.
Roy

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

Similar Messages

Maybe you are looking for