File: aguide04.htm

package info (click to toggle)
solid-desktop 2.2-3
links: PTS
area: non-free
in suites: potato, slink
size: 3,620 kB
ctags: 2,830
sloc: sh: 290; sql: 80; makefile: 64
file content (2067 lines) | stat: -rw-r--r-- 76,219 bytes
parent folder | download | duplicates (2)
<HTML>
<HEAD>
<TITLE></TITLE>
<LINK REL="ToC" HREF="httoc.htm">
<LINK REL="Index" HREF="htindex.htm">
<LINK REL="Next" HREF="aguide05.htm">
<LINK REL="Previous" HREF="aguide03.htm"></HEAD>
<BODY BGCOLOR="#FFFFFF">
<P ALIGN=CENTER>
<A HREF="aguide03.htm" TARGET="_self"><IMG SRC="gaguide/graprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Previous Page"></A>
<A HREF="httoc.htm" TARGET="_self"><IMG SRC="gaguide/gratop.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="TOC"></A>
<A HREF="htindex.htm" TARGET="_self"><IMG SRC="gaguide/graindex.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Index"></A>
<A HREF="aguide05.htm" TARGET="_self"><IMG SRC="gaguide/granext.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Next Page"></A>

<A NAME="E9E4"></A>
<H1>
<FONT FACE="Arial"><B>DATABASE MAINTENANCE</B></FONT></H1>
<BR>
<BLOCKQUOTE>
<P>This chapter gives you information on data security and database maintenance. It is divided into following topics
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>making backups
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>restoring backups
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>recovering from abnormal shutdown
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>logging
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>creating checkpoints
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>closing and opening the database
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>changing database location
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>running several servers on one computer
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>entering timed commands
</BLOCKQUOTE></UL>
<A NAME="E10E11"></A>
<P>
<FONT FACE="Arial"><B>Making Backups</B><A NAME="I2"></A></FONT>
<BLOCKQUOTE>
<P>Backups are made to secure the information stored in your database files. If you have lost your database files because of a system failure, you can continue working with the backup database.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>You can make backups manually by using SOLID <I>Remote Control</I>, or you can automate the backup operations to be run according to a fixed schedule. To automate backups, see the chapter <I>Entering timed commands</I> at the end of this chapter.
</BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. Be sure to have enough disk space in the backup directory. You will need space for your database and log files.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Make a Backup Manually Using SOLID </B><B><I>Remote Control</I></B></FONT></H4>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Connect to the server you want to backup. 
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Go to the BACKUP page and press the Backup button.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Enter the directory where you want the backup copy to be created, or use the suggested backup directory. 
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Press the OK button.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> uses a multiversioning technique allowing backups<A NAME="I3"></A> to be made on-line. You need not close the database file or shut down the server. However, it is advisable to automate your backups to be run at non-busy hours. After completing the<I> </I>backup, copy your backup files on tape using your backup software for protection against disk crashes.
</BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE 1. The backup directory entered must be a valid path name in the server operating system! For example, if the server runs on a UNIX operating system, path separators must be slashes, not backslashes.
<BR>NOTE 2. The time needed for making a backup is the time that passed between the messages Backup started and Backup completed successfully, which arrive to your SOLID <I>Remote Control</I> MESSAGES page.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Before starting the backup process, a checkpoint is created automatically. This guarantees that the state of a backup database is from the moment the backup process was started. The following files will be copied to the backup directory:
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>database file(s)
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>the configuration file (solid.ini)
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>the log file(s) modified or created after the previous backup (parameter BackupCopyLog is set yes by default)
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<P>The unnecessary log files are deleted from original directory after successful backup (parameter BackupDeleteLog is set yes by default).
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Correct a Failed Backup</B><A NAME="I4"></A></FONT></H4>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>When a backup is completed, you will see a message appear on the backup list in SOLID <I>Remote Control</I>. The first column in this list tells you the status of the backup, which can be either OK or Failed.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>If the backup failed, an error message appears on the message list. Correct the cause of the error and try again. The most common causes for failed backups are
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>the backup media is out of disk space
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>the backup directory does not exist
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>a database directory is defined as the backup directory
</BLOCKQUOTE></UL>
<A NAME="E10E12"></A>
<P>
<FONT FACE="Arial"><B>Restoring Backups</B><A NAME="I5"></A></FONT>
<BLOCKQUOTE>
<P>There are two alternative ways to restore a backup. You can either:
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>return to the state when backup was created or
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>revive a backup database to the current state by using log files to add data inserted or updated after the backup was made.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Return to the State when the Backup was Made</B></FONT></H4>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Shut down SOLID <I>Server</I>, if it is running.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Delete all log files from the log file directory. The default log file names are sol00001.log, sol00002.log, etc. 
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Copy the database file(s) from the backup directory to the database file directory.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Start your SOLID <I>Server</I>.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<P>This method will not perform any recovery because no log files exist.
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Revive a Backup Database to the Current State</B></FONT></H4>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Shut down SOLID <I>Server</I>, if it is running.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Copy the database file(s) from the backup directory to the database file directory.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Copy the log files from the backup directory to the log file directory. If there are logfiles with the same file names, <B>do not</B> replace those logfiles in the log file directory with logfiles from the backup directory.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Start your SOLID <I>Server</I>.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<P>SOLID <I>Server </I>will automatically use the log files to perform a roll-forward recovery. 
</BLOCKQUOTE>
<A NAME="E10E13"></A>
<P>
<FONT FACE="Arial"><B>Recovering from Abnormal Shutdown</B></FONT>
<BLOCKQUOTE>
<P>If the server was closed abnormally, i.e. if it was not shut down using the procedures described earlier, SOLID <I>Server</I> will automatically use the log files to perform a roll-forward recovery during the next start up. No administrative procedures are needed to start the recovery<A NAME="I6"></A>.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The message Starting roll-forward recovery appears. After the recovery<A NAME="I7"></A> has been completed, a message will indicate how many transactions were recovered. If no transactions were made since the last checkpoint, this is indicated by the following message
<BR>0 transactions recovered.
</BLOCKQUOTE>
<A NAME="E10E14"></A>
<P>
<FONT FACE="Arial"><B>Logging</B><A NAME="I8"></A></FONT>
<BLOCKQUOTE>
<P>Logging guarantees that no committed operations are lost in case of a system failure. When an operation is executed in the server, the same operation is also saved to a log file<A NAME="I9"></A>. The log file is used for recovery in case the server is shut down abnormally. 
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>A backup operation will copy the log and database files to the backup directory and delete the log files from the database directory. You may change the default behavior by changing the parameters BackupCopyLog<A NAME="I10"></A> and BackupDeleteLog<A NAME="I11"></A> in the General section of parameters in solid.ini.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The log file can be written using different modes. The modes differ in the speed and security they offer. The default ping-pong method is the best choice in most cases.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>You can set the logging mode using the LogWriteMode parameter<A NAME="I12"></A> in the Logging section of parameters. The different modes are listed in <I>Appendix B Configuration Parameters</I>. The log manager of SOLID <I>Server</I> can run in four different operation modes. The choice of log method depends on the log file media and the level of security needed. The available logging methods are:
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Ping-pong method
<BR>This method uses the last two allocated disk blocks in the log file to write the newest and second-newest version of the same logical incomplete disk block. The ping-pong method toggles between these two blocks until one block becomes full.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Write-once method
<BR>If the configuration parameter CommitMaxWait is set at zero, this method will write each log record immediately to the disk. An incomplete record is always padded with blanks, and the record is written to the disk. This is the method of choice when the log file storage media is, for example, a magnetic tape drive or a WORM, and when the update rate is low or when only one client at a time makes updates. If the server runs on a single thread, this method of logging should not be used.
<BR>If the parameter CommitMaxWait is greater than zero, the logging works in group-commit mode. The server waits for the time specified in CommitMaxWait for someone else to complete the disk block. When the disk block is completed, it is written to the disk. If time out has expired instead, the block will be padded with blank records. This is the most efficient algorithm when the database update rate is extremely high and the updates are performed by several threads.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Overwriting method
<BR>This method rewrites incomplete blocks at each commit until it becomes full. It may be used when data loss from the last log-file disk block is affordable.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>TIP  For both security and performance reasons, it is a good idea to keep log files and database files on different physical disk devices. If one disk drive is damaged, you will lose either your database files or log files but not both.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<A NAME="E10E15"></A>
<P>
<FONT FACE="Arial"><B>Creating Checkpoints</B><A NAME="I13"></A></FONT>
<BLOCKQUOTE>
<P>Checkpoints are used to store a consistent state of the database onto the database file. Checkpoints are needed for speeding up the roll-forward recovery<A NAME="I14"></A> after a system failure. In the roll-forward recovery<A NAME="I15"></A>, the database will start recovering transactions from the last checkpoint. The longer it has been since the last checkpoint was created, the more operations are recovered from the log file(s).
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>To speed up recoveries, checkpoints should be created frequently; however, the server performance is reduced during the creation of a checkpoint. Furthermore, the speed of checkpoint creation depends on the amount of database cache used; the more database cache is used, the longer the checkpoint creation will take. Consider these issues when deciding the frequency<A NAME="I16"></A> of checkpoints. See <I>Appendix B Configuration Parameters </I>for a description of the use of CacheSize parameter.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> has an automatic checkpoint<A NAME="I17"></A> creation daemon, which creates a checkpoint after a certain number of writes to the log files. The default checkpoint interval is every 5000 log writes. You may change the value of the parameter CheckpointInterval<A NAME="I18"></A> in the General section of parameters. To learn how to change a parameter value, see the chapter <I>SOLID Server Parameter Settings</I> in this guide. 
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Before and after a large database operation, you may want to create a checkpoint manually. You can create checkpoints manually by using SOLID <I>Remote Control</I> or you can automate the checkpoint creation using timed commands. To automate checkpoints, see the chapter <I>Entering timed </I><I>commands </I>at the end of this chapter. Use the following procedure to create a checkpoint manually.
</BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. There can be only one checkpoint in the database at a time. When a new checkpoint is created, the older checkpoint<A NAME="I19"></A> is automatically erased.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Create a Checkpoint Manually</B><A NAME="I20"></A><B> Using SOLID </B><B><I>Remote Control</I></B></FONT></H4>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Connect to the server for which you want to create a checkpoint<I>.</I>
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Select the BACKUP page.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Press the Checkpoint button.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Press the Yes button in the Do you want to create a checkpoint? dialog box.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI> Creation starts immediately. When it is completed, the message Checkpoint creation completed  appears on the status line. You can view this message also on the Messages page.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>On non-graphical user interfaces<A NAME="I21"></A>, you can create a checkpoint using the SOLID <I>Remote Control</I> (Teletype) program. Issue the command checkpoint to start checkpoint creation.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<A NAME="E10E16"></A>
<P>
<FONT FACE="Arial"><B>Closing the Database</B><A NAME="I22"></A></FONT>
<BLOCKQUOTE>
<P>In some cases you may want to prevent users from connect to the server. For example, when you are shutting down a server, you may want to prevent new users from connecting to the server. After closing the database, only connections from SOLID <I>Remote Control</I> will be accepted. Closing the database does not affect existing user connections. 
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Close the Database Using SOLID </B><B><I>Remote Control</I></B><A NAME="I23"></A></FONT></H4>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Connect to the server you want to close.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Wait for the STATUS page to appear.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Press the Close... button.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Answer Yes to the question Do you want to close the database?
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<P>After this, the database is closed and no new connections are accepted (clients will get SOLID Error Message 14506). This is indicated by the message text No new connections allowed.
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Open a Closed Database Using SOLID </B><B><I>Remote Control</I></B></FONT></H4>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Connect to the server you want to open.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Wait for the STATUS page to appear.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Press the Open... button.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Answer Yes to the question Do you want to open the database?
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<P>After this, the database is opened and new connections are accepted. This is indicated by the message New connections allowed.
</BLOCKQUOTE>
<A NAME="E10E17"></A>
<P>
<FONT FACE="Arial"><B>Changing Database Location</B><A NAME="I24"></A></FONT>
<BLOCKQUOTE>
<P>Changing a database location in SOLID <I>Server </I>is as easy as copying a file from one directory to another.
</BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. To copy a database file, you need to shut down the server to release the operating system file locks on the database file and log files.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Change Database Location</B><A NAME="I25"></A></FONT></H4>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Verify that SOLID <I>Server</I> is not running.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Copy the database and log files to the target directory.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Copy the solid.ini file to the target directory. Check that the database file directory, log file directory and backup directory are correctly defined in the configuration file solid.ini.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Start SOLID <I>Server </I>using the target directory as the current working directory using the command line option -c <I>directory-name</I>.
</BLOCKQUOTE></UL>
<A NAME="E10E18"></A>
<P>
<FONT FACE="Arial"><B>Running Several Servers </B><B>on One Computer</B><A NAME="I26"></A></FONT>
<BLOCKQUOTE>
<P>In some cases, you may want to run two or more databases<A NAME="I27"></A> on one computer. For example, you may need a configuration with a production database and a test database running on the same computer.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>SOLID <I>Server </I>is able to use one database per database server, but you can start several servers each using its own database file. To make these servers use different databases, either start the server processes from the directories your databases are located in or give the locations of configuration files by using the command line option -c <I>directory-name</I> to change the working directory. Remember to use different network names for each server.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>In the SOLID <I>Server</I> Windows version, there is a limitation to using several servers in one computer. Windows memory management allows only one SOLID <I>Server </I>to be run at a time. You can, however, trick Windows by renaming the other SOLID executable. For example, you can run SOLID.EXE and SOLID2.EXE at the same time without problems.
</BLOCKQUOTE>
<A NAME="E10E19"></A>
<P>
<FONT FACE="Arial"><B>Entering Timed Commands</B><A NAME="I28"></A></FONT>
<BLOCKQUOTE>
<P>SOLID<I> Server</I> has a built-in timer, which allows you to automate your administrative tasks<A NAME="I29"></A>. You can use timed commands to execute system commands, to create backups, checkpoints and database status reports, to open and close databases, to disconnect users or to shut down servers<A NAME="I30"></A><A NAME="I31"></A><A NAME="I32"></A><A NAME="I33"></A><A NAME="I34"></A><A NAME="I35"></A><A NAME="I36"></A><A NAME="I37"></A><A NAME="I38"></A>.
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Enter a Timed Command Using SOLID </B><B><I>Remote Control</I></B></FONT></H4>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Connect to the server.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Go to the TIMER page, and press the New button.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Select the command from the Commands list.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Enter the time when you want the command to be executed.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. The format used is HH:MM (24-hour format).
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Select a day for the timed command, or select All to have it executed every day.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Enter the command arguments in the Argument text box.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Press the Save button to enable the command.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Enter a Timed Command Manually</B></FONT></H4>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Timed commands can be entered manually by editing the At parameter of the [Srv] section in the solid.ini file. The syntax is:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>At-string := timed-command[, timed-command]
<BR>timed-command := [day] HH:MM command argument
<BR>day := sun | mon | tue | wed | thu | fri | sat</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>If the day is not given, the command is executed daily.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Example:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>[Srv]
<BR>At=20:30 makecp,21:00 backup,sun 23:00 shutdown</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>Arguments and the Defaults for the Different Timed Commands</B><A NAME="I39"></A></FONT></H4>
</BLOCKQUOTE>
<BLOCKQUOTE><TABLE>
<TR>
<TD WIDTH=160 VALIGN=top >
<P><B>Command</B>
</TD><TD WIDTH=160 VALIGN=top >
<A NAME="E7E11"></A>
<P>Argument
</TD><TD WIDTH=136 VALIGN=top >
<A NAME="E7E11"></A>
<P>Default</TD>
</TR>
<TR>
<TD WIDTH=160 VALIGN=top >
<P>backup
</TD><TD WIDTH=160 VALIGN=top >
<A NAME="E7E12"></A>
<P>backup directory
</TD><TD WIDTH=136 VALIGN=top >
<A NAME="E7E12"></A>
<P>the default backup directory that is set in the configuration file</TD>
</TR>
<TR>
<TD WIDTH=160 VALIGN=top >
<P>throwout
</TD><TD WIDTH=160 VALIGN=top >
<A NAME="E7E13"></A>
<P>user name, all
</TD><TD WIDTH=136 VALIGN=top >
<A NAME="E7E13"></A>
<P>no default, argument compulsory</TD>
</TR>
<TR>
<TD WIDTH=160 VALIGN=top >
<P>checkpoint
</TD><TD WIDTH=160 VALIGN=top >
<A NAME="E7E14"></A>
<P>no arguments
</TD><TD WIDTH=136 VALIGN=top >
<A NAME="E7E14"></A>
<P>no default</TD>
</TR>
<TR>
<TD WIDTH=160 VALIGN=top >
<P>shutdown
</TD><TD WIDTH=160 VALIGN=top >
<A NAME="E7E15"></A>
<P>no arguments
</TD><TD WIDTH=136 VALIGN=top >
<A NAME="E7E15"></A>
<P>no default</TD>
</TR>
<TR>
<TD WIDTH=160 VALIGN=top >
<P>report
</TD><TD WIDTH=160 VALIGN=top >
<A NAME="E7E16"></A>
<P>report file name
</TD><TD WIDTH=136 VALIGN=top >
<A NAME="E7E16"></A>
<P>no default, argument compulsory</TD>
</TR>
<TR>
<TD WIDTH=160 VALIGN=top >
<P>system
</TD><TD WIDTH=160 VALIGN=top >
<A NAME="E7E17"></A>
<P>system command
</TD><TD WIDTH=136 VALIGN=top >
<A NAME="E7E17"></A>
<P>no default</TD>
</TR>
<TR>
<TD WIDTH=160 VALIGN=top >
<P>open
</TD><TD WIDTH=160 VALIGN=top >
<A NAME="E7E18"></A>
<P>no arguments
</TD><TD WIDTH=136 VALIGN=top >
<A NAME="E7E18"></A>
<P>no default</TD>
</TR>
<TR>
<TD WIDTH=160 VALIGN=top >
<P>close
</TD><TD WIDTH=160 VALIGN=top >
<A NAME="E7E19"></A>
<P>no arguments
</TD><TD WIDTH=136 VALIGN=top >
<A NAME="E7E19"></A>
<P>no default</TD></TR>
</TABLE></BLOCKQUOTE>

