[jira] [Assigned] (TRAFODION-1796) Executor TEST131 fails with does not exist or is inaccessible error

Thu, 19 Jan 2017 11:10:08 -0800

     [ 
https://issues.apache.org/jira/browse/TRAFODION-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anoop Sharma reassigned TRAFODION-1796:
---------------------------------------

    Assignee: Anoop Sharma

> Executor TEST131 fails with <table> does not exist or is inaccessible error
> ---------------------------------------------------------------------------
>
>                 Key: TRAFODION-1796
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1796
>             Project: Apache Trafodion
>          Issue Type: Test
>          Components: sql-general
>            Reporter: Roberta Marton
>            Assignee: Anoop Sharma
>
> Executor TEST131 is failing even though the table exists:
>  *** ERROR[4082] Object TRAFODION.SEABASE.T1311K does not exist or is 
> inaccessible.
> Executor TEST131, which runs in sqlci (main sqlci) starts up a second sqlci 
> (secondary sqlci) to run some queries.  The main sqlci creates the tables and 
> the secondary sqlci tries to access them.  The secondary sqlci is failing 
> with error 4082 when it tries to access tables created by the main sqlci.
> Background: the runregr_executor.ksh script which controls the regression 
> test obeys a file called cidefs prior to running the test queries.  cidefs 
> sets up common information needed by the tests tests. cidefs contains the 
> following statement (among others):
>    set SCHEMA $$TEST_SCHEMA$$;
> In this case, TEST_SCHEMA is equivalent to trafodion.sch.  So the main sqlci 
> session assumes that the default schema is trafodion.sch.
> When the second sqlci session starts, it uses the default schema that is set 
> by default in the system.  In this case, the default schema happens to be 
> trafodion.seabase. (During “initialize trafodion”, the software creates this 
> schema and makes it the default.)
> So queries fail in the secondary sqlci session because it is looking in the 
> wrong schema.
> So how did this ever work?
> A special test exists in the core test suite – core/TEST000 that creates a 
> bunch of default information.  One of the statements changes the default 
> schema from trafodion.seabase to trafodion.sch (through an insert into the 
> “_MD_”.defaults table). So, if you run core/TEST000, as recommended, before 
> running executor/TEST131, the test passes.  In this case, the second sqlci 
> session uses trafodion.sch as the default schema.  This matches what the main 
> sqlci session uses.
> To avoid having TEST131 fail in our daily runs,   TEST131 will be updated.  
> However, a long term solution is needed so other can avoid this problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to