cancel
Showing results for 
Search instead for 
Did you mean: 

Database Migration from Informix to Oracle

Former Member
0 Kudos

Hello,

We are on testing stage for migration to ORACLE 9.2.0.8 from INFORMIX 7.31 FD2X9...

We have installed SAP R/3 4.6b with Oracle 9.2.0.8 on Solaris 5.9 [64bit] and now on the import stage...Export is also done from the informix server .. [db:approx 400 gb]

Kindly suggest/provide some document/note for Database Import [Informix - Oracle]..

Thanks,

RaHuL...

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

> We are on testing stage for migration to ORACLE 9.2.0.8 from INFORMIX 7.31 FD2X9...

>

> We have installed SAP R/3 4.6b with Oracle 9.2.0.8 on Solaris 5.9 [64bit] and now on the import stage...Export is also done from the informix server .. [db:approx 400 gb]

Delete that installation.

A migration is done like an installation - you provide the system with the export of the source database instead of the export CDs/DVDs that come for a new installation.

You will use the migration template instead of DATABASE.R3S.

For heterogeneous migration you need to have a certified migration consultant on-site (check http://service.sap.com/osdbmigration).

Markus

Answers (4)

Answers (4)

Former Member
0 Kudos

We are doing the exact same thing - what documents are you following? the Heterogeneous doc? I have a migration key, but need the kit. I will be starting this this week - if you have a doc let me know if you are willing to share.

Former Member
0 Kudos

Hi,

Yes we had used R3HET doc.. We are already done with the Migration...

Used the same doc as it was in the Migration Kit set...

Thanks

RaHuL...

Former Member
0 Kudos

Hi,

We have got stuck on this error: Kindly help..

INFO 2008-04-13 06:51:00 DBR3LOADEXEC_IND_IND R3loadPrepare:0

Total number of processes: 23

20 process(es) finished successfully: 0 1 2 5 6 7 8 9 10 11 12 13

14 15 16 18 19 20 21 22

3 process(es) finished with errors: 3 4 17

0 process(es) still running:

ERROR 2008-04-13 06:51:00 DBR3LOADEXEC_IND_IND R3loadPrepare:0

Processes started: 23

Ended with error: 3

load tool ended with error.

See above SAP*.log errors.

ERROR 2008-04-13 06:51:00 DBR3LOADEXEC_IND_IND R3loadFork:0

RC code form SyChildFuncWait = 255 .

ERROR 2008-04-13 06:51:00 DBR3LOADEXEC_IND_IND R3loadFork:0

See logfiles SAPlog and EXlog for further information.

ERROR 2008-04-13 06:51:00 DBR3LOADEXEC_IND_IND InternalInstallationDo:0

R3loadFork erred

ERROR 2008-04-13 06:51:00 DBR3LOADEXEC_IND_IND InstallationDo:0

Phase failed.

ERROR 2008-04-13 06:51:00 InstController Action:0

Step DBR3LOADEXEC_IND_IND could not be performed.

ERROR 2008-04-13 06:51:01 Main

Installation failed.

ERROR 2008-04-13 06:51:01 Main

Installation aborted.

-


Please also check this.. This is the SAPAPPL1.log file...

R3load -i SAPAPPL1.cmd -p SAPAPPL1.log -r -k

start of syntax check ###

end of syntax check ###

DbSl Trace: OCI-call 'olog' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'olog' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'olog' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'olog' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

#(IMP) ERROR: couldn't connect to DB

rc = 256

error message returned by DbSl:

DbSl Trace: OCI-call 'olog' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'olog' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

#STOP: 20080413003424

DbSl Trace: OCI-call 'olog' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'olog' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

#(IMP) ERROR: DbSlRollback failed

DbSlRollback: rc = 1

(SQL error 1034)

#START OF LOG: 20080413004158

R3load version @(#) $Id: //bas/46D/src/ins/R3load/R3load.c#40 $ SAP

Compiled Jul 25 2006 02:52:37

R3load -i SAPAPPL1.cmd -p SAPAPPL1.log -r -k 1WUfdeM50TL01eqtdAA91a94

start of syntax check ###

end of syntax check ###

DbSl Trace: OCI-call 'olog' failed: rc = 1017

DbSl Trace: CONNECT failed with sql error '1017'

trying to restart import ###

R3load> RETRY: nothing left to do

#START: 20080413004203

#STOP: 20080413004203

R3load> Import terminated successfully

#END OF LOG: 20080413004203

#START OF LOG: 20080413065056

R3load version @(#) $Id: //bas/46D/src/ins/R3load/R3load.c#40 $ SAP

Compiled Jul 25 2006 02:52:37

R3load -i SAPAPPL1.cmd -p SAPAPPL1.log -r -k 1WUfdeM50TL01eqtdAA91a94

start of syntax check ###

end of syntax check ###

DbSl Trace: OCI-call 'olog' failed: rc = 1017

DbSl Trace: CONNECT failed with sql error '1017'

trying to restart import ###

R3load> RETRY: nothing left to do

#START: 20080413065100

#STOP: 20080413065100

R3load> Import terminated successfully

#END OF LOG: 20080413065100

Thanks,

RaHuL...

markus_doehr2
Active Contributor
0 Kudos

ORA-01034 means, that the database is not available - it crashed apparently.

Check $ORACLE_HOME/saptrace/background/alert<SID>.log for possible errors.

Did you install the latest patches for 9.2.0.8?

Markus

Former Member
0 Kudos

Hello,

Thanks.

We have CI & DB on the same instance.. so we have to use CEDBMIGR.R3S command file...

But we dont find this in the osdbmigration kit cd...

Kindly suggest...

Thanks,

RaHuL...

Former Member
0 Kudos

Hello,

Thanks a lot Markus..

What does " Delete that Installation" mean?

Is it that sap 4.6 B what we have installed shouldn't have been done..

Only the export data form the informix server is to be imported to the Oracle Server..

Then what about the R/3 system... We have installed CI/DB/Oracle 9.2.0.8 on the 'Import system'..

Have we done anything wrong.. We plan to import the data in this system now..

Kindly please explain..

Thanks in advance..

RaHuL...

markus_doehr2
Active Contributor
0 Kudos

You can´t load an export into an already installed instance. The migration process is "non standard" (so to say), you have to start the migration of a system with a different template (MIGRATE.R3S instead of CENTRAL.R3S). This will install the CI and then load the data from your export. You will need a migration key for that action (http://service.sap.com/migrationkey).

Markus