Manual Upgrade Steps

Pre Upgrade Checks

1. Check the number of rows in the tables to ensure that no table has a huge number of rows.
This will prevent out of memory issues during the upgrade:

select num_rows, table_name from dba_tables where owner='<Demantraschema>' order

by num_rows desc
In this case there are no such tables, but there are known cases where tables like
user_security_series can have 1 million rows that can cause our of memory issues.
 You can do the following in such a case:

 Backup the database schema

 Backup the table user_security_series

o create table user_security_series_bk as select * from user_security_series;

 Truncate the table user_security_series

o truncate table user_security_series;

 You cannot roll back a TRUNCATE TABLE statement, nor can you use a
FLASHBACK TABLE statement to retrieve the contents of a table that has been
truncated.

 Run the upgrade

 After upgrade completes run the following SQL to restore the table user_security_series:

 MERGE INTO user_security_series USING (select user_id ui, series_id si from

user_security_series_bk) temp ON(user_id=ui and series_id=si) WHEN NOT matched THEN
insert(user_id, series_id) values (ui, si);

2. Run the following to check for all BAL related tables

select table_name from dba_tables where owner='<Demantraschema>' and table_name like

'%BAL%'
 Run the following and it should return only 1 row

o select distinct(tran_ID) from bal_bm

 o You can truncate the bal_bm_differences, bal_bm and bal_list tables to remove all
previous upgrade data.

 You cannot roll back a TRUNCATE TABLE statement, nor can you use a
FLASHBACK TABLE statement to retrieve the contents of a table that has
been truncated.

o This could prevent the BAL from hanging during the upgrade. This will also prevent the
user from selecting the wrong transaction when the BAL screen comes up during the
manual upgrade process

o Please backup the tables prior to truncating them

 Create table bal_bm_differences_backup as select * from bal_bm_differences

 Create table bal_bm_backup as select * from bal_bm

 Create table bal_list_backup as select * from bal_list

o You need to truncate in the following order

 truncate table bal_bm_differences

 truncate table bal_bm

 truncate table bal_list

o Alternatively you run the delete command

 Delete from <Table name>

o If for some reason you are unable to truncate you can run a delete command too

 DML statements (INSERT, UPDATE, MERGE, DELETE…) need an explicit

COMMIT statement to commit changes to the DB.

 delete from bal_bm_differences

 delete from bal_bm

 delete from bal_list

3. Enable enhanced logs

Go to the <patch folder.\Disk1\InstData\VM

Edit the demantra_log_conf.properties file and remove the # sign from the line and save file
log4j.appender.IA_FILE_APPENDER.File=/tmp/install.log
 Please ensure that C: had a folder called tmp which has all permissions

4. Start the upgrade

Go to <Patch folder> and double click on the setup.exe

This will bring up the installer. Click on Configure Log

Select Custom Settings. Give the Log File Name and path where you want to the logs and select
Trace in log level
Run the installer by clicking on Install Demantra Spectrum. In case you would like to configure
the application and engine in Linux/Solaris please select the appropriate checkbox
Select the Installation Set
Select your current Demantra installation folder as the path where you would like to install
If you get the below message for Tomcat, please select ‘Yes’
Give the Database credentials on this screen. Please use sys for DBA User Name:

Please input your current Demantra schema that you intend to upgrade in the below screen
along with password:
Please input your database server name, port and SID
If you have users connected to the Demantra schema then you will get the below message.
Please disconnect all connections and then click Retry

In the next screen select Upgrade Schema

Click Yes to the below screen
Select Application and Platform Upgrade
Select Manual Upgrade below
Go through next screen selecting the Languages you want to install, the root address etc and
then click install. It will start the process
On below screen, give the correct path to the 64 bit Java and set the Max memory Allocation to
8 GB
After a while it will bring up the BAL, let it run
Will next bring up the following screen. Let it continue to run
Once this screen becomes active by way of the Save and Close button becoming active like
below:
Click on Save and then Close
Once you click Close it will bring up this screen
Then go to Setting-->Set Business Modeler location to see if the modeler.exe location is NOT set

Right click on the Upgrade_AS_V1227_xxxx And click Upgrade

This will come to this page and run for some time
When BAL finishes it should bring up the Business Modeler like this
If the above screen does not come up, but you see that at the bottom left something like
Running Business Modeler, then
go to windows explorer and log into BM separately from the instance that you are upgrading.
Go to Configuration Validate Bal

It will bring the same page as the installer should have

From the top left drop down Select Transaction click on the drop down to make sure that selects
the correct current transaction
Then click Activate and let it run. This will run for sometime
Upon completion the following screen will come up. Click ok
Then click Close
This will bring back the BAL upgrade page. Wait for BAL to complete processing. Will take a few
minutes
After a while the below screen will pop up. Click ok
This will bring up the installer screen. Let it run
At this point if you had manually started the Business Modeler and if it still open, please close
the business Modeler too

After a while you will get the below screen. This indicates the upgrade has completed. Click
Done
5. Check all logs and test the application

 Please check the install logs that were configured through the installer

 In addition check the logs under c:\tmp

 The BAL Logs will be under :

o ..\..\Demand Planner\BAL\logs

 More logs under

o ..\..\Demand Planner\Database Objects\Oracle Server

 Check that the version_Details_history and version_Details table have been updated.
select * from version_details

B
VER
U S
SIO
IL P
N
D
12.2. 1
0
7 9

Select * from version_details_history order by upgrade_date

U
P
V
G
E B
R
R U
S A
S I
P D
I L
E_
O D
D
N
AT
E
21
7
-
. 4
M
3 5 0
A
. 0
R-
1
18
U
P
G
R
22
7 A
-
. 4 D
M
3 5 E
A
. 0 D
R-
1
18
F
R
O
M
1 23
2 -
. 1 M
0
2 9 A
. R-
7 18