-2 ERR_USRFAIL: User authorization failed

[florin_radulea]

Hello guys,

First to mention my system:

OS: Windows 2003 server

DB: MaxDB 7_7_06_17

I have one problem to connect through Database Manager to one DB instance that just now I have installed.

What I want to do is to install one MDM server.

The bellow are the steps that were already performed:

-installed Java server with sapinst (this created its database ZJD)

-after this Java server was finished installed I started to create one DB MDM instance using SDBSETUP.exe

-I was able to create this MDM instance successful

And the problem is here: This MDM database instance that was created with defaults users DBA and DBM. When the creation of this MDM was finished I tried to connect with both Database Manager and DBMCLI to MDM instance using these users but I am not able to connect. I get the "-2 ERR_USRFAIL: User authorization failed" error. Can you tell me which is the reason?

I am sure that I typed the right user and password. I tried to uninstall all and installed again inclusive OS and the same error. I mention that to instance ZJD I am able to connect.

I tried with default users for Maxdb (DBA with pass: SECRET and DBA and DBM with pass: SECRET and DBM) but this doesn't work.

Can you help me to solve this problem?

Best regards,

Florin Radulea

[Former Member · Accepted solution]

Are you able to connect to the database using the xuser mechanism?

Kind regards,

Mark Dijsselbloem

[florin_radulea · Accepted solution]

Hi Mark,

Ca you tell me exactly how can I connect using Xuser mecanism?

I am not sure if I can connect because the only users that are in database instance (MDM) are DBA, DBM and SAPMDMDB and their password don't work.

Thank you,

Best regards,

Florin

[Former Member · Accepted solution]

Hi Florin,

When you logon with the admin user, you can run the xuser list command. This command will show you the contents of the xuser file. It is basically a way of encrypting your password and store them, so you can login to the database without using a password.

More information regarding xuser can be found at: http://help.sap.com/saphelp_nw70ehp1/helpdata/en/28/873e4045796913e10000000a1550b0/frameset.htm

Normally each user has an entry in the xuser file. For logging on, you need the key entry.

So eg.

Key :c_J2EE

Username :CONTROL

UsernameUCS2:C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .

Password :?????????

PasswordUCS2:?????????

Dbname :IWQ

Nodename :nlscli67

Sqlmode :SAPR3

Cachelimit :-1

Timeout

Isolation

Charset :<unspecified>

In this case the key for user control is c_J2EE

From the command line you can try to connect to the database using: dbmcli -d <DB SID> -U c_J2EE

Hope this helps for you!

Kind regards,

Mark Dijsselbloem

[florin_radulea · Accepted solution]

Hi Mark,

Thank you for your response.

I ran xuser list as administrator user but I not able to see neither user. The list is empty. Can you tell me if the MDM users (DBA and DBM) are created by MDM sapinst? It is strange because when I created MDM database instance with SDBSETUP.exe this ask me to enter the password for DBA and DBM users. It is normal that these users to not be created? Or I not used right user to run this command.

Can you explain me this?

Thank you,

Best regards,

Florin

[Former Member · Accepted solution]

Hi Florin,

The users DBA and DBM are created by default by the MaxDB installation (option SAP MDM), so not by sapinst.

First you create the MDM system using sapinst, after that you have to install the database using sdbsetup.

The user SAPMDMDB is being created with the password SAP.

Since this is a fresh installation, you could also deinstall your Maxdb installation and reinstall it.

Kind regards,

Mark Dijsselbloem

[florin_radulea · Accepted solution]

Hi Mark,

