IS-U Migration Documentation

As Fritz has mentioned several times and there always appears to be a request for this - here is the link for the migration documents as well as the path.
Link to the thread
Guideline IS Migration Workbench (transaction EMIGALL)
Link to the marketplace:
Research Resources and Rules of Engagement
Navigate to the Technical information center > Migration
Direct Links to the documents on the Service Marketplace:
Performance Migration:
https://service.sap.com/~sapdownload/011000358700000500562009E/Cookbook_Perf_Migration.pdf
Migration Guidelines:
https://service.sap.com/~sapdownload/011000358700000500572009E/Guideline_ISMW.pdf
Initial CRM Download Performance
https://service.sap.com/~sapdownload/011000358700000101082010E/Perf_Initial_Download.pdf
regards,
bill.

A new version - v1.03 - of the migration documentation is now available. The same links as above are valid. Thank you Fritz.

Similar Messages

Oracle length semantics migration documention

Due to the oracle documention to migrate length semantics:
To convert an existing schema and its associated data from byte semantics and a single-byte character set to character semantics and a multibyte character set, such as UTF-8, you need only follow these steps: [The following steps have been corrected since the magazine was printed.]
1. Export the schema.
2. Issue an ALTER SYSTEM SET NLS_LENGTH_SEMANTICS=CHAR SCOPE=BOTH command on the target database.
3. Stop and restart the instance so that the parameter change takes effect.
4. Drop the original schema.
5. Recreate the original schema and its tables (you can use import's show=Y option to get the CREATE TABLE statements). Columns in the recreated tables will use character semantics, because that's now the default.
6. Import the schema into the target database using the IGNORE=Y import option.
What is the meaning of the terms target and original?
Suppose there is a (source) database with length semantics byte. If a (target) database
is to be created as a clone of the (source) database, except for the length semantic char, does one have to migrate the (source) database first?
Or rather, why is it not possible to
1. Export the data from the source database with length semantic byte,
2. Create a target database with length semantics char,
3. Import the data from the source database?)

This documentation is, unfortunately, poorly written.
If you want to migrate data from one database to another, with both databases having different character sets, you can avoid some data expansion issues, if you migrate to character set semantics at the same time.
You cannot just export data, and import it into a character semantics database, because export/import preserves original semantics of the exported tables.
Note: there is actually no such thing as a character semantics database. Character semantics is a column/variable property. The "character semantics database" is a confusing, though commonly used, term that actually means an instance which has NLS_LENGTH_SEMANTICS set to CHAR in its initialization file. The only significant meaning of this parameter is to be the default for session-level NLS_LENGTH_SEMANTICS. It is used for sessions that do not set this parameter explictly (through environment variable or ALTER SESSION). The session-level parameter is significant for CREATE TABLE/PROCEDURE/FUNCTION/PACKAGE [BODY] statements and tells the default for column and variable declarations that do not specify BYTE or CHAR explicitly.
To migrate semantics of an original schema you need to create a script that will contain all CREATE statements needed to recreate this schema (at least CREATE {TYPE | TABLE | MATERIALIZED VIEW | PROCEDURE | FUNCTION | PACKAGE [BODY]}). Then, you can just add the ALTER SESSION SET NLS_LENGTH_SEMANTICS=CHAR after any CONNECT command in this script. You can than run the script in the target database. How you create the script is irrelevant. You can use any reverse-engineering tool available (e.g. SHOW=Y option of import, DBMS_METADATA package, etc.)
After you pre-create the schema with the new semantics, you can import the data from the original (source) database with IGNORE=Y. The original semantics saved in the export file will be ignored for pre-created objects.
Note: PL/SQL may need manual corrections to migrate to character semantics. For example, SUBSTRB used to trim values before assignment may need to be replaced with SUBSTR.
-- Sergiusz

Migration Documentation question

Hi,
We are trying to follow the "How To Migrate from SAP Enterprise Portal 5.0 SP6 to SAP NetWeaver '04" documentation, but have questions and open OSS messages.
Does anyone have a set of documentation and or notes that can be followed to a completion of the migration? Any additional notes that may not be in the documentation or at least clear in the documentation?
Open questions:
1. Question on connectivity to the EP5 system from NW04 for migration; In the above mentioned documentation on page 42 in the section 3.2.8 "Defining and Configuring a System for EP5" number 4, it asks for an EP50 Server Port. Is this the default port 80 or is there a way to determine which port to use for this entry?
2. Page not displayed on service configuration; We have our NW04 SP14 Portal build working with Windows Integrated Authentication and our corporate LDAP for Single Sign On with our network ID's. When we login
to the Portal with our network id, we get "Page cannot be displayed" when navigating to System Administration-> System Configuration-> Service Configuration to add the migration key. If we login as Administrator, we can see the Service Configuration page and drill down
to applications - >UpgraderService.
Why does this page not render with our network id's as our network id's have the same roles as Administrator?
Any thoughts on the above questions and any help with better documentation will be greatly appreciated.
Best Regards,
Rick

