cancel
Showing results for 
Search instead for 
Did you mean: 

MDM 5.5 SP5 and MaxDB

Erdal_Şimşek
Participant
0 Kudos

Hi,

how can I connect to MaxDB via Console when trying to unarchive or create a repository?

To my understanding MaxDB is supported in SP5.

DBMS Server: ecesimsek

Database name: callas

login: dbadmin

In the Console I give in name ecesimsek\callas (also tried callas or ecesimsek only),

in the login I give in DBADMIN and the password. When I try to connect the following error message appears: "Error initializing database engine".

Anyone whi can help?

Cheers,

Erdal

P.S. connecting to MSSQL Server Desktop Engine is no problem!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Erdal,

Does your MDM Server generates the "mds.ini" file?. (It supposes to be located in the same path that in you "mds" executable file)

Does your MDM Server generates any log?

Erdal_Şimşek
Participant
0 Kudos

Hi Mariano,

yes the MDM Server does generate a mds.ini file. The content of that file is posted below:

-


[MDM Server]

XCS Ini Version=1

Accelerator Dir=C:\Programme\SAP MDM 5.5\Server\Accelerators

Lexicon Dir=C:\Programme\SAP MDM 5.5\Server\Lexicons

Extra DBConnection Validation=True

Log SQL Errors=True

RELEASE\UseAssert=True

String Resource Dir=C:\Programme\SAP MDM 5.5\Server\LangStrings\

Stemmer Install Dir=C:\Programme\SAP MDM 5.5\Server

Log Dir=C:\PROGRA1\SAPMDM1.5\Server\Logs

MDS Scone=

Autostart=0

Log Protocol Transactions=False

MDS Ini Version=1

Report Dir=C:\PROGRA1\SAPMDM1.5\Server\Reports\

Archive Dir=C:\PROGRA1\SAPMDM1.5\Server\Archives\

Distribution Root Dir=C:\PROGRA1\SAPMDM1.5\Server\Distributions\

CPU Count=1

SLD Registration=False

Default Interface Language Code=eng

Default Interface Country Code=US

Log SQL Modifications=False

Maximum DBMS Bind Count=256

MaxDB\Dll=libSQLDBC76_C.DLL

Allow Console to Retrieve Files=True

-


I also do have a log from the MDM Server. Please see below:

<Server>5.5.40.83</Server><Build>Built on 2007-Feb-20</Build><Repository major="1" minor="264"/></Version>

<Trace ts="2007/04/18 08:55:31.586 GMT" tid="2672" entry-no="3">mds Configured for CPU Count of 1<LF/></Trace>

<Trace ts="2007/04/18 09:11:46.399 GMT" tid="5780" entry-no="8">Failed to load libSQLDBC76_C.DLL</Trace>

<Trace ts="2007/04/18 09:11:46.399 GMT" tid="5780" entry-no="9">MaxDB Initialization Failed -- likely missing libraries/dlls</Trace>

<Trace ts="2007/04/18 09:11:46.399 GMT" tid="5780" entry-no="10">MaxDB Init failed<LF/></Trace>

<Trace ts="2007/04/18 09:11:57.977 GMT" tid="5780" entry-no="11">Failed to load libSQLDBC76_C.DLL</Trace>

<Trace ts="2007/04/18 09:11:57.977 GMT" tid="5780" entry-no="12">MaxDB Initialization Failed -- likely missing libraries/dlls</Trace>

<Trace ts="2007/04/18 09:11:57.977 GMT" tid="5780" entry-no="13">MaxDB Init failed<LF/></Trace>

<Trace ts="2007/04/18 09:12:37.039 GMT" tid="5780" entry-no="14">Failed to load libSQLDBC76_C.DLL</Trace>

<Trace ts="2007/04/18 09:12:37.039 GMT" tid="5780" entry-no="15">MaxDB Initialization Failed -- likely missing libraries/dlls</Trace>

<Trace ts="2007/04/18 09:12:37.039 GMT" tid="5780" entry-no="16">MaxDB Init failed<LF/></Trace>

<Trace ts="2007/04/18 10:37:34.073 GMT" tid="5780" entry-no="17">Failed to load libSQLDBC76_C.DLL</Trace>

<Trace ts="2007/04/18 10:37:34.073 GMT" tid="5780" entry-no="18">MaxDB Initialization Failed -- likely missing libraries/dlls</Trace>

<Trace ts="2007/04/18 10:37:34.073 GMT" tid="5780" entry-no="19">MaxDB Init failed<LF/></Trace>

<Trace ts="2007/04/18 10:37:40.135 GMT" tid="5780" entry-no="20">Failed to load libSQLDBC76_C.DLL</Trace>

<Trace ts="2007/04/18 10:37:40.135 GMT" tid="5780" entry-no="21">MaxDB Initialization Failed -- likely missing libraries/dlls</Trace>