I uninstalled MDM instance, after that I created MDM server with sapinst, and to the end I created MDM DB instance with SDBSETUP.exe, but again the same problem.:(

I ran command xuser list as user MDMadm and there is nothing in output list?

Can you please tell me what I have missed....?

May be the MDM database was not uninstalled correctly? I say this because when I uninstalled the MDM database I was asked to enter user and pass, I entered DBA and its pass, but I get " User authorization failed", but the next pop up I was able to uninstall database without authorization....May be this the issue?

Please tell me how can I proceed...

Thank you,

Best Regards,

Florin

[Former Member · Accepted solution]

Hi Florin,

You don't have to uninstall the MDM installation, only the database.

Forget about xuser for now, just check if the passwords provided during the installation are sufficient.

During the installation of the MDM database using sdbsetup, you have to enter the database name (default MDM) and the passwords for the users dbm and dba, right? After that you have to enter some parameters regarding the database file log settings etc.

Are you connecting in the following way: dbmcli -d MDM -u dbm,<password> ?

You can also try just to create an additional MaxDB installation (use another system ID), so you don't have to delete the current.

Can you also check if you can connect with user control or superdba with the password you provided?

Kind regards,

Mark

[florin_radulea · Accepted solution]

Hi Mark,

Thank you again for you response.

I tried to connect with dbmcli -d MDM -u dbm,<password> but I get the same error as in Database manager:

C:\Documents and Settings\zcdadm.VITEX>dbmcli -d MDM -u dbm,password

Error! Connection failed to node (local) for database MDM:

-24950,ERR_USRFAIL: User authorization failed

Yes, this was the way that I did, I entered the pass for DBM and DBA when I created MDM database instance with SDBSETUP.exe.

As you said, I tried to create another Database instance (MDM1), the instance was created but the same problem...I don't have the authorization to connect to this new database already created (MDM1).

I tried to use all users to connect but with all I get this authorization issue.

What is my thinking is that this users are not created in the database, but I don't know why.

Is normal that when I run xuser list when I am logged as MDMadm to get empty list?

Thank you,

Best regards,

Florin

[Former Member · Accepted solution]

Hi Florin,

I guess the xuser file will only be created during regular SAP installations.. MDM is in that sentence not similar to a regular SAP installation.

Kind regards,

Mark

[Former Member · Accepted solution]

One more thing; could it be that your x_server isn't running? However I would expect another error message in this case..

Check the following link: http://help.sap.com/saphelp_nw70ehp1/helpdata/en/1e/6e424089ff2571e10000000a155106/frameset.htm

Kind regards,

Mark

[former_member229109 · Accepted solution]

Hello Florin Radulea,

-> The Xuser data are the OS user dependent. Please run the u2018xuser listu2019 command as <applSID>adm user.

-> As I understood the MDM database instance was installed/created using SDBSETUP,

And itu2019s not connected to the application system. Correct?

If Itu2019s correct, then you have not the xuser entries on the application server.

-> Please post the steps/selection you did when MDM database instance was installed/created using SDBSETUP. What passwords you typed?

Thank you and best regards, Natalia Khlopina

[florin_radulea · Accepted solution]

Hello Natalia,

I want to list in chronological order all the steps that I performed:

1. Installed Java Server using BS_2005_SR3_SAP_Installation_Master

a)This created DB instance ZJD and connections to this database works fine

2. I created MDM instance with SDBSETUP, this ask me to enter passwords for DBA and DBM users.

After that I tried to connect to database with both Database Manager and DMCLI using DBA,DBM users and I got authorizations failed

3. I installed the MDM server using MDM_IM_WINDOWS_X86_64 installation master (this has SID ZCD)

a) After installation was finished with success i tried as Mark and advised me to run xuser list command to see the list of all users. This command was ran as ZCDadm. (normally this command should list the list of users for MDM instance, right?)

b) When I ran xuser list as user ZJDADM here I am able to see the list of database java's users

4.When I see that I am not able to see the users for MDM database and I am not able to connect MDM database I uninstalled both MDM database instance (with SDBSETUP) and MDM server (ZCD) using installation master MDM_IM_WINDOWS_X86_64.

5. I installed again as Mark advised me to create first MDM server using installation master MDM_IM_WINDOWS_X86_64 and after that to create database instance for MDM using SDBSETUP