Thanks, I appreciate your input!
On 8/24/2010 9:36 AM, kjhurni wrote:
>
> Ah, I see.
>
> So if you have a LUN (vdisk, whatever your SAN Vendor calls it), and
> let's say you have 2 or more servers that can access it, but you have
> NOT installed the NCS stuff yet.
>
> I THINK that unless the server try to mount it (and I think you'd have
> to enable the partition/pool thingy as "clusterable") you should be
> okay.
>
> But don't quote me on that one.
>
> I'm also thinking that before you make the resource
> "sharable/clusterable" that you have to install NCS but then make the
> "shared" LUN as shareable before you go making up the Cluster Resource
> objects.
>
> the only exception to that may be the SBD partition (that has to be
> shareable first I think)?
>
> It's been a LONG time since I installed clustering (ours was like 8
> years ago so we've just done upgrades since then).
>
>

OS migration documentation required

Hello Experts.
Can anybody share OS migration document with me?
I need to migrate HP-UX to AIX6.0.
So, please it will be very helpful if anybody share it.
Thanks,
Sudip.

You can use the system copy guides, it contains a path how to do that.
However, heterogeneous migrations must be done using a certified migration consultant on-site, otherwise you will loose support for the migration and for the target system (see http://service.sap.com/osdbmigration). This is also the reason why there are no defined guides for that.
Markus

Migrate WSUS server from 2003x86 to 2008x64, new hardware, use same name and IP address?

Searching through the WSUS forums and reading the TechNET migration documentation, I have bits and pieces of information to make this a smooth transition...I think. I have a plan in mind but
would like the communities input on what I am thinking before moving forward and having it blowup in my face :). <o:p></o:p>
I have the following currently:<o:p></o:p>
A single WSUS 3.0 SP2 server, running on Server Win2003x86, using the default WID (susdb.mdf) on the same server. I have SQL 2005 Express installed on this server as well for other services
but this has no bearing on the WID correct?<o:p></o:p>
What I would like to do:<o:p></o:p>
I have a new server (a much better one) that I would like to move WSUS on to, that will be running Server Win2008x64 (I have to setup first). <o:p></o:p>
Steps that I would like to follow:<o:p></o:p>
1. I will go through and setup this new server with all M$ updates etc... under a new name (ex. wsusnew) and DHCP acquired IP address and then power it down. <o:p></o:p>
2. Get on my current WSUS server and backup all current WSUS settings, groups, DB etc... to a network location for temporary storage. Then power it down.<o:p></o:p>
3. Delete the current WSUS server computer object in AD, DNS entry I will leave because my intension is to give the same IP address to the new WSUS server.<o:p></o:p>
4. Start the new server, static assign the IP address from the old WSUS server to this new server and then change the name of (wsusnew) to the old servers name, which should be ok sense I deleted
the AD object in step 3.<o:p></o:p>
5. After the obvious restart, the new server will have the same name and IP address as the old server. <o:p></o:p>
6. Now that the new server is up (with same settings name/IP as old server), I will then go through and install the WSUS role on the server and restore my WSUS information.<o:p></o:p>
Questions:<o:p></o:p>
1. Step 2 above, is it possible to do this, without making replica servers? I kept reading about this as I was researching doing this, I would rather just copy the DB and folders and simply
put them in-place on the new server.<o:p></o:p>
2. Step 6 above, restoring of the data, what is the proper way to do this in the scenarioI described? <o:p></o:p>
Thank you to anyone who can provide me some information.
Jeff

Thank you for the reply, I will follow and let you know. Proabably be next week sometime before I'm able to try though. So look for a reponse then. Thank you again.
Jeff
OR...
You can use the much more simple, much more reliable, and much more proven method of:
Install new server as a replica of the old.
Replicate.
Configure new server as upstream server.
Point clients to new server.
Turn off old server after all clients have redirected to the new server.
For everybody that has tried the backup/restore the database procedure described above, they have encounted complications of one form or another.
WSUS has a built-in and fully supported comprehensive replication capbility. use it! :-)
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

How to migrate installment plan with open items

