DataBlade Module Installation and Registration Guide Registering with the BladeManager Command-Line Interface

BladeManager generates a log file whenever you prepare, register, upgrade, or unregister a DataBlade module. If one of these tasks fails, the log file can point to the particular SQL statement that failed. Log files also list whether the failure was expected or unexpected and show the text of 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.

BladeManager stores log files in one of the following directories:

• /tmp/blademgr/uid, where uid is your UNIX user ID
• %TEMP%\blademgr

Periodically delete files from the log directory to free disk space.

You can manage log files by performing the following tasks:

• To view the list of log files, enter the following command:

	show log


BladeManager lists all available log files. You can see only log files created while BladeManager was running with your user ID.

• To see a particular log file, display the list of log files and enter the log file number.
• To see the most recent log file for the current session, enter the following command:

	show last log

• To delete log files for your user ID, enter the following command:

	del logs


BladeManager prompts you to continue with the removal of the log files from the operating system.