6.After all was finished successful installed I get the same problem with users:(, and when I try to run xuser list as ZCDADM user I am not able to see nothing, but with user ZJDADM I am able to see the list with ZJD database users.

I want to ask you, may be because I installed first in in wrong order (first I created MDM database with SDBSETUP and after that I run MDM_IM_WINDOWS_X86_64 installation master) instead first MDM_IM_WINDOWS_X86_64 and after that SDBSETUP, and after that I deleted all and installed again in order that Mark advised me? May be when I uninstalled MDM database possible to not be uninstalled in right order....?

Can you advice me how to proceed?

Thank you very much for your time,

Best regards,

Florin

[florin_radulea · Accepted solution]

Hi Mark,

Thank you for your response,

I checked my x_server on my host and is already started.

Any way I stooped with command x_server stop and after that I started with command x_server start, but this not solved my problem.

Thank you,

Best regards,

Florin Radulea

[Former Member · Accepted solution]

Hi Florin,

Are you following this guide: service.sap.com/~sapidb/011000358700001668482008E

Can you check to logon with control or superdba?

Kind regards,

Mark

[Former Member · Accepted solution]

Can you also check the users and passwords from this link: http://help.sap.com/saphelp_nw70ehp1/helpdata/en/ca/69d8b637f1bb4d913c877c1ab33b73/frameset.htm

[florin_radulea · Accepted solution]

Hi Mark,

Thank you for your response,

Yes, this was the guide that I have followed and I tried to connect with that defaults passwords, but these didn't work. Indeed those default password were for MaxDb versions up to 7.5 and my MaxDB versions is 7.7.

I think I will raise one message to SAP support to get their help. May be something easy that I don't see, or I overlook some step.

Thank you for your time spent to respond me.

Best regards,

Florin Radulea

[former_member229109 · Accepted solution]

Hello Florin Radulea,

-> The Xuser data are the OS user dependent as I wrote you already. Please run the u2018xuser listu2019 command as zcdadm user.

-> The running xserver needed to connect to the database from remote client.

And you donu2019t need the xserver running when you run locally u201Cdbmcli -d MDM -u dbm,passwordu201D

u201CERR_USRFAIL: User authorization failedu201D error occurred if you tried to connect to the database with wrong DBM user or wrong password of the DBM user.

Please post the output of the command :

Xinstinfo MDM

Check in MDM file in e:/sapdb/data/config you have next to CONTROLUSERID 3CONTROL or DBM.

-> What passwords did you type when you run the installation of MDM database?

-> Itu2019s good Idea to create the SAP ticket on this issue. Did you already create it?

Thank you and best regards, Natalia Khlopina

[florin_radulea · Accepted solution]

Hello Natalia,

Thank you again for your response.

--> I ran xuser list as zcdadm and this doesn't return anything.

--> The output for the next command is as follow:

Xinstinfo MDM

IndepData : E:\sapdb\data

IndepPrograms : E:\sapdb\programs

InstallationPath : E:\sapdb\MDM\db

Kernelversion : KERNEL 7.7.06 BUILD 017-123-221-951

Rundirectory : E:\sapdb\data\wrk\MDM

-->The password that I typed was one password that contain 9 characters, and that password was exactly the same for all MDM installation

--> Yes, already I created one SAP ticket on this issue, and now I am waiting for response from they.

Thank you for your time,

Best regards,

Florin Radulea

[florin_radulea · Accepted solution]

Hello all,

First thank you for you Natalia and Mark that help me with my problem.

I solved my problem. The solution was very easy, (but I think there was one MAXDB issue, ).

Was a problem with the length of password. The password entered by me had 9 characters, but this was truncated automatically to 8 characters. I can't imagine why. So i entered the password being "control9" (9 characters)and this automatically was truncated to "control" (8 characters). I didn't imagine that this can happen when I created MDM instance. So every time I entered the password that I entered during the installation. I was sure that the password is the right one and this was. One of my colleague, (is more experienced than me) tried to enter the password that I told to him, but only first 8 characters, and.....unbelievable the connection works:).

So may be this information will help another people that will have this problem.

Thank you again.

Best regards,

Florin Radulea

[former_member229109 · Accepted solution]

Hello Florin Radulea,

1) I was able to reproduce the issue on the local server.

When I created MDM database instance using the SDBSETUP and database software package version 7.7.06 BUILD 017. I selected password being "control09" (9 characters) and only 8 characters were accepted => the DBM user was created with password "control0" (8 characters).

2) What is your SAP ticket number?

Thank you and best regards, Natalia Khlopina

[florin_radulea · Accepted solution]

Hello Natalia,

Thank you for your response. Yes indeed this was the problem.

My SAP Message Number 317382/2010.

Thank you,

Best regards,

Florin Radulea

[Former Member · Accepted solution]

Hi Florin Radulea,

Could you please provide the details which has given to you by SAP Message.

I stucked in same problem.

Thanks & Regards,

Richa

[symon_braunbaer · Accepted solution]

I am trying to install NetWeaver 2004 on MaxDB and Linux and I'm getting an assertion error,

then the error described here when I try to start the DB. My password has only 8 characters.

Here is my thread, please help me!!

http://scn.sap.com/message/14124926#14124926

[Former Member]

Hello guys,

