The time has come to move the RCU for our exalytics to another machine as the current machine is being decommissioned. Please do this in your test environment before attempting in Live.
In the Old RCU DB:
1) Export the Database using the old exp method:
Export: Release 10.2.0.4.0 – Production on Tue May 6 12:27:48 2014
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Enter array fetch buffer size: 4096 >
Export file: expdat.dmp >
(1)E(ntire database), (2)U(sers), or (3)T(ables): (2)U >
Export grants (yes/no): yes >
Export table data (yes/no): yes >
Compress extents (yes/no): yes >
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)
About to export specified users …
User to be exported: (RETURN to quit) > EXA_BIPLATFORM
User to be exported: (RETURN to quit) >
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user EXA_B
In the New DB.
2) First In the new database where we want to move the RCU to, run the RCU script to create the RCU.
drop user EXA_BIPLATFORM cascade;
CREATE USER “EXA_BIPLATFORM” PROFILE “DEFAULT” IDENTIFIED BY EXA_BIPLATFORM DEFAULT TABLESPACE “EXA_BIPLATFORM” TEMPORARY TABLESPACE “EXA_IAS_TEMP” ACCOUNT UNLOCK;
GRANT CREATE SEQUENCE TO “EXA_BIPLATFORM”;
GRANT CREATE VIEW TO “EXA_BIPLATFORM”;
GRANT UNLIMITED TABLESPACE TO “EXA_BIPLATFORM”;
GRANT EXECUTE ON “SYS”.”DBMS_LOCK” TO “EXA_BIPLATFORM”;
GRANT SELECT ON “SYSTEM”.”SCHEMA_VERSION_REGISTRY” TO “EXA_BIPLATFORM”;
GRANT “CONNECT” TO “EXA_BIPLATFORM”;
GRANT “RESOURCE” TO “EXA_BIPLATFORM”;
drop user EXA_MDS cascade;
CREATE USER “EXA_MDS” PROFILE “DEFAULT” IDENTIFIED BY EXA_MDS DEFAULT TABLESPACE “EXA_MDS” TEMPORARY TABLESPACE “EXA_IAS_TEMP” QUOTA UNLIMITED ON “EXA_MDS” ACCOUNT UNLOCK
GRANT CREATE PROCEDURE TO “EXA_MDS”;
GRANT CREATE SEQUENCE TO “EXA_MDS”;
GRANT CREATE TABLE TO “EXA_MDS”;
GRANT CREATE TYPE TO “EXA_MDS”;
GRANT SELECT ON “SYSTEM”.”SCHEMA_VERSION_REGISTRY” TO “EXA_MDS”;
GRANT “CONNECT” TO “EXA_MDS”;
3) Now we will import the data using the old imp method:
imp system/** file=EXA_BIPLATFORM.dmp fromuser=EXA_BIPLATFORM touser=EXA_BIPLATFORM log=exa_biplatform.log ignore=y
imp system/** file=EXA_MDS.dmp fromuser=EXA_MDS touser=EXA_MDS log=exa_mds.log ignore=y
4) Update the datasources in weblogic:
4a. Log in to the Weblogic console for your OBIEE deployment.
4b. Select to lock and edit if it is not automatically selected.
4c. Go to services and find datasources.
4d. Review the connection pool for each datasource and determine if it needs to be changed. If you have only obiee deployed on this server you will probably have to modify all datasources.
4e. Change the server, schema and password to correspond with your new information for each connection string for any datasource pointing to one of the RCU tables.
4f. After completing the changes to the datasources save and release the configuration
5) Changing the scheduler data source in Enterprise Manager
5a. Go to Oracle Business Intelligence Node and select the coreapplication
5b. Select deployment and then select lock and edit.
5c. Go to the scheduler tab and update the datasource information.
5d. Save and check in the changes, which will require a restart (you will be prompted for this).
6) Test that your deployment is working as expected.