Transcription

Upgrading EDQ to 12c versionsORACLE TUTORIAL JULY 2017

Table of ContentsIntroduction2Table of Upgrade Paths by Release and Platform3Upgrade Path 1:4From EDQ 11g Using an Oracle / WebLogic Platform Installed Using the OUI to EDQ 12.1.3 Using anOracle / WebLogic Platform4Upgrade Path 217From any Release of EDQ Installed Manually (i.e. Without Using the Oracle Universal Installer) on anOracle / WebLogic Platform to EDQ 12.1.3 Using an Oracle / WebLogic Platform17Upgrade Path 3:30From any Release of EDQ Using an Oracle / Tomcat Platform to EDQ 12.1.3 Using an Oracle /WebLogic Platform30Upgrade Path 4:44From any Release of EDQ on a PostgreSQL / Tomcat Platform to EDQ 12.1.3 Using a PostgreSQL /Tomcat Platform44Upgrade Path 5:60From any Release of EDQ on an Oracle / Tomcat Platform to EDQ 12.1.3 Using an Oracle / TomcatPlatformUpgrade Path 6:6076From EDQ 11g Using an Oracle / WebLogic Platform Installed Using the OUI to EDQ 12.2.1 Using anOracle / WebLogic PlatformUpgrade Path 7:7691From EDQ 12.1.3 Using an Oracle / WebLogic Platform Installed Using the OUI to EDQ 12.2.1 Using anOracle / WebLogic PlatformUpgrade Path 891101From any Release of EDQ Installed Manually (i.e. Without Using the Oracle Universal Installer) on anOracle / WebLogic Platform to EDQ 12.2.1 Using an Oracle / WebLogic PlatformUpgrade Path 9:UPGRADING EDQ TO 12.1.3 OR 12.2.1101115

From any Release of EDQ Using a Postgres / Tomcat Platform to EDQ 12.2.1 Using an Oracle /WebLogic PlatformUpgrade Path 10:115130From any Release of EDQ Using an Oracle / Tomcat Platform to EDQ 12.2.1 Using an Oracle /WebLogic PlatformUpgrade Path 11:130145From any Release of EDQ on a Postgres / Tomcat Platform to EDQ 12.2.1 Using an Oracle / TomcatPlatformUpgrade Path 12:145166From any Release of EDQ on an Oracle / Tomcat Platform to EDQ 12.2.1 Using an Oracle / TomcatPlatformUPGRADING EDQ TO 12.1.3 OR 12.2.1166

IntroductionThis document explains how to upgrade older releases of Oracle Enterprise Data Quality to release12.1.3 and 12.2.1.A Little About EDQ’s PlatformIn order to function, an Enterprise Data Quality server requires: A database to function as its repository. An application server. A Java development kit (JDK).At release 12.1.3 the certified databases are the Oracle database and Postgresql.At release 12.2.1 only the Oracle database is certified for production use. Postgresql is certified only fordevelopment, test and evaluation use.At release 12.1.3 and at release 12.2.1, both Oracle WebLogic and Tomcat are certified as application servers.Please see the Fusion Middleware Certification matrixes for details of the versions of these databases andapplication servers that are certified, and please ensure that you only use certified versions.What Platform Does Oracle Recommend?Customers are urged to upgrade to a platform consisting of the Oracle Database and Oracle WebLogic whereverpossible. This is because future upgrades are likely to be much more straightforward with this combination ofdatabase repository and application server.Upgrading Production Instance of EDQ 9.0 and Below That Were Installed Using the the WindowsInstallerFor EDQ 9.0 and for earlier releases, a Windows Installer was provided that installed Enterprise Data Quality onWindows operating systems using the Tomcat application server and the PostgreSQL database as its platform.These installations were supported. You should follow the appropriate upgrade path in this document to upgrade allproduction instances of EDQ 9.0 and below that were installed using the Windows installer.Quick-Start Installations of EDQ 11 and 12For EDQ 11 and later releases, Oracle renamed the Windows installer the ‘Quick-Start Installer (Windows).’ ForEDQ 11 and for later releases, the Quick-Start Installer must not be used to install production environments. It maybe used to install EDQ for development, test and evaluation purposes only. Instances of EDQ 11 and later that areinstalled with the Quick-Start installer are not supported, and are not patchable.Upgrading Development, Test and Evaluation Instances of EDQ That Were Installed Using Either theWindows Installer or the Quick-Start InstallerThe primary intent of this document is to guide you through upgrades to supported installations of Enterprise DataQuality. Whilst you could use the upgrade paths in this document to upgrade development, test and evaluationinstallations of EDQ that were installed using either the Windows Installer or the Quick-Start Installer, the easiestway to upgrade such instances is simply to run the Quick-Start installer for the release you want to upgrade to. Thisshould automatically recognize and upgrade your existing instance.2 Upgrading EDQ to 12.1.3 or 12.2.1

