Books
in black and white
Main menu
Share a book About us Home
Books
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics
Ads

Teradata RDBMS forUNIX SQL Reference - NCR

NCR Teradata RDBMS forUNIX SQL Reference - NCR, 1997. - 913 p.
Download (direct link): teradataforunix1997.pdf
Previous << 1 .. 166 167 168 169 170 171 < 172 > 173 174 175 176 177 178 .. 241 >> Next

NO DUAL LOCAL NOT LOCAL AFTER JOURNAL a change to the type of image to be maintained for the table; any existing images are not affected until the table is updated. NO, DUAL, LOCAL, or NOT LOCAL: the NO and DUAL options specify the number of after-change images to be maintained for the table. NOT LOCAL and LOCAL specify whether single after-image journal rows for non-fallback data tables are written on the same virtual AMP (LOCAL) as the changed data rows, or on another virtual AMP in the cluster (NOT LOCAL).
DEFAULT JOURNAL TABLE= dbname. tname a redefinition of the current journal table or removes its status as the default for the database being modified.

8-216

Teradata RDBMS for UNIX SQL Reference
Teradata SQL Syntax Guide

MODIFY USER

Syntax Element ... Specifies . . .
DROP DEFAULT JOURNAL TABLE = tname removal of the default status of the journal table currently defined as the default for the database being modified. If the journal table resides in the database being modified, DROP also deletes the table from the system. An error message is returned if the DROP request would delete a journal table that is being used by active data tables. The tname parameter is required if this clause is specified without the DROP keyword. If a database is not specified, then the database being modified is assumed. If the database being modified does not have a journal table, tname is created. If a different database is specified, then it must already exist and tname must have been defined as its default journal table. Specifying this option does not change the status of existing data tables in the modified database.
COLLATION a keyword introducing the collation options, which redefine the user’s default collation. Refer to Appendix G, “International and Japanese Character Support”, for more information about collation options.
ASCII ASCII collation, which is the default HOST collation for configurations other than an IBM channel-attached host. ASCII here refers to Teradata’s extension to the ASCII standard.
EBCDIC EBCDIC collation, which is the default HOST collation for an IBM channel-attached host.
MULTINATIONAL that the default collation for the user is one of the European (diacritical) or Kanji sort sequences (see Usage Notes).
HOST that the default collation for the user is determined by the collation of the logon client system.

Several options can be included in a single MODIFY DATABASE statement. No order is imposed, but an error is reported if options are duplicated or conflicting options are included.

To use the MODIFY USER statement, the user must have the DROP Privileges Required USER privilege on the referenced user.

A user must have DROP USER privileges on himself in order to change PERMANENT, SPOOL, and ACCOUNT parameters.

Teradata RDBMS for UNIX SQL Reference

8-217
Teradata SQL Syntax Guide

MODIFY USER

MODIFY USER Rules

PERM or SPOOL Space is Changed Accordingly

default database

Two MODIFY Statements Needed to Change Default Journal Table

Dropped Journal Tables Cannot be Restored

MODIFY USER cannot be used to modify a database.

If the user who is entering the MODIFY USER statement is the same as the user who is referenced in the statement, then changing BEFORE JOURNAL, after JOURNAL, default JOURNAL TABLE, FALLBACK, PASSWORD, STARTUP, COLLATION, and DEFAULT DATABASE options does not require any access privilege.

The following rules apply to the use of MODIFY USER.

• Any or all options can be changed using the same MODIFY statement. A changed option applies to all subsequent operations that occur for the user.

• If an existing option is not changed by a MODIFY USER statement, that option remains the same.

If necessary, the defined PERM or SPOOL space is changed to the next higher value that is a multiple of the number of AMPs on the system.

If a DEFAULT DATABASE clause is specified, the default database is changed for subsequent user sessions. To change the default database for the current session, a DATABASE statement may be entered.

A user’s default database may not be set to NULL. To remove the current DEFAULT DATABASE, a user may set it to the username associated with the MODIFY USER statement. This is the default setting if a DEFAULT DATABASE clause has not been specified.

Two MODIFY statements are needed to change a default journal table that resides in the user space being modified. The first statement drops the present journal table from the system. After the table is dropped, a second statement is required to define a new default journal table.

An error message is returned if the journal table is being used by active data tables.

A dropped journal table cannot be restored. Archives containing data tables that reference the journal are no longer valid, and cannot be used.

8-218

Teradata RDBMS for UNIX SQL Reference
Teradata SQL Syntax Guide

MODIFY USER

Two or more databases/users can share a journal table. However, if Two Or More the sharing databases/users retain as their default the name of a
Previous << 1 .. 166 167 168 169 170 171 < 172 > 173 174 175 176 177 178 .. 241 >> Next