Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Unicode Export - NW_getDBInfo Error

Former Member
0 Kudos

Hi all,

We are starting our export from ECC 6.0 / HPUX 11.31/ Oracle 10.2.0.2 - Non Unicode system with the SR3 - Installation master DVD.

We have set the below env and started the sapinst as a root user. After giving the input parameter for the profile directory /sapmnt/DV2/profile, we get the below error.

Env Settings:

export JAVA_HOME=/opt/java1.4

export SAPINST_JRE_HOME=/opt/java1.4

export PATH=/opt/java1.4/bin:$PATH

export I18N_NAMETAB_TIMESTAMPS=IGNORE

export SHLIB_PATH=/sapmnt/DV2/exe

export DISPLAY=165.99.99.111:0.0

export dbms_type=ORA

Error Log:

ERROR 2008-12-03 10:15:02.940 [iaxxinscbk.cpp:260]

CJS-00030 Assertion failed: in component: NW_getDBInfo

step:fillContext

at this point the dbtype has to be != ind

ERROR 2008-12-03 10:15:02.950

CJSlibModule::writeError_impl()

MUT-03025 Caught ESAPinstException in Modulecall: in component: NW_getDBInfo

step:fillContext

at this point the dbtype has to be != ind.

ERROR 2008-12-03 10:15:03.100 [sixxcstepexecute.cpp:951]

FCO-00011 The step fillContext with step key |NW_Prepare_Export|ind|ind|ind|ind|0|0|NW_GetSidFromProfiles|ind|ind|ind|ind|1|0|NW_getDBInfo|ind|ind|ind|ind|4|0|fillContext was executed with status ERROR .

Export is not able to find the dbtype, though our DEFAULT.PFL file has the dbms/type = ora parameter set.

We tried to export using the sidadm also, but still face the same error

Can anyone help

Regards

Senthil

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

To solve the problem, change the following lines in the control.xml file

Old: (tORA_DbHome.name WHERE 1 = 1),

target (tGlobalDbParameters.dbHomeName ...

New: (tORA_DbHome.path WHERE 1 = 1),

target (tGlobalDbParameters.dbHome ...

Note that these lines should appear twice in control.xml.

Regards,

Sachin Rane.

7 REPLIES 7

former_member299080
Participant
0 Kudos

Hi,

This error:

MUT-03025 Caught ESAPinstException in Modulecall: in component: NW_getDBInfo

step:fillContext

at this point the dbtype has to be != ind.

means that the system is not picking up the correct DB type.

To correct this, please set the environment variable "DBMS_TYPE = ora"

and the restart sapinst. Try to set the variable in capital letters, it should work this time.

Marco

Former Member
0 Kudos

I tried setting the parameter DBMS_TYPE=ora as root user, but again it fails with the same error

ERROR 2008-12-03 11:10:44.950 [iaxxinscbk.cpp:260]

CJS-00030 Assertion failed: in component: NW_getDBInfo

step:fillContext

at this point the dbtype has to be != ind

Regards

Senthil

former_member299080
Participant
0 Kudos

Hi,

Check whether env variable ORACLE_HOME is properly set for users ora<sid> and <sid>adm. Also check file .cshrc.csh and make sure it is consistent. Sometimes the env variables are retrieved from this file.

Marco

Former Member
0 Kudos

Did you resolv this error.

I am facing the same issue while performing an export.

Thanks

Naresh P.

Former Member
0 Kudos

I am facing the same issue. Here's my ORA env variables:

ORACLE_BASE=/oracle

ORACLE_STAGE=/oracle/stage/102_64

ORACLE_SID=SMG

DBMS_TYPE=ORA

ORA_NLS10=/oracle/SMG/102_64/nls/data

DBS_ORA_TNSNAME=SMG

ORACLE_HOME=/oracle/SMG/102_64

Has anyone solved this? I cannot find an OSS Note on the topic.

Thanks,

Jeff Martens

Former Member
0 Kudos

Hi,

To solve the problem, change the following lines in the control.xml file

Old: (tORA_DbHome.name WHERE 1 = 1),

target (tGlobalDbParameters.dbHomeName ...

New: (tORA_DbHome.path WHERE 1 = 1),

target (tGlobalDbParameters.dbHome ...

Note that these lines should appear twice in control.xml.

Regards,

Sachin Rane.

0 Kudos

I am facing exactly the same error, though this post is of 2009 and we are in 2012 but this kind of problem keeps coming in SAP Install.

My System is a MCOD ( two separate SID on Same DB). We are trying to export ABAP. We were able to export JAVA successfully but for ABAP export this error is coming.

u201D Assertion failed: in component: NW_getDBInfou201D

We tried all the option available in the internet cloud and also followed Note-112-872.

The only option we didu2019t try is editing the control file mentioned in this post.

We are on AIX/ORACLE,

We are using the latest sapinst NW70EHP1

Our Environment Variable related to DB are.

Root:

ORA_VER=112_64

DIR_CLIENT_ORAHOME=/oracle/BIS/112_64

ORACLE_BASE=/oracle

ORACLE_SID=BIS

ORACLE_HOME=/oracle/BIS/112_64

dbms_type=ORA

DIR_ORAHOME=/oracle/BIS/112_64

SIDADM:

ORA_VER=112_64

DIR_CLIENT_ORAHOME=/oracle/BIS/112_64

ORACLE_BASE=/oracle

ORACLE_SID=BIS

ORACLE_HOME=/oracle/BIS/112_64

dbms_type=ORA

DIR_ORAHOME=/oracle/BIS/112_64

ORASID:

ORA_VER=112_64

ORACLE_BASE=/oracle

ORACLE_SID=BIS

DIR_SERVER_ORAHOME=/oracle/BIS/112_64

ORACLE_HOME=/oracle/BIS/112_64

dbms_type=ORA

Important: dbms_type was in lower case, per SAP reply we changed to Uppercase , still no luck.

Per Sachin Rane recommendation to edit the control file : we could not find the exact text in control.xml. The text available in the control.xml is

1

client.mapContextParameterWithDefault("pdDbHome","tORA_DbHomes","dbHome","WHERE 1=1","'dbHome'");

2

// client.mapContextParameterWithDefault("pdDbHome","tORA_DbHomes","dbHome","WHERE 1=1","'dbHome'");

3

// client.mapTableElementWithDefault("pdDbHome", "ORAMAIN_PAR","dbHome",where,"","tORA_DbHomes","dbHome","WHERE 1=1");

4

// client.mapContextParameterWithDefault("pdDbHome","tORA_DbHomes","dbHome","WHERE 1=1","'dbHome'");

5

// client.mapTableElementWithDefault("pdDbHome","ORAMAIN_PAR","dbHome",where,"","tORA_DbHomes","dbHome","WHERE 1=1");

If any one face this issue then could you share what changes were made to resolve this error.

Edited by: Brajendra Tewary on Jan 5, 2012 12:03 AM