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.

Similar Messages

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.

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 name reset after system copy

Hello
I´have a question regarding logical system set after performing a database copy from Production to Quality . In Quality the former logical system name before the copy was INT10 . After the refresh I want to runs the BDLS with conversion from the prod PRD10 to Quality INT10 . But when I run the BDLS I 've the error the logical system INT10 already exists . Can I remove this entry in the
BD54 in order to be able to specify INT10 as the target in BDLS ???
Thanks a lot for your advice .

Hello
In fact it worked it test mode but failed in Run mode . The job RBDLSMAP ran 1 seconde and stopped Here is the conversion report in the slg1
<    SAPoffice No object reference exists -> No conversion
<    SAPoffice Object references that have been converted: 0
     Table buffer in server synchronized after conversion
<    The processs is executed in the background (RBDLSMAP 11041701) in sys
I have one table which Field in table contains the name INT_010
BDSX_CON04*               LOG_SYSTEM                          0                              0 <<
When I have a look in the SCC4 the logical system name is still set to EXP_10 .
No conversion took place here .
Just a question , iI triggered the conversion in the client 000 . is ti correct or must it be triggered in the productive client ?
Thanks in advance

Change logical system names after system copy

Hi!
We successfully installed SAP ECC 6.0 system as system copy.
All the logical system names of old system have been copied to new system.
Question
What is the approach to change the logical system names for new SAP system?
a) just via tcode SCC4
b) via BDLS
c) other tcodes, reports
Thank you very much!
regards
Jürgen

Hi,
Go though the system copy guide.
http://service.sap.com/instguides
After system copy,
If you need to change logical system names in the system that results from the copy, change the logical system names as described in SAP Notes 103228 and 544509.
https://service.sap.com/sap/support/notes/103228
https://service.sap.com/sap/support/notes/544509
Before running BDLS to change the logical system name, you have to define the correct logical system name in the new copied system. in tcode BD54.
- while running BDLS, execute in background.
Regards,
Debasis.

Logical system names after system copy

Hi!
I installed a new SAP system via System Copy (SAPINST) approach.
As a consequence the old logical system names have been copied.
Question:
What is the appropriate approach (tcode, report) to change the logical system names of each clients of SAP system?
Thank you very much!
regards
Jürgen

Logical System Names
When data is distributed between different systems, each system within a network has to be clearly identifiable. The u201Clogical systemu201D deals with this issue.
A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client.
Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way.
Although SAP does not recommend that you connect test systems to production systems, a test system can have the same name as a production system. This makes copying production systems to test systems a lot simpler.
You are only allowed to change the logical system name of a system if the system is not connected to any other systems, because changing the logical system name would render all the connections to other systems useless.
In BW, you make the settings for the logical system names in the BW Customizing Implementation Guide under Business Information Warehouse ® Connections to other Systems ® General Connection Settings. In the source system, you make the settings for the logical system in the Implementation Guide under Cross Application Components ® Distribution (ALE) ® Basic Settings.
Note SR047 lists names that cannot be given to BW systems, because they are reserved for internal use.
Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: .

Myself Source system problem after System Copy

Hi All,
We recently did a system copy (Production -> Dev). After the logical system rename is done, the myself source system is showing up as a External SAP system, in source system tree under SAP instead of BI. I'm not able to restore/activate it. Any inputs on this problem is appreciated.
Thanks & Regards,
Sree

Problem was with inconsistency in the RSBASIDOC table. Solved by deleting invalid entry and running BDLS again for this specific table.

BDLS Conversion after System Copy fails

Hi All,
We are doing a Homogeneous System Copy on a AIX 5.3/Oracle 10.2.0.4/ SAP ERP 6.0 environment.
After the system copy we had to run BDLS to convert logical system names in tables. Except for 3 tables namely EDPP1, TBD05 and TBD06 the BDLS run was successful.
We tried to convert the logical system names in these tables by running BDLS for these tables individually however they failed again.
The error was - "Error in field of table. Manual correction required"
I checked SAP Note 121163 and it is mentioned in this note -
"If the new logical system name already exists in the system, it can cause errors for tables in which the logical system is key field or
unique index (for example, COFIO1). In this case the number of converted entries is smaller than the number of selected entries."
And in this case a manual post-processing is required. How do I go about doing this manual post-processing?
1. Should I maintain these directly at the table level - which is cumbersome as there are a lot of entries?
2. Or using a small ABAP program?
Please let me know if any other information is required frommy side.
Thanks, Dibya

