This document explains the cause and solution for errors occurring due to column name mismatches during the View creation step when running system.sh in the Tibero installation process.

This issue may occur in some Tibero 6 patches or specific environments and does not occur in the Tibero 7 environment.

Additionally, it summarizes past installation history and solutions for reference purposes.

Issue

The following View creation error occurs during the installation process.

The CREATE OR REPLACE VIEW statement fails to execute.

Example:

DDL execution failed (ec = -8026): create or replace view v$ssvr_slab_stat as 
select slab_size, slab_get_count, total_chunk_count, max_chunk_count 
from _vt_ssvr_slab_stat; 

Also, the View creation fails due to mismatches between the View definition SQL and actual column names.

Example:

DDL execution failed (ec = -8026): create or replace view v$ssvr_memstat as 
select total_pga_memory_mb, fixed_pga_memory_mb, used_pga_mamory_mb,  
total_shared_memory_mb, fixed_shared_memory_mb, used_shared_memory_mb 
from _vt_ssvr_memstat;

Cause

This issue occurs due to mismatches between the View definition SQL and actual column names.

The main causes are as follows.

• Column names changed from count to cnt.

• The View creation SQL still references the old column names.

• The mismatch between actual columns and View definition SQL causes View creation to fail.

Solutions

Modify the View creation SQL to match the actual column names and recreate the View.

Example:

create or replace view v$ssvr_slab_stat as 
select slab_size, slab_get_cnt, total_chunk_cnt, max_chunk_cnt 
from _vt_ssvr_slab_stat; 

Also, modify to the correct column names as follows and recreate the View.

create or replace view v$ssvr_memstat as
select total_pga_memory_mb, fixed_pga_memory_mb, used_pga_memory_mb,    
total_shared_memory_mb, fixed_shared_memory_mb, used_shared_memory_mb 
from _vt_ssvr_memstat;

After modification, rerun system.sh.

Note

• This issue does not occur in the Tibero 7 environment.

• It may occur only in older versions of Tibero 6 installation or specific environments.

• View creation errors can cause installation to stop.

Caution

• If an error occurs, manual correction of the View and rerunning system.sh is required.

• Check whether patches have been applied for each installation environment.