AS91-Current Yr Migration

Hi ,
We are  doing current yr migration for our fixed assets.I am doing testing for 2010 assets .In AS91 in the takeover values screen,system is only showing ordinary depreciaiton field available but all ther fileds like ***.acquisition value are greyed out,I need to put APC value then dep amount.I set the transfer date  as of  02/27/2010 as per my fiscal year,we are using NOV-DEC fiscal year, so my transfer date is in period 3,2010.When I try to put an asset before 2010 , all the fields are available in takeover values screen including ***.APC value field, but not in case when my APC date is in 2010? Do I need to change my transfer date or something else, Thanks
Regards
Shaun

Sri/Paul.
What I am doing in A91 for current year migration. I am updating ordinary dep field  with values as of last dep period posted in legacy system, then I hit transaction button and doing an external acquisition with TTY 100 and put the APC value for all books.It updates the APC values and showing dep as of year end, and in Posted values tab, it shows the book dep values which I updated in Ordinary dep. field. So everything looks ok. and system also creates a AA acquisition document which is showing up in the asset display under transaction. I guess I dont need to do any seperate F-90 or ABZON , cuz  values are already updated in the asset. and F-90 creates a GL document also, Can I do seperate journal entry to tie out GL with AA. Thanks for your replies.
Regards
Shaun

