![]() There are read-only tablespaces or a read-only table that you cannot change to read/write for some important reason. ![]() Again, you should be absolutely sure that the tables contain no data requiring conversion. Oracle strongly recommends that you scan even very large tables at least once.Īs with the case of very large tables, you may want to avoid scanning archival data stored in read-only tablespaces on slow storage devices, such as DVD-ROM jukeboxes. You may want to avoid scanning such a large table to reduce the scanning time of the whole database. Standard keyboards of computers running Microsoft Windows always allow such characters to be entered. Must not contain data entered by end users from keyboards that support non-ASCII characters even if the users are supposed to enter English text only. Such tables:Ĭannot contain CLOB columns, unless the current database character set is multibyte.Ĭan contain only character columns with internal application codes, yes/no flags, credit card numbers or other data known to contain only basic ASCII characters. There is a very large table in the database, with terabytes of data, which – you are absolutely sure – contains no convertible data. ![]() You want to avoid converting the column so that the applications may continue to access the data in a pass-through configuration. You cannot migrate the column to a binary data type ( RAW, LONG RAW, or BLOB), because you are unable to modify applications accessing the database, for example, because they are not developed in-house. There is a character column in the database that contains binary data. You need to solve a problem of multiple character sets in a single column (see " Working with Multilingual Columns"). In some situations, you may want to exclude selected columns or tables from scanning or conversion.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |