Migration to Linux

Hi all,
We are planning to Migrate 2 production systems 1 which is in Windows and 2nd which is on Hp-Ux to a linux box.Any suggestions or recommendations please
Regards
Bharathwaj V

You will need a certified migration consultant on-site, if you do that on your own, you won´t get any more support for the target system.
The procedure will be R3load (import + export) using a standard installation CD set. What you need to consider is the fact, that HP-UX is a BigEndian platform whereas Linux is LittleEndian - so if you exchange any BINARY data to other systems, they need to be made aware of that.
Additionally, if you have a CRM system connected (to the HP-UX system) you need to change configurations in CRMPAROLTP/CRMRFCPAR to use XML.
Check https://service.sap.com/osdbmigration for more information.
Get back to me if you need more info.
Markus

Similar Messages

Migrating from Linux Mail to Exchange 2013

Is there any official documents of the Best Practices of migrating Linux Mail (Exim) to Exchange 2013?
I appreciate any help that I can receive. Thanks in advance.
My best regards.

Hi,
Basic on my research, I’m afraid that there is no tool for this kind of migration, we may need to start from PST file.
We can use Microsoft Exchange PST Capture to search for PST files on computers in your organization and then import those files to mailboxes in your organization, for your reference:
https://technet.microsoft.com/en-us/library/hh781036(v=exchg.141).aspx
Besides, I find an similar thread about Migrate Exim to Exchange:
https://social.technet.microsoft.com/Forums/office/en-US/0ff095c4-2334-4dd6-8d08-bbee1c98867e/migrating-from-linux-to-exchange-server-2010-question?forum=exchangesvradminlegacy
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Migrating to Linux with Oraacle Application release 11i

Hi There!
I would appreciate your expert advice on migration of Oracle EBS 11i from Solaris to Linux.
We are following Oracle Metalink Doc id 230627.1 & 331221.1 (db 10gR1)
To give a brief picture on the environment, we have 4 servers, PRODUCTION on 2 servers (2 nodes, 1 db, 1 application), TEST on 3rd server and 4th one will act as target for migrating production multi node to single node (Solaris to Linux).
We have planned to make a fresh clone from production to test, it will be multi node to single node clone, then from the cloned test will migrate to Linux on new server (4th server) which will be a single node configuration.
I would like to have advice on the last stage of this process, since the final goal is to migrate the production from Solaris to Linux and we are using cloned instance on TEST for testing the whole process, will it be appropriate to export just the production database to the 4th server using datapump (while importing TABLE_EXISTS_ACTION = TRUNCATE) once the TEST instance is successful migrated to the 4th server? Rather than repeating the whole process again from PRODCUTION to the 4th server.
My point here is since this whole process of migrating the TEST to the 4th server might take a weeks time, the difference between the newly migrated 4th instance and the PRODUCTION will be a weeks data (since the 4th server is migrated from TEST which in turn is a clone of PRODUCTION), so by using datapump we will try to import up to date data from the production to the 4th server, this will save time and efforts by not repeating the whole process from PRODUCTION to the 4th server again. Or is there any better way of achieving this?
Regards.
AK.

What exactly is not supported?
i.) The parameter TABLE_EXISTS_ACTION = TRUNCATE while importing from a full export 'or' This option.
Please correct me if I have understood it wrong, do we still have to migrate the application, since the application is already migrated from TEST instance to the 4th server (the TEST instance happens to be a clone of the PRODUCTION). The only difference we have here is the data that to a week’s data ie the data generated on PRODUCTION instance since it was cloned to TEST. So will it be necessary to do the process all over again.For the application tier node, the simple answer is no (as long as no changes have been done at the application tier node, i.e. applied patches, created new custom forms/reports, ..etc).
If we are importing data into the migrated 4th server from PRODUCTION's full export file, how will DATAPUMP react when it come across already existing database with the same tables, because at this stage i will not be creating the database all over again, since it is already existing when we migrated the db and application from TEST to 4th server (according to the doc). One extra step i will perform in this approach, after importing the DB I will run post clone script on DB just to update tables with node information.The target instance should be clean when you migrate the database tier node, and this explains why the option of using the import parameter is not supported.
As you mentioned above, please log a SR and update this post when you hear back from the Oracle support.
Thanks,
Hussein

OBIEE 10g to 11g Migration on LINUX Machine

Hi All,
I want to Migrate OBIEE 10g (Windows Environment with SQL Server DB) to OBIEE 11g on LINUX Environment with Oracle DB.
If anybody know this can you please help me how to do ?Thnaks in Advance.
As per my Knowledge i know upto this .... "first we need to deploy RPD and WEBCatalog files in to New(OBIEE11g) system and we have to test RPD and WEBCatalog files,Whether these two are working fine or not? Because in OBIEE 10g we have OC4J Server,But in OBIEE 11g Architecture wise it's entirely Different here we have OBIEE WEBLOGIC Server. We have to Deploy RPD in WEBCatlog files in to WEBLogic server. And If any changes have to do in Securities and Variables we need to make changes in that after Migration".
Regards,
Prasad.

