Jobs pointing to old client after client copy

Hello
We have recently completed system refresh from PROD system to TEST system.
We have created new client in the new TEST system. Background jobs are copied properly from old client to new client.
We have deleted old client.
But all these jobs are pointing to old client only.
Hence all these jobs get cancelled.
How shall I change the client of all the jobs from old to new one.
-Nandu More

Hi,
This solution is not a good way, but either way it worked in a similar scenario for us.
Check the Table TBTCO for these fields
AUTHCKMAN                   Authorization check
STATUS                          Job status
Where the STATUS flag is "S", i.e SCHEDULED.
The AUTHCKMAN field will still contain reference to your OLD client no, for eg. if 300 is the deleted client and you are checking this table in the new client 200, the  AUTHCKMAN field will contain 300. Changing the client reference in this field to your new client will make the scheduled jobs run ok.

Similar Messages

  • Background jobs pointing to old client after client copy

    Hello
    We have recently completed system refresh from PROD system to TEST system.
    We have created new client in new TEST system. Background jobs are copied properly from old client to new client.
    But all these jobs are pointing to old client only. We have deleted old client.
    Hence all these jobs get cancelled.
    How shall I change the client of all the jobs from old to new one.
    -Nandu More

    Please check the thread:
    Error in Background Jobs After Client Copy
    Check some of the TBT* tables.

  • Exchange profile pointing to old hostname after the system copy

    Hi Team,
    I did system copy of SAP XI3.0 SP19 from host HOST1 (Windows 2003 , MS SQL 2005 SP3)to HOST2 (Windows 2008 R2, MS SQL 2005 SP3)with the same SID . I am using same SID as i will have to upgrade XI3.0 to PI7.1 EHP1 on the new host(trying to use parallel environment).
    The copy is fine and Java is up, however , there is some problem with the exchange profile of the new host.It has IR, ID, RWB,SLD hosts pointing to HOST1.When i try to change the host to HOST2 and save it gives me this message
    RFC call returned an error code: 300
    Stack Trace class com.sap.rprof.dbprofiles.DBException:
    at com.sap.rprof.dbprofiles.DBProfilesLock.checkReturn(DBProfilesLock.java:200)
    at com.sap.rprof.dbprofiles.DBProfilesLock.lockProfile(DBProfilesLock.java:112)
    at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactoryForUpdate(RemoteProfile.java:233)
    at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileForUpdate(RemoteProfile.java:169)
    at com.sap.rprof.dbprofiles.ExchangeProfile.getExchangeProfileForUpdate(ExchangeProfile.java:67)
    at com.sap.rprof.remoteProfile.webui.ProfileTreeItem.updateInstance(ProfileTreeItem.java:222)
    at com.sap.rprof.remoteProfile.webui.Edit.saveInstance(Edit.java:277)
    at com.sap.rprof.remoteProfile.webui.Edit.doGet(Edit.java:207)
    at com.sap.rprof.remoteProfile.webui.Edit.doPost(Edit.java:236)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Connection tab in the exchange profile points to HOST2.I ensured SLDAPICUST,SXMB_ADM->Integration Engine points to HOST2 ,also maintained the Pipe LIne URL to point to HOST2.I have followed the follow -up activities of system copy guides .But the issue is not resolved , exchange profile does not allow me to change the hostnames of IR, ID ,RWB.
    Could you please help me with this issue?
    Is the issue because of using same SID on different hosts?
    Thanks,
    Padmaja.

    Hello,
    You need to change host name manually in to Exchange profile, RFC, JCo and make sure PI is connected to SLD.
    Cheers,
    Yogesh

  • SWN_SELSEN not working in test client after client-copy

    Hi all,
    We are using extended notification without problem until test client was refreshed by client-copy from production client. In test client, report SWN_SELSEN did not generated notification even there are newly generated workflow items.  Because of client-copy, I found that tables SWN_NOTIF, SWN_NOTIFTSTMP, SWN_SENDLOG, SWN_TIMESTAMPS are all empty in test client.
    Please advise how to make report SWN_SELSEN back to work in test client.  Thanks.
    << Additional information >>
    (1) Run report SWN_SELSEN_TEST with test Case 5 - Simulate Send Only.  After this, some entries were written to above tables.  But test on new workflow item, the schedule report SWN_SELSEN still fail to trigger notification.
    (2) Run report SWN_SELSEN_TEST with test Case 4 - Send One Message Only.  It triggered notifications for all active workflow items and sent out several hundred emails including workflow item created in step 1.  However, further test on new workflowitem, the schedule report SWN_SELSEN is still unable to trigger notification.
    I think there may be something else missing, like the timestamp of delta.  Please help.
    Regards,
    Donald

    Hello,
    I've experienced a few cases where stopping SWN_SELSEN and then restarting it helped to fill up SWN_TIMESTAMPS with proper values. How does that table look after you run it?
    What is SWN_SELSEN_TEST?
    Chck in SLG1 to get an idea of why it's not working. You can also run SWN_SELSEN in the foreground and debug it to see exactly where and why it goes wrong. Also check ST22.
    regards
    Rick Bakker
    hanabi technology

  • SAP_ALL & SAP_NEW profiles not available in new client after client copy

    I am setting up a BI Client and have been following some documentation to do this downloaded from SDN. In the process, i created my client 'client 200' assigned to a logical system then doing client copy from 'client 000' using transaction SCCL. There is a step when i now have to create a user in the new client (client 200 ) where i am supposed to assign the user to profiles SAP_ALL and SAP_NEW. Unfortunately these are not available in my newly set client but in 'client 000' they are available.
    Did i make some error in the client copy process or i still need to do something to have the profiles in 'client 200'. Please assist.

    There is no issue in rerunning the Client Copy.
    But please check what mistake you made in the first one.
    Here are the steps.
    Create an entry in SCC4.
    RZ10 modify parameter login/no_automatic_user_sapstar=0
    Check that you have enouf background and dialog processes.
    Restart the sap system
    then login with SAP* in the Client you made.
    Run Sccl and give the Profile SAP_All
    Select the source Client as 000
    and Source Client user Master as 001
    Check tthat you dont select the check box of TEST MODE.
    and schedule in backgreond.
    Thanks Rishi Abrol

  • Restoring clients after homogeneous copy

    Hi...
    I have a QAS system with three clients (100, 120 and 200).
    I have a PRD system with just the client 100.
    I was asked to perform an homogeneous copy from PRD to QAS, but to make sure clients 120 and 200 are not destroyed.
    My question is:
    Would a client export (SCC8) with profile SAP_RECO solve my problem?
    I would first export both clients (120 and 200) with SAP_RECO, using the QAS system as the target, perform the copy, and then import the clients again through STMS. Would this work? Or is there any other way of doing this?
    thanks
    Antonio

    Hi Antonio
    If your are performing the system copy from PRD to QAS its will be comes only 100 client.
    for this kindly follow the steps
    1. Before starting the system copy Export the QAS client  120 & 200.
    2. Perform the system copy from PRD to QAS, & Post system copy activitys
    3. Create the New clients in QAS system
    4. Do the Import which you already performed
    BR
    SS

  • Message Bridge Destination points to old IP, after failover with HA pair

    Hi
    Weblogic Version in use is 7.0sp7
    We have this Messaging Bridge configured, between two instances of Weblogic server (Each weblogic server exists on Different Weblogic domains)
    Both the weblogic servers run on the same machine.
    So we have configured the message bridge destination with localhost, instead of an IP or DNS name in it.. viz.
    t3://localhost:8001
    t3://localhost:8020 respectively
    where 8001 and 8020 are the listen ports of the respective weblogic servers.
    This machine is a HA pair, controlled by vcs cluster server.
    Which means when we failover from one node to another of the HA pair, the transition(which also involves the IP change from node A to node B) should be ideally transparent to weblogic.
    But when it comes to these messaging bridge destinations
    The Messaging bridge resolves the localhost in the Message Bridge destination to the old node IP, after the failover is done using vcs cluster server.
    To me it looks like weblogic is caching the IP details somewhere and probably reusing it, unaware of the fact that the IP of the machine has changed after the failover.
    I tried configuring the message bridge destination with addresses like t3://<DNSname>:8001 and 8020 respectively. But stiil it tries to connect to the IP of the old node only.
    I did come across this patch in Weblogic 7.0 sp5, which is pretty close to the issue that i am encountering..
    CR126201 In a multiple-server domain, if a Managed Server was rebooted to use a different address or port
    number, the JTA subsystem failed to update the address information. This would cause the
    following exception when the changed server was rebooted:
    javax.naming.CommunicationException. Root exception is
    java.net.ConnectException: t3://ip_address:port_number:
    Destination unreachable;
    nested exception is: java.net.ConnectException: Connection
    refused; No available router to destination
    Would really appreciate if someone can help with this issue.
    Regards
    Azad

    I'm not quite sure what the correct solution might be, but a possible work-around might be to hard-code the two addresses directly into the bridge URL. For example: t3://host:7010,host:7020. WebLogic will try each address in turn, starting from the first one until one succeeds or all fail.
    Another solution might be to configure an "external listen address" on each server. This is the address that "reconnectable" external clients (such as EJBs or a bridge ) will use for reconnect in place of the server's actual listen address.
    Tom

  • TCURM in target client empty after Client Copy

    Hi Experts,
    Has anyone encountered situation whereby TCURM does not contain a record for the target client after Client Copy process is completed? Is this a feature or bug?
    Regards

    Hi ,  I  user the exclude tables option to exclude some tables.
    but I have another problem:  the client copy still failed.  I get these  informations:
    table/object   component                         error
    ANLU           FI-AA-AA                   Field missing locally
    C905            SD-MD-CM                Different Field Names
    IMPTT          PM-EQM-SF-MPC      Field missing locally
    how can i finish my client copy ?   can you give me the solution
    thanks very much

  • Scheduled Background jobs after Client Copy

    Hello,
    I've been doing some searching online and I don't seem to be able to find a definitive answer to this question:
    Are background jobs client specific?
    I've seen some discussions on here say some are and some are not.  I've also seen a discussion that says ALL background jobs are client specific.
    It's really related to non-SAP background jobs after a client copy.
    If I have a client 100 in QA with half a dozen non-SAP standard jobs configured, and I create client 110 in QA and perform a remote client copy from PROD into client 110 on QA, will my non-SAP standard backgrounds run in Client 110, or do I need to set them all up again?
    Thanks

    Hello All
    If I have a client 100 in QA with half a dozen non-SAP standard jobs configured, and I create client 110 in QA and perform a remote client copy from PROD into client 110 on QA, will my non-SAP standard backgrounds run in Client 110, or do I need to set them all up again?
    Yes. You will need to set those non standard jobs in the new client. When you schedule a job there will be a reference to the client where the job will be executed is stored under AUTHCKMAN in the table TBTCO. If the job is scheduled periodically then the job is executed only on the client where it is scheduled.
    I used SAP_ALL profile when performing the client copy.  So my scheduled jobs WILL have been copied along with everything else? Is that correct?
    In SAP_ALL profile the background jobs will be coming from source client not from QA client 100.
    No. Background jobs are not transportable and will not be copied during a client copy. Job definitions are client independent.
    Read these SAP notes.
    31503 - FAQ: Background jobs
    51135 - Why are bkgd processing jobs not generally transportable?
    If you want to schedule those jobs in the new client the follow the suggestion in the SAP note 3150 point 6.
    Regards
    RB

  • Error in Background Jobs After Client Copy

    Hi,
    We had performed a system refresh from a production client(with client no 300) to a quality server (client no: 200). The post processing steps were performed ok. Later the client 300 on the quality server was dropped. However, the scheduled user jobs in the background on client 200 still refer to the original client 300 and abort.
    Is there any way of modifying there jobs(there are lots of them) so that the client(300 in this case) reference is modified to the existing client 200.
    Points will be rewarded for good answer.
    Thanks and Regards,
    Subodh

    Hi
    The reason for the jobs getting cancelled could be that they are
    client dependent jobs and inoder to resolve the issue, please
    reschedule the jobs in client 200 and check whether the job fails.
    Please let me know if all the jobs are failing or the issue is only
    with the client dependent jobs.
    Hope this information helps. Please get back to me if further
    assistance is required. I would be glad to assist you.
    venkat

  • Error message: no valid initialization after client copy

    Hi,
    We recently did a client copy of our quality BW and R/3 systems from preproduction. In the 'new' clients we have problems with the delta process for 2LIS_13_VDITM. We get an error message that there was no valid initialization in the system, where in fact a valid initialization has taken place (everything from preprodcution was copied).
    The source systems setting where corrected using BDLS, but the entries in R/3 tables roosprmsf / roosprmsc were still pointing to the old system. This has now been corrected.
    One problem remains. There is no entry for 2LIS_13_VDITM in table RSSDLINIT. I suspect that this causes the error message. Can anybody confirm this ? Is there a standard way to add the correct entry (with the package number of the init package) in table RSSDLINIT or realign table RSSDLINIT with table roosprmsf in R/3 ?
    Thanks in advance !

    Hi,
    After system copy. You will ahve delet your whole data and reload every thing.
    In case you are getting dump when you double click infopacakge then delete your data source entry in RSA7 in source system and then go for fresh init load and then continue with delta load. Before goign for fresh init load you will have to first delet the init load entry.
    This must help
    Regards,
    Rohini
    Message was edited by: Rohini Garg

  • Unable to find product categories after client copy

    Hi all,
    We have copied  clients from an existing ones for both SRM and ECC. After client copy we have followed standard procedure after client copy i.e.
    Run transcation BDLS
    created new RFC connections
    changed attributes using the Attributes replace report
    created new distributon model
    maintained CRM parameters
    maintained new site attributes in SMOEAC transaction
    maintained entries in table TWPURLSVR
    however , when i try to create a shopping cart,  I cannot see any product category. The extended attributes for product category point to new ECC client becuse we have run the attributes replace report.
    however in the product category table , COMM_CATEGORY , the product categories listed are all for the old ECC client
    When i tried to load the Object DNL_CUST_PROD1 using transaction R3AS in SRM and tried to pull from new ECC client , it is in runing status for a long time and new categories with new ECC backend reference are not being replicated in the SRM.
    Can you tell me why this could be happening ? How can i get the product categories from new ECC backend into my client?
    Regards,
    Mangesh

    problem solved
    i was using wrong parameters in BDLS

  • Change Myself system in RSA1 trx after client copy

    Hi,
    I have installed SCM 2007 system.
    As post-processing step i have configured myself system in RSA1 trx in the 001 client.
    Now, i want to perform client copy and use that new client 100 as Prod client. What are the steps required to change myself system to point to the new client?
    Please help.
    Regards,
    Chintan

    HI,
    As logical systems are used to define you can use BDLS to convert them after client copy.
    Go through :Note 325470,325525.
    Thanks.

  • SAP* not authorized after Client copy

    Dear All,
    Here's the scenario:
    1. Created a new logical system for a new Quality client 230.
    2. Created the new client 220
    3. scheduled a test remote client copy from the new client, source Production. (Successful)
    4. Scheduled the actual client copy to run last night.
    5. Today morning, I'm logging into the new client with SAP*, it prompted me to change password.
    6. I want to look for the client copy logs (SCC3), but getting "not authorized"
    7. Checked all other transactions, all giving "not authorized" error
    Any help would be appreciated. Thanks in advance.

    Dear Reza,
    Better to go for Client Export Import process . This is what SAP reccomends for coping clients  between
    different systems ( Like from Production to Quality ) as the remote client copy has many
    disadvantages..
    For this 1 ) you should get the downtime of production system and do the client export process .
    SCC8 . See the logs at scc3 .
    2) Copy the datafile and cofile to the Source system
    3) Import it usting stms_import .
    Monitor the logs as the logs will be grown massive and make sure enough space is there.
    4) After client copy , go for post processing ( scc7 ) .
    Hope you are clear and feel free to get back if any doubts.
    Regards,
    Nibu

  • Material Master and CMIR Texts not copied after Client Copy

    Hi All,
    We had a scenario wherein we had to copy our production client and create a new client (Preproduction). When we performed the client copy, i see that the texts maintained in material master (sales text) and Customer material info record are not not copied into the new client.
    Can somebody suggest me a way out for this..
    Thanks and Regards
    Bhushan

    Hi All ,
    Closing this thread as the same have got copied into the new client after recopying..
    Regards
    Bhushan

Maybe you are looking for