heterogeneous system copy is wrong (DBDDLOADDCHECK_XT_IND_ORA)

[former_member290911]

Hi SAP Experts.

I am migrating a Systema SAP 4.0B kernel 4.0_EXT with plataform AIX 5.3 and database software Oracle 9.2.0.7.

But when I execute the command ./R3SETUP -f CENTRAL.R3S, the process is canceled in the phase DBDDLOADDCHECK_XT_IND_ORA, with the folllowing error in DBMIG.log:

ERROR 2010-11-24 10:24:41 DBDDLOADDCHECK_XT_IND_ORA

SyOraCheckDdloadd:100

ORA-00942: table or view does not exist

ERROR 2010-11-24 10:24:41 DBDDLOADDCHECK_XT_IND_ORA

SyOraCheckDdloadd:400

DbSlExeRead failed. rc = 107.stmt = SELECT OBJECTNAME FROM

DDLOADD WHERE OBJECTTYPE = 'TABLE' MINUS SELECT SEGMENT_NAME FROM

SYS.DBA_SEGMENTS WHERE SEGMENT_TYPE = 'TABLE' AND OWNER =

ERROR 2010-11-24 10:24:41 DBDDLOADDCHECK_XT_IND_ORA

InternalInstallationDo:0

See logfile dev_dbsl for further information.

ERROR 2010-11-24 10:24:41 DBDDLOADDCHECK_XT_IND_ORA InstallationDo:0

Phase failed.

ERROR 2010-11-24 10:24:41 InstController Action:0

Step DBDDLOADDCHECK_XT_IND_ORA could not be performed.

Also, I see el following error in the file dev_dbsl:

DbSl Trace: dbsloci.c 6694 Got ORACLE_HOME=/oracle/DEV/920_64 from environment

DbSl Trace: dboci.c 2333 -->oci_initialize

DbSl Trace: dbsloci.c 6694 Got ORACLE_SID=DEV from environment

DbSl Trace: dbsloci.c 7198 Got NLS_LANG=AMERICAN_AMERICA.WE8DEC from environment

DbSl Trace: dbsloci.c 5509 Logon as OPS$-user to get SAPR3's password

DbSl Trace: dbsloci.c 6991 Connecting as /@DEV on connection 0 ...

DbSl Trace: dboci.c 2416 -->oci_logon(con_hdl=0, user='', dbname='DEV')

DbSl Trace: dboci.c 2435 OCI-call 'olog' failed: rc = 1017

DbSl Trace: dbsloci.c 7003 CONNECT failed with sql error '1017'

DbSl Trace: dbsloci.c 5555 Try to connect with default password

DbSl Trace: dbsloci.c 6991 Connecting as SAPR3/oci_logoff(con_hdl=0)

DbSl Trace: dbsloci.c 6935 Now I'm disconnected from ORACLE

DbSl Trace: dboci.c 2435 OCI-call 'olog' failed: rc = 1017

DbSl Trace: dbsloci.c 7003 CONNECT failed with sql error '1017'

DbSl Trace: dboci.c 2435 OCI-call 'olog' failed: rc = 1017

DbSl Trace: dbsloci.c 7003 CONNECT failed with sql error '1017'

DbSl Trace: dboci.c 2435 OCI-call 'olog' failed: rc = 1017

DbSl Trace: dbsloci.c 7003 CONNECT failed with sql error '1017'

DbSl Trace: dboci.c 2435 OCI-call 'olog' failed: rc = 1017

DbSl Trace: dbsloci.c 7003 CONNECT failed with sql error '1017'

DbSl Trace: dboci.c 2435 OCI-call 'olog' failed: rc = 1017

DbSl Trace: dbsloci.c 7003 CONNECT failed with sql error '1017'

DbSl Trace: dboci.c 2435 OCI-call 'olog' failed: rc = 1017

DbSl Trace: dbsloci.c 7003 CONNECT failed with sql error '1017'

DbSl Trace: dboci.c 2435 OCI-call 'olog' failed: rc = 1017

DbSl Trace: dbsloci.c 7003 CONNECT failed with sql error '1017'

DbSl Trace: dboci.c 2435 OCI-call 'olog' failed: rc = 1017

DbSl Trace: dbsloci.c 7003 CONNECT failed with sql error '1017'

DbSl Trace: dboci.c 2435 OCI-call 'olog' failed: rc = 1017

DbSl Trace: dbsloci.c 7003 CONNECT failed with sql error '1017'

DbSl Trace: dboci.c 2435 OCI-call 'olog' failed: rc = 1017

DbSl Trace: dbsloci.c 7003 CONNECT failed with sql error '1017'

DbSl Trace: dboci.c 2435 OCI-call 'olog' failed: rc = 1017

When I execute the following commads with the user devadm, get a correct connection to database DEV:

sqlplus /

sqlplus /@DEV

sqlplus sapr3/sap

I applied the notes: 400241, 562863 and 361641 but I get the same error.

How can I solve the problem?.

Best regards.

Luis Gómez

[markus_doehr2]

> I am migrating a Systema SAP 4.0B kernel 4.0_EXT with plataform AIX 5.3 and database software Oracle 9.2.0.7.

Gosh, that is really old

Is the source systems schema name "SAPR3" or is it "SAPDEV"?

Markus

[former_member290911]

The source systems schema name is "SAPR3" .

Best regards.

Luis Gómez

[Former Member]

hey rojas,

cann you please share the details how did you resolve this issue??? i am having the same problem

thanks,

Siva Kumar

[Former Member]

Is R3trans -d working fine?

Kind regards,

Mark

[former_member290911]

Hi.

The R3trans -d is working fine. I get code 000.

Best regards.