Table of Upgrade Paths by Releaseand PlatformToRelease 12.1.3on Oracle /WebLogicRelease 12.1.3on Postgres /TomcatRelease 12.1.3on Oracle /TomcatRelease 12.2.1on Oracle /WebLogicRelease 12.2.1on Postgres /TomcatRelease 12.2.1on Oracle /TomcatRecommended:See upgradepath 1Inadvisable –no upgradepath providedInadvisable –no upgradepath providedRecommended:See upgradepath 6Not possible –no upgradepath providedInadvisable –no upgradepath providedNot ApplicableInadvisable –no upgradepath providedInadvisable –no upgradepath providedRecommended:See upgradepath 7Not possible –no upgradepath providedInadvisable –no upgradepath providedRecommended:See upgradepath 2Inadvisable –no upgradepath providedInadvisable –no upgradepath providedRecommended:See upgradepath 8Not possible –no upgradepath providedInadvisable –no upgradepath providedNot possible –no upgradepath providedPossible: Seeupgrade path 4Not possible –no upgradepath providedRecommended:See upgradepath 9Not possible –no upgradepath providedPossible:Seeupgrade path11Recommended:See upgradepath 3Inadvisable –no upgradepath providedPossible: Seeupgrade path 5Recommended:See upgradepath 10Not possible –no upgradepath providedPossible: Seeupgrade path12FromRelease11 onOracle /WebLogicInstalledwith OUIRelease12.1.3 onOracle /WebLogicinstalledwith OUIAnyReleaseinstalledon Oracle /WebLogicmanually(i.e withoutthe OUI)AnyreleaseinstalledonPostgres /TomcatAnyreleaseinstalledon Oracle /Tomcat3 UPGRADING EDQ TO 12.1.3 OR 12.2.1

Upgrade Path 1:From EDQ 11g Using an Oracle / WebLogic Platform Installed Using the OUI to EDQ 12.1.3 Using anOracle / WebLogic PlatformOverviewUpgrading from an installation of EDQ 11g that was installed using the Oracle Universal Installer (OUI) and thatuses the Oracle database and the WebLogic application server as its platform to EDQ 12.1.3 using the OracleDatabase and Oracle WebLogic as its platform is essentially a two-part process: Part 1 – Perform a Partial Installation of EDQ 12.1.3 Part 2 – Upgrade Your Old EDQ Environment.Part 1: Perform a Partial Installation of EDQ 12.1.31.Ensure that your environment satisfies all EDQ 12.1.3 System Requirements, as outlined in section 1.4 ofthe Installing and Configuring Oracle Enterprise Data Quality guide, and upgrade your environment ifnecessary.2.Download EDQ 12.1.3, as described in section 1.5 of the Installing and Configuring Oracle Enterprise DataQuality guide.3.Download the Fusion Middleware Infrastructure release 12.1.3.4.If your environment’s current Java Development Kit does not support EDQ 12.1.3, install a JavaDevelopment Kit to support EDQ 12.1.3, as described in section 2.2 of the Installing and ConfiguringOracle Enterprise Data Quality guide.5.If your environment’s current Oracle Fusion Middleware Infrastructure does not support EDQ 12.1.3, installOracle Fusion Middleware Infrastructure to support EDQ 12.1.3.Note that the Oracle Fusion Middleware Infrastructure that you used to support your old release of EDQ will notsupport your new release of EDQ. Therefore, unless, you have already installed the new release of the OracleFusion Middleware Infrastructure 12.1.3 for some other purpose, you will have to install it now. Note also thatthe new release of the Fusion Middleware Infrastructure will have to be installed in a different FusionMiddleware Home to your old release.6.If your environment’s current Oracle Database does not support EDQ 12.1.3, upgrade the OracleDatabase to a release that will support EDQ 12.1.3.7.Install Enterprise Data Quality 12.1.3 assets, as described in section 3 (Installing Enterprise Data Quality)of the Installing and Configuring Oracle Enterprise Data Quality guide, ensuring that you install EDQ inyour new Fusion Middleware Infrastructure’s Fusion Middleware Home. For the avoidance of doubt, thisstep entails installing the Oracle Fusion Middleware EDQ distribution. This is usually downloaded as a zipfile that contains a single file with a name similar to fmw 12.1.3.x.x edq.jar. Running this jar file invokesthe Oracle Universal Installer.4 Upgrading EDQ to 12.1.3 or 12.2.1

