RSS

Tag Archives: RCU Error

Things to remember for OBIEE 11G on Microsoft SQL Server

The basic things to remember when configuring OBIEE 11G on Microsoft SQL Server:

1. While running RCU:

  • Use case-sensitive collation in order that the database can reflect any case-sensitivity in your repository naming conventions.
    Run this sql command: ALTER DATABASE OBI COLLATE Latin1_General_CS_AS 
    (This command is for UK English installation, for US locale installation use Latin1_General_CP1_CS_AS)
  • Activate the mechanism of row versioning, so it`s require to enable Read Commit Snapshot.
    Run this command: ALTER DATABASE OBI SET READ_COMMITTED_SNAPSHOT ON

2. When configuring OBIEE 11G Scheduler with MS SQL server:

When installed with a Microsoft SQL Server 2005/2008 database, the Oracle Business Intelligence installer configures Oracle BI Scheduler with a SQL Server 2005/2008 driver. If multibyte data is used, scheduled jobs might fail. To avoid this issue, use Oracle Enterprise Manager to configure the Oracle Business Intelligence system to use a SQL Server 7.0/2000 driver instead.

To configure Oracle BI Scheduler to use the SQL Server 7.0/2000 driver with Microsoft SQL Server 2005/2008:

  1. After you install Oracle Business Intelligence, log into the system through Oracle Enterprise Manager.
  2. Navigate to the Scheduler tab for the Oracle Business Intelligence server.
  3. Click Lock and Edit Configuration.
  4. Click the Database drop-down list and select SQL Server 7.0/2000.
  5. Click Apply.

3. When configuring OBI Publisher 11G Scheduler with MS SQL server:

Prerequisite: Ensure that the Microsoft SQL Server is set up with mixed mode authentication. Also ensure that the user that you enter to configure the scheduler has the “db_owner” role.

The below table describes the fields for the DataDirect driver to connect to a Microsoft SQL Server 2000 or 2005 database.

DataDirect Driver Fields for SQL Server Databases

Field Entry
Database Type: Select Microsoft SQL Server 2000 or Microsoft SQL Server 2005 from the list.
Connection String: Enter the following connection string parameters: jdbc:hyperion:sqlserver://<hostname>:<port>;DatabaseName=<DATABASENAME> For example: jdbc:hyperion:sqlserver:// mydatabaseserver.com:1433;DatabaseName=bipscheduler
Database Driver Class: hyperion.jdbc.sqlserver.SQLServerDriver

4. in RPD Development:

  • When you are creating DSN for SQL Server, use sql server native client 10.0 instead of any other drivers. From Sql server 2008 onward, it is strongly recommended even some documents says dont use ODBC native drivers.
  • In RPD, the Query DBMS for SQL server in 11.1.1.6 only work when you specify the DSN name directly (by default it comes with OLAP_DSN session variable).
  • If you have a column with UNIQUEIDENTIFIER as its data type in MS SQL server, then change that column datatype to BINARY(16) or VARCHAR(40) in OBI RPD Physical layer.

5. Performance Tuning:

The following guidelines pertain to performance tuning parameters for Microsoft SQL Server databases. For more information about these parameters, see your Microsoft SQL Server documentation.

  • Store tempdb on a fast I/O device.
  • Increase the recovery interval if perfmon shows an increase in I/O.
  • Use an I/O block size larger than 2 KB.

Thanks,
Shiva

Advertisements
 
2 Comments

Posted by on July 2, 2012 in BI Publisher, OBI EE, OBIEE 11g

 

Tags: , , , , , , , , , , , , , ,

RCU Schema Configuration failed with the error “The specified prefix already exists”

We all know that we need to create RCU schemas before starting OBIEE 11G (In fact, for any Fusion Middleware application) Installation. Because it is the base store for FMW.

Recently I came across a scenario where my customer created RCU schemas with Oracle Repository Creation Utility (RCU) version 11.1.1.3.0 and Installed OBIEE 11.1.1.3.0. Now after new OBIEE 11.1.1.5.0 release he wants to upgrade his application from 11.1.1.3.0. But he is not interested at the In-place upgrade. So we uninstalled weblogic and OBIEE 11.1.1.3.0 and started RCU 11.1.1.3.0 to drop the _BIPLATFORM and _MDS schemas.

The RCU shown up with successful message and so we thought everything is cleaned up and it’s good to create schemas again. I started RCU 11.1.1.5.0 and selected Oracle Business Intelligence component and given prefix as DEV. But am not able to assign this prefix and got a message like “The specified prefix already exists”.  Though I got successful dropped schemas message, just for cross check I looked at database for the DEV_BIPLATFORM and DEV_MDS schemas. There I am not seeing any of them.

Then I checked at dropped schemas log generated by RCU and realized that there is an entry in System.SCHEMA_VERSION_REGISTRY$ table which is stopping me to assign the same DEV prefix which we used for earlier version schemas.

Actually the RCU should drop schemas using mdsschemamanager.pl script. This script has capability to do cascade delete and will delete entries in System.SCHEMA_VERSION_REGISTRY$ table.

To make sure this log into RCU DATABASE as sys and run the following SQL Query:

Select * from System.SCHEMA_VERSION_REGISTRY$;

If this query returns any record then it means the RCU didn’t drop the schemas properly.

Actually what happened in this case is the RCU schemas were not dropped using mdsschemamanager.pl script, it’s just dropped with normal schema delete and the resulting repository record for the schema is not clean. Keep in mind, this is just in case if you want to use same prefix. Otherwise RCU will let you proceed to create new prefixed Schemas.

If the RCU schemas have been deleted incorrectly using the RCU drop user command, then We need to clean these entries before starting new repository schemas creation.

To do this, run the following SQL*Plus command as sys to complete the removal of the RCU schemas records in the repository database:

delete from System.SCHEMA_VERSION_REGISTRY$;

Once you confirmed there are no entries in System.SCHEMA_VERSION_REGISTRY$  table and start the RCU to create repository schemas with the prefix (DEV in my case). The RCU will go smooth and wont complain with any error.

Hope this helps you in your RCU issues troubleshooting.

 

Thanks,

Shiva

 
8 Comments

Posted by on November 16, 2011 in BI Publisher, OBI EE, OBIEE 11g

 

Tags: , , , , , , , , , , , , ,