Information

Title	Database can't open extent created with ADDONLINE

URL Name	P127852

Article Number	000127998

Environment	Product: OpenEdge Version: 10.1A and later OS: UNIX

Question/Problem Description

Database can't open extents created with PROSTRCT ADDONLINE
Extents are created and not deleted on the error

UMASK is set in the .profile to 022
Databases extents have Group and anybody set to read and execute but not write 644 or 640

Steps to Reproduce

Clarifying Information

Error Message	** Cannot find or open file <file-name>, errno = <number>. (43) Cannot find or open file /directory/dbname.d5, errno = 13. (43) Database add extent: ERROR adding extent: -20010. (6976) A logical error in shared memory has occurred while adding extents online. Recovery is performed by restarting the database. (12547) prostrct add FAILED. (12867)

Defect Number

Enhancement Number

Cause

When the addonline feature of prostrct is used, the permissions are inherited from the umask user .profile. If these are such that they exclude other users who have access to the database from writting to this extent, their sessions will fail with error 43.

Resolution

Initially, The file permissions must be modified using chmod, eg: chmod a+rw {files}

In order to prevent new extents from being created with restrictive permissions, set the UMASK to allow all users who have access to the database to be able to open those extents, e.g. UMASK 000 or 002.

Workaround

Notes

References to Other Documentation:

Progress Articles:

Why does prostrct addonline check connected users?
What are the rules for adding extents online to replicated databases?

Keyword Phrase

Last Modified Date	11/20/2020 7:37 AM

Database can't open extent created with ADDONLINE

Information