Kbase P127852: Database can't open extent created with ADDONLINE
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/3/2008 |
|
Status: Verified
FACT(s) (Environment):
UNIX
OpenEdge 10.1x
SYMPTOM(s):
Database can't open extent created with ADDONLINE
Extents are created and not deleted on the error
UMASK is set in the .profile to 022
** 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)
Databases extents have Group and anybody set to read and execute but not write
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.
FIX:
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.