Source system copy

hi all,
my question is
i need to make a copy of source system,i.e make a copy,then what will happen to my delta?
whether i have to initialize this delta again?
regards,
nnpr

If you have copied the BW system and also the source system at the same time, the delta points should be set there. So you don't need re-init again.
If the source system is not copied then you don't have the option except reinit delta.
Procedure: You need to do reinit without data transfer and in order to reinit, you have to delete the existing one, otherwise, it won't let you do it.
Hope it helps..

Similar Messages

Problems Delta Extractor after Homogeneous Source System Copy

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

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

We would like to test old deltas from the source system( copied to new)

Hi Gurus,
The scenario is
They will make a DB copy of the Prod system onto a QA system, the Copied system will have
its system ID changed(SID) to a new one.
There will be deltas available in the RSA7, as this is a copy of the 3 weeks old prod
system. Now the delta's will be available on the Copied system pointing to the BW Prod system.
We would like to test these delta's to BW Dev. why we would like to do the delta's to the
BW dev system is to check whether we can do system copies without clearing the delta's on
the source system.
After the system copy we will do all the activities necessary to reflect the system changes
a. Like BDLS, We20, we21,ALE checks, RFCDES, RSLOGSYSDEST, RSBASIDOC, etc on the source system to
reflect the changes of the BW Prod system to BW Dev system.
b. Likewise, we will perform all the above activities on the BW dev system by changing the
existing source system to the new source system( performing BDLS,we0, we21, etc)to reflect
the new Source system with the new (SID).
c. We will check the source system connection
d. Replicate the datasources on the new source system
e. Activate the Transfer rules for the new source system.
Now for us to do delta's from the new source system to the Bw dev system we need to change
underlying tables in source system to point the delta's, arfc TID's etc to the BW dev system.
We can change the entries in the TRFCQOUT, ARFCCSTATE, ARFCDATA tables to point the LUW's and
destination to the BW dev system.
What I presume is if we run the BDLS on the Copied system to change the BW prod system to BW
and also the underlying Tables for the LUW's and etc will still be pointing to BW Dev. I would
like to know if this is the case .
Lastly, appreciate if anyone can say if this is possible to do without having to clear the
BW delta queue on the source system.

Hi Ramesh,
Appreciate a lot for your response, but i would like to know if we can reflect the entries in table RSSDLINIT(Last Valid Initializations to an OLTP Source) and RSSDLINITSEL(Last Valid Initializations to an OLTP Source) in the BW system on the copied source system
tables ROOSPRMSC(Control Parameter Per DataSource Channel), ROOSPRMSF(Control Parameter Per DataSource Channel) by executing the ABAP program RSSM_OLTP_INIT_DELTA_UPDATE after we do the BDLS conversion on the new copied source system.
After the BDLS conversion I reckon the entries in the RSA7 queue, ARFCCSTATE, TRFCQOUT tables willl reflect the BW Development system instead of the BW Production system isnt it.
response much appreciated.
Kalyan

Mixed (Java & ABAP w/different sources) System Copy Failed- NW 7.0 SR3/SP14

Hello SAP Friends! Our NW admin did a dual stack system copy where the ABAP server came from system 1 and the Java server came from system 2. This worked fine for ABAP (duh it was installed first), but the Java system copy was a disaster. the server started but many key services did not.
Why?
Many of the configuration entries were not generated properly. For example, a new, unknown SID was created, and many entries referenced System 1 (the ABAP source, not even the Java source). We were able to find and fix some incorrect config entries, but we still couldn't get all of the services we needed to work.
I think NW is so complicated that such a configuration is probably impossible, but maybe I am wrong.
Does anyone have tips? Or can confirm that this would never work?
The current plan is to install the Java Server from scratch as an add-in, which is less effort than searching through all the config files without any certainty that it will work. Hopefully it will work.
Many thanks in advance.

