Consultor Eletrônico



Kbase 19072: Probkup to non-existing file cause errors 43 and 1617
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   8/31/1999
Probkup to non-existing file cause errors 43 and 1617

Title: probkup to non-existing file cause errors 43 and 1617

KnowledgeBase number: 19072
Creation Date: 1999/08/31
Modified Date: 1999/08/31
This document applies to: probkup, unix, umask, permissions, error
43, 13, and 1617

Version and Release Number: Impacts all versions less than or equal
to 9.0B.

Summary:

This kbase is being generated to document a bug which has been fixed
in versions > 9.0B. The bug deals with doing probkup online to a file
on disk which does not currently exist on your unix machine. When
you issue the probkup online command, you will receive the following
errors and probkup will terminate. The errors are:

Cannot find or open file filename errno = 13. (43)
Backup terminated due to errors. (1617)

Probkup online and offline should perform consistently when backing
up a database to disk to a non-existent file. Due to this bug they
do not.

Details:

The reason why it is different is because the offline backup is
creating the file just like the online backup does. The offline
backup is assigning the appropriate owner and group. The online
backup is is assigning the wrong owner and group and therefore has to
rely on the umask settings for other which in your case, probably does
not have write access.

One way to validate your umask is to enter: umask -S

There are currently two workarounds for this issue. They are:

1. You can type touch filename, which will create the file and then
the backup will be performed appropriately with the correct owner
and group.
or
2. You can change your umask to be 000 or give others write
permissions. This will allow the file to be created but will
still have the wrong owner and group.

Additional Information:

The bug # for this issue was 19990721-037. This bug has been closed
and is fixed in versions > 9.0B. The bug has not been patched as there
are workarounds to address this issue.