SYBASE ASE 15.0.3 VS 15.7 SP64

[Former Member]

We have 15.0.3 and 15.7 SP64 DB instance on one SUNOS box . 

15.0.3 version server produces the error log with below permissions at OS level .

-rw-r--r--      1      sybase    sybase    56879 Jul  25  10:08    SYBASE_Error.log

But 15.7 SP64 version produces the error log with below permission at OS level .

-rw-r-----      1      sybase    sybase    56879 Jul  25  10:08    SYBASE157_Error.log

Can you please advise on this .

Why 15.7 SP64 version fails to create error log file  with READ permission (-rw-r-----) whereas 15.0.3 version produces the log file with ( -rw-r--r-- )  permission .

Because of this our application team/Monitoring tool  is not able to read the errorlog file  . ( As a SYBASE user and as a DBA we are able to grant the permission , But Every Reboot requires DBA or SYBASE user to change the permission manually ) .

Please help me to fix this issue .

[jayrijnbergen · Accepted solution]

a restart by default doesn't start a new errorlog, but that's easily automated in the runserver file

e.g. archiving or removing the old server logfile, touching a new one a set the right permissions

so check the runserver files (for 15.0 and 15.7), maybe there's a umask command in there

otherwise you can easily set the umask or do chmod inside the runserver file

[Former Member · Accepted solution]

Thanks for the response Jeroen Rijnbergen . We have "mv" command in RUN server file ( It will move the error log file with date parameter ) and it moves to execute the dataserver command . So it creates a new errorlog file everytime in our environment .  ( It remains same for both versions ) . But 15.7 SP64 fails to create a file with "Read" permission for others . Apart from MV command ,,  Our Env Run server files doesn't have any unix command ( Umask, Chmod , chown ) . Please help to resolve this issues

[jayrijnbergen · Accepted solution]

so after the mv command, add these commands in your runserver file

touch SYBASE157_Error.log

chmod 644 SYBASE157_Error.log

[Former Member · Accepted solution]

Thanks for suggestion  Jeroen Rijnbergen . Would like to understand why 15.7 version dataserver process generates error log file without read permission for other user accounts.

[former_member188958 · Accepted solution]

This was a deliberate change made by SAP to improve security in 15.7 SP100.  See previous discussion

Similar changes were made to the permission settings of output files created by the isql and bcp utilities and, if memory serves, database dump and transaction log dump files. 

[Former Member · Accepted solution]

Bret, Thanks for the explanation . Previous discussion and demonstration will help me a lot .