SQL/MP Installation and Management Guide

HP NonStop SQL/MP Installation and Management Guide—523353-004
A-1
A Licensed SQLCI2 Process
A licensed SQLCI2 process (licensed program) can perform privileged operations,
such as deleting or updating rows in catalog tables. Normally only the super ID can
perform these operations because of the potential risk to the database. The super ID
must explicitly license program files before beginning.
These operations are restricted to licensed processes:
•
Creating or dropping a catalog without reference to the CATALOGS table
•
Writing to the SQL catalog tables as if they were user tables (without referring to
the SQL file labels)
If the write request is issued from SQLCI, the SQLCI2 process must be licensed. If the
statement is issued from a program file, the program file must be licensed.
Licensing SQLCI2
You must license the SQLCI2 process if you want to enable it to perform privileged
operations. Running SQLCI2 as the super ID does not pass the SQL license test
automatically.
To license a program, the super ID must run the FUP LICENSE command, naming the
program. This license persists until the super ID explicitly revokes it by executing the
FUP REVOKE command.
To license SQLCI2, do not use the FUP LICENSE command on the
$SYSTEM.SYSTEM.SQLCI2 program. Instead, make a copy of SQLCI2 and use that
copy for privileged operations.
Running SQLCI2 as SUPER.SUPER
For example, suppose that you want a version of the program that can be used only by
the super ID. Suppose that the SQLCI2 program is on $SYSTEM.SYSTEM, and the
system catalog is on the default location of $SYSTEM.SQL.
Enter these commands at the command interpreter prompt:
33> LOGON SUPER.SUPER, password
34> FUP DUP $SYSTEM.SYSTEM.SQLCI2, $SYSTEM.SYSTEM.SQLCI2L
35> FUP SECURE SQLCI2L, "NN--"
36> SQLCOMP /IN SQLCI2L/ CATALOG $SYSTEM.SQL
37> FUP LICENSE SQLCI2L
SQLCI2L is now a licensed version of SQLCI2 and you have secured it for use only by
the super ID.
Caution. These operations can be extremely dangerous to the consistency of the database
and the data dictionary. Only the most extreme situations should require the use of a licensed
SQLCI2. Only the most knowledgeable SQL/MP manager should attempt to correct problems
with a licensed SQLCI2 process.