<Trace ts="2007/04/18 10:37:40.135 GMT" tid="5780" entry-no="22">MaxDB Init failed<LF/></Trace>

<Trace ts="2007/04/18 10:42:01.292 GMT" tid="5780" entry-no="24">Failed to load libSQLDBC76_C.DLL</Trace>

<Trace ts="2007/04/18 10:42:01.307 GMT" tid="5780" entry-no="25">MaxDB Initialization Failed -- likely missing libraries/dlls</Trace>

<Trace ts="2007/04/18 10:42:01.307 GMT" tid="5780" entry-no="26">MaxDB Init failed<LF/></Trace>

<Trace ts="2007/04/18 10:42:07.635 GMT" tid="5780" entry-no="27">Failed to load libSQLDBC76_C.DLL</Trace>

<Trace ts="2007/04/18 10:42:07.635 GMT" tid="5780" entry-no="28">MaxDB Initialization Failed -- likely missing libraries/dlls</Trace>

<Trace ts="2007/04/18 10:42:07.635 GMT" tid="5780" entry-no="29">MaxDB Init failed<LF/></Trace>

<Trace ts="2007/04/18 10:42:19.010 GMT" tid="5780" entry-no="30">Failed to load libSQLDBC76_C.DLL</Trace>

<Trace ts="2007/04/18 10:42:19.010 GMT" tid="5780" entry-no="31">MaxDB Initialization Failed -- likely missing libraries/dlls</Trace>

<Trace ts="2007/04/18 10:42:19.010 GMT" tid="5780" entry-no="32">MaxDB Init failed<LF/></Trace>

<Trace ts="2007/04/18 10:42:38.917 GMT" tid="5780" entry-no="33">Failed to load libSQLDBC76_C.DLL</Trace>

<Trace ts="2007/04/18 10:42:38.917 GMT" tid="5780" entry-no="34">MaxDB Initialization Failed -- likely missing libraries/dlls</Trace>

<Trace ts="2007/04/18 10:42:38.917 GMT" tid="5780" entry-no="35">MaxDB Init failed<LF/></Trace>

<Trace ts="2007/04/18 21:13:56.079 GMT" tid="5540" entry-no="36">System Shutdown</Trace>

<Trace ts="2007/04/18 21:13:56.719 GMT" tid="5540" entry-no="37">Service Ordered to Stop</Trace>

<Trace ts="2007/04/18 21:13:58.157 GMT" tid="5540" entry-no="38">Service Stopped</Trace>

</Open>

Hope this helps!

Thanks!!!

Cheers,

Erdal

Answers (3)

Answers (3)

Erdal_Şimşek
Participant
0 Kudos

Thanks!

Erdal

Former Member
0 Kudos

Also check if you are able to create a new repository.

Sometimes there may be issues when you port an archive created in a different database system.

If you are able to create a new repository, then there is no database intitialization problem. The problem may be with the portability.

Erdal_Şimşek
Participant
0 Kudos

Hi Adhappan,

I neither can connect nor create on the console. I got the same error message as usual.

Just another question: I installed "maxdb-all-win-32bit-i386-7_6_00_34" . Is this the

correct installation or do I have to look for something else ???

Thanks!!!

Cheers,

Erdal

Former Member
0 Kudos

Hi Erdal,

I have found this informations in the installguides MDM 5.5 SP05 :

Requirement Type Requirement

Hardware

Requirements

See MDM 5.5 Sizing Guide on service.sap.com/installMDM.

Operating Systems See Product Availability Matrix (PAM) on SAP Service Marketplace under

service.sap.com/pam &#56256;&#56431; SAP NETWEAVER &#56256;&#56431; SAP MDM

Minimum Database

Versions

&#56256;&#56440; <b>MaxDB 7.7.01</b>

&#56256;&#56440; IBM DB2: 8.2

&#56256;&#56440; IBM DB2 for z/OS: 8 in New Function Mode

&#56256;&#56440; IBM DB2 for i5/OS: V5R4

&#56256;&#56440; Oracle 9: 9.2.0.7

&#56256;&#56440; Oracle 10: 10.2

&#56256;&#56440; MS SQL: 8 SP3

MaxDB 7.7 is not officially released so I think this is a mistake.

Former Member
0 Kudos

Try the following:

Is the database running?

Are you able to log in direclty to database server via the database client with the user id and password?

In the console make sure you give the correct DBMS name. Case Sensitivity may be a problem.

Are you using the default database or have you created any instance on the database. If you have created any instance, then you have to include the instance name as well to connect to. You can find out by trying to log in to the database directly.

Erdal_Şimşek
Participant
0 Kudos

Hi Adhappan,

yes, I am able to log on the DBM Command Line Interface. The Database seems running.

I type in servername, database and user/password and can connect directly. I am using the default database, i.e. while installing it I just gave it a name ('CALLAS') and I use this name.

I also tried vrious ways in terms of case sensitivity but still couldn't connect.

Thanks!!!

Cheers,

Erdal