Migration of Infospaces with Accelerated version (blade 2.0) of Explorer

Hi Experts,
I would like to know how the Infospaces (Explorer XI 3.2 Accelerated version) are migrated from one environment to other.
Can we use LCM for this? Please clarify. Any pointers for SAP documentation related to this would be really helpful. Thanks.

hi to all guru's
and thanks for replying me
and now i again started the fresh installation but this time i selected non unicode and still i face the errors in IMPORT ABAB phase
check my log
Loading of 'DOKCLU' import package is interrupted with R3load error.
(RFF) ERROR: invalid checksum in data file "D:\ecc6dump\ECC6 DUMP3\EXP11\DATA\DOKCLU.001"
             current table was "DOKCLU"
and this error happens same for SAPSSEXC_1, SAPAPPL0_3, SAPSSEXC_3
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 4, completed 30, failed 0, total 35.
Import Monitor jobs: running 2, waiting 3, completed 30, failed 0, total 35.
Import Monitor jobs: running 3, waiting 2, completed 30, failed 0, total 35.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 2, waiting 2, completed 30, failed 1, total 35.
Import Monitor jobs: running 3, waiting 1, completed 30, failed 1, total 35.
Loading of 'SAPAPPL0_3' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 30, failed 2, total 35.
Loading of 'DOKCLU' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 30, failed 3, total 35.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 30, failed 4, total 35.

