Refreshing the database SCON log
Even when the amount of data written to the scon.log file is minimal, over time this file can reach a limit that causes processing to cease. The following instructions provide the steps for a utility that copies the existing log file and then empties scon.log, without impacting NetBackup IT Analytics processing.
The utility to refresh scon.log executes automatically according to the following rules:
Utility executes monthly to refresh the scon.log file
First run executes 30 days after portal installation
Production run is scheduled for the first Tuesday of every month
The utility searches for the following directory paths until an scon.log file is found:
'C:\opt\oracle\logs','C:\opt\aptare\oracle\logs','C:\opt\aptare\oracle\log','/tmp'
To refresh the scon.log file, use the following utility:
Log in to SQLPLUS, as shown below.
Linux & Windows:
sqlplus portal/<portal_password>@//localhost:1521/scdb
Execute the log cleanup utility,
Linux & Windows:
exec logfile_cleanup_pkg.cleanupLog('Y','Y');Two parameters are required, as described in the following table:
Description
Y
Y
scon.log file emptied
backup in scon_<month>.log file
Y
N
scon.log file emptied
backup in scon1.log file; all backups will overwrite scon1.log
N
Y
scon.log file emptied
no backup of the scon.log file
N
N
scon.log file emptied
no backup of the scon.log file
Note:
This utility is intended to be run no more than once a month. If you plan to run it more than once in a month, be aware of the naming convention for the backup scon.log file, as shown with the parameters in the above table.