Hi,
Yes ofcourse, you need to check all settinfs, once you copy teh system you are going loose all RFC's and Source and Destinations ectc, so adject all that settings.
See the following SAP Notes:
SAP Note 886102 - System Landscape Copy for SAP NetWeaver BW
SAP Note 325470 - Activities after client copy in BW source systems
SAP Note 325525 - Copying and renaming systems in a BW environment
SAP Note 1333302 - Special procedure for BW system copy
SAP Note 996238 - Dump 'RFC connection error' after BW system copy
Search for PDF in SDN
How Tou2026System Copy in SAP Business Intelligence System Landscapes
Thanks
Reddy

Source System Problem after system refresh in RSA1 trx

Hi,
We have R/3 4.7 Test source system created in our SCM 2007 Test System. The source system check was OK.
The R3 Test system was refreshed with Production data few days back and now my source system is not working. When i perform Source System check it says:
BI unknown in source system
BI IDoc type ZSSB006 is not the same as source system IDoc type
I performed following steps in R3 Test system after its system refresh:
1. Created logcal system and created RFC.
2. Created port in trx we21.
3. Created partner profile in trx we20.
4. For the outbound parameter RSSEND, I had to create idoc type that should be same as in my SCM system i.e. ZSSB006.
5. Created idoc type using trx we30 as a copy of RSSEND and added entry in table EDIMSG. Now, i could also create outbound parameter RSSEND with idoc type ZSSB006.
After performing the above steps i also replicated the datasources for the R3 Test source system, but its still showing above error.
I also checked the RSBASIDOC table in SCM test system. It has correct entry for my source system. But there is no such entry in RSBASIDOC table in the R3 test system.
Someone pls help me.
Regards,
Chintan

Hi
Need to restore the All Dalaload connection settings after refresh the system which either R/3 or SCM.
RSA1 -> select the Source system -> Right click -> Restore , It'll ask the connecon paramters like RFC , method of activations. Then check the connection test of the Source system .
Check the the note for further info...
Note 886102 - System Landscape Copy for SAP BW and NW BI
Hope halp you...
Regards,
Sureshram

Source System Problem after System Refresh

Hi,
We have R/3 4.7 Test source system created in our SCM 2007 Test System. The source system check was OK.
The R3 Test system was refreshed with Production data few days back and now my source system is not working. When i perform Source System check it says:
BI unknown in source system
BI IDoc type ZSSB006 is not the same as source system IDoc type
I performed following steps in R3 Test system after its system refresh:
1. Created logcal system and created RFC.
2. Created port in trx we21.
3. Created partner profile in trx we20.
4. For the outbound parameter RSSEND, I had to create idoc type that should be same as in my SCM system i.e. ZSSB006.
5. Created idoc type using trx we30 as a copy of RSSEND and added entry in table EDIMSG. Now, i could also create outbound parameter RSSEND with idoc type ZSSB006.
After performing the above steps i also replicated the datasources for the R3 Test source system, but its still showing above error.
I also checked the RSBASIDOC table in SCM test system. It has correct entry for my source system. But there is no such entry in RSBASIDOC table in the R3 test system.
Someone pls help me.
Regards,
Chintan

Hi Chintan,
Can you please check IDOC in your Target system. It should be the same type. Better you do the Partner profile steps.
Also please check have correctly created the idoc in Inbound or Outbound.
Consider the case like if its exist in BW as Out bound then its connected to Inbound IDOC of R/3 and vice a versa.
Please elaborate your refresh activites. Normally IDOC setting never get changed in you refresh activites.
Just check your BW system patch level and search for Notes.
Regards,
Mahesh

Logical system names after system copy for SAP ECC 6.0

