Professional Documents
Culture Documents
Vel 30 IA
Vel 30 IA
Copyright
Copyright 1999 by Centura Software Corporation. All rights reserved.
Velocis 3.0 Installation and Administration Guide
20-7301-1002
November 1999
Contents
Chapter 1 Introduction
1.1 Velocis Documentation................................................................................................ 1-1
1.1.1 About This Manual................................................................................................. 1-1
1.1.2 Related Velocis Documents ................................................................................... 1-2
1.1.3 Document Conventions ......................................................................................... 1-2
1.2 Other Helpful Resources ............................................................................................. 1-3
Contents i
2.4.3.2 Named Pipes Transport for Windows NT 4.0/2000............................. 2-13
2.4.3.3 TCP/IP Transport for Windows NT 4.0/2000 ...................................... 2-13
2.4.3.4 Local Transport for Windows NT 4.0/2000........................................... 2-13
2.4.4 UNIX Client Platform........................................................................................ 2-13
2.4.4.1 UNIX Platform Requirements ................................................................. 2-13
2.4.4.2 TCP/IP Transport for UNIX.................................................................... 2-14
2.4.4.3 Local Transport for UNIX ........................................................................ 2-14
2.4.4.4 UNIX Domain Sockets Transport for UNIX .......................................... 2-14
Contents iii
6.3.1 Registering a Database Device ......................................................................... 6-10
6.3.1.1 Using Velocis Administrator to Register a Database Device .............. 6-11
6.3.1.2 Using rdsadm to Register a Database Device........................................ 6-12
6.3.2 Changing a Database Device ............................................................................ 6-13
6.3.2.1 Using Velocis Administrator to Change a Database Device ............... 6-13
6.3.2.2 Using rdsadm to Change a Database Device ........................................ 6-13
6.3.3 Deleting a Database Device .............................................................................. 6-14
6.3.3.1 Using Velocis Administrator to Delete a Database Device.................. 6-14
6.3.3.2 Using rdsadm to Delete a Database Device........................................... 6-15
6.4 Configuring and Managing Databases .................................................................... 6-15
6.4.1 Registering a Database ...................................................................................... 6-15
6.4.1.1 Using Velocis Administrator to Register a Database ........................... 6-16
6.4.1.2 Using rdsadm to Register a Database..................................................... 6-18
6.4.2 Initializing a Database ....................................................................................... 6-19
6.4.2.1 Using Velocis Administrator to Initialize a Database .......................... 6-19
6.4.2.2 Using rdsadm to Initialize a Database.................................................... 6-19
6.4.3 Changing a Database ......................................................................................... 6-19
6.4.3.1 Using Velocis Administrator to Change the Location of a Database . 6-20
6.4.3.2 Using Velocis Administrator to Change Global Database Access...... 6-20
6.4.4 Deleting a Database Definition......................................................................... 6-20
6.5 Configuring and Managing Database Users........................................................... 6-21
6.5.1 Controlling User Permissions........................................................................... 6-21
6.5.1.1 Access Levels ............................................................................................. 6-21
6.5.1.2 Permissions ................................................................................................ 6-22
6.5.1.3 Preloaded Examples ................................................................................. 6-23
6.5.1.4 Case in Database User Accounts............................................................. 6-23
6.5.2 Managing User Accounts.................................................................................. 6-23
6.5.2.1 Registering a Database User .................................................................... 6-24
6.5.2.2 Modifying a User Account....................................................................... 6-26
6.5.2.3 Deleting a User Account .......................................................................... 6-27
6.5.3 Managing Database Access .............................................................................. 6-27
6.5.3.1 Setting Up Database Access and Permissions ....................................... 6-27
6.5.3.2 Changing a User’s Database Permissions .............................................. 6-28
6.5.3.3 Removing Database Access ..................................................................... 6-29
6.5.4 Setting Up Velocis SQL Database Access Privileges ..................................... 6-29
6.5.4.1 Using rsql to Set Up Access Privileges to a Velocis SQL Database .... 6-30
6.5.4.2 Using the grant Statement to Assign Database Access Privileges ...... 6-31
6.5.4.3 Using the grant Statement to Assign Command Privileges ................ 6-31
6.5.5 Revoking Velocis SQL Database Access Privileges ....................................... 6-31
6.5.5.1 Using rsql to Delete Access Privileges ................................................... 6-32
6.5.5.2 Using the revoke Statement to Delete Database Access Privileges .... 6-32
6.5.5.3 Using the revoke Statement to Delete Command Privileges .............. 6-33
6.5.6 Setting Up a Permanent Administrator Account........................................... 6-33
Contents v
Appendix A velocis.ini File Parameters
A.1 Velocis Server Parameters ..........................................................................................A-1
A.2 Changing a velocis.ini File Parameter.......................................................................A-1
A.3 [Server] Section Parameters .......................................................................................A-2
A.4 [Engine] Section Parameters ......................................................................................A-3
A.5 [SQL] Section Parameters ...........................................................................................A-8
A.6 [Environment] Section Parameters............................................................................A-9
A.7 BLOB Data Logging .................................................................................................. A-10
Contents vii
Figures
Figure 5-1. Velocis Administrator at Startup....................................................................... 5-7
Figure 5-2. Velocis Administrator Toolbar Buttons............................................................ 5-9
Figure 5-3. rdsadm Opening Menu .................................................................................... 5-10
Figure 6-1. Update VELOCIS.INI File Dialog Box.............................................................. 6-3
Figure 6-2. Database Devices View..................................................................................... 6-11
Figure 6-3. Databases View.................................................................................................. 6-16
Figure 6-4. Install Database Dialog Box ............................................................................. 6-17
Figure 6-5. Accounts View................................................................................................... 6-24
Figure 6-6. New User Accounts Dialog Box ...................................................................... 6-25
Figure 6-7. New Database Access Dialog Box................................................................... 6-28
Figure 6-8. Extensions View ................................................................................................ 6-34
Introduction 1-1
Finally, Appendix B provides the directory structure of the files on the Velocis installation
disk.
Before attempting to install the Velocis software, be sure to read Chapter 2. We also
recommend that you read the first three chapters of the Velocis Database Server User’s
Guide for a descriptive overview of Velocis.
Note: The trademarked name of this product is Velocis Database Server. However, for
ease of reference within the manuals, the simpler form of Velocis is used.
Velocis system components are furnished on a CD. The CD includes a readme.txt file
that contains the release notes for your particular operating environment. Be sure to read
this file carefully. It provides detailed information about:
• Recent changes to the system that are not documented in the current manuals.
• Issues specific to your particular operating system or compiler.
Convention Description
Bold Text Indicates the names of functions, commands, data
structures, statements, databases, utilities, files, etc.
Note that the case distinctions used in the names are
not significant for all operating systems.
Italic Text Represents the names of variables, such as parameters
and command options. Additionally, the Velocis
documents use italics for the names of books.
Introduction 1-3
Chapter 2
About the Velocis Environment
This chapter describes environment and network details for the different platforms
supported by the Velocis Database Server. Section 2.1 provides basic information about
each of the network transports that Velocis can use. Section 2.2 describes the platforms
that support standalone versions of Velocis. Section 2.3 provides detailed operating
system and network transport information about each platform that can host a Velocis
server. Section 2.4 gives similar operating system and network transport details about the
client platforms that can host Velocis.
Note: The underlying architectures of the Velocis platforms do not support running more
than one copy of Velocis (either server or standalone Velocis configurations) at the same
time on the same system catalog or database files. However, the environments can
support more than one server, provided that each has a unique name and interacts with
separate system catalog and database files.
We suggest that you read the particular information in this chapter that concerns the
platforms on which you want to install and administer Velocis. Then proceed to Chapter
3 for standalone Velocis or Velocis server installation instructions, including procedures
for post-installation environment configuration. Chapter 4 presents the same type of
information, but for Velocis client platforms.
The local transport does not use network services; it provides a lightweight
communication facility for use in standalone Velocis installations. This special transport
is marked in Table 2-1 with an asterisk and is described in section 2.2.
The following parameters are used to configure different transports in the velocis.ini file:
Enabled=yes_no
Indicates whether or not the particular transport will be turned on. The value of this
parameter can be yes (the default) or no. Thus, if the configuration section is missing
from the velocis.ini file for a transport, it is enabled. If the transport is turned off,
any attempt to connect to this server from the client applications using this particular
transport will fail. This effectively disables all aliases defined in any connect.ini file
on the client machines that are bound to this server and the transport.
Port=number
Specifies the TCP/IP port number to which the server is bound. You can use this
parameter for configuring the [TCP Configuration] section.
PacketSize=size
Defines the packet size the server uses with the specific protocol. The default packet
size is 4096. This setting can be used for the [TCP Configuration] and [UD
Configuration] sections.
Required=yes_no
Indicates whether this transport must initialize and start correctly for the server to
continue. If the transport cannot initialize and this flag is yes, the server will shut
down. If the transport cannot initialize and this flag is no, the server will continue to
initialize if at least one transport has been initialized correctly. The default for all
transports is yes.
Temp=path
Specifies the path for temporary files used in connections for the UD transport and
for the local transport. This parameter is only available on UNIX. The default path is
/tmp.
Important: With the Service Control Manager, you must register Velocis as a service
either during the Velocis server setup process or by using the instrds utility as instructed
in Chapter 3. This utility places the CATPATH variable in the Windows NT 4.0/2000
Registry for you, and sets the variable to point to the system catalog files. Velocis also
stores other pieces of configuration information in the Registry, including the name by
which the Velocis server is known in the NT domain (limited to eight characters). For
more information on Windows NT 4.0/2000 servers and domain controllers, see your
Windows NT 4.0/2000 system administration manuals.
Note: If needed for setting up the Port parameter, you can use the rpcinfo utility to print
a list of active ports.
For UNIX
1. Local
2. UNIX Domain
3. TCP/IP
The following parameters are used to define aliases bound to different transport
protocols:
Protocol=name
Specifies a name for the protocol. An alias section must contain this parameter. The
protocol value can be a comma-separated list of protocols that are declared in the
same order in which attempted connections are made with the protocols. Valid
values for this parameter are TCP, Named Pipes, UNIX DOMAIN, and Local.
Name=server_name
Specifies a string that represents the name of the running Velocis server. This
parameter is recommended for all aliases except those bound to TCP/IP. Instead, the
TCP/IP-bound aliases should use the combination of Host and Port to locate the
server process. For protocols other than TCP/IP, if a Name parameter is not specified,
the alias name is used as the server name.
Encryption=mode_number
Specifies the encryption mode to use for the connection. This parameter defines
secure connection. If this parameter is missing, a mode of 0 (no encryption) is used.
Note: Instead of offering encryption capabilities, Velocis supplies hooks that the
application developer can use to be certain all messages sent across the connection are
secure. In this case, the number given in the Encryption parameter in the connect.ini file
is passed to the encryption shared library. This allows different connections to use
different modes of encryption.
[misserver]
Protocol=Named Pipes
Name=MIS
Node=ACCOUNTING
Encryption=1
[localserver]
Protocol=Local
Name=RDS
Use the following parameters to configure different transports in the connect.ini file.
Enabled=yes_no
Indicates whether or not the particular transport will be turned on. The value of the
parameter can be yes (the default) or no. Thus, if the configuration section is missing
from the connect.ini file for a transport, it is enabled. If the transport is turned off, all
the alias definitions for this transport are disabled.
PacketSize=size
Specifies the packet size used for the TCP/IP and UNIX Domain protocols. The
default packet size is 4096. It is recommended that the client side PacketSize
parameter match that of the server side.
NamedServices=on_off
Specifies whether name services is available, for the Named Pipes transport only.
The value can be on or off (the default). Turning Named Services on allows a client
to connect to a server of a known name but unknown location on the network. If this
option is enabled on large networks, the connection process can be very slow. This
parameter works on Windows NT 4.0/2000, but not on Windows 95/98.
Sessions=number
Specifies the maximum number of sessions allowed from one client application. It is
Directory Description
\Centura\Velocis The home directory.
\Centura\Velocis\Bin The directory for the rdsdll server device. Contains the
Velocis server file (rds.exe) and the DLLs. Utility program
files are also found in here.
\Centura\Velocis\Catalog The directory for the catdev server device. Contains the
system catalog database files, catalog.* and syscat.*. Also
includes lockcat.fil, dbfix_t.dbd, dbimp_t.d01,
dbimp_t.dbd, dbimp_t.k01, the velocis.ini file, which
contains configuration information for Velocis, and the
change log indicator file (rdm.chi).
\Centura\Velocis\Examples Contains example databases and programs.
\Centura\Velocis\Include Contains header and import files.
\Centura\Velocis\Lib Contains Velocis library files.
\Centura\Velocis\Sqldb The directory for the sqldev server device. Contains the
preloaded example SQL databases sales and invntory.
\Centura\Velocis\Syslog The directory for the sysdev server device. Contains the
change log and checkpoint files.
For example, if your CD-ROM mount point is /cdrom and your platform is Linux,
the command would be as follows:
tar xvf /cdrom/Linux/Server/Lnxt.tar
6. From the Velocis home directory, run the shell script named "install", by executing
the following on the command line:
sh ./install
This script sets file permissions and creates the Velocis environment script files,
rdshome.sh (for the Bourne and Korn shells) and rdshome.csh (for the C shell).
Directory Description
$RDSHOME The root directory of the Velocis software installation tree.
$RDSHOME/bin Contains Velocis binaries (including utilities and the server,
rds) and shared libraries.
$RDSHOME/catalog The directory for the catdev server device. Contains the
system catalog database files, catalog.* and syscat.*. Also
includes the velocis.ini file, which specifies configuration
information for Velocis. After the server is started for the
first time, this directory will include the change log indicator
file (rdm.chi) and the backup indicator log file (rdm.bil).
$RDSHOME/examples Contains example source code and databases.
$RDSHOME/include Contains header files.
$RDSHOME/Setoolkt Contains the Server Extension Toolkit source files.
$RDSHOME/sqldb The directory for the sqldev server device. Contains the
preloaded example SQL databases, sales and invntory.
$RDSHOME/syslog The directory for the sysdev server device. Contains the
change log files and, after the server is started for the first
time, the checkpoint image file (rdm.chk).
Note: The Velocis server will also use an RDS.log file, which will be created in the
directory from which you launch the server. This file is used to store server informational
and error messages, which are also printed to the screen when Velocis is run directly
from a command line.
Shell Command
Bourne or Korn shell . ./rdshome.sh
C shell source ./rdshome.csh
For example, if your CD-ROM mount point is /cdrom and your platform is Intel
Linux 6.0 kernel 2.222.9, the command would be
tar xvf /cdrom/Linux/Client/Lnxtcli.tar
6. From the Velocis home directory, run the shell script named "install", by executing
the following on the command line:
sh ./install
This script sets file permissions and creates the Velocis environment script files,
rdshome.sh (for the Bourne and Korn shells) and rdshome.csh (for the C shell).
Shell Command
Bourne or Korn shell . ./rdshome.sh
C shell source ./rdshome.csh
If you do not specify a name when starting the server, Velocis uses "Velocis" as the
default server name.
The -d option instructs the server to run in background mode (the daemon mode).
The -p options set the priority of the background process, normal (-pn), high (-ph) or
idle (-pi). Normal priority is the default setting. This option takes effect only if -d is
specified.
Note: If the -d option is specified, the server remains running in the background after the
current Windows 95/98 user logs out.
The server displays its startup routine in the DOS window, including a list of the
transports on which the server is listening. When the server display indicates "Ready"
near the bottom of the screen, the server is operable and the startup procedure is finished.
During operation, the server displays messages reflecting logins, logouts, and other
server events.
If the -d option is specified, a copy of the server is launched in the background. The
original does not exit until the copy is fully initialized and is listening on the configured
transports. When the program returns to the DOS prompt, the background server is
completely up and running.
Proceed to section 5.2 to learn about accessing the Velocis Administrator and rdsadm
utilities, which are the primary tools for configuring and managing a Velocis database
system.
If your server display does not indicate "Ready," the server has failed to enter the Ready
state and is not operable. For diagnosis and suggested solutions, see Chapter 7, "Velocis
Maintenance."
If you do not specify a name when starting the server, Velocis uses "Velocis" as the
default server name.
Option Description
Automatic The server starts automatically when the server computer boots.
Manual The user starts the server.
Disabled No startup is available.
If you do not specify a name when starting the server, Velocis uses "Velocis" as the
default server name.
The optional -d switch starts the server as a daemon.
The server displays its startup routine, including the list of transports on which the server
is listening. When the server display indicates "Ready" near the bottom of the screen, the
server is operable and the startup procedure is finished. During operation, the server
displays messages reflecting logins, logouts, and other server events.
If the -d option is specified, a copy of the server is launched in the background. The
original does not exit until the copy is fully initialized and is listening on the configured
transports. When the program returns to the shell prompt, the background server is
completely up and running. In daemon mode, the server has no console. Therefore, the
server events are only registered in RDS.log, which is created in the current working
directory when RDS is started.
Proceed to section 5.2 to learn about accessing the Velocis Administrator and rdsadm
utilities, which are the primary tools for configuring and managing a Velocis database
system.
If your server display does not indicate "Ready", the server has failed to enter the Ready
state and is not operable. For diagnosis and suggested solutions, see Chapter 7, "Velocis
Maintenance."
The opening Velocis Administrator window displays a menu bar and a toolbar at the top
of the window. Until you have logged into a server, only the Login to Server button (at
the left end of the toolbar) and the Help button (at the right end) are active. (For more
information about the toolbar, see section 5.2.1.3.) To activate the toolbar buttons and to
gain access to all the Velocis Administrator views and dialog boxes, you must log into a
server.
If you want to look at more than one view at the same time, you can open a new window
(using the Window menu) and then display another view in the second window.
2. At the Enter Centura Server name prompt, type the connection name and press
<Enter>.
The connection name is the server name or alias defined in the connect.ini file. See
Chapter 2, section 2.4.1.1 for information on defining aliases.
3. At the Enter your userid prompt, type the name of your user account and press
<Enter>.
(If you are logging into a server for the first time, after installing the software, the
default userid is "admin".)
4. At the Enter your password prompt, type your password and press <Enter>.
(If you are logging into a server for the first time, and used the default userid
"admin," the default password is "secret".)
After a brief pause, Velocis displays the message, "Successful login," and the opening
menu, shown in Figure 5-3.
1. User
2. Device
3. Database
4. Configuration
5. Show
6. Extension Modules
7. Hot Backup
8. Shutdown Server
9. Exit
Enter selection (1-9):
Instructions for using rdsadm to configure your database system are provided in Chapter
6, "Server Configuration."
To close rdsadm:
At the Enter selection prompt, type the number of the Exit option (9) and press
<Enter>.
Available Aliases
=================
tcpserver (Encryption: off):
1. Protocol: TCP/IP
Host: 195.211.252.12, Port: 2000
localserver (Encryption: off):
1. Protocol: Local
Server: RDS
npserver (Encryption: off):
1. Protocol: Named Pipes
Name: RDS, Node: backbone
all (Encryption: 2):
1. Protocol: Local
Name: RDS
2. Protocol: Named Pipes
Name: RDS, Node: backbone
3. Protocol: TCP/IP
Host: 195.211.252.12, Port: 2000
6. Call vping using different aliases. This will test your connectivity to the newly
installed Velocis server using different transports.
7. The vping utility tests the physical and logical connections between the client and
the server. If everything is working properly, you should see a response similar to
the following example.
[1] 18029 sent 18029 received
[2] 2953 sent 2953 received
[3] 26079 sent 26079 received
[4] 30719 sent 30719 received
[5] 64113 sent 64113 received
[6] 21410 sent 21410 received
[7] 61346 sent 61346 received
[8] 50764 sent 50764 received
[9] 58221 sent 58221 received
[10] 11057 sent 11057 received
If vping finds that a connection is not operable, it displays the message, "Error:
NCP_RC_SERVER unavailable," with suggestions for corrective action.
Note: If your account does not have the administrative rights on the server, Shutdown is
disabled (displayed in gray) on the server menu.
2. At the Enter Centura Server name prompt, type the connection name and press
<Enter>.
The connection name is the server name or an alias defined in the connect.ini file.
See Chapter 2, section 2.4.1.1, for information on defining aliases.
3. At the Enter your userid prompt, type the name of an administrator account and
press <Enter>.
4. At the Enter your password prompt, type your administrator password and press
<Enter>.
5. At the Enter selection prompt, type 8 (for Shutdown server) and press <Enter>.
The server starts the shutdown process.
Note: If your account does not have the administrative rights on the server, an error
message is displayed.
5.4.3.2 Shutting Down from the Service Control Manager (Windows NT 4.0/2000
Only)
Note: If the server was started as a daemon, you can only use the kill command to shut
down. Using rdsadm to shut down (described in section 5.4.2) works both with the
daemon and the regular server process.
Any clients active at shutdown receive an error message the next time the application
calls the server.
You can use the Velocis Administrator or rdsadm utilities, described in Chapter 5, section
5.2, to perform most of the configuration procedures provided in this chapter.
Alternatively, you can create an administrative application.
Table 6-2 describes the parts of the Update VELOCIS.INI File dialog box. Note that the
dialog box refers to parameters as entries.
Table 6-2. Update VELOCIS.INI File Dialog Box Elements
Note: You must shut down and restart the server because Velocis allocates resources for
each client during startup.
Note: You must shut down and restart the server because Velocis allocates resources for
each client during startup.
Caution: Back up the system catalog files occasionally. Remember that they change
when you register server objects, etc.
Important: To locate a Velocis file, you must specify its associated database device.
Therefore, you must register a database device before attempting to register any other
server object that uses it. Each database device definition must have a unique path. No
two database devices should point to the same physical directory, even if the paths are
different (for example, one fully qualified and one relative).
Database file names do not need to be unique, except that within one database device,
unique physical file names are required. The number of database devices you define
depends upon your particular needs. The minimum is one database device, for which all
system files are located in the same directory.
Velocis places no restrictions regarding the location of system files, as long as the server
can transparently access the files. Generally, it is best for organizational purposes to
locate related files together. For example, you also can use one database device to locate
all data and key files for one database. You can also locate individual files with different
database devices. You may be able to improve the performance of your Velocis system
by placing files in different database devices, to take advantage of the concurrency of
multiple disk drives.
Note: You cannot place the Velocis \Catalog and \Syslog directories on a CD-ROM
device.
Note: If any directories in the path to the database device do not yet exist, you must
create them before you enter the path. Velocis Administrator rejects any attempt to use a
directory that does not exist.
Caution: Be careful about mapping a database device to a network drive. Using such a
drive can leave the server vulnerable to network problems (but no database corruption) if
the network connection to system files goes down. Additionally, using a network drive
for a database device can compromise system security because network drives can be
publicly accessed. A final reason for not using a network drive is that some network file
systems do not support write-through capabilities, which Velocis needs to guarantee
recovery in case of a system crash.
Note: If any directories in the path to the database device do not yet exist, you must
create them before you enter the path. Velocis Administrator rejects any attempt to use a
directory that does not exist.
Caution: Be careful about mapping a database device to a network drive. Using such a
drive can leave the server vulnerable to network problems (but no database corruption) if
the network connection to system files goes down. Additionally, using a network drive
for a database device can compromise system security because network drives can be
publicly accessed. A final reason for not using a network drive is that some network file
systems do not support write-through capabilities, which Velocis needs to guarantee
recovery in case of a system crash.
The Databases view window contains four separate areas, each displaying a list and one
or more command buttons. When configuring and managing databases, you use the
command buttons in the Databases area of the window.
To register a database:
1. In the Databases area, click New.
The Install Database dialog box appears.
To initialize a database:
1. In the Databases area, select the name of the database you want to initialize and click
Init.
The Velocis Administrator message box appears with the following message: "This
will initialize all the data and key files. Are you sure?"
2. Click OK.
6.5.1.2 Permissions
Table 6-7 describes the database permissions available to users of Velocis databases:
Table 6-8 summarizes the permissions available to normal users and to users with
administrator privilege level.
3. In the Name box, type the name of the user you want to register.
A name can be any alphanumeric string, up to 14 characters long. User account
names are case-sensitive.
4. In the Password box, type a password for this user.
If this user will have administrator privileges, you must supply a password. If this is
a normal user, a password is optional. A password can be any alphanumeric string
up to seven characters long. Passwords are case-sensitive.
5. In the Home Device list box, select a home database device for this user.
Velocis will use this database device to locate databases that the client creates
through the database schema.
6. If you want this user to have administrator-privilege-level access, click the Admin
Privilege Level box. If you do not check this box, the user has normal access
privileges.
7. Click OK.
Note: Velocis provides an alternative method for authorizing user access to a database
that may be more convenient to use if you are adding a new database to an already
configured and operating Velocis server. That method allows you to access a dialog box
from the Databases view window and to select those users you want to have access to the
database from a list of the currently registered users. For information, see section 6.4.1.1.
3. In the Database Name list box, select the name of the database you want the user to
access.
4. If you want the user to have more than just Read permission for the database, click
the appropriate check boxes: Insert, Update, or Delete.
(Note that Read access permission is automatically checked for any user granted
database access.)
5. Click OK.
Caution: A user who issues a Velocis SQL statement for which access privileges have not
been granted receives an access rights violation error message (errACCESS) from Velocis.
See Chapter 18 of the Velocis Reference Manual for a description of this message.
3. To find all security statements issued on the database, use a query similar to the
following example, which is based on the sales sample database.
select syslookup.name, user_name, txtln
from syslookup, sysseclog, systext
where syslookup.lookup_addr = sysseclog.obj_addr
and sysseclog.log_addr = systext.log_addr
and syslookup.qual_name = "SALES"
4. For each user, use the grant statement to assign database access and command
privileges as required. For details, see sections 6.5.4.2 and 6.5.4.3.
5. Exit rsql by entering .q at the prompt.
If you issue a grant command while a user is logged into Velocis, the user will have to log
out and then log in again in order to use the new permissions.
The following example illustrates how you can use a view to restrict access to a portion of
a database table.
create view skk_customers as
select * from customer where sale_id = "SKK"
with check option;
The next example restricts the user Jack to issuing select, update, and create view
statements.
grant commands create view, update to Jack;
3. To find all security statements issued on the database, use a query similar to the
following example, which is based on the sales sample database.
select syslookup.name, user_name, txtln
from syslookup, sysseclog, systext
where syslookup.lookup_addr = sysseclog.obj_addr
and sysseclog.log_addr = systext.log_addr
and syslookup.qual_name = "SALES"
4. For each user whose privileges require deletion, use the revoke statement as
described in sections 6.5.5.2 and 6.5.5.3.
5. Exit rsql by entering .q at the prompt.
If you issue a revoke command while a user is logged into Velocis, ask the user to log out
and then log in again in order to apply the changed permissions.
The next example shows an rsql script that automatically drops the home_sales view
when user Martha’s access privilege on the salesperson table is revoked.
You may check a specific database at any time by listing it on the command line:
dbcheck -a database_name
The dbcheck utility places the server into hot backup mode so the database files will not
change during the consistency check.
Caution: Since backup is manual, Velocis has no way of knowing whether you have
actually backed up every file. Therefore, you must take care to back up all files. If you
miss a file, subsequent roll forward recovery will fail.
3. Select 1 (Begin Hot Backup Mode). The server system log displays the message "Hot
backup mode started -- N bytes allocated", where N varies in proportion to the
number of files managed by your server.
4. Archive the server databases using the physical backup procedures that you
normally use. You might copy the database files to another directory or to another
database device. Alternatively, you might use tape or other media to archive the
database and change log files.
5. With the backup complete, end the hot backup mode by selecting 7 from the main
menu, and then 2 (End Hot Backup Mode). The server system log displays the
message "Hot backup mode ended".
6. Select 3 (Flush Hot File) from the Backup menu, at any time following the End Hot
Backup, to migrate all remaining hot database pages from the hot file to the database
files. It is not necessary to flush the hot file. Velocis migrates the hot pages to the
database files as they are referenced with little performance impact.
7. When you are ready to exit from rdsadm, select 9 (Exit) at the main menu command
prompt.
Caution: Since backup is manual, Velocis has no way of knowing whether you have
actually backed up every file. Therefore you must take care to back up all files. If you
miss a file, subsequent roll forward recovery will fail.
Caution: If you choose not to perform a roll forward operation immediately after
restoring the server backup, you will not be able to perform roll forward recovery later
without complete restoring the backup again.
Note: For less severe errors, instead of making a controlled shutdown, the server
displays an error message.
When you see a diagnostic error message on the server console, you should note the
information displayed. You can then attempt to correct the error by using the diagnostic
guide and corrective procedures presented below.
Installation Faults
The server indicates this Velocis does not recognize the Update the Velocis search
message: specified name. path. See section 7.4.3.4.
"The name specified is not
recognized as an internal or
external command, operable
program, or batch file".
7.4.3.1 Verifying that the Utility Can Run (Windows 95/98, Windows NT 4.0/2000)
1. Check whether the location of the Velocis DLLs is reflected in the PATH
environment variable.
2. Verify that CATPATH points to the Velocis catalog directory and PATH points to
the Velocis DLL and EXE files.
3. If you do change an environment variable, shut down Velocis and restart it as
described in Chapter 5.
Note: If you installed your Velocis DLLs to your Windows system directory during
setup, use that as your DLL path when running instodbc.
4. If you do change the environment variable, shut down Velocis and restart it as
described in Chapter 5.
This creates two batch files called rdshome.csh (for the C shell) and rdshome.sh (for the
Bourne and related shells). If you are using the C shell, run the following command:
source ./rdshome.csh
If these do not set your environment correctly, you need to set your environment
manually as shown below.
1. If you are using the Bourne shell for AIX 4.3, locate the rdshome.sh script file and set
the LIBPATH variable as follows.
LIBPATH=/velocis/bin; export LIBPATH
If you are using the C shell for AIX 4.3, locate the rdshome.csh script file and set
LIBPATH.
setenv LIBPATH /velocis/bin
If you are using the Bourne shell for HP-UX 11, locate the rdshome.sh script file and
set the SHLIB_PATH variable.
SHLIB_PATH=/velocis/bin; export SHLIB_PATH
If you are using the C shell for HP-UX 11, locate the rdshome.csh script file and set
SHLIB_PATH.
setenv SHLIB_PATH /velocis/bin
If you are using the Bourne shell for UnixWare 7, Sparc Solaris, Intel Solaris, Linux,
or BSDI, locate the rdshome.sh script file and set the LD_LIBRARY_PATH variable.
LD_LIBRARY_PATH=/velocis/bin; export LD_LIBRARY_PATH
If you are using the C shell for UnixWare , Sparc Solaris, Intel Solaris, Linux, or
BSDI, locate the rdshome.csh script file and set LD_LIBRARY_PATH.
setenv LD_LIBRARY_PATH /velocis/bin
2. Ensure that the UDP module exists in the directory referenced by the associated
database device.
3. Ensure that the server environment includes paths to all modules on which the UDP
module depends.
The result set lists registered functions and the devices that contain the DLLs.
2. Ensure that the database device mentioned in the create function statement contains
the UDF.
3. Ensure that the server environment includes paths to all modules on which the UDF
module depends.
Note: You can change Velocis parameters after the server starts, but only before you
open a database.
In addition, the velocis.ini file contains parameters for network transports. For
information about platform-specific parameters, see the readme.txt file.
Parameters are specified in the following format:
<parameter name>=<value>.
In a parameter name, case is not significant.
Parameter Description
CTRL_BREAK_EVENT If set to 1, specifies that the window running the server
is to give Velocis a shutdown signal if the Service
Control Manager issues a stop command. If this
Windows NT-specific parameter is set to 0, the server is
killed.
CTRL_C_EVENT If set to 1, specifies that the window running the server
is to issue a shutdown signal upon entry of <Ctrl+C>
from the login window. If this Windows NT-specific
parameter is set to 0, the server is killed.
CTRL_CLOSE_EVENT If set to 1, specifies that the window running the server
is to give Velocis a shutdown signal when an application
is closed. If this Windows NT-specific parameter is set
to 0, the server is killed.
CTRL_LOGOFF_EVENT If set to 1, specifies that the window running the server
is to issue a shutdown signal when the client logs out of
the server. If this Windows NT-specific parameter is set
to 0, the server is killed.
CTRL_SHUTDOWN_EVENT If set to 1, specifies that the window running the server
is to issue a shutdown signal upon server shutdown. If
this Windows NT-specific parameter is set to 0, the
server is killed.
NumRPCThreads Specifies the number of worker threads the RPC system
should start up when it is initialized. The default is 16.
This is indicates the maximum number of remote client
requests that can be handled simultaneously. Other
request will be queued until one of the threads finishes
its work and is available to work for another client.
Parameter Description
Archiving Specifies 1 (default) if the server archives inactive
change log files, and 0 if it deletes the files when they are
cycled. If you want to perform roll forward recovery, set
this parameter to 1.
AsyncTransactions Specifies 0 (default) if the server commits transactions
immediately (before the d_trend or SQLCommit
function returns), and 1 if it delays them. Every
transaction commit requires at least one file write. The
default value of 0 forces the server to flush a transaction
end marker to the change log file, making transaction
changes permanent. A value of 1 places the transaction
in the internal change log buffer until the buffer
overflows, possibly committing dozens of transactions at
once with one file write.
Parameter Description
ColStats Specifies the state of column statistics. A value of 1 (default)
indicates that the SQL module maintains maximum and minimum
values for every column for use by the Velocis internal SQL
optimizer. A value of 0 turns off column statistics, saving server
memory.
CurrSymb Specifies the system currency symbol (default "$").
DateFormat Specifies the system date constant format (default 2, SQL standard):
1 MM-DD-YYYY
2 YYYY-MM-DD
3 DD-MM-YYYY
DateSep Specifies the system date separator character (default "-").
DecSymb Specifies the system decimal point symbol (default ".").
HisPrec Specifies the granularity of the update stats index file distribution
histogram. The default is 25 (meaning that counts are kept for each
25 percent increment). Finer granularity consumes more server
memory.
LockTime Specifies the wait time, in seconds, before a read lock times out
(default 30).
MaxDBs Specifies the size of the open database and open instance caches in
memory (default 16).
MaxEdges Specifies the size of the edge cache in memory (default 256).
MaxPrecision Specifies the maximum decimal precision (default 32).
MaxProcs Specifies the maximum number of UDPs that Velocis can cache
(default 24).
MaxScale Sets the maximum specifiable decimal scale (default 16).
MaxString Specifies the maximum length of a string literal (default 256).
Parameter Description
SQLDebug Turns on the level of SQL debug information. This is a bit map
which can be any combination of the following values:
1 Show compiled statements
2 Show expression tree
4 Show optimizer tables
8 Show execution plan
If this is non-zero, the debug output for each SQL statement is
written to a debug.xxx file, where xxx starts at 000 and increments
for each statement.
The "default" options indicate the BLOB data logging option when d_bloblog is not
called. Note that all d_blob calls are logged. The logging option only indicates whether
the BLOB data itself is logged. Thus, the BLOB page allocations and BLOB structure
changes are always logged.
B.3.1 Aliases
Each alias can have multiple parameters to describe how to find the server associated
with that alias. Table B-1 describes the alias parameters.