This step places elements of Enterprise Data Quality in your environment’s new Fusion Middleware Homelocation. Some of these elements will be used later in the installation process. Note, however, that you will nothave a working EDQ environment at this stage.Part 2: Upgrade your Old EDQ Environment1.Back up your old EDQ environment.a.Before you begin, Oracle recommends that you make a complete backup of your old EDQenvironment, including your EDQ domain. For instructions, see “Backup and RecoveryStrategies for Upgrade” in the Planning an Upgrade of Oracle Fusion Middlewaredocumentation.2.Shutdown your old EDQ environment’s Managed WebLogic Server.3.Ensure that your old EDQ environment’s WebLogic Server Administration Server remains running.4.If your old EDQ environment used a File-Based Keystore, migrate it to an OPSS Security Store.At release 12c, all Oracle Fusion Middleware products store their security credentials in an Oracle Platform SecurityServices (OPSS) schema within an Oracle database. The Oracle term for this is security store. If you were using afile-based keystore in the configuration directories, you must now use an OPSS DB-based security store.To convert to an OPSS DB-based security store, you create the OPSS, Audit Services, and Audit Services Viewerschemas. The Audit Services and Audit Services Viewer schemas are required by the Oracle Platform SecurityServices schema. After creating these schemas, you then create a WebLogic Server data source for the OPSSschema, and then re-associate the EDQ keystore to the OPSS schema.a.Create the OPSS Schemai.Download the 11g Repository Creation Utility (RCU) from Oracle. For instructions, seehttp://docs.oracle.com/cd/E23104 01/download readme ps6/download readme ps6.htm#BABHDBJCii.Extract the contents to a directory of your choice; this directory will be referred to as theRCU HOME directory. On Windows operating systems, make sure that you do notunzip the RCU file to a directory name that contains spaces.iii.Run the command shell or console of the operating system.iv.Start RCU from the bin directory inside the RCU HOME directory.Note:If you are running RCU using a non-English database, set the following environment variables:setenv LANG en US.UTF8setenv LC ALL LANGsetenv NLS LANG american america5 UPGRADING EDQ TO 12.1.3 OR 12.2.1