Similar Messages

  • BO Explorer Accelerated Version for BWA with BO Enterprise 4.0.2 ????

    Dear all,
    we are currently running a complete BO Enterprise 4.0.2 landscape, including BO Explorer 4 (non accelerated version).
    What we would like to add in addition(!), is an installation of BO Explorer (accelerated version of a dedicated blade) which directly accesses the data in our BWA, but which makes use of the already existing BOE landscape (including CMS, SAP authentication, etc.)
    I checked all documentation on the service.sap.com, etc. and I have to say that I'm a little bit lost about the versions and the naming.
    - There was once a version which was called SAP BO Explorer (blade) 2.0 and in the installation/master guide there was a dedicated part how to connect the new BO Explorer to the BO Enterprise and how to establish a connection between the BO Explorer and the BWA (so exactly what we from my general understanding need to do).
    Unfortunately this guide was always based on the BOE XI3.2 version and NOT on the current 4.0.2 version
    - The successor of SAP BO Explorer (blade) 2.0 is now called SBOP EXPLORER PACKAGE 4.0 (as I can read in service.sap.com), but when I check /instguides for "explorer", I can again read the following:
    SAP BusinessObjects Explorer, accelerated version comprises the following software packages and components:
    SAP BusinessObjects Explorer (blade) 2.0
    SAP NetWeaver BW Accelerator 7.2
    SAP BusinessObjects Accelerator (blade) 1.0
    SAP BusinessObjects Data Services
    SAP BusinessObjects Accelerator Index Designer
    SAP NetWeaver Business Warehouse (optional)
    And now I'm lost. Does it mean that the latest installable blade edition is still SAP BusinessObjects Explorer (blade) 2.0, even when we are running BO Enterprise 4.0.2 ???? If so, is there any major difference between the XI3.2 version from the (blade) 2.0 installation/master guide and version 4.0.2 (except that I do not need the SAP integration stuff anymore)?! Is there an installation guide for BO Enterprise 4.0.2?
    And last but not least, which version is the version which I can find under /swdc
    SBOP EXPLORER ACCELERATED VERSION -> SBOP EXPLORER PACKAGE -> SBOP EXPLORER PACKAGE 4.0
    It seems to me that this is the NON ACCELERATED version - so not the blade edition which is going directly to the BWA...
    OR
    Having the new BO Explorer Version 4 available does not at all require a special blade installation anymore?!? I simply need
    - BWA720 and need to perform the following steps:
    To connect SAP BusinessObjects Explorer with a designated SAP NetWeaver BW Accelerator via the CMC administration page:
    1. Stop the Explorer servers.
    2. Logon to the BusinessObjects Enterprise CMC.
    3. Navigate to Manage > Applications.
    4. Right-click Explorer and click Properties.
    5. Within Advanced Configuration: type the host and port values of the designated BWA.
    For example:
    com.businessobjects.datadiscovery.dataprovider.trex.host=<mybwaserver>
    com.businessobjects.datadiscovery.dataprovider.trex.port=3<TREX_instance_number>16
    Who can help me with this?
    Thanks,
      Andreas
    Edited by: Andreas Freistedt on Jan 28, 2012 10:07 PM

    Dear Anbu,
    long time ago since I did the initial configuration.
    When I remember right, there was an additional parameter in one of the *ini files on the Trex Server, but when I searched I was not able to find any additional parameter - so I guess there is none.
    One thing that I remember is, that we had to use the IP-adress on the BO server configuration instead the server name, as otherwiese the BO server was not able to reach the BWA (but his might be due to our internal configuration).
    Regards,
    Andreas

  • I used migration to send photos form my Mac Book to my I Mac now i get an error message "iPhoto can not be opened because of a problem"  Check with the developer to make sure iPhoto works with this version of Max OSX.  You may need to install any availabl

    I used migration to send photos form my Mac Book to my I Mac now i get an error message "iPhoto can not be opened because of a problem"  Check with the developer to make sure iPhoto works with this version of Max OSX.  You may need to install any available updates or reinstall IPhoto.
    I tried installing Iphoto it said it was downloaded successfully. I still get the error messafe, and can not open any photos of program,  any suggestions?

    What version of iPhoto do you have on the Macbook and on the iMac? What systems are you running on the Macbook and on the iMac?
    Does the message only refer to "a problem" or does it specify what it is?
    Happy Holidays

  • With updating infinity blade 2 version 1.0.1 to 1.2 does your save data get deleted?

    please help me
    with updating infinity blade 2 version 1.0.1 to 1.2 does your save data get deleted?
    tnx every one

    No, it shouldn't. But sync your phone first, this will create a current iPhone backup. App data is included in the iPhone backup.

  • SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

    Hello,
    We are doing an installation of SAP NW 7.01 SR1 on V6R1.
    <br>
    We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
    <br>
    We are again getting error in following steps:
    <br>
    sapinst.log
    <br>
    <br>WARNING 2009-09-30 23:25:28.477
    Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
    IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
    J9VM - 20090309_31291_BHdSMr
    JIT  - 20090210_1447ifx1_r8
    GC   - 200902_24)
    I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
    <br>Loading of 'SAPNTAB' import package: OK
    <br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
    Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
    Loading of 'DOKCLU' import package: OK
    Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
    Loading of 'SAPAPPL1' import package: OK
    Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
    Loading of 'DD03L' import package: OK
    Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
    Loading of 'SCPRSVALS' import package: OK
    Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
    Loading of 'SAPSDIC' import package: OK
    Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
    Loading of 'SCPRVALS' import package: OK
    Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
    Loading of 'SAPSSRC' import package: OK
    Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
    Loading of 'FUPARAREF' import package: OK
    Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
    Loading of 'TODIR' import package: OK
    Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
    Loading of 'SEOSUBCODF' import package: OK
    Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
    Loading of 'E071K' import package: OK
    Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
    Loading of 'SAPPOOL' import package: OK
    Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
    Loading of 'SAPSPROT' import package: OK
    Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
    Loading of 'SAPSDOCU' import package: OK
    Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
    Loading of 'SAPCLUST' import package: OK
    Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
    Loading of 'SAPSLEXC' import package: OK
    Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
    Loading of 'SAPUSER' import package: OK
    Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
    Loading of 'SAPDDIM' import package: OK
    Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
    Loading of 'SAPUSER1' import package: OK
    Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
    Loading of 'SAPAPPL0' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
    Loading of 'SAPSSEXC' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
    <br>
    WARNING[E] 2009-09-30 23:25:28.524
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
    <br>
    ERROR 2009-09-30 23:25:28.914
    FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|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 .
    <br>
    <br>import_monitor.log.
    <br>****************************************************************************************************************************************************
    <br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is successfully completed.
    <br>
    WARNING: 2009-09-30 23:31:31
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2009-09-30 23:31:31
    1 error(s) during processing of packages.
    INFO: 2009-09-30 23:31:31
    Import Monitor is stopped.
    <br>*************************************************************************************************************************************************
    <br>SAPAPPL02.LOG
    <br>**************************************************************************************************************************************************
    <br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) INFO: TVV1 created #20091001110304
    <br>
    (DB) INFO: TVV1 deleted/truncated #20091001110304
    <br>
    (IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
    <br>
    (DB) ERROR: DDL statement failed<br>
    (ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
    DbSlExecute: rc = 99<br>
      (SQL error -539)<br>
      error message returned by DbSl:
    Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
    Your inputs will help a lot.
    Regards,
    Prasad

    Hello,
    We are doing an installation of SAP NW 7.01 SR1 on V6R1.
    <br>
    We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
    <br>
    We are again getting error in following steps:
    <br>
    sapinst.log
    <br>
    <br>WARNING 2009-09-30 23:25:28.477
    Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
    IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
    J9VM - 20090309_31291_BHdSMr
    JIT  - 20090210_1447ifx1_r8
    GC   - 200902_24)
    I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
    <br>Loading of 'SAPNTAB' import package: OK
    <br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
    Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
    Loading of 'DOKCLU' import package: OK
    Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
    Loading of 'SAPAPPL1' import package: OK
    Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
    Loading of 'DD03L' import package: OK
    Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
    Loading of 'SCPRSVALS' import package: OK
    Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
    Loading of 'SAPSDIC' import package: OK
    Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
    Loading of 'SCPRVALS' import package: OK
    Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
    Loading of 'SAPSSRC' import package: OK
    Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
    Loading of 'FUPARAREF' import package: OK
    Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
    Loading of 'TODIR' import package: OK
    Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
    Loading of 'SEOSUBCODF' import package: OK
    Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
    Loading of 'E071K' import package: OK
    Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
    Loading of 'SAPPOOL' import package: OK
    Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
    Loading of 'SAPSPROT' import package: OK
    Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
    Loading of 'SAPSDOCU' import package: OK
    Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
    Loading of 'SAPCLUST' import package: OK
    Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
    Loading of 'SAPSLEXC' import package: OK
    Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
    Loading of 'SAPUSER' import package: OK
    Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
    Loading of 'SAPDDIM' import package: OK
    Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
    Loading of 'SAPUSER1' import package: OK
    Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
    Loading of 'SAPAPPL0' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
    Loading of 'SAPSSEXC' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
    <br>
    WARNING[E] 2009-09-30 23:25:28.524
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
    <br>
    ERROR 2009-09-30 23:25:28.914
    FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|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 .
    <br>
    <br>import_monitor.log.
    <br>****************************************************************************************************************************************************
    <br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is successfully completed.
    <br>
    WARNING: 2009-09-30 23:31:31
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2009-09-30 23:31:31
    1 error(s) during processing of packages.
    INFO: 2009-09-30 23:31:31
    Import Monitor is stopped.
    <br>*************************************************************************************************************************************************
    <br>SAPAPPL02.LOG
    <br>**************************************************************************************************************************************************
    <br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) INFO: TVV1 created #20091001110304
    <br>
    (DB) INFO: TVV1 deleted/truncated #20091001110304
    <br>
    (IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
    <br>
    (DB) ERROR: DDL statement failed<br>
    (ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
    DbSlExecute: rc = 99<br>
      (SQL error -539)<br>
      error message returned by DbSl:
    Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
    Your inputs will help a lot.
    Regards,
    Prasad

  • SAP ECC error:'Migration Monitor' exits with error code 103.

    Hi All,
    I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
    I am stuck at the import ABAP.Getting error
    ERROR 2008-08-08 16:10:53
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    1) imort_monitor.java.log-->contains
    java version "1.4.2_12"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
    Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
    Import Monitor jobs: running 1, waiting 0, completed 18, failed 0, total 19.
    Loading of 'SAPVIEW' import package: ERROR
    Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
    2)import_monitor.log
    ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPVIEW' import package is interrupted with R3load error.
    Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
    For mode details see 'SAPVIEW.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    INFO: 2008-08-08 16:10:52
    All import packages are processed.
    WARNING: 2008-08-08 16:10:52
    1 error(s) during processing of packages.
    INFO: 2008-08-08 16:10:52
    Import Monitor is stopped.
    3)SAPVIEW.log
      error message returned by DbSl:
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) ERROR: DDL statement failed
    (CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001"  ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001",  T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
    DbSlExecute: rc = 103
      (SQL error -942)
      error message returned by DbSl:
    (DB) INFO: disconnected from DB
    D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
    D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
    Only SAPDB: SAPSID srvice of SAP DB is only up.
    No other services of database are  up.And i am not able to up the other services also.
    Is it required to up the other services?
    If not?
    Why this error is occuring?
    Any help will be appreciated.
    Thanks&Regards
    Manisha das

    Hello Manisha,
    The one of the possible reasons for this is due to lack of H/W.
    Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
    If the issue is with H/W, then this should fix the issue.
    Hope it helps,
    Regards,
    Satish.

  • How can I open a project made in 2000 on Final Cut Pro to migrate it to a new version?

    how can I open a project made in late 2000 on Final Cut Pro to migrate it to a new version to finish editing it? files, timeline and unfinished edit are all stored on hard drive since early 2001, with all the original miniDV tapes still in hand

    Do you still have legacy FCP? If you not you need to find someone who will open the project in FCP6.0.6 or later. Export an XML file of the project. Use 7toX to convert it to an XML format that works with FCPX. Import the converted XML file to FCP.

  • API5036: Client Version 10.1.0.4 is not compatible with Repository version

    I have an OWB repository version 10.1.0.1.0 and a client of 10.1.0.2.0. We have have been running this fine. I need to upgrade to 10.1.0.4.0 of OWB so I can begin to use a 10gR2 database as my target. I exported (database wise) my repository and imported it into the 10.2.0.1 database - all went well. I now went to upgrade the repository from 10.1.0.1.0 to 10.1.0.4.0 and ran the shell in the ../bin/unix dierctory. It ran fine, yet when I connect to the repository using the 10.1.0.4 client I get the "API5036: Client Version 10.1.0.4 is not compatible with Repository version 10.1.0.1.0" as if I never ran the DT upgrade shell. I then noticed the shell provided with the 10.1.0.4 install is DTupg92to10g.sh and I am not upgrading a 92 repos to a 10 repos. Is there a upgrade for 10.1.0.1.0 to 10.1.0.4.0?
    Thanks,
    Sean

    for OWB metadata, run this following script
    <OWB_HOME>/owb/reposasst/upg/upg10gTo10104.sql
    For runtime data
    <OWB_HOME>/owb/bin/unix/RT_upgrade_to_10_1
         This is only if it's NOT upgrading to 10gR2 database
    If you are upgrading to Oracle10g Release 2 with partial export and
    import and if you are changing the database instance or the computer
    hosting the database, then run the migration script:
    – For UNIX, navigate to OWB_HOME/owb/bin/unix and run
    RT_migrate_to_10_1.sh.
    The RT_migrate_to_10_1.sh prompts you for several parameters:
    the User Name and Password of your original Runtime Repository
    schema, the database connection string for your original Runtime
    Repository (in the form of host:port:servicename), the User Name
    and Password for your new Runtime Repository schema (whose values
    should match the original Runtime Repository), and the database
    connection string for the new Runtime Repository (also in the form of
    host:port:servicename). Additionally, as it runs, the script prompts
    you for SYS User Names and Passwords for the Oracle Database
    instances for any Target Schemas and Oracle Workflows being upgraded.

  • Firefox 4 Menu Bar - When I hover over or select a menu bar item, the menu bar sub-menu becomes transparent and unreadable. Is this a known issue that can be corrected with an update or is it functionality that is not designed to work with this version?

    Firefox 4 Menu Bar - When I hover over or select a menu bar item, the menu bar sub-menu becomes transparent and unreadable. Is this a known issue that can be corrected with an update or is it functionality that is not designed to work with this version?

    If this happens on monitor 2 of 2, this problem has been solved here:
    http://support.mozilla.com/en-US/questions/794823#answer-157988
    Go to "Firefox"--> "Options" --> "Advanced"
    Then un-check "Use hardware acceleration when available"
    While not verified, I believe this problem is due to an SLI configuration where the focus is on monitor 1. (I.e acceleration is available, but only on monitor 1.)

  • My web pplication does not working with new version of firefox 31. It uses heatmap.js plugin for leaflet.js to build temperature map.

    There is site for heatmap.js: http://www.patrick-wied.at/static/heatmapjs/example-heatmap-leaflet.html
    It has example for leaflet layer.
    After update firefox to version 31 I could not see temperature map in browser for this example. But with previous version of firefox I could see it.
    My web application users leaflet.js and heatmap.js plugin. It users the same code as on the example page.
    After updating firefox version it saying "your script take too long time to run. Continue?" again and again and temperature map does not appear.
    I use leaflet-0.7.2.js and heatmap-1.0.js plugin for leaflet.

    Seems to be working here.
    You can try these steps in case of issues with web pages:
    You can reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.
    *Hold down the Shift key and left-click the Reload button
    *Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
    *Press "Command + Shift + R" (Mac)
    Clear the cache and cookies only from websites that cause problems.
    "Clear the Cache":
    *Firefox/Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"
    "Remove Cookies" from sites causing problems:
    *Firefox/Tools > Options > Privacy > "Use custom settings for history" > Cookies: "Show Cookies"
    Start Firefox in <u>[[Safe Mode|Safe Mode]]</u> to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.
    *Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
    *Do NOT click the Reset button on the Safe Mode start window
    *https://support.mozilla.org/kb/Safe+Mode
    *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

  • Redwood: Migration from Basic to Full version

    Hi All,
    Our client is now going ahead with OEM version of REDWOOD and will plan for full blown version in future. In this regard, we wanted to know the possibility of migrating all the existing stuff (like all the created scripts, job chains, time windows etc.). Request your inputs in this regard.
    Thanks and Regards,
    Vithalprasad

    Best way to do it is use oracle export, import.

  • SAP Basis/Abap components with diff Version inEnterprise Service Builder

    Dear Experts,
    We have PI 7.4 system in our environment, when i check content in ESR, i have found different versions components as below.
    SAP ABA  7.30
    SAP BASIS 7.02 & SAP BASIS 7.40
    I would like to know, since system is 7.4 version, do I need to maintain SAP ABA & Basis with 7.4 content only. Would there be any impact on developments/Models which are done using above version of ESR Content if I upload 7.40 Version content.
    If I am not wrong developments/Models done with above versions would work with 7.40 too, but keen on to know what would be impact if I upload
    7.40 Content in system.
    Is there any possibility migrate developments/models/object to *tpz from above versions to 7.40 , if required.
    I have checked SAP Note 1632370 - Maintenance of ESR Content (XI Content),SAP Note 1865292 - SAP NetWeaver 7.4: Import of ESR-Content,
    and also link Importing ESR Content - Configuring Process Integration (PI) After Installation - SAP Library
    still i dont see any information related to PI 7.4
    SAP Note 1632370 has attachment where it only provides 7.30 version related ESR information.
    Regards
    ks

    Hi Giridharan,
    Thanks for reply.
    I have gone through sap note 1868799 - SAP Basis ESR content versions after PI upgrade had clarified my questions.
    There is no issue with seeing multiple versions of the SAP Basis content in the ESR or in the Integration Builder.
    The Communication Channels will continue to work as normal using the old SAP Basis version.
    The SAP Basis content contains the Adapter Metadata.
    New adapter features are delivered with this Adapter Metadata.
    If you have no business requirement to use any new features, then you don't need to make any changes to the existing channel configurations.
    If you do have a requirement to use any new features, then you will need to change from the pre-upgrade version to the new PI version.
    New channels can use either the older SAP Basis versions or the new SAP Basis version (it makes more sense to use the newer version).
    Regards
    sk

  • BO Explorer Non accelerated version

    Hi All,
    I am looking for documentation related to the architecture of BO Explorer non accelerated version. Any help will be appreciated.
    Thanks,
    Nisha

    Hi Nisha,
    If you have found the architecture document for your non accelarated version search, please share with me.
    We are in the process of installing the BO server and configuring the tools.
    Thanks

  • I have installed Firefox4 to find it is not compatible with my version of OSX how do I get version 3.6 back or do I just give up and use Safari?

    I downloaded Version 4 and installed it. At no point did it say that it was not compatible with the version of OS X that I am running (10.4.11) now that it is installed it will not open but it has already up graded from 3.6 so I have lost the lot. How can I download a version of 3.6 so that I can use it again or should I just pack up and use Safari as all I can get from your site is version 4. HELP!!!

    Go to this link and find your language:
    http://www.mozilla.com/en-US/firefox/all-older.html

  • Add management server: Setup version: 7.0.9538.0 is not compatible with database version: 7.1.10226.0

    I want to add another management server to our existing SCOM environment. But whenever I run this setup on a new server I get stuck in the window for selecting the OperationsManager database. The database field stays blank and in the OpsMgrSetupWizard log
    there are lines that the setup version is not compatible with the database version. But I use the same installer as when I installed the other management servers a year ago.
    Maybe there is a newer setup installer? But I can't find it.
    [10:42:54]: Error:
    :Error:setup version: 7.0.9538.0 is not compatible with database version: 7.1.10226.0
    [10:42:54]: Info:
    :Info:Using DB command timeout = 1800 seconds.
    [10:42:54]: Info:
    :Info:isOMDatabase:  Read returned true.  so far, this is OM DB, not an empty DB
    [10:42:54]: Debug:
    :Connection was not open.  We will try to open it.
    [10:42:54]: Debug:
    :SqlConnectionReady returned True.
    [10:42:54]: Info:
    :Info:Using DB command timeout = 1800 seconds.
    [10:42:54]: Info:
    :Info:isOMDatabase:  Read did not return true.  The MG is missing. This is not OM DB
    [10:42:54]: Info:
    :Info:Using DB command timeout = 1800 seconds.
    [10:42:54]: Always:
    :Azman store table not found in OperationsManagerDW table, assuming this is an not a valid OMDB for empty DB scenario.
    [10:42:54]: Info:
    :Info:DatabaseConfigurationPage: DB connection attempt completed.
    [10:42:54]: Info:
    :Info:DatabaseConfigurationPage: DB connection attempt completed.

    Never mind, found it!
    Apparently there was a newer version of SCOM setup in msdn and someone upgraded our existing SCOM environment. Downloaded the new setup, new report viewer controls and a System
    CLR Types for Microsoft® SQL Server® 2012 and now it works!! 

Maybe you are looking for