Prasad,
Refer the tutorial here..http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm#t4s3
Your approach is correct.

Oracle 10g migration to linux

Hi,
At present we are maintaining a J2EE application running on a UNIX Platform with the following environment configuration:
o Web Server (Apache 2.0.52)
o Application Server (WebLogic Server 9.0)
o Database Server (Oracle 9i)
The current requirement is to upgrade Oracle 9i on UNIX to Oracle 10g on Linux. Will there be any impact on
· Oracle developer applications (Forms/Reports) because of oracle upgrade?
· .net applications accessing oracle because of oracle upgrade?
· Java applications accessing oracle because of oracle upgrade?
And there are plans to use Oracle Warehouse Builder and Oracle Workflow Server. Are there any known issues with respect to the above applications during this migration?
Thanks,

Hi,
Upgrading on the same machine doesn't work well. Installing in a different machine
will work fine.
This can be done for apps also where you will be migrating the config alone.
Regards,
Nirmal

Migrating to linux 4 from linux3 32bit

We are migrating OID server to linux 4 32bit from linux 3 32 bit.
Just wonder if anybody have any suggestion better than to reinstall everything including metadata repository?
we have configured synchronization with AD.
Thanks in advance.

Just to clarify, we are migrating the OS on the box from linux 3 to linux4 not the OID server. We are looing for easier way not to reinstall OID and metadata repository.

Upgrade 11.5.10.2 to R12 and migrate from linux 32-bit to linux 64-bit

Dear all ,
I have two servers :
1. OS . Redhat 4 32-bit have the EBS 11.5.10.2 .
2. OS . Oracle Linux 5.3 64-Bit have the DB 10.2.0.5 .
i want to upgrade the EBS to R12 and migrate it on another server 64-Bit .
Can you provide me please with the steps for this with the notes number.
and should i run the upgrade first or migrate first.
should i download R12 32-bit or 64-bit for linux .
where should i run the rapidwiz .
Note : the DB will stay on the same server and wont change anything on it.
Thanks. waiting your reply.

965322 wrote:
Dear all ,
I have two servers :
1. OS . Redhat 4 32-bit have the EBS 11.5.10.2 .
2. OS . Oracle Linux 5.3 64-Bit have the DB 10.2.0.5 .
i want to upgrade the EBS to R12 and migrate it on another server 64-Bit .
Can you provide me please with the steps for this with the notes number.
and should i run the upgrade first or migrate first.
should i download R12 32-bit or 64-bit for linux .
where should i run the rapidwiz .
Note : the DB will stay on the same server and wont change anything on it.
Thanks. waiting your reply.I would suggest the following:
1) Upgrade the database to 11.2.0.3
Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0) [ID 881505.1]
Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade [ID 761570.1]
2) Install R12 (64-bit) and upgrade to 12.1.1 on Node 1 after you install a 64-bit OS
Oracle E-Business Suite Installation Guide Using Rapid Install
http://docs.oracle.com/cd/E18727_01/doc.121/e12842/toc.htm
Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86-64 [ID 761566.1]
3) Upgrade to 12.1.3
Oracle E-Business Suite Release 12.1.3 Now Available
https://blogs.oracle.com/stevenChan/entry/ebs_1213_available
Note: Please make sure you back up your 11i Apps tier files before you install 64-bit OS on Node 1. In case you have CUSTOM_TOPs you need to copy them to Apps R12 Apps tier (APPL_TOP) which can done before or after the upgrade.
Thanks,
Hussein

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

Portal Migration to Linux server

Hi All
We have deployed Portal 7.01 SP5, ESS6.03 on windows operating system But the end users will be using Linux server.
Can you please advise what all changes are required from portal end for this migration.
Thanks and Regards,
Honey

Hello Honey,
What I can understand from your post is that, end users will be accessing the portal from a linux os (Browser may not be IE ). You may have to make sure that the application is compatible on the browser which the end users are going to access .
Regards,
Vinod

Migrating from Linux to Snow Leopard - how to migrate mboxes

We are moving from a Linux (Fedora) environment to a mac running Snow Leopard server and will need to migrate a couple of our imaped mailboxes - inbox, sent mail, and some folder for a couple of account holders.
We have a mail server that has a problem. We want to replace the entire server (which serves the mail now to everyone) with the new mac server. Same name, same ip address, same everything.
What is the best way for us to do this to ensure that we don't loose any data - and we have a lot (years of company critical messages) of it. This is critical for at least 2 of our key people who must have audit trails of incoming and sent emails for contractual reasons.
Is there some way we can migrate the existing mailboxes over to the new mac server? This is a fedora core linux setup with standard sendmail running with dovecot for imap - if that helps.
Thanks in advance - we are under a major time crunch.

