Data Replication Problem

Hi Friends,
In my MAM application,
<b>AT MI CLIENT:</b>
I can see only <b>USER VIEW MANAGER</b>
According to the <b>"TroubleShoot Guide for Smart Synchronization",</b> the reason is that I am not getting the <b>"User Customizing Data",</b> in the table <b>MEREP_207</b> for syncBO MAM25_090,
<b>AT MI SERVER:</b>
I checked the table <b>MEREP_207</b> and really it contains replicated date only for MAM25_016 (Profile Data) though I have started the replicator for all Timed 2-way syncBO's.
So I tried to replicate again as suggested by the Troubleshoot Guide. But the problem was not solved.There was no change in the contents of the table MEREP_207.
<b>AT BACKEND:</b>
Instead the function module <b>MAM25_090_GETDETAIL</b> from backend is giving the required output, that means the customizing data is lying at the Backend.
I dont know why the data is not getting replicated from <b>Backend to MI Server (In Table MEREP_207).</b>
Please suggest what can be the problem in getting the data replicated from backend to MI Server,
The help will be highly appreciated,
Thanks
Deepak

Hi Nameeta,
Thanks for the reply,
But I dont have any jobs scheduled, I am replicating manually through merep_ex_replic which is showing 0 DB Records replicated each time,
SyncBO are already generated and enabled.
and RFC Destination is working fine!
Any other clue???
Regards,
Deepak