I'm having the same issue while installing an IDES SAP system based on MaxDB in Linux 11R2.

The password of SUPERDBA and CONTROL is 8 character long.

Here's the current database configuration, database is in ADMIN mode:

/sapdb/programs/bin/dbmcli on xxx : DHS>inst_enum

OK

7.7.06.10    /sapdb/DHS/db

/sapdb/programs/bin/dbmcli on xxx : DHS>db_enum

OK

DHS     /sapdb/DHS/db                           7.7.06.10       fast    running

DHS     /sapdb/DHS/db                           7.7.06.10       quick   offline

DHS     /sapdb/DHS/db                           7.7.06.10       slow    offline

DHS     /sapdb/DHS/db                           7.7.06.10       test    offline

/sapdb/programs/bin # ./sdbregview -l

DB Analyzer         /sapdb/programs    7.7.06.10     64 bit    valid

Server Utilities    /sapdb/programs    7.7.06.10     64 bit    valid

PCR 7300            /sapdb/programs    7.3.00.60               valid

PCR 7301            /sapdb/programs    7.3.01.22               valid

PCR 7500            /sapdb/programs    7.5.00.50     64 bit    valid

SAP Utilities       /sapdb/programs    7.7.06.10     64 bit    valid

Redist Python       /sapdb/programs    7.7.06.10     64 bit    valid

Base                /sapdb/programs    7.7.06.10     64 bit    valid

JDBC                /sapdb/programs    7.6.06.02               valid

Messages            /sapdb/programs    MSG 0.7732              valid

ODBC                /sapdb/programs    7.7.06.10     64 bit    valid

Database Kernel     /sapdb/DHS/db      7.7.06.10     64 bit    valid

SQLDBC 77           /sapdb/programs    7.7.06.10     64 bit    valid

Loader              /sapdb/programs    7.7.06.10     64 bit    valid

SQLDBC              /sapdb/programs    7.7.06.10     64 bit    valid

Fastload API        /sapdb/programs    7.7.06.10     64 bit    valid

SQLDBC 76           /sapdb/programs    7.6.05.15     64 bit    valid

Do you know what could be the problem?

Thank for any hint!

Sorin

[former_member229109]

Hello Florin Radulea,

1) Please post the output of the commands running on the database server:

sdbregview u2013l

dbmcli inst_enum

dbmcli db_enum

2) Please try to connect to the database with dbm user and password dba.

Post the results.

Thank you and best regards, Natalia Khlopina

[florin_radulea]

Hello Natalia,

Yes I tried to connect with user DBA and pass DBA

http://maxdb.sap.com/doc/7_7/44/bbd88f91407006e10000000a155369/frameset.htm but I am not abbe to connect. I get that error Re: -2 ERR_USRFAIL: User authorization failed.

Below are the commands output that you advised me:

dbmcli inst_enum

OK

7.7.06.17 F:\sapdb\MDM\db

7.7.06.17 E:\sapdb\ZJD\db

dbmcli db_enum

OK

MDM F:\sapdb\MDM\db 7.7.06.17 fast running

MDM F:\sapdb\MDM\db 7.7.06.17 slow offline

ZJD E:\sapdb\ZJD\db 7.7.06.17 fast offline

ZJD E:\sapdb\ZJD\db 7.7.06.17 slow offline

The output for below command is in the next post to be more easy to read.

sdbregview u2013l

Thank you,

Best regard,

Florin

[florin_radulea]

Hello,

Bellow is the output for

sdbregview u2013l command:

package "DB Analyzer":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.7.06.17

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: Base >= 7.7.06.17

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: bin/dbanalyzer.exe

IS SUBPACKAGE: NO

DBANALYZER PATH: E:/sapdb/programs

package "Server Utilities":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.7.06.17

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: Base >= 7.7.06.17

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: bin/x_server.exe

IS SUBPACKAGE: NO

INDEPENDENT PROGRAM PATH: E:/sapdb/programs

package "PCR 7300":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.3.00.59

PACKAGE VERSION: 0

VALID: YES

MODIFICATION DATE: 13.04.2010

REQUIRE: Base >= 7.3.00.59

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: runtime/7300/pgm/libpcr.dll

IS SUBPACKAGE: NO

PRECOMPILER 7300 PATH: e:/sapdb/programs

package "PCR 7301":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.3.01.22

PACKAGE VERSION: 0

VALID: YES

MODIFICATION DATE: 13.04.2010

