CREATE TABLE BONUS
(ENAME VARCHAR2(10),
JOB VARCHAR2(9),
SAL NUMBER,
COMM NUMBER);
CREATE TABLE EMP
(EMPNO NUMBER(4) NOT NULL,
ENAME VARCHAR2(10),
JOB VARCHAR2(9),
MGR NUMBER(4),
HIREDATE DATE,
SAL NUMBER(7, 2),
COMM NUMBER(7, 2),
DEPTNO NUMBER(2));
INSERT INTO EMP VALUES
(7369, 'SMITH', 'CLERK', 7902,
TO_DATE('17-DEC-1980', 'DD-MON-YYYY'), 800, NULL, 20);
INSERT INTO EMP VALUES
(7499, 'ALLEN', 'SALESMAN', 7698,
TO_DATE('20-FEB-1981', 'DD-MON-YYYY'), 1600, 300, 30);
INSERT INTO EMP VALUES
(7521, 'WARD', 'SALESMAN', 7698,
TO_DATE('22-FEB-1981', 'DD-MON-YYYY'), 1250, 500, 30);
INSERT INTO EMP VALUES
(7566, 'JONES', 'MANAGER', 7839,
TO_DATE('2-APR-1981', 'DD-MON-YYYY'), 2975, NULL, 20);
INSERT INTO EMP VALUES
(7654, 'MARTIN', 'SALESMAN', 7698,
TO_DATE('28-SEP-1981', 'DD-MON-YYYY'), 1250, 1400, 30);
INSERT INTO EMP VALUES
(7698, 'BLAKE', 'MANAGER', 7839,
TO_DATE('1-MAY-1981', 'DD-MON-YYYY'), 2850, NULL, 30);
INSERT INTO EMP VALUES
(7782, 'CLARK', 'MANAGER', 7839,
TO_DATE('9-JUN-1981', 'DD-MON-YYYY'), 2450, NULL, 10);
INSERT INTO EMP VALUES
(7788, 'SCOTT', 'ANALYST', 7566,
TO_DATE('09-DEC-1982', 'DD-MON-YYYY'), 3000, NULL, 20);
INSERT INTO EMP VALUES
(7839, 'KING', 'PRESIDENT', NULL,
TO_DATE('17-NOV-1981', 'DD-MON-YYYY'), 5000, NULL, 10);
INSERT INTO EMP VALUES
(7844, 'TURNER', 'SALESMAN', 7698,
TO_DATE('8-SEP-1981', 'DD-MON-YYYY'), 1500, NULL, 30);
INSERT INTO EMP VALUES
(7876, 'ADAMS', 'CLERK', 7788,
TO_DATE('12-JAN-1983', 'DD-MON-YYYY'), 1100, NULL, 20);
INSERT INTO EMP VALUES
(7900, 'JAMES', 'CLERK', 7698,
TO_DATE('3-DEC-1981', 'DD-MON-YYYY'), 950, NULL, 30);
INSERT INTO EMP VALUES
(7902, 'FORD', 'ANALYST', 7566,
TO_DATE('3-DEC-1981', 'DD-MON-YYYY'), 3000, NULL, 20);
INSERT INTO EMP VALUES
(7934, 'MILLER', 'CLERK', 7782,
TO_DATE('23-JAN-1982', 'DD-MON-YYYY'), 1300, NULL, 10);
CREATE TABLE DEPT
(DEPTNO NUMBER(2),
DNAME VARCHAR2(14),
LOC VARCHAR2(13) );
INSERT INTO DEPT VALUES (10, 'ACCOUNTING', 'NEW YORK');
INSERT INTO DEPT VALUES (20, 'RESEARCH', 'DALLAS');
INSERT INTO DEPT VALUES (30, 'SALES', 'CHICAGO');
INSERT INTO DEPT VALUES (40, 'OPERATIONS', 'BOSTON');
CREATE TABLE SALGRADE
(GRADE NUMBER,
LOSAL NUMBER,
HISAL NUMBER);
INSERT INTO SALGRADE VALUES (1, 700, 1200);
INSERT INTO SALGRADE VALUES (2, 1201, 1400);
INSERT INTO SALGRADE VALUES (3, 1401, 2000);
INSERT INTO SALGRADE VALUES (4, 2001, 3000);
INSERT INTO SALGRADE VALUES (5, 3001, 9999);
COMMIT;
Tuesday, July 29, 2014
Oracle HR Schema EMP & DEPT Tables Script
Thursday, July 24, 2014
ODI Upgrading from 11g 11.1.1.7 To ODI 12c 12.1.3 Using the Upgrade Assistant
ODI Upgrading from 11g
11.1.1.7 To ODI 12c 12.1.3 Using the Upgrade Assistant
11G 11.1.1.7 Repository Version: 04.03.04.02
12c 12.1.3 Repository Version: 05.01.02.02
After upgrading from 11.1.1.7 to 12.1.3 your
Repository version will be 05.01.02.02.
Note:
All Yellow interfaces from 11g it will be converted into Reusable mapping
in 12C.
Goto=>ODI 12C MIDDLEWARE Home location
Example for Windows ODI 12c Path.
C:\oracle\Middleware\Oracle_Home\oracle_common\upgrade\bin
Launch ua.batch file for windows and ua.sh for UNIX or
LINUX
1)
Schema: This option only for
Repository Migration.
2)
Standalone System Components Configuration:
This option for WebLogic domain components up gradation like J2EE Agent &
ODI Console
Wednesday, July 23, 2014
ODI-26163: Access Denied
A connection to the repository could not be established because of insufficient user privilege.
Solution: Ensure the ODI user has sufficient privilege to connect to the specified repository.
ODI-26168: Client requires a repository with version 0 but the repository version found is 1
ODI-26168: Client requires a repository with version {0} but the repository version found is {1}
It is an issue with Repository Version miss-match between two work repositories.
Please check your Repository version.
It is an issue with Repository Version miss-match between two work repositories.
Please check your Repository version.
ODI-26170: JDBC url is mandatory.
ODI-26170: JDBC url is mandatory.
JDBC Url was missing in Topology=>Physical Data Server.
Please goto your Physical technologies=>Data Server=> JDBC Tab=> Provide JDBC User details like HOST : PORT NO : SID (Service Name)
JDBC Url was missing in Topology=>Physical Data Server.
Please goto your Physical technologies=>Data Server=> JDBC Tab=> Provide JDBC User details like HOST : PORT NO : SID (Service Name)
ODI-26174: Database connection is not available.
ODI-26174: Database connection is not available.
It is an issue with Source / Target Database was Down or Not available. Check your Database
Connection and TNS Details.
It is an issue with Source / Target Database was Down or Not available. Check your Database
Connection and TNS Details.
ODI-26177: ODI-26177: Unable to connect to the DBA user.
ODI-26177: ODI-26177: Unable to connect to the DBA user.
Check Your DBA Privileged user Credentials. It is common error for Invalid User name and Password.
Check Your DBA Privileged user Credentials. It is common error for Invalid User name and Password.
ODI-26179: ODI-26179: Invalid Date Format
ODI-26179: ODI-26179: Invalid Date Format
Invalid Date Format In Filter Condition or Mappings.
Solution:
Check your Filter/Mapping expression Datatype and if it is not DATE data type using convert function to convert DATE.
Invalid Date Format In Filter Condition or Mappings.
Solution:
Check your Filter/Mapping expression Datatype and if it is not DATE data type using convert function to convert DATE.
ODI-15068: Unknown flexfield code.
ODI-15068: Unknown flexfield code.
Solution:
Check your Flex Field Short Code in SECURITY where you have defined flexfileds.
We need to consider Flex field Code or ID (Internal ID).
Solution:
Check your Flex Field Short Code in SECURITY where you have defined flexfileds.
We need to consider Flex field Code or ID (Internal ID).
ODI Errors - ORA-02019 connection description for remote database not found
ORA-02019 connection description for remote database not found
You use a KM using non existing DBLinks. Check the KM options and pre-requisites.
Subscribe to:
Posts (Atom)