On Linux:./rcuOn Windows:rcu.batv.Start RCU from the bin directory inside the RCU HOME directory.vi.Click Next to pass through the Welcome screen.vii.On the Create Repository screen, select Create, then click Next .viii.On the Database Connection Details screen, enter the connection details for your oldenvironment’s EDQ repository database and the login credentials of an EDQ repositorydatabase user who has DAB or SYSDBA privileges. Click Next . The RCU will checkprerequisites.ix.On the Select Components screen, ensure that you select the same schema prefix thatis used for your old environment’s EDQ Repository (for example, if the oldenvironment’s schemas started with DEV, then ensure you select DEV). This willusually entail checking the Select existing prefix option. Under Oracle AS RepositoryComponents, expand AS Common Schemas and then select Audit Services andOracle Platform Security Services. Click Next .x.On the Schema Passwords screen, supply passwords for the schema owners. ClickNext .xi.On the Map Tablespaces screen, the default tablespace names are displayed. Eitheraccept these, or select alternative tablespaces for the components. (Optionally, youcan click Manage Tablespaces at this point to change the tablespaces sizes.) ClickNext .xii.b.On the Summary screen, click Create to complete the creation of the schema.Create a JDBC Data Source for the OPSS Schema.Use the WebLogic Server Administration Console to create a generic JDBC data source for the OPSS schema. Forassistance or more information on any screen, click Help.i.In the Domain Structure tree, expand Services, then select Data Sources.ii.On the Summary of Data Sources screen, click New and select Generic Data Source.iii.On the JDBC Data Sources Properties screen, enter the data source name and theJNDI name of the OPSS schema that you created with the 11g RCU in Task 1. TheOPSS DataSources name is opss-data-source and the JNDI name is similar to thisexample: jdbc/OpssDataSource. Select the database type as Oracle, and thenclick Next.iv.On the Create a New JDBC Data Source screen, in the Database Driver pull-down,select Oracle's Driver (Thin) for Instance connections; Versions:9.0.1 and later(this is a non-XA JDBC driver) and then click Next.6 UPGRADING EDQ TO 12.1.3 OR 12.2.1

Note: You must install JDBC drivers before you can use them to create database connections. Some JDBCdrivers are installed with WebLogic Server, but many are not installed.v.On the Transaction Options screen, make sure that Supports Global Transactions isdeselected and then click Next.vi.On the Connection Properties screen, enter the connection details and credentials toconnect to the OPSS schema that you created with the 11g RCU in the previous step.vii.On the Test Database Connection screen, review the connection parameters and clickTest Configuration. Results from the connection test are displayed at the top of thepage. If the test is unsuccessful, correct any configuration errors and retry the test. Ifthe JDBC driver you selected is not installed on the WebLogic Server AdministrationServer, click Next to skip this step. Install the driver after finishing this procedure.viii.On the Select Targets page, select the WebLogic Server(s) or cluster(s) on which youwant to deploy the data source. Select both the EDQ Managed WebLogic Server andthe WebLogic Server Administration Server as targets. If you are using WebLogicclustering, deploy the data source to the cluster.ix.Click Finish to save the JDBC data source configuration and deploy the data source tothe targets that you selected.x.If your WebLogic Server is working in production mode, click Activate Changes in theChange Center of the Administration Console. Not all changes take effect immediately,but all will take effect when you restart the server at the end of the EDQ upgradeprocess.xi.Restart the WebLogic Server Administration Server. (If the console tells you that norestart is necessary, ignore this message and restart anyway – the next step will notwork unless you restart the Administration Server).c.Reassociate the File-based Keystore to a DB-based Security StoreUse the WebLogic Server Scripting Tool (WLST) to reassociate the file-based keystore to the OPSS data sourcethat you created with the WebLogic Server Administration Console.i.From the 11g EDQ HOME/oracle common/common/bin directory, issue the followingcommand to run the WebLogic Server Scripting Tool (WLST):UNIX/Linux:./wlst.shWindows:wlst.cmdii.In WLST, connect to your WebLogic instance.connect('username', 'password', 'host:port')Where:7 UPGRADING EDQ TO 12.1.3 OR 12.2.1