Hi Matt,
What kind of infos are you looking for? I didn't perform the copy, have just been trying to figure out how to get all of the Java stack's services to start properly. As far as I know, it was done using the standard System Copy wizard. The ABAP server was done as a central instance and then the Java server was copied and installed as a java add-in.
I have asked the admin to post the details to this thread, but it would be helpful if you could mention what types of info and details you are looking for.
Thanks and Best Regards,
John

Question about source system copy for BW

Dear all,
I have a quick question about copying a source system for BW.
We have two clients in the source ERP:
100 Customizing
200 Testing
Our BW is only linked to client 200, so when we now delete client 200 and make a copy from 100 to 200, are we then still able to restore the source system connection so that our extraction will work, or will it fail, as in client 100 I have no BW related (except the cross-client-objects like datasource) information, that can be used for a possible restore of this connection.
What is the procedure in this case?
Thanks,
Andreas

Unfortunately, you will lose your source connection and need to create a new one in R/3. You can use the same source system name in BW, but check the source system connection after the copy (SM59). Also, I would "Restore" the source system (in BW, right-click on Source system in RSA1, and click "Restore") to insure the datasources get replicated from R/3 to BW.
Depending on how much you want your BW and R/3 systems to be in synch, you will need to rebuild all your data providers (cubes/ODS's) from your R/3 system. This means deleting all the data and running the initializations from scratch. At the very least, you will need to rebuild the delta queues.
Curious, if 100 is just for customizing, is there any data in it? Are you just creating a new blank client 200?

Error in the Source system while data loding through Process Chain

Hi,
I am facing issue while data loading for certain extractors through Process chain. Load of 0BPM_WIHEAD, 0BP_LOGHIST, OBPM_OBJREL, 0BPM_DEADLINES(there are 2-3 more extractors) is getting failed daily with message Error occurred in the source system and if we repeat the same it is getting executed successfully.
Regards,
Javed

Hi..
It means that the extraction job is failing in the source system..
Please check the Job log in the source system --> Copy the request nimber --> In the source system go to SM37 --> Give * then the request number......execute --> Check the Job log..
Look there may be multiple reasons behind this....
1) Connection problem : Go to SM59 and test the connection, If you don't have the access in SM59...then go to RSA1 --> Source Systems --> Right click --> Connection Parameters --> Connection Test
2) Or may be work processes are not available and due to which jobs are failing due to time out...
In both the cases you can check with the Basis Team if they can suggest something....or you can change the process chain scheduling time if possible, and schedule it in such a time when less no of jobs are running..
Regards,
Debjani..

Restore source system

.after the Client copy to the source system I want to restore the source system what hapens to the objects which already migrated to BI 7.0 and all the transformations and DTP's created.
Partner profile and IDoc settings

you may wish to check this note
Note 886102 - System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
For more insights-
Client Copy / Source system copy
Note 184322 - Procedure after DB copy of BW source systems
Note 886102 - System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
Note 771209 - NW04: System copy (supplementary note)
Note 89188 - R/3 Source System Copy
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
Hope it Helps
Chetan
@CP..

System copy with NW 7.01 Ehp1 MaxDB hang

Hi
I'm performing a system copy with a NW 7.01 Ehp1 MaxDB from a Dev to QA.
The source system copy was run successfully but in the target system copy, the sapinst keep running and running for days at IMPORT ABAP step (Phase 18 of 27).
I don't know what is going on behind it, no error is reported. In the import_monitor.java.log, I see this:
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 18, failed 0, total 30.
Import Monitor jobs: running 3, waiting 9, completed 18, failed 0, total 30.
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 19, failed 0, total 30.
Import Monitor jobs: running 3, waiting 8, completed 19, failed 0, total 30.
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 20, failed 0, total 30.
Import Monitor jobs: running 3, waiting 7, completed 20, failed 0, total 30.
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 21, failed 0, total 30.
Import Monitor jobs: running 3, waiting 6, completed 21, failed 0, total 30.
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 22, failed 0, total 30.
Import Monitor jobs: running 3, waiting 5, completed 22, failed 0, total 30.
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 23, failed 0, total 30.
Import Monitor jobs: running 3, waiting 4, completed 23, failed 0, total 30.
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 24, failed 0, total 30.
Import Monitor jobs: running 3, waiting 3, completed 24, failed 0, total 30.
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 25, failed 0, total 30.
Import Monitor jobs: running 3, waiting 2, completed 25, failed 0, total 30.
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 26, failed 0, total 30.
Import Monitor jobs: running 3, waiting 1, completed 26, failed 0, total 30.
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 27, failed 0, total 30.
You can see, the sapinst is getting stuck on the last 2 jobs. I waited it for 3 days and nothing happen.
Anybody has the same problem? What else that I can check ?
Thanks
Halomoan