Similar Messages

  • Data replication problem in SRM using inbound idoc FM IDOC_INPUT_HRMD

    Hello Experts,
    We are using FM IDOC_INPUT_HRMD for replicating HR data in SRM 5.0.
    Now the data which was passed to port is in insert mode i.e in transaction PFAL we are passing Idoc in Insert mode.
    So this means whatever data exist in target system that should be overwritten by this new Idoc data.
    The Idoc which is created in target system (in SRM) is in status 52 & message is 'Business Partner already exist',
    So data is not posted in system due to this error.
    Idoc details as below:
    Process code:HRMD
    FM: 'IDOC_INPUT_HRMD'.
    Could you please help in this?
    regards,
    Amol'

    Hi
    Authorizations might be one of the reason.
    So IDOC transfered but no records to be writeen to DB.
    regards
    vijay

  • Data Replication Between Sqlserver and Oracle11g using materialized view.

    I have Sqlserver 2005 as my source and oracle11g as my target.I need to populate the target daily with change data from source.
    for that we have created a dblink between sqlserver and oracle and replicated that table as a Materialized view in Oracle.
    problem we are getting here is Fast refresh option is not available.each day it will pick full data from the source.
    is there any way to use Fast refresh in this scenario??
    Thanks in advance.
    Regards,
    Balaram.

    Pl do not post duplicates - Data Replication Between Sqlserver and Oracle11g using materialized view.

  • How can i solve this replication problem between TT and ORACLE

    Hi
    I have an application that using AWT cashgroup implement the replication between TT (7.0.6.7) and ORACLE(10g);
    but i encounter this problem:
    16:16:50.01 Err : REP: 2302682: ABM_BAL_WH:meta.c(4588): TT5259: Failed to store Awt runtime information for datastore /abm_wh/abm_bal_ttdata/abm_bal_wh on Oracle.
    16:16:50.02 Err : REP: 2302682: ABM_BAL_WH:meta.c(4588): TT5107: TT5107: Oracle(OCI) error in OCIStmtExecute(): ORA-08177: can't serialize access for this transaction rc = -1 -- file "bdbStmt.c", lineno 3726, procedure "ttBDbStmtExecute()"
    16:16:50.02 Err : REP: 2302682: ABM_BAL_WH:receiver.c(5612): TT16187: Transaction 1316077016/357692526; Error: transient 0, permanent 1
    the isolation level of my date store is read-committed ,and the sys.ODBC.INI file is also set Isolation=1(readcommitted mode)
    so ,I still wonder how the error ORA-08177!
    how can i solve this replication problem?
    thank you.

    I suspect this is failing on an UPDATE to the tt_03_reppeers table on Oracle. I would guess the TT repagent has to temporarily use serializable isolation when updating this table. Do you have any other datastores with AWT cachegroups propagating into the same Oracle database? Or can you identify if some other process is preventing the repagent from using serializable isolation? If you google ORA-08177 there seem to be ways out there to narrow down what's causing the contention.

  • Session in-memory replication problem

    Hi,
              I am running into some cluster HttpSession replication problems. Here is
              the scenario where replication fails (all servers mentioned here are a
              part of a cluster).
              1a - 2 Weblogic servers (A&B) are running - no users logged in,
              2a - user logs in and a new session in server A is created.
              3a - after several interactions, server A is killed.
              4a - after user makes susequent request, Weblogic correctly fails over
              to server B
              Problem: Not entire session data is replicated. The authentication info
              seems to
              be replicated correctly but there are some collections in the session of
              server A
              that did not make it to the session in server B.
              The interesting part is this: If there is only one server A running to
              begin with and a user
              interacts with it for a while and only then server B is started, when
              after server B starts up
              server A dies - the entire session (which is exactly the same as in the
              failing scenario) is
              corretly replicated in B, including collections that were missing in the
              failing scenario.
              How can this be possible ????
              Thanks for any info on this one - it really puzzles me.
              Andrew
              

    Yes, you are on the right track. Everytime you modify the object you should call
              putValue. We will make it more clear in the docs.
              - Prasad
              Andrzej Porebski wrote:
              > Everything is Serilizable. I get no exceptions. I did however read some old
              > posts regarding
              > session replication and I hope I found an answer. It basically seems to boil
              > down to what
              > triggers session sync-up between servers. In my case , I store an object into
              > session and
              > later on manipulate that object directly wihotu session involvment and the
              > results of those manipulations
              > are not replicated - no wonder if HttpSession's putValue method is the only
              > trigger.
              > Am i on the right track here?
              >
              > -Andrew
              >
              > Prasad Peddada wrote:
              >
              > > Do you have non serializable data by any chance?
              > >
              > > - Prasad
              > >
              > > Andrzej Porebski wrote:
              > >
              > > > Hi,
              > > > I am running into some cluster HttpSession replication problems. Here is
              > > > the scenario where replication fails (all servers mentioned here are a
              > > > part of a cluster).
              > > > 1a - 2 Weblogic servers (A&B) are running - no users logged in,
              > > > 2a - user logs in and a new session in server A is created.
              > > > 3a - after several interactions, server A is killed.
              > > > 4a - after user makes susequent request, Weblogic correctly fails over
              > > > to server B
              > > >
              > > > Problem: Not entire session data is replicated. The authentication info
              > > > seems to
              > > > be replicated correctly but there are some collections in the session of
              > > > server A
              > > > that did not make it to the session in server B.
              > > >
              > > > The interesting part is this: If there is only one server A running to
              > > > begin with and a user
              > > > interacts with it for a while and only then server B is started, when
              > > > after server B starts up
              > > > server A dies - the entire session (which is exactly the same as in the
              > > > failing scenario) is
              > > > corretly replicated in B, including collections that were missing in the
              > > > failing scenario.
              > > >
              > > > How can this be possible ????
              > > >
              > > > Thanks for any info on this one - it really puzzles me.
              > > >
              > > > Andrew
              > >
              > > --
              > > Cheers
              > >
              > > - Prasad
              >
              > --
              > -------------------------------------------------------------
              > Andrzej Porebski
              > Sailfish Systems, Ltd. Phone 1 + (212) 607-3061
              > 44 Wall Street, 17th floor Fax: 1 + (212) 607-3075
              > New York, NY 10005
              > -------------------------------------------------------------
              

  • BP Replication Problem v2  (CRM 5 - ECC 6)

    Hi¡¡¡¡
    I’m trying to replicate BP between CRM 5 ->> ECC 6, but not successful. I just get replicating BP’s but is not  creating a customer in the ECC system.
    I have maintained all steps mentioned in building block - C03 (CRM Master and Transaction Data Replication). I have maintained separate account group approach.I have defined an account group Z001 for customers that are created in the CRM system and have to be replicated to the ECC system (external number assignment in the receiving system).I made sure that number ranges are in sync in both the systems. Particularly in PIDE, mapping classification Customer 'B'  and Consumer “E” to 'Z001'.
    In the SMW01, the BDoc is green.
    Please help me to resolve this problem. I am in real urgency.
    Thank’s
    Jose Alvarez
    [email protected]
    Santiago, Chile

    Laercio,
    Your business partner grouping in CRM is setup wrong.  The ZLEV that corresponds to the R/3 CLEV should actually be setup as an external number range in CRM.
    The way this working is the following:
    If the number originates in R/3 then CRM must use an external number range
    If the number originates in CRM then R/3 must use an external number range.
    So your CLEV account group should map to a CLEV partner grouping in CRM and the ZLEV must map to ZLEV grouping in R/3.
    The CLEV in R/3 will be internal numbering
    The ZLEV in R/3 will be external numbering
    The CLEV in CRM will be external numbering
    The ZLEV in R/3 will be external numbering.
    I believe if you do this, then it should allow you to keep the numbers the same for those two account groups.
    For issue two:  You need to make sure that all your sales areas are setup and the tuples are defined per sales area.  Once the tuples have been defined and attributes setup on the organizational units, then you can do another initial load and the sales area should come over again.
    Good luck,
    Stephen

  • First Hit Session Data Replication

    We are using WLS 5.1 with sp3 in a cluster of three
              servers using in-memory-rep, JSP, and Apache as our proxy.
              Session data replication between a primary and secondary server
              seems to work fine except in the following case:
              1) Make first hit to the cluster. During the JSP processing of
              that hit set some HTTP session data via setAttribute().
              2) Kill-off the primary server (the one that handled the first hit).
              3)Make a second hit to the cluster, it is handled by another
              server (the secondary), the session is recognized as an ongoing
              session however the session data that was set during the first hit is not
              present in the second hit.
              If we make two hits to the first server and set data, then kill-off
              the primary server, the secondary has the data at the third hit. The
              only issue seems to be when the primary is killed after the first hit.
              Anyone have any ideas?
              Thanks,
              -darren
              

    You can configure ClusterServlet in your web server farm (WLAS as web
              servers) to proxy JSP and servlet requests to the WLAS farm (WLAS processing
              your JSP and servlet).
              Set up in-memory replication in your WLAS farm. Session in JSP will be
              replicated.
              Cheers - Wei
              Yen Liu <[email protected]> wrote in message
              news:[email protected]...
              > Hello,
              >
              > I read breifly the section on BEA's online documentation talking about
              in-memory
              > replication and clustering.
              >
              > In it, it mentioned the ClusterServlet and configuring the
              weblogic.properties
              > file to assign servlets to the ClusterServlet so that sessions will be
              handled
              > correctly and all.
              >
              > My question is, "what about JSP" I am using a lot of JSP pages which sets
              > session parameters for the specific user into session objects.
              >
              > Any tips, recommendations will be most helpful.
              >
              > Thanks,
              >
              > Yen Liu
              > 510/870-1169
              >
              > Prasad Peddada wrote:
              >
              > > Darren,
              > >
              > > It shouldn't be the case. After your first hit, when you kill the
              primary
              > > server, when you make your next request you should find all the info in
              the
              > > session. I will post again, if we find the same problem on monday in our
              test
              > > environment.
              > >
              > > Thanks
              > >
              > > Prasad
              > >
              > > Darren Kessler wrote:
              > >
              > > > We are using WLS 5.1 with sp3 in a cluster of three
              > > > servers using in-memory-rep, JSP, and Apache as our proxy.
              > > > Session data replication between a primary and secondary server
              > > > seems to work fine except in the following case:
              > > >
              > > > 1) Make first hit to the cluster. During the JSP processing of
              > > > that hit set some HTTP session data via setAttribute().
              > > > 2) Kill-off the primary server (the one that handled the first hit).
              > > > 3)Make a second hit to the cluster, it is handled by another
              > > > server (the secondary), the session is recognized as an ongoing
              > > > session however the session data that was set during the first hit is
              not
              > > > present in the second hit.
              > > >
              > > > If we make two hits to the first server and set data, then kill-off
              > > > the primary server, the secondary has the data at the third hit. The
              > > > only issue seems to be when the primary is killed after the first hit.
              > > >
              > > > Anyone have any ideas?
              > > >
              > > > Thanks,
              > > >
              > > > -darren
              >
              

  • HR link replication problems (ALE)

    Dear experts:
    We are facing a problem with HR to CRM Employee replication.
    The replication of some links is not working.
    We detected that the links replication (HRP1001) CP-OS are not working for those employees which are replicated in CRM with an alias (relation 207, u201CIs identical tou201D) with different number from HR personal number.
    I give some examples to illustrate the problem:
    One employee replication which is working well shows in HRP1001 this:
    OTYPE OBJID      PLVAR RSIGN RELAT ISTAT   .....  SCLAS SOBID
    CP    00000477   01    B     207   1         ...   BP    0000000477
    Note that SOBID number and OBJID are the same
    One employee replication which is not working well shows in HRP1001 this:
    OTYPE OBJID      PLVAR RSIGN RELAT ISTAT   .....  SCLAS SOBID
    CP    50000112   01    B     207   1              BP    0000001524
    Note that SOBID number and OBJID are not the same.
    Since the OBJID number 50000112 seems an internally generated number, I looked at number ranges, and I realized that for some reason, the system is giving internal numbers to some employees, taken from the number Object  RP_PLAN, Subobject is 01$$.
    The replication of the links related to the Employees with an alias with internal number is not working, the others are working well.
    Has anyone some idea of how to face this problem?
    Thank you in advance.
    Jordi

    A CAS and eight primaries: just being curious: how many clients are you managing in total?
    See
    http://blogs.technet.com/b/umairkhan/archive/2014/02/18/configmgr-2012-data-replication-service-drs-unleashed.aspx and
    http://blogs.technet.com/b/umairkhan/archive/2014/03/25/configmgr-2012-drs-troubleshooting-faqs.aspx for troubleshooting.
    Torsten Meringer | http://www.mssccmfaq.de

  • Data replication offline/online

    e have a java application which has to work both in off-line and
    on-line mode.The application is in two tier architecture and the
    environment is : Forte(IDE),JVM 1.3.0 Hotspot,JDO,pointbase
    embedded for offline mode and oracle 8.1.7 for on line mode
    (behind a firewall).The user can choose to work in offline mode
    and the data has to be moved/replicated to the online DB as soon
    as the user connects with the server in online mode next time.
    We have the following problems.
    1)The replication of data from offline to online is not working-
    mainly due to firwall.We cannot have a workaround by allowing
    all users thro'firewall.
    2)Forte /JDO do not support oracle lite(in place of point
    base).We are not able to convert the persistent classes to jar.
    3) Switching over to 3 tier architecture/ JDBC(replacing JDO)
    may solve some problem but involves lot of effort.
    -Is there any other suitable database?
    -Is there any other method to overcome this problem?

    What do you mean by 'Online Data replication'? Do you mean the Oracle Advanced Replication or do you mean the Oracle Dataguard?
    Oracle Data Guard Concepts and Administration
    Release 2 (9.2)
    Part Number A96653-02
    Oracle9i Advanced Replication
    Release 2 (9.2)
    Part Number A96567-01
    ~ Madrid

  • Technical master data replication error

    Dear Experts,
    I am facing a problem with the TECHNICAL MASTER DATA replication from ISU TO CRM, Problem is I have completed the initial load  of the TECHNICAL MASTER DATA load is sucessfull issue is when i am creating the NEW TECHNICAL MASTER DATA like connection object and premise they are not moving to CRM immediately every time i am doing the request load or initial load by putting the filters could you please tell me how to solve this issue.
    Thanks & Regards
    Boyz

    Hi,
    Sometimes, the data can get stuck in the queues. So you need to check on it as well.
    After creating the technical master data, please check whether it exist in ISU system.
    Then you can check the SMQ1(Outbound queue) in ISU.
    Then you can check the SMQ2 (Inbound queue) in CRM.
    Also in Tcode SMW01 ( BDoc message) in CRM.

  • DFS Replication Problem

    Hi Friends,
    I have windows server 2003 domain at two location before somw month back its replication data
    and its working fine but now i unable to see replicate data i mean i thing having replication problem
    i gotted some evint id error on server
    Event id error :- 5002  , 4202  , 1925 ,13568
    Please help me .
    Thanks,
    Madhukar

    The 4202 is staging quota size is too small.  
    Run these 2 Power Shell commands to determine the correct Staging Quota size:
    $big32 = Get-ChildItem DriveLetter:\FolderName -recurse | Sort-Object length -descending | select-object -first 32 | measure-object -property length –sum
    $big32.sum /1gb
    Take that resulting number, round it up to the nearest whole integer, mulitply that times 1024 and enter that number on the Staging tab of the Properties of a replicated folder in DFS Mgt.
    More info here:
    http://blogs.technet.com/b/askds/archive/2007/10/05/top-10-common-causes-of-slow-replication-with-dfsr.aspx
    Run this command to tell you the status of Replication:
    wmic /namespace:\\root\microsoftdfs path DfsrReplicatedFolderInfo get replicatedFolderName, State
    0: Uninitialized
    1: Initialized
    2: Initial Sync
    3: Auto Recovery
    4: Normal
    5: In Error
    Let us know how that goes.

  • Data Replication issue for R/3 on i5

    QUESTION:
    1) Do we need the data in following 2 files to be replicated when the production operation runs on
    Stand-by system?
    DBSTATIDB4 Index Sizes in the Database (statistical data)
    DBSTATTDB4 Table Sizes in the Database (statistical data)
    2) If we don't need data in those 2 files when production operation is underway on Stand-by,
    please let us know any considerations if you have.
    BACKGROUND INFO:
    Although our customer has two R/3 system on i5 configured as a production and a stand-by system
    and replicate R/3 production data to stand-by system using data replication tool called MIMIX,
    sometimes we encounter a problem with the data of following files are out of synchronization.
    Files cannot be replicated:
    DBSTATIDB4     F@Index Sizes in the Database (statistical data)
    DBSTATTDB4     F@Table Sizes in the Database (statistical data)
    The reason for that is  because of the new DB function called fast-delete since V5R3.
    This problem happens due to the fact that this function execute ENDJRN/STRJRN and it makes
    problem within MIMIX replication operation.
    In order to avoid this problem, we'd like to make sure that it's possible to eliminate these files
    out of synchronization and need more information for these files.

    Hello Yuhko,
    first of all thank you very much, that you are the first user/customer, that is using this new and great forum !!!
    We will move lot's of further customers into this forum soon.
    Fortunately, yes you can ignore these 2 tables if you like - they are not really interesting for the healthy of your SAP system. But, are you really on the latest PTF Levels of V5R3 - because I know this error and it should be fixed in the meantime - perhaps you need a newer MIMIX version as well - you should at least check.
    Then you could configure to run this "crazy" job not twice a day, but once a week only - that makes even your system faster ... This could be done in ST03 in the collector configuration. It is RSORATDB or RSDB_TDB in TCOLL - depending on your SAP release.
    But again:
    If you want to exclude these 2 tables from replication you are fine as well - but I would make this job even more rarely for better performance.
    Regards

  • MDG-F 7.0 future planned data replication

    Hello,
    From what I have learned, valid from date in Edition can be used to control of timing of the data replication. In my data prototype in MDG-F 7.0, it is clear that GL change request will go with that. In other words, if the valid from date =August 1, 2014 (today=07/15/2014), GL change request won't come into ECC until August 1 2014 is arrived. it is behaved this way regardless of the choise of replication timing I have made.
    Will the same behavior occur to cost center change request and profit center change request?
    Thanks,
    Luo

    Hello Luo
    Yes you can do that but the real problem I faced is that in the edition screen you get the list of all the editions. Users get confused with this.
    Best way is to connect your DEV / Quality systems with resp MDG Dev and Quality. Use automatic replication. Perform the testings in each system. Once you get the approval you can create master data in production a day before go-live. This is working well till now in my case.
    Kiran

  • Date popup problem in APEX 3.1

    Hi
    I have a date picker (DD-MM-YYYY HH24:MI) and after upgrading to APEX 3.1 from APEX 3.0.1 the popup window height is too small.
    The end user is having to resize the window to click on the OK button.
    Is there a file I can edit to increase the height, couldnt find it in templates/themes.
    Regards
    Adam

    Hi Adam,
    This is a bug in APEX 3.1. It was discussed here:
    Apex 3.1 Upgrade Issue - dba_lock and date picker display
    and here:
    Date Picker problem in Apex 3.1
    I'll let Carl investigate and provide an official response and recommendation. Although I know where this problem is occurring.
    The size of the popup calendar window is hard-wired in the file apex/images/javascript/apex_3_1.js. In APEX 3.0, the size of the popup window was determined programatically at runtime and was a function of the date format, if it included a time component or not.
    The uncompressed, readable version of this same file is in apex/images/javascript/uncompressed/apex_3_1.js. Look for p_DatePicker and you'll see what I'm talking about. You'll see the height is hard-wired to 210 and width to 258. In APEX 3.0, the height was set to 255 if the date format contained a time component.
    So my suggestion, until Carl provides an official response, is to look for '210' in apex/images/javascript/apex_3_1.js and change this to 255. Granted, all calendar popup windows will be this big, but it won't put as great a burden on the end-user.
    I hope this helps.
    Joel

  • ORA-01403: no data found Problem when using AUTOMATIC ROW FETCH to populate

    ORA-01403: no data found Problem when using AUTOMATIC ROW FETCH to populate a form.
    1) Created a FORM on EMP using the wizards. This creates an AUTOMATIC ROW FETCH
    TABLE NAME - EMP
    Item Containing PRIMARY KEY - P2099_EMPNO
    Primary key column - EMPNO
    By default the automatic fetch has a ‘Process Error Message’ of ‘Unable to fetch row.’
    2) Created a HTML region. Within this region add
    text item P2099_FIND_EMPNO
    Button GET_EMP to submit
    Branch Modified the conditional branch created during button creation to set P2099_EMPNO with &P2099_FIND_EMPNO.
    If I then run the page, enter an existing employee number into P2099_EMPNO and press the GET_EMP button the form is populated correctly. But if I enter an employee that does not exist then I get the oracle error ORA-01403: no data found and no form displayed but a message at the top of the page ‘Action Processed’.I was expecting a blank form to be displayed with the message ‘Unable to fetch row.’
    I can work around this by making the automated fetch conditional so that it checks the row exists first. Modify the Fetch row from EMP automated fetch so that it is conditional
    EXIST (SQL query returns at least one row)
    select 'x'
    from EMP
    where EMPNO = :P2099_EMPNO
    But this means that when the employee exists I must be fetching from the DB twice, once for the condition and then again for the actual row fetch.
    Rather than the above work around is there something I can change so I don’t get the Oracle error? I’m now wondering if the automatic row fetch is only supposed to be used when linking a report to a form and that I should be writing the fetch process manually. The reason I haven’t at the moment is I’m trying to stick with the automatic wizard generation as much as I can.
    Any ideas?
    Thanks Pete

    Hi Mike,
    I've tried doing that but it doesn't seem to make any difference. If I turn debug on it shows below.
    0.05: Computation point: AFTER_HEADER
    0.05: Processing point: AFTER_HEADER
    0.05: ...Process "Fetch Row from EMP": DML_FETCH_ROW (AFTER_HEADER) F|#OWNER#:EMP:P2099_EMPNO:EMPNO
    0.05: Show ERROR page...
    0.05: Performing rollback...
    0.05: Processing point: AFTER_ERROR_HEADER
    I don't really wan't the error page, either nothing with the form not being populated or a message at the top of the page.
    Thanks Pete

Maybe you are looking for