<A NAME="E7E19"></A>
<P><B>USING SOLID DATABASE TOOLS</B>
<BLOCKQUOTE>
<P>This chapter describes SOLID Database Tools, a set of utilities for performing various database tasks. Not all SOLID Tools are necessarily part of the standard product delivery, and their availability on some platforms may be limited. For information about SOLID Database Tools, contact your SOLID sales representative or Solid Online Services on our Web server. The service is located at:
<BR><B>        </B><B>http://www.solidtech.com/</B>
</BLOCKQUOTE>
<A NAME="E10E20"></A>
<P>
<FONT FACE="Arial"><B>Command Line Arguments</B></FONT>
<BLOCKQUOTE>
<P>This paragraph lists and describes the available command line arguments that can be used with all SOLID Database Tools. The tool-specific options are listed with the usage of each tool.
</BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. When there is a contradiction in the command line, the tool gives you a list of the possible options as a result. Please check the command line you entered.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>Command Line Arguments:</B></FONT></H4>
</BLOCKQUOTE>

<BLOCKQUOTE><TABLE>
<TR>
<TD WIDTH=120 VALIGN=top >
<P><B>Argument</B>
</TD><TD WIDTH=360 VALIGN=top >
<A NAME="E7E20"></A>
<P>Description</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>server name
</TD><TD WIDTH=360 VALIGN=top >
<A NAME="E7E21"></A>
<P>This network name of the SOLID <I>Server</I> that you are connected to. Logical Data Source Names can also be used with tools; refer to the <B>chapter </B><B><I>Network Connections</I></B> for further information. The given network name must be enclosed in quotes.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>user name
</TD><TD WIDTH=360 VALIGN=top >
<A NAME="E7E22"></A>
<P>This is required to identify the user and to determine which rights he has. Without appropriate rights execution is denied.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>password
</TD><TD WIDTH=360 VALIGN=top >
<A NAME="E7E23"></A>
<P>This password given to the user for accessing the database.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>table name
</TD><TD WIDTH=360 VALIGN=top >
<A NAME="E7E24"></A>
<P>The name of the table accessed. * can be used with SOLID <I>Export</I> to export all tables with one command line.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>control file
</TD><TD WIDTH=360 VALIGN=top >
<A NAME="E7E25"></A>
<P>The name of the control file that defines the import file used with SOLID <I>SpeedLoader</I>. A file of this type is produced by executing SOLID <I>Export</I>.</TD></TR></TABLE>
<A NAME="E10E21"></A>
<P>
<FONT FACE="Arial"><B>SOLID </B><B><I>SpeedLoader</I></B></FONT>
<BLOCKQUOTE>
<P>SOLID <I>SpeedLoader</I> is a tool for loading data from external ASCII files into a SOLID database. SOLID <I>SpeedLoader</I> can load data in a variety of formats and produce detailed information of the loading process into a log file. The format of the import file, i.e., the file containing the external ASCII data, is specified in a control file.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>There are two versions of SOLID <I>SpeedLoader</I>, the standalone version and the network version. They both perform the same task but in different manners. 
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>In the standalone version, data is loaded directly into the database file. This enables maximum performance; the server must be shut down while the loading occurs.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>In the network version, data is loaded into the database through the SOLID <I>Server</I> program. This enables online operation of the database during the loading. The data to be loaded does not have to reside in the server computer.
</BLOCKQUOTE></UL>
<P>
<FONT FACE="Arial"><A NAME="I40"></A><A NAME="I41"></A>Control File<A NAME="I42"></A><A NAME="I43"></A></FONT>
<BLOCKQUOTE>
<P>The control file provides information on the structure of the import file. It gives the following information:
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>the name of the import file
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>the format of the import file
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>the table and columns to be loaded
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. Each import file requires a separate control file. SOLID <I>SpeedLoader</I> loads data into one table at a time.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The control file format is somewhat similar to control file structures found in other database management systems, i.e., Oracle and DB/2.
</BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P><A NAME="I44"></A><A NAME="I45"></A>NOTE 1. The table must exist in the database in order to perform data loading.
<BR>NOTE 2. Schema support is not currently available in SOLID <I>Speedloader</I>.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<P>
<FONT FACE="Arial">Import File<A NAME="I46"></A><A NAME="I47"></A></FONT>
<BLOCKQUOTE>
<P>The import file must be of ASCII type. The import file may contain the data either in a fixed or a delimited format:
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>In fixed-length format data records have a fixed length, and the data fields inside the records have a fixed position and length.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>In delimited format data records can be of variable length. Each data field and data record is separated from the next with a delimiting character such as a comma (this is what SOLID <I>Export </I>produces). Fields containing no data are automatically set to NULL.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<P>Data fields within a record may be in any order specified by the control file.
</BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE 1. Data in the import file must be of a suitable type. E.g., numbers that are presented in a Float format cannot be loaded into a field of Integer or Smallint type.
<BR>NOTE 2. Data of Varbinary and Long Varbinary type are hexadecimal encoded in the import file.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<P>
<FONT FACE="Arial"><A NAME="I48"></A><A NAME="I49"></A>Message Log File<A NAME="I50"></A><A NAME="I51"></A></FONT>
<BLOCKQUOTE>
<P>During loading, SOLID <I>SpeedLoader</I> produces a log file containing the following information:
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>the date and time of the loading
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>loading statistics  such as the number of rows successfully loaded, the number of failed rows, and the load time if it has been specified with the option
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>any possible error messages
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<P>If the log file cannot be created, the loading process is terminated. By default the name of the log file is generated from the name of the import file by substituting the file extension of the import file with the file extension .log. For example, my_table.ctr creates the log file my_table.log. To specify another kind of file name, use the option -l.
</BLOCKQUOTE>
<P>
<FONT FACE="Arial">Configuration File<A NAME="I52"></A><A NAME="I53"></A></FONT>
<BLOCKQUOTE>
<P>A configuration file is not required for SOLID <I>SpeedLoader</I>. The configuration values for the server parameters are included in the SOLID <I>Server</I> configuration file solid.ini.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Client copies of this file can be made to provide connection information required for SOLID <I>Speedloader</I>. If no server name is specified in the command line, SOLID <I>SpeedLoader</I> will choose the server name it will connect to from the server configuration file. E.g., to connect to a server using the NetBIOS protocol and with the server name SOLID, the following lines should be included in the configuration file:
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>[Com]
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Connect=netbios SOLID
</BLOCKQUOTE>
<P>
<FONT FACE="Arial">Invoking SOLID <I>SpeedLoader</I><A NAME="I54"></A><A NAME="I55"></A></FONT>
<BLOCKQUOTE>
<P>SOLID <I>SpeedLoader</I> is invoked with the command solload or solloads followed by various arguments. If you invoke SOLID <I>SpeedLoader</I> with no arguments, you will see a summary of the arguments with a brief description, i.e. their usage. The command line syntax is:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>solload [options] [server-name] &lt;user-name&gt; &lt;password&gt; &lt;control-file&gt; </PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>or
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>solloads [options] [server-name] &lt;user-name&gt; &lt;password&gt; &lt;control-file&gt; </PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>The possible options are<A NAME="I56"></A><A NAME="I57"></A> in the following table:
</BLOCKQUOTE>
<BLOCKQUOTE><TABLE>
<TR>
<TD WIDTH=162 VALIGN=top >
<P><B>Option</B>
</TD><TD WIDTH=318 VALIGN=top >
<A NAME="E7E26"></A>
<P>Description</TD>
</TR>
<TR>
<TD WIDTH=162 VALIGN=top >
<P>-b&lt;records&gt;
</TD><TD WIDTH=318 VALIGN=top >
<A NAME="E7E27"></A>
<P>Number of records to commit in one batch</TD>
</TR>
<TR>
<TD WIDTH=162 VALIGN=top >
<P>-c&lt;dir&gt;
</TD><TD WIDTH=318 VALIGN=top >
<A NAME="E7E28"></A>
<P>Change working directory</TD>
</TR>
<TR>
<TD WIDTH=162 VALIGN=top >
<P>-l&lt;filename&gt;
</TD><TD WIDTH=318 VALIGN=top >
<A NAME="E7E29"></A>
<P>Write log entries to this file</TD>
</TR>
<TR>
<TD WIDTH=162 VALIGN=top >
<P>-L&lt;filename&gt;
</TD><TD WIDTH=318 VALIGN=top >
<A NAME="E7E30"></A>
<P>Append log entries to this file</TD>
</TR>
<TR>
<TD WIDTH=162 VALIGN=top >
<P>-n&lt;records&gt;
</TD><TD WIDTH=318 VALIGN=top >
<A NAME="E7E31"></A>
<P>Insert array size (network version)</TD>
</TR>
<TR>
<TD WIDTH=162 VALIGN=top >
<P>-t
</TD><TD WIDTH=318 VALIGN=top >
<A NAME="E7E32"></A>
<P>Print load time</TD>
</TR>
<TR>
<TD WIDTH=162 VALIGN=top >
<P>-x emptytable
</TD><TD WIDTH=318 VALIGN=top >
<A NAME="E7E33"></A>
<P>Load data only if there are no rows in the table</TD>
</TR>
<TR>
<TD WIDTH=162 VALIGN=top >
<P>-x errors:&lt;count&gt;
</TD><TD WIDTH=318 VALIGN=top >
<A NAME="E7E34"></A>
<P>Maximum error count</TD>
</TR>
<TR>
<TD WIDTH=162 VALIGN=top >
<P>-x nointegrity
</TD><TD WIDTH=318 VALIGN=top >
<A NAME="E7E35"></A>
<P>No integrity checks during load (standalone version)</TD>
</TR>
<TR>
<TD WIDTH=162 VALIGN=top >
<P>-x skip:&lt;records&gt;
</TD><TD WIDTH=318 VALIGN=top >
<A NAME="E7E36"></A>
<P>Number of records to skip</TD>
</TR>
<TR>
<TD WIDTH=162 VALIGN=top >
<P>-?
</TD><TD WIDTH=318 VALIGN=top >
<A NAME="E7E37"></A>
<P>Help = Usage</TD></TR>
</TABLE></BLOCKQUOTE>

