BFO UPG Oracle Upgrade

Business FLEX 250.
Oracle Database Upgrade

Guide
Document ID: BFO-UPG-250

Revision Date: September 2016
Copyright, Notices, and Trademarks
Copyright, Notices, and Trademarks

Honeywell International Inc. 1998 2016. All Rights Reserved.
While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied
warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be
stated in its written agreement with and for its customer.
In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The information and
specifications in this document are subject to change without notice.
Honeywell, Experion, Uniformance and Business FLEX are registered trademarks of Honeywell International Inc.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
Crystal Reports and Business Objects are trademarks or registered trademarks of Business Objects SA in the United
States and/or other countries.
Adobe and Acrobat Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the
United States and/or other countries.
OSIsoft and The PI System are either registered trademarks or trademarks of OSIsoft, Inc.
All other brand and product names shown are trademarks of their respective owners.
About Business FLEX

Business FLEX is a family of advanced applications that improve plant profitability by enabling plant staff to work
more effectively and make better decisions. To learn more about Business FLEX and other Honeywell software
solutions, contact your Honeywell account manager.
Visit us online at www.honeywell.com/ps, or contact us at 800-822-7673.
Honeywell, 1860 West Rose Garden Lane, Phoenix, Arizona, 85027, USA
Release Information
Business FLEX 250: Release 250.1
Revision Date: September 2016
Business FLEX Database Version: BF250.0.00
Document ID: BFO-UPG-250
ii Oracle Database Upgrade Guide

Contents
Contents
About the Database Upgrade 1
What is Business FLEX database upgrade 1
About this guide 2
Related documents 3
Contact us 3
Upgrade Checklist 5
What is a checklist 5
Overall upgrade checklist 5
Before You Begin 7

Understanding the Business FLEX database upgrade 7
Installation guidelines 8
Prerequisites 10
Pre-Upgrade: Create the Oracle NET configuration files 12
Export PRD Database 19

Prerequisites 19
Checklist for exporting the PRD database 19
Before you begin 19
Exporting the PRD database 20
Creating a backup of the database 23
Upgrade the Business FLEX Database 29

Overview 29
Upgrade process 29
Checklist for upgrade of Business FLEX database 30
Enable User Based Shift Rotation feature 30
Prepare for the Business FLEX 250 database 33
Creating the Business FLEX database 36
Upgrade Pre-250 Business FLEX database to 250 39
Post-Upgrade Remove ACM entry from IP_APPL table 41
Grant permissions to run the Business FLEX application server 41
Post Upgrade Migrate the users 42
Post Upgrade Enable Database Synchronization with PHD300 or

later 43
Overview 43
Checklist for database synchronization with PHD 43
Oracle Database Upgrade Guide iii

Contents
Configuring the database 44

Verifying applications server user is registered with PHD database 44
Configuring the background processes 45
Appendix A Recent Changes in Business FLEX 47

Summary 47
Oracle versions 47
Oracle database organization 48
Installation of Business FLEX oracle database 48
Database interconnections 49
Use of IP_APPL_VER and owner columns 49
Security 49
Plant Reference Model 50
Migration considerations for existing sites 50
Appendix B Kill MSGLOGSERVER Job 53

Overview 53
Determining the correct user 53
Killing the MSLOGSERVER 53
Appendix C Sort Unicode Databases 57

Overview 57
Change to a language specific sort 59
Appendix D Exporting the Business FLEX 240 database from

Oracle 11.2.0.1 61
Exporting the Business FLEX 240 database 61
Completing the installation of Oracle 11.2.0.1.0 patch 12 62
iv Oracle Database Upgrade Guide

About the Database Upgrade
What is Business FLEX database upgrade

A typical Business FLEX system upgrade involves installing several
components:
Server components
Historian, on one node or in a shadow/buffer hierarchical arrangement
Oracle database
Application Server
End user components

Uniformance Desktop or third-party historian desktop tools
Oracle client software
TPI (TotalPlant Information)
Application-specific components such as the Production Balance user
interface or the LIMS COA feature.
The server components can be installed on a single computer or on several
computers.
Business FLEX release 201/210/220/230/240/241/242/250 and Uniformance
PHD release 210 introduced a significant change in the organization of the
Oracle database. Prior to Business FLEX R200, a single Oracle instance was
used for both Uniformance and Business FLEX, and this Oracle instance was
created by Uniformance and extended by Business FLEX. In the future, these
two product lines will maintain separate Oracle instances.
Business FLEX 250 release includes common installation kit that provides an
option to install BFLEX 250 Database on Oracle 11gR2/12c software. In
addition, Business FLEX 250 database installed on Oracle11gR2/12c software
provides redundancy support using Oracle Real Application Clusters. Refer to
the Oracle Real Application Cluster Guide for details.
Oracle Database Upgrade Guide 1

About this guide

This guide provides instruction on how to upgrade an existing
Uniformance/Business FLEX Oracle database to Business FLEX 250 Oracle
database.
This document provides the following instructions:
How to upgrade to Business FLEX 250 Database from earlier versions
How existing Business FLEX users can convert their database to Unicode
How to enable communication to the Uniformance database if PHD is the
historian of choice for the site
Each section in this manual indicates what it is to be used for.
NOTE: This guide does not substitute the Oracle documentation provided by
Oracle Corporation and must be used in conjunction with that documentation set.
Who should use this guide

This guide is intended for Honeywell employees who are responsible for
upgrading an existing Uniformance / Business FLEX database to Business FLEX
250.
Conventions used in this guide

The following typographic and stylistic conventions are used throughout this
guide:
This Indicates this
Click To position the mouse over a topic, button, box, or window area and
then click the left mouse button.
Double-click To position the mouse over a topic, button, box, or window area and
then click the left mouse button twice in succession.
Right-click To position the mouse over a topic, button, box, or window area and
then click the right mouse button.
Courier A command you type or a file or directory location.
Italics Another Business FLEX document.
Bold A button or menu command you click in a window.
2 Oracle Database Upgrade Guide

In addition, these symbols are used:

Symbol Definition
ATTENTION: Identifies information that requires special consideration.
TIP: Identifies advice or hints for the user, often in terms of performing a
task.
CAUTION Indicates a situation which, if not avoided, may result in equipment or work
(data) on the system being damaged or lost, or may result in the inability to
properly operate the process.
Related documents
Further information about Business FLEX Database and related applications can
be found in the following documents.
Document Title
BF-INS-250 Business FLEX Installation Guide
BFO-RAC-250 Business FLEX Oracle Real Application Cluster Guide
BFO-INS-250 Oracle Database Installation Guide
For more information on the other Business FLEX applications see the
documents included on the Business FLEX Software DVD. Refer to the Business
FLEX Software Change Notice for a list of the documents that are supplied.
Contact us
Please send any comments or questions to the Help Desk at
support@honeywell.com. Ensure that you type Business FLEX Oracle Database
in the subject line of your e-mail.

This page is intentionally left blank

Upgrade Checklist
Upgrade Checklist
What is a checklist
A checklist provides a list of tasks that you must perform to complete a job. Each
checklist includes sub-tasks that must be done in the order listed, unless specified
otherwise.
This guide makes extensive use of checklist to guide you through the installation
process. Make sure to complete the tasks listed in the checklist before
proceeding.
Overall upgrade checklist

The following table lists the order of tasks that must be performed to upgrade the
Business FLEX Oracle Database in a system having PHD215 as the historian.
Refer to Go to
Export PRD Database 19

Upgrade the Business FLEX Database 29

Upgrade Checklist

Before You Begin
Before You Begin
Understanding the Business FLEX database upgrade
Workflow
ATTENTION:
These migration procedures are developed for this Business FLEX release
expecting that existing users will continue to use PHD as their historian of
choice for their sites.
This means that sites must complete the Uniformance 300 upgrade process
prior to starting the Business FLEX 250 database migration process.
If a site wishes to upgrade their database to Business FLEX 250 and change
historians at the same time, contact AppTech for assistance.
This guide is prepared to simplify the database migration procedure for existing
Business FLEX customers who want to migrate from an existing Uniformance /
Business FLEX Oracle database to the database version as delivered with
Business FLEX 250. This guide includes the procedures to upgrade Business
FLEX from previous versions to 250 and to create the Business FLEX
installation scripts. However, this guide does not include the procedures to
remove previous version of Oracle, install and configure Oracle11gR2/12c
software. Refer to the BFO Installation Guide for details.
When you follow these procedures, ensure that you read each step and review the
screens associated with the step before proceeding. This document includes notes
that provide critical upgrade information to help you avoid mistakes during your
upgrade.

Before You Begin
Expertise requirements
This guide assumes that the person handling the upgrade is familiar with
Oracle11gR2/12c server concepts, which is required for the successful upgrade of
the Business FLEX database and/or Oracle11gR2/12c server software.
ATTENTION:
Honeywell suggests that before you install the Oracle 11gR2/12c software, you
become familiar with the Oracle11gR2/12c installation documentation which is
located on the ORACLE11gR2/12c Documentation DVD. The following
ORACLE11gR2/12c documents contain a wealth of information that must be
reviewed:
For Oracle 11gR2:
ORACLE11gR2 Database Installation Guide, Release 2 (11.2.0.3.0) for
Windows
ORACLE11gR2 Database Release Notes, Release 2 (11.2) for Windows
For Oracle 12c:
ORACLE12c Database Installation Guide, (12.1.0.2) for Windows
ORACLE12c Database Release Notes, (12.1) for Windows
Read the latest Business FLEX 250 Software Change Notice to be aware of any
installation issues. The Software Change Notice (SCN) contains information
needed for a particular release, including changes that are not in the product
documentation. This includes information that must be read before installing the
software.
Additional technical notices and updates to the Software Change Notice are
available on the Honeywell Solution Support Online website. Before installing
this release, check for updates through http://hpsweb.honeywell.com.
Those who are not able to access Honeywell Solution Support Online can
obtain the SCN updates by contacting their regional Honeywell Technical
Assistance Center (TAC).
Installation media
Business FLEX 250 is distributed on a single DVD containing the following:
DVD Title Contents
Business FLEX The Business FLEX applications, Business FLEX Oracle database,
250 Software Business FLEX TPI Client, and Business FLEX Application Server
(background processes). This DVD includes the supplemental
software components and user documentation.
Installation guidelines
Administrator privileges
You must have Administrator privileges for the Windows account to install
Oracle11gR2/12c, and install or upgrade Business FLEX on a system.

