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.

asked 06 May '16, 07:40

Arthoor's gravatar image

Arthoor
1.1k274058
accept rate: 0%

edited 06 May '16, 07:46


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...

permanent link

answered 06 May '16, 08:15

Volker%20Barth's gravatar image

Volker Barth
30.8k308456665
accept rate: 32%

edited 06 May '16, 08:21

That was the case, thank you!

(06 May '16, 08:32) Arthoor
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×29
×25
×15
×6

question asked: 06 May '16, 07:40

question was seen: 356 times

last updated: 06 May '16, 08:32