Consultor Eletrônico



Kbase P73303: Second database connection fails with error 1136 due to owner/group pairing
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   5/27/2008
Status: Verified

FACT(s) (Environment):

UNIX
Progress/OpenEdge Versions

SYMPTOM(s):

Connecting to multiple databases

Connecting to initial database with mpro

Connecting to second database using CONNECT statement in procedure editor

1136 error when connecting to second database

SYSTEM ERROR: Shared memory access permission denied (1136)

Setuid bit is enabled for all progress executables except _sqlsrv2 and _waitfor

Connecting from command line (mpro db1 -db db2) works fine for both databases.

CAUSE:

The user who owns the database was not a member of the group assigned to the database.

FIX:

Check the database owner and group for the database files. Make sure the owner is also a member of the group specified. If the owner of the database files is not in the corresponding group, the user will only have "other" permissions to the database.

For example,

The permissions for the database files might look like this:

-rw-rwxr-- 1 joeuser ts 2228224 Mar 22 16:23 sports2000.b1
-rw-rwxr-- 1 joeuser ts 720896 Mar 22 16:24 sports2000.d1
-rw-rwxr-- 1 joeuser ts 32768 Mar 22 16:24 sports2000.db
-rw-rwxr-- 1 joeuser ts 443 Mar 22 16:24 sports2000.lg
-rw-rwxr-- 1 joeuser ts 320 Mar 22 16:23 sports2000.st
-rw-rwxr-- 1 joeuser ts 327680 Mar 22 16:24 sports2000_10.d1

The second connection will fail for joeuser if he is not a member of the group ts. The group should be changed in that case to a group that joeuser is a member of or joeuser's default group. Or, alternatively, the owner should be changed to a user who is in the ts group. Otherwise, joeuser will only have read permissions to the database files, as the permissions for the files only allow r-- to any user.

Additionally, the group listed for the database files must have write access on the database files.