|Oracle® Enterprise Data Quality for Product Data R12 PIM Connector Installation Guide
Release 11g R1 (18.104.22.168)
Part Number E29141-02
|PDF · Mobi · ePub|
dlsUser and Schema
This chapter describes how to create the
dls user, install the R12 PIM Connector database schema, and associate the installed database schema with the
Note:This chapter presents one EBS environment. Your EBS environment may be different so the computer responses will differ though the commands you execute do not.
The R12 PIM Connector API components are installed on the EBS using Oracle Database user account,
dls. Create the
Log into your EBS database server as user,
applmgr or the user that installed the original EBS instance.
Ensure that your login user environment is sourced.
Following is an example of how to source the
applmgr environment file:
Check that the environment is set correctly:
The return value should be the SID of the EBS database server.
From the system that you installed EDQP, copy the
dls_pim_connector_install folder that you extracted from the product package to a temporary directory on your EBS database server.
On your EBS database server, change directories to the
Create the R12 PIM Connector
dls user in the EBS database server:
sqlplus system/manager@VIS < dls_user_creation.sql
Ensure that the
dls user creation successfully completes and no errors are displayed.
For EBS 12.2.x servers, the
dls user must have the "editions" feature enabled. To enable editions for the
dls user, enter the following command from SQL*Plus:
ALTER USER dls ENABLE editions FORCE;
The PIM Connector database schema which includes tables, views, and packages that implement the PIM Connector API is installed using the
dls_pim_connector_install.sh script into the EBS
dls database user previously created. The necessary grants and privileges to the tables accessed by the Enterprise DQ for Product R12 PIM Connector are configured in the
The installation script uses the existing Transaction tablespace and for the installation of the DLS tables in indexes such as the semantic key cache. This is consistent with current Oracle practice (see MetaLink note 248857.1 under the Product tablespaces link).
The temporary tables used by the Enterprise DQ for Product will be written to the Interface tablespace (see MetaLink note 248857.1 under the Product tablespaces link).
The installation script creates a new schema called
dls that is granted quota on the Transaction and Interface table spaces.
While still logged into the EBS Server as
applmgr and in the
dls_pim_connector_install directory, change the file permissions of the R12 PIM Connector installation script:
chmod +x *.sh
Install the database schema:
Please enter Apps Schema Name for VIS:
Please enter Apps Password for VIS:
Please enter DLS Schema Name for VIS:
Please enter DLS Password for VIS:
dls database schema has now been populated with the tables, views, packages, synonyms and triggers. The
apps schema has also been populated with the grants and synonyms needed to call the Enterprise DQ for Product R12 PIM Connector.
A log file is written to the
tmp directory of the
Review the installation log file,
dls_inst_####.log, and ensure that there were no errors.
The following erroneous error message should be ignored:
Warning: Package created with compilation errors. . Errors for PACKAGE DLS_CONNECTOR_PVT: . LINE/COL ERROR -------- ----------------------------------------------------------------- 49/3 PL/SQL: Declaration ignored 51/66 PLS-00201: identifier 'DLS_CONNECTOR_PUB.G_SEMANTICATTR' must be declared