ODI Console Step By Step configurations

1 .	Open the Command Prompt window. Change directory to: <WLS-HOME>\common\bin (for example: C:\oracle\Middleware\Oracle_ODI1\common\bin). Execute config command. The Configuration Wizard starts.
2.	In the Welcome screen, select: Extend an existing WebLogic domain. Click Next. In the screen that follows, select the domain ODI-DOMAIN, as shown on the screenshot. Click Next.
3 .	In the screen that follows, select the Oracle Enterprise Manger Plugin For ODI – 11.1.1.0, which will also include the Oracle Enterprise Manager – 11.1.1.0. Also select Oracle Data Integrator-Console-11.1.1.0. Click Next. In the screen that follows, click OK to replace the existing component. Click Next. In the screen that follows, click OK to replace the existing component odi_server1, that was created earlier.
4 .	In the next screen, accept the default application location. Click Next.
5 .	The wizard will set up the ODI repository connection within the domain server. During the wizard configuration, the repository connection information must be supplied. Click the check boxes next to ODI Master schema, and next to ODI Work schema. Configure the JDBC component schema as shown in the following table. Click Next. Verify that the test was successful (if not, correct any connectivity settings). Click Next. Database Connection (Master Repository) Parameter Value Vendor Oracle Driver Oracle’s driver (Thin) for Instance connections Master Schema Owner snpm1 Master Schema Password oracle1 Work Schema Owner snpw1 Work Schema Password oracle1 DBMS/Service orcl Host Name localhost Port 1521
6 .	In the next screen, select Managed Servers, Clusters and Machines. Click Next. Verify that Listen port is set to 8001 for managed server odi_server1. Click Next. In the Configure Clusters screen, click Next.
7 .	In the Configure Machines screen, click Next. The Assign Servers to Machines screen will already have the odi_server1 assigned to localODImachine. Click Next. Review the Configuration Summary, and then click Extend. When the domain is created, click Done.

Connecting to the WebLogic server and managed server odi_server1.

Now that you have created and extended the WebLogic domain with the Enterprise Manager, you need to connect to WebLogic server and managed server odi_serevr1.

1.	In the command shell, change directory to the directory of the WLS Home - C:\Oracle\Middleware\user_projects\domains\ODI-DOMAIN\bin . Execute the startweblogic command.
2 .	To start managed server odi_server_1, change directory to WLS Home - C:\Oracle\Middleware\user_projects\domains\ODI-DOMAIN\bin , and use the execute command: StartManagedWeblogic odi_server1. For Username, enter weblogic . For the password, enter welcome1 . Verify that your managed server is started in RUNNING mode. Note: You created the credential store for ODI Supervisor and for the domain ODI-DOMAIN in the OBE: Deploying and Configuring the ODI Agent as Java EE Application. Note: All commands are case-sensitive! You can copy commands from the text file provided HERE.
3 .	If not started, start ODI Designer and connect to ODI Work repository (WORKREP1). For user SUPERVISOR, eneter password: SUNOPSIS. Open Topology Navigator, open Physical architecture and then open ODI JEE agent OracleDIAgent. Click Test icon to test connectivity of your ODI Java EE agent. Click OK. Close OracleDIAgent tab. Use Enterprise Manager to Administer ODI With Enterprise manager, explore your ODI environment and resources. 1. Start the browser and enter URL: http://localhost:7001/em . Log in to Enterprise Manager. For the user, enter weblogic . For the password, enter welcome1 . On the screen that follows, click Continue.   2. With Enterprise Manager, a process and resources can be monitored and managed. You can explore the deployed application by clicking on each link. You can see running processes, workload, log file information, and more. Drill down into ODI objects by expanding ODI > odiconsole > MASTER REPOSITORY in the left panel, as shown in the following screen. Note: Your information may differ from the information provided on these screens. 3 . Click MASTER REPOSITORY to view more details. Click the OracleDIAgent to see the Java EE agent information. 4 . Click the localagent node to see details for the standalone agent. 5 . Expand the Application Deployment node, and then click oraclediagent . View the WebLogic server application deployment information. Use ODI Console to Explore ODI Environment With ODI Console, explore your ODI environment. 1 . Start the browser and enter URL: http://localhost:8001/odiconsole to start the Oracle Data Integrator Console. To log in Work reposotory, enter SUPERVISOR for the user ID, and enter SUNOPSIS for the password. Expand the Design Time tab and then expand Projects, Models , and Topology as shown on the screenshot below. Note: Your projects may differ from the information provided on these screens. 2 . Select the Procedure-CRT-TBL project, and then click the View icon. 3 . Click the First Folder link. Click the Procedures tab. Scroll-down, and then select procedure PRD-create-populate-table. 4 . Scroll-down and view details for this procedure. 5 . Expand: Runtime > Sessions > All Sessions. Select session PRD-create-populate table- 1001, and then click View icon . Scroll-down and view execution information for selected session. Similarly, expand Topology > Agents > Physical Agents. View information for your agents. You may wish to continue exploration of your ODI environment. Note: To view information for each selected node, click icon. 6 . To stop managed WebLogic server odi_server1 and then WebLogic server, change directory to WLS Home - C:\Oracle\Middleware\user_projects\domains\ODI-DOMAIN\bin, and then execute the following command: stopManagedWebLogic odi_server1. For Username, enter weblogic . For the password, enter welcome1 . To stop WebLogic server, execute the command: stopWebLogic.

Error Table Structure in oracle data integrator

Error Table Structure

The E$ error table has the list of columns described in the following table:

Columns	Description
[Columns of the checked table]	The error table contains all the columns of the checked datastore.
ERR_TYPE	Type of error: 'F' when the datastore is checked during flow control 'S' when the datastore is checked using static control
ERR_MESS	Error message related to the violated constraint
CHECK_DATE	Date and time when the datastore was checked
ORIGIN	Origin of the check operation. This column is set either to the datastore name or to an interface name and ID depending on how the check was performed.
CONS_NAME	Name of the violated constraint.
CONS_TYPE	Type of the constraint: 'PK': Primary Key 'AK': Alternate Key 'FK': Foreign Key 'CK': Check condition 'NN': Mandatory column