Problem get solved !
With SAP Note: Note 941635.
Thanks,
Halomoan

Process to setup new R3 Source System

Hi, there seems to be a lot of posts out there regarding this topic, but I can't seem to get a specific answer out of it all?
I am adding a new R3 Source System (R2) to my BI System in addition to the existing R3 Source System (R1). I would like all of my BI Objects to have the same connections (Transformations, etc.) to my new R3 Source System (R2) that I currently have for my R1.
What do I have to do to make this happen? Is there a defined process for this?
Do I have to manually copy the transformations for everything? (This would be sooo difficult due to volume)
Please add clarity to this situation if you can...
Thanks!

Hi,
take a look:
Fresh source system clients in production BW system
Fresh source system clients in production BW system
Threads are about fresh source system clients but maybe they are useful for you.
Additional:
Change Source System
Copy Transfer Rules
This doesn't seem like an uncommon scenario. Surely I don't have to manually recreate all of these datasource transformations?
In my mind you have to recreate if you are not using standard BI Content which you only have to activate.
Regards
Andreas

System copy tools for SAP Basis 46C.

Hi All,
I need to do system copy for SAP Basis 46c. I have a query regarding the tools used for system copy. It is written in the SAP Documents and we need to use the latest version of the system copy tools (i.e. R3load,R3check,R3ldctl,,R3szchk,R3trans).
I need to do the Heterogeneouse system copy
Source :- Oracle 9.2.0.8 , AIX 5.3
Target :- Oralce 9.2.0.8 (Or 10.2.0.4 if possible) , Sun Solaris
So my question is
1) Am i suppose to use only the tools (i.e. R3load,R3check,R3ldctl,,R3szchk,R3trans) which are compatible to relase 4.6C (Kernel 46D_EXT, latest path level is 2541) or
2) Can i download and use the Latest version of system copy tools (i.e. Withe release 7.00 for R3load,R3check,R3ldctl,,R3szchk,R3trans) to do the herogeneous system copy of SAP Basis 4.6C ??
Please reply.
Thanks

> Yes we are aware about the certified consultant. But before going for such a big project we wanted to find out the possibilities how we can minimise system downtime and optimize the process therefore wanted to have some information earlier.
Exactly that is the use of that consultant Those are experienced people who have done lots of migrations in the past, they know the possibilities of the tools and versions.
> So now i am very sure that we can use 10.2 while installation of new target system while doing heterogenouse system copy from oracle 9.2.
Correct.
> 1) Migration Monitor (source :-System copy & Migration optimization.pdf)
> The Migration Monitor is downward-compatible. As new features and bug fixes are only implemented in the latest version, SAP urgently recommends that you always use the latest version available.
You can use it of course but support of it is not "built in" - there's no clicker to check as is in newer versions of sapinst. You will need to modify the R3S file at the "correct place" to make use of it.
> 2) Distribution Monitor (Source :- Distribution Monitor (version 1.9.1) Usersu2019 Guide)
> Restrictions:-The following restrictions apply to the current implementation:The DM does not support system copies of releases lower than SAP_BASIS 6.20
So you can't use that option.
> 3) PACKAGE SPLITTING (source :-System copy & Migration optimization.pdf)
> The package splitting option is available and integrated into the system copy tools R3SETUP and SAPinst since SAP R/3 4.0B SR1.
The "old version" is a perl script, you'll need to make sure you have perl installed.
>
> 4) TABLE SPLITTING (source :-System copy & Migration optimization.pdf)
> AVAILABILITY:
> Table splitting can be used for ABAP systems with SAP kernel 6.40 or above
So that is also not usable.
> 6) R3LOAD OPTIONS - (source :-System copy & Migration optimization.pdf)
> R3load option '-fast' (<= 4.6D) or '-loadprocedure fast': These options are available
> u2022 from SAP kernel release 6.40 for - DB2/UDB - MSSQL - Oracle (see SAP Note 1045847 - Oracle Direct Path Load Support in R3load)
So it's also not built in for Kernel 46D_EX2.
> Request your final comments on the above points and Need to know whether parallel import and export can be done for 4.6C (46D_EXT Kernel) release using migration monitor. Please reply.
As I said before and as is written in the documentation, it can be used but not "by default", you'll make sure you stop at the right place with your migration to configure it manually (or the consultant will do).
Markus

