on 11-28-2006 10:38 AM
Hello all,
We currently run SolMan v3.1 on aged 32bit hardware and we plan to upgrade this to SolMan v4 on a new 64bit infrastructure. As part of this task, we would also like to move from Windows 2000 to Windows 2003 x64 and from Oracle 9.2 to Oracle 10.2
The current situation is that the new server is built to Windows 2003 x64 level only. Nothing else is installed on the new server at this time. My plan was to install Oracle 9.2 and SolMan 3.1 and then take a system copy of the existing database and then upgrade it to SolMan v4 and Oracle 10.2 (leaving the old system as-is for recovery reasons, should we run into problems).
Has anyone any experience of doing this in a Windows and Oracle environment who could help me with getting this right?
Many thanks,
Arwel Owen.
I have done similar upgrades in the past with Oracle. here's the plan:
install win2003 64-bit
install Oracle 9 64-bit
install SAP 64-bit
backup/restore from old machine to new machine
check SAP parameters, Oracle parameters, /usr/sap/trans, etc...
that's about it.
Good luck.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Eric,
Thanks for your response.
I took a look in https://service.sap.com/swcenter-3pmain and found that the only NT-based Oracle 9 64-bit patch is for 9.2.0.8 on IA-64. We're running on an Opteron-based (i.e. x86_64) platform so it's unlikely that this'll work for us. The only available x86_64 based Oracle patch is for Oracle 10.
Does it appear that our only route is to install a base 32bit Oracle 9 and upgrade it to 64bit Oracle 10 after copying the database?
Cheers,
Arwel.
Hello Arwen
It is the right way to upgrade the Oracle from 32 to 64 bit after installation.
In the sap service marketplace you will find the 64 bit software and installation guide for Oracle.
https://websmp201.sap-ag.de/swdc
In the installation guide the steps are branched for an upgrade from 32 to 64 bit oracle upgrade and also installation of 64 bit oracle.
Hope that helps.
for <b>Migration X86_64 Windows</b>.
you will find <a href="http://service.sap.com/sap/support/notes/960769">Windows: Migration von 32-Bit nach 64-Bit (x86_64)</a>.
The right and only answer is:
homogenious system copy!!!!!!!!!!!
regards
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
As this is a fairly low-priority upgrade, we decided to try to experiment a little to try to avoid the ORacle 9 to 10 upgrade. We decided upon the following approach:
1) Install Windows 2003 x64 (on new server)
2) Install Oracle 10.2 x64
3) Install SolMan v3.1
4) Export existing SolMan v3.1 database (from existing server)
5) Import existing SolMan v3.1 database (onto new server)
6) Upgrade to SolMan v4
We have installed Oracle 10.2 and applied 10.2.0.2 Patchset 1 and all seemed okay. We are now installing SolMan v3.1, but SAPinst crashes out after specifying the SAP system directory and transport host and just before starting the database-dependent cations. The error message is:
<b>ERROR: MDB-06168. Oracle is not installed on this host. Install Oracle before continuing.</b>
Oracle definitely IS installed, but it appears that SAPInst for SolMan v3.1 may be too old to recognise Oracle 10.2.
I thought I'd ask for advice before I go and butcher the KEYDB.XML and ORADBPAR.XML files. (It's only a test install!)
Thanks,
Arwel.
Hallo Arwel,
I executed a similar scenario.
Win2000 32-bit
Oracle 9.2 32-bit
R/3 4.6C
Migrated to
Win2003 x86_64
Oracle 10.2 64-bit
R/3 4.6C
using Oss note 932722-Upgrade to Oracle 10.2 during a db copy.
You could do :
Win2000 32-bit
Oracle 9.2 32-bit
Solman 3.1 Upgrade to Solman 4.0
and after
Win2003 x86_64
Oracle 10.2 64-bit
Solman 4.0 new
and after follow Oss note 932722
Mario
how the backup is implemented.
as long as there are no native interfaces (DLLs) they provide for the Oracle Kernel, you normally can also use the 32 Bit Windows Backup Tool.
There is no real need for a 64 Bit Backup Tool as long as the 32 Bit one is doing the job. Backup Tools typically did not need the big amount of memory (address space) which would request 64 Bit address space.
Peter
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.