username is the name of the Oracle WebLogic Server admin user.password is the Oracle WebLogic Server admin user's password.host is the name of the machine that the WebLogic server is running on.port is the connection port for the WebLogic Server Administration Server.iii.Reassociate the OPSS schema from the file-based format to the database formatusing the reassociate script.reassociateSecurityStore(domain "upgradeDomain",servertype "DB ORACLE", jpsroot "cn jpsroot",datasourcename "name of datasource")Where:upgradeDomain is the name of the WebLogic domain used for your oldinstance of Enterprise Data Quality.name of datasource is the name of the new OPSS JNDI data source thatyou created in the WebLogic Server Administration Console in the previousstep.For more information about the reassociate script, seehttp://docs.oracle.com/cd/E29542 01/core.1111/e10043/cfgauthr.htm#JISEC2675iv.Once the reassociation has completed, restart the WebLogic Server AdministrationServer.Do not restart the EDQ managed server(s) yet. Complete the rest of the upgrade steps. The changes you madeare stored on the server and will propagate to the rest of the servers when you restart the servers afterupgrade.5.Create the Required 12c Schemas.Oracle Fusion Middleware Release 12c introduces new schemas and tables that must be created with the Release12.1.3 version of the Oracle Repository Creation Utility (RCU). This step of the upgrade must be performed beforeupgrading your old environment’s EDQ Domain.a.To create the required 12.1.3 schemas, see Section 4.2, "Creating an EDQ DatabaseRepository" of the Installing and Configuring Oracle Enterprise Data Quality guide for release12.1.3. Follow those instructions, but with these four additions:i.On the Database Connection Details screen, ensure that you supply the connectiondetails for your old EDQ environment’s database repository. This is because you aregoing to add new EDQ 12.1.3 schemas to your old repository.ii.On the Select Components screen, ensure that you select the same schema prefix thatis used for your old environment’s EDQ Repository (for example, if the old8 UPGRADING EDQ TO 12.1.3 OR 12.2.1

environment’s schemas started with DEV, then ensure you select DEV). This willusually entail checking the Select existing prefix option.iii.On the Select Components screen, the AS Common Schemas option should beselected by default. Do not make any changes.iv.If, when you click Next, you see an error message similar to “RCU-6019: Invalidformat for schema owner STB.Prefixable components should havetheir schema owner in the following format prefix Any String where the prefix is DEV”, deselect and then reselect the CommonInfrastructure Services Component, and click Next again.v.The effect of this should be that the RCU will create exactly one new schema: Common Infrastructure Services.You should be able to confirm that this new schema (and its associated tablespaces)are going to be created when you get to the Map Tablespaces screen, and also on thesubsequent Summary screen. Before you click Create on the Summary screen, makeabsolutely sure that this schema will be created, and also ensure that it has the sameprefix as your existing EDQ Repository schemas.6.Follow the instructions below to upgrade the schemas in the EDQ repository database.a.Start the Upgrade Assistant:i.Go to the following directory, where 12.1.3 FMW HOME is the version 12.1.3 Oraclehome directory.On UNIX operating systems:12.1.3 FMW HOME/oracle common/upgrade/binOn Windows operating systems:12.1.3 FMW HOME\oracle common\upgrade\binii.Run the following program:On Linux or UNIX operating systems:./uaOn Windows operating systems:ua.batb.At the Welcome screen, Review Important Reminders before Proceeding. The Welcome screencontains reminders to consider before proceeding with your upgrade. Make sure you read theseand verify that you are ready to proceed. For assistance or more information on any screen, clickHelp. Otherwise, click Next .9 UPGRADING EDQ TO 12.1.3 OR 12.2.1

For more information about the following screens, see ”Upgrading Schemas with the Upgrade Assistant” inUpgrading with the Upgrade Assistant.c.Select the type of upgrade you wish to perform.i.d.Select Schemas.The Available Components screen will display a list of the components (or in other words,schemas) from your old EDQ environment’s domain. The following components should alwaysbe listed: Oracle Enterprise Data Quality Results Schema Oracle Audit Services Oracle Platform Security Services Oracle Enterprise Data Quality Configuration SchemaDepending upon how your EDQ 11g environment was configured, it is possible that othercomponents may also be listed.Select all of the following components if they appear:i.e. Common Infrastructure Services Oracle Audit Services. Oracle Enterprise Data Quality (this should automatically select bothOracle Enterprise Data Quality Configuration Schemaand Oracle Enterprise Data Quality Results Schema) Oracle Platform Security ServicesClick Next .At the Domain Directory screen, enter your old EDQ environment’s domain directory (forexample, this could be similar toC:\Oracle11\Middleware\user projects\domains\edq domain). Click Next .f.In the Prerequisites screen, verify that you have met the prerequisites, and, provided that youhave, check the relevant boxes (note that The Upgrade Assistant will not verify that theprerequisites have been met.). Then click Next .g.Specify Database and Schema Credentialsi.ii.iii.Screens for each of the components you selected, starting with The EDQRESULTSschema, are displayed in succession.On the first screen, specify connection details for your old environment’s EDQRepository (note that you may have to add as sysdba to the DBA User Name), andthen click Connect. Once you have clicked Connect, the Schema User Name andSchema Password fields should be populated automatically for the EDQ Resultsschema (if they are not, enter this information manually).The remaining screens are automatically populated with the database connection andschema credentials that you supplied on the EDQ Results Schema screen. If these10 UPGRADING EDQ TO 12.1.3 OR 12.2.1

