- Sign in to the system on which the domain resides.
- Edition Based Database Users Only: If you have configured your schemas with Edition-Based Reassociation, you must manually supply a default edition name before running the Reconfiguration Wizard.
To set the default edition, enter the following SQL command:
ALTER DATABASE DEFAULT EDITION = edition_name;
Where, edition_name is the name of the default database edition.
- Run the Reconfiguration Wizard by entering the following command:
On UNIX operating system:
$ORACLE_HOME/oracle_common/common/bin/reconfig.sh
On Windows operating system:
%ORACLE_HOME%\oracle_common\common\bin\reconfig.cmd
Note:
When you run the
reconfig.cmd or
reconfig.sh command, you can get the following error message to indicate that the default cache directory is not valid:
*sys-package-mgr*: can't create package cache dir
You can change the cache directory by including the -Dpython.cachedir=valid_directory parameter in the command.
Oracle recommends that you specify the "log" option while starting the Reconfiguration Wizard as shown in the following example:
./reconfig.sh -log=/$ORACLE_HOME/logs/reconfig.log -log_priority=ALL
You can set the log_priority as per your requirements.
- On the Select Domain screen, specify the location of the domain you want to upgrade or click Browse to navigate and select the domain directory. Click Next.
- The Reconfiguration Setup Progress screen shows the progress of the setup process. When complete, click Next.
During this process:
-
The reconfiguration templates for your installed products, including Fusion Middleware products, are automatically applied. This updates various domain configuration files such as config.xml, config-groups.xml, and security.xml (among others).
-
Schemas, scripts, and other such files that support your Fusion Middleware products are updated.
-
The domain upgrade is validated.
- On the Domain Mode and JDK screen, select the JDK to use in the domain or click Browse to navigate to the JDK you want to use. Click Next.
Note:
You cannot change the
Domain Mode at this stage.
- A JDBC data source contains a pool of database connections that are created when the data source instance is created, deployed or targeted, or at server startup.
Applications look up a data source on the JNDI tree, and then request a connection. When the applications no longer need the connections, they return the connections to the connection pool in the data source.
You can configure the JDBC data sources defined in your domain source on the JDBC Data Sources screen. The JDBC data sources associated with the products for which you are creating the domain are listed in the lower half of the screen.
Select the data source(s) from the Data Source Name drop-down list for which you want to specify the settings. The values that you specify are displayed in the appropriate columns in the data source list, for the selected data source.
For Oracle RAC Configuration for data sources, you can select one of the three options:
- Convert to GridLink
- Convert to RAC multi data source
- Don’t convert
For more information about each option, click Help.
After specifying the details, click Next.
If you do not select any data sources on the JDBC Data Sources screen, you get a pop-up with the following warning:
Missing Driver
Click Ok to proceed without verification, click Cancel to return to the JDBC Data Sources page.
In this case, if you click Ok, the data sources are not verified.
- On the JDBC Data Sources Test screen, select the check box for the data source connection you configured on the JDBC Data Sources screen and click Test Selected Connections to test the data source connection.
Note:
In order to test the database connections, the database to which you are connecting must be running. If you do not want to test the connections at this time, do not select any data sources. Click
Next to continue.
- On the Database Configuration Type screen, select RCU Data .
Enter the database connection details using the RCU service table (STB) schema credentials and click Get RCU Configuration.
The Reconfiguration Wizard uses this connection to automatically configure the data sources required for components in your domain.
If the check is successful, click Next. If the check fails, reenter the connection details correctly and try again.
- On the JDBC Component Schema Test screen, select all the component schemas and click Test Selected Connections to test the connection for each schema.
When the check is complete, click Next.
- The Node Manager screen is only displayed if the domain you are reconfiguring is currently using a per host Node Manager.
On the Node Manager screen, select the Node Manager configuration to use for the reconfigured domain. The resulting configuration depends on the combination of options you select for Node Manager Type and Node Manager Configuration.
- On the Advanced Configuration screen, you can select all categories for which you want to perform advanced configuration. For each category you select, the appropriate configuration screen is displayed to allow you to perform advanced configuration.
Note:
The categories that are listed on the
Advanced Configuration screen depend on the resources defined in the templates you selected for the domain.
For this upgrade, select none of the options and click Next.
- On the Configuration Summary screen, review the detailed configuration settings of the domain before continuing.
You can limit the items that are displayed in the right-most panel by selecting a filter option from the View drop-down list.
To change the configuration, click Back to return to the appropriate screen. To reconfigure the domain, click Reconfig.
Note:
The location of the domain does not change when you reconfigure it.
- The Reconfiguration Progress screen displays the progress of the reconfiguration process.
During this process:
-
Domain information is extracted, saved, and updated.
-
Schemas, scripts, and other such files that support your Fusion Middleware products are updated.
When the progress bar shows 100%, click Next.
- The End of Configuration screen indicates whether the reconfiguration process completed successfully or failed. It also displays the location of the domain that was reconfigured as well as the Administration Server URL (including the listen port). If the reconfiguration is successful, it displays “Oracle WebLogic Server Reconfiguration Succeeded”.
If the reconfiguration process did not complete successfully, an error message is displayed to indicate the reason. Take appropriate action to resolve the issue. If you cannot resolve the issue, contact My Oracle Support.
Note the Domain Location and the Admin Server URL for further operations.