PI 7.11 sp6 system copy causes target sys to register with source

Experts,
We have a PI 7.1 (EHP1, sp6) PI system based on AIX 6.1 OS and Oracle 11g.
I recently did the standard PI system copy from a prod source (PIP) to a training target (PIT).
I used the most recenty PI system copy guide that is specific for PI 7.1 EHP1
I did not run into any major problems doing the steps of the itself.
I did the usual "post" steps, documented in the guide that really are done on any NW system.
Then I got into the specific "PI" post steps and that's where I now have a problem.
I could not run the "wizard for post copy" since I'm on 7.11sp6. Yes, I know they "downported" it but I don't have those latest LMtools type packages. Anyway, I'm OK with that.
I followed all the steps, fixing my RFCs, JCos, Destinations, cleaning up SLD, SLDAPICUST, creating new business systems...etc.
My big problem is with the exchange profile. Yes, it's easy to change all the SIDs and hostnames using the search tool for all the parameters in the exchange profile, but the one I COULD NOT CHANGE was the "ABAP Connection". In there right after the copy was the hostname of the prod system, the client, and the user PILDUSER. I attempted to put the hostname of my target (PIT) system, but I would get the error:
RFC 399 unable to connect
I'm certain the user is NOT locked and the password is correct for PILDUSER.
Worse yet, If I left the hostname in there that was set to "prod", then when I changed all the other values in the "parameters" section of the XI profile, then it actually changed my PROD system!!
If I keep the ABAP connection to PIT, then the entire exchange profile disappears for PIT.
Also, now my PROD system shows the PIT system as a "non-central adapter engine".
Ughh! I'm totally stuck. I'm not sure what to do.
It's as if the PIT (PI training) system somehow is linked to PIP (PI prod). It's like PIT doesn't think he is his own box...
Any ideas? I'm resisting opening a message because this will be so hard to explain to sap support.
--NICK

Hi Nick,
We went thru the same issue. Fortunately, it was between Dev to sandbox. I stopped the dev system and changed the exchange profile parameters to sandbox hostname and brought the Dev up to fix the issue.
Prod showing as Non-Central Adapter engine :- Check your Business System in SLD and In CIM Instances in SLD, check your XI Integration server assigned to right Business System.
Note 764176 - Error in XI due to inconsistent SLD contents :- helped me come over PI post step issues.
Thanks,
Arjun

No username of Source system is avbl after livecache system copy

Hi Experts
I have done a livecache system copy from the source system to target system. Here the steps are
Assume my Source SYstem Livecache is RP1 and Target System livecache is RS1.
1. Taken Source system livecache DATA and LOG Area backup RP1.
2. Defined the same source system backup medium name in Target System (RS1 and moving the Source system Liveacache backuped files to Target system and defined the medium name as per that)
3. put the livecache db_admin mode
4. db_activate RECOVER <medium_name>.
5. recover_start <log_medium_name> LOG <nnn>
6. db_online.
Here we faced that
ERR
-24622,ERR_AUTOLOADSYSTAB: Automatic loading of the System Tables failed
-24907,ERR_DBAWRONG: Wrong database system administrator
-24988,ERR_SQL: SQL error
-4008,Unknown user name/password combination
So we activated the SUPERDBA as " db_activate SUPERDBA,<password>
then it came to online. and afterwards we have used the load_systab command to load the tables.
BUT we could not find any Source System name like "RP1ADM" in the tables of the livecache database. Only there are CONTROL,SUPERDBA username availbale. Usually there will be also the source admin name . I dont know why it is missing
Before a month we have done livecahe restore same as now in that time we got the source system name admin also. ( RP1ADM) and also tables which owned by RP1ADM. alos i could find APPSYSPARAM table and the instance also registered.
But now in this restore we could not find the above.
We followed the same procedure and there is no change in the steps also.
Could anyone help me...
Regards
bala