Similar Messages

  • Office 2010 vs. 2013 - migrating from XP to W7

    I have a client with >200 PCs, and about 50 already run W7 with Office 2010. The remaining 150+ XP PCs are currently being migrated to W7, and the client wants to stay with Office 2010, as they have already purchased 50 or so licenses for their existing
    W7 PCs.
    I am finding Office 2010 licenses harder and harder to find, and much more expensive since Office 2013 was released. The client also has plans to add 50+ PCs during Q4 2014 when a new location is opened. I am hesitant to proceed with their direction,
    if 2010 licenses become no longer available. I know that MS has discontinued sales, and vendors will only be allowed to continue to sell 2010 until their inventory is depleted. My client is aware of this, but they do not want to standardize on 2013 because
    they feel they would then have wasted their money buying the roughly 50 copies of 2010. And they do not want a mishmosh of 2010/2013 in their company, they want to be all on the same version.
    Any advice?I do not want to move them away from Office (to openoffice, Corel, or worse!) but if I can't get them standardized on 2010 they may be forced to move to another platform or worse decide to find a new IT consultant. They understand this is not
    my fault per se, but they blame me for not anticipating this during the last few years when I recommended Office 2010 for their new W7 PCs. No good deed goes unpunished as they say.

    Hi
    Since it is hard to purchase Office 2010, you can take Office 2013 and downgrade to Office 2010.
    However downgrade rights are only available for volume licenses.
    Check the following article:
    http://www.microsoft.com/licensing/about-licensing/briefs/downgrade-rights.aspx
    Tylor Wang
    TechNet Community Support

  • Best Solution to Migrate Application

    Hi,
    We have a application developed for SAP Mobile Infrastructure. It's developed using JSP and Generic Sync.
    We are with problem of performance. Our customer asked for us other solution for application.
    I would like to know, if there is a solution to "migrate" the application on MI Client ito a web application, to this application become a "online" application without re-builiding the current.
    We think to use WebDynpro, but we will have to re-build the application.
    Thanks and Regards,
    Bruno

    Hi Bruno,
    There is currently no migration plan to an online application.That is because there are a number of differences between the offline app and the online app. The offline app uses JSP/AWT with Syncbos as the data models. The online app uses Webdynpro and does not use Syncbos as the data model. So unfortunately you will have to redo it.
    Best Regards,
    Karthik

  • Migration Workbench for migrating IBM DB2 on OS/390 to Oracle 10Gon Solaris

    Hi,
    We are looking to migrate an IBM DB2 database on OS/390 onto Oracle 10G on SUN Solaris. Can anyone help us with a migration workbench toolkit for the same.
    Regards,
    Jagdish Narayanan

    Jagdish,
    We don't currently support migration from DB2 on the OS/390 platform. If you need a solution now, you might investigate a solution from one of our migration partners like Ispirer: http://www.ispirer.com/products/
    Donal

  • Migrate DB2 on an IBM OS390 VM/CMS mainframe to Oracle on NT

    The migration workbench documentation indicates that DB2 on an AS/400 can be converted to Oracle on NT. Has anyone attempted to convert DB2 on an IBM OS390 to Oracle on NT?
    Also, the workbench documentation indicates that stored procedures are not converted from DB2 to Oracle, but they are for Sybase and Informix. Is this true? If so, why doesn't the workbench convert DB2 stored procedures?

    Hi David,
    the latest version of the Migration Workbench (Version 2.0.2.0.0) supports the migration of DB2\400 V4R3 and V4R5 databases to
    Oracle. The Workbench does not currently support migrations from DB2 on the OS\390 and there are no plans to
    provide this through a migration workbench plugin in the short term. The next version of the Workbench, due out in July,
    will support the migration of DB2 UDB v6 and v7 (certified on the MS Windows platform).
    Currently, none of the DB2 Workbench plugins support the migration of parsable objects i.e. stored procedures, triggers,
    etc.. This capability may be added in future releases of the Workbench depending on the demand. Again, there are no
    immediate plans to include a parser with the DB2 plugins.
    If you would like to provide us with any input on what parser capabilities you would like to see in the DB2 plugins (i.e. a
    parser for a certain language?) then we would be delighted to recieve your information.
    I hope this information is of help,
    Tom - Team OMWB.

  • Message store migration question

    Howdy. We are currently testing migration methods between a currently running 5.2 Messaging Server (iPlanet Messaging Server 5.2 HotFix 2.18) to a newly installed 6.3 Messaging Server (Sun Java(tm) System Messaging Server 6.3-0.15).
    We are not running a front end Message Multiplexer so we will suffer some downtime when switching from the old hardware to the new hardware.
    In order to minimize the downtime, we thought that the quickest approach would be to rsync the 5.2 message store onto the 6.3 machine. Due to the fact that the old machine has 8 message store partitions and the new machine has 20 message store partitions, we are doing rsyncs at the user level of the message store (i.e. users end up in different partitions on the new server). Because of this, we cannot migrate the message store databases.
    It appears to us that the message store itself is capable of holding all necessary flags/states/etc. and that we only need to reconstruct on the new system. However, it also appears that stored is "lazy" about updating new data in the databases out to the "store.sub,store.usr,etc." files. When we do our final shutdown of the 5.2 system, we would obviously want the store.* files updated so as to be consistent with the data in the message store databases so that our final rync copies complete consistent data.
    We are at a loss as to how to cause stored to flush/backup/whatever its database information out to the store.* files.
    Is there some way to do this or is our whole migration strategy bogus?
    Vern Gerein
    Senior Systems Administrator
    Server & Database Services
    University of Saskatchewan
    Great White North

    trepan wrote:
    If you are migrating I would highly recommend that the newly installed machine be at the latest patch release. 120228-28 is available on sunsolve.We were waiting for the latest from sun support but they didn't toss it our direction yet. I'll get a co-worker that has an account to grab it from sunsolve.You should be able to access it using the same login as you are using to post to this forum. It is a publicly available patch.
    How large a move are we talking here (size/messages/users)? Also are you using messaging express or just IMAP/POP access?1.4 TB / 35 Million messages / 85,000 users. We are using messaging express and IMAP/POP on the old hardware. We will only be using IMAP/POP on the new hardware (no messaging express).
    Expect to see an increase in overall disk usage due to single-message-copy links being expanded with the increased number of partitions.Our first test rsync from a live system went from 1.4 TB on the old system to 1.6 TB on the new. It is no worse than we expected. I was assuming we'd get a bit of that back if we ran a relink step after the migration.Correct -- the relinker will help to recover some space.
    If I was in your position (and I used to be), I would be looking to add an MMP into the equation so that you could perform user-by-user migrations. This would > allow slower/online migrations which will reduce risk of something going wrong in the move. You can gradually increase the load on the MS6.3 system.We love the idea of being able to do a slower/online migration as you suggest. We had thought about this already be we foresaw one problem with this approach:
    Our current email machine (mail.usask.ca) is used by a LOT of clients so we cannot just deploy a new MMP front end and then ask our client base to now point to that. The only way for us to deploy a MMP front end would be to have it named mail.usask.ca and to change the name of the current 5.2 box to something else. Actually there is another approach that you may not have considered.
    1. Install a 5.2 MMP on the current email machine and reconfigure the existing server to listen on another port for IMAP/POP e.g. 1143 for IMAP and thenn specify the backend port with the MMP so mail.usask.ca:143 (MMP) goes to mail.usask.ca:1143 (backend) for example.
    2. Install and configure new system with a different hostname e.g. mail-server1.usask.ca and configure to listen on the same ports as used in (1)
    3. To migrate the accounts, use the MoveUser utility, this will change the mailhost so email will be redirected and client connections will go mail.usask.ca:143 -> mail-server1.usask.ca:1143
    4. Once all users are migrated, assign the IP for mail.usask.ca to a new MMP frontend server running MS6.3 MMP and MS6.3 MTA.
    NOTE: Step (3) WILL break Messenger Express access but as you said there was no plans on providing ME access on the MS6.3 server this shouldn't be an issue.
    Alas, I don't know of any way to quickly rename an existing Messaging Server (the host name etc. is embedded everywhere, LDAP, configuration files, etc.). The only way I can think of is to reinstall the software. And even if one managed to rename the box, what would it then do with messages that are still in the queues? Of course, I could be missing something simple/obvious.It is possible to do this and requires a lot of planning and testing. Basically the idea is to configure messaging server to recognise itself as two names (mail.usask.ca and mail-server1.usask.ca) and then slowly change the various settings (e.g. users mailhosts: value) from the old hostname to the new hostname. Eventually you work through all the settings till only the clients themselves are actively using mail.usask.ca at which point you assign the IP to a new MMP. If there is a problem you assign the IP back, fix the issue then try again.
    When migrating from Netscape 4.15 to iMS5.2 I had the exact same issue but it was further complicated due to the use of Messenger Express. Since you are not planning on using this going forth this makes things much easier.
    Is there a easy/quick/utterly-and-completely-safe way to rename an existing production 5.2 Messaging Server?Easy, no. Quick, no. Utterly-and-completely-safe, no. But with time, planning and testing it can be achieved.
    Or am I thinking about this in a completely wrong way?There are two approaches mentioned above. I suggest you think which one is going to work for you. In my case I was told in no uncertain terms, the 'migration' must be flawless (i.e. completely transparent to the end-user). It was -- from planning/(re)testing/debugging/customisation/integration to completion took me 12 months (albeit elapsed not effort time).
    Regards,
    Shane.

  • Migrate peoplesoft sybase HRMS database to oracle 11g

    Hi All,
    I want to know if I can migrate a sybase peoplesoft HRMS database to oracle 11g using sql developer 3.0. I am trying to do this following the steps given in the link below but it is taking for ever for the convert step, I could see the messae saying building converted model.
    http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/sqldev/r30/SybaseMigration/SybaseMigration.htm
    The sybase database is 55GB and the version is 12. There are around 20,000 tables in Sybase Database.
    Please advise, if this is possible with SQL Developer??
    If yes, how long this process might take(for each step in the above link), based on any past convertions of the same size database??
    If this is not feasable with SQL Developer because of the complexity of the database, are there any other tools we can look into which might be faster/better than SQL Developer.
    Please advise.
    Thanks..

    Hi Dermot, Tanks for the reply.
    "Do you know the number of views and procedures captured". Below is the ouput from some of the tables in migration repositary.
    count from md_derivatives table, grouped by derived_type.
    MD_CATALOGS     1
    MD_USERS     1
    MD_CONNECTIONS     2
    MD_SCHEMAS     4
    MD_TRIGGERS     40
    MD_VIEWS     34316
    MD_TABLES     48048
    MD_INDEXES     55850
    MD_INDEX_DETAILS     112043
    MD_COLUMNS     766244
    Count from md_views table 34316
    Count from md_additional_properties table 110322
    "Is there a chance the convert phase has hung, or does it refresh ever so ofter with details of another object being "migrated"?"
    It is not hung. I can see the message 'Translating views' right now, and the View names change often but not fast roughly every minute. When I checked for what the session is doing, I could see the below two sql statements.
    SELECT PROP_KEY, VALUE, PROPERTY_ORDER, CONNECTION_ID_FK
    FROM MD_ADDITIONAL_PROPERTIES
    WHERE REF_ID_FK = :1
    ORDER BY PROPERTY_ORDER;
    SELECT ID
    FROM MD_TABLES -- Some times this is MD_VIEWS
    WHERE SCHEMA_ID_FK = :1 AND UPPER (TABLE_NAME) = UPPER (:2)
    "What is the current "Being migrated" information?"
    Translating View xxx.
    "Does the tablespaces your migration repository schema is based on have sufficient space?"
    Yes, Since there is no data at this point, it is all done in one table space which is set to grow UNLIMITED. At this point the size of the table space is a little over 500M.
    "Is SQL Developer being run on the same machine as the Oracle database containing the migration repository? (conversion can be alot quicker for procedure,view,trigger conversion if SQL Developer is on the same machine as the repository)"
    NO. SQL developer is running on my machine but the migration repositary is in the database which is on HP-UX box. Below are some of the details of the server. Also, since the database in on HP-UX, I couldn't find SQL developer for UNIX. I also read in the release note of 3.0 that it is not supported with UNIX, Is that right? else is there a way I can install SQL developer on the Unix server and that might improve the performance!, if yes, please guide me with the steps to do this installation.
    Server:
    Processors: 4, CPU version: PA 8700 CPU module 3.1, clock Frequency: 750MHz, Hardware Model: 900/800/L3000-7x, Kernel width Support 64.
    Physical Memory 8199.3 MB
    Real Memory --> Active: 2990487.0 KB, Total: 3956471.8 KB
    Virtual Memory --> Active: 5787735.5 KB, Total: 6864998.0 KB
    Free Memory Pages: 127049 at 4 KB/page
    Swap Space --> Avail: 4096 MB, Used: 4096 MB, Free: 0 MB
    OS Identification: B.11.11 U
    I see the below when I do a 'glance' on the server. Looks like it is using most of the memory and the Swap. These are the numbers from the server after the migration started, they stay consistent all time with very small variation.
    CPU Util S SR RU U | 34% 31% 39%
    Disk Util F F | 4% 4% 13%
    Mem Util S SU UB B | 93% 93% 93%
    Swap Util U UR R | 86% 86% 86%
    PROCESS LIST Users= 1
    User CPU Util Cum Disk Thd
    Process Name PID PPID Pri Name ( 400% max) CPU IO Rate RSS Cnt
    oraclefap 16560 1 178 oracle 97.9/98.3 132507 0.1/ 0.6 16.0mb 1
    My Machine where SQL Developer is Running
    Windows XP Professional SP3. 2GB Memoery. All this, time I was using around 1 Gb of memory while this process is running, Out of which SQL developer uses only 200 to 300 MB at any given point and the CPU is less than 5%.
    "What version of Oracle database have you installed the migration repository in?"
    Below is the Banner.
    Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    PL/SQL Release 10.2.0.4.0 - Production
    CORE     10.2.0.4.0     Production
    TNS for HPUX: Version 10.2.0.4.0 - Production
    NLSRTL Version 10.2.0.4.0 - Production
    Also please let me know about this request I have popsted. https://apex.oracle.com/pls/apex/f?p=43135:7:2259365896228241::NO:RP,7:P7_ID:29361
    I would greatly appreciate any help. Thanks again.

  • Migration unicode Linux to unicode AIX

    Not sure if this is the right forum.
    I am trying to run heterogeneous system copy of Unicode SolMan 7 Enh 1 system from Source Linux target AIX.
    Having problems with R3load export.
    /usr/sap/SID/SYS/exe/run/R3load -e D010INC.cmd -datacodepage 4102 -l D010INC.log
    -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: Export without hintfile
    (CNV) ERROR: There shall be only one Unicode in a database
    I THINK I have to do a Unicode migration to get from Linux Unicode little endian
    to AIX Unicode big endianu2026
    Is there such a thing as Unicode to Unicode migration documentation anywhere?
    Does current Unicode Migration document have Unicode source section?
    This system already had Unicode migration at SM 7.0 level...
    Does this mean UMG tables need reset?
    Ken

    TRACE      2010-08-10 16:25:53.385 [syuxctask.cpp:1382]
               CSyTaskImpl::start(bool)
    A child process has been started. Pid = 20731
    ERROR      2010-08-10 16:25:53.421 [sixxcstepexecute.cpp:950]
    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 .
    TRACE      2010-08-10 16:25:53.440 [iaxxgenimp.cpp:752]
                CGuiEngineImp::showMessageBox
    <html> <head> </head> <body> <p> An error occurred while processing option SAP Solution Manager 7.0 EhP1 > Software Life-Cycle Options > System Copy > IBM DB2 for Linux, UNIX, and Windows > Source System Export > Central System > Based on AS ABAP and AS Java > Database and Central Instance Export. You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>View Log</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to /nfs/@soulman-t/cd/tmpdir/sapinst_instdir/SOLMAN/LM/COPY/DB6/EXP/CENTRAL/AS/EXP. </p> </body></html>
      export_monitor.java.log -
    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 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04)
    Export Monitor jobs: running 1, waiting 55, completed 0, failed 0, total 56.
    Export Monitor jobs: running 2, waiting 54, completed 0, failed 0, total 56.
    Export Monitor jobs: running 3, waiting 53, completed 0, failed 0, total 56.
    Export Monitor jobs: running 3, waiting 52, completed 1, failed 0, total 56.
    Export Monitor jobs: running 3, waiting 51, completed 2, failed 0, total 56.
    Unloading of 'BALDAT' export package: ERROR
    Export Monitor jobs: running 1, waiting 51, completed 2, failed 2, total 56.
    Unloading of 'BDLDATCOL' export package: ERROR
    Export Monitor jobs: running 0, waiting 51, completed 2, failed 3, total 56.
    Unloading of 'D010INC' export package: ERROR
    Export Monitor jobs: running 0, waiting 51, completed 2, failed 3, total 56.
    Export Monitor jobs: running 1, waiting 50, completed 2, failed 3, total 56.
    Export Monitor jobs: running 2, waiting 49, completed 2, failed 3, total 56.
    Export Monitor jobs: running 3, waiting 48, completed 2, failed 3, total 56.
    Unloading of 'DOKCLU' export package: ERROR
    Export Monitor jobs: running 2, waiting 48, completed 2, failed 4, total 56.
    Unloading of 'DSVASREPODOCS' export package: ERROR
    Export Monitor jobs: running 1, waiting 48, completed 2, failed 5, total 56.
    Unloading of 'D010TAB' export package: ERROR
    Export Monitor jobs: running 0, waiting 48, completed 2, failed 6, total 56.
    Export Monitor jobs: running 1, waiting 47, completed 2, failed 6, total 56.
    Export Monitor jobs: running 2, waiting 46, completed 2, failed 6, total 56.
    Export Monitor jobs: running 3, waiting 45, completed 2, failed 6, total 56.
    Unloading of 'DSVASRESULTSGEN' export package: ERROR
    Export Monitor jobs: running 2, waiting 45, completed 2, failed 7, total 56.
    Unloading of 'DSVASRESULTSATTR' export package: ERROR
    Export Monitor jobs: running 1, waiting 45, completed 2, failed 8, total 56.
    Unloading of 'DSVASTEXTCLUSTER' export package: ERROR
    Export Monitor jobs: running 0, waiting 45, completed 2, failed 9, total 56.
    Export Monitor jobs: running 1, waiting 44, completed 2, failed 9, total 56.
    Export Monitor jobs: running 2, waiting 43, completed 2, failed 9, total 56.
    Export Monitor jobs: running 3, waiting 42, completed 2, failed 9, total 56.
    Unloading of 'DYNPSOURCE' export package: ERROR
    Export Monitor jobs: running 1, waiting 42, completed 2, failed 11, total 56.
    Unloading of 'E071K' export package: ERROR
    Export Monitor jobs: running 1, waiting 42, completed 2, failed 11, total 56.
    Unloading of 'OCSCMPLOBJ' export package: ERROR
    Export Monitor jobs: running 0, waiting 42, completed 2, failed 12, total 56.
    Export Monitor jobs: running 1, waiting 41, completed 2, failed 12, total 56.
    Export Monitor jobs: running 2, waiting 40, completed 2, failed 12, total 56.
    Export Monitor jobs: running 3, waiting 39, completed 2, failed 12, total 56.
    Unloading of 'RSDDSTATEVDATA' export package: ERROR
    Export Monitor jobs: running 2, waiting 39, completed 2, failed 13, total 56.
    Unloading of 'REPOTEXT' export package: ERROR
    Export Monitor jobs: running 1, waiting 39, completed 2, failed 14, total 56.
    Unloading of 'REPOSRC' export package: ERROR
    Export Monitor jobs: running 0, waiting 39, completed 2, failed 15, total 56.
    Export Monitor jobs: running 1, waiting 38, completed 2, failed 15, total 56.
    Export Monitor jobs: running 2, waiting 37, completed 2, failed 15, total 56.
    Export Monitor jobs: running 3, waiting 36, completed 2, failed 15, total 56.
    Unloading of 'SACONT01' export package: ERROR
    Unloading of 'SAPAPPL0_1' export package: ERROR
    Export Monitor jobs: running 1, waiting 36, completed 2, failed 17, total 56.
    Export Monitor jobs: running 1, waiting 36, completed 2, failed 17, total 56.
    Unloading of 'RSDDSTATLOGGING' export package: ERROR
    Export Monitor jobs: running 0, waiting 36, completed 2, failed 18, total 56.
    Export Monitor jobs: running 1, waiting 35, completed 2, failed 18, total 56.
    Export Monitor jobs: running 2, waiting 34, completed 2, failed 18, total 56.
    Export Monitor jobs: running 3, waiting 33, completed 2, failed 18, total 56.
    Unloading of 'SAPAPPL0_4' export package: ERROR
    Export Monitor jobs: running 2, waiting 33, completed 2, failed 19, total 56.
    Unloading of 'SAPAPPL0_2' export package: ERROR
    Export Monitor jobs: running 1, waiting 33, completed 2, failed 20, total 56.
    Unloading of 'SAPAPPL0_3' export package: ERROR
    Export Monitor jobs: running 0, waiting 33, completed 2, failed 21, total 56.
    Export Monitor jobs: running 1, waiting 32, completed 2, failed 21, total 56.
    Export Monitor jobs: running 2, waiting 31, completed 2, failed 21, total 56.
    Export Monitor jobs: running 3, waiting 30, completed 2, failed 21, total 56.
    Unloading of 'SAPAPPL0_5' export package: ERROR
    Export Monitor jobs: running 2, waiting 30, completed 2, failed 22, total 56.
    Unloading of 'SAPAPPL1_1' export package: ERROR
    Export Monitor jobs: running 1, waiting 30, completed 2, failed 23, total 56.
    Unloading of 'SAPAPPL1_2' export package: ERROR
    Export Monitor jobs: running 0, waiting 30, completed 2, failed 24, total 56.
    Export Monitor jobs: running 1, waiting 29, completed 2, failed 24, total 56.
    Export Monitor jobs: running 2, waiting 28, completed 2, failed 24, total 56.
    Export Monitor jobs: running 3, waiting 27, completed 2, failed 24, total 56.
    Unloading of 'SAPAPPL1_3' export package: ERROR
    Export Monitor jobs: running 2, waiting 27, completed 2, failed 25, total 56.
    Unloading of 'SAPAPPL2_1' export package: ERROR
    Export Monitor jobs: running 1, waiting 27, completed 2, failed 26, total 56.
    Unloading of 'SAPAPPL2_2' export package: ERROR
    Export Monitor jobs: running 0, waiting 27, completed 2, failed 27, total 56.
    Export Monitor jobs: running 1, waiting 26, completed 2, failed 27, total 56.
    Export Monitor jobs: running 2, waiting 25, completed 2, failed 27, total 56.
    Export Monitor jobs: running 3, waiting 24, completed 2, failed 27, total 56.
    Unloading of 'SAPAPPL2_4' export package: ERROR
    Export Monitor jobs: running 2, waiting 24, completed 2, failed 28, total 56.
    Unloading of 'SAPAPPL2_3' export package: ERROR
    Unloading of 'SAPCLUST' export package: ERROR
    Export Monitor jobs: running 0, waiting 24, completed 2, failed 30, total 56.
    Export Monitor jobs: running 0, waiting 24, completed 2, failed 30, total 56.
    Export Monitor jobs: running 1, waiting 23, completed 2, failed 30, total 56.
    Export Monitor jobs: running 2, waiting 22, completed 2, failed 30, total 56.
    Export Monitor jobs: running 3, waiting 21, completed 2, failed 30, total 56.
    Unloading of 'SAPDFACT' export package: ERROR
    Export Monitor jobs: running 2, waiting 21, completed 2, failed 31, total 56.
    Unloading of 'SAPDODS' export package: ERROR
    Unloading of 'SAPDDIM' export package: ERROR
    Export Monitor jobs: running 0, waiting 21, completed 2, failed 33, total 56.
    Export Monitor jobs: running 0, waiting 21, completed 2, failed 33, total 56.
    Export Monitor jobs: running 1, waiting 20, completed 2, failed 33, total 56.
    Export Monitor jobs: running 2, waiting 19, completed 2, failed 33, total 56.
    Export Monitor jobs: running 3, waiting 18, completed 2, failed 33, total 56.
    Unloading of 'SAPPOOL' export package: ERROR
    Export Monitor jobs: running 2, waiting 18, completed 2, failed 34, total 56.
    Unloading of 'SAPSDIC' export package: ERROR
    Export Monitor jobs: running 1, waiting 18, completed 2, failed 35, total 56.
    Unloading of 'SAPNTAB' export package: ERROR
    Export Monitor jobs: running 0, waiting 18, completed 2, failed 36, total 56.
    Export Monitor jobs: running 1, waiting 17, completed 2, failed 36, total 56.
    Export Monitor jobs: running 2, waiting 16, completed 2, failed 36, total 56.
    Export Monitor jobs: running 3, waiting 15, completed 2, failed 36, total 56.
    Unloading of 'SAPSDOCU' export package: ERROR
    Export Monitor jobs: running 2, waiting 15, completed 2, failed 37, total 56.
    Unloading of 'SAPSLDEF' export package: ERROR
    Export Monitor jobs: running 1, waiting 15, completed 2, failed 38, total 56.
    Unloading of 'SAPSLEXC' export package: ERROR
    Export Monitor jobs: running 0, waiting 15, completed 2, failed 39, total 56.
    Export Monitor jobs: running 1, waiting 14, completed 2, failed 39, total 56.
    Export Monitor jobs: running 2, waiting 13, completed 2, failed 39, total 56.
    Export Monitor jobs: running 3, waiting 12, completed 2, failed 39, total 56.
    Unloading of 'SAPSLOAD' export package: ERROR
    Export Monitor jobs: running 2, waiting 12, completed 2, failed 40, total 56.
    Unloading of 'SAPSSEXC_1' export package: ERROR
    Export Monitor jobs: running 1, waiting 12, completed 2, failed 41, total 56.
    Unloading of 'SAPSPROT' export package: ERROR
    Export Monitor jobs: running 0, waiting 12, completed 2, failed 42, total 56.
    Export Monitor jobs: running 1, waiting 11, completed 2, failed 42, total 56.
    Export Monitor jobs: running 2, waiting 10, completed 2, failed 42, total 56.
    Export Monitor jobs: running 3, waiting 9, completed 2, failed 42, total 56.
    Unloading of 'SAPUSER' export package: ERROR
    Export Monitor jobs: running 2, waiting 9, completed 2, failed 43, total 56.
    Unloading of 'SAPSSEXC_2' export package: ERROR
    Export Monitor jobs: running 1, waiting 9, completed 2, failed 44, total 56.
    Unloading of 'SAPSSRC' export package: ERROR
    Export Monitor jobs: running 0, waiting 9, completed 2, failed 45, total 56.
    Export Monitor jobs: running 1, waiting 8, completed 2, failed 45, total 56.
    Export Monitor jobs: running 2, waiting 7, completed 2, failed 45, total 56.
    Export Monitor jobs: running 3, waiting 6, completed 2, failed 45, total 56.
    Unloading of 'SAPUSER1' export package: ERROR
    Unloading of 'SASACONT1' export package: ERROR
    Export Monitor jobs: running 1, waiting 6, completed 2, failed 47, total 56.
    Export Monitor jobs: running 1, waiting 6, completed 2, failed 47, total 56.
    Unloading of 'SEOCOMPODF' export package: ERROR
    Export Monitor jobs: running 0, waiting 6, completed 2, failed 48, total 56.
    Export Monitor jobs: running 1, waiting 5, completed 2, failed 48, total 56.
    Export Monitor jobs: running 2, waiting 4, completed 2, failed 48, total 56.
    Export Monitor jobs: running 3, waiting 3, completed 2, failed 48, total 56.
    Unloading of 'SMD_HASH_TABLE' export package: ERROR
    Export Monitor jobs: running 1, waiting 3, completed 2, failed 50, total 56.
    Unloading of 'TST03' export package: ERROR
    Export Monitor jobs: running 1, waiting 3, completed 2, failed 50, total 56.
    Unloading of 'SOFFCONT1' export package: ERROR
    Export Monitor jobs: running 0, waiting 3, completed 2, failed 51, total 56.
    Export Monitor jobs: running 1, waiting 2, completed 2, failed 51, total 56.
    Export Monitor jobs: running 2, waiting 1, completed 2, failed 51, total 56.
    Export Monitor jobs: running 3, waiting 0, completed 2, failed 51, total 56.
    Unloading of '_BI0_F0CCMARSH' export package: ERROR
    Export Monitor jobs: running 2, waiting 0, completed 2, failed 52, total 56.
    Unloading of '_BI0_F0CCMSAEXE' export package: ERROR
    Export Monitor jobs: running 1, waiting 0, completed 2, failed 53, total 56.
    Unloading of 'WDR_ADP_CONST_MP' export package: ERROR
    Export Monitor jobs: running 0, waiting 0, completed 2, failed 54, total 56.
    sample failing package log D010INC.log (they all look the same)
    /usr/sap/SSM/SYS/exe/run/R3load: START OF LOG: 20100810161653
    /usr/sap/SSM/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
    /usr/sap/SSM/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
    Compiled May 22 2010 00:12:41
    /usr/sap/SSM/SYS/exe/run/R3load -ctf E /nfs/@soulman-t/cd/export/ABAP/DATA/D010INC.STR /nfs/@soulman-t/cd/export/ABAP/DB/DDLDB6_LRG.TPL D010INC.TSK DB6 -l D010INC.log
    (RTF) ########## WARNING ###########
            Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
    /usr/sap/SSM/SYS/exe/run/R3load: job completed
    /usr/sap/SSM/SYS/exe/run/R3load: END OF LOG: 20100810161653
    /usr/sap/SSM/SYS/exe/run/R3load: START OF LOG: 20100810161653
    /usr/sap/SSM/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
    /usr/sap/SSM/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
    Compiled May 22 2010 00:12:41
    /usr/sap/SSM/SYS/exe/run/R3load -e D010INC.cmd -datacodepage 4102 -l D010INC.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: Export without hintfile
    (CNV) ERROR: There shall be only one Unicode in a database
    /usr/sap/SSM/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/SSM/SYS/exe/run/R3load: END OF LOG: 20100810161655
    end of logs -
    Ken

  • Sybase SQL Anywhere migration

    Hi all
    I'm migrating a little db (10 tables) from Sybase ASA 7/8 to Oracle 8. How could I do this the better way?
    Thank you

    Sebastian,
    We currently support migration from Sybase Adaptive Server 11.9.2 to Oracle 8i. Sybase SQL Anywhere migration support is under development.
    Turloch
    Oracle Migration Workbench Team

  • Migration from Siteminder DMS to Sun Access Manager

    Hi
    We are working on a project that involves migration of Siteminder and SiteMinder-DMS to Sun Access Manager.
    My concerns are
    1. Do I need any changes to the Directory Tree of the LDAP..?
    2. How do I migrate the policies..>
    3. Does Sun have the exact quivalents(the same coarse grained APIs) as Siteminder-DMS..?
    4. Heard of a tool that can do the migration from Siteminder to Sun Access Manager. How good is the tool and what in its scope and what are its limitations.?
    Thnx
    siva

    I currently reviewing migrating from SiteMinder to Sun Access Manager. I have the same issues as you have had. I would greatly appreciate any feedback on any of these issues. My email address is [email protected] if you prefer to email me directly.

  • Using Entity Framwork migrations with Elastic Scale

    Hi, I wanted to know what is the best practice to update your shards when I have schema changes in the Data base using entity framework.
    In the elastic scale with EF example in MSDN, it relies on the fact that the DB is empty. I want to change the schema on a DB with data and not lose the data.
    Thanks.

    Hi,
    Thanks for your question. The sample for Elastic Scale and EF in the VS Samples Gallery (https://code.msdn.microsoft.com/Elastic-Scale-with-Azure-bae904ba) can use migrations.
    Check out the Migrations folder in the VS project to see some Migrations that we played with in the context of this sample.
    In general, the challenge with current EF migrations and sharding is how to target the migration to the shard. There are the three following cases that we have covered so far:
    Case 1: I have an empty database that needs to be added as a new shard and the schema needs to be provisioned to this new shard.
    Case 2: I am developing and want to apply migrations to my development database (and not the sharded production databases).
    Case 3: I have coded and tested a schema change using migrations on my development database (Case 2) and now want to roll it out across all my shards in the production environment.
    Let's look at these cases one by one.
    Case 1: The sample project deals with this case in the RegisterNewShard function by simply connecting into the shard with a regular connection. EF notices that it is an empty database and creates the schema. This is discussed in the section
    "Shard Schema Deployment through EF Migrations" here:
    http://azure.microsoft.com/en-us/documentation/articles/sql-database-elastic-scale-use-entity-framework-applications-visual-studio/.
    Case 2: The sample project uses a call to SetContextFactory in ElasticScaleDbConfiguration.cs to bootstrap connections to the development database. The connection string for your development database can be configured through a setting in
    app.config of the sample.
    Case 3: My recommendation would be to try using Update-Database calls with a connection string parameter to roll out schema changes iteratively through migrations to the shards in your data tier. Obviously, it would be great to have just
    single call with a shard map parameter for Update-Database. Unfortunately, we do not (yet :-)) support shard maps on Update-Database calls. So, you will need to enumerate your shard connection strings for these calls to Update-Database. As an alternative,
    you can also extract the T-SQL of the migration using Update-Database and then use your SQL Server management tool of choice to roll out the change across your shard fleet.
    Hope this helps. If this does not make sense, please drop me a note at torsteng(at-nospam)microsoft.com
    Thanks,
    Torsten
    This posting is provided "AS IS" with no warranties, and confers no rights.

  • Migrating from mssql to oracle or postgres to oracle

    I have a database driven web application written in J2EE. Currently this application works with Microsoft SQL 7.0 and Postgres 7.3. It uses various datatypes and also has many stored procedures. I will be migrating actual data, table definations and stored procedures.
    Can you please tell me whether to go for MS SQL to oracle migration or postgresql to oracle?

    Hi Margaret,
    The Oracle Migration Workbench MS SQL Server 7 plugin will migrate your MS SQL Server 7 schema, stored programs and data to Oracle. You can freely download the Migration Workbench from the Migration Technology Center on OTN at http://otn.oracle.com/tech/migration/content.html.
    Currently the Migration Workbench does not support migrations to postgres.
    I hope this helps,
    Tom.

  • Migrating BW-BPS to 2004s

    We are planning to upgrade from BW 3.5 to NW 2004s.  Our main concern is with the BW-BPS object migration.  Per my understanding, there are two provisions – BW-BPS and BI-IP - for planning in 2004s (both can run in parallel!!). 
    http://help.sap.com/saphelp_nw04s/helpdata/en/44/05829c6ef7025be10000000a1553f7/content.htm
    Is there any support strategy for BW-BPS vs BI-IP from SAP; like BI-IP will be supported in future upgrades whereas BW-BPS will be terminated?
    Also it looks like if one prefers to go with BI-IP, only certain BW-BPS objects can be migrated to BI-IP and requires new development for other objects.  I have looked at the following link and it is confusing.
    http://help.sap.com/saphelp_nw04s/helpdata/en/44/059baf6ef7025be10000000a1553f7/content.htm
    My specific questions include:
    1. If we decide to stick with BW-BPS in 2004s, then we do not need any new development after the upgrade to continue operating the way we were.  Is this a correct statement?
    2. If we choose to go with BI-IP, the link says “Objects that you created in the planning workbench (transaction BPS0) for BW-BPS must be migrated to the new objects in the planning modeler. Once any necessary remodeling is complete, you have to create the objects as new objects in the planning modeler. You can use the old objects as templates.”  Does it mean that all the objects created using BPS0 transaction have to be re-created in the planning modeler of BI-IP?  Why does it say “You can use the old objects as templates.”?  Some one who have migrated from BW-BPS to BI-IP, please comment.
    3. Looks like the whole authorization concept has changed, how smooth is the migration of authorizations from BW 3.5 to NW 2004s?
    4. We use SEM_BPS_NO_LOCK.  Is this supported in NW 2004s?
    5. What’s your take on BW-BPS vs BI-IP in 2004s?  Which one is recommended and how smooth is the transition to BI-IP provided we have 3 basic planning areas and 2 multi-planning areas with 100 planning levels?  Please comment.
    All the helpful information will be rewarded.  Please also provide me with the links/documents where I can learn more about the migration from BW-BPS to BI-IP.

    Hi Sean,
        Here are some thoughts on your questions below:
    A) you should be able to go directly from 3.2 (BW 3.1) directly to 6.0 (NW04s BI).  An intermediate step is not necessary.
    b) not sure exactly what you are suggesting with this.  If you mean stop using SEM-BPS and use BW-BPS this can't really be done.  Once you've installed SEM on your BW box it's there forever.  Therefore you'd have to upgrade to SEM 6.0.  I believe the only way you could avoid SEM 6.0 is a fresh install of BW.  (not sure if I'm understanding your question correctly)
    c)  This option would allow you to enhance the frontend experience for the end users and allow you to leverage the BW frontend components (queries, structures, variables, etc.) in planning.  The drawbacks are that there isn't currently a migration tool so you'll have to do some rework to get there.  In addition if you're using some of the SEM only functions (allocations, etc.) thost functions don't yet exist in IP so they'd have to still be executed via SEM-BPS or rebuilt in fox.

  • Migration from powerbook 10.4.11 to imac 10.6.8

    Migrating from Powerbook G4 10.4.11 (cannot upgrade beyond this release). Migrating to a new iMac 10.6.8. Problem: both computers are on the same wireless network. Start Migration Assistant on iMac then on Powerbook. Select "From another Mac" on iMac and "To another Mac" on Powerbook. Powerbook sees iMac, offers passcode entry field. Enter Passcode from iMac into Powerbook Passcode field. iMac displays "processing information ...". Powerbook does same. After 10seconds Powerbook displays the Passcode entry field again. Enter the same Passcode from the iMac into the Powerbook Passcode entry field. Powerbook displays "searching for other computers ...". iMac displays "processing information ...". After a few minutes, iMac displays dropdown box stating "connection to other Mac failed" (or similar wording) while Powerbook continues "searching for other computers ..." and iMac Migration Assistant main dialog box continues "processing information ...".
    Any help solving this problem will be much appreciated.
    Steve

    Steve your first mistake is attempting to do this wirelessly. If you can get it to start expect the migration to take a week or more. The easiest way is to connect the two together via Firewire with a cable like this which you can find at your local computer store, Radio Shack or of course Amazon. This assumes the Powerbook has Firewire, if it doesn't then create a bootable clone on an external HD. You will use either SuperDuper or Carbon Copy Cloner to create the bootable clone. Then instead of using Migration Assistant use Setup Assistant which you ignored when you turned on the new iMac for the first time, this mean you will need to start over. Please read Setup Assistant tips for detailed instructions beginning at "Second Chance..."
    Finally when you are migrating I would strongly recommend not migrating your Applications because you are moving from a PPC based machine to Intel. You may have apps that don't run on Intel or simply need to be updated to do so. This is your opportunity to update Apps and get current.
    Migration Assistant and Setup Assistant are cousins, similar but different. First is SA is more reliable and second it does not create a second user account.

  • Migrating mailman from 10.5 to 10.6 Server

    I am currently in migrating my home server from 10.5 running on a Xserve G4 to 10.6 on an Intel Xserve.
    I wanted to document how I migrated my mailman setup from the old to the new server. This may be obvious to many readers of this forum, but I didn't readily find it explained anywhere. It was simple:
    1. Boot old server into Target Disk Mode and connect to new server via FireWire.
    2. Turn off mail service in Server Admin.
    3. In Terminal issue the commands
    sudo mv /var/mailman /var/mailman-stock
    sudo mkdir root:wheel /var/mailman
    sudo chmod 775 /var/mailman
    sudo ditto -V /Volumes/<old server OS drive>/var/mailman/ /var/mailman/
    4. Turn on mail service in Server Admin.
    Done.
    Message was edited by: D. Hoffmann

    Hello, I have checked a bit more.
    When I have replaced the original /private/var/mailman/locks directory:
    rwxrwsr-x@ 2 root _mailman 68 11 11 00:05 locks
    with new one like:
    drwxrwxrwx 4 root _mailman 136 11 11 18:15 locks
    the Permission denied error on this directory stops but it generate another permission error like
    post(34854): IOError : [Errno 13] Permission denied: '/private/var/mailman/qfiles/in/xxx.pck.tmp'
    I guess that proper file mode for Mailman has been changed in 10.6. If there are someone running the mailing list server on 10.6, would you tell me the file mode of these directory, or just a result of following command:
    'ls -l /private/var/mailman'
    Thanks.

