Dac10 1 3 4 1
Dac10 1 3 4 1
Console
Release Notes
Version 10.1.3.4.1
Part No. E12655-06
March 29, 2010
These release notes describe known issues and workarounds for the Oracle Business
Intelligence Data Warehouse Administration Console releases 10.1.3.4 and 10.1.3.4.1.
The Oracle Business Intelligence Data Warehouse Administration Console is a
centralized console for schema management as well as configuration, administration,
loading, and monitoring of the Oracle Business Analytics Warehouse.
The following list describes the sections of this document:
■ Section 1, "How to Use These Release Notes"
■ Section 2, "General Issues and Workarounds"
■ Section 3, "Oracle Business Intelligence Data Warehouse Administration Console:
General"
■ Section 4, "Documentation Accessibility"
1
2.2 Installation and Upgrade
This section provides release notes on installing and upgrading Oracle Business
Intelligence Data Warehouse Administration Console. It contains the following topics:
■ Section 2.2.1, "DAC Release 10.1.3.4 Usage with Oracle Business Intelligence
Applications"
■ Section 2.2.2, "Invoke setup.exe From the Relevant Platform Directory on the
Installation CD-ROM"
■ Section 2.2.3, "Oracle Universal Installer Cannot Install DAC On A UNIX
Platform"
■ Section 2.2.4, "Co-locate the DAC Server With the Informatica Server"
■ Section 2.2.5, "Informatica Static Parameter Files Need to Be Copied from Oracle
Business Intelligence Applications Installation Folder to DAC 10.1.3.4 Folder"
■ Section 2.2.6, "Oracle Universal Installer Cannot Remove DAC"
■ Section 2.2.7, "Deinstalling DAC 10.1.3.4.1"
■ Section 2.2.8, "Custom SQL and Index Overrides Are Obsoleted"
■ Section 2.2.9, "Installing DAC 10.1.3.4.1 On a Non-English Environment Server
Without an Oracle Home"
■ Section 2.2.10, "Platform Upgrade Users Should Accept Target for Phases Before
Merge"
■ Section 2.2.11, "Installer Requests Oracle Home Location"
■ Section 2.2.12, "DAC Behavior for Truncating Tables When Upgrading from DAC
7.9.x to DAC 10.1.3.4.1"
2.2.1 DAC Release 10.1.3.4 Usage with Oracle Business Intelligence Applications
This issues applies to Release 10.1.3.4 and 10.1.3.4.1.
DAC release 10.1.3.4 is an Oracle BI foundation component that is designed to be used
with Oracle Business Intelligence Applications. Before installing DAC release 10.1.3.4,
ensure that a working instance of any prior release of DAC exists in your current
Oracle Business Intelligence Applications environment.
DAC release 10.1.3.4 will be installed in an Oracle home directory, which is a different
directory from the current working Oracle BI/DAC directory. Therefore, DAC release
10.1.3.4 can be installed on the same machine that contains your current release of the
DAC Client (or DAC Server). DAC release 10.1.3.4 can co-exist with previous releases.
When the DAC Client release 10.1.3.4 is configured to read DAC metadata in the
current DAC repository database for the first time, the current DAC repository will be
upgraded to be compatible with DAC release 10.1.3.4. Only the DAC Client release
10.1.3.4 (and DAC Server release 10.1.3.4) can be used to read that repository after the
upgrade.
2.2.2 Invoke setup.exe From the Relevant Platform Directory on the Installation
CD-ROM
This issue applies to Releases 10.1.3.4 and 10.1.3.4.1.
You need to invoke the DAC setup.exe file from the relevant platform directory on the
installation CD-ROM.
2
For example, to install DAC on the Windows 32-bit version, you need to access the
setup.exe file from the directory \dac\disk1\install\win32\setup.exe.
Workaround
1. On the Windows machine on which the DAC Client is installed, create a
temporary directory (for example, a directory named \OracleBI_UNIX\).
You will use this temporary directory to create a zip file for the UNIX/Solaris
deployment.
2. Copy the \DAC\ directory to the temporary directory (for example, \OracleBI_
UNIX\).
3. From the \DAC\ directory in the temporary directory, remove the \export and
\icons sub-folders.
4. Zip up the temporary directory (for example, \OracleBI_Solaris\).
5. Copy the ZIP file to the target UNIX machine.
Note: If you use FTP to copy the zip file, use binary mode.
6. On the target UNIX machine, place the zip file in a directory where you want to
install the DAC server.
7. On the target machine, unzip the zip file.
8. Shell scripts are provided in the DAC/unix_script_bkp directory. Copy these files
to the /DAC directory.
After copying these files to a UNIX machine and before using them, you may need
to use a MS-DOS to UNIX conversion tool to convert the script files to UNIX
format (that is, remove the carriage return and line feed characters). Alternatively,
you can manually remove the carriage return and line feed characters from the
script files.
9. On the UNIX machine copy the appropriate JDBC drivers to the /DAC/lib
directory.
10. If required, edit the config.sh or config.csh file located in the /DAC directory to
point to the correct version of the Java JDK by setting the JAVA_HOME
environment variable.
3
2.2.5 Informatica Static Parameter Files Need to Be Copied from Oracle Business
Intelligence Applications Installation Folder to DAC 10.1.3.4 Folder
This issues applies to Releases 10.1.3.4 and 10.1.3.4.1.
After you install DAC 10.1.3.4, you need to copy the Informatica static parameter files
named parameterfileDW.txt and parameterfileOLTP.txt from the Oracle BI
Applications installation folder into the DAC 10.1.3.4 folder.
1. Navigate to the Oracle BI Applications folder
\OracleBI\DAC\Informatica\parameters\input.
2. Copy the static parameter files named parameterfileDW.txt and
parameterfileOLTP.txt into the DAC 10.1.3.4 folder
\DAC\Informatica\parameters\input.
Workaround
Use the following procedures to remove DAC manually.
On all platforms:
■ Delete the entire ORACLE_HOME directory location where DAC is installed.
This is the location that is specified during the installation location of DAC.
On a Windows platform, perform the following additional steps:
1. Locate the installed DAC Oracle Home Name ID, as follows:
a. Start the Windows registry editor 'regedit'.
b. Go to "HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE".
c. In "HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE", locate the registry
key name beginning with "KEY_" that has the ORACLE_HOME value set to
the installed DAC location.
d. Make a note of the value of ORACLE_HOME_NAME, which is the Oracle
Home Name ID.
In the remaining steps of this task, the Oracle Home Name ID will be referred
to as ${ORACLE_HOME_NAME}.
2. Delete the registry key "HKEY_LOCAL_
MACHINE\SOFTWARE\ORACLE\KEY_${ORACLE_HOME_NAME}".
3. Delete the registry key "HKEY_LOCAL_
MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Oracle Merant ODBC Driver in
DAC 10g_Oracle - ${ORACLE_HOME_NAME}".
4. Delete the registry value "Oracle Merant ODBC Driver in DAC 10g_Oracle -
${ORACLE_HOME_NAME}" in "HKEY_LOCAL_
MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers Oracle Merant
ODBC Driver in DAC 10g_Oracle - ${ORACLE_HOME_NAME}".
4
5. In Windows Explorer, navigate to the folder "C:\Documents and Settings\All
Users\Start Menu\Programs\${ORACLE_HOME_NAME}-Oracle Business
Intelligence".
6. If the \Programs\${ORACLE_HOME_NAME}-Oracle Business Intelligence folder
contains one folder named "${ORACLE_HOME_NAME}-DataWarehouse
Administration Console 10g", then delete the folder "C:\Documents and
Settings\All Users\Start Menu\Programs\${ORACLE_HOME_NAME}-Oracle
Business Intelligence".
7. If the \Programs\${ORACLE_HOME_NAME}-Oracle Business Intelligence folder
contains multiple folders, then delete the folder named "${ORACLE_HOME_
NAME}-DataWarehouse Administration Console 10g".
Use the following commands to deinstall DAC using the silent deinstall command
■ For Windows, enter the following command:
%ORACLE_HOME%\oui\bin\setup.exe -ignoreSysPrereqs -silent
-waitforcompletion -noconsole -nowait -deinstall OH_HOME_
DEINSTALL=true
■ For Linux, enter the following command:
$ORACLE_HOME/oui/bin/runInstaller -ignoreSysPrereqs -sd OH_
HOME_DEINSTALL=true
5
2.2.8 Custom SQL and Index Overrides Are Obsoleted
This issues applies to Releases 10.1.3.4 and 10.1.3.4.1.
Custom SQL and Index Overrides are not supported by DAC 10.1.3.4. If you are
upgrading from an Oracle Business Intelligence Applications 7.9.x release of DAC, you
need to manually convert your XML definitions to actions, as described in this section.
For all tasks, this issue applies to:
■ Pre-Full-Load Command
■ Pre-Incremental Load Command
■ Post-Full-Load Command
■ Pre-Incremental Load Command
For tasks that are of type SQL File, this issue applies to:
■ Load Types
- Full Command
- Incremental Command
■ Indexes
- Index overrides
6
You can specify an Operation System group that has write permissions to the above
directory."
2.2.10 Platform Upgrade Users Should Accept Target for Phases Before Merge
This issues applies to Releases 10.1.3.4 and 10.1.3.4.1.
The DAC upgrade process generates a difference report highlighting conflicts and
offers some default actions to resolve the conflicts. In the case of the Platform Upgrade
(upgrading from DAC 7.8 to DAC 10.1.3.4), "Accept Source" is usually the default
action.
However, users should explicitly choose to "Accept Target" when "Phase" is shown as
different between the source and the target.
Users should choose "Accept Source" for phase differences in other kinds of upgrade
scenarios like Refresh Base or Replace Base.
Workaround
Provide an empty folder location as the Oracle Home for DAC.
2.2.12 DAC Behavior for Truncating Tables When Upgrading from DAC 7.9.x to DAC
10.1.3.4.1
When upgrading from DAC 7.9.x to DAC 10.1.3.4.1, DAC does not truncate some
target tables even if the Truncate Always flag is selected on the target table. This occurs
when more than one DAC task writes to the target table.
The DAC behavior for truncating tables when more than one DAC task writes to the
target table is as follows:
■ The first DAC task truncates the target table. DAC does not truncate the target
tables during the execution of the subsequent tasks even if the Truncate Always or
Truncate for Full Load flags are checked on the subsequent tasks.
■ DAC truncates a target table only once during the life span of one ETL execution.
■ If the DAC task belongs to a group and the group truncate property is different
from the individual task truncate properties, the target table will be not truncated.
You need to identify those tasks and associate a truncate table task action as a
preceding action to these tasks if the truncate is truly desired.
7
The DAC online help and manuals were not updated to reflect changes made to the
DAC 10.1.3.4.1 installer and user interface.
There is no workaround for this issue.
8
In DAC 10.1.3.4, you can work around this issue by exporting files only into a new
folder or into an erasable folder containing DAC metadata.
In DAC 10.1.3.4.1, the Export behavior was modified as follows:
■ If the target folder is empty, DAC exports without a warning.
■ If the target folder contains DAC metadata, DAC exports after warning and when
OK is clicked. The process replaces all content in the target folder with a new
export.
■ If the target folder has non-DAC metadata along with DAC Metadata, DAC
exports after warning and when OK is clicked. The process replaces all content in
the target folder with new export. All non-DAC metadata is deleted.
■ If the target folder has only non-DAC metadata, DAC cannot export into that
target folder.
Workaround
Use the following procedure to force password encryption.
Encrypted string
–>dMGpMvpsuQwXD5UvRmq0OZxhppTWK0Y7fzBtxHL04Gg=<–
Will decrypt to –>Administrator<–
9
3. Modify the file DAC\conf\infa_command.xml by replacing all occurrences of
<-p> with <-pv> and <-x> with <-X>.
4. Stop the DAC server.
5. Log into the DAC client and navigate to the Setup menu and choose the
Informatica Servers tab.
6. Highlight the Informatica Server record and enter the name of the environment
variable that you created in Step 2 of this procedure as the value of Password. Save
the record.
7. Repeat the previous step for the Informatica Repository Server.
8. Close and re-open the client to test the connections.
9. If the DAC server is located on the same machine, start the DAC server and run
ETL.
10. Verify that DAC issues the following pmcmd command.
pmcmd startworkflow -sv BI_DW_Server -d <Domain> -u Administrator -pv **** -f
<folder> -lpf <filename><workflow>
INFORMATICS TASK:<workflow> has finished execution with Completed status.
1. Set the environmental variable on the server machine and modify the
DAC\conf\infa_command.xml.
2. Shut down the DAC server when testing Informatica connectivity or unit
testing a DAC task via the DAC client.
12. If the DAC server is on a non-Windows machine, do the following:
1. Set the environmental variable on the server machine and modify the
DAC\conf\infa_command.xml.
2. Shut down the DAC server when testing Informatica connectivity or unit
testing a DAC task via the DAC client.
Workaround
Perform the following procedure before manipulating the user's properties.
Note: These steps are required every time user passwords are
modified on DAC 10.1.3.4 when the DAC server is on AIX.
10
2. Go to the DAC Client Set Up dialog and select the System Properties tab. Change
the Server OS property from AIX to Windows (or any other value).
3. Save and close the client.
4. Make and save the required user changes.
5. Save and close the client.
6. Open the client and set the Server OS property back to AIX.
7. Save and close the client.
8. Start the DAC server and DAC client and confirm that the error message does not
appear.
Workaround
To prevent this issue, you must perform the following configuration.
1. Shut down the DAC server.
2. Open the client and read the DAC repository. If the DAC repository is a prior
release, click Yes when prompted to upgrade.
3. Go to the Setup menu and choose DAC System Properties. Enter the DAC server
information.
4. On the AIX machine hosting the DAC server, navigate to the directory containing
ServerSetupPrompt.sh.
5. Execute ServerSetupPrompt.sh.
6. Re-enter all passwords wherever they apply (for example, DAC repository and
email).
7. Save your changes and start the DAC server.
11
exactly as in the Informatica sessions. In DAC 10.1.3.4 and DAC 10.1.3.4.1, DAC
generates parameter files and log files with variable names and therefore it is not
possible to re-run workflows directly from Informatica.
Workaround
Always run tasks from DAC using the Preview Run Details in the Execute view to unit
test individual workflows.
12
3.8 Configuring DAC to Create a Different Number of Parallel Indexes by
Table
This issues applies to Release 10.1.3.4.1 only.
In the past, users could configure the number of parallel indexes that DAC created for
a given connection. This property applied to all tables in that connection. It was not
possible to create only one index at a time on one table and more than one index at a
time on another table. In DAC 10.1.3.4.1, users can configure the number of parallel
indexes in two ways: at a connection level that applies to all tables or at a table level
within a connection that applies to specific tables.
At a connection level that applies to all tables – This method is set by accessing the
DAC client, selecting the Setup menu, choosing Physical Data Source, then choosing
Edit (Sub Tab), and specifying a value in the Number of Parallel Connections per Table
field.
This value applies to all tables in this connection. For example, if the value is 2, then
DAC creates two indexes in parallel on all tables.
At a table level within a connection that applies to specific tables – This method is
set by accessing the DAC client, selecting the Setup menu, choosing Physical Data
Source, then choosing the Parallel Indexes (Sub Tab). Enter the Name of the Table and
number of indexes you want to run in parallel for that table
The value set at the table level overrides the value set at the connection level
(described in the "At a connection level that applies to all tables" method, above).
For example, if a user configures DAC to create two parallel indexes on all tables in the
data warehouse connection and sets DAC to create one index in parallel on W_
ORDER_F, then DAC creates two indexes at a time on all tables except W_ORDER_F,
for which only one index will be created at a time.
13
the below text for an example. Note that in the following example, an error occurs
because DAC issues pmcmd with -lpf in the syntax.
$$SYND_DS_PARTITION_TRUNCATE_SQL_TEXT=SELECT
LTRIM(MAX(SYS_CONNECT_BY_PATH('execute immediate ''ALTER TABLE
getTableName() TRUNCATE PARTITION ' || '"' ||COUNTRY_REGION_NAME|| '"' ||''''
WHERE SOURCE='W_SYNDD_DS_FS')
CONNECT BY prev = PRIOR curr START WITH curr = 1
Workaround
To prevent this issue, edit DAC\Conf\infa_command.xml and replace all instances of
<-lpf> with <-paramfile>.
This workaround will ensure that DAC uses -paramfile in the pmcmd syntax and
Informatica can recognize the multi-line parameters.
Workaround
14
7. Re-enter the passwords for all Informatica servers (services) and all physical data
source connections. To re-enter the passwords, access the DAC Client and choose
the Setup view.
3.12 Importing the Data Warehouse Container Into the DAC Repository
This issues applies to Release 10.1.3.4.1 only.
Most DAC repository objects are developed in the data warehouse container and
referenced into other source system containers that are shipped out of the box.
Customers using DAC 10.1.3.4.1 can import the Oracle Business Intelligence
Applications 7.9.6. data warehouse container.
15
This release of the Teradata JDBC Driver is distributed as platform-independent JAR
files in both ZIP (TeraJDBC__indep_indep.13.00.00.00.zip) and TAR (TeraJDBC__
indep_indep.13.00.00.00.tar).
Perform the following procedure to properly set the classpath to refer to the correct
JAR files.
1. Download either the ZIP file or the TAR file and unzip (or untar) the downloaded
file into a directory of your choice.
2. Copy the following files into the DAC\lib folder.
■ terajdbc4.jar
■ tdgssconfig.jar
3.16 Class Names for Teradata JDBC Driver Changed in Teradata Version
12
This issues applies to Releases 10.1.3.4 and 10.1.3.4.1.
Starting in Teradata Version 12, the class names have changed for the Teradata JDBC
driver. However, the names used in the previous version still work with DAC but with
a warning. To avoid these warnings, modify DAC\conf\connection_template.xml
when using Teradata Drivers Version 12 and above. To modify this file, open the
connection_template.xml file and follow the instructions included in the file.
16
Sources tab. When entering text into these fields, you must be sure to conform to
the database specifications.
■ You can configure the DAC Client connection (to create or connect to the DAC
repository) with user specified URLs in the DAC client login screen.
■ The DAC Server can be configured using specific JDBC URLs.
- If the DAC Server is installed on Windows, you can configure specific JDBC
URLs by accessing the client and using the Server Set Up menu.
- If the DAC Server is installed on Unix or Linux, you can configure the JDBC
URLs by executing ServerSetupPrompt.sh and following the on screen
instructions.
3.19 DAC Parameters Can Be Specified for Full Load or Incremental Load
ETLs
This issue applies to Release 10.1.3.4.1 only.
17
Parameters can be registered in DAC as either Source System Parameters or Task Level
Parameters.
Source System Parameters – A list of parameter names and the values applicable to
each source system can be registered by accessing DAC, then Design View, and using
the Source System Parameter tab.
Task Level Parameters – Parameters that apply to all tasks under a source system may
be registered under the Source System Parameters. If there are parameters that are
specific to particular tasks, developers can create such task specific parameters by
accessing the Task tab and using the Parameters subtab. Task level parameters have
priority over source system parameters. If the same parameter is registered as a source
system parameter and as a task level parameter, DAC will evaluate the parameter with
the task level value.
Both Source System Parameters and Task Level Parameters are enhanced in DAC
10.1.3.4.1 where customers can specify different values for the parameters for full load
ETL runs and/or for incremental load ETL runs. A new field called "Load Type" has
been added in the Parameters tab for specifying a value as it applies to the parameter.
For example, if you have a parameter called "SourceSystemParameter" at the source
system level, you can define this parameter as shown in the following table.
18
PersonDimension_TD as full and incremental commands, respectively, on a Teradata
database.
1. In the DAC Design view, go to the Tasks tab.
2. Query for the task to which you want add multiple workflows.
3. Select the task, and then click the Parameters subtab.
4. Create a new parameter for a full load command:
a. Click New in the subtab toolbar.
b. In the Name field, enter $$workflow_CMD_PARAMETER.
c. In the Data Type field, select DB Specific Text.
d. In the Load Type field, select Full.
e. Click in the Value field to open the Enter Parameter Value dialog box.
f. In the Connection Type field, select @DAC_TARGET_DBTYPE.
g. In the appropriate database fields, enter the full command name for both
database types.
For example, enter SIL_PersonDimension_Full in the Oracle field and SIL_
PersonDimension_Full_TD in the Teradata field.
5. Create a new parameter for an incremental load command:
a. Click New in the subtab toolbar.
b. In the Name field, enter $$workflow_CMD_PARAMETER.
c. In the Data Type field, select DB Specific Text.
d. In the Load Type field, select Incremental.
e. Click in the Value field to open the Enter Parameter Value dialog box.
f. In the Connection Type field, select @DAC_TARGET_DBTYPE.
g. In the appropriate database fields, enter the incremental command name for
both database types.
For example, enter SIL_PersonDimension in the Oracle field and SIL_
PersonDimension_TD in the Teradata field.
6. With the same task selected, click the Edit subtab.
7. In the Command for Incremental Load field, enter @DAC_$$workflow_CMD_
PARAMETER.
8. In the Command for Full Load field, enter @DAC_$$workflow_CMD_
PARAMETER.
9. Click Save.
19
then gets parsed to determine whether the workflow is still running, completed
successfully, or failed.
However, for non-English based operating systems DAC issues commands in the
waiting mode (synchronously). This means that when the process completes the exit
code tells DAC whether the workflow succeeded or not.
Workaround
The commands used by DAC to communicate with Informatica are externalized in a
file called infa_commands.xml.
The DAC 10.13.4.1 command template does not have a place holder for specifying the
wait mode. Without this wait mode configuration, on non-English OS based
installation, this results in DAC proceeding with the execution even before the
workflow completes executing. This might result in errors, such as Informatica's bulk
loader failing because of index presence or fact tables getting loaded without foreign
key references.
To fix the problem, go to DAC\conf folder and edit the file called infa_commands.xml.
Depending upon the version of informatica you are using, edit either the block called
START_WORKFLOW_7 or START_WORKFLOW_8 and verify whether
%WAITMODE is in the syntax. If it is not, add it as follows:
1. For START_WORKFLOW_7 replace the following line:
pmcmd startworkflow -u %USER -p %PASSWORD -s %SERVER:%PORT -f %FOLDER -lpf
%PARAMFILE %WORKFLOW
With:
pmcmd startworkflow -u %USER -p %PASSWORD %WAITMODE -s %SERVER:%PORT -f
%FOLDER -lpf %PARAMFILE %WORKFLOW
With:
pmcmd startworkflow -sv %SERVER -d %DOMAIN -u %USER -p %PASSWORD %WAITMODE -f
%FOLDER -lpf %PARAMFILE %WORKFLOW
3. Once you modify this file (the modifications should be done both on the DAC
client and the server machines), restart the DAC server and client for the changes
to take effect.
4 Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible to all users, including users that are disabled. To that end, our
documentation includes features that make information available to users of assistive
technology. This documentation is available in HTML format, and contains markup to
facilitate access by the disabled community. Accessibility standards will continue to
evolve over time, and Oracle is actively engaged with other market-leading
technology vendors to address technical obstacles so that our documentation can be
accessible to all of our customers. For more information, visit the Oracle Accessibility
Program Web site at http://www.oracle.com/accessibility/.
20
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The
conventions for writing code require that closing braces should appear on an
otherwise empty line; however, some screen readers may not always read a line of text
that consists solely of a bracket or brace.
Oracle Business Intelligence Data Warehouse Administration Console Release Notes, Version 10.1.3.4.1
Part No. E12655-06
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected
by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them
to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following
notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions
and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the
additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway,
Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any
inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications,
then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software.
Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation
and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services.
Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services.
21
22