Hi all,
I am trying to figure out how to migrate an installment plan, when my legacy system does not tie my open items directly to my installment plans. And the amounts in my open items table may not add up to the exact amount of the installment plan.
So for a simple example, I have $10 left on an installment plan that was created 6 months ago.
Since the creation of the plan obviously more charges and payments have been posted to this account, clearing previously open items and creating new ones.
Presently, I have only 2 open items remaining, one for $6 and one for $7.
So I have "enough" open items ($13 worth) to post the $10 installment plan, but not an exact match.
The way I read the migration documentation on this, I thought I could use a OPUPZ field (Subitem for a Partial Clearing in Document) to signify that I want to partially clear that $7 charge. Apparently I misinterpreted that.
So my question is, is there a way to migrate this installment plan with this set of open items?
Or is my only option to alter the payment plan to the open items, and say that there is $13 remaining on the plan?
Thanks.

C N,
The principal Idea is to migrate either
- the original amounts, the installment plan and last the latest payments (you migrate payment history)
- or to migrate the still open amount as one or more open items and subsequently an installment based on that amount.
Kind regards,
Fritz

Migrating from G5 Xserve to Intel Xserve

I have a G5 Xserve running 10.3.9 Server that is dying a slow and painful death. A new Xserve should be arriving in the next few days. The problem is, the only migration documentation I can find is for 10.4 and above. Is it possible to migrate from 10.3.9? If so, can anyone point me to the proper procedures? If not, what's the best approach to take?

I've found out more technical info about this problem at AFP548.
http://www.afp548.com/article.php?story=20050615173039158
Apparently in LDAP speak, records missing the sn attribute will not import into LDAP databases on servers newer than 10.4. I'm guessing sn is the surname entry under the Information tab for each user in WGM. The sn attribute was introduced to the Mac OS X server LDAP schema in 10.3.9.
That's was it! The 10.4 server that I'm working on started out as a 10.3 server. The sn attribute was added for all existing users to the LDAP database when I incrementally upgraded the OS to 10.3.9. But I had a template in WGM that I used to create new users that did not have the sn attribute. So any new users created using this template after the upgrade to 10.3.9, and even after the upgrade to 10.4, would be missing the sn attribute.

Issue with the EPM migration tool.

Hi All,
I am in the process of migrating Hyperion Performance suite 8.5 to Hyperion EPM system 11.1.1. In the migration documentation PDF I am seeing the screen shots of navigation process. When I try to run migration uitlity tool all the screen shots matches up to objects to migrate screen after that I am supposed to get Hyperion shared services regitry entry screen, but for me utility tool is directly navigating to Hyperion reporting and analysys screen where I can enter BIPLUS entries.
With this I am not able to enter shared services registry database entires al all. Does any one encountered this error. Can you please let me know if I am missing some thing here.
Any help will be greatly appreciated.
Thanks
Prasad

Hello,
Try to apply the new patch 9865650 "Patch 50". We are running 11.1.1.3 and had a similar problem. These problems are fixed in this patch.

Wanted Oracle AIM documentation templates

Hi There,
I would appreciate if someone could be so kind and share/send/upload to me the good old Oracle AIM documentation templates.
I don't need all only couple of them, for example:
MD070, RD070, MD120, etc ...
Thanks in advance.
Regards,
Viktoria

Bruce, historically there have been only two different approaches to IT documentation.
Approach 1 - there isn't any
Approach 2 - the documentation is worthless
Both approaches are in wide spread use today.
If you plan on breaking with IT tradition then I suggest you keep it simple. Plain text or html will be readable years from now without having to have the correct version of any piece of software or someone having to reformat the documentation into a new version of some product or worse trying to migrate documentation stored in one product into a different product altogether.
A simple directory structure fillled with application project definition documents, program descriptions, batch cycle descriptions, and glossaries on a network device that is actually backed up rather than just said to be backed up can prove very useful over time.
HTH -- Mark D Powell --

System Documentation Templates ?

Hi
I have been set the task of comprehensively documenting our systems, especially backup and recovery processes, troubleshooting etc.
Just wondered if anyone has a link to any templates that I could plug all my info into, rather than fiddling around creating new word docs each time ?
(I know its a bit optimistic, but just thought i'd ask)
Any pointers more than appreciated
Cheers
Ian

Bruce, historically there have been only two different approaches to IT documentation.
Approach 1 - there isn't any
Approach 2 - the documentation is worthless
Both approaches are in wide spread use today.
If you plan on breaking with IT tradition then I suggest you keep it simple. Plain text or html will be readable years from now without having to have the correct version of any piece of software or someone having to reformat the documentation into a new version of some product or worse trying to migrate documentation stored in one product into a different product altogether.
A simple directory structure fillled with application project definition documents, program descriptions, batch cycle descriptions, and glossaries on a network device that is actually backed up rather than just said to be backed up can prove very useful over time.
HTH -- Mark D Powell --

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> 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: <ul> <li> Choose Retry to repeat the current step. </li> <li> Choose View Log to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> Log files are written to /nfs/@soulman-t/cd/tmpdir/sapinst_instdir/SOLMAN/LM/COPY/DB6/EXP/CENTRAL/AS/EXP. </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

Migration upgrade from albpm 5.7 to 6.5/Oracle 10g

Hi !
We need to upgrade our current ALBPM bpm 5.7 deployment into portal 6.0, to Oracle 10g/bpm6.5.
1) Does this need to be a two step process. Upgrage from 5.7 to 6.0 and then again from 6.0 to Oracle10g/BPM6.5?
2) Is there any documentation regarding upgrade from ALBPM 5.7 to Oracle 10g or from ALBPM 6.0 to Oracle 10g?
3) What is the portal version supported with ALBPM 6.5/Oracle 10g? Will ALBPM 6.5/Oracle 10g run on Portal 6.1 ?
If anybody has any upgrade experience or can point any ALBPM upgrade related doc.
Please respond.
Thanks and regards
Manoj