Maybe you are looking for

  • How to use multiple submit buttons in jsp form

    hello dextors, Im using a jsp page which have got some 'n' no submit buttons according to the Iterator ..each iterator display a row contains few fields plus submit button ..ex., If ' n' rows means 'n' respective submit buttons..the problem here is w

  • How to remove/displace default signature-block in a widget ?

    I want the signature to be placed in some other position in the document unlike at the bottom. So while creating pdf form by Adobe Acrobat, I created a new signature field and placed at my desired position. But, when I created a wedget through API wi

  • PS CS5 (x64, x32), Windows 7 (x64) - Photomerge crahes PS

    Hi! I use PS CS5 x64 to merge some pics for a panorama with Photomerge, which worked just fine - for awhile. Nowadays whenever I try to use Photomerge crashes PS. There is a note the Event Manager of Windows x64 Ultimate (german): name of crashing ap

  • Verizon Messages sending random texts

    Hi, I have a Motorola Droid HD and I am using Verizon Messages. (I HAVE disabled the phones native messaging app) I have been experiencing the following issues: 1. Most importantly, I noticed that after I send a message, the messaging app will send a

  • Getting a text when a e-mail

    i just go the 8900 and when i get a e-mail from my yahoo account it sends me a text. how do i stop that from happening i still want to get the e-mails on my phone just not the text. and also is using your phone as a modem bad for your phone. i heard