<P>
<FONT FACE="Arial">Control File Syntax<A NAME="I58"></A><A NAME="I59"></A></FONT>
<BLOCKQUOTE>
<P>The control file syntax has the following characteristics:
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>keywords must be given in capital letters
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>comments can be included using the standard SQL double-dash (--) comment notation
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>statements can continue from line to line with new lines beginning with any word
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<P>SOLID <I>SpeedLoader</I> reserved words must be enclosed in quotes if they are used as data dictionary objects, that is, table or column names. The following list contains all reserved words for the SOLID <I>SpeedLoader</I> control file:
</BLOCKQUOTE>
<BLOCKQUOTE><TABLE>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>AND
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E38"></A>
<P>ANSI</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>APPEND
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E39"></A>
<P>BINARY</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>BLANKS
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E40"></A>
<P>BY</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>CHAR
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E41"></A>
<P>CHARACTERSET</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>DATA
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E42"></A>
<P>DATE</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>DECIMAL
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E43"></A>
<P>DOUBLE</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>ENCLOSED
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E44"></A>
<P>ERRORS</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>FIELDS
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E45"></A>
<P>FLOAT</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>IBMPC
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E46"></A>
<P>INFILE</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>INSERT
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E47"></A>
<P>INTEGER</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>INTO
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E48"></A>
<P>LOAD</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>LONG
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E49"></A>
<P>MSWINDOWS</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>NOCNV
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E50"></A>
<P>NOCONVERT</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>NULLIF
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E51"></A>
<P>NULLSTR</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>NUMERIC
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E52"></A>
<P>OPTIONALLY</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>OPTIONS
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E53"></A>
<P>PCOEM</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>POSITION
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E54"></A>
<P>PRECISION</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>PRESERVE
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E55"></A>
<P>REAL</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>REPLACE
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E56"></A>
<P>SCAND7BIT</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>SKIP
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E57"></A>
<P>SMALLINT</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>TABLE
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E58"></A>
<P>TERMINATED</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>TIME
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E59"></A>
<P>TIMESTAMP</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>TINYINT
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E60"></A>
<P>VARBIN</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>VARCHAR
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E61"></A>
<P>WHITESPACE</TD></TR>
</TABLE></BLOCKQUOTE>