entries are not correct for any schema, change the entries and ensure that a databaseconnection is made.h.Complete the upgrade validation.i.i.On the Examine screen, the Upgrade Assistant performs a series of validations on thecomponents. Validations for the Oracle Enterprise Data Quality Results component,the Oracle Enterprise Data Quality Configuration component and Oracle PlatformSecurity Services component should succeed, and the Upgrade Assistant shouldreport that an upgrade is not necessary for either of the Oracle Audit Servicescomponent or the Common Infrastructure Services Component. Click Next .Initiate the Upgrade.i.7.Click Upgrade on the Upgrade Summary screen to initiate the upgrade. The UpgradeProgress screen shows information about the progress of the upgrade, and theUpgrade Success screen summarizes the upgrade.Reconfigure the EDQ Domain.In this step you will run the Oracle Fusion Middleware reconfiguration wizard to complete the upgrade of yourWebLogic Server domain environment.a.Check that the Staging Mode is set to Nostage.i.Log in to the WebLogic Server Administration Server console from any web browser.ii.In the left pane, expand Environment and then click Servers. The Summary ofServers screen will be displayed.iii.In the Summary of Servers screen, click your EDQ Managed WebLogic Server (forexample: edq server1).iv.Select the Configuration tab, then the Deployment tab.v.From the Staging Mode menu, ensure that nostage is selected, and, if it is not, selectit. Do not change any other server settings.vi.b.Click Save, and, if working in production mode, activate your settings.Start Node Manager if it is not already runningNote that you only need to complete this step if the Node Manager is not already running.This task ensures that Node Manager has been started at least once since it was installed. Starting Node Managercreates a set of script files that must be moved from the old domain to the release 12.1.3 domain. Performing thistask eliminates the need for extra steps when upgrading your domain.i.Using a command line tool (for example, the Windows Command prompt or a Linux orUnix terminal), navigate to the bin folder in your old EDQ environment’s WebLogicbase domain (this will be at a location similar toFMW HOME/user projects/domains/edq domain/bin).ii.Run the following command to start Node Manager. For hostname, specify the nameof the system where Node Manager is installed, and for port, specify the port numberon which it runs.11 UPGRADING EDQ TO 12.1.3 OR 12.2.1

Windows:startNodeManager.cmd hostname portUNIX:./startNodeManager.sh hostname portc.Stop Node Manageri.If the Node Manager was not already running, and you started it using the commandabove, then stop it by closing the command shell from which it is running.ii.If Node Manager was already running (for example, because it was already running asa service in your environment), then stop it using the appropriate means (for example,stop the Node Manager service).d.Start the Reconfiguration WizardIn this step you will launch the wizard that will upgrade the EDQ domain.i.ii.Stop the WebLogic Server Administration Server and all managed servers.Go to the following directory, where 12.1.3 FMW HOME is the release 12.1.3 FusionMiddleware home directory.On Windows operating systems:12.1.3 FMW HOME\oracle common\common\binOn UNIX operating systems:12.1.3 FMW HOME/oracle common/common/biniii.Start the domain reconfiguration wizard.On UNIX operating systems:./reconfig.sh -log log fileOn Windows operating systems:reconfig.cmd -log log fileSpecify the full path and file name in place of log file. Creating a log file can be helpful if you need totroubleshoot the reconfiguration process.Note that if the following error message is displayed, it indicates that the default cache directory is not valid:*sys-package-mgr*: can't create package cache dirYou can change the cache directory by setting the environment variable CONFIG JVM ARGS. For example:CONFIG JVM ARGS -Dpython.cachedir valid directorye.Specify the domain.i.On the Select Domain screen, specify the full path to the location of your old EDQdomain (it is likely to be similar toOLD FMW HOME/user projects/domains/edq domain or12 UPGRADING EDQ TO 12.1.3 OR 12.2.1

