Kbase P117094: Getting 1136 error when attempting to connect to a second database from procedure editor.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/12/2009 |
|
Status: Verified
SYMPTOM(s):
Getting 1136 error when attempting to connect to a second database from procedure editor.
Permissions on second database are 644
FACT(s) (Environment):
UNIX
Progress/OpenEdge Versions
CAUSE:
The recommended permissions for Progress database files require read write permissions for owner and group.
When Progress starts up, the Progress / OpenEdge client executables typically have the setuid bit enable which allows us to temporarily increase the security rights of the executable to match those of the owner of the executable.
After the client executable has completed its startup phase, the rights of the executable are dropped down to those of the user.
At that point in time if an attempt is made to connect to a database that the user doesn't have write privileges for either because the user is not a member of the same group listed for all the databse files or the permissions on the files do not allow any group to write to the files, the user will get an 1136 error.
FIX:
P117808Use the Unix chmod utility to set permissions on the databases which will be connected to from within the procedure editor.
Example:
chmod 664 <dbname>*