Before You Begin
Installation variables
The following table describes installation variables for which you are prompted
in forms, default values you must use, and a place for you to enter your actual
values when defaults are not used.
Database Installation Installation Default Value Users Actual Value
Variable (Fill In)
ORACLE Server Host Name

Database Instance PRD
Database Alias Name TOTALPLANT (upper case
only)
32-bit ODBC Data Source TOTALPLANT32
Name
ORACLE Server Port 1521, 1526
Numbers
Oracle user name/password defaults

There are three Oracle users referenced in this document. There is a default
password assigned to each. The SYS and SYSTEM user accounts are created
automatically when creating a new Oracle database. The TOTALPLANT account
is explicitly created when configuring a database that is to be used by Business
FLEX.
NOTE: Ensure that you limit the Oracle account name to less than 30 characters.
This includes both the domain name and user name.
The passwords for these users may differ from those in your database. Substitute
with your passwords where appropriate.
User Default Password Actual Password
SYS BFLEX
SYSTEM BFLEX
TOTALPLANT BFLEX
Oracle LISTENER password

The command line version of the Oracle Listener Control program LSNRCTL
can, optionally, utilize a password. This password must be set before starting or
stopping the Listener. To stop listener from remote systems with authentication,
modify the listener.ora and add the PASSWORDS_LISTENER=<password>.
For example, PASSWORDS_LISTENER=oracle. This is not an encrypted
password.

Before You Begin
For upgrades, perform the following steps to verify if your system uses a
password:
1. Open the listener.ora file.
By default, the file is located in the following directory:
2. Check to see if the PASSWORDS_LISTENER line is present in the file:
Not present LSNRCTL does not require a password
Present LSNRCTL requires a password
Prerequisites
Oracle prerequisites and considerations
Database version
Business FLEX 250 runs on Oracle 11gR2 and Oracle12c. ORACLE7,
ORACLE8 and Oracle 9i are not supported in this release. Before you begin,
ensure that the Oracle software you plan to use for this installation/upgrade meets
the following version requirements:
Oracle 11g Standard Edition Release 11.2.0.3.0
Oracle 11g Enterprise Edition Release 11.2.0.3.0
Oracle 11g Standard Edition One Release 11.2.0.3.0
Oracle 12c Standard Edition 2, 12.1.0.2
NOTE: Standard Edition One is a licensing edition. It is same as Standard
Edition for a system that includes 1 or 2 processor sockets. There are no
packaging differences. It was called Standard Edition One as it was originally
Standard Edition for a 1 processor socket system. After the release of 10g, it has
extended to 1 or 2 processor socket systems. Therefore, to install Standard
Edition One, you have to install Standard Edition software. In addition, it must
not be used in a clustered environment (RAC).
Check the latest Business FLEX R250 Software Change Notice (SCN) to see if
any patches from Oracle are approved and required by Honeywell, and then
obtain those patches.
For patches subsequent to the Business FLEX release and for additional technical
notifications, log on to Honeywell's Solution Support Online website through
http://hpsweb.honeywell.com.
NOTE: Oracle 11.2.0.3.0 and Oracle 12.1.0.2 are the only supported versions on
all 64-bit and 32-bit operating systems.

Before You Begin
Server prerequisites and considerations

For the Oracle Net configuration, you must know the hostname of the computer
that you are installing or upgrading.
Perform the following steps to get the hostname:
1. Open the Command Prompt.
2. Enter the command hostname.
The hostname is displayed.
3. Record the value. For example,
Server HOSTNAME: ____________________________________________
Oracle connect strings

Connection to the Oracle database requires three things:
username
password
database alias
Example
sqlplus system/BFLEX@totalplant
In the early stages of the database install, connections are made to the database
that do not use the database alias portion of the connect string. This is because
the Net8 configuration files are not yet configured in the early stages of the
database install, and therefore, making a connection with the database alias is not
possible.
Disk space requirements

The Oracle 11gR2 software installation requires about 3.5 GB of disk space.
Refer to the Oracle 11gR2 Documentation for more information about disk space
requirements.
The Oracle 12c software installation requires about 4.55 GB of disk space. Refer
to the Oracle 12c Documentation for more information about disk space
requirements.
The Business FLEX database scripts require about 64Mb.
The Business FLEX database files for installs and upgrades require 1.6 GB.
Upgrades, at a minimum require the specified disk space. In addition, an upgrade
requires adequate space for the full export from the pre 250 database.
The Business FLEX 250 database files are setup to autoextend. Therefore, as
and when the database fills with data, the database files automatically get larger
to accommodate the increasing space requirements.

Before You Begin
Setting the database files to autoextend reduces some database maintenance as

the database no longer suffers from a full tablespace condition. Instead, the
database grows to meet the requirements. The only condition that prevents the
database from getting larger is when it runs out of physical disk space.
TIP: Verify that your system includes automatic or manual mechanisms in place
to watch disk space usage on a regular basis and to ensure that the system does
not run out of disk space.
Pre-Upgrade: Create the Oracle NET configuration

files
You can configure the TNSNAMES.Ora and LISTENER.Ora files by following
the procedure mentioned in this section or by following any other Oracle
specified methods (for example, Net Manager) or other third party applications.
Refer to Oracle Documentation for more information.
Checklist for creating Oracle configuration files

Refer to Go to
Copying the Business FLEX database scripts 12

Copying the Business FLEX Oracle NET stub files 13
Stopping the Oracle11gR2/12c listener 14
Renaming the Oracle NET files 14
Editing the Oracle NET configuration files 14
Copying the Business FLEX database scripts

Perform the following steps to copy the Business FLEX database scripts:
1. Create the Business FLEX database folder (\BFX_DB) if you have not
already created it. By default the target drive letter for the \BFX_DB folder is
D. Therefore the directory must be called D:\BFX_DB
2. Insert the Business FLEX 250 Software DVD into your DVD-ROM drive.
3. Use Windows Explorer to navigate to the Business FLEX Database folder on
the Business FLEX 250 DVD.
4. Select and copy all files to the Business FLEX working area, by default this
is D:\BFX_DB
5. Remove the read only property on the files and folders that were copied to
the working area.
Copying the Business FLEX Oracle NET stub files

This section explains how to set up your Oracle configuration files for the Local
Naming Method. For other network configuration options, such as Host Naming
or Oracle Name Server, refer to the Oracle Documentation.

Before You Begin
Business FLEX ships with the three stub Oracle configuration files. They are:
1. LISTENER.OR_
2. SQLNET.OR_
3. TNSNAMES.OR_
These files must be copied from the Business FLEX working area to the Oracle
Net configuration directory. By default, the Business FLEX working area is
D:\BFX_DB.
Perform the following steps to copy the Business FLEX Oracle NET stub files:
1. Navigate to the Business FLEX 250 working area.
By default, this is D:\BFX_DB
2. Copy the following Oracle configuration files to the Oracle configuration
folder.
For Oracle11gR2, the Oracle configuration folder is
D:\app\administrator\product\11.2.0\dbhome_1\NETWORK\ADM
IN
copy listener.or_
IN
copy sqlnet.or_
IN copy tnsnames.or_
IN
For Oracle12c, the Oracle configuration folder is
IN
copy listener.or_
IN
copy sqlnet.or_
IN copy tnsnames.or_
IN

Before You Begin
Stopping the Oracle 11gR2/12c listener

Perform the following steps to stop the Oracle 11gR2/12c listener:
1. Open Command Prompt.
2. Stop the LISTENER service.
lsnrctl stop
The following information must be displayed during the LISTENER stop:
The command completed successfully
3. Exit the Listener Control program.
LSNRCTL> exit
Renaming the Oracle NET files

Perform the following steps to rename the Oracle net files:
1. Change to the location where the Oracle Net configuration files are located.
For Oracle 11gR2, the location is
IN
For Oracle 12c, the location is

IN
2. Rename the Oracle Net configuration files.

ATTENTION: If these files (listener.ora, sqlnet.ora, tnsnames.ora) already
exist in this directory, they must be renamed or deleted before performing
this step.
rename *.or_ *.ora
Editing the Oracle NET configuration files
Updating the listener.ora file

Perform the following steps to update the listener .ora file:
1. Navigate to the following folder.
For Oracle 11gR2:
D:\app\administrator\product\11.2.0\dbhome_1\NETWORK\ADMIN
For Oracle 12c:

2. Edit the LISTENER.ORA file.

3. Change the value of HOSTNAME to match that of the Server on which
Oracle is installed.

Before You Begin
NOTE: If you have named your database anything other than the Business
FLEX default of PRD, change the SID_NAME to reflect your database name.
ATTENTION:
If you installed have the Oracle 11gR2/12c Enterprise Edition Server
software and installed the Oracle Enterprise Manager by following the
instructions in this guide, uncomment the three lines for the OEMREP
SID name.
If you have used a SID name other than OEMREP, make changes
accordingly.
4. Save the file.
Updating the tnsnames.ora files

5. Navigate to the following folder
For Oracle 11gR2:
For Oracle 12c:

6. Edit the TNSNAMES.ORA file.

7. Change the value of HOSTNAME to match that of the Server on which
Oracle is installed.
NOTE: If you have named your database anything other than the Business
FLEX default of PRD, change the value for SERVICE_NAME to reflect
your database name.
ATTENTION:
If you have installed the Oracle 11gR2/12c Enterprise Edition Server
software and installed the Oracle Enterprise Manager by following the
instructions in this guide, then make the following changes:
Uncomment the entry for OEMREP (remove /* and */).
Change the value of HOSTNAME to match that of the Windows machine
on which ORACLE is installed.
If you have named your Oracle Enterprise Manager database anything
other than the Uniformance default of OEMREP, change the value for
SERVICE_NAME to reflect your instance name.
8. Save the file.

Before You Begin
Verifying the Oracle NET configuration files

The following files must be found in the Oracle Net configuration directory.
For Oracle 11gR2, the path is
LISTENER.ORA SQLNET.ORA TNSNAMES.ORA
For Oracle 12c, the path is

