Skip to end of metadata
Go to start of metadata


Preparation for iloader

Before executing the iloader, be sure to check the following environment variables before proceeding.

ALTIBASE_NLS_USE is required to prevent the breakdown of Korean data, and ILO_DATEFORM should be set to prevent duplication when a date type column has a unique value.


In the session of executing the iloader, it is applied by setting it with the export command as shown below or adding it to the user environment configuration file (.bash_profile or .profile) and logging out and logging in.

How to set environment variables

How to set environment variables

How to set environment variables


The ALTIBASE HDB server character set can be checked with the following sentence: NLS_CHARACTERSET is the ALTIBASE server's character set and NLS_USE is the client's character set. Hangul data is not broken only when these two are set identically.

Error rendering macro 'code': Invalid value specified for parameter 'firstline'
iSQL> set linesize 1024;
iSQL> set colsize 20;
iSQL> select NLS_USE, NLS_CHARACTERSET from v$nls_parameters;
MS949                 MS949
1 row selected.


Performing backup

Use to backup table data.

Download data for all tables in the database must be a file created after entering UserID as sys when executing aexport.


Downloading data of a table belonging to a specific user

In order to back up only tables owned by a specific user, use that aexport-ed to that user.

If aexport is executed by sys, it can extract only the user from and execute it.

Ex) When the user name is altitest

Downloading data for a specific table

In order to download only specific tables, extract only the tables you want from and back them up.

Ex) Extracting the SYS user's ORDERS tables

Execute iloader formout and iloader out commands in sequence.

Ex) Backup of the SYS user's ORDERS table

If there are many tables or a lot of data, monitor download.out to see if it is shutting down.


Data download performance log monitoring


Check the data download result

Check the execution log

The run log is the file specified in the tee command.


Check whether an error has occurred in the specified file as follows.

Check log by table

When is executed, log files in the form of DBUSER_TABLENAME.log are created. (Eg, ALTITEST_ORDERS.log in the altitest user's orders table)
In these files, check for errors with the command below.


Data download file

The backup file created by running is created in USERNAME_TABLENAME.dat format.

  • No labels