Migrate Central instance from 32-bit to 64-bit

Hi All,
We have SAP in Distributed Environmnet( Central Instance running on 32-bit windows & Database instance is running on 64-bit AIX).
Since there are lots of memory dumps , we have decided to upgrade Central instance from 32-bit to 64-bit windows.
We don't want to disturd database instance as it is alredy running on 64-bit.
Please share your thoughts to accmplish this task.
Thanks in advance
regards
Venu

Ah ... during this migration, it'd also be nice to migrate your CI to a virtual name. This way, for future migrations, you won't have to change the profiles.
If you decide not to migrate to a virtual name, then make sure you adjust the default and instance profiles to reference the new server name for CI.
If you decide to migrate to virtual name ...
1. Assign 2nd static IP to your server.
2. Insert your virtual name in the following registry and reboot:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 > create new multi string variable with name "BackConnectionHostNames" and put as value the virtual name.
yourHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters > create new multi string variable with name "OptionalNames" and put as value the virtual name.
3. Adjust the c:\windows\system32\drivers\etc\hosts to include mapping of 2nd static IP to the virtual name.
4. Map your virtual name to the secondary static IP in WINS.
5. Make sure you rebooted the server. Log into the server and do a "net view virtualname" and "net view physicalname", both should be successful. Do not continue until this is successful, most problems are caused by DNS vs WINS, some corporations need the mapping in DNS and not WINS, some the otherway around.
6. Change the user variable to include SAPLOCALHOST and SAPLOCALHOSTFULL, set both to the virtual name.
7. Adjust the start and instance profile of the CI to include SAPLOCALHOST and SAPLOCALHOSTFULL.
8. Cycle the SAP NT services to make sure the new user variables are adapted.
9. Adjust all default and profiles to adapt to the new CI.
10. Adjust STMS to use new CI name.
And, you can also migrate DB to a virtual name as well using the same registry entries. Except DB name doesn't require it's own IP, so it can share the same IP as the physical server. Adjust the user environment variables and SAP profiles afterwards to adapt to new virtual name.

Similar Messages

Migrating perl application from 32 bit to 64 bit

Hello,
I am migrating an application which is written in perl from 32-bit Solaris 2.5 to 64-bit Solaris 9. What part of code should I concentrate? Is there any guidelines available for the same? Any help would be greatly appreciated.
Devesh.

There are Sun 32bit to 64bit programming guides. Check http://docs.sun.com/ .
Also, Perl is an interpeted language. Unless you're using the "C" interface and/or doing some bit twiddling, I would think it would run "as is". You may want to google perldoc.com for more info.
HTH,
Roger S.

Migration of EBS from 32 bit to 64 bit

Hi
I want to migrate my EBS (11.5.10.2) from SUSE Linux 10 32 bit to SUSE linux 10 64 bit.
I want to upgrade EBS from 11.5.10.2 to 12.1.1.
As this Production I want to reduce the max down time.
I know that 11i is not supported on 64 bit architecture.
Can you please guide me the migration path on higher level
Thanks

IMO, the following would be the best approach.
1. Lay down R12 (12.1.1) software on the new 64-bit server
Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86-64 [ID 761566.1]
Oracle E-Business Suite Installation Guide: Using Rapid Install
http://docs.oracle.com/cd/E18727_01/doc.121/e12842/toc.htm
2. Upgrade 11i to R12 (12.1.1)
Oracle E-Business Suite Upgrade Guide
http://docs.oracle.com/cd/E18727_01/doc.121/e16342/toc.htm
3. Upgrade 12.1.1 to 12.1.3
Oracle E-Business Suite Release 12.1.3 Now Available
https://blogs.oracle.com/stevenChan/entry/ebs_1213_available
If you have any queries about migrating the database, please mention your database version and whether you want to migrate it to 64-bit (or if it's already running on 64-bit OS).
Thanks,
Hussein

How to Migrate SSIS packages from 32 bit to 64 bit environment

Hi,
We developed many SSIS packages in 32 bit environment using SQL 2008 on windows 2003 server 32 bit OS. In order to utilize the 64 bit features we wish to migrate these packages into a 64 bit. Wanted to know.
1. Whether we can execute these packages that are developed in 32 bit environment onto a 64 bit environment. If yes, then do we get the benefits of 64 bit environment. For ex. RAM utilization. If no, then what advantage do we get.
2. Is it possible to develop the packages directly in a 64 bit environment.
Thanks in advance,
Yog

One thing you need to make sure when migrating to 64 bit machines is to have drivers installed for 64 bit ie for providers like excel. One more thing to note is that SSDT/BIDS which is used for developing packages is by itself a 32 bit application. So
you may need to use 3 bit driver at design time and run packages with 64 bit runtime set to false at design time. And while deployed on server it can use 64 bit driver itself for its execution.
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

Changing OS of Central Instance, is it a heterogenous Systemcopy?

Hello,
I can't find a clear document.
We have a distributed landscape.
We want to change the OS of the Central Instance from AIX to Linux. The DB Sever remains the same (HANA/Linux).
Is it a heterogenous copy?
The guides etc. don't mention distributed landscapes.
To my mind I'll stop the system, install the new CI, move releveant files (Joblogs etc to the new instance) and restart it. Perhaps a bit postprocessing because of changing hostnames.
So no additional Export/Import will be needed as the DB remains untouched....
Thanks
Jan

Hi Jan,
To my mind I'll stop the system, install the new CI, move releveant files (Joblogs etc to the new instance) and restart it. Perhaps a bit postprocessing because of changing hostnames.
Yes, you will stop application server and then install new PAS, move relevant files(including host and services) and post-processing, including keys and updating IP/hostname(where-ever used).
This is not a system copy - homogeneous or heterogeneous.
It's not a migration of system, it's just a switching of application platform.
Regards,
Divyanshu

ISetup - R12, Central Instance

The Oracle iSetup R12 user guide says that having a separate central instance from which Oracle iSetup runs is highly recommended, but then goes on to say that iSetup can be run from the source or target instance as well.
Can someone tell me the benefits of having a separate central instance?
Also, how did you determine which instance was appropriate to use as the central instance? (We have number environments such as dev, test, qa, prod, patch, train, etc...These environments are periodically refreshed with Prod. If we were to install iSetup on any of these, once a refresh took place we would lose it. What is the recommended way to retain what has been done with iSetup?
Thanks
Edited by: user12067133 on May 13, 2010 2:02 PM

Hi,
The concept of Central, Source and Target instances are more logical than physical. It is upon you to decide and identify one instance which would stay relatively for longer period so that you can keep backup of your extracts in the instance. If all your instances are refreshed frequently, then you can download the extract zip file of your interest and source control it. Once the instance comes back online, you can upload the extracts from source control to EBS instance and use it for deployment.
Thanks
Mugunthan

Error - EBS DB importing OLAP from 32 bit to 64

Hi All,
While importing olap aw am getting below error. I know I am making simple mistakes. . I am in stage of migrating EBD DB from 32 bit 64 bit.
Could you please correct me with correct steps.
During export I hv made step like in server xxxxx
SQL> select OWNER, AW_NAME ,PAGESPACES from dba_aws where owner != 'SYS' order by 1,2;
OWNER AW_NAME PAGESPACES
APPS ODPCODE 1106
APPS XWDEVKIT 1082
FPA FPAPJP 504
ZPB ZPBCODE 743
SQL> exec dbms_aw.execute('aw attach APPS.ODPCODE rw');
PL/SQL procedure successfully completed.
SQL> exec dbms_aw.execute('allstat');
PL/SQL procedure successfully completed.
SQL> create directory OLAP_DIR as '/u01/ora/test/db';
Directory created.
SQL> grant all on directory OLAP_DIR to public;
Grant succeeded.
SQL> exec dbms_aw.execute('cda OLAP_DIR');
PL/SQL procedure successfully completed.
SQL> exec dbms_aw.execute('export all to eif file ''OLAP_DIR/export_olap.eif ''');
PL/SQL procedure successfully completed.
I can see *.eif files under '/u01/ora/test/db' and the same step followed for other repostory name.
Now I am in import stage and follwed the step in server YYYY
-> mkdir "olap_dir1" under '/u01/ora/test/db'
SQL>exec dbms_aw.execute('aw create APPS.ODPCODE');
SQL>create directory OLAP_DIR1 as '/u01/ora/test/db/olap_dir1'
#copied all *.eif files from server XXXX to YYYY(/u01/ora/test/db/olap_dir1/)
SQL> grrant all on directory OLAP_DIR1 to public;
SQL>exec dbms_aw.execute('cda OLAP_DIR1'); [ I have tried to import without running this ]
SQL>exec dbms_aw.execute('import all from eif file ''OLAP_DIR1/export_olap.eif'' data dfns');
getting below errors:
BEGIN dbms_aw.execute('import all from eif file ''OLAP_DIR1/export_olap.eif'' data dfns'); END;
ERROR at line 1:
ORA-36786: File OLAP_DIR1/export_olap.eif does not exist or cannot be accessed.
ORA-27300: OS system dependent operation:open failed failed with status: 2
ORA-27301: OS failure message: No such file or directory
ORA-27302: failure occurred at: SlfFopen1
ORA-06512: at "SYS.DBMS_AW", line 93
ORA-06512: at "SYS.DBMS_AW", line 122
ORA-06512: at line 1
while queriying: SQL> select directory_path from all_directories;
DIRECTORY_PATH
/u01/ora/test/db/olap_dir1
/u01/ora/test/db
/u01/ora/test/db/11.2.0/ccr/state
/usr/tmp
/usr/tmp
/usr/tmp
/u01/ora/test/db
/u01/ora/test/db/admin/test/dpdump/
Please help with correct step which I need to follow.
Thanks,
kn

This is a duplicate post - EBS R12 migration to 64 bit Linux

Going from 128-bit to 256-bit encryption

Hello all,
This is my first post here so please be gentle.
I'm a tech manager who inherited an undocumented environment and have a question regarding upgrading the encryption on our 6.1 iPlanet instances from 128-bit to 256-bit.
I've searched through the documentation and I can't seem to get a clear answer.
1. To upgrade to 256-bit do I just need to update the following line in my obj.conf file:
PathCheck fn="ssl-check" secret-keysize="128"
to
PathCheck fn="ssl-check" secret-keysize="256"
2. Are there any dependencies for making this change such as generating a new SSL cert?
Thanks in advance - Bill

Here is some documentation about ssl-check :
http://docs.sun.com/app/docs/doc/820-2203/abujv?l=en&a=view&q=ssl-check
The ssl-check function is used along with a Client tag to limit
access of certain directories to non-exportable browsers. If a
restriction is selected that is not consistent with the current cipher
settings, this function displays a warning that ciphers with larger
secretkeysizes must be enabled.
secret-keysize (Optional) Minimum number of bits required in the secret key.
Which version of 6.1 Server are you using?
$cd <web-server-install-dir>/<web-server-instance-dir>/
$start -versionCan you send your server.xml settings?
Assuming your machine is foo.bar.test.com
$cd alias
$../bin/https/admin/bin/certutil -L -d . -p https-foo.bar.test.com-foo-displays the server's certificate nickname lets say it is Server-Cert
Then try to get the certificate details in ascii format
$../bin/https/admin/bin/certutil -n Server-Cert -p https-foo.bar.test.com-foo-It will show something like :
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number: .... (0x...)
        Signature Algorithm: PKCS #1 SHA-1 With RSA Encryption
        Issuer: "CN=..."
        Validity:
            Not Before: .... 2008
            Not After : .... 2018
        Subject: "CN=..."
        Subject Public Key Info:
            Public Key Algorithm: PKCS #1 RSA Encryption
            RSA Public Key:
                Modulus:
                    bd:10:c2:e0:bc:ad:fd:e6:75:ce:86:82:51:de:bf:37:
                    51:05:06:89:db:c2:6d:0c:31:f4:19:32:90:59:77:c1:
                    a0:6c:ef:88:54:ed:f8:d3:d2:6a:f7:22:f4:c6:95:60:
                    06:3a:64:f3:e4:0c:09:f4:37:c6:44:e7:d4:37:5a:4d
                Exponent: 65537 (0x10001)
...Each line in Modulus section corresponds to 128 bits. In my case I have 4 lines, so my certificates key size is 4*128 = 512 bits.
Can you send your modulus info i.e key size with which your certificates were created?
Edited by: mv on Feb 8, 2008 9:28 AM

Best Practice to migrate existing Message/Central Instance to new hardware?

I've done some searching for this, but it all seems to be fairly old (I found one decent thread from 2008, but it just seemed outdated). I would like to get some updated info & suggestions on a process to follow for this task.
Here is some info about the current config:
I have an existing SAP ERP 6.0 EHP5 system. SID "XYZ"
Everything is currently running on Windows x64.
ABAP only config.
It is currently setup as a distributed system.
DB server is SQL, which is running on its own hardware as a dedicated DB server. I don't need to touch this.
Uses logon groups to distribute the load between 3 App servers.
One of the App Servers is setup as the Message/CI server. This is what I am wanting to move to VM hardware.
The other two App Servers are setup just as Dialog Instances. VM already. I don't need to touch these.
What I am wanting to do:
I am wanting to migrate the existing Message/CI server to VM hardware to get the current Message/CI system off of very old hardware.
I need to keep the system with the same name & IP.
I do not need/want to mess with the DB server at all.
Need to minimize downtime as much as possible.
I do NOT want to go to an HA environment. That is a different project for the future.
Suggestions? I would like to hear what some of you have done.
Minimize downtime? I have a short maintenance window of a few hours coming up in the next few months, and would like to do this changeover during that downtime.
How do I handle setting this up on the new hardware using the same name & IP, especially with the existing system still running.
What I think I need to do: (Some of these may be out of order, which is why I'm asking for suggestions)
Setup new Windows VM server, named differently than current Message/CI server (Done already).
Run SAPINST to run Global Host Preparation on the new Windows VM server.
Run SAPINST to setup ASCS Instance on the new Windows VM server.
Skip the Database Instance installation, since I already have one running.
Run SAPINST to setup Central Instance on the new Windows VM server.
Copy all of the appropriate profile parameters that were on the old server.
Start SAP and make sure everything is running and working correctly.
Copy all job, spool files, etc. from the old server.
What needs to be done in between those steps for the server rename & IP changes?
Which of these steps can I do in advance of my maintenance downtime window, without it affecting the currently running system?
I have a test environment that I am going to test this with. I'm just trying to get a jump start on my instructions, so that I can hopefully do this quickly and easily. I'm very comfortable doing the installs. Just needing some guidance on how to handle this case.
I'm open to suggestions, and any links you can send my way that show some more recent success at doing this. Everything I keep finding talks about doing the migration for the DB. I am not migrating my DB. It is staying where it is. I'm just wanting to migrate my Message/Central Instance to a VM, without affecting the users, and hopefully them never noticing the changes.
Thanks!

If you're using VMWare, there is a tool provided to virtualize existing systems. Basically it makes a copy of the old system (while it is down) and recreates it as a VM with the same name, IP, etc. I haven't double-checked to see if this process is 'officially' supported by SAP, and I don't know the technical details about how it's done or how long it will take (VMWare is managed by the Network Operations group in my team, so as the SAP sysadmin I'm basically a customer of theirs). However, we have virtualized a few smaller systems that needed to get off failing hardware in a hurry and it worked very well, so I would expect it would for an SAP dialog instance as well. As you're not copying a database, just the app server, it probably would fit within your maintenance window.
If this route works for you, then there is no need to actually install the SAP system on the VM instance... you just copy the old server as-is, then make any adjustments required due to no longer needing old drivers, etc, plus potentially having different memory parameters.

Migration from 32-bit to 64-bit on Oracle 9.2.0.5

Hi guys.
I have two question for migration 32 bit to 64 (x86_64) bits on Oracle 9.2.0.5 for SAP 4.7 Enterprise?
1.- When i migrated 32 bits to 64 (x86_64) bits is necesary migrated to Oracle 10 ?
In the note SAP Note 960769 - Windows: Migration from 32-bit to 64-bit (x86_64), say that, pag 4:
" Oracle:
=====================================
On Windows Server 2003 X86_64 (64-bit), you may only use Oracle 10g Release 2 (10.2) software for X86_64 (64-bit) as a database. Note 949116 describes the installation (homogenous system copy) of old products that were not originally released on Oracle 10g Release 2 (10.2). If you want to make the copy using the backup/restore procedure, for which the source database was not yet upgraded to Oracle 10.2, see Note 932722"
But, in the pam matrix say that support for 9.2.
I confused for the information.
2.- In the case that is not necessary to migrate to oracle 10, i can execute the migration to 64 bits the SAP 4.7 with the procedure Backup/Restore?
I don´t have the new server, the server for the migration is the same. The procedure you want to follow is:
1.- Backup Offline all server.
2.- Delete the server, i install the server on Windows 2003 64 bits.
3.- Install SAP 4.7 on kernel 64 bits.
4.- Restore de backup offline (only data): datafiles, archive log, redo log.
Aprecciated for the help.
Best regards,
Desiré

Hi,
According to Note:814834
#Note that there is currently no 64-bit support for the x86_64 platform
for Oracle 9.2 because Oracle does not provide a 64-bit DB client for this purpose,
and, in addition, 64-bit operation of the DB server is not supported.
This means that this DB version can only be used in conjunction with SAP components on
Windows 32-bit on x86_64 hardware in 32-bit mode.
For more information, refer to the "Oracle" section in the note.
Furthermore, it states 32bit SAP instance can connect ot a 32 bit Oracle 9.2 or 10.2 database instance.
So for your case, its better to upgrade your current database to Oracle 10.2 and then proceed with migration.

Migrating EBS from 32-bit to 64-bit

Hi,
I have a R12 Instance(12.1.3) with 11.1.0.7 database on 32-bit Linux. Now we are planning to do a clone of the existing R12 Instance to a newly created 64-bit Linux server. So i would like to know the steps involved in migrating the E-Business Suite from 32-bit to 64-bit.
Regards,
Vineel.C

I had gone through the Metalink Note[471566.1] which you had sent me. It was useful but internally it had referred to another Note:762669.1 which says in Migrate from Linux 32-bit to Linux 64-bit
h.Upgrade the database from 32-bit to 64-bit (recompile pl/sql modules and change the word size) by running $ORACLE_HOME/rdbms/admin/utlrp.sql. Refer to the usage and notes sections in the script for instructions on how to run it.
But in general utlrp.sql is used for compiling Invalid objects.
Can you elaborate on this.Because of the word size change (from 32-bit to 64-bit), the database objects will be invalidated and you need to run utlrp.sql script to compile them.
Difference between UTLRP.SQL - UTLIRP.SQL - UTLIP.SQL? [ID 272322.1]
Changing between 32-bit and 64-bit Word Sizes [ID 62290.1] -- Step 16. Run utlirp.sql
Thanks,
Hussein

Migrating from 32 bit server to 64 bit server

Hi
We have planned to migrate our portal server from 32 bit to 64 bit.
I need your help in identifying the tasks to be performed after the migration.
Migration will be done by a BASIS consultant.
My job would be to make sure that portal is up and running with all the settings same as it is on the 32 bit old server.
We are operating on EP 7.0 (2004s) SPS 13.
We are using LDAP for internal users and UME for external users.
EP system is connected to R/3 4.7 and BI 7.0 systems.
New system will have different IP address and logical name but same SID.
It would be great if I get the url of the help links and documentation.
Regards
Vineet Vikram

Vineet,
Itu2019s difficult to identity all tasks you need because itu2019s depends of your scenario.
But basically you can check:
u2022     UME configuration (configuration, SSL, XML, security policies)
u2022     KM configuration (repository, crawlers, indexes, channels, system, ACL cache, search options)
u2022     Collaboration configuration
u2022     XML form filter
u2022     Anonymous users
u2022     Central portal configuration
u2022     Guided Procedures
u2022     Rule Collection
u2022     Data sources JDBC
u2022     ICE Protocol
u2022     Custom login page
u2022     Group x User x Role association
u2022     PAR and EPA transports
u2022     Web Dynpro applications
u2022     SLD check
Your basis consultant must pay attention some notes:
Note 1024539 - Recommended Settings for NW04 >= SP14, NW 7.0 >= SP6 on AIX
Note 1024700 - Installation/Upgrade information for NW04/NW 7.0 on AIX
Note 680617 - INST: Appl.Server in Heterogeneous SAP System Environment
Note 941735 - SAP memory management for 64-bit Linux systems
Note 861333 - Very slow start of the j2ee engine on AIX with 64bit IBM JDK
Note 723909 - Java VM settings for J2EE 6.40/7.0
Reward points if itu2019s helpful

64 bis DB server with 32 bit central instance

HI,
i ve got a question concerning the hardware configuration of a SAP-landscape. Is it possible to run a standalone dbserver with 64 bit and a central instance (sap application server) with a 32bit machine. I mean does it work, that the data from application server is transferred to the db-server in this constellation ?

Hi Marek,
This is supported once http://service.sap.com/pam lists the combination of DB/OS and SAP kernel for the instances.
It is always important to bring the 32bit and 64bit Kernel to the same (or almost the same) kernel patch after the installation - otherwise the instance(s) might not start. You should restart the system also when updating the kernel for one platform.
Regards, Mark

10g migration from 32 bit linux to 64 bit-synchronizing appsutil

I am currently attempting to migrate my TEST instance from a 32 bit Linux server to a 64 bit Linux server. In a nutshell, I have prepared the new 64 bit Linux host for running the Oracle database. I have also already run adpreclone.pl on source instance apps and db tiers. I am following a number of documents, mostly from Oracle but a few from different blogs.
In following http://levicorp.com/2010/04/08/migration-oracle-10g-db-from-linux-32bit-to-linux-64bit/
I will list the first 5 steps. I am stuck on step 5.
The steps are :
1. Backup source datafile of the database.
2. Copy the backup datafile to destination server.
3. Install the Oracle Software in destination server.
4. Install patchset 10.2.0.4.0 for Linux 64 bit (Patch# 6810189)
5. Do Cloning database, create control file
The new 64 bit Linux server has the 10g database software only. So, on the target server I looked to run adcfgclone.pl , but I noticed that in the new $ORACLE_HOME there was no appsutil folder. What I did next was copy that directory from the source database server over to the target server. I have been unable to run adcfgclone.pl on target server against the db tier. Fails with:
java.lang.NullPointerException
     at java.util.Hashtable.put(Unknown Source)
     at oracle.apps.ad.clone.util.CloneCleanser.doMigrate(CloneCleanser.java:98)
     at oracle.apps.ad.context.CloneContext.doClone(CloneContext.java:710)
     at oracle.apps.ad.context.CloneContext.main(CloneContext.java:5093)
RC-50004: Error occurred in CloneContext:
So I can't help but wonder, was even supposed to do that - copy from one server to another? Is the appsutil directory and its contents somewhat custom relative to the host it's on?

Please post the details of the application release, database version and OS.
Are you migrating the database only?
If this is an EBS database then the supported ways are using export/import of transportable tablespaces.
If you are on 11i with 10gR2 database please refer to:
10g Release 2 Export/Import Process for Oracle Applications Release 11i [ID 362205.1]
Cross Platform Transportable Tablespaces on 11i with 10gR2 [ID 454574.1]
If you are on R12 with 10gR2 database please refer to:
Export/Import Process for Oracle E-Business Suite Release 12 using 10gR2 [ID 454616.1]
Using Transportable Database to migrate E-Business Suite R12 Using Oracle Database 10gR2 or 11g [ID 734763.1]
Migrating Oracle E-Business Suite R12 from Linux 32-bit to Linux 64-bit [ID 471566.1]
Thanks,
Hussein

How to make upgrade from application server and not from central instance?

Hello SAP Gurus!
I have SAP ECC release 6.0, and I´m gonna make upgrade to enhancement package 6.06, do you know if Can I make upgrade from application server, but not from central instance?
Thanks.

Hi Victor,
Upgrade process has to execute from the server where message server is running.
So I guess it is not possible to initiate the SAP upgrade from application server.
Regards,
Deepak Kori

Migrate Central instance from 32-bit to 64-bit

Similar Messages

Maybe you are looking for