Partitioning Oracle WebCenter Analytics Data

15-4 Oracle Fusion Middleware Administrators Guide The following tasks describe the procedure: ■ Task 1, Stop All Oracle Fusion Middleware Components ■ Task 2, Shut Down the Database ■ Task 3, Change the Network Configuration ■ Task 4, Change References to the Network Configuration ■ Task 5, Start the Database ■ Task 6, Change the System Data Source ■ Task 7, Restart Your Environment Task 1 Stop All Oracle Fusion Middleware Components Stop all components that use the database, even if they are on other hosts. Stop the Administration Server, the Managed Servers, and all components, as described in Chapter 4 . Task 2 Shut Down the Database Prepare your host for the change by stopping the database: 1. Set the ORACLE_HOME and ORACLE_SID environment variables. 2. Shut down the listener and database: lsnrctl stop sqlplus nolog SQL connect SYS as SYSDBA SQL shutdown SQL quit 3. Verify that all Oracle Fusion Middleware processes have stopped. 4. To ensure that Oracle Fusion Middleware processes do not start automatically after a restart of the host, disable any automated startup scripts you may have set up, such as etcinit.d scripts. Task 3 Change the Network Configuration If you are changing the host name, domain name, or IP address, update your operating system with the new names or IP address, restart the host, and verify that the host is functioning properly on your network. Consult your operating system documentation for information on how to perform the following steps: 1. Make the updates to your operating system to properly change the host name, domain name or IP address. 2. Restart the host, if required by your operating system. 3. Verify that you can ping the host from another host in your network. Be sure to ping using the new host name, domain name, or IP address to ensure that everything is resolving properly. Task 4 Change References to the Network Configuration You must modify files that contain the host name, domain name, or IP address, depending on the components that you are using. The following lists some of the files that you may need to modify to change references to the new host name, domain name or IP address: Changing Network Configurations 15-5 ■ tnsnames.ora, which is located in: ORACLE_HOMEnetworkadmintnsnames.ora ■ listener.ora, which is located in: UNIX ORACLE_HOMEnetworkadminlistener.ora Windows ORACLE_HOME\network\admin\listener.ora ■ For Oracle HTTP Server, edit the httpd.conf file, making the following changes: – Update the Listen directive with the new host name or IP address and port if the production environment Oracle HTTP Server is using a different port. – Update the VirtualHost directive, if the host name, IP address, or port number is defined, with the new values for the production environment. – Update any other nondefault directives that were configured at the test environment and have topological host name, IP address, port number or other machine-specific information. ■ For Oracle HTTP Server, the PlsqlDatabaseConnectString in the dads.conf file ■ For Oracle HTTP Server, if you use mod_oradav, the ORACONNECTSN parameter in the mod_oradav.conf file ■ For Oracle HTTP Server, if you use mod_plsql, the PlsqlDatabaseConnectString attribute in the dads.conf file ■ For Oracle HTTP Server, if you use mod_wl_ohs, update the mod_wl_ohs.conf file Update the WebLogicHost, WebLogicPort, or WebLogicCluster directives with the host name, IP address, and port number. ■ For Oracle Portal, portal_dads.conf and sqlnet.ora ■ For Oracle Forms Services, sqlnet.ora ■ For Oracle Business Intelligence Discoverer, module_disco.conf This is not an exhaustive list. See Chapter 21 for additional information about files used by components. That chapter describes how to move components, including a database, from a test to a production system, in effect changing the host name. Task 5 Start the Database Start the database: 1. Log in to the host as the user that installed the database. 2. Set the ORACLE_HOME and ORACLE_SID environment variables. 3. On UNIX systems, set the LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, LIB_ PATH, or SHLIB_PATH environment variables to the proper values, as shown in Table 3–1 . The actual environment variables and values that you must set depend on the type of your UNIX operating system. 4. Start the database and listener: sqlplus nolog SQL connect SYS as SYSDBA SQL startup SQL quit lsnrctl start 15-6 Oracle Fusion Middleware Administrators Guide Task 6 Change the System Data Source Change the system data source to use the new host name, domain name, or IP address for the database. To do so, you use Oracle WebLogic Server Administration Console: 1. Start the Administration Server, as described in Section 4.2.1 . 2. Go to the Administration Console. 3. In the Change Center, click Lock Edit. 4. In the Domain Structure section, expand Services, then Data Sources. The Summary of JDBC Data Sources page is displayed. 5. Select the data source you want to change. The Settings page is displayed. 6. Select the Connection Pool tab. 7. Change the following entries to reflect the information for the database on the production environment: – URL: The database host name and port details. For example: jdbc:oracle:thin:newhostname.domainname:portsid jdbc:sqlserver:newhostname.domainname:port;database=database – Driver class: This is specific to the type of database. For example: oracle.jdbc.OracleDrivercom.microsoft.sqlserver.jdbc.SQLServerDriver – Properties: Database user name – Password: Database password 8. Click Save. 9. Restart the servers that use this data source. Click the Target tab to see the servers that use this data source. Task 7 Restart Your Environment Start the components that use the database: 1. Start all components that use the database, even if they are on other hosts. Start the Administration Server, the Managed Servers, and all components, as described in Chapter 4 . 2. If you disabled any processes from automatically starting Oracle Fusion Middleware at the beginning of this procedure, enable them.

