Administrator Guide : Administering solidDB® : Starting and stopping servers : Starting solidDB®
  
Starting solidDB®
You can start solidDB® by issuing the command solid [options] at the command prompt, or in Windows environments, using the Start > Programs > solidDB® menu path.
Before you begin
To start solidDB®, a valid license file must be located in your working directory or in the location specified with a SOLIDDIR environment variable.
About this task
This section applies to standard solidDB® only. If you are using solidDB® with shared memory access (SMA) or linked library access (LLA), see the solidDB® Shared Memory Access and Linked Library Access User Guide for instructions on how to start a SMA or LLA server.
Procedure
To start the solidDB® server:
Operating system
Procedure
Linux and UNIX
In the working directory, enter the command
solid [options]
at the command prompt.
When you start the server for the first time, use the command-line option -f to force the server to run in the foreground:
solid -f
Windows
Click the icon labeled Start solidDB® server through the Start > Programs > solidDB® menu path.
In the working directory, enter the command:
solid [options]
at the command prompt.
To start the server to run in the background, enter the command:
start solid
options are:
Option
Description
Examples
-c directory
Changes the working directory.
solid -c /data/solid
-f
Starts the server in foreground.
 
-m
Enables the monitoring facility for tracing SQL statements.
For more details, see Monitoring solidDB®.
 
-n name
Sets the server name.
 
-s install,
name,fullexepath
-c directory
[,autostart]
The Windows version of solidDB® is by default an icon exe version. You can allow Windows to run solidDB® as a service by using the option -s install.
Note After the service is installed, it must be started manually using the Windows Services dialog or command prompt.
The [autostart] parameter sets the Startup Type of the service to Automatic, that is, solidDB® will run automatically as a service when Windows is started. Note, however, that regardless of the [autostart] parameter, the service is not started automatically at the time of install. For the first time, the service has to be started manually in the Windows Services dialog or command prompt.
When the server is running as a service, the server cannot interact with the display and cannot create a new database. The service version writes warning and error messages also to the Windows event log.
solid -s"install,SOLID,
:\SOLID\SOLID.EXE
-cD:\SOLID"
solid -s"install,SOLID, D:\SOLID\SOLID.EXE -cD:\SOLID,autostart"
-s remove,name
Removes a Windows service instance of the solidDB® server.
solid -s"remove,SOLID"
-s start
Specifies that solidDB® starts in a services mode when, for example, solidDB® is created as a service using the Windows sc.exe utility.
In the services mode, solidDB® cannot interact with the display and cannot create a new database.
Note The -s start option is included automatically when using the -s install option.
sc create SOLID binPath= "c:\solidb\bin\solid.exe -cC:\soliddb -sstart"
-U username
Specifies the username for the database that is being created.
See also options -x execute, -x executeandnoexit, and -x exit.
 
-P password
Specifies the password for the database that is being created.
See also options -x execute, -x executeandnoexit, and -x exit.
 
-p
Create a new database with externally authenticated database administrator.
 
-E
Encrypts the database.
An encryption password is mandatory when ‑E is specified. The encryption password is needed to protect the symmetric encryption key which is stored in an unencrypted header page of the database file.
Specify the encryption password using the -x keypwdfile:file_name or -S encryption_password option.
solid -C mycatalog -U admin -P admin123 -E -x keypwdfile:pwd.txt
solid -C mycatalog -U admin -P admin123 -E -S admin456
-S encryption_password
Specifies the database file encryption password.
 
-x assert:s
Disables emergency exit dialog.
 
-x autoconvert
Converts (migrates) the database format from a previous release version to the current release version and starts the server.
 
-x backupserver
Used only in HotStandby setups.
Starts the server in a netcopy listening mode. A server in the netcopy listening mode accepts only netcopy operations from the Primary server.
 
-C catalog
Specifies the database catalog name.
 
-x convert
Converts (migrates) database format to the current format used by solidDB® and starts the server process.
 
-x decrypt -S password
Decrypts the database.
solid -x decrypt -S dba
solid -x decrypt
-x keypwdfile:pwd.txt
-x disableallmessageboxes
Hides all message windows.
 
-x errormsgnostop
Does not wait for user actions on error dialogs.
 