REQUIRE: Base

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: runtime/7301/pgm/libpcr.dll

IS SUBPACKAGE: NO

PRECOMPILER 7301 PATH: e:/sapdb/programs

package "PCR 7500":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.5.00.51

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: Base >= 7.5.00.51

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: runtime/7500/pgm/pgm64/libpcr.dll

IS SUBPACKAGE: NO

PRECOMPILER 7500 PATH: E:/sapdb/programs

package "Webtools":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs/web

SOFTWARE VERSION: 7.6.03.09

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: ODBC >= 7.6.03.09 64

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: pgm/webdbm.dll

IS SUBPACKAGE: NO

WEBTOOLS PATH: E:/sapdb/programs/web

package "SAP Utilities":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.7.06.17

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: Base >= 7.7.06.17

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: bin/dbmrfc.exe

IS SUBPACKAGE: NO

: E:/sapdb/data

INDEPENDENT PROGRAM PATH: E:/sapdb/programs

package "Redist Python":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.7.06.17

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: Base

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: bin/x_python.exe

IS SUBPACKAGE: NO

REDIST PYTHON PATH: E:/sapdb/programs

package "Base":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.7.06.17

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE:

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: pgm/dbmcli.exe

IS SUBPACKAGE: NO

INDEPENDENT DATA PATH: E:/sapdb/data

INDEPENDENT PROGRAM PATH: E:/sapdb/programs

package "JDBC":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.6.06.05

PACKAGE VERSION: 0

VALID: YES

MODIFICATION DATE: 13.04.2010

REQUIRE: Base

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: NO

IS SUBPACKAGE: NO

JAVA DRIVER PATH: E:/sapdb/programs

package "Messages":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: MSG 0.7732

PACKAGE VERSION: 0

VALID: YES

MODIFICATION DATE: 13.04.2010

REQUIRE: Base

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: NO

IS SUBPACKAGE: NO

MESSAGES PATH: E:/sapdb/programs

package "ODBC":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.7.06.17

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: Base >= 7.7.06.17

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: pgm/sdbodbc.dll

IS SUBPACKAGE: NO

ODBC PATH: E:/sapdb/programs

package "SQLDBC 77":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.7.06.17

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: Database Connectivity >= 7.7.06.17

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: pgm/libSQLDBC77.dll

IS SUBPACKAGE: NO

DBC PATH: E:/sapdb/programs

package "Database Kernel":

-

---

PACKAGE DIRECTORY: f:/sapdb/mdm/db

SOFTWARE VERSION: 7.7.06.17

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: Server Utilities >= 7.7.06.17

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: pgm/kernel.exe

IS SUBPACKAGE: NO

DEPENDENT PATH: f:/sapdb/mdm/db

PACKAGE DIRECTORY: e:/sapdb/zjd/db

SOFTWARE VERSION: 7.7.06.17

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: Server Utilities >= 7.7.06.17

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: pgm/kernel.exe

IS SUBPACKAGE: NO

DEPENDENT PATH: e:/sapdb/zjd/db

package "Loader":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.7.06.17

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: Redist Python >= 7.7.06.17

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: bin/loadercli.exe

IS SUBPACKAGE: NO

LOADER PATH: E:/sapdb/programs

package "SQLDBC":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.7.06.17

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: Base

FILELIST: YES

HAS DISPLAY NAME: YES

SCRIPT: YES

TEST FILE: pgm/libSQLDBC.dll

IS SUBPACKAGE: NO

DBC PATH: E:/sapdb/programs

package "SQLDBC 76":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.6.06.07

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: Database Connectivity >= 7.6.06.07

FILELIST: YES

HAS DISPLAY NAME: YES

SCRIPT: YES

TEST FILE: pgm/libSQLDBC76.dll

IS SUBPACKAGE: NO

DBC PATH: E:/sapdb/programs

package "Fastload API":

-

---

PACKAGE DIRECTORY: e:/sapdb/programs

SOFTWARE VERSION: 7.7.06.17

PACKAGE VERSION: 0

VALID: YES

MODE: 64 bit

MODIFICATION DATE: 13.04.2010

REQUIRE: SQLDBC 77

FILELIST: YES

HAS DISPLAY NAME: NO

SCRIPT: YES

TEST FILE: pgm/libSDBLoader.dll

IS SUBPACKAGE: NO

FASTLOAD PATH: E:/sapdb/programs