OLD FMW HOME\user projects\domains\edq domain). You can also clickBrowse and use the file manager window to help you select the domain location. (Becareful – you may find that the 12.1.3 Home is selected by default – remember tonavigate to your old FMW home instead).f.View the Reconfiguration Setup Progress.i.The Reconfiguration Setup Progress displays the reconfiguration progress and verifieswhether the base domain that you selected can be reconfigured to the 12.1.3 domain.The message “Core WLS Infrastructure Reconfigured Successfully!” indicates that thedomain can be reconfigured to the 12.1.3 domain, and you can click Next to go to thenext step. If this message is not returned, the domain cannot be reconfigured to the12.1.3 domain. If this happens, check to see if the EDQ version is earlier than version11g; if so, then select the appropriate upgrade path for version 12.1.3, and start theentire upgrade process again.g.Select the Domain Mode and JDK.i.It is not possible to change the Domain Mode from development to production or viceversa.ii.On the Domain Mode and JDK screen, specify the location of the Java DevelopmentKit (JDK) to use in the new EDQ domain. This must be a JDK that conforms to thesystem requirements of your new EDQ 12.1.3 environment.h.Check the JDBC Data Sources.i.On the JDBC Data Sources screen, your old EDQ domain’s Config and Resultsdatasources should be listed in the lower half of the screen. If you need to makechanges, select the check box next to the data source name and then make thechanges.i.Test the JDBC Data Sourcesi.On the JDBC Data Sources Test screen, test the data source connections that weredetected. Select both schemas and then click Test Selected Connections.j.Select the Database Configuration Type.i.In the Database Configuration Type screen, the RCU Data option should be selectedby default. The connection details for your EDQ repository database should bepartially populated, and the schema owner for the Common Infrastructure schema(STB) should be displayed. If this information is not all automatically populated, or isnot correct, make any necessary entries or amendments. (In particular, make sure thatthe prefix of the schema owner is correct).ii.Click Get RCU Configuration. The Reconfiguration Wizard should report that it canconnect to the Database Server and that it can retrieve schema data and bind localschema components with the retrieved data. If these steps fail, amend the connectiondata and click Get RCU Configuration again. Otherwise, click Next .k.Check the JDBC Component Schema.13 UPGRADING EDQ TO 12.1.3 OR 12.2.1

i.On the JDBC Component Schema screen, the schemas associated with your old EDQdomain are listed in the lower half of the screen. If you need to make changes, selectthe check box next to the data source name and then make the changes. Note that theconnection details for some of the schemas may not be correct. If they are not, amendthem so that they are correct.l.Test the JDBC Component Schemai.On the JDBC Component Schema Test screen, test the data source connections thatwere detected. Select the schemas that you want to test and then click Test SelectedConnections.To test a connection, the database to which you are connecting must be running. Note that the test for theOPSS Audit Viewer component schema may fail (all other tests should succeed). If the test for the OPSS AuditViewer component schema fails, click Next anyway, and click OK in the subsequent dialog box to proceedwithout verification.m.Node Manageri.Leave the default options for the Node Manager Type and Node ManagerConfiguration selected, and enter the Node Manager’s Credentials.n.Select Optional Advanced Configuration OptionsOn

Upgrading EDQ to 12c versions ORACLE TUTORIAL JU LY 2017 . UPGRADING EDQ TO 12.1.3 OR 12.2.1 Table of Contents Introduction 2 Table of Upgrade Paths by Release and Platform 3 Upgrade Path 1: 4 From EDQ 11g Using an Oracle / WebLogic Platform Instal