Skip to end of metadata
Go to start of metadata

 

Database object and data upload procedure


In order to restore all database objects and data, execute the following .sh files created when aexport is executed in order.

From 2. to 8., execute it in order.

Each file contains isql commands that execute .sql files containing object creation statements.

Preparation before uploading data


Before restoring data, 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.

  • ALTIBASE_NLS_USE
  • ILO_DATEFORM

In the session of executing 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

The ALTIBASE HDB server character set can be checked with the following statement: 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.

How to check the ALTIBASE server character set-Available from ALTIBASE HDB version 5

Creating database object


When running the .sh file, the user should leave a log file to check for errors.

Ex) Logging when running .sh

 

Uploading data


Data upload is performed using run_il_in.sh. In order to upload only a table owned by a specific user or only a specific table, the user can extract only what the user wants from run_il_in.sh as follows.

Ex) In case of uploading only table owned by ALTITEST user
Ex) In case of uploading the SYS user's ORDERS table

If there are many tables or a lot of data, monitor upload.out to see if it is terminated.

Data upload performance log monitoring

 

Checking the data upload result


Checking the .sh running log

Whenever .sh is running, all logs are left to check whether it is normal or not through the log after running .sh.

Ex) Checking errors

Checking log files for each table

Execute the following commands to check if there is an error when uploading data.

 

 

  • No labels