Hello Bala,
1. As I wrote you already, the notes:
886103 System Landscape Copy for SAP SCM
877203     Post steps after the Homogenous liveCache copy using backup/
457425     Homogenous liveCache copy using backup/restore
has all recommended steps to do, when you will run the u201CSystem Landscape Copy for SAP SCMu201D
2. If you run the u201CHomogenous liveCache copy using backup/restoreu201D you should pay attention to the note 457425. After you imported the complete data backup < step 2. > you need to update the system tables.
To update the system tables you need to know the correct database SYSDBA user & password.
After you restored the databackup of the source database, start the database online & run u201Cselect * from usersu201D SQL command to see the SYSDBA user. Then check that you know the DBA user ( DataBase Administrator ) & password of the source database instance => Open the SQL session with this
user & password.
Example:
after db_activate recover <medium_name>
login as control,password
db_online
sql_execute select * from users
sql_connect superdba,<password of source system>
If you didnu2019t get error with the last command, then you could update the system tables with the superdba,<password of source system> using load_systab command.
The system tables will be updated & the correct SYSDBA user & password will be updated in *.UPC file.
3.
user_sysdba:
You make the database system administrator known to Database Manager. It is only necessary to use this DBM command if the database administrator is not known or is incorrectly known to Database Manager.
u201CI have tried like this
after db_activate recover <medium_name>
login as control,password
db_admin
user_sysdba superdba,<password of source system>
db_onlineu201D
You could update the .upc files with the wrong SYSDBA user password u2026
You was lucky, that you knew the correct SYSDBA user and password of the source database.
Example < NLK is my local database >:
A.     I could update the .upc file with wrong password of SYSDBA user:
dbmcli -d NLK -u control,control
dbmcli on NLK>user_sysdba superdba,test
OK
dbmcli on NLK>db_online
OK
dbmcli on NLK>load_systab
ERR
-24909,ERR_DBAUNKNOWN: SYSDBA unknown
dbmcli on NLK>exit
B. I could update the .upc file with wrong SYSDBA user:
dbmcli -d NLK -u control,control
dbmcli on NLK>user_sysdba test,test
OK
dbmcli on NLK> user_get test
OK
u2026
dbmcli on NLK>sql_connect test,test
ERR
-24988,ERR_SQL: SQL error
-4008,Unknown user name/password combination
dbmcli on NLK> dbmcli on NLK>sql_connect superdba,admin
OK
I could connect as test,test; but the test user is NOT SYSDBA user u2026
dbmcli -d NLK -u test,test
dbmcli on NLK>
Itu2019s recommended to user the load_systab command, so the .upc files will be updated with the correct SYSDBA user/password or
you will get error.
4. http://maxdb.sap.com/doc/7_7/86/68627a1bc642e6a6f73d3bc7a55fe1/content.htm
You got error:
ERR
-24622,ERR_AUTOLOADSYSTAB: Automatic loading of the System Tables failed
-24907,ERR_DBAWRONG: Wrong database system administrator
-24988,ERR_SQL: SQL error
-4008,Unknown user name/password combination
The automatically updating the system tables, according to the default value, is switched on.
After you will run the update system tables with the correct SYSDBA user & password the *.UPC file will be updated,
and with the next liveCache restart you will not get this error.
5. See more information in the MAXDB library:
http://maxdb.sap.com/doc/7_7/45/11cbd6459d7201e10000000a155369/content.htm
Thank you and best regards, Natalia Khlopina
Edited by: Natalia Khlopina on May 19, 2010 2:58 PM

