anchor.diff:  ////
   
   <<<
  +[[alter_sequence_statement]]
  +== ALTER SEQUENCE Statement
  +
  +The ALTER SEQUENCE Statement changes the future behavior of exiting sequence, including INCREMENT, MAXVALUE, CACHE and CYCLE. 
  +
  +Multiple options can be concurrently specified and separated by a space. Any options not altered will
  +retain their previous settings.
  +
  +ALTER SEQUENCE is a Trafodion SQL extension.
  +
  +For more inforamation, see <<create_sequence_statement,CREATE SEQUENCE Statement>> or <<drop_sequence_statement,DROP SEQUENCE Statement>>.
  +
  +```
  +ALTER SEQUENCE [[catalog-name.]schema-name.]sequence
  +[INCREMENT BY integer]
  +[MAXVALUE integer | NO MAXVALUE]
  +[CACHE integer]
  +[CYCLE | NO CYCLE]
  +```
  +<<<
  +[[alter_sequence_syntax]]
  +=== Syntax Description of ALTER SEQUENCE
  +
  +The options above serve the same purposes as they serve when you create a sequence. For more information, see <<create_sequence_statement,CREATE SEQUENCE Statement>>.
  +
  +NOTE:
  +
  +* START WITH, MINVALUE, NO CACHE and DATA TYPE cannot be changed. Instead, drop and recreate the sequence specifying the desired options.
  +
  +* The unused preallocated values will be lost if a sequence is altered.
  +
  +* Some sequence values will be skipped if you change the INCREMENT BY before the first reference to `seqnum(SEQUENCE, next)`.
  +
  +<<<
  +[[alter_sequence_considerations]]
  +=== Considerations for ALTER SEQUENCE
  +To issue an ALTER SEQUENCE statement, one of the following must be true:
  +
  +* You are DB ROOT.
  +
  +* You have the ALTER or ALTER_SEQUENCE component privilege for the SQL_OPERATIONS component.
  +
  +<<<
  +[[alter_sequence_examples]]
  +=== Examples of ALTER SEQUENCE
  +
  +The following statement changes the MAXVALUE and CACHE for the sequence named `employee_seq`, which is created in <<create_sequence_examples,Examples of CRAETE SEQUENCE>>.
  +
  +```
  +ALTER SEQUENCE employee_seq 
  +MAXVALUE 20000
  +CACHE 30
  +```
  +
  +<<<
   [[alter_table_statement]]
   == ALTER TABLE Statement
   
  
positive.code: ON persnl.employee (last_name, first_name);
  ```
  
  <<<
  [[create_library_statement]]
  == CREATE LIBRARY Statement
  
negative.code: an SQL identifier containing the name of a statement already prepared in this session. An SQL identifier is
  case-insensitive (will be in uppercase) unless it is double-quoted. It must be double-quoted if it contains blanks,
  lowercase letters, or special characters. It must start with a letter. When you refer to the prepared query in a
  SELECT statement, you must use uppercase.
  
  Note: A few non-reserved words that can be used for prepared statement names cannot be used directly in EXPLAIN.
  For example, 'EXPLAIN access;' results in a syntax error. You can still use the name, however, by using a
  delimited identifier. That is, specify the name in upper case, surrounded by double-quotes. For example,
  'EXPLAIN "ACCESS";' will work.
  
  * `_query-text_`
  +
  specifies the text of a query.
  