Skip to main content

Search

Welcome to Tibero GTS!

Workaround for 7207 Error When Creating Objects with Designated Reserved Words

Document Type | Technical Information

Category | Administration

Applicable Product Version | 6FS06

Document Number | TADTI035

 

Overview

When creating an object using a designated reserved word in Tibero, a TBR-7207 error occurs.
It is recommended to avoid creating objects with the exact name of a reserved word whenever possible. However, if it is necessary to create an object with that name, this document provides a workaround.
Note
TBR-7207: New identifier required: ' ' is a reserved word.
 

Method

SQL> select * from v$reserved_words where keyword in ('VIEW', 'XMLTYPE');

KEYWORD                            LENGTH RESERVED
------------------------------ ---------- --------
VIEW                                  4         Y
XMLTYPE                               7         N

2 rows selected.
 

# Creating a table
SQL> create table VIEW (c1 varchar(10));
TBR-7207: New identifier required: 'VIEW' is a reserved word.
at line 1, column 14 of null:

SQL> create table XMLTYPE (c1 varchar(10));

Table 'XMLTYPE' created.


โ€“ Workaround
# Creating a table
SQL> create table "VIEW" (c1 varchar(10));

Table 'VIEW' created.

# Dropping the table
SQL> drop table "VIEW" purge;

Table 'VIEW' dropped.

Note

v$reserved_words: View to check designated reserved words in Tibero (Y: reserved word, N: not a reserved word)

Caution

  • It is recommended to create names different from words designated as reserved words.
  • When using double quotes (" "), case sensitivity applies regardless of whether the word is a reserved word, so caution is needed when using them.

 

 

 

Related to