If you mean on a per user bases, then the answer is probably yes... here is an example from http://pwet.fr/man/linux/commandes/imapsync :
To synchronize the imap account buddy on host imap.src.fr to the imap account max on host imap.dest.fr (the passwords are located in too files /etc/secret1 for buddy, /etc/secret2 for max) :
imapsync --host1 imap.src.fr --user1 buddy --passfile1 /etc/secret1 \
--host2 imap.dest.fr --user2 max --passfile2 /etc/secret2
Then, you will have buddy's mailbox updated from max's mailbox.

Migrating from Linux to Mac OS X Server 10.5

I am replacing a Fedora Core 3 Linux Server with an Xserve running Mac OS X Server 10.5.
Would appreciate any migration tips, especially those involving migrating user accounts and user mail over to the new server.
Any help would be appreciated.
Thank you,
Michael

Are your Fedora users in LDAP?
Apple has their own schema file, in /etc/openldap/schema, that is used in their user account entries. An LDIF-formatted user account looks like this, in OSX:
uid: myuser
objectClass: inetOrgPerson
objectClass: posixAccount
objectClass: shadowAccount
objectClass: apple-user
objectClass: extensibleObject
objectClass: organizationalPerson
objectClass: top
objectClass: person
uidNumber: 1039
shadowExpire: 0
shadowLastChange: 99999
sn: 99
apple-generateduid: 463EA237-5AF2-4141-A6FD-889A1DF419FF
cn: My User
gidNumber: 20
authAuthority: ;ApplePasswordServer;0x45e460b23d5fe0010000002000000020,1024 35
1345071926058281304721232558339827013846098893167653281446360984388676425738
50516338293908291285234596987349520801964828311538467653456892088525932177301
75097368617498905044836833794456703593938920562810570915630890501344214295721
35040193131304888799442156409779010254234461994915950682169628843172243920544
77 root@yamnuska:xxx.xxx.xxx.xxx
authAuthority: ;Kerberosv5;0x45e460b23d5fe0010000002000000020;myuser@MYREALM.
CA;MYREALM.CA;1024 35 1345071926058281304721132558339827013846098893167653281446
36098438867642573850516338293908291333433596987349520801964828311538467653456
89208852593217730175097368617498905044836833794492403593938920562810570915630
89050134421429572135040193131304888799442150946779010254251461994915950682169
62884317224392054477 root@yamnuska
userPassword:: KioqKioqKio=
homeDirectory: /Network/Servers/myserver.domain.ca/Users/myuser
loginShell: /bin/bash
description: An Example User
(names and numbers altered to protect the innocent)
You'll have to skip the authAuthority entries. One of them is for the password server, where Apple stores passwords, and the other obviously is for Kerberos. I think I read somewhere that you can actually use the userPassword: field if you put a plaintext password in there. I'd be interested to know if {crypt} or {md5} would work, like they do in regular OpenLDAP deployments.
Once you have the users imported into OpenDirectory, you can create the password server and Kerberos entries using the Server Admin tool, although this might require changing the password.
As for email, are you already using a recent version of Cyrus IMAP? If so, you just need to copy the files over (after importing users). If not, there are scripts floating around that can convert email from other systems to Cyrus.
Cheers
Brent
Message was edited by: Host

Migrating from Linux based Tacacs+ server to Cisco ACS 1113 appliance

I'm trying to migrate my configuration from a Linux based Tacacs+ server to the Cisco ACS 1113 appliance. Does anyone have any recommendations.
Thanks.

Hi
We (extraxi) offer migration and general consultancy for ACS if you need professional help.
www.extraxi.com/contact.htm

Migrating to linux from window 2003

Winodws 2003
Db 9.2.0.7
EBS 11.5.10.2
HRMS application.
I would like to migrate everything from windows to linux(centOS).
Right now we have everything in Single node.
I would ike to split into 2 nodes application and database.
Please give me direction/document.
Thanks.

Hi,
CentOS is not Certified by Oracle, correct?Oracle Apps 11i/R12 is not certfied on CentOS.
VMWare on this not certified , correct?You can install VMWare on CentOS, then install a supported OS which is certified with Oracle Apps 11i/R12.
Regards,
Hussein

Test migration to linux using vmware

I was wondering if in doing a migration from netware to linux that it would be a good idea to do a test migration in a virtual environment (i.e. grab an image of my current netware server and build a virtural sles and do the migration as a test there first?
Anyone tried this?
Thanks!
Pedro

delc9876 wrote:
> Anyone tried this?
Well, I've done plenty of test migrations with VMWare, certainly, but it
really depends on how big your GW system is, etc. whether it's really worth
it. I know it sounds like a "scary" proposal, but it's really not that
difficult of a procedure overall.
Danita
http://www.caledonia.net/blog

Migrating from Linux server to SL 10.6 server

Anybody know a way to get my users/groups from a linux server to SL 10.6 server? It would be a pain to re-do by hand, esp. passwords.

Just take the G4 along with you & decide what you want to migrate from it to the new MBP. As mentioned in Apple Retail Store - One to One, a primary feature of this service is transferring your files from your old computer to your new one for you.

Migration to Linux

Similar Messages

Maybe you are looking for