Configuring OWB Installed as Part of Oracle Database 11g Release 2

Configuring OWB Installed as Part of Oracle Database 11g Release 2

Once Oracle Database 11g Release 2 is installed, you only have to unlock two accounts: OWBSYS and OWBSYS_AUDIT.

To unlock OWBSYS and OWBSYS_AUDIT accounts:

1. At the command prompt, start SQL*Plus:

% sqlplus

SQL*Plus: Release 11.2 - Production on Mon July 27 13:06:27 2009

Copyright (c) 1982, 2009, Oracle. All rights reserved.

2. When prompted for user name, log in as a user with administrative privileges.

Enter user-name: sys as sysdba

Enter password: password

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2 - Production

With the Partitioning, OLAP and Data Mining options

3. Unlock the OWBSYS user account, and set its new password:

SQL> alter user owbsys identified by password account unlock;

User altered.

4. Unlock the OWBSYS_AUDIT user account, and set its new password:

SQL> alter user owbsys_audit identified by password account unlock;

User altered.

Configuring OWB Installed as a Standalone Instance

About Configuring OWB Installed as a Standalone Instance

1.       Ensure that the database is fully installed and working; if you it is not, see Oracle Database Quick Installation Guide

2.       Note of the host name, the port, and Oracle service name of this database. The example here uses the following connection information:

localhost:1521:orcl.

3.       Ensure that you have username and password for an account with SYSDBA privileges.

You must first create an OWBSYS schema, and then install repository objects within it. Oracle Warehouse Builder has command-level scripts to perform this task:

■ The clean_owbsys.sql script drops the contents of any existing OWBSYS schema installations, but leaves the schema otherwise intact.

■ The cat_owb.sql script checks if an OWBSYS schema exists, and creates it if necessary, and then installs the objects required by Oracle Warehouse Builder 11.2 repository.

■ The reset_owbcc_home.sql script ensures that Oracle Warehouse Builder uses the 11.2 version of the Control Center Service.

■ [Optional] The remote_owb_install.sql script, when executed on the server, ensures that a repository on a remote system can be installed; it sets the REMOTE_OWB_HOME variable for authentication by remote systems.

Cleaning an Oracle Warehouse Builder Repository

To clean an existing Oracle Warehouse Builder repository:

1. At the command prompt, start SQL*Plus:

% sqlplus

SQL*Plus: Release 11.2 - Production on Mon July 27 13:14:43 2009

Copyright (c) 1982, 2009, Oracle. All rights reserved.

2. When prompted for user name, log in as OWBSYS user.

Enter user-name: owbsys

Enter password: password

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2 - Production

With the Partitioning, OLAP and Data Mining options

3. Stop Oracle Warehouse Builder Control Center service.

SQL> @OWB112/owb/rtp/sql/stop_service.sql

See "stop_service" on page 9-12 for more information.

4. Connect as user with administrative privileges:

SQL> connect sys as sysdba

Enter password: password

5. Run the clean_owbsys.sql script to drop all the objects in the existing OWBSYS schema:

SQL> @OWB112/owb/UnifiedRepos/clean_owbsys.sql

Creating an OWBSYS Schema with Repository Objects

To set-up an OWBSYS schema with repository objects:

1. At the command prompt, start SQL*Plus:

% sqlplus

SQL*Plus: Release 11.2 - Production on Mon July 27 13:22:11 2009

Copyright (c) 1982, 2009, Oracle. All rights reserved.

2. When prompted for user name, log in as a user with administrative privileges.

Enter user-name: sys as sysdba

Enter password: password

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2 - Production

With the Partitioning, OLAP and Data Mining options

3. Run the cat_owb.sql script to set up OWBSYS in a tablespace in your database.

For example, this command sets up OWBSYS in the USERS tablespace:

SQL> @OWB112/owb/UnifiedRepos/cat_owb.sql USERS

Configuring the Control Center Service

If you are installing OWB 11.2 on an older Oracle Database release, or if you integrating OWB with Oracle Business Intelligence Standard Edition (Oracle Discoverer), you must run the reset_owbcc_home.sql script to ensure that the Control Center Service functions correctly.

To configure the Control Center service:

1. Confirm the correct Oracle Home path, paying particular attention to

capitalization. In this example, the path is OWB112.

The path entered in the next steps must be an exact match to the Oracle Warehouse

Builder home directory, including letter case match.

2. At the command prompt, start SQL*Plus:

% sqlplus

SQL*Plus: Release 11.2 - Production on Mon July 27 13:47:31 2009

Copyright (c) 1982, 2009, Oracle. All rights reserved.

3. When prompted for user name, log in as a user with administrative privileges.