LISTENER.ORA SQLNET.ORA TNSNAMES.ORA
The contents of these files must resemble the following examples.
LISTENER.ORA
The value for HOSTNAME must match that of the Server on which Oracle is
installed.
The value for SID_NAME must match your database instance name. If you
named your database anything other than the Business FLEX default of PRD,
change the value for SID_NAME to reflect your database name.
SQLNET.ORA
SQLNET.EXPIRE_TIME = 10
#
# uncomment for Windows Authentication (NTS)
#
#SQLNET.AUTHENTICATION_SERVICES=(NTS)
TNSNAMES.ORA
The value for HOSTNAME must match that of the Server on which Oracle is
installed.
The value for SID must match your database name. If you named your database
anything other than the Business FLEX default of PRD, change the value for
SID to reflect your database name.
TOTALPLANT =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = HOSTNAME)(PORT =
1521))
(CONNECT_DATA = (SERVICE_NAME = PRD))
)
/*
OEMREP =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT =
1521))
(CONNECT_DATA = (SERVICE_NAME = OEMREP))
)
*/
Ensure the files on your system have some resemblance to these examples.

Before You Begin
Restarting the Oracle 11gR2/12c listener

Perform the following steps to restart the Oracle 11gR2/12c listener:
2. Start the LISTENER service
lsnrctl start
Various bits of information are displayed during the LISTENER startup. But
you must see output that resembles the following:
Services Summary
Service PRD has 1 instance(s)
Instance PRD, status UNKNOWN, has 1 handler(s) for
this service...
The command completed successfully
3. Type EXIT to exit the LISTENER control utility.
Testing the Oracle NET configuration

Perform the following steps to test the Oracle Net configuration:
2. Use SQL*Plus and logon as ORACLE user SYSTEM
You must see a SQL> prompt.
3. Type EXIT to exit SQL*Plus.
ATTENTION:
If you are unable to log on to SQL*Plus, do the following to determine
why a connection cannot be made to the database:
Review the Oracle Net configuration steps to ensure none were
missed.
Check to make sure you copied the network configuration files into the
proper directory.
From a command prompt, use the TNSPing utility to check the
connection to the Oracle instance (tnsping totalplant).
Verify whether the hostnames are correct.
Verify whether the SID is correct.
If you are still unable to log on to SQL*Plus, contact your local Oracle
Data Base Administrator, or call Honeywell TAC for assistance.

Before You Begin

Export PRD Database
Export PRD Database

This section applies to sites that are currently on Oracle7, Oracle8 or Oracle 9i
and sites that are running Oracle11gR2 or 12c but want to move to new hardware
with BF250.
The upgrade to Oracle11gR2/12c is a significant operation in both time and
complexity. The Oracle11gR2/12c 2 installation utilities are quite different than
previous versions of Oracle7 and Oracle8. Read this section very carefully before
attempting to upgrade to Oracle11gR2/12c.
NOTE: Not all steps are required for all sites. Be careful in your reading to
ensure you follow all of the steps that apply to your site.
Prerequisites
The prerequisites required for exporting the PRD Database are described:
An idle database is required for a successful upgrade. To make the database
idle, you must shut down:
The Application Server. Refer to Prerequisites for details.
The Message Log Server. Refer to Appendix B Kill MSGLOGSERVER
Job for details.
ATTENTION: Not shutting down the Application Server and Message Log
Server results in severe database upgrade problems during various stages of
the upgrade.
Checklist for exporting the PRD database

Refer to Go to
Exporting the PRD database 20

Creating a backup of the database 23
Before you begin
Shutdown connections to the database

Ensure that there are no active users on the system. This includes Web
applications, TPI forms, and even PHD.

Export PRD Database
Exporting the PRD database
Creating the Business FLEX working area

Perform the following steps to create the Business FLEX working area:
already created it. Do this on the same drive where a previous version of the
BFLEX database is located. By default the target drive letter for the
\BFX_DB folder is D, and therefore the directory must be called
D:\BFX_DB
2. Insert the Business FLEX 250 Software DVD into your DVD drive.
3. Use Windows Explorer to navigate to the Business FLEX Database
folder on the Business FLEX 250 DVD.
4. Select and copy all files to the Business FLEX working area. By default this
is D:\BFX_DB
the working area.
Preparing CUSTOMTBS.SQL
CUSTOM tablespaces are the tablespaces other than TOTALPLANT default
tablespaces. This is an optional procedure to create CUSTOM tablespaces.
Perform the following steps to create CUSTOM tablespaces:
1. Prepare a CUSTOMTBS.sql file if site wants to create any CUSTOM
tablespaces. CUSTOM tablespaces are the tablespaces other than
TOTALPLANT default tablespaces.
2. Copy the CUSTOMTBS.sql file to Business FLEX working area. This is by
default D:\BFX_DB.
3. Uncomment the following line from bfxdbImport.cmd
rem if exist %BfxDir%\CUSTOMTBS.sql
%ORA_HOME%\bin\sqlplus /nolog @%BfxDir%\CUSTOMTBS.sql
by removing the word rem from in front of it:
if exist %BfxDir%\CUSTOMTBS.sql %ORA_HOME%\bin\sqlplus
/nolog @%BfxDir%\CUSTOMTBS.sql
NOTE: Copy the CUSTOMTBS.sql file to the BFX_DB folder of the Oracle
system that will host the new Business FLEX database.

Export PRD Database
How to Prepare CUSTOMTBS.SQL

Refer to your Oracle Documents for the correct syntax and structure of the
CUSTOMTBS.SQL file.
A CUSTOMTBS.SQL must first connect to database using SYS account:
For the database Run the script
Oracle 7/8i systems connect internal/totalplant

Oracle 9i, 10g, 11gR2, and connect sys/<password> as sysdba
12c systems
It contains one or more tablespace create statements. Refer to Oracle Documents

for syntax of tablespace creation statements. Ensure that your
CUSTOMTBS.SQL file ends with an exit statement.
Exit
Shutting down and restarting the existing database

Ensure no one is using the database at this time. This is absolutely crucial to the
success of the upgrade. All users must be disconnected and all processes that
connect to the database must be shutdown.
The following commands shutdown the Oracle database and restart it in
restricted mode. Only those with restricted session privileges, such as Data
Base Administrators, can connect to the database.
Perform the following steps to shutdown or restart the existing database:
2. Set the database SID value to match the database SID which is by default
PRD. If your database SID is not PRD, substitute the appropriate SID in the
following line.
set ORACLE_SID=PRD
3. Begin process of shutting down the database:
Oracle 7 systems Svrmgr23

Oracle 8i, 9i, 10g, 11gR2, sqlplus /nolog
and 12c systems
4. At the SQL prompt, connect internal

Oracle 7/8i systems connect internal/totalplant

Oracle 9i/10g/11gR2/12c connect sys/<password> as sysdba
systems
Result: Connected
If you get a TNS protocol adapter error, the Oracle SID was not set correctly
in a previous step.

Export PRD Database
If the password you specified for internal is incorrect, contact your Oracle
DBA or Honeywell TAC to change the internal password.
5. Shutdown the database.
shutdown immediate
NOTE: Shutting down the Oracle instance may take a few minutes.
Result: Database closed.
Database dismounted.
Oracle instance shut down.
If the database does not shutdown, call Honeywell TAC for assistance.
6. Startup the database in restricted mode (change the pfile value where
necessary)
For the Run the script
database
Oracle 7 startup restrict pfile=<Oracle server

systems installation
directory>\orant\database\initprd.ora open prd
Oracle 8i startup restrict pfile=<Oracle server
directory>\ora8\admin\prd\pfile\init.ora open prd
Oracle 9i startup restrict pfile= <Oracle server
directory>\oracle\admin\prd\pfile\init.ora open
prd
Oracle 10g startup restrict pfile= <Oracle server
directory>\oracle\product\10.2.0\admin\prd\pfile\
init.ora open prd
Oracle startup restrict pfile= <Oracle server
11gR2 installation
systems directory>\app\administrator\product\11.2.0\admin
\PRD\pfile\init.ora open prd
Oracle 12c startup restrict pfile= <Oracle server
directory>\app\administrator\product\12.1.0\admin
\PRD\pfile\init.ora open prd
Result: Oracle instance started
Database Opened
7. Type EXIT to exit Server Manager.
8. Use SQL*Plus to attempt to connect to the database
Oracle 7 systems plus33

phd_readonly/phd_readonly@totalplant
Oracle 8i/9i/10g/11gR2/12c sqlplus
systems phd_readonly/phd_readonly@totalplant
Result: You must not be able to connect to the database.

9. Press the <Enter> key twice to exit SQL*Plus.

Export PRD Database
Creating a backup of the database
Options available
This guide outlines the steps to do a database backup using EXP. The file which
is created by this export is needed for steps that come later in this guide. To
perform an additional backup, other than an export, contact your DBA.
ATTENTION:
Oracle recommends that you not rely solely on EXP as a backup
mechanism. You are advised to always implement a proper physical
backup strategy for databases.
Image backups must be taken. In the event of a catastrophic upgrade
failure, the entire system could be restored from an image backup. This
would be much faster than having to reinstall/recreate the database, and
then perform a full import.
If an image backup is taken, ensure the Oracle database is completely
shut down before making the image backup.
Determining the file export size

Perform the following steps to determine the export file size:
2. Navigate to the Business FLEX 250 working area. By default, this is
D:\BFX_DB.
3. Navigate to the sub-folder PRE_BFX.

4. Use SQL*Plus to run the script that will calculate the approximate disk space
required for the full export of the existing database.
Oracle 7 systems plus33 system/manager@totalplant

@exportsize
Oracle Set Oracle_sid=prd
8i/9i/10g/11gR2/12c sqlplus system/bflex@totalplant
systems @exportsize
Space Required: __________________________________

Export PRD Database
Migrating to Business Flex 250
Preparing the user files

Perform the following steps to prepare the user files:
D:\BFX_DB.
3. Run the script that will generate a script that is used for recreating the user on
the system.
Oracle 7 systems plus33 totalplant/totalplant@totalplant

@GenUsersRolesPer
8i/9i/10g/11gR2/12c sqlplus totalplant/bflex
systems @GenUsersRolesPer
The UsersRolesPer.sql file is created by this script. Make sure that a

copy of this file exists in the Business FLEX working area which is by
default D:\BFX_DB.
Preparing the user files from OMPro database

ACM does not support Oracle database in the OMPro 320 release. Hence the
ACM user instances in the old Business FLEX database must be removed before
migrating to Business FLEX 250.
Perform the following steps for removing the ACM-related users from the
UsersRolesPer.sql file.
1. Open the command prompt.

