Viewing log files
BladeManager generates a log file when you prepare a database for registration and when you register, upgrade, or unregister a DataBlade module. If one of these tasks fails, the log file lists the specific SQL statement that failed. Log files also list whether the failure was expected or unexpected, and they show the error generated by the SQL command.
An example of an expected error is an error issued when a DataBlade module contains an SQL statement to create a table, but that table already exists. When BladeManager receives an unexpected error, it halts the operation and returns the database to its prior state.
Log files are numbered consecutively and contain a time stamp. You should periodically delete log files to free disk space.