Databases Reference
In-Depth Information
Configuring server migration for WLS_BAM1
It is highly recommended to configure server migration for
WLS_BAM1
on which
the singleton BAM Server is running. In the case of
WLS_BAM1
server crash or
failure, BAM Server services will be brought up automatically on
bamhost2
, so
that BAM Web applications or other clients can continue using the services or
interface provided by theBAM Server.
In this section, you will learn how to configure server migration for
WLS_BAM1
that hosts both the BAM Server and the BAM Web applications.
Setting up a leasing table for server migration
Perform these steps to create a leasing table for server migration:
1.
Create a
tablespace
called
leasing
. For example, log on
to
SQL*Plus
as the
sysdba
user, and run the following command:
SQL> create tablespace leasing logging datafile 'DB_HOME/oradata/orcl/leasing.dbf' size 32m autoextend on next 32m maxsize 2048m extent management local;
2.
Create a user named
leasing
, and assign it to the leasing
tablespace
as follows:
SQL> create user leasing identified by welcome1;
SQL> grant create table to leasing;
SQL> grant create session to leasing;
SQL> alter user leasing default tablespace leasing;
SQL> alter user leasing quota unlimited on LEASING;
3.
Copy the
WL_HOME/server/db/oracle/920/leasing.ddl
file to your
database node.
4.
Connect to the database as the
leasing
user, and run the script in
SQL*Plus
.