15.3 Moving Between On-Network and Off-Network

This section describes how to move an Oracle Fusion Middleware host on and off the network. The following assumptions and restrictions apply: ■ The host must contain an instance that does not use an Infrastructure, or both the middle-tier instance and Infrastructure must be on the same host. ■ DHCP must be used in loopback mode. Refer to the Oracle Fusion Middleware Installation Planning Guide for more information. ■ Only IP address change is supported; the host name must remain unchanged. Changing Network Configurations 15-7 ■ Hosts in DHCP mode should not use the default host name localhost.localdomain. The hosts should be configured to use a standard host name and the loopback IP should resolve to that host name. ■ A loopback adapter is required for all off-network installations DHCP or static IP. Refer to the Oracle Fusion Middleware Installation Planning Guide for more information.

15.3.1 Moving from Off-Network to On-Network Static IP Address

This procedure assumes you have installed Oracle Fusion Middleware on a host that is off the network, using a standard host name not localhost, and would like to move on to the network and use a static IP address. The IP address may be the default loopback IP, or any standard IP address. To move on to the network, you can simply connect the host to the network. No updates to Oracle Fusion Middleware are required.

15.3.2 Moving from Off-Network to On-Network DHCP

This procedure assumes you have installed on a host that is off the network, using a standard host name not localhost, and would like to move on to the network and use DHCP. The IP address of the host can be any static IP address or loopback IP address, and should be configured to the host name. To move on to the network: 1. Connect the host to the network using DHCP. 2. Configure the host name to the loopback IP address only.

15.3.3 Moving from On-Network to Off-Network Static IP Address

Follow this procedure if your host is on the network, using a static IP address, and you would like to move it off the network: 1. Configure the etchosts file so the IP address and host name can be resolved locally. 2. Take the host off the network. There is no need to perform any steps to change the host name or IP address.

15.4 Changing Between a Static IP Address and DHCP

This section describes how to change between a static IP address and DHCP. The following assumptions and restrictions apply: ■ The host must contain all Oracle Fusion Middleware components, including Identity Management components, and any database associated with those components. That is, the entire Oracle Fusion Middleware environment must be on the host. ■ DHCP must be used in loopback mode. Refer to Oracle Fusion Middleware Installation Planning Guide for more information. ■ Only IP address change is supported; the host name must remain unchanged. ■ Hosts in DHCP mode should not use the default host name localhost.localdomain. The hosts should be configured to use a standard host name and the loopback IP should resolve to that host name.