Columns aliasing in PL/SQL

[sda]

It seems sometimes the columns aliasing is not taken in account by Invantive’s PL/SQL
ex:

create or replace table invantivecache_count@inmemorystorage
as 
select PartitionCode as division
,      PartitionCompanyName
,      RowCount invantivecache_count
,      MaxSeenTimestampCurrent as invantivecache_lastTimestamp
,      MaxSeenTimestampCurrentDateTime
from   IncrementalLoadStatuses@eol 
where  Tablenamerequested like '%TransactionLinesIncremental%'
;

The invantivecache_count@inmemorystorage will not have the aliased columns with their alias names and show as PartitionCode and MaxSeenTimestampCurrent.

How to circumvent this?

After I use a Synchronize with update statement, and the columns names need to match to be recognized.

[sda]

Workaround would be:

create or replace table invantivecache_count@inmemorystorage
as 
select to_number(PartitionCode) as division
,      PartitionCompanyName
,      to_number(RowCount) as invantivecache_count
,      to_number(MaxSeenTimestampCurrent) as invantivecache_lastTimestamp
,      MaxSeenTimestampCurrentDateTime
from   IncrementalLoadStatuses@eol 
where  Tablenamerequested like '%TransactionLinesIncremental%'
;

[forums]

The problem could not be reproduced on release 24.0.106 (see picture).

It is recommended to upgrade to this release or newer.

[sda]

@sda

create or replace table invantivecache_count@inmemorystorage
as 
select PartitionCode as division
,      PartitionCompanyName
,      RowCount invantivecache_count
,      MaxSeenTimestampCurrent as invantivecache_lastTimestamp
,      MaxSeenTimestampCurrentDateTime
from   IncrementalLoadStatuses@eol 
where  Tablenamerequested like '%TransactionLinesIncremental%'
;

thanks, I was on a previous 24.0 version. indeed now it is solved.

[forums]

Ok, thanks for confirmation.