SID.log file too large

[Former Member]

Dear all,

SID.log file is too large(36GB)

I even could not open it in notepad or word.

Appreciate if you could give any idea on how can I read the log.

Please help.

Regards,

Fadzly Iqbal

[hans-juergen_schwindke · Accepted solution]

Hi,

for the future:

If ASE is down you can rename the SID.log file, e.g. to SID_yyyymmdd.log.  During startup ASE will create a new log file SID.log. By doing this you will have more log files but they are smaller and easier to handle.

When your ASE is running, you can switch to a new log file by using the procedure sp_errorlog. SyBooks Online

So when you run (Linux example path)

sp_errorlog 'change log','/sybase/SM3/ASE-15_0/install/SM3_new.log', 'jslog false'

ASE will stop using your current log SM3.log and start writing into SM3_new.log.

After you reboot ASE it will write into SM3.log again because in the runserver - file (RUN_SM3.bat) the parameter -e specifies this. So if you want to use SM3_new.log permanently you have to change the -e parameter.

Best regards,

Juergen

[victoria_normand · Accepted solution]

Nice advise for the future. Please just take into account that for Business Suite applications the ASE error log should always be named as <SID>.log.
On Unix platform this "rename" is done automatically when starting with startsap/startdb.
Best regards,

Victoria.

[DilipVoora · Accepted solution]

Hi Victoria,

Can you please elaborate on your last line "on Unix platform this "rename" is done automatically when starting with startsap/startdb"?

Regards,

Dilip Voora