D:\BFX_DB.
3. Edit the GenUsersRolesPer.sql script by adding all the ACM-related

users in the exclude list and save it.

Export PRD Database
4. Run the script that generates a script that is used for recreating the user on the
system.
Oracle 7 systems plus33 totalplant/totalplant@totalplant

@GenUsersRolesPer
8i/9i/10g/11gR2/12c sqlplus totalplant/bflex
systems @GenUsersRolesPer
The UsersRolesPer.sql file is created by this script. Make sure that a

copy of this file exists in the Business FLEX working area which is by
default D:\BFX_DB.
NOTE: Copy the UsersRolesPer.sql file to the D:\BFX_DB.folder of the
Oracle system that will host the new Business FLEX database.
NOTE: If the users are created on tablespaces other than TOTALPLANT
Default tablespaces then the tablespaces have to be created using
CUSTOMTBS.sql. Refer to the section How to prepare CUSTOMTBS.sql for
details on creating custom tablespaces.
The input validation to the IDENTIFIED BY VALUES clause for CREATE
USER, CREATE ROLE, ALTER USER, and GRANT is improved in Oracle
12.2.
If users have GLOBAL_AQ_USER_ROLE role in 11g environment with
Authentication_type as Global and password as global, the creation of role as
CREATE ROLE "GLOBAL_AQ_USER_ROLE" IDENTIFIED BY VALUES
'GLOBAL' is not supported by Oracle 12c (Standard). Users must change it as
CREATE ROLE "GLOBAL_AQ_USER_ROLE" in the UsersRolesPer.sql
file before importing the customer database.

Export PRD Database
Creating schema export for TOTALPLANT from non-OM Pro database

Perform the following steps to create the Schema Export for Migration:
1. Change to a drive/directory large enough to hold an export of the existing
database.
2. Perform an export for the TOTALPLANT user. The default name of the
export is pre_250.dmp. Make a note if you change the name as you will
require this file later on when you import into the new ORACLE10g
database.
Oracle 7 systems exp73 system/manager@totalplant

file=pre_250.dmp buffer=3000000
owner=totalplant compress=n
log=common.log
8i/9i/10g/11gR2/12c exp system/BFLEX file=pre_250.dmp
systems buffer=3000000
log=common.log
NOTE: Copy the pre_250.dmp file to the D:\BFX_DB.folder of the Oracle
system that will host the new Business FLEX database.
Creating schema export for TOTALPLANT from OM Pro database

Perform the following steps to create the schema export for migration.
1. Change to a drive/directory large enough to hold an export of the existing
database.
2. Perform an export for the TOTALPLANT user. The default name of the
export is pre_250.dmp. Make a note if you change the name as you will
require this file later when you import into the new Oracle 10g database.
Oracle 7 systems exp73 system/manager@totalplant

file=pre_250.dmp buffer=3000000
log=common.log grants=n
8i/9i/10g/11gR2/12c exp system/BFLEX file=pre_250.dmp
systems buffer=3000000 grants=n
log=common.log
NOTE:
If the export fails in Oracle 11.2.0.1 server with the following error, refer to the
section Appendix D Exporting the Business FLEX 240 database from Oracle
11.2.0.1.0.
EXP-00008: ORACLE error 1455 encountered
ORA-01455: converting column overflows integer datatype
EXP-00000: Export terminated unsuccessfully

Export PRD Database
The ORA-1455 is caused by bug 9306119, which was fixed in

the Oracle Patch Set Update 11.2.0.1 patch 12.
Exporting schemas for NON-TOTALPLANT

Perform the following steps to Export Non-TOTALPLANT Schemas that
contains objects:
D:\BFX_DB.
3. Run the export command.

cmd> export.cmd
Following information needs to be prompted as part of the execution of the
export command file:
Password for Oracle user SYSTEM (default is MANAGER).
DB alias for Oracle (default is TOTALPLANT).
The name of the USER to be exported.
A user specific dump file is created - named USER.dmp, where USER is
the name of the USER that was exported.
NOTE: Copy the User.dmp file to the D:\BFX_DB.folder of the Oracle system
that will host the new Business FLEX database.

Export PRD Database

Upgrade the Business FLEX Database
Upgrade the Business FLEX

Database
Overview
Uniformance has been a prerequisite for Business FLEX and users who are
following the Business FLEX 250 Database Upgrade, have the PRD Database
instance and Uniformance in their systems.
The following table outlines the steps that sites can follow to upgrade their
existing Oracle database to Business FLEX 250 depending on their starting point.
ATTENTION: Business FLEX 250 database migration is recently initiated through
a single database command file. This command file is capable of handling a
migration from as far back as Uniformance 150.1.6.
Upgrade process
The following table outlines the various starting points and prerequisites to
update to Business FLEX 250:
Starting Point Prerequisites
Business FLEX 140 system This upgrade scenario requires the transport of the PRD
-using new server hardware dump file from one system to another. Follow the steps
outlined in Export PRD Database, followed by Prepare for
the Business FLEX 250 database, Creating the Business
FLEX Database and Upgrade Pre-250 Business FLEX
database to 250.
There will be work needed to decommission the old Oracle
server which is beyond the scope of this guide.
Business FLEX 140 system This upgrade scenario requires the transport of the PRD
-converting to Unicode dump file from one system to another. Following the steps
database outlined in Export PRD Database, followed by Prepare for
the Business FLEX 250 database, Creating the Business
FLEX Database and Upgrade Pre-250 Business FLEX
database to 250.
Earlier Business FLEX This upgrade scenario requires the transport of the PRD
systems like dump file from one system to another. Follow steps
BF200/201/210/220/230/240 outlined in Export PRD Database, followed by Prepare for
-using new server hardware the Business FLEX 250 database, Creating the Business
FLEX Database, and Upgrade Pre-250 Business FLEX
database to 250.
There will be work needed to decommission the old Oracle
server which is beyond the scope of this guide.

Starting Point Prerequisites
Business FLEX 230/240 This is a simple upgrade scenario. Follow the steps
system outlined in Prepare for the Business FLEX 250 database
-using same server hardware and Upgrade Pre-250 Business FLEX database to 250.
NOTE: This guide does not discuss how to install Oracle11gR2/12c or remove
previous versions of Oracle. Refer to the Oracle Database Installation Guide
(BFO-INS) for details.
Checklist for upgrade of Business FLEX database

Refer to Go to
Enable User Based Shift Rotation feature 30

Prepare for the Business FLEX 250 database 30
Creating the Business FLEX Database 35
Upgrade Pre-250 Business FLEX database to BF250 39
Post-Upgrade Remove ACM entry from IP_APPL table 41
Post-Upgrade Migrating the users 37
Enable User Based Shift Rotation feature

If you are upgrading from the previous release to BF 250 and in the existing
database, if you have the User based Shift Rotation Configuration feature
enabled, then perform the following steps.
Enable User based Shift Rotation Configuration for an existing user

You can enable User based Shift Rotation configuration for an existing user in
one of the following ways.
Install EDS and continue the installation process (see Scenario 1)
Ignore error messages and continue the installation process (see Scenario
2)
Scenario 1
Perform the following steps to install EDS first and then continue with the
installation process:
1. Install EDS. For more information on the installation of EDS, refer to
Experion Desktop Server installation guide.
2. Configure Oracle Database Gateway. For more information about how to
configure Oracle Database Gateway, refer to BFO-INS guide, Appendix
C Configuring Oracle Database Gateway for ODBC section.
3. Upgrade the Business FLEX Database