Manoj,
Currently the upgrade process is from one version to its direct following version. We are looking forward to implement a straight migration from ALBPM 5.7 to Oracle BPM 10gR3, but this does not have a firm timeline yet. If you are urged to migrate, you will need to first migrate from ALBPM 5.7 to ALBPM 6.0 and then from ALBPM 6.0 to OBPM 10gR3. If you are only migrating your project source code without in flight instance migration, you may want to attempt the export of your projects in ALBPM 5.7 and then import them directly into OBPM 10gR3.
As per the migration documentation, you may want to check in the eDocs for ALBPM 6.0 and OTN for OBPM 10gR3.
eduardoc.

ATG Migration from 9.3 to 10.2

We are migrating our application from ATG 9.3 to ATG 10.2. Please let us know whether we have any direct migration document from ATG 9.3 to 10.2?

You can find the migration guides at:
Oracle ATG Web Commerce Migration Documentation
Here you will see this is a three step migration. See 9.x version from the document above for the steps.

Migrating Groupwise in a mixed node cluster

I am currently migrating from a 2 node netware 6.5 cluster to a 2 node SLES 10 OES2 cluster. we are currently running GW 7. The new linux cluster node has been joined to the exisitng netware cluster to perform a rolling migration. The cluster is utilizing shared storage on an EMC san. I have looked at the migration documentation for GW, but it basically only talks about using the migration tool. Since the linux node has access to the SAN I dont need to actually migrate any data. Is it as simple as installing the GW linux agents on the linux node and failing over the resource? I have read that the GW database files use upper case letters which the linux cannot process and a database conversion needs to be conducted first.
I am looking for some direction since there doesnt seem to be a whole lot of documentation available for migrating GW on a mixed cluster.
Thanks.

I don't think it will be quite that simple. The case conversion needs to be done, in both the files themselves (internally) and, I believe, the files and directory names.
I am not sure if the migration "has" to be done, it may be possible to do an "inplace" conversion (agents down) using gwcheck (standalone) with the case conversion option. For the internal file stuff.
for the file names, there may be a way to do this, scripted, even using linux commands. mv, awk, sed, for example.
Hopefullly, google and others in the forum, can help.
But, if you have the storage, or can create it, just use dbcopy, with the migration option. Depending on how you do it, you would have to alter the cluster startup and shutdown scripts to mount the new volumes.
joe a.
Originally Posted by jturnermia
I am currently migrating from a 2 node netware 6.5 cluster to a 2 node SLES 10 OES2 cluster. we are currently running GW 7. The new linux cluster node has been joined to the exisitng netware cluster to perform a rolling migration. The cluster is utilizing shared storage on an EMC san. I have looked at the migration documentation for GW, but it basically only talks about using the migration tool. Since the linux node has access to the SAN I dont need to actually migrate any data. Is it as simple as installing the GW linux agents on the linux node and failing over the resource? I have read that the GW database files use upper case letters which the linux cannot process and a database conversion needs to be conducted first.
I am looking for some direction since there doesnt seem to be a whole lot of documentation available for migrating GW on a mixed cluster.
Thanks.

NEW XSERVE (migrate from PowerPC G5?)

Hey folks!
I just purchased a new XServe and was wondering how I can get my server migrated over from my Power PC G5. Obviously I'm not running Snow Leopard Server but rather Leopard Server on the G5. Can I just attach the XServe via firewire and "copy" it like I would two iMacs?
Thanks in advance!
-JD

This is really the place to start - it is Apple's official 10.6 upgrading versus migrating documentation:
http://manuals.info.apple.com/enUS/Migrationv10.6.pdf
Because of the PPC <-> Intel thing I think you're forced to migrate versus upgrade but the process is spelled out in some detail.
Good luck,
=Tod

IS-U Migration Documentation

Similar Messages

Maybe you are looking for