ACTIVATE DATABASE command
Activates the specified database and starts up all necessary
database services so that the database is available for connection
and use by any application.
ADD CONTACT command
Adds a contact to the contact list which can
be either defined locally on the system or in a global list. Contacts
are users to whom processes such as the Scheduler and Health Monitor
send messages.
ADD CONTACTGROUP command
Adds a new contact group to the list of groups
defined on the local system. A contact group is a list of users and
groups to whom monitoring processes such as the Scheduler and Health
Monitor can send messages.
ADD XMLSCHEMA DOCUMENT command
Adds one or more XML schema documents to an existing but
incomplete XML schema before completing registration.
ARCHIVE LOG command
Closes and truncates the active log file for a recoverable
database.
ATTACH command
Enables an application to specify the instance at which
instance-level commands (CREATE DATABASE and FORCE APPLICATION, for example) are to be executed. This
instance can be the current instance, another instance on the same
workstation, or an instance on a remote workstation.
AUTOCONFIGURE command
Calculates and displays initial values for
the buffer pool size, database configuration and database manager
configuration parameters, with the option of applying these reported
values.
BACKUP DATABASE command
Creates a backup copy of a database or a table space. A backup of your DB2® database and related stored data should be created to prevent data loss in the event of a database service outage.
BIND command
Invokes the bind utility, which prepares SQL statements
stored in the bind file generated by the precompiler, and creates
a package that is stored in the database.
CATALOG DATABASE command
Stores
database location information in the system
database directory.
The database can be located either on the local workstation or on
a remote database partition server. The CATALOG DATABASE command
can also be used to recatalog uncataloged databases, or maintain multiple
aliases for one database, regardless of database location
CATALOG DCS DATABASE command
Stores information about remote host or System i® databases in the Database
Connection Services (DCS) directory.
CATALOG LDAP NODE command
Catalogs a new node entry in Lightweight Directory Access
Protocol (LDAP).
CATALOG LOCAL NODE command
Creates a local alias for an instance that resides on the
same machine. A local node should be cataloged when there is more
than one instance on the same workstation to be accessed from the
user's client. Interprocess Communications (IPC) is used to access
the local node.
CATALOG NAMED PIPE NODE command
Adds a named pipe node entry to the node directory. The
named pipe is used to access the remote node.
CATALOG TCPIP/TCPIP4/TCPIP6 NODE command
Adds a Transmission Control Protocol/Internet Protocol
(TCP/IP) database partition server entry to the node directory. The
TCP/IP communications protocol is used to access the remote database
partition server. The CATALOG TCPIP/TCPIP4/TCPIP6 NODE command
is run on a client.
CHANGE DATABASE COMMENT command
Changes a database comment in the system
database directory or the local database
directory. New comment text can be substituted for text currently
associated with a comment.
CHANGE ISOLATION LEVEL command
Changes the way that DB2 isolates data from other processes while a database is
being accessed.
COMPLETE XMLSCHEMA command
Completes the process of registering an XML schema in the
XML schema repository (XSR).
CREATE DATABASE command
Initializes a new database with an optional user-defined
collating sequence, creates the three initial table spaces, creates
the system tables, and allocates the recovery log file. When you initialize
a new database, the AUTOCONFIGURE command is issued
by default.
CREATE TOOLS CATALOG command
Creates the DB2 tools catalog tables in a new or existing
database. The tools catalog contains information about the administrative
tasks that are available to you.
DECOMPOSE XML DOCUMENT command
Invokes a stored procedure to decompose a single XML document
using a registered and decomposition-enabled XML schema.
DECOMPOSE XML DOCUMENTS command
Decomposes XML documents stored in a database column. The
data from the XML documents is stored in columns of relational tables
based on annotations specified in an XML schema.
DEREGISTER command
Deregisters the DB2 server from the network directory server.
DESCRIBE command
Displays
metadata about the columns, indexes, and data partitions of tables
or views. This command can also display metadata about the output
of SELECT, CALL, or XQuery statements.
DETACH command
Removes the logical DBMS instance attachment, and terminates
the physical communication connection if there are no other logical
connections using this layer.
DROP CONTACT command
Removes a contact from the list of contacts
defined on the local system. A contact is a user to whom the Scheduler
and Health Monitor send messages. The setting of the Database Administration
Server (DAS) contact_host configuration parameter
determines whether the list is local or global.
DROP CONTACTGROUP command
Removes a contact group from the list of contacts
defined on the local system. A contact group contains a list of users
to whom the Scheduler and Health Monitor send messages. The setting
of the Database Administration Server (DAS) contact_host configuration
parameter determines whether the list is local or global.
DROP DATABASE command
Deletes the database contents and log files for the database,
uncatalogs the database, and deletes the database subdirectory.
DROP DBPARTITIONNUM VERIFY command
Verifies if a database partition exists in the database
partition groups of any databases, and if an event monitor is defined
on the database partition. This command should be used before dropping
a database partition from a partitioned database environment.
DROP TOOLS CATALOG command
Drops the DB2 tools
catalog tables for the specified catalog in the given database.
ECHO command
Permits the user to write character strings to standard
output.
EDIT command
Launches a user-specified editor with a specified command
for editing. When the user finishes editing, saves the contents of
the editor and exits the editor, permits the user to execute the command
in CLP interactive mode.
EXPORT command
Exports data from a database to one of several
external file formats. The user specifies the data to be exported
by supplying an SQL SELECT statement, or by providing hierarchical
information for typed tables.
FORCE APPLICATION command
Forces local or remote users or applications
off the system to allow for maintenance on a server.
GET ADMIN CONFIGURATION command
Returns the values of individual DB2 Administration Server (DAS) configuration
parameter values on the administration node of the system. The DAS
is a special administrative tool that enables remote administration
of DB2 servers.
GET CONTACTGROUP command
Returns the contacts included in a single contact group
that is defined on the local system. A contact is a user to whom the
Scheduler and Health Monitor send messages.
GET CONTACTGROUPS command
Provides a list of contact groups, which can be either
defined locally on the system or in a global list. A contact group
is a list of addresses to which monitoring processes such as the Scheduler
and Health Monitor can send messages.
GET CONTACTS command
Returns the list of contacts defined on the local system.
Contacts are users to whom the monitoring processes such as the Scheduler
and Health Monitor send notifications or messages.
GET DATABASE MANAGER MONITOR SWITCHES command
Displays
the status of the database system monitor switches that are currently
active. Monitor switches instruct the database manager to collect
database activity information.
GET DESCRIPTION FOR HEALTH INDICATOR command
Returns a description for the specified health indicator.
A Health Indicator measures the healthiness of a particular state,
capacity, or behavior of the database system. The state defines whether
or not the database object or resource is operating normally.
GET HEALTH NOTIFICATION CONTACT LIST command
Returns the list of contacts and contact groups that are
notified about the health of an instance. A contact list consists
of email addresses or pager Internet addresses of individuals who
are to be notified when non-normal health conditions are present for
an instance or any of its database objects.
GET HEALTH SNAPSHOT command
Retrieves the health status information for the database
manager and its databases. The information returned represents a
snapshot of the health state at the time the command was issued.
GET MONITOR SWITCHES command
Displays
the status of the database system monitor switches for the current
session. Monitor switches instruct the database manager to collect
database activity information.
GET RECOMMENDATIONS FOR HEALTH INDICATOR command
Returns descriptions of recommendations
for improving the health of the aspect of the database system that
is monitored by the specified health indicator.
GET ROUTINE command
Retrieves a routine SQL Archive (SAR) file for a specified
SQL routine.
GET SNAPSHOT command
Collects status information and formats the
output. The information that is returned is a snapshot of
the database
manager operational
status at the time that you issued the command.
HELP command
Permits the user to invoke help from the Information Center.
HISTORY command
Displays the history of commands run within a CLP interactive
mode session.
IMPORT command
Inserts data from an external file with a supported
file format into a table, hierarchy, view or nickname. LOAD is
a faster alternative, but the load utility does not support loading
data at the hierarchy level.
INGEST command
Ingests data from an input file or pipe into a DB2 table. The INGEST command provides the ability to move data into DB2 tables with no impact to running applications.
INGEST GET STATS command
Displays statistics about one or more INGEST commands that are being run by the authorization ID that is connected
to the database. The ingest utility maintains statistics for a maximum
of 128 ingest jobs running at a time.
INGEST LIST command
Lists basic information about INGEST commands that are being run by the authorization ID that is connected
to the database. The ingest utility maintains statistics for a maximum
of 128 ingest jobs running at a time.
INGEST SET command
Sets a configuration parameter for subsequent INGEST commands
in the current CLP session.
INITIALIZE TAPE command
Initializes tapes for backup and restore operations
to streaming tape devices. This command is only supported on Windows operating systems.
INSPECT command
Inspects database for architectural integrity, checking
the pages of the database for page consistency. The INSPECT command
checks that the structures of table objects and structures of table
spaces are valid. Cross object validation conducts an online index
to data consistency check.
LIST ACTIVE DATABASES command
Displays a subset of the information listed by the GET SNAPSHOT FOR ALL DATABASES command. An active database
is available for connection and use by any application.
LIST APPLICATIONS command
Displays to standard output the application program name,
authorization ID (user name), application handle, application ID,
and database name of all active database applications. This command
can also optionally display an application's sequence number, status,
status change time, and database path.
LIST COMMAND OPTIONS command
Lists the current settings for the environment variables: DB2BQTIME, DB2DQTRY, DB2RQTIME, DB2IQTIME, DB2OPTIONS.
LIST DATABASE DIRECTORY command
Lists the contents of the system
database directory. If a path is specified, the contents of the local database
directory are listed.
LIST DCS APPLICATIONS command
Displays to standard output information about applications
that are connected to host databases via DB2 Connect™ Enterprise Edition.
LIST DRDA INDOUBT TRANSACTIONS command
Provides a list of transactions that are indoubt between DRDA® requesters and DRDA servers. If DRDA commit protocols are being used, lists indoubt transactions
between DRDA sync point managers.
LIST HISTORY command
Lists entries in the database history
records. The database history records contain a record of recovery
and administrative events.
LIST INDOUBT TRANSACTIONS command
Provides a list of transactions that are indoubt. The user
can interactively commit, roll back, or forget the indoubt transactions.
LIST INSTANCE command
Lists all database members, cluster caching facility and
hosts associated with the current database, and provides details about
their states.
LIST TABLESPACES command
Lists table spaces and information about table spaces for
the current database.
LIST UTILITIES command
Displays to standard output the list of active utilities
on the instance. The description of each utility can include attributes
such as start time, description, throttling priority (if applicable),
as well as progress monitoring information (if applicable).
LOAD command
Efficiently loads large amounts of data into a DB2 table. The LOAD command loads data at the page level, bypasses trigger firing and logging, and delays constraint checking and index building until after the data is loaded into the DB2 table.
LOAD QUERY command
Checks the status of a load operation during processing
and returns the table state. If a load is not processing, then the
table state alone is returned.
MIGRATE DATABASE command
Converts a previous version of a DB2 database to the formats corresponding to
the release run by the instance.
PING command
Tests the network response time of the underlying connectivity
between a client and a connected database server.
PRECOMPILE command
Processes an application program source file containing
embedded SQL statements. A modified source file is produced, containing
host language calls for the SQL statements and, by default, a package
is created in the database.
PRUNE HISTORY/LOGFILE command
Used to delete entries from the recovery history
file or to delete log files from the active log file path.
Deleting entries from the recovery history file might be necessary
if the file becomes excessively large and the retention period is
high.
PUT ROUTINE command
Uses the specified routine SQL Archive (SAR) file to define
a routine in the database.
QUERY CLIENT command
Returns current connection settings for an application
process.
QUIESCE command Forces all users off either
the specified instance or database across all members and puts them
into a quiesced mode.
QUIESCE TABLESPACES FOR TABLE command
Quiesces table spaces for a table. There are
three valid quiesce modes: share, intent to update, and exclusive.
QUIT command
Exits the command
line processor interactive input mode and returns to the operating system
command prompt.
REBIND command
Allows the user to re-create a package stored in the database
without the need for a bind file.
RECOVER DATABASE command
Restores and rolls forward a database to a particular point
in time or to the end of the logs.
REDISTRIBUTE DATABASE PARTITION GROUP command
Redistributes data across
the partitions in a database partition group. This command affects
all objects present in the database partition group and cannot be
restricted to one object alone.
REFRESH LDAP command
Refreshes the cache on a local machine with updated information
when the information in Lightweight Directory Access Protocol (LDAP)
has been changed.
REGISTER command
Registers the DB2 server
in the network directory server.
REORGCHK command
Provides
table or index statistics that indicate whether reorganization might
be required.
RESET ADMIN CONFIGURATION command
Resets entries in the DB2 Administration Server (DAS) configuration file on the node
to which you are connected. The DAS is a special administrative tool
that enables remote administration of DB2 servers.
RESET ALERT CONFIGURATION command
Resets the health indicator settings for specific
objects to the current defaults for that object type or resets the
current default health indicator settings for an object type to the
install defaults.
RESET MONITOR command
Resets the internal database system monitor data areas
of a specified database, or of all active databases, to zero. The
internal database system monitor data areas include the data areas
for all applications connected to the database, as well as the data
areas for the database itself.
RESTART DATABASE command
Restarts a database that has been abnormally terminated
and left in an inconsistent state. At the successful completion of RESTART DATABASE, the application remains connected to
the database if the user has CONNECT privilege.
RESTORE DATABASE command
Restores a database that has been backed up using the DB2® backup utility. The restored database is in the same state that it was in when the backup copy was made. The Restore Database command can also be used to encrypt an already existing database.
REWIND TAPE command
Rewinds tapes for backup and restore operations
to streaming tape devices. This command is only supported on Windows operating systems.
ROLLFORWARD DATABASE command
The ROLLFORWARD DATABASE command recovers a database by applying transactions recorded in the database log files. The ROLLFORWARD DATABASE command can be run after a database or a table space backup image was restored, or if any table spaces were taken offline by the database due to a media error.
RUNCMD command
Executes a specified command from the CLP interactive mode
command history.
RUNSTATS command
Updates
statistics in the system catalog about the characteristics of a table,
associated indexes, or statistical views. These characteristics include
number of records, number of pages, and average record length. The
optimizer uses these statistics when determining access paths to the
data.
SET CLIENT command
Specifies connection settings for the back-end process.
SET RUNTIME DEGREE command
Sets the maximum run time degree of intra-partition parallelism
for SQL statements for specified active applications.
SET SERVEROUTPUT command
Specifies whether output from the DBMS_OUTPUT message buffer
is redirected to standard output.
SET STOGROUP PATHS command
Sets the storage paths of a storage group during a redirected
restore operation.
SET TAPE POSITION command
Sets the positions of tapes for backup and
restore operations to streaming tape devices. This command is only
supported on Windows operating
systems.
SET WORKLOAD command
Specifies the workload to which the
database connection is to be assigned.
SET WRITE command
The SET WRITE command
allows a user to suspend I/O write operations or to resume I/O write
operations for a database.
START DATABASE MANAGER command
Starts the database manager on the target
member or all members. In a DB2 pureScale® environment,
this command also starts the cluster caching facility (CF).
START HADR command
Starts HADR operations for a database. This is a cluster-wide command in a DB2 pureScale environment,
so you can issue it on any member.
STOP DATABASE MANAGER command
Stops the database manager on the target member or all
members. In a DB2 pureScale environment,
it is also used to stop the cluster caching facility (CF).
STOP HADR command
Stops HADR operations for a database. This is a cluster-wide
command in a DB2 pureScale environment,
so you can issue it on any member, including non-replay members on
the standby database.
TAKEOVER HADR command
Instructs an HADR standby database to take over as the
new HADR primary database for the HADR pair. This is a cluster-wide command in a DB2 pureScale environment,
so you can issue it on any member on the standby, including non-replay
members.
TERMINATE command
Explicitly terminates the command
line processor's back-end process.
UNQUIESCE command Restores
user access to instances or databases which have been quiesced for
maintenance or other reasons. The UNQUIESCE command restores
user access without necessitating a shutdown and database restart.
UPDATE ADMIN CONFIGURATION command
Modifies specified entries in the DB2 Administration Server (DAS) configuration
file. The DAS is a special administrative tool that enables remote
administration of DB2 servers.
UPDATE COMMAND OPTIONS command
Sets one or more command options during an interactive
session, or from a batch input file. The settings revert to system
defaults (or the system default overrides in DB2OPTIONS)
when the interactive session or batch input file ends.
UPDATE CONTACT command
Updates the attributes of a contact that is
defined on the local system. A contact is a user to whom the Scheduler
and Health Monitor send messages.
UPDATE CONTACTGROUP command
Updates the attributes of a contact group that
is defined on the local system. A contact group is a list of users
who should be notified by the Scheduler and the Health Monitor.
UPDATE DATABASE CONFIGURATION command
Modifies individual entries in a specific database
configuration file. A database configuration file resides on every database partition
on which the database has been created.
UPDATE HISTORY command
Updates the location, device type, comment,
or status in a database history records entry.
UPDATE LDAP NODE command
Updates the protocol information associated with a node
entry that represents the DB2 server in Lightweight Directory Access Protocol (LDAP).
DB2 10.5 for Linux, UNIX, and Windows