4. If the SQL server name has changed, then perform the following step.
a. Browse to the following path D:\BFX_DB and run the following
script in SQL Server (EDS).
Use ExperionCoreServices;
insert into SecurityApplication values
('OPMGMT',0,'Operations Management');
insert into SecurityRole
values('BFShiftAdmin',GETDATE(),GETDATE(),'Allows to
change Shift Rotation in TPI',1);
insert into SecurityApplicationRoleMap values
('OPMGMT','BFShiftAdmin');
insert into SecurityHierarchyApplicationMap values
('ASSET','OPMGMT');
Scenario 2
Perform the following steps if you are not following the sequence of installation
for EDS:
1. Import the pre-250 BFlex database (see Creating the Business FLEX
database).
2. Upgrade pre-250 Business Flex database to 250 (see Upgrade the
Business FLEX Database).
3. Ignore all the invalid object messages that are displayed while upgrading
and type C in the below screen to continue.

6. Remove the commented line from the compile3.sql file as shown below.

7. Login TPI as TOTALPLANT user.

8. Run the compile3.sql command.
Enable User based Shift Rotation Configuration for a new user

Perform the following steps.
3. Upgrade the Business FLEX Database.
4. Browse to the following path D:\BFX_DB and run the TPI_changes.sql
file as a TOTALPLANT user.

a. Enter the user name for SQL Server that you had configured in
ODBC database.
b. Enter password for SQL Server user.
5. Run the following script in SQL Server (EDS).

Use ExperionCoreServices;
insert into SecurityApplication values
('OPMGMT',0,'Operations Management');
insert into SecurityRole
values('BFShiftAdmin',GETDATE(),GETDATE(),'Allows to
change Shift Rotation in TPI',1);
insert into SecurityApplicationRoleMap values
('OPMGMT','BFShiftAdmin');
insert into SecurityHierarchyApplicationMap values ('ASSET','OPMGMT');
Prepare for the Business FLEX 250 database
Copying the Business FLEX database scripts

already created it. By default the target drive letter for the \BFX_DB folder is
D. Therefore the directory must be called D:\BFX_DB
2. Insert the Business FLEX 250 Software DVD into your DVD drive.
3. Use Windows Explorer to navigate to the Business FLEX Database
folder on the Business FLEX 250 DVD.
4. Select and copy all files to the Business FLEX working area, by default this
is D:\BFX_DB.
NOTE: Copy the files to the D:\BFX_DB.folder of the Oracle system that will
host the new Business FLEX database.
the working area.

Editing the Business FLEX database scripts

Perform the following steps to review or update the settings.cmd file:
1. Using Windows Explorer, navigate to the Business FLEX 250 working area.
By default, this is D:\BFX_DB.
2. Make changes to the parameters in the settings.cmd file as described.
NOTE: Spaces are not allowed around the = sign in the variable
definitions. In addition, trailing spaces are not allowed nor are trailing
backslashes \in paths.
Verify the HOSTNAME of the Oracle server.
If no value is specified, the script defaults to the name of the localhost.
Verify the Drive and directory for the Business FLEX database files.
If no value is specified, the script defaults to the following folder location
D:\BFX_DB.
Verify the Instance Identifier (SID) of the new database.

If no value is specified, then the script defaults to the Business FLEX
default PRD
set ORACLE_SID=PRD
Verify the location of the Oracle software files (ORACLE_HOME) and
instance specific files (ORACLE_BASE).
If no values are specified, then the script defaults to:
For Oracle 11gR2:
set ORA_HOME= D:\app\administrator\product\11.2.0\dbhome_1
set ORA_BASE= D:\app\administrator\product\11.2.0
For Oracle 12c:
set ORA_HOME= D:\app\administrator\product\12.1.0\dbhome_1
set ORA_BASE= D:\app\administrator\product\12.1.0
Verify the release of the Oracle database:
For Oracle 11gR2, set Release=11g
For Oracle12c, set Release=12c
Verify the Historian Version that is used with the system.
If the site uses PI Historian then
set Histversion=PI
If the site uses Uniformance version prior to PHD300, then
set Histversion=Pre300
If the site uses Uniformance version which is PHD300 or Post PHD300,
then
set Histversion=Post300
Verify the user for Background Processes.
If no value is specified, then the script defaults to the name of the
UNISERVER
set OraBgUser=UNISERVER

NOTE: If a domain user is used for running the background processes, then
the full username such as <Domain>\UNISERVER must be mentioned.
Verify the schema owner, schema password, DB alias.
If no value is specified, then the script defaults to:
set OraSchemaOwner=Totalplant
set OraDbAlias=Totalplant
Determine if the existing schema must be backed-up:
if no value is specified, then the script defaults to:
set BackupOldSchema=NO
Determine if the database is migrated to Unicode.
If the site wishes to make the database Unicode compliant then the
following value must be set:
set CHARSET=AL32UTF8
If the site DOES NOT WANT to make the database Unicode compliant
then the following value must be set:
set CHARSET=WE8MSWIN1252
Verify the TNS connection information to the Uniformance database.
Sites that have selected to use PHD as their Historian must enter the
TNSNAMES connection information for the Uniformance database to
allow database synchronization to occur.
If no value is specified, the script defaults to the name of the
Uniformance
set UnfConnectStr=Uniformance
Verify the ISDBUNICODE.
This environment variable is valid from BF200 database onwards.
Databases above BF200 must run this environment variable to migrate to
Unicode.
By default, this is set to NO.
If the existing database or dump is Unicode set:
ISDBUNICODE=YES
If the existing database or dump is Non-Unicode set:
ISDBUNICODE=NO
ATTENTION:
As the upgrade process requires an idle database to upgrade
successfully, Application Server must be shutdown.
Refer to Prerequisites for details.
As the upgrade process requires an idle database to upgrade
successfully, Message Log Server must be shut down.
Refer to Appendix B Kill MSGLOGSERVER Job for details.
NOTE: In Business FLEX 250, TPI supports creation of windows authenticated

users. Oracle has the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\<ServerHome>\OSAUTH
_PREFIX_DOMAIN, which controls if the domain name is mandatory for
windows authenticated users. If this registry key is set to True, then the windows
authenticated users created from TPI should also have domain name mandatory.

To enable this, a lookup value OSAUTH_PREFIX_DOMAIN is created in

database. If this lookup value is True, then the domain name is mandatory for
windows users. This lookup value is populated during the database installation
based on the Oracle registry key
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\<ServerHome>\OSAUTH
_PREFIX_DOMAIN. The lookup value is True if the registry value is True. Else,
the lookup value is False.
If the value of the registry key is changed after the database installation, the
lookup value in TPI has to be modified accordingly.
Creating the Business FLEX database
Before you begin

ATTENTION: This is required for all sites that are moving to new hardware /
Unicode.
1. Copy the pre_250.dmp file, CUSTOMTBS.SQL, and the UsersRolesPer.sql
script file to the Business FLEX working area. By default this folder is
D:\BFX_DB.
Creating the Business FLEX database

ATTENTION: If the Database server machine is of 64-bit, and if Oracle Server
Software installed is 64-bit and Oracle Client installed is of 32-bit, then there could
be some issues while migrating the Business FLEX database in the same server.
Please follow the below steps in this scenario.
1. In the Server machine, remove the Oracle client path from ENVIRONMENT
VARIABLE PATH
2. Create and Migrate the Business FLEX database.
3. Include the Oracle client path to the ENVIRONEMT VARIABLE PATH
removed in step 1 above.
Perform the following steps to create the Business FLEX database:

D:\BFX_DB.
3. Run the database creation/import command file as Run as Administrator.

BfxDbImport
The environment variables set is displayed. Press any key to continue. A
message is displayed prompting you for the password.

4. Enter the password.

NOTES:
1. The default password is BFLEX. You can change the password, if
required. In addition, you can have different passwords for individual
users such as SYS, TOTALPLANT, and SYSTEM.
2. Make a note of the Oracle software owner password that you have
entered during the Oracle Server installation.
The command file creates the database instance and imports that database
contents from the pre_250.dmp file.
If the script aborts with error messages, you must stop and determine the
cause of the error.
If unacceptable errors are found in any of the log files, the name of the log
file and the error messages are reported on the screen.
If you are unable to determine the cause of the error, contact Honeywell TAC
for assistance.
NOTES:
1. At this point of time, following objects may be invalid if you are upgrading
Business FLEX 120 or 130 databases to BF200, 201, 210, 220, 230, 240 or
241 or 250. This is not an issue. The following objects are compiled with the
BF200, 201, 210, 220, 230, 240, 241, 242, 250 migrations using the script
Bfora9prep.sql.
PA, PBINTERFACE,
PBSEQUENTIAL,
PBWRITEBACK,
PBUTILITY,
PHDSQL Body, and

Production tracker functions or procedures.

2. Ignore the following errors when running the import command file
BfxDbImport. The following errors are displayed in the Common.log file.
IMP-00015: Following statement failed because the object already exists.
IMP-00041: Warning: object created with compilation warnings
IMP-00003: ORACLE error 1435 encountered
IMP-00017: Following statement failed with ORACLE error 12913.
ORA-01435: User does not exist
ORA-12913: Cannot create dictionary managed tablespaces
ORA-00001: Unique constraint violation.
ORA-30019: Illegal role back segment operation in automatic undo mode.
TIP:
The script aborts if the database instance or database directories already
exist.
To fix this, you can do either of the following:
Enter a different ORACLE_SID in the settings.cmd.
Or
Remove the existing database instance using the oradim.exe utility,
and then remove the database directories and files. By default, the
database directories and files are -
<ORA_BASE>\admin\<ORACLE_SID>
<ORA_BASE>\oradata\<ORACLE_SID>
<ORA_HOME>\database\*<ORACLE_SID>.ora
Importing Non-TOTALPLANT schemas that contains objects

Perform the following steps to import non-TOTALPLANT schemas that contain
objects:
D:\BFX_DB.
3. Ensure that the user specific dump file (user.dmp) created previously is
located in the Business FLEX 250 working area and where USER refers to
the user name initially exported.
4. Run the import command.
cmd> import.cmd
The following information needs to be prompted for as part of the execution
of the import command file:
Password for Oracle user SYSTEM (default is MANAGER).

The name of the USER to be imported

The password of the USER to be imported
DB alias to which the USER is imported
The dump file name (format is User.dmp)
Upgrade Pre-250 Business FLEX database to 250
Prerequisites
The Application Server is installed as a Windows service (IP_Schedule.exe).
Before continuing with the database upgrade, you must stop the services.
Perform the following steps to stop each service:
1. At each Application Server node, open the Services application in the
Windows Control Panel.
For Windows NT: Start> Settings> Control Panel> Services.
For other Windows versions: Start> Settings> Control Panel>
Administrative Tools> Services.
2. Stop the service named Uniformance Scheduler xxxx for Business FLEX pre-
200.
Stop the service Business FLEX Application Server Scheduler xxxx for
Business FLEX 200 release and later.
Where xxxx refers to the TNS name selected for the ORACLE connection.
NOTE: Post Business FLEX 120 users will see Uniformance 200 Scheduler
xxx.
On receiving the stop signal, the Application Server tries to stop all the
running processes. A warning message may be displayed stating that the
service is not responding to the stop command.
3. Click OK to ignore the message and wait a few minutes before attempting to
stop the service again.
4. Perform the following steps to prevent the Scheduler and associated
processes from restarting when you restart during the database
upgrade/install:
Set the Uniformance Scheduler xxxx and Business FLEX Scheduler xxxx
services to Manual startup.
Open the TPI application and disable the configured "background
processes".
5. Verify that the Message Log Server job is not running. Refer to the section
Kill MSGLOGSERVER Job for more details.

6. Shutdown connections to the database. Ensure that there are no active users
on the system. This includes Web applications, TPI forms, and even PHD.
Running the scripts for migration

Perform the following steps to migrate to Business FLEX database:
1. Open a Command Prompt window.
2. Navigate to the Business FLEX 250 working area.
By default, this is D:\BFX_DB
3. Run the database migration command file
BfxDbUpgrade
4. The upgrade command file prompts to enter passwords for the SYS,
SYSTEM and TOTALPLANT users. You can use the default password.
5. The database migration script prompts you to enter a version of Business
Flex you want to update to.
The following message is displayed Upgrade to which version of Business
FLEX (120/130/140/140.2/200/201/210/220/230/240/241/242/250).
Mention the version to upgrade the database.
If you do not mention a version, the database is upgraded to 250 version, by
default.
The length of time required for this process depends entirely on the speed
and memory configuration of the server that is running Oracle. The minimum
time range is 10 minutes and the maximum time depends on the size of the
data in the site.
During this migration step, some of the log files may show compilation
errors. Ignore the errors. All the objects are compiled at the end of the step.
NOTE: If you get an error "ORA-02260: table can have only one primary
key" during the execution of V40010A.SQL and V40010B.SQL scripts,
ignore it. These scripts are executed when the database is migrated from
earlier versions to BF250.
6. If the script ends with error messages, you must stop and determine the cause
of the error.
If unacceptable errors are found in any of the log files, the name of the log
file and the error messages are displayed.
If you are unable to determine the cause of the error, contact Honeywell TAC
for assistance.
7. Verify that the Business FLEX database is upgraded correctly. The following
message is displayed:
"Business FLEX Database upgrade completed successfully"
Version - BFX BF250.0.00

Alternately, you can check the upgrade from a SQL PLUS command.
sqlplus totalplant/BFLEX@totalplant
When in SQL PLUS, type:
SELECT prodline, ver_name from ip_appl_ver;
you must see the following:
BFX BF250.0.00
8. The log file deletion begins, and until the deletion is complete, it is
recommended not to close the command prompt.
NOTE: The log file deletion process may take 20 to 25 minutes to complete.
Dropping database migration working tables

ATTENTION:
This procedure is optional.
Connect as a System Administrator and grant the necessary permissions to the
schema owner to perform this task.
Perform the following steps to drop database migration working tables:

Drop the temporary tables which were created during the migration process. Run
the DropWorkingTables script connected as the schema owner.
at the SQL Plus command, execute the following:
grant drop public synonym to TOTALPLANT;
conn totalplant/totalplant@totalplant
@DropWorkingTables.sql
At the DOS prompt, execute the following to revoke the previously applied
permissions:
revoke drop public synonym from TOTALPLANT;
Post-Upgrade Remove ACM entry from IP_APPL

table
If you are migrating Oracle database from OM Pro 310 to OM Pro 320, then after
the database migration is completed, remove the entry for ACM application from
the IP_APPL table, using the below statement
Delete * from IP_APPL where APPL_NAME = ACM;
Grant permissions to run the Business FLEX

application server
Several authentication-related procedures must be completed for the Applications
Scheduler (IP_Schedule.exe) to operate correctly. Ensure that you have
completed the procedures explained in the Business FLEX Installation Guide,

Business FLEX Application Server sections post-installation instructions.

Specifically, see Granting Privileges to Application Server in the Post-
Installation/Upgrade Requirements subsection.
Post Upgrade Migrate the users

NOTE: This section is not applicable for Business FLEX 240 migration and is
applicable only for migration of Business FLEX 230 or prior releases.
In Business FLEX 240, a few new fields are added in the User Profile
Configuration Form such as the type of authentication and status. In order to
update the existing users, perform the migration steps.
Perform the following steps to migrate all the users from the previous database to
TPI User Configuration form.
1. Open the command prompt window.
D:\BFX_DB.
3. Open SQL PLUS (sqlplus totalplant/BFLEX@totalplant).
4. Run the user migration script (Users_Migration.sql).
NOTE: Please check that the users_migration log file is created in the same
folder for the correctness of the migration. If the migration script is not able to
migrate due to some reasons, it is recorded in the log file so that it can be
rectified/migrated/created manually in the TPI User Profile Configuration form.
The user migration script migrates only the Active users in the database at the
time when the script runs.
All the newly migrated users have Migrated Users in the description field.

Post Upgrade Enable Database Synchronization with PHD300 or later
Post Upgrade Enable Database

Synchronization with PHD300 or
later
Overview
ATTENTION:
This section is required for sites that want to use PHD300 or later as the site
Historian.
The following steps are involved in reading ip_tag related data from PHD
Database.
The following table data are read and update from PHD to Business FLEX
instance tables.
IP_TAG
IP_TAG-SRC
IP_ENG_UNIT
IP_ENG_UNIT_TYP
NOTE: The IP_CORRLTN_TBL and IP_CORRLTN_TBL_DETAIL are

handled separately through TPI. You can enter the correlation details in TPI >
Process History > 1D Correlation Configuration Form. You can edit the fields
and enter the details.
Checklist for database synchronization with PHD

The following table lists the order of tasks that must be performed to enable
database synchronization with PHD:
Refer to Go to
Configuring Database 42
Verifying Application Servers user is registered with PHD Database 42
Configuring the Background Processes 43

Configuring the database

Verify the parameters OraBgUser, OraDbAlias, BfxDir present in
settings.cmd. Refer to Editing the Business Flex Database Scripts to ensure that
OraBgUser, OraDbAlias, BfxDir is properly set.
Perform the following steps to configure the database for synchronization:

1. Using Windows Explorer, navigate to the Business FLEX 250 working area.
By default, this is D:\BFX_DB.
2. Open Command Prompt and run the following:
BuildDBforEclipse.cmd <<Enter>>
This command creates the package called READDATAFROMUNF and creates
six packed procedures. It also updates the configuration details in
IP_APP_PROCESS_CNTRL, IP_APP_PROCESS_EXEC,
IP_APP_PROCESS_CNTRL_PARAM and IP_LKP.
Verifying applications server user is registered with

PHD database
In PHD Server, open Control Panel Computer Management Local users and
groups Groups.
The following three groups are available: Product Administrator, Engineer and
Operator.
The Application Server user should be registered with any of these groups. If not,
add the user under Operator group, as the access to the applications requires read-
only permissions only.

Configuring the background processes

After successfully configuring the database as mentioned in the section
Configuring the Database, you must configure the ReadDatafromEclipse
background process in the Application Server Configuration form.
To access the form:
1. Start Business FLEX TPI.
2. Select the Application Management option.
3. Select and click the Applications Server Configuration form.
ReadDataFromEclipse
This executable reads data from the PHD database and updates the respective
tables in Business FLEX database. This procedure reads and updates only those
records which are changed in PHD database after last run of this process.
The following is a sample of background process configuration.
Following are the input parameters:

CONNNECT_STRING: /@datasource (Mandatory)
DELETE_YES: Yes or No (Mandatory)
This option is No by default. If you change this option to Yes, this process
deletes the rows in BFlex database which are no longer present in PHD database.
This option should be No, if sites decide to retain data in the Business FLEX
tables even though it is not present in PHD Database.

NOTE:
The DELETE_YES parameter is not required for correlation table
synchronization. The correlation table synchronization is slightly different from
the synchronization of tags and units. Correlation table synchronization performs
delete, update, and insert operations of synchronization together.
The Business FLEX TPI has a user interface to update the tables. If these tables
are updated manually, insert and update operations may fail. Hence, the
executable performs all three operations of synchronization together.
CMDLINE_SWITCHES:
SQL Server host name: -h hostname (Mandatory).

SQL Server host name is the system where PHD SQL server database is present.
Process Name: -pn processname (Optional). Default value is
readdatafromeclipse
Log Directory: -ld log directory (optional).
Log File: -lf filename (optional). Default value is processname_DDMMYY.log
Complete Reset: -md (optional). In normal case, readdatafromeclipse selects
only those tags for synchronization which are updated after the last run of it. But
if the switch is present then it considers all the tags for synchronization.
ATTENTION: On the Application Server Configuration form, if the Program Type
is DB Proc, then the sequence number must not be provided and the Sequence
field on the Parameters tab must be left blank.
If the Program Type is OS Program, then defining the sequence number in the
Sequence field is mandatory.
Switch for synchronizing 1D correlation tables with PHD Server

Corr (optional) By default, ReadDataFromEclipse does not synchronize the
1D correlation tables. However, if the corr switch is enabled; the 1D correlation
table data is synchronized. The corr switch deletes all the extra data from the
correlation tables and retains only the data that is present in PHD server. The
command line switch DELETE_YES does not have any effect on the behavior of
this switch.
If corr switch is enabled, then do not use the TPI form for inserting correlation
records. This is because; the executable deletes those records that do not match
with the entries in the PHD server.

Appendix A Recent Changes in Business FLEX
Appendix A Recent Changes in

Business FLEX
Summary
Starting with Business FLEX release 200 and Uniformance PHD release 210 the
organization of the Oracle database changed significantly. Previously, a single
Oracle instance was used for both Uniformance and Business FLEX, and this
Oracle instance was created by Uniformance and extended by Business FLEX.
In Business FLEX 200 (and 201, 210, 220, 230, 240, 241, 242 and 250) these
two product lines maintain separate Oracle instances. This section of the guide
discusses this change in the use of Oracle, and addresses a few considerations
from the perspective of staff responsible for installing, maintaining, and
supporting Honeywell products.
Business FLEX 250 release includes common installation kit that provides an
option to install BFLEX 250 Database on Oracle 11g/12c software. In addition,
Business FLEX 250 database installed on Oracle11g/12c software provides
redundancy support using Oracle Real Application Clusters. Refer to the Oracle
Real Application Cluster Guide for details.
All new installations of Business FLEX Oracle database are made Unicode
compliant. The existing sites can either move to a Unicode database or retain the
existing non-Unicode database.
Oracle versions
Business FLEX 250 requires Oracle 11.2.0.3.0 or Oracle 12.1.0.2.0. This is the
minimum version of Oracle that supports Business FLEX 250.

Oracle database organization

Prior to Business FLEX 200, Uniformance and Business FLEX applications
shared a single Oracle instance, by default called PRD internally and
TOTALPLANT externally. The scripts required to create this database instance
were delivered with Uniformance. Business FLEX releases extended the
Uniformance database instance with additional tables, views, procedures, and
data.
Starting with Business FLEX release 200, the Uniformance PHD and Business
FLEX product lines maintain separate Oracle database instances. These two
database instances can reside on a single Oracle server which is the
recommended configuration, or can be installed on separate servers.
The new Uniformance instance is called UNF by default, and contains just the
information required for PHD. The new Uniformance instance does not support
site-specific database objects.
The existing PRD/TOTALPLANT instance will become the Business FLEX
instance. The Business FLEX instance will contain essentially all the information
currently found in the merged database, which includes copies of selected tables
found in the Uniformance instance. The Business FLEX instance continues to
support site-specific database objects. For sites that are migrating from an earlier
version, the existing merged instance will become the Business FLEX instance,
and a new Uniformance instance will be created.
As part of this move, the Business FLEX development group will assume
responsibility for the PRD/TOTALPLANT instance. In conjunction with this
transition of ownership, selected tables and business logic relating to PHD
configuration and operation will be migrated from the existing TOTALPLANT,
to a new Uniformance instance named UNF.
Installation of Business FLEX oracle database

The Oracle Database Installation Guide for Business FLEX has been developed
to reflect the parallel paths that a user may follow to arrive at the point when they
are ready to install the Business FLEX Oracle database:
1. A PHD user that wishes to also install applications.
2. An application user who has chosen to use a different historian than PHD.
The installation guide contains the steps required to install Oracle for the case
when Oracle has not been installed already as part of the Uniformance database
installation. Refer to the Oracle Database Installation Guide for details.

Database interconnections
PHD tag names and engineering units are maintained in one Oracle instance, and
automatically copied to the other using Oracle database links between the two
Oracle instances.
The master tables and business logic relating to PHD configuration and operation
are maintained within the Uniformance database instance. The Business FLEX
database instance also contains some of these same tables. The contents of these
common tables are maintained by Uniformance. The Business FLEX database
installation process will create Oracle database links between the two instances.
Therefore, when tags (and other information) are edited in the Uniformance
instance, the changes are automatically propagated to the Business FLEX
instance.
NOTE: These links are created if the site has specified PHD as the historian type
used in the SETTINGS.CMD file.
These links keep the Business FLEX database instance up-to-date with process
tag and engineering unit information. As a result, applications continue to have
access to PHD tags and engineering units in the Business FLEX database
instance and therefore need not be changed.
User of the Business FLEX applications can view tag configuration from the
Business FLEX TPI but configurations changes can only be done using the
Uniformance TPI.
Use of IP_APPL_VER and owner columns

Business FLEX database patches currently make heavy use of the owner column
in the IP_APPL_VER table. This has continued in the Business FLEX 200, 201,
210, 220, 230, 240, 241, 242, and 250 releases. In previous releases, throughout
the TOTALPLANT schema there were a number of other tables that identify
owners (UNF or BFX). Starting with Business FLEX 200, 201, 210, 220, 230,
240, 241, 242, and 250 the UNF entries in the TOTALPLANT database are
changed to BFX.
Security
The Uniformance and Business FLEX Oracle instances continue to provide the
same level of security as before. However, users require separate Oracle accounts
to access these two database instances, and these accounts are maintained
independently. A site may choose to configure Oracle authentication using
Windows Integrated Security. This is still required to create two accounts for
each user who requires access to both Uniformance and Business FLEX.
Each of the two TPI instances is connected to a different Oracle database
instance. Therefore, they have independent security and user accounts.

Plant Reference Model

Prior to Business FLEX 200 the Plant Reference Model (PRM) was maintained
as part of Uniformance. Effective with Business FLEX 200/Uniformance 210 the
PRM is distributed and maintained as part of Business FLEX. Sites that license
only Uniformance PHD no longer receive the PRM.
NOTE: There are no changes in the structure or behavior of the PRM and
applications that currently work with the PRM continue to work without any
change.
Migration considerations for existing sites

A migration path is provided for all releases back to Uniformance 150.1.
Migration tools are provided on the Business FLEX software media. The
Business FLEX development team has assumed the Oracle database installation
and migration scripts originally delivered with Uniformance 202. These scripts
have been merged with the Business FLEX installation and migration scripts
from Business FLEX 140 to provide users with a single set of scripts that can be
used for pursuing either an install or upgrade path.
Business FLEX 250 supports application users migrating from Uniformance
150.1 to Business FLEX 250.
A version prerequisite check is conducted early in the migration process to
ensure that the database meets the minimum supported version prior to starting
the migration process. Users with system early than Uniformance 150 are
required to contact Honeywell to obtain the necessary scripts and procedures to
upgrade to Uniformance 150.
Uniformance 210 is the only Uniformance release that is supported with Business
FLEX 200 and 201. Uniformance 215 supports Business FLEX 210, 220, 230,
240, 241, 242, and 250. Migration to Business FLEX 250 requires two steps:
1. To upgrade to Uniformance 215.
2. To upgrade to Business FLEX 250.
This will ensure that their applications will continue to function as expected.
The Business FLEX database upgrade procedure includes information for sites
that are beginning the procedure from different starting points. In all cases, the
starting point for the Business FLEX migration is the dump file created during
the Uniformance 210 upgrade process. Refer to the Exporting the PRD database
for more information about how to create a dump file, if needed.
NOTE: Some sites have LIMS and other Business FLEX applications that use
Oracle, but do not use PHD.

Migrating from releases prior to Uniformance 202 or Business FLEX 140 will
require upgrading Oracle to 10.2.0.5.0 as part of the release activities. The
standard Business FLEX migration procedures do not include information related
to the installation/migration of Oracle versions on the database server as the
Oracle migration step is addressed by the Uniformance upgrade.
At the end of a successful Uniformance / Business FLEX upgrade, sites will have
two Oracle database instances on a single server computer (optionally two
servers).
CAUTION Over time, unused database objects may be removed in future releases. A
procedure is established with Product Management to inform interested users
of the pending removal of items well in advance of a release.
It is expected that the TOTALPLANT schema will continue to be used by some

customers as a repository for site-specific custom objects.
The database upgrade associated with Business FLEX 200, 201, 210, 220, 230,
240, 241, 242, and 250 is no longer included in the Business FLEX Installation
Guide. Refer to the section Upgrade the Business FLEX Database for details.
The migration process maintains the user accounts and passwords and will not
reset the passwords for Business FLEX users as the Uniformance 210 migration
will.


Appendix B Kill MSGLOGSERVER Job
Appendix B Kill
MSGLOGSERVER Job
Overview
Killing the MSGLOGSERVER requires that you run queries as the Oracle user
that submitted the MSGLOGSERVER job.
The user is validated in Oracle at the operating system level. You must log on to
Windows with adequate permission to run the Uniformance Windows Scheduler
service and kill the MSGLOGSERVER job.
Determining the correct user

Perform the following steps to determine the correct Windows user to kill the
Message Log Server on your system:
1. Go to the Application Server node and open the Services application in the
Windows Control Panel.
For Windows NT: Start> Settings> Control Panel> Services.
For other Windows versions: Start> Settings> Control Panel>
Administrative Tools> Services.
2. To determine the configured username, check the Logon tab in the Properties
of the service Uniformance Scheduler xxxx. xxxx refers to the TNS
name selected for the ORACLE connection.
Killing the MSLOGSERVER

Before continuing with the upgrade, perform the following steps to kill the
Message Log Server job.
Connecting to Oracle
Perform the following steps to connect to Oracle:
1. At the ORACLE database node, log on to Windows as the user identified in
the previous step l.
NOTE: The user may be a local or a domain user.

2. Open a command prompt window and connect to Oracle by typing the

following:
sqlplus /@totalplant
Run the script

declare
a int;
begin
dbms_pipe.pack_message('STOP');
a:=dbms_pipe.send_message('Uni_MsgLog');
commit;
end;
/
Finding the MSLOGSERVER job information

1. At the SQL prompt, type in the following query in totalplant login:
SELECT B.SID, A.JOB, A.WHAT, A.SCHEMA_USER
FROM DBA_JOBS A, DBA_JOBS_RUNNING B
WHERE B.JOB = A.JOB
AND UPPER(A.WHAT) LIKE 'MSGLOGSERVER%';
2. Note the SID (Oracle session ID) and the JOB
SID ____________JOB: ____________________
If the following message appears, then the MSGLOGSERVER job is not
running and you may skip the following steps:
no rows selected
Finding the Oracle session associated with the MSGLOGSERVER

job
1. Enter the following and substitute <SID> with the SID revealed in step 4.
SELECT SERIAL# FROM V$SESSION WHERE SID = <SID>;
2. Note the SERIAL#:
_____________________________
Removing the MSGLOGSERVER job

Perform the following steps to remove the MSGLOGSERVER Job:
1. Enter the following and substitute <JOB> with the JOB revealed in step 4.
EXEC DBMS_JOB.REMOVE( <JOB> );
Killing the Oracle session associated with the MSGLOGSERVER job

Perform the following steps to kill the Oracle session associated with the
MSGLOGSERVER Job:

1. Enter the following and substitute <SID> and <SERIAL> with the SID and
SERIAL revealed in the previous steps.
ALTER SYSTEM KILL SESSION '<SID>,<SERIAL>';
There may be a pause when ORACLE attempts to kill the session. It may not
take more than five minutes for the MSGLOGSERVER to stop running.
ORACLE will eventually respond with the following error if the session
being killed is performing a non-interruptible task. The error indicates that
the session will be killed when it completes its task. This error can be
ignored. Continue to the next step.
ERROR at line 1:
ORA-00031: session marked for kill
Verifying that the MSGLOGSERVER is no longer running

Perform the following steps to verify that the MSGLOGSERVER is not running:
1. Enter the following query to verify that no jobs are listed:
SELECT B.SID, A.JOB, A.WHAT, A.SCHEMA_USER
FROM DBA_JOBS A, DBA_JOBS_RUNNING B
WHERE B.JOB = A.JOB
AND UPPER(A.WHAT) LIKE 'MSGLOGSERVER%';


Appendix C Sort Unicode Databases
Appendix C Sort Unicode

Databases
Overview
This section explains on the type of sorting and the language specific sorting
supported by Oracle.
Binary sort
The most common way to sort the character data is to order them by their
numeric binary codes as defined by the character encoding scheme. This is
achieved by using Binary sort. It is the quickest method of sorting in the database
because no special processing is required on sorted values. Binary sorts produce
reasonable results for the English alphabet because the ASCII and EBCDIC
standards define the letters in ascending numeric value. When characters used in
other languages are present, a binary sort generally does not product reasonable
results.
Monolingual linguistic sort

Linguistic sorts provide an alternative sort technique that sorts characters
independently of their numeric values in the character encoding scheme (the
culturally expected ordering). A linguistic sort operates by replacing characters
with numeric values that reflect each character's proper linguistic order. These
numeric values are found in a table containing major and minor values.
With monolingual sorting, Oracle makes two passes when comparing strings.
They are:
1. To compare the major value of the entire string from the major table.
2. To compare the minor value from the minor table.
Each major table entry contains the Unicode codepoint and major value. Usually,
letters with the same appearance will have the same major value. Oracle defines
letters with diacritic and case differences for the same major value but different
minor values. Sorting with two levels is limited because many languages have
properties that cannot be sorted in two levels. Monolingual Linguistic Sort, as the
name implies, sorts data in one language order. It can support only around 1000
characters, and therefore, cannot perform sorts for Chinese, Japanese and Korean
Languages.

The following is a list of monolingual sorts supported in Oracle Database.

ARABIC HEBREW
ARABIC_MATCH HUNGARIAN
ARABIC_ABJ_SORT XHUNGARIAN
ARABIC_ABJ_MATCH ICELANDIC
AZERBAIJANI INDONESIAN
XAZERBAIJANI ITALIAN
BENGALI LATIN
BULGARIAN LATVIAN
CATALAN LITHUANIAN
XCATALAN MALAY
CROATIAN NORWEGIAN
XCROATIAN POLISH
CZECH PUNCTUATION
XCZECH XPUNCTUATION
CZECH_PUNCTUATION ROMANIAN
XCZECH_PUNCTUATION RUSSIAN
DANISH SLOVAK
XDANISH XSLOVAK
DUTCH SLOVENIAN
XDUTCH XSLOVENIAN
EEC_EURO SPANISH
EEC_EUROPA3 XSPANISH
ESTONIAN SWEDISH
FINNISH SWISS
FRENCH XSWISS
XFRENCH TURKISH
GERMAN XTURKISH
XGERMAN UKRAINIAN
GERMAN_DIN VIETNAMESE
XGERMAN_DIN WEST_EUROPEAN
GREEK XWEST_EUROPEAN
For example, for the German strings, add the

NLS_SORT=GERMAN
to the Registry in the
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0]
in the EDS/Web server (ORACLE_HOME).
Multilingual linguistic sort

This enables us to sort data in more than one language in a single sort. Oracle11g
extends monolingual linguistic sorts with multilingual linguistic sorts. This
enables you to sort additional languages as part of one sort. For multilingual data,
Oracle provides a sorting mechanism based on an ISO standard (ISO14651 -
International String Ordering) and the Unicode 3.0 standard. This is useful for
certain regions or languages that have complex sorting rules or global
multilingual databases. Multilingual linguistic sorts also work for Asian language
sorts ordered by the number of strokes, PinYin, or radicals. Additionally,
ORACLE11g still supports all the sort orders defined by previous releases.

Following is a list of the Asian Multilingual Linguistic Sorts supported in

ORACLE11g:
Basic Name Explanation
JAPANESE_M Japanese sort supports SJIS character set order and EUC
characters which are not included in SJIS.
KOREAN_M Korean sort: Hangul characters are based on Unicode binary
order. Hanja characters based on pronunciation order. All
Hangul characters are before Hanja characters.
THAI_M Thai sort supports swap characters for some vowels and
consonants.
SCHINESE_STROKE_M Simplified Chinese sort uses number of strokes as primary
order and radical as secondary order.
SCHINESE_PINYIN_M Simplified Chinese PinYin sorting order.
TCHINESE_RADICAL_M Traditional Chinese sort based on radical as primary order and
number of strokes order as secondary order.
TCHINESE_STROKE_M Traditional Chinese sort uses number of strokes as primary
order and radical as secondary order.
For example, for the PINYIN order for the Chinese strings, add the
NLS_SORT=SCHINESE_PINYIN_M
Change to a language specific sort
Sorting for Unicode migration and clean installation

Different languages have their own sorting rules. Some languages are collated
according to the letter sequence in the alphabet. Others are collated according to
the number of stroke counts in the letter. In addition, there are languages that are
ordered by the pronunciation of the words.
Changing to a language specific sort

There are different types of sorting available in Oracle. The default type of
sorting is Binary sort and this is used in Business FLEX. If any installation
requires language specific sort, the following changes must be made in the
database.
Add
NLS_SORT = Sorting Type


Appendix D Exporting the Business FLEX 240 database from Oracle 11.2.0.1
Appendix D Exporting the

Business FLEX 240 database from
Oracle 11.2.0.1
Exporting the Business FLEX 240 database

Perform the following steps to install Oracle patch set update 11.2.0.1 patch 12
on the Oracle server.
1. Log on to the server computer using an account that has local administrator
permissions on that computer.
2. Download the following Oracle 11.2.0.1.0 patches from the Oracle metalink
website http://metalink.oracle.com.
Patch: 12393431 For 32-bit server
Patch: 12393432 For 64-bit server
3. Unzip and extract the files to your local drive. For example, <Drive>\
p12393432_112010_MSWIN-x86-64.
4. Ensure that your Oracle database installation is the same release for which
you are applying the patch. In other words, apply these release 11.2.0.1.0
bundle patches only on an Oracle 11.2.0.1.0 database.
5. Apply this patch on top of the 11.2.0.1.0 base release.
6. Backup the current installed database, %ORACLE_HOME% directory, and
the Oracle inventory under C:\Program Files\Oracle Directory.
This is required in case of any issues while installing the patch and also for
restoring the inventory in case of any issues with the patch.
7. Perform a clean shutdown of all Oracle services (database, Oracle listeners,
Oracle agents, etc).
8. Stop the Distributed Transaction Coordinator service (this is not an Oracle
service), if it is running.
9. Set the ORACLE_HOME environment variable to the correct Oracle home
for which you must apply this patch.

10. Go to the directory where you have downloaded the patch.
11. Type the following command to run the Opatch.
12. Inspect the Opatch <timestamp> log file generated in

%ORACLE_HOME%\cfgtoollogs\opatch for any errors.
Completing the installation of Oracle 11.2.0.1.0 patch

12
NOTE: Refer to this section only if you have Created the Business FLEX
Database. Refer to the Oracle Database Installation Guide for more details.
Perform the following steps to complete the installation of Oracle 11.2.0.1.0
patch 12 on the Oracle server.
1. Start the database listener and Oracle instance from the Control Panel.
2. Log on to the database using SQL*Plus as SYSDBA and run catcpu.sql as
follows.
CMD> cd %ORACLE_HOME%\Bundle\Patch12
CMD> sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catcpu.sql
SQL> QUIT

3. Check the following log files in $ORACLE_BASE/cfgtoollogs/catbundle for

any errors.
catbundle_WINBUNDLE_<database SID>_APPLY_<TIMESTAMP>.log
catbundle_WINBUNDLE_<database
SID>_GENERATE_<TIMESTAMP>.log
where, TIMESTAMP is in the YYYYMMMDD_HH_MM_SS format.
4. Execute the following commands to ensure that all dependent objects are
valid after running the catcpu.sql.
NOTE: For large number of objects, this compilation step can take some
time. If you are applying this patch through the Oracle Enterprise Manager
console, a message is displayed asking you to run this compilation script.
> cd %ORACLE_HOME%\rdbms\admin
> sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql
To check for invalid objects, execute the following command.
SQL> SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE
STATUS = 'INVALID';
After you have applied the patch successfully, run the export command
again.

Notices
Documentation feedback
You can find the most up-to-date documents on the Honeywell Process Solutions support website at:
http://www.honeywellprocess.com/support
If you have comments about Honeywell Process Solutions documentation, send your feedback to:
hpsdocs@honeywell.com
Use this email address to provide feedback, or to report errors and omissions in the documentation. For immediate help with a
technical problem, contact your local Honeywell Process Solutions Customer Contact Center (CCC) or Honeywell Technical Assistance
Center (TAC) listed in the Support and other contacts section of this document.
How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software defect or weakness that can be exploited to reduce the
operational or security capabilities of the software.
Honeywell investigates all reports of security vulnerabilities affecting Honeywell products and services.
To report a potential security vulnerability against any Honeywell product, please follow the instructions at:
https://honeywell.com/pages/vulnerabilityreporting.aspx
Submit the requested information to Honeywell using one of the following methods:
Send an email to security@honeywell.com.

or
Contact your local Honeywell Process Solutions Customer Contact Center (CCC) or Honeywell Technical Assistance Center (TAC)
listed in the Support and other contacts section of this document.
Support and other contacts

For support and other contact details, go to http://www.honeywell.com/ps .
World Wide Web Elsewhere
Honeywell Process Solutions website: Contact your nearest Honeywell office.
http://www.honeywellprocess.com/support
For more information
To learn more about Honeywells products or
solutions visit www.honeywellprocess.com or
contact your Honeywell account manager.
Honeywell Process Solutions
1250 West Sam Houston Parkway South

Houston, TX 77042
Honeywell House, Skimped Hill Lane

Bracknell, RG12 1EB
Shanghai City Centre, 100 Junyi Road

Shanghai, China 20051
www.honeywellprocess.com

BFO UPG Oracle Upgrade

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BFO UPG Oracle Upgrade

Uploaded by

Copyright:

Available Formats

Business FLEX 250.

Oracle Database Upgrade

Document ID: BFO-UPG-250

Copyright, Notices, and Trademarks

About Business FLEX

ii Oracle Database Upgrade Guide

Before You Begin 7

Export PRD Database 19

Upgrade the Business FLEX Database 29

Post Upgrade Enable Database Synchronization with PHD300 or

Oracle Database Upgrade Guide iii

Configuring the database 44

Appendix A Recent Changes in Business FLEX 47

Appendix B Kill MSGLOGSERVER Job 53

Appendix C Sort Unicode Databases 57

Appendix D Exporting the Business FLEX 240 database from

iv Oracle Database Upgrade Guide

About the Database Upgrade

What is Business FLEX database upgrade

End user components

Oracle Database Upgrade Guide 1

About this guide

Who should use this guide

Conventions used in this guide

2 Oracle Database Upgrade Guide

In addition, these symbols are used:

Oracle Database Upgrade Guide 3

This page is intentionally left blank

4 Oracle Database Upgrade Guide

Overall upgrade checklist

Export PRD Database 19

Oracle Database Upgrade Guide 5

This page is intentionally left blank

6 Oracle Database Upgrade Guide

Before You Begin

Understanding the Business FLEX database upgrade

Oracle Database Upgrade Guide 7

8 Oracle Database Upgrade Guide

ORACLE Server Host Name

Oracle user name/password defaults

Oracle LISTENER password

Oracle Database Upgrade Guide 9

Oracle prerequisites and considerations

10 Oracle Database Upgrade Guide

Server prerequisites and considerations

Oracle connect strings

Disk space requirements

Oracle Database Upgrade Guide 11

Setting the database files to autoextend reduces some database maintenance as

Pre-Upgrade: Create the Oracle NET configuration

Checklist for creating Oracle configuration files

Copying the Business FLEX database scripts 12

Copying the Business FLEX database scripts

Copying the Business FLEX Oracle NET stub files

12 Oracle Database Upgrade Guide

Oracle Database Upgrade Guide 13

Stopping the Oracle 11gR2/12c listener

Renaming the Oracle NET files

For Oracle 12c, the location is

2. Rename the Oracle Net configuration files.

Editing the Oracle NET configuration files

Updating the listener.ora file

For Oracle 12c:

2. Edit the LISTENER.ORA file.