Extraction failing after source system and client copy

Hi all,
We refreshed our source QA system with a copy of production. And basically tried to "restore" the connection from our BW QA system. Some of the datasources can be extracted from BW, others fail with an error of "No transfer structure is available for InfoSource 0COSTCENTER_ATTR in the source system".
Trying to do the same thing with RSA3 in the source system, works fine.
The strange thing is it works for some objects but not others.
here's what we did:
1. System copy from R3 Prod to R3 QA
2. Client copy with R3 QA client 300 -> 200
3. Restore connectivity in BW QA to the R3 QA system (Using RSA1 -> Source System -> Restore)
4. Now some objects can be extracted in BW, others fail as I mentioned above.
I have regenerated the transfer structures in BW and R3.
All of these objects that don't work seem to work in RSA3 on the R3 system but not in RSA1 on BW.
All the SAP documentation is geared to copying the R3 source system and then restoring connectivity between BW and R3. I don't think any of it involves copying the client in the R3 source system - which might be causing our problems.
We are using an SAP delivered PDF and note 886102 mainly for direction.
SAP PDF is "How to... System Copy in SAP Business Intelligence System Landscapes".
Does anyone have any ideas?
Thanks,
Kevin

Hi,
can you isolate somehow the kind of DataSource which works and those who don't?
Master data / transactional or client dependent and not, delta or full....
To which R/3 client is your BW connected? when you succeed loading the data, is it coming from the right client?
RSA3: do you run it specifying your BW client in the target sys field? does it make a difference if yes or if not?
Are your RFC connections and partner profiles all right?
Check some IDOCs sent by BW received in R/3 and vice-versa (RSSEND, RSINFO, RSRQST..). Load a hierarchy (via IDOC)... verify that your IDOC have the correct partner settings....
let us know
Olivier.
Message was edited by:
Olivier Cora

System copy: RZ21 MTE has source SID and not the target SID

An system copy of PRD to QAS environment has been performed.
Since then receive the following message in the CCMS Monitor sets (trx RZ20):
Unable to determine the name of MTE class from <SID>\Background\...\SAP_SRT_COLLECTOR_FOR_MONITORIN or the message "Failed to determine MTE information for system QAS"
Checked and in the transaction RZ21 the MTE class is pointing to the PRD system and not to the QAS system:
RZ21 -> MTE-specific properties
Monitoring: Properties Assigned to MTEs
RZ21 -> Methods assigned to specific MTEs
Monitoring: Properties and Methods
Unable to determine the name of MTE class from PRD\Background\...\SAP_SRT_COLLECTOR_FOR_MONITORIN
I would expect here the value "QAS\Background\...\SAP_SRT_COLLECTOR_FOR_MONITORIN".
How can I adjust the MTE to check the QAS instead of the source system PRD ?

Received following answer from SAP:
we can find out the follow errors from the dev_disp developer trace file you attached.
ERROR => e=13 semop(1048668,(0,-1,4096),1)
(13: Permission denied) [semux.c 1196]
ERROR => CCMS: AlCreateAttachShm_AS : lock semaphore return 1
[alxxappl.c 665]
ERROR => CCMS: sAlInit: could not create/attach shared memory key 13(rtc = 1) [alxx.c 1187]
ERROR => AlDpAdmInit: sAlInit rtc = 1 [alxx.c 514]
ERROR => DpLoopInit: AlDpAdmInit [dpxxdisp.c 2033]
The shared memory area 13 is the one that is responsible for the alert area.
An error within that area could cause the problem that you are facing when opening monitoring trees.
If we look at your OS, we can see that the semaphore for this area is currently being held by the root user:
[1]ipcs | grep 1048668
s 1048668 0x00004e46 ra-r root system
You need to delete this area with root user using ipcrm and restart the instace or to reboot the OS and start the instance once again.
Performed these actions and the issue was solved.

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.

Source system copy

Similar Messages

Maybe you are looking for