summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2013-02-11 00:58:51 (EST)
committer Sven Rottstock2013-03-11 07:38:10 (EDT)
commite9225c314442318ec466fd40a34aae4014047e1e (patch)
treef2e5fbaa9d7aef677a0b6fdd896b93e4c41a1d99
parent78fd60cf553a3108ddac1afdfa4cdf645893c0c2 (diff)
downloadorg.eclipse.stardust.documentation-e9225c314442318ec466fd40a34aae4014047e1e.zip
org.eclipse.stardust.documentation-e9225c314442318ec466fd40a34aae4014047e1e.tar.gz
org.eclipse.stardust.documentation-e9225c314442318ec466fd40a34aae4014047e1e.tar.bz2
CRNT-25660 - Added step by step runtime upgrade
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@62871 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.dev/html/handbooks/operation/commandline/ag-commandline-2.htm85
1 files changed, 42 insertions, 43 deletions
diff --git a/org.eclipse.stardust.docs.dev/html/handbooks/operation/commandline/ag-commandline-2.htm b/org.eclipse.stardust.docs.dev/html/handbooks/operation/commandline/ag-commandline-2.htm
index 2157099..d771c94 100644
--- a/org.eclipse.stardust.docs.dev/html/handbooks/operation/commandline/ag-commandline-2.htm
+++ b/org.eclipse.stardust.docs.dev/html/handbooks/operation/commandline/ag-commandline-2.htm
@@ -458,7 +458,7 @@ lock table and cluster table administration:</p>
<li><a href="#proxyTableAdmin">Proxy Lock Tables Administration</a></li>
<li><a href="#cluster">Cluster Table Administration</a></li>
<li><a href="#run">Runtime Upgrade</a></li>
- <li><a href="#multistep">Step by step Runtime Upgrade</a></li>
+ <li><a href="#multistep">Step-by-step Runtime Upgrade</a></li>
</ul>
<h3 id="archive">Audit Trail Archive Administration</h3>
<p>The archive command deletes or archives data from the audit trail. The deleted
@@ -829,70 +829,69 @@ Finalize schema task:
Default link types will be added.
</pre>
-<h4 id="multistep">Step by step Runtime Upgrade</h4>
+<h4 id="multistep">Step-by-step Runtime Upgrade</h4>
<p>
You can execute runtime upgrade step by step.
-Suppose you want to upgrade from @productname@ 5.3 to @productname@ 7.0.
+Suppose, you want to upgrade from @productname@ 6.0 to @productname@ 7.1.
Firstly, perform the upgrade using the option <tt>-ddl</tt> in combination with <tt>-step</tt> option.
</p>
<pre>
-sysconsole -p sysop upgraderuntime -verbose -step -ddl 5_3To6_0.txt
+sysconsole -p sysop upgraderuntime -verbose -step -ddl 6_0To7_0.txt
</pre>
-<p>Following upgrade details are displayed in the 5_3To6_0.txt file. </p>
+<p>Following upgrade details are displayed in the 6_0To7_0.txt file. </p>
<pre>
-// 6.0.0 schema upgrade DDL
-
-CREATE TABLE carnot.preferences (OWNERID NUMBER, OWNERTYPE VARCHAR2(32 CHAR), MODULEID VARCHAR2(255 CHAR), PREFERENCESID VARCHAR2(255 CHAR), PARTITION NUMBER, STRINGVALUE CLOB);
-CREATE UNIQUE INDEX carnot.preferences_idx1 ON carnot.preferences(OWNERID, OWNERTYPE, MODULEID, PREFERENCESID, PARTITION);
-DROP SEQUENCE carnot.message_store_seq;
-DROP TABLE carnot.message_store;
-CREATE TABLE carnot.model_ref (CODE INTEGER, MODELOID NUMBER, ID VARCHAR2(255 CHAR), REFOID NUMBER, DEPLOYMENT NUMBER);
-CREATE UNIQUE INDEX carnot.model_ref_idx1 ON carnot.model_ref(CODE, MODELOID, ID, DEPLOYMENT);
-CREATE UNIQUE INDEX carnot.model_ref_idx2 ON carnot.model_ref(CODE, MODELOID, REFOID, DEPLOYMENT);
-CREATE TABLE carnot.model_dep (OID NUMBER, DEPLOYER NUMBER, DEPLOYMENTTIME NUMBER, VALIDFROM NUMBER, DEPLOYMENTCOMMENT VARCHAR2(255 CHAR));
-CREATE UNIQUE INDEX carnot.model_dep_idx1 ON carnot.model_dep(OID);
-CREATE INDEX carnot.model_dep_idx2 ON carnot.model_dep(DEPLOYMENTTIME);
-CREATE INDEX carnot.model_dep_idx3 ON carnot.model_dep(DEPLOYER);
-CREATE SEQUENCE carnot.model_dep_seq;
-ALTER TABLE carnot.process_instance ADD DEPLOYMENT NUMBER;
-
-// 6.0.0 schema finalization DDL
+// 7.0.0 schema upgrade DDL
+
+ALTER TABLE ipp.activity_instance ADD CRITICALITY DOUBLE;
+ALTER TABLE ipp.activity_instance ADD PROPERTIESAVAILABLE INT;
+CREATE INDEX activity_inst_idx9 ON ipp.activity_instance(CRITICALITY, PROCESSINSTANCE);
+UPDATE ipp.activity_instance SET criticality = -1;
+UPDATE ipp.activity_instance SET propertiesAvailable = 0;
+ALTER TABLE ipp.workitem ADD CRITICALITY DOUBLE;
+UPDATE ipp.workitem SET criticality = -1;
+CREATE TABLE ipp.procinst_link (PROCESSINSTANCE BIGINT, LINKEDPROCESSINSTANCE BIGINT, LINKTYPE BIGINT, CREATETIME BIGINT, CREATINGUSER BIGINT, LINKINGCOMMENT VARCHAR(255));
+CREATE TABLE ipp.link_type (OID BIGINT AUTO_INCREMENT PRIMARY KEY, ID VARCHAR(50), DESCRIPTION VARCHAR(255), PARTITION BIGINT);
+CREATE UNIQUE INDEX link_type_idx1 ON ipp.link_type(OID);
+CREATE TABLE ipp.partition_lck (OID BIGINT);
+CREATE UNIQUE INDEX partition_lck_idx ON ipp.partition_lck(OID);
+
+// 7.0.0 schema finalization DDL
</pre>
-<p>The upgrade is performed till the version 6.0. Secondly, again execute the following
-command:</p>
+<p>
+Using <tt>-ddl</tt> parameter writes the sql that performs the audit trail upgrade into a ddl script.
+Until here the audit trail is not modified. Only when you execute the ddl script the audit trail gets modified.
+So, run upgrade command with option <tt>-step</tt> to modify the audit trail and upgrade to 7.0.
+
+Using <tt>upgraderuntime -step</tt> command without <tt>-ddl</tt> modifies the audit trail while running this command.
+Database schema is upgraded and data migration is done.
+</p>
+<p>Then, run the following command with <tt>-step</tt> and <tt>-ddl</tt> options:</p>
<pre>
-sysconsole -p sysop upgraderuntime -verbose -step -ddl 6_0To7_0.txt
+sysconsole -p sysop upgraderuntime -verbose -step -ddl 7_0To7_1.txt
</pre>
-<p>Following upgrade details are displayed in the 6_0To7_0.txt file.</p>
+<p>Following upgrade details are displayed in the 7_0To7_1.txt file.</p>
<pre>
+// 7.1.0 schema upgrade DDL
+
+ALTER TABLE ipp.data_value ADD DOUBLE_VALUE DOUBLE;
+UPDATE ipp.data_value SET double_value=0.0;
+ALTER TABLE ipp.structured_data_value ADD DOUBLE_VALUE DOUBLE;
+UPDATE ipp.structured_data_value SET double_value=0.0;
+
+// 7.1.0 schema finalization DDL
-// 6.0.0 schema upgrade DDL
-
-CREATE TABLE carnot.preferences (OWNERID NUMBER, OWNERTYPE VARCHAR2(32 CHAR), MODULEID VARCHAR2(255 CHAR), PREFERENCESID VARCHAR2(255 CHAR), PARTITION NUMBER, STRINGVALUE CLOB);
-CREATE UNIQUE INDEX carnot.preferences_idx1 ON carnot.preferences(OWNERID, OWNERTYPE, MODULEID, PREFERENCESID, PARTITION);
-DROP SEQUENCE carnot.message_store_seq;
-DROP TABLE carnot.message_store;
-CREATE TABLE carnot.model_ref (CODE INTEGER, MODELOID NUMBER, ID VARCHAR2(255 CHAR), REFOID NUMBER, DEPLOYMENT NUMBER);
-CREATE UNIQUE INDEX carnot.model_ref_idx1 ON carnot.model_ref(CODE, MODELOID, ID, DEPLOYMENT);
-CREATE UNIQUE INDEX carnot.model_ref_idx2 ON carnot.model_ref(CODE, MODELOID, REFOID, DEPLOYMENT);
-CREATE TABLE carnot.model_dep (OID NUMBER, DEPLOYER NUMBER, DEPLOYMENTTIME NUMBER, VALIDFROM NUMBER, DEPLOYMENTCOMMENT VARCHAR2(255 CHAR));
-CREATE UNIQUE INDEX carnot.model_dep_idx1 ON carnot.model_dep(OID);
-CREATE INDEX carnot.model_dep_idx2 ON carnot.model_dep(DEPLOYMENTTIME);
-CREATE INDEX carnot.model_dep_idx3 ON carnot.model_dep(DEPLOYER);
-CREATE SEQUENCE carnot.model_dep_seq;
-ALTER TABLE carnot.process_instance ADD DEPLOYMENT NUMBER;
-
-// 6.0.0 schema finalization DDL
</pre>
+
+
<script language="JavaScript" type="text/javascript">
<!--
writeFooter();