-x execute: file_name
Prompts for the user name and password of the database administrator, creates a new database, executes SQL statements from a file, and exits.
You can also use the options -U and -P to provide the DBA user name and password.
The input file must be encoded with a 7-bit or 8-bit character set, such as ASCII or Latin-1.
solid.exe -x execute:init.sql
solid.exe -x execute:init.sql -Udba -Pdba
-x executeandnoexit: file_name
Prompts for the user name and password of the database administrator, creates a new database, executes SQL statements from a file, but does not exit.
You can also use the options -U and -P to provide the DBA user name and password.
The input file must be encoded with a 7-bit or 8-bit character set, such as ASCII or Latin-1.
solid.exe -x executeandnoexit:init.sql
solid.exe -x executeandnoexit:init.sql -Udba -Pdba
-x exit
Prompts for the user name and password of the database administrator, creates a new database, and exits.
You can also use the options -U and -P to provide the DBA user name and password.
solid.exe -x exit
solid.exe -x exit -Udba -Pdba
-x forcerecovery
Performs a forced roll-forward recovery.
 
-x hide
Hides the server icon.
 
-x ignoreerrors
Ignores index errors.
 
-x ignorecrashed
Ignores log files and reverts to checkpoint.
 
-x inifile:file_name
Specifies the configuration file name, instead of using the default solid.ini file in the working directory.
 
-x infodbfreefactor
Informs about unused pages.
The server exits after performing the task.
See also:-x reorganize.
 
-x keypwdfile: file_name
Reads the database encryption password from a file, instead of command line argument. This way the password cannot be seen by running the UNIX command ps.
 
-x listen:network_name
Sets a listening address.
 
-x migratehsbg2
This command-line switch has two effects:
▪It instructs the server to accept and convert the existing database (the same effect as the -x autoconvert parameter).
▪It enables the new Secondary to communicate with the old Primary by way of the old replication protocol.
This parameter is needed only when upgrading a server that uses HotStandby.
 
-x nologrecovery
Ignores log files during recovery.
 
-x pathprefix:directory
Uses files in the specified directory.
 
-x pwdfile: file_name
Reads the password from a file instead of command line argument. This way the password cannot be seen by running the UNIX command ps.
 
-x recreatejnoconfirm
Creates a new empty database in place of the existing one.
 
-x reorganize
Compacts the database by removing unused pages.
The server exits after performing the task.
 
-x testintegrity
Performs a full database integrity test and exits.
 
-x testblocks
Checks the disk block integrity and produces a report in a ssdebug.out file.
The server exits after performing the task.
 
-x testindex[:size]
Tests database index and exits.
The optional [:size] parameter outputs index size.
 
-x version
Displays the server version and exits.
 
-?, -h
Help.
 
Results
When solidDB® is started, it checks if a database exists. The server first looks for a solid.ini configuration file and reads the value of IndexFile.FileSpec parameter. Then the server checks if there is a database file with the names and paths specified in the IndexFile.FileSpec parameter. If a database file is found, solidDB® automatically opens that database. If no database is found, the server creates a database.
Related tasks
Running solidDB® server as a Windows service
Related reference
solidDB® command-line options
Related information
Configuring solidDB®
Modifying Windows shortcuts for solidDB® server and solidDB® SQL Editor (solsql)
By default the Start solidDB® server and solsql SQL Editor icons in the Start > Programs > solidDB® menu path start programs in the eval_kit\standalone directory. To change the default settings, modify Properties of the shortcuts.
Modifying Start solidDB® server shortcut
By modifying the Properties of the Start solidDB® server shortcut you can specify the working directory, login data and system catalog name, and additional command-line options used when starting solidDB®.
1 Right-click on the Start solidDB® server icon.
2 Select Properties and then the Shortcut tab.
3 To change the login data and catalog name (or other startup options), modify the command-line options given in the Target field:
-C — system catalog name
-P — password
-U — username
For example:
"C:\Program Files\UNICOM\soliddb\soliddb100\bin\solid.exe" -C mycatalog -P mypassword -U myname
See solidDB® command-line options for a list of available solidDB® startup options.
4 To change the working directory, modify the directory path in the Start in field. For example:
"C:\Program Files\UNICOM\soliddb\soliddb100\eval_kit\mytest\"
Modifying solsql SQL Editor shortcut
By modifying Properties of the solsql SQL Editor shortcut you can specify the connection information and the login data for the solidDB® server to which solidDB® SQL Editor (solsql) connects to.
1 Right-click on the solsql SQL Editor icon.
2 Select Properties and then the Shortcut tab.
3 To change the connection information and login data, modify the server name, username, and password given in the Target field. For example:
"C:\Program Files\UNICOM\solidb\soliddb100\bin\solsql.exe" "tcp 2315" myname mypassword
You can also specify startup options in the Target field. See Troubleshooting a problem for a list of available solsql startup options.
See also
Starting and stopping servers