Hi!
We successfully installed SAP ECC 6.0 system as system copy.
All the logical system names of old system have been copied to new system.
Question
What is the approach to change the logical system names for new SAP system?
a) just via tcode SCC4
b) via BDLS
c) other tcodes, reports
Thank you very much!
regards
Jürgen

I think you can do it through BDLS

Incorrect Source System name after System Copy

Hello Friends,
When we copied Source system from Production to our Qulaity system, the DTP s are still displaying Production Source system.
We are in BI7.0 SP13 . I have run TC BDLS to convert Old Source system to new Source system.
But still displaying Old source system .
Please help me with this Issue .
Any advice appreciated .
Thanks

Hi,
Take a look at OSS notes below.
o 184447 Building a BW-system landscape
o 121163 BDLS: Converting logical system names
o 369758 BDLS: New functions and better performance
o 524554 Storing destinations in the BW environment
o 325470 Activities after client copy in BW source systems
o 538052 Maintenance of Myself destination in BW
o 305527 Details for correct BW Source System Connection
o 325525 Copying and renaming systems in a BW environment
o 184971 Notes on BW source system connections
o 184754 Procedure after BW database copy
o 305527 Details for correct BW Source System Connection
o 547314 FAQ: System Copy procedure
o 140276 Error in source system assignment
Regards.

Rescue & Recovery system lost after system restoring

Hi,
I have a X61 7673-a22 and my RnR environment is now the latest edition.
Yesterday I had a factory state restore and I cannot find my RnR within Vista. I downloaded the installation package from the support site but it cannot be installed as my existing RnR environment is newer than the one I downloaded!
Hmm... as the download site is quite messy, I downloaded the latest one I found, but not necessarily the lastest one provided.
Without the RnR installed in my Vista I cannot make backups of my new system. Any help or information is appreciated, thank you!
Message Edited by zkJoker on 04-24-2009 09:06 PM

S1nfullman wrote:
As a last ditch effort to solve a problem I was having I did a complete wipe and os x leopard reinstall. That part went fine but when I did the restore from time machine it keeps hanging on the last step of transfering information. It gets stuck on less than a minute remaining transfering files to support applications. I tried to restart it and then restore again but it says the disk is too full so I'm guessing files are there but bringing the system up without restoring doesn't let me access my information. I tried the whole process again and the same thing happens.
I'm desperate here. My system is unusable and I can't access my files. Any ideas on how I can get past the final hang or what might be wrong?
no idea. if you can't make the automated migration from TM work I suggest you do an erase and install and migrate what you need from the TM backup by hand.
see this link on what to restore from your home directory
http://discussions.apple.com/message.jspa?messageID=6185507
you'll also have to reinstall your apps.
I'm running an original MacBook pro.

Operating system problem after system recovery

i have PURCHASED HP-ENVY-M6-1125DX (IN-USA) IT CAME WITH - WINDOWS8 OS .(BOUGHT IN BEST BYE)
RECENTLY I UPGRADED TO WINDOWS8.1 PRO PREVIEW. SINCE THIS VERSION OF OS WAS ASKING THE ACTIVATION KEY,
I HAVE RECOVERED MY LAPTOP TO FACTORY SETTINGS BY USING RECOVERY PARTITION PRESENT IN MY HARDDISK.
BUT NOW THE OS IS WINDOES 8 BUILD9200, AND THIS OS IS ALSO ASKING FOR ACTIVATION KEY.
PLEASE HELP US IN SOLVING THIS PROBLEM.

Hello Mahantesh-uppin,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I understand that you are having issues reactivating your Windows 8 Product Key after a factory recovery. I would recommend that you review and follow the instructions in the HP Support document: Windows 8 Product Activation. This document will walk you through reactivating your Windows 8.
I hope I have answered your question to your satisfaction. Thank you for posting this issue on the HP Forums. Have a great weekend!
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
Dunidar
I work on behalf of HP
Find out a bit more about me by checking out my profile!
"Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

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

Logical System Conversion after system refresh failed

Similar Messages

Maybe you are looking for