Avoid or limit output log messages when inserting data into proxy table

[former_SQLA_member1694875]

Hi,

I have a table _test in one DB (name it archive DB):

CREATE TABLE _test(id INTEGER);

And I have a proxy table in another DB (name it main DB):

CREATE SERVER "arch_database" CLASS 'SAODBC' USING 'place connection string here';
CREATE EXISTING TABLE p_test AT 'arch_database;;dba;_test';

Then I insert some records into this proxy table:

INSERT INTO p_test(id)
    SELECT row_num FROM sa_rowgenerator(1, 5);
COMMIT;

Main DB output log:

I. 05/06 14:12:57. 
The query is being processed in NO PASSTHRU mode

The capability check of 86 failed
I. 05/06 14:12:57. The Original Statement is 
    insert into p_test( id ) 
  select sa_rowgenerator.row_num from sa_rowgenerator(1,5)
I. 05/06 14:12:57. The Virtual Statement is 
    insert into p_test( id ) 
  select sa_rowgenerator.row_num from sa_rowgenerator(1,5)
I. 05/06 14:12:57. The Remote Statement for vt_1 is 
    insert into p_test( id ) values( :? ) 
I. 05/06 14:12:57. Server arch_database: INSERT INTO "dba"."_test"  ("id") VALUES (1 ) 
I. 05/06 14:12:57. Server arch_database: INSERT INTO "dba"."_test"  ("id") VALUES (2 ) 
I. 05/06 14:12:57. Server arch_database: INSERT INTO "dba"."_test"  ("id") VALUES (3 ) 
I. 05/06 14:12:57. Server arch_database: INSERT INTO "dba"."_test"  ("id") VALUES (4 ) 
I. 05/06 14:12:57. Server arch_database: INSERT INTO "dba"."_test"  ("id") VALUES (5 ) 

This is only a simple example. When real data will be "archived" in such a way, there will be millions of unnecessary rows flooding the output log.

So here is the question: is it possible to somehow turn off only these specific messages in main DB output log? Thanks in advance.

Main DB version: 11. Archive DB version: 16.

P. s.: I know I could implement archiving in an opposite direction (i. e. getting data instead of pushing) but this question is not about that.

[VolkerBarth · Accepted solution]

AFAIK, those console log messages come from the remote data access logging facility - apparently you have set option CIS_OPTION = 7. Unset that option via

SET OPTION PUBLIC.cis_option = '0';

(or unsetting it when used as temporary option) should prevent further messages.

I would only set it to 7 (and possibly only for the desired connection) when you really need to "debug" the remote queries...

Confine that question and Breck's answer for details...

[former_SQLA_member1694875 · Accepted solution]

That was the case, thank you!