System copy problems

Hello,
I am doing a systemcopy with backup / restore from System X69 to Q69 on a different server. Therefore I did an online backup to file, copied it to target server a try to restore the database.
I have executed the command
brdb6brt -bm RETRIEVE -ts 20140806083346 -user db2x69 -using Password
to create the redirect commands.
The result (without comments):
UPDATE COMMAND OPTIONS USING S ON Z ON Q69_NODE0000.out V ON;
SET CLIENT ATTACH_NODE  0;
SET CLIENT CONNECT_NODE 0;
ECHO @./X69_NODE0000.scr@;
RESTORE DATABASE X69
USER db2q69 USING xxxxxxxx
FROM /db2/backup
TAKEN AT 20140806083346
ON /db2/Q69/sapdata4
   ,/db2/Q69/sapdata3
   ,/db2/Q69/sapdata2
   ,/db2/Q69/sapdata1
INTO Q69
NEWLOGPATH /db2/Q69/log_dir/NODE0000/LOGSTREAM0000/
WITH 2 BUFFERS
BUFFER 1024
REDIRECT
SET STOGROUP PATHS FOR IBMSTOGROUP ON '/db2/Q69/sapdata4','/db2/Q69/sapdata3','/db2/Q69/sapdata2','/db2/Q69/sapdata1' ;
After executing the script by db2 -tvf X69_NODE0000.scr I have executed db2 RESTORE DATABASE X69 CONTINUE
After this the ROLLFORWARD fails with error:
db2 => rollforward db Q69 to end of backup and complete
SQL0752N  Connecting to a database is not permitted within a logical unit of work when the CONNECT type 1 setting is in use.  SQLSTATE=0A001
If I terminate the session I get the error.
db2 => rollforward db Q69 to end of backup and complete
SQL1119N  A connection to or activation of database "Q69" cannot be made because a previous restore is incomplete or still in progress.  SQLSTATE=57019
How do I get the db2 to rollforward the logs of the ONLINE backup?
Best Regards
Andreas

Hello,
I have found one solution by doing all commands in a db2 dialog shell instead of a script.
After the successfull command restore database Q69 continue
DB20000I  The RESTORE DATABASE command completed successfully.
Now I can do a get db cfg with the following output:
All committed transactions have been written to disk    = YES
Rollforward pending                                     = NO
Restore pending                                         = YES
At this point I can not start a rollforward. The restore has been completed successfully but the status is still pending.
What can I do to use the database now?
Regards
Andreas