<BLOCKQUOTE>
<P>The control file begins with the statement LOAD DATA followed by several statements that describe the data to be loaded. Only comments or the OPTIONS statement may optionally precede the LOAD DATA statement.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The following table describes the full syntax of the control file.
</BLOCKQUOTE>

<BLOCKQUOTE><TABLE>
<TR>
<TD WIDTH=150 VALIGN=top >
<P><B>Syntax Element</B>
</TD><TD WIDTH=330 VALIGN=top ><BR></TD>
</TR>
<TR>
<TD WIDTH=150 VALIGN=top >
<P>control-file
</TD><TD WIDTH=330 VALIGN=top >
<A NAME="E7E62"></A>
<P>::= [option-part] load-data-part into-table-part</TD>
</TR>
<TR>
<TD WIDTH=150 VALIGN=top >
<P>option-part
</TD><TD WIDTH=330 VALIGN=top >
<A NAME="E7E63"></A>
<P>::= OPTIONS (options)</TD>
</TR>
<TR>
<TD WIDTH=150 VALIGN=top >
<P>options
</TD><TD WIDTH=330 VALIGN=top >
<A NAME="E7E64"></A>
<P>::= option [, option ]</TD>
</TR>
<TR>
<TD WIDTH=150 VALIGN=top >
<P>option
</TD><TD WIDTH=330 VALIGN=top >
<A NAME="E7E65"></A>
<P>::= [SKIP = 'int_literal'] | [ERRORS = 'int_literal']</TD>
</TR>
<TR>
<TD WIDTH=150 VALIGN=top >
<P>load-data-part
</TD><TD WIDTH=330 VALIGN=top >
<A NAME="E7E66"></A>
<P>::= LOAD [DATA] [characterset-specification] [DATE date_mask] [TIME time_mask] 
<BR>[TIMESTAMP timestamp_mask] [INFILE filename] [PRESERVE BLANKS]</TD>
</TR>
<TR>
<TD WIDTH=150 VALIGN=top >
<P>characterset-specification
</TD><TD WIDTH=330 VALIGN=top >
<A NAME="E7E67"></A>
<P>::= CHARACTERSET 
<BR>{ NOCONVERT | NOCNV | ANSI | MSWINDOWS | PCOEM | IBMPC | SCAND7BIT }</TD>
</TR>
<TR>
<TD WIDTH=150 VALIGN=top >
<P>into-table-part
</TD><TD WIDTH=330 VALIGN=top >
<A NAME="E7E68"></A>
<P>::= INTO TABLE tablename [APPEND | INSERT | REPLACE]
<BR>[FIELDS TERMINATED BY
<BR>{ WHITESPACE | hex_literal |'char']}
<BR>[FIELDS [OPTIONALLY] ENCLOSED BY
<BR>{&quot;char'&quot;| hex_literal} [AND &quot;char&quot; | hex_literal]] (column_list)</TD>
</TR>
<TR>
<TD WIDTH=150 VALIGN=top >
<P>hex_literal
</TD><TD WIDTH=330 VALIGN=top >
<A NAME="E7E69"></A>
<P>::= X'hex_byte_string'</TD>
</TR>
<TR>
<TD WIDTH=150 VALIGN=top >
<P>column_list
</TD><TD WIDTH=330 VALIGN=top >
<A NAME="E7E70"></A>
<P>::= column [, column]</TD>
</TR>
<TR>
<TD WIDTH=150 VALIGN=top >
<P>column
</TD><TD WIDTH=330 VALIGN=top >
<A NAME="E7E71"></A>
<P>::= column_name datatype_spec 
<BR>[POSITION ('int_literal' {: | -} 'int_literal')]
<BR>[DATE date_mask ] [TIME time_mask ]
<BR>[TIMESTAMP timestamp_mask ]
<BR>[NULLIF BLANKS | NULLIF NULLSTR| NULLIF 'string' | NULLIF (('int_literal' {: | -} 'int_literal') = 'string')]</TD>
</TR>
<TR>
<TD WIDTH=150 VALIGN=top >
<P>datatype_spec
</TD><TD WIDTH=330 VALIGN=top >
<A NAME="E7E72"></A>
<P>::= {BINARY | CHAR [ length ] | DATE | 
<BR>DECIMAL [ ( precision [ , scale ] ) ] | DOUBLE PRECISION | FLOAT [ ( precision ) ] | INTEGER | LONG VARBINARY | LONG VARCHAR | NUMERIC [ ( precision [ , scale ] ) ] | REAL | SMALLINT | TIME | 
<BR>TIMESTAMP [ ( timestamp precision ) ] | TINYINT | VARBINARY | VARCHAR [ ( length ) ] }</TD></TR>
</TABLE></BLOCKQUOTE>

<BLOCKQUOTE>
<P>The following paragraphs explain syntax elements and their use is in detail.
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>CHARACTERSET</B></FONT></H4>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The CHARACTERSET keyword is used to define the character set used in the input file. If the CHARACTERSET keyword is not used or if it is used with the parameter NOCONVERT or NOCNV, no conversions are made. Use the parameter ANSI for the ANSI character set, MSWINDOWS for the MS Windows character set, PCOEM for the ordinary PC character set, IBMPC for the IBM PC character set, and SCAND7BIT for the 7-bit character set containing Scandinavian characters.
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>DATE, TIME, and TIMESTAMP</B></FONT></H4>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>These keywords can be used in two places with different functionality:
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>When one of these keywords is used as a part of the  load-data-part element, it defines the format used in the import file for inserting data into any column of that type.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>When a keyword appears as a part of a column definition it specifies the format used when inserting data into that column.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE 1. Masks used as part of the load-data-part element must be in the following order: DATE, TIME, and TIMESTAMP. Each is optional.
<BR>NOTE 2. Data must be of the same type in the import-file, the mask, and the column in the table into which the data is loaded.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The following table shows the available data masks:
</BLOCKQUOTE>
<BLOCKQUOTE><TABLE>
<TR>
<TD WIDTH=240 VALIGN=top >
<P><B>Data Type</B>
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E73"></A>
<P>Available Data Masks</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>DATE
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E74"></A>
<P>YYYY/YY-MM/M-DD/D</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>TIME
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E75"></A>
<P>HH/H:NN/N:SS/S</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>TIMESTAMP
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E76"></A>
<P>YYYY/YY-MM/M-DD/D HH/H:NN/N:SS/S</TD></TR>
</TABLE></BLOCKQUOTE>

<BLOCKQUOTE>
<P>In the above table, year masks are YYYY and YY, month masks MM and M, day masks DD and D, hour masks HH and H, minute masks NN and N, and second masks SS and S. Masks within a date mask may be in any order, e.g., a date mask could be &#145;MM-DD-YYYY&#146;. If the date data of the import file is formatted as 1995-01-31 13:45:00, use the mask YYYY-MM-DD HH:NN:SS.
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>PRESERVE BLANKS</B></FONT></H4>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The PRESERVE BLANKS keyword is used to preserve all blanks in text fields.
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>into-table-part</B></FONT></H4>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The into-table-part element is used to define the name of the table and columns that the data is inserted into.
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>FIELDS TERMINATED BY</B></FONT></H4>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The FIELDS TERMINATED BY keyword is used to define the character used to distinguish where fields end in the input file.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The ENCLOSED BY keyword is used to define the character that precedes and follows data in the input file.
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>POSITION</B></FONT></H4>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The POSITION keyword is used to define a field's position in the logical record. Both start and end positions must be defined.
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>NULLIF</B></FONT></H4>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The NULLIF keyword is used to give a column a NULL value if the appropriate field has a specified value. An additional keyword specifies the value the field must have. The keyword BLANKS sets a NULL value if the field is empty; the keyword NULL sets a NULL value if the field is a string 'NULL'; the definition 'string' sets a NULL value if the field matches the string 'string'; the definition '((start : end) = 'string')' sets a NULL value if a specified part of the field matches the string 'string'.
</BLOCKQUOTE>
<P>
<FONT FACE="Arial">Loading Fixed-format Records</FONT>
<BLOCKQUOTE>
<P>Examples of the control file when loading data from a fixed-format import file:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>-- EXAMPLE 1
<BR>LOAD DATA
<BR>INFILE 'EXAMP1.DAT'
<BR>INTO TABLE SUPPLIERS (
<BR>NAME   POSITION(01:19) CHAR,
<BR>ADDRESS   POSITION(20:40) VARCHAR,
<BR>ID   POSITION(41:48) INTEGER )
-- EXAMPLE 2
<BR>OPTIONS (SKIP = 10, ERRORS = 5)
<BR>-- Skip the first ten records. Stop if 
<BR>-- errorcount reaches five.
<BR>LOAD DATA
<BR>INFILE 'sample.dat'
<BR>-- import file is named sample.dat
<BR>INTO TABLE TEST1 (
<BR>ID         INTEGER POSITION(1-5),
<BR>ANOTHER_ID INTEGER POSITION(8-15),
<BR>DATE1      POSITION(20:29) DATE 'YYYY-MM-DD',
<BR>DATE2      POSITION(40:49) DATE 'YYYY-MM-DD' NULLIF NULL)</PRE></BLOCKQUOTE>
<P>
<FONT FACE="Arial">Loading Variable-length Records</FONT>
<BLOCKQUOTE>
<P>Examples of the control file when loading data from a variable-length import file:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>-- EXAMPLE 1
<BR>LOAD DATA
<BR>INFILE 'EXAMP2.DAT'
<BR>INTO TABLE SUPPLIERS
<BR>FIELDS TERMINATED BY ','
<BR>(NAME VARCHAR, ADDRESS VARCHAR, ID INTEGER)
-- EXAMPLE 2
<BR>OPTIONS (SKIP=10, ERRORS=5)
<BR>-- Skip the first ten records. Stop if 
<BR>-- errorcount reaches five.
<BR>LOAD 
<BR>DATE 'YYYY-MM-DD HH:NN:SS'
<BR>-- The date format in the import file
<BR>INFILE 'sample.dat'
<BR>-- The import file
<BR>INTO TABLE TEST1
<BR>-- data is inserted into table named TEST1
<BR>FIELDS TERMINATED BY X'2C'
<BR>-- Field terminator is HEX ',' == 2C 
<BR>-- This line could also be:
<BR>-- FIELDS TERMINATED BY ','
<BR>OPTIONALLY ENCLOSED BY '[' AND ')'
<BR>-- Fields may also be enclosed 
<BR>-- with '[' and ')'
<BR>(
<BR>ID INTEGER,
<BR>ANOTHER_ID DECIMAL(2),
<BR>DATE1 DATE(20) DATE 'YYYY-MM-DD HH:NN:SS',
<BR>DATE2 NULLIF NULL
<BR>)
<BR>-- ID is inserted as integer
<BR>-- ANOTHER_ID is a decimal number with 2 
<BR>-- digits.
<BR>-- DATE1 is inserted using the datestring
<BR>-- given above
<BR>-- The default datestring is used for DATE2.
<BR>-- If the column for DATE2 is 'NULL' a NULL is
<BR>-- inserted.</PRE></BLOCKQUOTE>
<P>
<FONT FACE="Arial">Running a Sample Load Using Solload</FONT>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Run a Sample Load Using Solload</B></FONT></H4>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Start your SOLID <I>Server</I>.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Create the table using the sample.sql script and your SOLID <I>SQL Editor.</I>
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Start loading using the following command line:
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<PRE>solload &quot;shmem solid&quot; dba dba delim.ctr </PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>The user name and password are assumed to be 'dba'. To use the fixed length control file, use the following command line:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>solload &quot;shmem solid&quot; dba dba fixed.ctr </PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>The output of a successful loading using delim.ctr will be:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>SOLID Speed Loader v.02.20.0004
(C) Copyright Solid Information Technology Ltd 1992-1997
Load completed successfully, 19 rows loaded.</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>The output of a successful loading using fixed.ctr will be:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>SOLID Speed Loader v.02.20.0004
(C) Copyright Solid Information Technology Ltd 1992-1997
Load completed successfully, 19 rows loaded.</PRE></BLOCKQUOTE>
<P>
<FONT FACE="Arial">Running a Sample Load Using Solloads</FONT>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Run a Sample Load Using Solloads</B></FONT></H4>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Start your SOLID <I>Server</I>.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Create the table using the sample.sql script and your SOLID <I>SQL Editor</I>.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Shut down SOLID <I>Server</I>.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Copy the database SOLID.DB to the directory where the SOLLOADS program exists.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Start loading using the following command line:
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<PRE>solloads dba dba delim.ctr</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>The user name and password are assumed to be 'dba'. To use the fixed length control file, use the following command line:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>solloads dba dba fixed.ctr </PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>The output of a successful loading using delim.ctr will be:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>SOLID Speed Loader v.02.20.0004
(C) Copyright Solid Information Technology Ltd 1992-1997
Load completed successfully, 19 rows loaded.</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>The output of a successful loading using fixed.ctr will be:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>SOLID Speed Loader v.02.20.0004
(C) Copyright Solid Information Technology Ltd 1992-1997
Load completed successfully, 19 rows loaded.</PRE></BLOCKQUOTE>
<P>
<FONT FACE="Arial">Hints to Speed up Loading</FONT>
<BLOCKQUOTE>
<P>The following hints can be used to ensure that loading is done with maximum performance:
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>SOLID<I> SpeedLoader</I> (standalone) is faster than SOLID <I>SpeedLoader</I> (network) because data is loaded directly into the database file, solid.db.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>If the network version is used, it is faster not to load data over the network, i.e., connect locally if possible.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Increasing the number of records committed in one batch speeds up the load. By default, commit is done after each record.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>If the standalone version is used, it is faster to disable logging. Do not use logging with the network version.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<P>To disable logging the LogEnabled parameter needs to be used. The following lines in the solid.ini file will disable logging:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>[Logging]
<BR>LogEnabled=no</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>After the loading has been completed, remember to enable logging again. The following line in the solid.ini file will enable logging:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>[Logging]
<BR>LogEnabled=yes</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. Running the server with logging disabled is strongly discouraged. If logs are not written, no recovery can be made if an error occurs due to power failure, disk error etc.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<A NAME="E10E22"></A>
<P>
<FONT FACE="Arial"><B>SOLID </B><B><I>Export</I></B></FONT>
<BLOCKQUOTE>
<P>SOLID <I>Export</I> is a product for unloading data from a SOLID database to ASCII files. SOLID <I>Export</I> produces both the import file, i.e., the file containing the exported ASCII data, and the control file that specifies the format of the import file. SOLID <I>SpeedLoader</I> can directly use these files to load data into a SOLID database.
</BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. The user name used for performing the export operation must have select rights on the table exported. Otherwise no data is exported.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<P>
<FONT FACE="Arial">Invoking SOLID <I>Export</I><A NAME="I60"></A></FONT>
<BLOCKQUOTE>
<P>SOLID <I>Export</I> is invoked with the command solexp. If you invoke solexp with no arguments, you'll see a summary of the arguments with a brief description. The command line syntax is:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>solexp [options] [servername] &lt;username&gt; &lt;password&gt; &lt;tablename|*&gt;</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>The possible options are<A NAME="I61"></A>
</BLOCKQUOTE>
<BLOCKQUOTE><TABLE>
<TR>
<TD WIDTH=240 VALIGN=top >
<P><B>Option</B>
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E77"></A>
<P>Description</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-c&lt;dir&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E78"></A>
<P>Change working directory</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-e&lt;sql-string&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E79"></A>
<P>Execute SQL string for export</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-f&lt;filename&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E80"></A>
<P>Execute SQL string from file for export</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-h, -?
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E81"></A>
<P>Help = Usage</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-l&lt;filename&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E82"></A>
<P>Write log entries to this file</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-L&lt;filename&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E83"></A>
<P>Append log entries to this file</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-o&lt;filename&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E84"></A>
<P>Write exported data to this file</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-s&lt;schemaname&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E85"></A>
<P>Use only this schema for export</TD></TR>
</TABLE></BLOCKQUOTE>

<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE 1. The symbol * can be used to export all tables with one command. However, it cannot be used as a wildcard.
<BR>NOTE 2. The -tTABLENAME (Export table) option is still supported in order to keep old scripts valid.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<A NAME="E10E23"></A>
<P>
<FONT FACE="Arial"><B>SOLID </B><B><I>Data Dictionary</I></B></FONT>
<BLOCKQUOTE>
<P>SOLID <I>Data Dictionary </I> is a product for retrieving data definition statements from a SOLID database. SOLID <I>Data Dictionary</I> produces an SQL script that contains data definition statements describing the structure of the database. The generated script contains definitions for tables, views, procedures, sequences, and events.
</BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE 1. User and role definitions are not listed for security reasons.
<BR>NOTE 2. The user name used for performing the export operation must have select right on the tables. Otherwise the connection is refused.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<P>
<FONT FACE="Arial">Invoking SOLID <I>Data Dictionary</I><A NAME="I62"></A></FONT>
<BLOCKQUOTE>
<P>SOLID <I>Data Dictionary</I> is invoked with the command soldd. If you invoke soldd with no arguments, you'll see a summary of the arguments with a brief description. The command line syntax is:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>soldd [options] [servername] &lt;username&gt; &lt;password&gt; [tablename]</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>The possible options are<A NAME="I63"></A>:
</BLOCKQUOTE>
<BLOCKQUOTE><TABLE>
<TR>
<TD WIDTH=240 VALIGN=top >
<P><B>Option</B>
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E86"></A>
<P>Description</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-c&lt;dir&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E87"></A>
<P>Change working directory</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-h, -?
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E88"></A>
<P>Help = Usage</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-o&lt;filename&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E89"></A>
<P>Write data definitions to this file</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-O&lt;filename&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E90"></A>
<P>Append data definitions to this file</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-s&lt;schemaname&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E91"></A>
<P>List definitions from this schema only</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-x indexonly
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E92"></A>
<P>List index definitions only</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-x tableonly
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E93"></A>
<P>List table definitions only</TD></TR>
</TABLE></BLOCKQUOTE>

<BLOCKQUOTE>
<P>Example:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>soldd -odatabase.sql &quot;tcp database_server 1313&quot; dbadmin f1q32j4</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE 1. If no table name is given, all definitions are listed to which the user has rights.
<BR>NOTE 2. The -ttablename option is still supported in order to keep old scripts valid. 
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<A NAME="E10E24"></A>
<P>
<FONT FACE="Arial"><B>SOLID </B><B><I>Remote Control</I></B><B> (Teletype)</B></FONT>
<BLOCKQUOTE>
<P>With SOLID R<I>emote Control</I> (Teletype), commands can be given at the command line, command prompt, or by executing a script file that contains the commands.
</BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. The user performing the administration operation must have administrator&#146;s rights, or the connection will be refused.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<P>
<FONT FACE="Arial">Invoking SOLID <I>Remote Control</I> (Teletype)<A NAME="I64"></A><A NAME="I65"></A></FONT>
<BLOCKQUOTE>
<P>SOLID <I>Remote Control</I> (Teletype) is invoked with the command solcon. On Novell Netware, you start SOLID <I>Remote Control</I> (Teletype) with the command load solcon at the command prompt. SOLID <I>Remote Control</I> (Teletype) connects to the first server specified in the Connect parameter in the solid.ini file. If you start SOLID <I>Remote Control</I> (Teletype) with no arguments, you'll be prompted for the database administrator&#146;s user name and password. The command line syntax is:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>solcon [options] [servername] [username password]</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>The possible options are<A NAME="I66"></A>:
</BLOCKQUOTE>
<BLOCKQUOTE><TABLE>
<TR>
<TD WIDTH=240 VALIGN=top >
<P><B>Option</B>
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E94"></A>
<P>Description</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-c&lt;dir&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E95"></A>
<P>Change working directory</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-e&lt;string&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E96"></A>
<P>Execute command string</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-f&lt;filename&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E97"></A>
<P>Execute command string from file</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-h, -?
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E98"></A>
<P>Help = Usage</TD></TR>
</TABLE></BLOCKQUOTE>

<BLOCKQUOTE>
<P>You can give the connection information at the command line to override the connect definition in solid.ini.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Example:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>solcon &quot;spx solid&quot;</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>Also the administrator's user name and password can be given at the command line.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Example:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>solcon &quot;tcp localhost 1313&quot; admin iohi4y</PRE></BLOCKQUOTE>
<P>
<FONT FACE="Arial">Using SOLID <I>Remote Control</I> (Teletype)<A NAME="I67"></A></FONT>
<BLOCKQUOTE>
<P>After the connection to the server has been established, the command prompt appears.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Available commands are described in the following table:
</BLOCKQUOTE>
<BLOCKQUOTE><TABLE>
<TR>
<TD WIDTH=120 VALIGN=top >
<P><B>Command</B>
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E99"></A>
<P>Abbreviation
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E99"></A>
<P>Explanation</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<A NAME="E7E99"></A>
<P>    backup
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E100"></A>
<P>bak
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E100"></A>
<P>Makes a backup of the database. The default backup directory is the one specified in the configuration file. The backup directory may also be given as an argument.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>backuplist
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E101"></A>
<P>bls
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E101"></A>
<P>Displays a status list of last backups.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>close
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E102"></A>
<P>clo
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E102"></A>
<P>Closes server connections; no new connections are allowed.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>errorcode
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E103"></A>
<P>ec
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E103"></A>
<P>Displays a description of an error code. Give the code number as an argument.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>exit
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E104"></A>
<P>ex
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E104"></A>
<P>Exits SOLID <I>Remote Control</I>.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>help
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E105"></A>
<P>?
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E105"></A>
<P>Displays available commands.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>hotstandby
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E106"></A>
<P>hsb
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E106"></A>
<P>Executes a hot standby command.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>makecp
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E107"></A>
<P>mcp
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E107"></A>
<P>Makes a checkpoint.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>messages
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E108"></A>
<P>mes
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E108"></A>
<P>Displays server messages.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>monitor
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E109"></A>
<P>mon
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E109"></A>
<P>Sets server monitoring on and off.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>open
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E110"></A>
<P>ope
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E110"></A>
<P>Opens server connections; new connections are allowed.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>report
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E111"></A>
<P>rep
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E111"></A>
<P>Generates a report of  server info to a file given as an argument.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>shutdown
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E112"></A>
<P>sd
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E112"></A>
<P>Shuts down SOLID <I>Server</I>.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>status
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E113"></A>
<P>sta
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E113"></A>
<P>Displays server statistics.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>throwout
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E114"></A>
<P>to
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E114"></A>
<P>Throws out users from SOLID <I>Server</I>. To throw out a specified user, give the user id as an argument. To throw out all users, use the keyword ALL as an argument.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>userlist
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E115"></A>
<P>ul
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E115"></A>
<P>Displays a list of users.</TD>
</TR>
<TR>
<TD WIDTH=120 VALIGN=top >
<P>version
</TD><TD WIDTH=114 VALIGN=top >
<A NAME="E7E116"></A>
<P>ver
</TD><TD WIDTH=246 VALIGN=top >
<A NAME="E7E116"></A>
<P>Displays server version info.</TD></TR>
</TABLE></BLOCKQUOTE>

<BLOCKQUOTE>
<P>You can execute all commands either using this interface or giving them at the command line with the -e option or in a text file with the 
<BR>-f option. Commands can be given using either the complete command name or its abbreviation.
</BLOCKQUOTE>
<A NAME="E10E25"></A>
<P>
<FONT FACE="Arial"><B> SOLID </B><B><I>SQL Editor</I></B><B> (Teletype)</B></FONT>
<BLOCKQUOTE>
<P>With SOLID <I>SQL Editor</I> (Teletype), statements can be given at the command line, command prompt, or by executing a script file that contains the SQL statements.
</BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. The user performing SQL statements must have appropriate user rights on the corresponding tables, or the connection will be refused.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<P>
<FONT FACE="Arial">Starting SOLID <I>SQL Editor</I> (Teletype)<A NAME="I68"></A></FONT>
<BLOCKQUOTE>
<P>SOLID <I>SQL Editor</I> (Teletype) is started by entering the command solsql. On Novell Netware, you start SOLID <I>SQL Editor</I> (Teletype) with the command load solsql at the command prompt. SOLID <I>SQL Editor</I> (Teletype) connects by default to the first server specified in the Connect parameter in solid.ini file and prompts for a user name and password. The command line syntax is:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>solsql [options] [servername] [username] [password] [filename]</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>The possible options are<A NAME="I69"></A>:
</BLOCKQUOTE>
<BLOCKQUOTE><TABLE>
<TR>
<TD WIDTH=240 VALIGN=top >
<P><B>Option</B>
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E117"></A>
<P>Description</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-a
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E118"></A>
<P>Auto commit every statement</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-c
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E119"></A>
<P>Change working directory</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-e&lt;sql-string &gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E120"></A>
<P>Execute SQL string</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-f&lt;filename&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E121"></A>
<P>Execute SQL string from file</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-h, -?
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E122"></A>
<P>Help = Usage</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-o&lt;filename&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E123"></A>
<P>Write result set to this file</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-O&lt;filename&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E124"></A>
<P>Append result set to this file</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-s&lt;schemaname&gt;
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E125"></A>
<P>Use only this schema</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-t
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E126"></A>
<P>Print execution time per command</TD>
</TR>
<TR>
<TD WIDTH=240 VALIGN=top >
<P>-x onlyresults
</TD><TD WIDTH=240 VALIGN=top >
<A NAME="E7E127"></A>
<P>Print only rows</TD></TR>
</TABLE></BLOCKQUOTE>

<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE.  If user name and password are given as command line arguments also the server name must be given as a command line argument.  Also if the name of the SQL script file is given as a  command line argument (not with the option -f), the server name, user name and password must also be given as command line arguments. 
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<P>
<FONT FACE="Arial">Using SOLID <I>SQL Editor</I> (Teletype)<A NAME="I70"></A></FONT>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>Executing SQL Statements</B></FONT></H4>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>After the connection to the server has been established a command prompt appears. SOLID <I>SQL Editor</I> (Teletype) executes SQL statements terminated by a semicolon.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Example:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>create table testtable (value integer, name varchar);
insert into testtable (value, name) values (31, &#145;Duffy Duck&#146;);
select value, name from testtable;
drop table testtable;</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>Exiting SOLID SQL Editor</B></FONT></H4>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>To exit from SOLID <I>SQL Editor</I> (Teletype) enter the command:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>exit;</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>Executing an SQL Script</B></FONT></H4>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>To execute an SQL script from a file, the name of the script file must be given as a command line parameter:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>solsql server-name user-name password file-name</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<P>All statements in the script must be terminated by a semicolon. SOLID <I>SQL </I><I>Editor</I> (Teletype) exits after all statements in the script file have been executed.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Example:
</BLOCKQUOTE>
<BLOCKQUOTE>
<PRE>solsql &quot;tcp localhost 1313&quot; admin iohe4y tables.sql</PRE></BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. Remember to commit work at the end of the SQL script or before exiting SOLID <I>SQL Editor</I> (Teletype). If an SQL-string is executed with the option -e, commit can only be done using the -a option.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<A NAME="E10E26"></A>
<P>
<FONT FACE="Arial"><B>Tools Sample: Reloading a Database</B></FONT>
<BLOCKQUOTE>
<P>This example demonstrates how a SOLID <I>Server</I> database can be reloaded to a new one. At the same time the use of each SOLID tool is introduced with an example. This reload is a useful procedure since it shrinks the size of the database file solid.db to a minimum.
</BLOCKQUOTE>
<BLOCKQUOTE>
<H4>
<FONT FACE="Arial"><B>To Reload the Database:</B></FONT></H4>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Extract data definitions from the old database.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Extract data from the old database.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Replace the old database with a new one.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Load data definitions into a new database.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Load data into the new database.
</BLOCKQUOTE></UL>
<P>
<FONT FACE="Arial">Walkthrough</FONT>
<BLOCKQUOTE>
<P>In this example the server name is SOLID and the protocol used for connections is Shared Memory. Therefore, the network name is &quot;ShMem SOLID&quot;. The database has been created with the user name &quot;dbadmin&quot; and the password &quot;password&quot;.
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Data definitions are extracted with SOLID <I>Data Dictionary. </I>Use the following command line to extract an SQL-script containing definitions for all tables, views, procedures, sequences, and events. The default for the extracted SQL-file is soldd.sql.
<BR>
<BR>soldd &quot;ShMem SOLID&quot; dbadmin password
<BR>
<BR>With this command all data definitions are listed into one file, soldd.sql (the default name). As mentioned earlier, user and role definitions are not listed for security reasons. If the database contains users or roles, they need to be appended into this file.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>All data is extracted with SOLID <I>Export.</I> The export results in control files (files with the extension .ctr) and data files (files with the extension .dat). The default file name is the same as the exported table name. In 16-bit environments, file names longer than eight letters are concatenated. Use the following command line to extract the control and data files for all tables.
<BR>
<BR>solexp &quot;ShMem SOLID&quot; dbadmin password *
<BR>
<BR>With this command data is exported from all tables. Each table&#146;s data is written to an import file named table_name.dat. A separate control file table_name.ctr is written for each table name.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>A new database can be created to replace the old one by deleting the solid.db and all sol####.log files from the appropriate directories. When SOLID <I>Server</I> is started for the first time after this, a new database is created.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. It is recommended that a backup is created of the old database before it is deleted. This can be done using SOLID <I>Remote Control</I> (Teletype).
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Use the following command line to create a backup using SOLID <I>Remote </I><I>Control</I> (Teletype):
<BR>
<BR>solcon -eBACKUP &quot;ShMem SOLID&quot; dbadmin password
<BR>
<BR>With this command a backup is created. The option -e precedes an administration command.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Load data definitions into the new database. This can be done using SOLID <I>SQL Editor</I> (Teletype). Use the following command line to execute the SQL-script created by SOLID <I>Data Dictionary</I><B><I>.</I></B>
<BR>
<BR>solsql -fSOLDD.SQL &quot;ShMem SOLID&quot; dbadmin password
<BR>
<BR>With this command, data definitions are loaded into the new, empty database. Definitions are retrieved with the option -f from the file soldd.sql. Connection parameters are the same as in the earlier examples.
<BR>
<BR>The previous two steps can be performed together by starting SOLID <I>Server</I> with the following command line. The option -x creates a new database, executes commands from a file, and exits. User name and password are defined as well.
<BR>
<BR>solid -Udbadmin -Ppassword -x execute:soldd.sql
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Load data into the new database. This can be done with either version of SOLID <I>Speedloader.</I> Solload.exe is the network version and solloads.exe the standalone version. In this example, the database directory is C:\Solid. Therefore, using solloads.exe requires changing the working directory if the extracted data is not in the same directory with the database. To load several tables into the database a batch file containing a separate command line for each table is recommended. In Unix-based operating systems and in OS/2, using the wildcard symbol * is possible. Use either of the following command lines to load data into the new database.
<BR>
<BR>solload &quot;ShMem SOLID&quot; dbadmin password table_name.ctr
<BR>
<BR>With this command data for one table is loaded using the network version. The server is online.
<BR>
<BR>solloads -cc:\solid dbadmin password c:\temp\table_name.ctr
<BR>
<BR>With this command data for one table is loaded using the standalone version. The server is shut down. The database file is located in c:\solid\ as instructed with the option -c, and the control file is located in c:\temp\.
</BLOCKQUOTE></UL>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<P>NOTE. No server name is needed with solloads.exe since the server is off-line. SOLID <I>SpeedLoader</I> (network) has the required functionality of a database server embedded.
<HR ALIGN=CENTER>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Batch files that can be used are:
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Shell scripts in Unix environments
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>.com -scripts in VMS
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>.cmd -scripts in OS/2
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>.bat -scripts in DOS, Windows 3.x, 95, and NT
</BLOCKQUOTE></UL>
<A NAME="E7E128"></A>
<P ALIGN=CENTER>
<A HREF="aguide03.htm" TARGET="_self"><IMG SRC="gaguide/graprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Previous Page"></A>
<A HREF="httoc.htm" TARGET="_self"><IMG SRC="gaguide/gratop.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="TOC"></A>
<A HREF="htindex.htm" TARGET="_self"><IMG SRC="gaguide/graindex.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Index"></A>
<A HREF="aguide05.htm" TARGET="_self"><IMG SRC="gaguide/granext.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Next Page"></A>

<center><p><font SIZE=-2>Copyright &copy; 1992-1997 Solid Information Technology Ltd All rights reserved.</font></p></center></BODY></HTML>