Enter user-name: sys as sysdba

Enter password: password

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2 - Production

With the Partitioning, OLAP and Data Mining options

4. Run the reset_owbcc_home.sql script to force the Control Center Service to

run from Oracle Warehouse Builder 11.2 installation:

SQL> @OWB112/owb/UnifiedRepos/reset_owbcc_home.sql OWB112

Unlocking the OWBSYS and OWBSYS_AUDIT Accounts

To unlock OWBSYS and OWBSYS_AUDIT accounts:

1. At the command prompt, start SQL*Plus:

% sqlplus

SQL*Plus: Release 11.2 - Production on Mon July 27 13:57:03 2009

Copyright (c) 1982, 2009, Oracle. All rights reserved.

2. When prompted for user name, log in as a user with administrative privileges.

Enter user-name: sys as sysdba

Enter password: password

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2 - Production

With the Partitioning, OLAP and Data Mining options

3. Unlock the OWBSYS user account, and set its new password:

SQL> alter user owbsys identified by password account unlock;

User altered.

4. Unlock the OWBSYS_AUDIT user account, and set its new password:

SQL> alter user owbsys_audit identified by password account unlock;

User altered.

Setting the OWB Home for Remote Installations

You must create a database directory OWB_REMOTE_ADMIN that is accessed by remote installations, so they can read the server's OWB_HOME/owb/bin/admin directory.

1. At the command prompt, start SQL*Plus:

% sqlplus

SQL*Plus: Release 11.2 - Production on Mon July 27 14:06:12 2009

Copyright (c) 1982, 2009, Oracle. All rights reserved.

2. When prompted for user name, log in as a user with administrative privileges.

Enter user-name: sys as sysdba

Enter password: password

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2 - Production

With the Partitioning, OLAP and Data Mining options

3. Set the OWB_REMOTE_HOME variable using script remote_owb_install.sql:

SQL> @OWB112/owb/UnifiedRepos/remote_owb_install.sql OWB_REMOTE_HOME

Creating the First Workspace in the Repository

To use a repository, you must define an initial workspace, and the owner of that workspace. The following instructions use the Repository Assistant.

To create a workspace:

1. At the command prompt, navigate to the UNIX bin directory:

% cd OWB112/owb/bin/unix

% pwd

OWB112/owb/bin/unix

2. Start the repository assistant.

% ./reposinst.sh

4.       On the Welcome screen of the Repository assistant, click Next.

4. On the Database Information screen, enter the connection information (Host Name, Port Number, and Oracle Service Name) for the repository database, and click Next.

5. On the Choose Operation screen, select Manage Warehouse Builder Workspaces.

Click Next.

6. On the Choose Workspace Operations screen, select Create a New Warehouse

Builder workspace. Click Next.

7. On the New or Existing User screen, select Create a workspace with a new

workspace owner. Click Next.

8. On the DBA Information screen, enter the User Name of a user with a CREATE USER privilege, and that user's Password.

Click Next.

9. In the Workspace Owner (New) screen, enter the following information:

■ Workspace Owner's User Name (wks_owner1)

■ Workspace Owner's Password

■ Workspace Owner's Password Confirmation

■ Workspace Name (wks1)

Click Next.

10. In the OWBSYS Information screen, enter the OWBSYS Password. Click Next.

Note that you need these credentials to seed the OWBSYS schema.

11. [Optional] For remote installations (when you the schema is on a remote system), the system performs the verification of versions, and displays the dialog "Found OWB software with the compatible version installed locally on the database server machine with path REMOTE_OWB_HOME."

12. On the Select Tablespaces screen, enter the following information:

■ Tablespace for Data (USERS, or the name of the desired tablespace)

■ Tablespace for Indexes (USERS, or the name of the same tablespace)

■ Tablespace for Temporary Data (TEMP)

■ Tablespace for Snapshots (USERS, or the name of the same tablespace)

Click Next.

13. On the Select Languages screen, select the Base Language from the menu.

Click Next.

14. On the Workspace Users (Optional) screen, select the appropriate existing users from the Available list add them to the Selected list.

[Optional] Click Create New User to make new users who can access OWB. This takes you to step 15.

Click Next. This takes you to step 17.

15. [Optional] In the Create New Database User screen, enter the following: User Name (demo_user)

■ Password

■ Re-enter Password

Click OK.

Note that DBA User Name (system) and DBA User Password are disabled fields and cannot be edited.

16. In the Workspace Users (Optional) screen, click Next.

17. On the Summary screen, click Finish.

18. Once the Installation Result screen appears, click OK.

Note : all the information is taken from metalinks and google search.