Bug 1309601

+++ This bug was initially created as a clone of Bug #1163685 +++

With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.)
Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does.
A - 1. Copy the vdbname-vdb.xml into deployments folder
    2. Start the server
B - 1. Start the server
    2. Copy the vdbname-vdb.xml into deployments folder

That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table natively,...)

Affected version:
DV 6.1.0 ER3, DV 6.1.0 ER4

Steps to reproduce:
1. Define teiid_rel:ON_VDB_START_SCRIPT property with external materialized view table.
2. Copy the vdb into deployments folder of stopped server
3. Start the server
4. Check that ON_VDB_START_SCRIPT wasn't invoked (Via debug log or expected action performed by the script)

--- Additional comment from JBoss JIRA Server on 2014-11-14 12:55:46 EST ---

Ramesh Reddy <rareddy> updated the status of jira TEIID-3215 to Resolved

--- Additional comment from JBoss JIRA Server on 2015-10-08 10:39:57 EDT ---

Steven Hawkins <shawkins> updated the status of jira TEIID-3215 to Closed

--- Additional comment from JBoss JIRA Server on 2016-02-18 04:24:14 EST ---

Jan Stastny <jstastny> updated the status of jira TEIID-3215 to Reopened