Similar Messages

  • BI system copy problem~

    Dear Expert:
    I try to do BI system copy.
    But got an error when I tried to backup from source system .
    Error during "Import ABAP" phase in step "runMigrationMonitor"
    I had already read the note 970518.
    But the solution is not working for this problem.
    Here is the error message below:
    FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    Please Help~
    Thanks~
    Regards
    Jack Lee

    Dear Expert:
    Here are logs below~
    In sapinst.log
    WARNING 2009-04-16 13:08:45.329
    Execution of the command "C:\j2sdk1.4.2_16-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.exp.ExportMonitor -sapinst" finished with return code 103. Output:
    java version "1.4.2_16"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_16-b05)
    Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_16-b05, mixed mode)
    Export Monitor jobs: running 1, waiting 0, completed 72, failed 0, total 73.
    Unloading of 'SAPAPPL0_1' export package: ERROR
    Export Monitor jobs: running 0, waiting 0, completed 72, failed 1, total 73.
    ERROR 2009-04-16 13:08:45.329
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) export_monitor.java.log, export_monitor.log.
    ERROR 2009-04-16 13:08:45.392
    FCO-00011  The step runMigrationMonitor with step key |NW_Export|ind|ind|ind|ind|0|0|NW_ABAP_Export_Dialog|ind|ind|ind|ind|4|0|NW_ABAP_Export|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) export_monitor.java.log, export_monitor.log.).
    *In export_monitor.java.log*
    java version "1.4.2_16"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_16-b05)
    Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_16-b05, mixed mode)
    Export Monitor jobs: running 1, waiting 0, completed 72, failed 0, total 73.
    Unloading of 'SAPAPPL0_1' export package: ERROR
    Export Monitor jobs: running 0, waiting 0, completed 72, failed 1, total 73.
    In SAPAPPL0_1.log:
    D:\usr\sap\BWD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20090416114013
    D:\usr\sap\BWD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
    D:\usr\sap\BWD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jan 24 2008 01:41:44
    D:\usr\sap\BWD\SYS\exe\uc\NTAMD64\R3load.exe -e SAPAPPL0_1.cmd -datacodepage 4103 -l SAPAPPL0_1.log -stop_on_error
    (DB) INFO: connected to DB
    (GSI) INFO: dbname   = "BWDBWDEV                                                                                "
    (GSI) INFO: vname    = "MSSQL                           "
    (GSI) INFO: hostname = "BWDEV                                                           "
    (GSI) INFO: sysname  = "Windows NT"
    (GSI) INFO: nodename = "BWDEV"
    (GSI) INFO: release  = "5.2"
    (GSI) INFO: version  = "3790 Service Pack 1"
    (GSI) INFO: machine  = "16x AMD64 Level 15 (Mod 4 Step 8)"
    (GSI) INFO: instno   = "INITIAL   "
    (EXP) ERROR: DbSlPrepare/BegRead failed
      rc = 103, table "/BI0/0100000020"
      (SQL error 208)
      error message returned by DbSl:
    Invalid object name '/BI0/0100000020'.
    Statement(s) could not be prepared.
    (DB) INFO: disconnected from DB
    D:\usr\sap\BWD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
    D:\usr\sap\BWD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20090416114017

  • System copy problem...No transfer rules available

    Hi ,
    We are facing a problem in getting the Transfer Rules...
    1.we did a system copy from PRD system and created a Sandbox system .
    2.After the system copy the problem came from the source system.....i.e for the datasource's in the table RSOLTPSOURCE the mapping is showing for 2 systems....CRM PRD system & CRM SANDBOX system....
    3.Coz of this issue the Transfer rules are not available and the all the DS are inactive......
    4.I tried with the FM RS_TRANSTRUC_ACTIVATE_ALL but im getting message as no transfer structure is available.
    5.When i tried to manually activate the DS from BW side it is asking to create TRANSFER RULE.
    Please help me to sort it out.....
    Thanks in Advance
    BASKAR

    HI ,
    I also raised a OSS to SAP ....what they suggested is....
    According the logs in BWS there was definitely a systemcopy from BWP to BWS, but the BDLS logs looks very strange, which actually did not converted anything, because the administration tables containing some very strange entries.
    Lets take the datasource 0crm_sales_act_1 for example. If you check this datasource in table RSOLTPSOURCE you can see, that it exists currently for both source systems:
    OLTPSOURCE LOGSYS OBJVERS
    0CRM_SALES_ACT_1 CMPCLNT501 A
    0CRM_SALES_ACT_1 CMSCLNT501 A
    Unfortunately the root cause of this is unkown, but most probably it is caused by an improper copy procedure, where the consulting note
    886102 was not followed.
    To solve the problem, please follow the below steps:
    1. Implement note 1405233 and 1336119 to your system 2. Go to RSA1 and delete the source System CMS.
    3. With function module rsar_logical_system_delete delete the source system CMP:
    I_LOGSYS CMPCLNT501
    I_FORCE_DELETE X
    I_NO_TRANSPORT X
    I_NO_AUTHORITY X
    4. In your productive BW (BWP) please create a transport request which contains all the source system dependent objects for CMP. Please check note 886102 scenario B3 step 2 for details.
    5. In BWS, please recreate the source system to CMS and activate it but please do not replicate the datasources yet.
    6. In BWS please maintain the table RSLOGSYSMAP and map CMP to CMS and import the transport request created in step 4.
    Please be aware, that such a constellation happens mostly, if some steps are missed or are not carried out properly from consulting note 886102. Please get in touch with your basis colleagues and provide them this note, so the next time such a problem does not occur.
    I hope this helps to solve the problem.
    Thanks
    BASKAR

  • Java system copy problems with the Java Migration Toolkit

    During the JAVA system copy, we have have got the error in second last
    step i.e;Java Migration Toolkit. We tried to do the system copy twice
    but every time we have got the below error.
    Is this a know bug? I have got the OSS note 966752 but the value
    of 'src.ci.host' is already correct. has anybody come across the similar issue. please help.
    " CJSlibModule::writeInfo_impl()
    Output of /usr/java14_64/bin/java -
    classpath /usr/sap/CMT/SYS/global/sltools/sharedlib/launcher.jar:. -Xj9
    com.sap.engine.offline.OfflineToolStart
    com.sap.sdt.jmt.migrationtool.MigrationToolImport /usr/sap/CMT/SYS/global/sltools/jmt:/usr/sap/CMT/SYS/global/sltools/sharedlib import.switch
    resume downtime mti.properties is written to the
    logfile /home/cmtadm/CI_Import_08312009/runJmt.log.
    WARNING 2009-09-01 20:49:43.473
    CJSlibModule::writeWarning_impl()
    Execution of the command "/usr/java14_64/bin/java -
    classpath /usr/sap/CMT/SYS/global/sltools/sharedlib/launcher.jar:. -Xj9
    com.sap.engine.offline.OfflineToolStart
    com.sap.sdt.jmt.migrationtool.MigrationToolImport /usr/sap/CMT/SYS/global/sltools/jmt:/usr/sap/CMT/SYS/global/sltools/sharedlib import.switch
    resume downtime mti.properties" finished with return code 27. Output:
    ERROR 2009-09-01 20:49:43.477
    CJSlibModule::writeError_impl()
    CJS-20068 Error when running the J2EE Migration Toolkit.<br>SOLUTION:
    See output of logfile /home/cmtadm/CI_Import_08312009/runJmt.log: ''.
    ERROR 2009-09-01 20:49:43.479
    CJSlibModule::writeError_impl()
    CJS-20068 Error when running the J2EE Migration Toolkit.<br>SOLUTION:
    See output of logfile /home/cmtadm/CI_Import_08312009/runJmt.log: ''.
    ERROR 2009-09-01 20:49:43.480 [iaxxgenimp.cpp:731]
    showDialog()
    FCO-00011 The step RunMigrationController with step key
    |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|2|0|RunMigrationController was executed with status ERROR ."
    There is no log file by the name runJmt.log.
    Regards,
    Sagar

    This issue was resolved by OSS note 966752 itself. Below is the important line in the OSS note.
    Note: The default value is crucial! If a custom value other than the default value was applied, we highly recommend that you restore the default value.
    Thanks,
    Sagar

  • MaxDB upgrade/heterogeneus system copy problem with unicode conversion

    Project goal:
    upgrade a Content Server Version 7.3.0.35   32bit Non Unicode to
    version 7.6.06.16   64bit Unicode
    I found and followed note 962019
    My plan (following the note): 
    -create a clone of the original Content Server (vmware clone)
    -as per note 962019 patched server 7.3.0.35 to 7.3.0.62 (> 7.3.0.57)
    -created index
    -on a fresh installed windows 2003 server 64bit i installed Content Server with build 7.6.06.16
    -using loadercli from the target server (7.6.06.16) exported data
    Now i was ready to start the import, as the note states:
    "if the database parameter _UNICODE is set to the value NO and you want to start the target system with SAP MaxDB Version 7.6, you can use procedure described here for the import into a target system only with SAP MaxDB Version 7.6.05 build 11 or higher"
    Having version 7.6.06.16 i was confident on such procedure, but my import stops immediatly with error:
    D:\exportKpro>loadercli -d PRD -u SAPR3,SAP -b import.sql
    Loader protocol: 'C:\Documents and Settings\administrator\My Documents
    \sdb\loader\log\loader.log'
    Loader packages: 'C:\Documents and Settings\administrator\My Documents
    \sdb\loader\packages'
    Error connecting user SAPR3 to database PRD on local host: -25005
    User (SAPR3) logon to database PRD failed: SQL error -8046 = Conversion from UNI
    CODE impossible: 7600 (error position: 1)
    And now i'm stuck with no hints on how to proceed.
    Thanks in advance.
    Regards
    Simone Zaffalon

    Hello Simone,
    as you're staying on Windows platform, there is no need for a heterogenous system copy.
    All you've to do is to upgrade the 32-Bit installation to your target release (why not use MaxDB 7.7 right away?).
    Once this is done, you can check whether the database catalog is still non-unicode (_UNICODE=FALSE).
    If it is, there is a catalog migration procedure you can use to change this.
    If the 32-Bit database is as you want it, take a full data backup.
    Then uninstall the 32-Bit software, install the same version of MaxDB in the 64-Bit fashion.
    Finally create the db instance by a restore of the backup.
    After a load_systab your database is fully ready to go!
    Just to stress this again: the _UNICODE parameter is not about your data!.
    It's about the database catalog.
    Having this parameter set to YES you can create e.g. tables named with Unicode characters.
    The parameter does in no way affect your business data!
    Since many customers ask why they should't use loadercli for a scenario like this:
    a) It's only supported if you must use it, that is, you change the byte-order of the OS platform
    b) it's way faster than export and import. We're talking about a few hours compared to days here!
    c) It's much safer and controllable to use backup/restore and SDBUPD and move on step-by-step than exporting all data into a big file chunk and hoping that everything will be fine afterwards.
    regards,
    Lars

  • BW Procedure System Copy - Problemas with transformations and DTP

    Hello,
    My Administration system have done a BW production copy to a BW non-productive system. After that, I have created a transport order in BW production with the option "with the source-system-dependent objects". Before I transport this order to BW non-productive system, I have deleted, in this system, the ancient source-system assignment.
    When I have transported the order to BW non-productive system, the system I created transformation an DTP with another  ID. I was expected that the ID was the same and not another one. Is this normal? What will happen when i tranport the changes form BW non-productive system to BW productive system?
    Best regards.
    Sérgio Pinto

    Hello Raghavendra,
    But the BDLS report is not only for changing the logical name of the BW system? Is it possible to use this program in BW for changing the logical name of the source system than is assigned to the datasources?
    By changing ID I want to say that the DTP with the ID DTP_4EC3YB6B6DT0OIH1TMBB0F5VG is change to the ID DTP_4K1H1XZ38M1CLVJ2IA8KFDQYY in BW no-productive system, after transport from productive to non-productive system.
    Best regards.
    Sérgio Pinto

  • Problem in homogenus system copy

    Sir ,
          We are using SAP R/3 4.7 ,win2003 server& sql server2000. After attaching database ,i am facing a problem,dispatcher is not start.
    I am sending devloper trace of dispatcher,wp devloper trace.
          Please help
    DISPATCHER DEVLOPER TRACE
    trc file: "dev_disp", trc level: 1, release: "640"
    Sun Mar 16 14:39:16 2008
    kernel runs with dp version 128(ext=102) (@(#) DPLIB-INT-VERSION-128)
    length of sys_adm_ext is 312 bytes
    systemid   560 (PC with Windows NT)
    relno      6400
    patchlevel 0
    patchno    25
    intno      20020600
    make:      multithreaded, ASCII
    pid        3364
    ***LOG Q00=> DpSapEnvInit, DPStart (01 3364) [dpxxdisp.c   1100]
         shared lib "dw_xml.dll" version 26 successfully loaded
         shared lib "dw_xtc.dll" version 26 successfully loaded
         shared lib "dw_stl.dll" version 26 successfully loaded
         shared lib "dw_gui.dll" version 26 successfully loaded
    Sun Mar 16 14:39:21 2008
    WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  3886]
    MtxInit: -2 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: JAVA is not active
    DpShMCreate: sizeof(wp_adm)          16560     (828)
    DpShMCreate: sizeof(tm_adm)          2219848     (11044)
    DpShMCreate: sizeof(wp_ca_adm)          18000     (60)
    DpShMCreate: sizeof(appc_ca_adm)     6000     (60)
    DpShMCreate: sizeof(comm_adm)          192000     (384)
    DpShMCreate: sizeof(vmc_adm)          0     (320)
    DpShMCreate: sizeof(wall_adm)          (22440/34344/56/100)
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 04A30040, size: 2515352)
    DpShMCreate: allocated sys_adm at 04A30040
    DpShMCreate: allocated wp_adm at 04A317A8
    DpShMCreate: allocated tm_adm_list at 04A35858
    DpShMCreate: allocated tm_adm at 04A35880
    DpShMCreate: allocated wp_ca_adm at 04C537C8
    DpShMCreate: allocated appc_ca_adm at 04C57E18
    DpShMCreate: allocated comm_adm_list at 04C59588
    DpShMCreate: allocated comm_adm at 04C595A0
    DpShMCreate: allocated vmc_adm_list at 04C883A0
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated ca_info at 04C883C8
    DpShMCreate: allocated wall_adm at 04C883D0
    MBUF state OFF
    EmInit: MmSetImplementation( 2 ).
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 1024 kByte.
    Using implementation std
    <EsNT> Memory Reset enabled as NT default
    <EsNT> EsIUnamFileMapInit: Initialize the memory 1698 MB
    <ES> 1697 blocks reserved for free list.
    ES initialized.
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG Q0K=> DpMsAttach, mscon ( sapdev) [dpxxdisp.c   9719]
    CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
    Sun Mar 16 14:39:22 2008
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpMsgAdmin: Set release to 6400, patchlevel 0
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1025]
    DpMsgAdmin: Set patchno for this platform to 25
    Release check o.K.
    Sun Mar 16 14:40:01 2008
    ERROR => W0 (pid 3576) died [dpxxdisp.c   12170]
    ERROR => W1 (pid 3596) died [dpxxdisp.c   12170]
    ERROR => W2 (pid 2716) died [dpxxdisp.c   12170]
    ERROR => W3 (pid 3564) died [dpxxdisp.c   12170]
    ERROR => W4 (pid 3092) died [dpxxdisp.c   12170]
    ERROR => W5 (pid 2644) died [dpxxdisp.c   12170]
    ERROR => W6 (pid 1616) died [dpxxdisp.c   12170]
    ERROR => W7 (pid 3604) died [dpxxdisp.c   12170]
    my types changed after wp death/restart 0xbf --> 0xbe
    ERROR => W8 (pid 3208) died [dpxxdisp.c   12170]
    ERROR => W9 (pid 3612) died [dpxxdisp.c   12170]
    my types changed after wp death/restart 0xbe --> 0xbc
    ERROR => W10 (pid 3624) died [dpxxdisp.c   12170]
    my types changed after wp death/restart 0xbc --> 0xb8
    ERROR => W11 (pid 2504) died [dpxxdisp.c   12170]
    ERROR => W12 (pid 3128) died [dpxxdisp.c   12170]
    ERROR => W13 (pid 780) died [dpxxdisp.c   12170]
    ERROR => W14 (pid 2688) died [dpxxdisp.c   12170]
    ERROR => W15 (pid 2524) died [dpxxdisp.c   12170]
    my types changed after wp death/restart 0xb8 --> 0xb0
    ERROR => W16 (pid 3616) died [dpxxdisp.c   12170]
    ERROR => W17 (pid 1196) died [dpxxdisp.c   12170]
    my types changed after wp death/restart 0xb0 --> 0xa0
    ERROR => W18 (pid 204) died [dpxxdisp.c   12170]
    ERROR => W19 (pid 2012) died [dpxxdisp.c   12170]
    my types changed after wp death/restart 0xa0 --> 0x80
    DP_FATAL_ERROR => DpWPCheck: no more work processes
    DISPATCHER EMERGENCY SHUTDOWN ***
    increase tracelevel of WPs
    killing W0-3576 (SIGUSR2)
    ERROR => DpWpKill(3576, SIGUSR2) failed [dpxxtool.c   2468]
    killing W1-3596 (SIGUSR2)
    ERROR => DpWpKill(3596, SIGUSR2) failed [dpxxtool.c   2468]
    killing W2-2716 (SIGUSR2)
    ERROR => DpWpKill(2716, SIGUSR2) failed [dpxxtool.c   2468]
    killing W3-3564 (SIGUSR2)
    ERROR => DpWpKill(3564, SIGUSR2) failed [dpxxtool.c   2468]
    killing W4-3092 (SIGUSR2)
    ERROR => DpWpKill(3092, SIGUSR2) failed [dpxxtool.c   2468]
    killing W5-2644 (SIGUSR2)
    ERROR => DpWpKill(2644, SIGUSR2) failed [dpxxtool.c   2468]
    killing W6-1616 (SIGUSR2)
    ERROR => DpWpKill(1616, SIGUSR2) failed [dpxxtool.c   2468]
    killing W7-3604 (SIGUSR2)
    ERROR => DpWpKill(3604, SIGUSR2) failed [dpxxtool.c   2468]
    killing W8-3208 (SIGUSR2)
    ERROR => DpWpKill(3208, SIGUSR2) failed [dpxxtool.c   2468]
    killing W9-3612 (SIGUSR2)
    ERROR => DpWpKill(3612, SIGUSR2) failed [dpxxtool.c   2468]
    killing W10-3624 (SIGUSR2)
    ERROR => DpWpKill(3624, SIGUSR2) failed [dpxxtool.c   2468]
    killing W11-2504 (SIGUSR2)
    ERROR => DpWpKill(2504, SIGUSR2) failed [dpxxtool.c   2468]
    killing W12-3128 (SIGUSR2)
    ERROR => DpWpKill(3128, SIGUSR2) failed [dpxxtool.c   2468]
    killing W13-780 (SIGUSR2)
    ERROR => DpWpKill(780, SIGUSR2) failed [dpxxtool.c   2468]
    killing W14-2688 (SIGUSR2)
    ERROR => DpWpKill(2688, SIGUSR2) failed [dpxxtool.c   2468]
    killing W15-2524 (SIGUSR2)
    ERROR => DpWpKill(2524, SIGUSR2) failed [dpxxtool.c   2468]
    killing W16-3616 (SIGUSR2)
    ERROR => DpWpKill(3616, SIGUSR2) failed [dpxxtool.c   2468]
    killing W17-1196 (SIGUSR2)
    ERROR => DpWpKill(1196, SIGUSR2) failed [dpxxtool.c   2468]
    killing W18-204 (SIGUSR2)
    ERROR => DpWpKill(204, SIGUSR2) failed [dpxxtool.c   2468]
    killing W19-2012 (SIGUSR2)
    ERROR => DpWpKill(2012, SIGUSR2) failed [dpxxtool.c   2468]
    NiWait: sleep (10000 msecs) ...
    NiISelect: timeout 10000 ms
    NiISelect: maximum fd=1553
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Sun Mar 16 14:40:11 2008
    NiISelect: TIMEOUT occured (10000 ms)
    dump system status
    Workprocess Table (long)               Sun Mar 16 09:10:11 2008
    ========================
    No Ty. Pid      Status  Cause Start Err Sem CPU    Time  Program  Cl  User         Action                    Table
    0 DIA     3576 Ended         no      1   0             0                                                             
    1 DIA     3596 Ended         no      1   0             0                                                             
    2 DIA     2716 Ended         no      1   0             0                                                             
    3 DIA     3564 Ended         no      1   0             0                                                             
    4 DIA     3092 Ended         no      1   0             0                                                             
    5 DIA     2644 Ended         no      1   0             0                                                             
    6 DIA     1616 Ended         no      1   0             0                                                             
    7 DIA     3604 Ended         no      1   0             0                                                             
    8 UPD     3208 Ended         no      1   0             0                                                             
    9 UPD     3612 Ended         no      1   0             0                                                             
    10 ENQ     3624 Ended         no      1   0             0                                                             
    11 BTC     2504 Ended         no      1   0             0                                                             
    12 BTC     3128 Ended         no      1   0             0                                                             
    13 BTC      780 Ended         no      1   0             0                                                             
    14 BTC     2688 Ended         no      1   0             0                                                             
    15 BTC     2524 Ended         no      1   0             0                                                             
    16 SPO     3616 Ended         no      1   0             0                                                             
    17 SPO     1196 Ended         no      1   0             0                                                             
    18 UP2      204 Ended         no      1   0             0                                                             
    19 UP2     2012 Ended         no      1   0             0                                                             
    Dispatcher Queue Statistics               Sun Mar 16 09:10:11 2008
    ===========================
    --------++++--
    +
    Typ
    now
    high
    max
    writes
    reads
    --------++++--
    +
    NOWP
    0
    3
    2000
    10
    10
    --------++++--
    +
    DIA
    5
    5
    2000
    5
    0
    --------++++--
    +
    UPD
    0
    0
    2000
    0
    0
    --------++++--
    +
    ENQ
    0
    0
    2000
    0
    0
    --------++++--
    +
    BTC
    0
    0
    2000
    0
    0
    --------++++--
    +
    SPO
    0
    0
    2000
    0
    0
    --------++++--
    +
    UP2
    0
    0
    2000
    0
    0
    --------++++--
    +
    max_rq_id          13
    wake_evt_udp_now     0
    wake events           total     9,  udp     8 ( 88%),  shm     1 ( 11%)
    since last update     total     9,  udp     8 ( 88%),  shm     1 ( 11%)
    Dump of tm_adm structure:               Sun Mar 16 09:10:11 2008
    =========================
    Term    uid  man user    term   lastop  mod wp  ta   a/i (modes)
    Workprocess Comm. Area Blocks               Sun Mar 16 09:10:11 2008
    =============================
    Slots: 300, Used: 1, Max: 0
    --------++--
    +
    id
    owner
    pid
    eyecatcher
    --------++--
    +
    0
    DISPATCHER
    -1
    WPCAAD000
    NiWait: sleep (5000 msecs) ...
    NiISelect: timeout 5000 ms
    NiISelect: maximum fd=1553
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Sun Mar 16 14:40:16 2008
    NiISelect: TIMEOUT occured (5000 ms)
    Shutdown server ...
    DpModState: buffer in state MBUF_PREPARED
    NiBufSend starting
    NiIWrite: write 110, 1 packs, MESG_IO, hdl 3, data complete
    MsINiWrite: sent 110 bytes
    MsIModState: change state to SHUTDOWN
    DpModState: change server state from STARTING to SHUTDOWN
    Switch off Shared memory profiling
    ShmProtect( 57, 3 )
    ShmProtect(SHM_PROFILE, SHM_PROT_RW
    ShmProtect( 57, 1 )
    ShmProtect(SHM_PROFILE, SHM_PROT_RD
    DpWakeUpWps: wake up all wp's
    Stop work processes...
    Stop gateway
    killing process (1252) (SOFT_KILL)
    Stop icman
    killing process (3028) (SOFT_KILL)
    Terminate gui connections
    [DpProcDied] Process lives  (PID:1252  HANDLE:1524)
    waiting for termination of gateway
    NiWait: sleep (1000 msecs) ...
    NiISelect: timeout 1000 ms
    NiISelect: maximum fd=1553
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Sun Mar 16 14:40:17 2008
    NiISelect: TIMEOUT occured (1000 ms)
    [DpProcDied] Process died  (PID:1252  HANDLE:1524)
    [DpProcDied] Process died  (PID:3028  HANDLE:1516)
    DpHalt: cancel all lcom connections
    MPI CancelAll 2 -> 0
    MPI DeleteAll 2 -> 0
    NiIMyHostName: hostname = 'sapdev'
    AdGetSelfIdentRecord: >                                                                           <
    AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
    DpConvertRequest: net size = 163 bytes
    NiBufSend starting
    NiIWrite: write 562, 1 packs, MESG_IO, hdl 3, data complete
    MsINiWrite: sent 562 bytes
    send msg (len 110+452) to name          -, type 4, key -
    detach from message server
    ***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c   9945]
    NiBufSend starting
    NiIWrite: write 110, 1 packs, MESG_IO, hdl 3, data complete
    MsINiWrite: sent 110 bytes
    MsIDetach: send logout to msg_server
    MsIDetach: call exit function
    DpMsShutdownHook called
    NiSelClear: removed hdl 3 from selectset
    MBUF state OFF
    AdGetSelfIdentRecord: >                                                                           <
    AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
    blks_in_queue/wp_ca_blk_no/wp_max_no = 1/300/20
    LOCK WP ca_blk 1
    make DISP owner of wp_ca_blk 1
    DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 19)
    MBUF component DOWN
    NiBufClose: clear extensions for hdl 3
    NiBufSetStat: bufstat of hdl 3 changed from OK to OFF
    NiICloseHandle: shutdown and close hdl 3 / socket 1532
    MsIDetach: detach MS-system
    EsCleanup ....
    ***LOG Q05=> DpHalt, DPStop ( 3364) [dpxxdisp.c   8478]
    Good Bye .....
    *WP TABLE DEVLOPER TRACE*
    trc file: "dev_w0", trc level: 1, release: "640"
    ACTIVE TRACE LEVEL           1
    ACTIVE TRACE COMPONENTS      all, M

    B Sun Mar 16 14:39:22 2008
    B  create_con (con_name=R/3)
    B  Loading DB library 'E:\usr\sap\DIF\SYS\exe\run\dbmssslib.dll' ...
    B  Library 'E:\usr\sap\DIF\SYS\exe\run\dbmssslib.dll' loaded
    B  Version of 'E:\usr\sap\DIF\SYS\exe\run\dbmssslib.dll' is "640.00", patchlevel (0.26)
    B  New connection 0 created
    M systemid   560 (PC with Windows NT)
    M relno      6400
    M patchlevel 0
    M patchno    25
    M intno      20020600
    M make:      multithreaded, ASCII
    M pid        3576
    M
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 3576) [dpxxdisp.c   1160]
    I  MtxInit: -2 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: JAVA is not active
    M  DpShMCreate: sizeof(wp_adm)          16560     (828)
    M  DpShMCreate: sizeof(tm_adm)          2219848     (11044)
    M  DpShMCreate: sizeof(wp_ca_adm)          18000     (60)
    M  DpShMCreate: sizeof(appc_ca_adm)     6000     (60)
    M  DpShMCreate: sizeof(comm_adm)          192000     (384)
    M  DpShMCreate: sizeof(vmc_adm)          0     (320)
    M  DpShMCreate: sizeof(wall_adm)          (22440/34344/56/100)
    M  DpShMCreate: SHM_DP_ADM_KEY          (addr: 05230040, size: 2515352)
    M  DpShMCreate: allocated sys_adm at 05230040
    M  DpShMCreate: allocated wp_adm at 052317A8
    M  DpShMCreate: allocated tm_adm_list at 05235858
    M  DpShMCreate: allocated tm_adm at 05235880
    M  DpShMCreate: allocated wp_ca_adm at 054537C8
    M  DpShMCreate: allocated appc_ca_adm at 05457E18
    M  DpShMCreate: allocated comm_adm_list at 05459588
    M  DpShMCreate: allocated comm_adm at 054595A0
    M  DpShMCreate: allocated vmc_adm_list at 054883A0
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 054883C8
    M  DpShMCreate: allocated wall_adm at 054883D0
    X  EmInit: MmSetImplementation( 2 ).
    X  <ES> client 0 initializing ....
    X  Using implementation std
    M  <EsNT> Memory Reset enabled as NT default
    X  ES initialized.

    M Sun Mar 16 14:39:24 2008
    M  calling db_connect ...
    C  Thank You for using the SLOLEDB-interface
    C  Using dynamic link library 'E:\usr\sap\DIF\SYS\exe\run\dbmssslib.dll'
    C  dbmssslib.dll patch info
    C    patchlevel   0
    C    patchno      26
    C    patchcomment MSSQL: GetNextMsst1 error (754819)
    C  np:(local) connection used on SAPDEV
    C  Failed to initialize provider SQLNCLI. See note #734034 for more information.
    C  Using provider SQLOLEDB instead.
    C  OpenOledbConnection: line 21990. hr: 0x8000ffff Cannot open user default database. Login failed.
    C  sloledb.cpp [OpenOledbConnection,line 21990]: Error/Message: (err 4064, sev 0), Cannot open user default database. Login failed.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 21990]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  Failed to initialize provider SQLNCLI. See note #734034 for more information.
    C  Using provider SQLOLEDB instead.
    C  OpenOledbConnection: line 21990. hr: 0x8000ffff Cannot open user default database. Login failed.
    C  sloledb.cpp [OpenOledbConnection,line 21990]: Error/Message: (err 4064, sev 0), Cannot open user default database. Login failed.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 21990]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  Failed to initialize provider SQLNCLI. See note #734034 for more information.
    C  Using provider SQLOLEDB instead.
    C  OpenOledbConnection: line 21990. hr: 0x8000ffff Cannot open user default database. Login failed.
    C  sloledb.cpp [OpenOledbConnection,line 21990]: Error/Message: (err 4064, sev 0), Cannot open user default database. Login failed.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 21990]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  failed to establish conn to np:(local).
    C  Retrying without protocol specifier: (local)
    C  Failed to initialize provider SQLNCLI. See note #734034 for more information.
    C  Using provider SQLOLEDB instead.
    C  OpenOledbConnection: line 21990. hr: 0x8000ffff Cannot open user default database. Login failed.
    C  sloledb.cpp [OpenOledbConnection,line 21990]: Error/Message: (err 4064, sev 0), Cannot open user default database. Login failed.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 21990]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  Failed to initialize provider SQLNCLI. See note #734034 for more information.
    C  Using provider SQLOLEDB instead.
    C  OpenOledbConnection: line 21990. hr: 0x8000ffff Cannot open user default database. Login failed.
    C  sloledb.cpp [OpenOledbConnection,line 21990]: Error/Message: (err 4064, sev 0), Cannot open user default database. Login failed.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 21990]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  Failed to initialize provider SQLNCLI. See note #734034 for more information.
    C  Using provider SQLOLEDB instead.
    C  OpenOledbConnection: line 21990. hr: 0x8000ffff Cannot open user default database. Login failed.
    C  sloledb.cpp [OpenOledbConnection,line 21990]: Error/Message: (err 4064, sev 0), Cannot open user default database. Login failed.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 21990]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  failed to establish conn. 0
    B  ***LOG BY2=> sql error 0      performing CON [dbsh#2 @ 1200] [dbsh    1200 ]
    B  ***LOG BY0=> <message text not available> [dbsh#2 @ 1200] [dbsh    1200 ]
    B  ***LOG BY2=> sql error 0      performing CON [dblink#1 @ 419] [dblink  0419 ]
    B  ***LOG BY0=> <message text not available> [dblink#1 @ 419] [dblink  0419 ]
    M  ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c   1271]
    M  in_ThErrHandle: 1
    M  *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   9379]

    M  Info for wp 0

    M    stat = 4
    M    reqtype = 1
    M    act_reqtype = -1
    M    rq_info = 0
    M    tid = -1
    M    mode = 255
    M    len = -1
    M    rq_id = 65535
    M    rq_source = 255
    M    last_tid = 0
    M    last_mode = 0
    M    int_checked_resource(RFC) = 0
    M    ext_checked_resource(RFC) = 0
    M    int_checked_resource(HTTP) = 0
    M    ext_checked_resource(HTTP) = 0
    M    report = >                                        <
    M    action = 0
    M    tab_name = >                              <

    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Server sapdev_DIF_01 on host sapdev (wp 0)
    M  *  ERROR       tskh_init: db_connect
    M  *
    M  *  TIME        Sun Mar 16 14:39:24 2008
    M  *  RELEASE     640
    M  *  COMPONENT   Taskhandler
    M  *  VERSION     1
    M  *  RC          13
    M  *  MODULE      thxxhead.c
    M  *  LINE        9555
    M  *  COUNTER     1
    M  *
    M  *****************************************************************************

    M  PfStatDisconnect: disconnect statistics
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
    M  *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   730]
    M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  246]
    M  Entering ThSetStatError
    M  Entering ThReadDetachMode
    M  call ThrShutDown (1)...
    M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 3576) [dpnttool.c   357]
    PLEASE SEND ME SOLUTION IT'S URGENT
    Thanks in advance
    Karan

    Hi,
    check 551915 - R/3 won't start after database restore or database copy
    don't open two thread for same error.
    homogenus system copy error
    regards,
    kaushal
    Edited by: kaushal malavia on Mar 17, 2008 11:47 AM

  • Product problem in CRM after system copy

    Hi,
    W made CRM system copy - created test system from production system.
    after this we have problems with replication of sales orders from test R/3 to test CRM.
    Product IDs were not replicated, but the rest of order yes.
    I think this is problem with logical systems on products due to system copy.
    What should I do to correct it?
    run BDLS for all product tables , to change logical system production R/3 to test R/3 ?
    Regards
    Radek

    Hi Radek,
        Check the values for Logical System in COMM_PRODUCT CRM table. If its still pointing to your production system, just run the BDLS again. You need to run BDLS for two times. First one to change CRM Old Logical System to CRM New logical system and second one for ECC Old Logical System to ECC new logical system.
    You need to run two times, because for some products ECC is the source system and for some CRM is source system.
    //Bhanu

  • Problems with the Oracle Pre-Load actions in an homogeneous system copy

    Hi,
    I am trying to do a NW04 homogeneous system copy, and I am having troubles with the ABAP copy. (Oracle Pre-Load Actions step)
    I am with the database specific procedure, so I am creating the new system until the sapinst asks me to bring an online-offline backup and the control file, then the sapinst tries to recover the database by himself, but he finds trouble:
    Error: CJS-00084 SQL statement or script failed.<br>DIAGNOSIS: Error message: ORA-01194: file 1 needs more recovery to be consistent Ora-01110: data file 1: 'oracle/XIE...'
    If I try to do the recover manually I have to make the usual:
    RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE;
    CANCEL
    ALTER DATABASE OPEN RESETLOGS;
    If I follow the sapinst.log I find that the sapinst tries to recover the database but fails with the above message and:
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    Yes, that's true, if I make it manually I have to open the database with the 'alter database open resetlogs';
    the problem could be fixed modifying the run_control.sql statement that the SAPINST creates at the working directory, but no modification to that statement is possible because the SAPINST deletes and creates the statement IMMEDIATELY before executing it, so what can I do?
    Many thanks
    Mario

    SOLVED
    for your info, the run_control.sql is UNMODIFIABLE, but I could modify the CONTROL.SQL that he calls, so I recovered manually the Database, and the CONTROL.SQL was a simply CONNECT and then OPEN DATABASE, just like that, so I could continue with my installation, another point for us against the damned SAPINST !!!

  • 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

  • ODS/PSA Problems after System Copy

    Hello All....i am a basis admin and am having problems with PSA after performing system copy. I have copied R/3 (source system) ans SCM (source system) and BW (3.5)systems from production into test environment in parrallel. I have performed all required BDLS steps on R/3, SCM, and BW as well as maintenance of RSLOGSYSDEST table. All profiles and ports (we20/we21) have been maintained as well. I have modified and tested all RFC connections and have used RSA1 to restore the source system connections and to activate and replicate. When activating ODS objects, the following error is generated...
    There is no PSA for InfoSource 8ZFAP_O01 and souce system PB1CLNT510.
    PB1CLNT510 references former production BW logical sys and correct logical sys should be QB1CLNT510. Apparently BDLS has missed a table or I have skipped a step in my post-clone process of BDLS and WE20/21. I am wondering if there is a re-initialization or logical system conversion step i have missed or is anything else i can do to resolve this issue.
    Maximum points awarded for quick resolution.
    Thanks in Advance
    Chris
    Basis

    Hello Chris,
    This InfoSource is related to a DataSource in which the source system is BW system itself (in your case: QB1CLNT510).
    Try to first activate the DataSource 8ZFAP_O01 using the standard program (SE38): RS_TRANSTRU_ACTIVATE_ALL in which you should input the source system (QB1CLNT510) and the InfoSource 8ZFAP_O01. If you get a green light in the log that appears after the activation completes in which it says that all the structures have been activated, then all you need is to locate the DataSource in RSA15 and right click -> replicate.
    If the log showed you that this DataSource doesn't exist, then you'll need to Activate the source system QB1CLNT510 again.
    I hope this helps. Cheerz,
    Ali

  • Problem with extractors after system copy

    Hi Gurus!
    After system copy I have problem with export data source from infocubes. Logical system name was converted  with BDLS. When I check any export datasource (8*) with transaction RSA3 system tell me that no data records was found though data in fact table every infocube exist (in SE11). What can I do to solve this problem?
    Thanx.

    Hi,
    Of course I tried reactivate myself source system but problem is still here. When I check extractor (with RSA3) of any data source of  any infoobject (master data) - everything is OK. When I check extractor for export data sorce - I have problem.
    to Mickael: In modeling every thing is OK.
    Thank you for all answers.....

  • 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.

  • 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

  • Problem restoring source system connection post BW system copy

    Hi.
    I am having problems restoring the R/3 connection in our BW system.
    This is the scenario.
    We need to move our BW production system onto a new system, but keep both BW connected to R/3 production for testing etc until cutover to our new BW system.
    Basis performed a system copy and restore of BW production to the new system and ran BDLS.
    When I try to restore the R/3 connection via RSA1 I am getting the following error at the end-
    "A connection already exists there ......." and the message refers to our current/live BW system. The options are to delete the existing or not delete. I have only chosen "do not delete" and therefore the connection is not restored. My concern is that if I choose "delete" this will damage my existing connection between R/3 and the currently live BW system which is we cannot afford to do.
    In our newly copied BW system we are using the existing R/3 SM59 (from system copy), and in R/3 we have created a new SM59 for our new BW system.
    It seems from the error message information that is complains that BW sent R/3 some sort of ID (value = "WS") and that is already taken by the existing BW system. I tried to find where and what this WS value is referring to and the only thing I have found is that in table RSBASISIDOC "WS" is the suffix for transfer structure for that R/3 system. ??? Not sure if this is related for what.
    Thanks for any help

    Hi ,
    Please check with basis or if you can ,then try to restore the source system in BI/BW.This should correct the  inconsistencies between the two systems which is being caused by different Idoc types
    Also check the table RSBASIDOC in the BI system and compare this to R/3 system ,the "basic type" field should be same.
    A restore should work,it has always worked for me.
    Regards
    Amit

Maybe you are looking for