Setting Up Data Sources on Linux and UNIX 15-7
■
For Solaris and Linux, the library path variable is LD_LIBRARY_PATH.
■
For HP-UX, the library path variable is SHLIB_PATH.
■
For AIX, the library path variable is LIBPATH. For example, to set the library path variable for the 32-bit driver on Linux:
Linux: Oracle BI 32 bit mode
SQLServer 2000 Parameters ---------------------------------------
LD_LIBRARY_PATH=userlocalOracleBIodbclib: LD_LIBRARY_PATH export LD_LIBRARY_PATH
3.
Save and close the file.
4.
Open the odbc.ini file. You can find this file at: ORACLE_INSTANCE
bifoundationOracleBIApplicationcoreapplicationsetupodbc.ini
5.
Create an entry for your database, ensuring that the ODBC connection name is identical to the data source name specified in the connection pool defined in the
repository. Be sure to set the Driver parameter to the file name and location of the DataDirect Connect driver for Microsoft SQL Server. In the following example, the
Driver parameter is set to the 64-bit DataDirect Connect driver, and the data source name is SQLSERVER_DB.
[SQLSERVER_DB] Driver=usrOracleBIodbclib64SEmsss23.so
Description=DataDirect 5.1 SQL Server Wire Protocol Address=111.111.111.111,1433
AlternateServers= AnsiNPW=Yes
ConnectionRetryCount=0 ConnectionRetryDelay=3
Database=dbschema_name LoadBalancing=0
LogonID= Password=
QuoteID=No ReportCodePageConversionErrors=0
6.
Save and close the odbc.ini file.
7.
Open your repository in the Administration Tool on a Windows computer.
8.
In the Physical layer, double-click the database object for the Microsoft SQL Server database.
9.
Click the Features tab and scroll to the IDENTIFIER_QUOTE_CHAR parameter. Then, replace the value for this parameter with single quotes. The default
value is double quotes .
10. Click OK.
11.
Save and close the repository.
12.
On the Linux or UNIX computer, shut down Oracle Business Intelligence.
13.
Copy the repository from the Windows computer to the Linux or UNIX computer.
14.
Start Oracle Business Intelligence on the Linux or UNIX computer.
15-8 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition
Configuring the DataDirect Connect ODBC Driver for Sybase ASE Database
The name of the DataDirect ODBC driver file to connect to a Sybase ASE database is SEase23.so. See
System Requirements and Certification for information about
supported versions of Sybase ASE.
To configure the DataDirect Connect ODBC Driver to connect to Sybase ASE Database:
1. Open the user.sh file. You can find this file at:
ORACLE_INSTANCE bifoundationOracleBIApplicationcoreapplicationsetupuser.sh
2.
In the section for your operating system, include the appropriate library path environment variable for the DataDirect Connect libraries. Make sure to point to
the appropriate library, depending on whether you are using a 32-bit or 64-bit database. Note the following:
■
For Solaris and Linux, the library path variable is LD_LIBRARY_PATH.
■
For HP-UX, the library path variable is SHLIB_PATH.
■
For AIX, the library path variable is LIBPATH. For example, to set the library path variable for the 32-bit driver on Linux:
LD_LIBRARY_PATH=userlocalOracleBIodbclib: LD_LIBRARY_PATH export LD_LIBRARY_PATH
3.
Save and close the file.
4.
Open the odbc.ini file. You can find this file at: ORACLE_INSTANCE
bifoundationOracleBIApplicationcoreapplicationsetupodbc.ini
5.
Create an entry for your database, ensuring that the ODBC connection name is identical to the data source name specified in the connection pool defined in the
repository. Be sure to set the Driver parameter to the file name and location of the DataDirect Connect driver for Sybase ASE Database. For NetworkAddress,
provide the IP address or fully qualified host name and the port number.
In the following example, the Driver parameter is set to the 64-bit DataDirect Connect driver, and the data source name is SybaseASE_DB.
[SybaseASE_DB] Driver=usrOracleBIodbclib64SEase23.so
Description=DataDirect 5.3 Sybase Wire Protocol AlternateServers=
ApplicationName= ApplicationUsingThreads=1
ArraySize=50 AuthenticationMethod=0
Charset= ConnectionRetryCount=0
ConnectionRetryDelay=3 CursorCacheSize=1
Database=Paint DefaultLongDataBuffLen=1024
EnableDescribeParam=0 EnableQuotedIdentifiers=0
EncryptionMethod=0 GSSClient=native
HostNameInCertificate= InitializationString=
Setting Up Data Sources on Linux and UNIX 15-9
Language= LoadBalancing=0
LogonID=my_id NetworkAddress=111.111.111.111,5005
OptimizePrepare=1 PacketSize=0
Password= RaiseErrorPositionBehavior=0
ReportCodePageConversionErrors=0 SelectMethod=0
ServicePrincipalName= TruncateTimeTypeFractions=0
TrustStore= TrustStorePassword=
ValidateServerCertificate=1 WorkStationID=
6.
Save and close the odbc.ini file.
Configuring the DataDirect Connect ODBC Driver for Informix Database
The name of the DataDirect ODBC driver file to connect to an Informix database is SEifcl23.so. See
System Requirements and Certification for information about
supported versions of Informix.
To configure the DataDirect Connect ODBC Driver to connect to Informix: 1.
Open the user.sh file. You can find this file at: ORACLE_INSTANCE
bifoundationOracleBIApplicationcoreapplicationsetupuser.sh
2.
In the section for your operating system, include the appropriate library path environment variable for the DataDirect Connect libraries. Make sure to point to
the appropriate library, depending on whether you are using a 32-bit or 64-bit database. Note the following:
■
For Solaris and Linux, the library path variable is LD_LIBRARY_PATH.
■
For HP-UX, the library path variable is SHLIB_PATH.
■
For AIX, the library path variable is LIBPATH. For example, to set the library path variable for the 32-bit driver on Linux:
LD_LIBRARY_PATH=userlocalOracleBIodbclib: LD_LIBRARY_PATH export LD_LIBRARY_PATH
3.
Save and close the file.
4.
Open the odbc.ini file. You can find this file at: ORACLE_INSTANCE
bifoundationOracleBIApplicationcoreapplicationsetupodbc.ini
5.
Create an entry for your database, ensuring that the ODBC connection name is identical to the data source name specified in the connection pool defined in the
repository. Be sure to set the Driver parameter to the file name and location of the DataDirect Connect driver for Informix. Also, you must specify the HostName
parameter you can use the fully qualified host name or the IP address and the PortNumber parameter.
In the following example, the Driver parameter is set to the 64-bit DataDirect Connect driver, and the data source name is Informix_DB.
15-10 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition
[Informix_DB] Driver=usrOracleBIodbclib64SEifcl23.so
Description=DataDirect Informix Wire Protocol AlternateServers=
ApplicationUsingThreads=1 CancelDetectInterval=0
ConnectionRetryCount=0 ConnectionRetryDelay=3
Database= HostName=111.111.111.111
LoadBalancing=0 LogonID=informix
Password=mypassword PortNumber=1526
ReportCodePageConversionErrors=0 ServerName=
TrimBlankFromIndexName=1
6.
Save and close the odbc.ini file.
Configuring Database Connections Using Native ODBC Drivers
Oracle Business Intelligence bundles UNIX ODBC drivers for some data sources, but not all. For these data sources, including Teradata, you must install your own ODBC
driver, then update the user.sh and odbc.ini files to configure the data source.
To configure a database connection using a native ODBC driver: 1.
Install the ODBC driver for your data source.
2.
Open the user.sh file. You can find this file at: ORACLE_INSTANCE
bifoundationOracleBIApplicationcoreapplicationsetupuser.sh
3.
In the section for your operating system, include the appropriate library path environment variable for the native ODBC driver. Make sure to point to the
appropriate library, depending on whether you are using a 32-bit or 64-bit database. Note the following:
■
For Solaris and Linux, the library path variable is LD_LIBRARY_PATH.
■
For HP-UX, the library path variable is SHLIB_PATH.
■
For AIX, the library path variable is LIBPATH. For example, to set the library path variable for Teradata on Linux:
LD_LIBRARY_PATH=usrodbclib:usrlpptdodbcodbcdrivers: LD_LIBRARY_PATH export LD_LIBRARY_PATH
Note that for Teradata in particular, you need to put usrodbclib at the beginning of the library path variable before all other entries. This step is only
required for Teradata.
4.
Save and close the file.
5.
Open the odbc.ini file. You can find this file at: ORACLE_INSTANCE
bifoundationOracleBIApplicationcoreapplicationsetupodbc.ini
6.
Create an entry for your database, ensuring that the ODBC connection name is identical to the data source name specified in the connection pool defined in the
repository. Be sure to set the Driver parameter to the file name and location of the
Setting Up Data Sources on Linux and UNIX 15-11
native ODBC driver for your database, with the library suffix appropriate for your operating system for example, .so for Solaris and AIX, or .sl for HP-UX.
The following example provides details for a Teradata data source on Solaris, with a data source name of Terav502.
[Terav502] Driver=usrodbcdriverstdata.so
Description=NCR 3600 running Teradata V2R5.2 DBCName=172.20.129.42
LastUser= Username=
Password= Database=
DefaultDatabase=name_of_target_database_or_user
Note that the DefaultDatabase parameter can be left empty only if you have selected the option Require fully qualified table names in the General tab of the
Connection Pool dialog for this data source in the Administration Tool.
7.
Still in the odbc.ini file, add an entry to the section [ODBC Data Sources] with the details appropriate for your data source. The following example provides details
for a Teradata data source with a data source name of Terav502.
Terav502=tdata.so
8.
Using the Administration Tool, open the repository and add the new DSN you created as the Connection Pool Data source name for the appropriate physical
databases. See Creating or Changing Connection Pools
for more information.
9.
Restart the Oracle BI Server.
Configuring Oracle RPAS ODBC Data Sources on AIX UNIX
You can access Oracle RPAS ODBC data sources when the Oracle BI Server is running on an AIX UNIX platform. To configure this database connection, first update the
odbc.ini file to configure the Oracle RPAS ODBC data source, then use the rdaadmin tool to define dimension tables as not normalized at run time.
See Setting Up Oracle RPAS Data Sources
for information about configuring Oracle RPAS ODBC data sources on Windows.
To configure Oracle RPAS ODBC as a data source on AIX UNIX: 1.
Log on as a separate telnet session.
2.
Open the odbc.ini file. You can find this file at: ORACLE_INSTANCE
bifoundationOracleBIApplicationcoreapplicationsetupodbc.ini
3.
In the RPAS data source section, edit the values. For example: [RPAS Sample]
Data Source Name=RPAS Sample Driver=[client RPASClientlibraixoaodbc.so
DriverUnicodeType=1 Description=OpenRDA DSN
The Data Source Name you provide must match the value entered for DATABASE: in Step 3 of the following procedure. Also, you must add the line
DriverUnicodeType=1 as shown in the preceding example.
15-12 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition
To use the rdaadmin client tool to define dimension tables as not normalized at run time:
1.
Locate the rdaadmin client tool in the following location: binrdaadmin
2.
Run the rdaadmin client tool by typing the following command: rdaadmin
3.
Enter appropriate text when prompted, as follows: DATABASE: [Oracle_RPAS_database_name]
The database name must match the name given for the Data Source Name in the previous task for example, RPAS Sample.
ADDRESS: [ip_address] PORT: [port_number]
An example port number value is 1707. CONNECT_STRING: [NORMALIZE_DIM_TABLES=NO]
This value treats dimension tables as not normalized at run time. TYPE: []
SCHEMA_PATH: [] REMARKS: []
4.
The RPAS environment variable OPENRDA should be declared in the Oracle BI Server session on UNIX. For example, declare the variable as follows using the 64
bit rdaadmin client tool:
OPENRDA_INI=rpasclient64configraixopenrda.ini export OPENRDA_INI
Configuring Essbase Data Sources on Linux and UNIX
The Oracle BI Server uses the Essbase client libraries to connect to Essbase data sources. You must ensure that the Essbase client libraries are installed on the computer
running the Oracle BI Server before you can set up a connection to Essbase data sources. See
System Requirements and Certification for information about supported
versions of the Essbase Client for use with Oracle Business Intelligence. After you install the Essbase client libraries, ensure that the PATH environment
variable includes the location of the Essbase client driver. For example, to configure access to Essbase client libraries on Linux 32-bit, add the Essbase Client Libraries
directory to LD_LIBRARY_PATH:
LD_LIBRARY_PATH=LD_LIBRARY_PATH:Essbase_Client_Libraries_directory For example:
LD_LIBRARY_PATH=LD_LIBRARY_PATH:exporthomeHyperionAnalyticServicesClientbin export LD_LIBRARY_PATH
Set the appropriate variable for your operating system, using the appropriate syntax. For example, update LIBPATH on AIX, SHLIB_PATH on HP-UX Itanium, and LD_
LIBRARY_PATH_64 on Solaris 64-bit.
Setting Up Data Sources on Linux and UNIX 15-13
You also need to ensure that an additional environment variable is set appropriately either ESSBASEPATH or ARBORPATH, depending on your client version. For more
information, see Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide or the equivalent title for your client version.
Finally, you need to update opmn.xml with the appropriate Essbase client library information. See
Updating Essbase Information in opmn.xml for more information.
Configuring DB2 Connect on IBM zOS and s390 Platforms
IBM DB2 Connect does not support the option of automatically disconnecting when an application using it receives an interrupt request.
When the native database uses DB2 Connect workstation, then you must change the setting of the parameter INTERRUPT_ENABLED. This parameter must be changed on
any Oracle Business Intelligence computer if the database or any data source resides on IBM DB2 on a mainframe running zOS or s390 platforms.
To configure the INTERRUPT_ENABLED parameter: 1.
Configure a database alias to be used as the native CLI Data Source Name. For example, create a new database entry using DB2 Configuration Assistant.
2.
Using the database alias created and the name of the actual target DB2 database, set the INTERRUPT_ENABLED parameter using the following syntax:
uncatalog dcs db local_dcsname catalog dcs db local_dcsname as target_dbname parms \,,INTERRUPT_ENABLED\
where:
– local_dcsname represents the local name of the host or database database
alias name
Note: The following additional steps are required for HP-UX
Itanium systems:
1.
Define ESSLANG and LANG. For example:
ESSLANG=English_UnitedStates.UTF-8Binary export ESSLANG
LANG=en_US.utf8 export LANG
2.
Comment out LOCALE, SORT_ORDER_LOCALE, and SORT_TYPE in the NQSConfig.ini file. For example:
[ GENERAL ] LocalizationInternationalization parameters.
LOCALE=English-usa; SORT_ORDER_LOCALE=English-usa;
SORT_TYPE=binary;
Note: If IBM DB2 is used, DB2 Connect must be installed on the
Oracle BI Server computer. The version of DB2 Connect must match the most recent DB2 instance that was configured as a data source.
15-14 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition
– target_dbname represents the name of database on the host or database
system
The following example uses an OS390 DB2 instance: uncatalog dcs db DB2_390
catalog dcs db DB2_390 as Q10B parms \,,INTERRUPT_ENABLED,,,,,\ catalog database DB2_390 as DB2_390 at node NDE1EF20 authentication dcs
Note: Be sure to use backslashes to pass the quotation marks as part
of the string.
16
Managing Oracle BI Repository Files 16-1
16
Managing Oracle BI Repository Files
This chapter provides information about topics related to managing your repository files, including comparing and merging repositories, equalizing objects, and querying
and managing metadata.
This chapter contains the following topics:
■
Comparing Repositories
■
Equalizing Objects
■
Merging Repositories
■
Querying and Managing Repository Metadata
■
Changing the Repository Password
Comparing Repositories
This section explains how to use the Compare repositories dialog in the Administration Tool. This feature enables you to compare all repository objects in two
different repositories.
If you are using an Oracle BI Applications repository and have customized its content, you can use this option to compare your customized repository to a new version of the
repository received with Oracle BI Applications.
See Merging Repositories
for more information about merging your customized Oracle BI Applications repository with a new version of the repository.
To compare two repositories: 1.
In the Administration Tool, open a repository in offline mode. The repository that you open in this step is referred to as the current repository.
See Using Online and Offline Repository Modes
for instructions on opening a repository.
2. From the File menu, select Compare.
