How to generate a DDL and a DML in Oracle SQL (Scriptable) - oracle
I want to generate a .DDL that contains all the 'CREATE TABLES' and a .DML that contains all the 'INSERT'
I tried to use the answers of this question but didn't get to modify them to get the DDL and the DML
The question you referenced lets you get the DDL, to get the DML its easiest to use a tool. SQLcl is free and lets you do it easily, eg
SQL> select * from scott.emp;
EMPNO ENAME JOB MGR HIREDATE SAL COMM DEPTNO
---------- ---------- --------- ---------- --------- ---------- ---------- ----------
7369 SMITH CLERK 7902 17/DEC/80 800 20
7499 ALLEN SALESMAN 7698 20/FEB/81 1600 300 30
7521 WARD SALESMAN 7698 22/FEB/81 1250 500 30
7566 JONES MANAGER 7839 02/APR/81 2975 20
...
14 rows selected.
SQL> select /*insert*/ * from scott.emp;
REM INSERTING into SCOTT.EMP
SET DEFINE OFF;
Insert into SCOTT.EMP (EMPNO,ENAME,JOB,MGR,HIREDATE,SAL,COMM,DEPTNO) values (7369,'SMITH','CLERK',7902,to_timestamp('17/DEC/80','DD/MON/RR HH12:MI:SSXFF AM'),800,null,20);
Insert into SCOTT.EMP (EMPNO,ENAME,JOB,MGR,HIREDATE,SAL,COMM,DEPTNO) values (7499,'ALLEN','SALESMAN',7698,to_timestamp('20/FEB/81','DD/MON/RR HH12:MI:SSXFF AM'),1600,300,30);
Insert into SCOTT.EMP (EMPNO,ENAME,JOB,MGR,HIREDATE,SAL,COMM,DEPTNO) values (7521,'WARD','SALESMAN',7698,to_timestamp('22/FEB/81','DD/MON/RR HH12:MI:SSXFF AM'),1250,500,30);
Insert into SCOTT.EMP (EMPNO,ENAME,JOB,MGR,HIREDATE,SAL,COMM,DEPTNO) values (7566,'JONES','MANAGER',7839,to_timestamp('02/APR/81','DD/MON/RR HH12:MI:SSXFF AM'),2975,null,20);
Insert into SCOTT.EMP (EMPNO,ENAME,JOB,MGR,HIREDATE,SAL,COMM,DEPTNO) values (7654,'MARTIN','SALESMAN',7698,to_timestamp('28/SEP/81','DD/MON/RR HH12:MI:SSXFF AM'),1250,1400,30);
Insert into SCOTT.EMP (EMPNO,ENAME,JOB,MGR,HIREDATE,SAL,COMM,DEPTNO) values (7698,'BLAKE','MANAGER',7839,to_timestamp('01/MAY/81','DD/MON/RR HH12:MI:SSXFF AM'),2850,null,30);
...
...
Download SQLcl from Oracle
https://www.oracle.com/au/tools/downloads/sqlcl-downloads.html
Getting the DDL is easier now, it's a built-in command for SQL Developer and SQLcl.
For EMPLOYEES table, bonus: grabbing dependent objects on the table.
cd c:\users\jdsmith\desktop
set feedback off
set ddl segment_attributes off
set ddl storage off
set ddl tablespace off
spool employees_so.sql
ddl employees
set sqlformat insert
select * from employees;
spool off
Run this via F5 in SQL Developer (desktop) or SQLcl (cli at shell).
Out pops this file -
CREATE TABLE "HR"."EMPLOYEES"
( "EMPLOYEE_ID" NUMBER(6,0),
"FIRST_NAME" VARCHAR2(20) COLLATE "USING_NLS_COMP",
"LAST_NAME" VARCHAR2(25) COLLATE "USING_NLS_COMP" CONSTRAINT "EMP_LAST_NAME_NN" NOT NULL ENABLE,
"EMAIL" VARCHAR2(25) COLLATE "USING_NLS_COMP" CONSTRAINT "EMP_EMAIL_NN" NOT NULL ENABLE,
"PHONE_NUMBER" VARCHAR2(20) COLLATE "USING_NLS_COMP",
"HIRE_DATE" DATE CONSTRAINT "EMP_HIRE_DATE_NN" NOT NULL ENABLE,
"JOB_ID" VARCHAR2(10) COLLATE "USING_NLS_COMP" CONSTRAINT "EMP_JOB_NN" NOT NULL ENABLE,
"SALARY" NUMBER(8,2),
"COMMISSION_PCT" NUMBER(2,2),
"MANAGER_ID" NUMBER(6,0),
"DEPARTMENT_ID" NUMBER(4,0),
CONSTRAINT "EMP_SALARY_MIN" CHECK (salary > 0) ENABLE,
CONSTRAINT "EMP_EMAIL_UK" UNIQUE ("EMAIL")
USING INDEX ENABLE,
CONSTRAINT "EMP_DEPT_FK" FOREIGN KEY ("DEPARTMENT_ID")
REFERENCES "HR"."DEPARTMENTS" ("DEPARTMENT_ID") ENABLE,
CONSTRAINT "EMP_JOB_FK" FOREIGN KEY ("JOB_ID")
REFERENCES "HR"."JOBS" ("JOB_ID") ENABLE,
CONSTRAINT "EMP_MANAGER_FK" FOREIGN KEY ("MANAGER_ID")
REFERENCES "HR"."EMPLOYEES" ("EMPLOYEE_ID") ENABLE
) DEFAULT COLLATION "USING_NLS_COMP" ;
CREATE UNIQUE INDEX "HR"."EMP_EMP_ID_PK" ON "HR"."EMPLOYEES" ("EMPLOYEE_ID")
;
ALTER TABLE "HR"."EMPLOYEES" ADD CONSTRAINT "EMP_EMP_ID_PK" PRIMARY KEY ("EMPLOYEE_ID")
USING INDEX "HR"."EMP_EMP_ID_PK" ENABLE;
COMMENT ON COLUMN "HR"."EMPLOYEES"."EMPLOYEE_ID" IS 'Primary key of employees table.';
COMMENT ON COLUMN "HR"."EMPLOYEES"."FIRST_NAME" IS 'First name of the employee. A not null column.';
COMMENT ON COLUMN "HR"."EMPLOYEES"."LAST_NAME" IS 'Last name of the employee. A not null column.';
COMMENT ON COLUMN "HR"."EMPLOYEES"."EMAIL" IS 'Email id of the employee';
COMMENT ON COLUMN "HR"."EMPLOYEES"."PHONE_NUMBER" IS 'Phone number of the employee; includes country code and area code';
COMMENT ON COLUMN "HR"."EMPLOYEES"."HIRE_DATE" IS 'Date when the employee started on this job. A not null column.';
COMMENT ON COLUMN "HR"."EMPLOYEES"."JOB_ID" IS 'Current job of the employee; foreign key to job_id column of the
jobs table. A not null column.';
COMMENT ON COLUMN "HR"."EMPLOYEES"."SALARY" IS 'Monthly salary of the employee. Must be greater
than zero (enforced by constraint emp_salary_min)';
COMMENT ON COLUMN "HR"."EMPLOYEES"."COMMISSION_PCT" IS 'Commission percentage of the employee; Only employees in sales
department elgible for commission percentage';
COMMENT ON COLUMN "HR"."EMPLOYEES"."MANAGER_ID" IS 'Manager id of the employee; has same domain as manager_id in
departments table. Foreign key to employee_id column of employees table.
(useful for reflexive joins and CONNECT BY query)';
COMMENT ON COLUMN "HR"."EMPLOYEES"."DEPARTMENT_ID" IS 'Department id where employee works; foreign key to department_id
column of the departments table';
COMMENT ON TABLE "HR"."EMPLOYEES" IS 'employees table. Contains 107 rows. References with departments,
jobs, job_history tables. Contains a self reference.';
CREATE INDEX "HR"."EMP_DEPARTMENT_IX" ON "HR"."EMPLOYEES" ("DEPARTMENT_ID")
;
CREATE INDEX "HR"."EMP_JOB_IX" ON "HR"."EMPLOYEES" ("JOB_ID")
;
CREATE INDEX "HR"."EMP_MANAGER_IX" ON "HR"."EMPLOYEES" ("MANAGER_ID")
;
CREATE INDEX "HR"."EMP_NAME_IX" ON "HR"."EMPLOYEES" ("LAST_NAME", "FIRST_NAME")
;
CREATE OR REPLACE EDITIONABLE TRIGGER "HRREST"."TRIG_FOREIGN_TABLE"
BEFORE INSERT ON HR.EMPLOYEES
REFERENCING OLD AS OLD NEW AS NEW
BEGIN
NULL;
END;
/
ALTER TRIGGER "HRREST"."TRIG_FOREIGN_TABLE" ENABLE;
CREATE OR REPLACE EDITIONABLE TRIGGER "HR"."SECURE_EMPLOYEES"
BEFORE INSERT OR UPDATE OR DELETE ON employees
BEGIN
secure_dml;
END secure_employees;
/
ALTER TRIGGER "HR"."SECURE_EMPLOYEES" DISABLE;
CREATE OR REPLACE EDITIONABLE TRIGGER "HR"."UPDATE_JOB_HISTORY"
AFTER UPDATE OF job_id, department_id ON employees
FOR EACH ROW
BEGIN
add_job_history(:old.employee_id, :old.hire_date, sysdate,
:old.job_id, :old.department_id);
END;
/
ALTER TRIGGER "HR"."UPDATE_JOB_HISTORY" ENABLE;
CREATE OR REPLACE EDITIONABLE TRIGGER "HR"."EMPLOYEES_EMPLOYEE_ID_TRG"
before insert on employees
for each row
begin
if :new.employee_id is null then
select employees_seq.nextval into :new.employee_id from sys.dual;
end if;
end;
/
ALTER TRIGGER "HR"."EMPLOYEES_EMPLOYEE_ID_TRG" ENABLE;
REM INSERTING into EMPLOYEES
SET DEFINE OFF;
Insert into EMPLOYEES (EMPLOYEE_ID,FIRST_NAME,LAST_NAME,EMAIL,PHONE_NUMBER,HIRE_DATE,JOB_ID,SALARY,COMMISSION_PCT,MANAGER_ID,DEPARTMENT_ID) values (100,'Steven','King','SKING','515.123.4567',to_date('18-06-1987 06:00:00','DD-MM-YYYY HH24:MI:SS'),'AD_PRES',240000,null,null,90);
Insert into EMPLOYEES (EMPLOYEE_ID,FIRST_NAME,LAST_NAME,EMAIL,PHONE_NUMBER,HIRE_DATE,JOB_ID,SALARY,COMMISSION_PCT,MANAGER_ID,DEPARTMENT_ID) values (101,'Neena','Kochhar','NKOCHHAR','515.123.4568',to_date('22-09-1989 06:00:00','DD-MM-YYYY HH24:MI:SS'),'AD_VP',17000,null,100,90);
Insert into EMPLOYEES (EMPLOYEE_ID,FIRST_NAME,LAST_NAME,EMAIL,PHONE_NUMBER,HIRE_DATE,JOB_ID,SALARY,COMMISSION_PCT,MANAGER_ID,DEPARTMENT_ID) values (102,'Lex','De Haan','LDEHAAN','515.123.4569',to_date('14-01-1993 06:00:00','DD-MM-YYYY HH24:MI:SS'),'AD_VP',17000,null,100,90);
Insert into EMPLOYEES (EMPLOYEE_ID,FIRST_NAME,LAST_NAME,EMAIL,PHONE_NUMBER,HIRE_DATE,JOB_ID,SALARY,COMMISSION_PCT,MANAGER_ID,DEPARTMENT_ID) values (103,'Alexander','Hunold','AHUNOLD','590.423.4567',to_date('03-01-1990 00:00:00','DD-MM-YYYY HH24:MI:SS'),'IT_PROG',9000,null,102,60);
Insert into EMPLOYEES (EMPLOYEE_ID,FIRST_NAME,LAST_NAME,EMAIL,PHONE_NUMBER,HIRE_DATE,JOB_ID,SALARY,COMMISSION_PCT,MANAGER_ID,DEPARTMENT_ID) values (104,'Bruce','Ernst','BERNST','590.423.4568',to_date('20-05-1991 00:00:00','DD-MM-YYYY HH24:MI:SS'),'IT_PROG',6000,null,103,60);
Insert into EMPLOYEES (EMPLOYEE_ID,FIRST_NAME,LAST_NAME,EMAIL,PHONE_NUMBER,HIRE_DATE,JOB_ID,SALARY,COMMISSION_PCT,MANAGER_ID,DEPARTMENT_ID) values (105,'David','Austin','DAUSTIN','590.423.4569',to_date('25-06-1997 00:00:00','DD-MM-YYYY HH24:MI:SS'),'IT_PROG',4800,null,103,60);
Insert into EMPLOYEES (EMPLOYEE_ID,FIRST_NAME,LAST_NAME,EMAIL,PHONE_NUMBER,HIRE_DATE,JOB_ID,SALARY,COMMISSION_PCT,MANAGER_ID,DEPARTMENT_ID) values (106,'Valli','Pataballa','VPATABAL','590.423.4560',to_date('05-02-1998 00:00:00','DD-MM-YYYY HH24:MI:SS'),'IT_PROG',4800,null,103,60);
Insert into EMPLOYEES (EMPLOYEE_ID,FIRST_NAME,LAST_NAME,EMAIL,PHONE_NUMBER,HIRE_DATE,JOB_ID,SALARY,COMMISSION_PCT,MANAGER_ID,DEPARTMENT_ID) values (107,'Diana','Lorentz','DLORENTZ','590.423.5567',to_date('07-02-1999 00:00:00','DD-MM-YYYY HH24:MI:SS'),'IT_PROG',4200,null,103,60);
...
To adapt #ThatJeffSmith's answer
If you have three tables: employees, departments, jobs then you can use:
cd c:\users\jdsmith\desktop
set feedback off
set ddl segment_attributes off
set ddl storage off
set ddl tablespace off
spool myschema.ddl
ddl employees
ddl departments
ddl jobs
spool off
spool myschema.dml
set sqlformat insert
select * from employees;
select * from departments;
select * from jobs;
spool off
Related
SQL: ORA-02291: integrity constraint violated - parent key not found
I am creating this code SQL code and I keep getting the same error from every line of the insert statements after the errors begin here statement. the error is, ORA-02291: integrity constraint violated - parent key not found. I think it has something to do with the employee section constraint EMPSUPERVRFK but, that is the only constraint that the error message would lead to. -- keep these two commands at the top of every sql file set echo on set linesize 120 delete from Employee; commit; -- insert only managers first with their dno is null INSERT INTO Employee VALUES ('James','E','Borg',888665555,'10-NOV-1937','450 Stone, Houston, TX','M',55000,null,null); INSERT INTO Employee VALUES ('Franklin','T','Wong',333445555, to_date('1955-12-08', 'YYYY-MM-DD'), '638 Voss, Houston, TX','M',40000,888665555,null); INSERT INTO Employee VALUES ('Jennifer','J','Zelaya',987654321,'20-JUN-1941','291 Berry, Bellaire, TX','F',43000,888665555,null); delete from Department; commit; insert into Department values ('Research',5,333445555,'22-MAY-1988'); insert into Department values ('Headquarters',1,888665555,'19-JUN-1981'); insert into Department values ('Administration',1,888665555,'01-JAN-1995'); -- now, update employee.dno for managers UPDATE Employee SET dno = 1 WHERE ssn = 888665555; UPDATE Employee SET dno = 5 WHERE ssn = 333445555; -- need to update the rest of managers -- insert the rest of non-manager employees, supervisors first --errors begin here delete from Employee; commit; INSERT INTO Employee VALUES ('John','B','Smith',123456789,'09-JAN-1965','731 Fondren, Houston, TX','M',30000,333445555,5); insert into Employee values ('Alica','J','Zelya',999887777,'19-JAN-1968','3321 Castle, Spring, TX','F',25000,987654321,4); insert into Employee values ('Ramesh','K','Narayan',666884444,'15-SEP-1962', '975 Fire Oak, Humnle, TX','M',38000,333445555,5); insert into Employee values ('Joyce','A','English',453453453,'31-JUL-1972','5631 Rice, Houston, TX','F',25000,333445555,5); insert into Employee values ('Ahmad','V','Jabbar',987987987,'29-MAR-1969','980 Dallas, Houston, TC','M',25000,987654321,4); --Project delete from PROJECT; commit; insert into PROJECT values ('ProductY',2,'Sugarland',5); insert into PROJECT values ('ProductZ',3,'Houston',5); insert into PROJECT values ('Computerication',10,'Stafford',4); insert into PROJECT values ('Reorganization',20,'Houston',1); insert into PROJECT values ('Newbenefits',30,'Stafford',4); --dept_Locations delete from DEPT_LOCATIONS; commit; insert into DEPT_LOCATIONS values (1, 'Houston'); insert into DEPT_LOCATIONS values (4,'Stafford'); insert into DEPT_LOCATIONS values (5,'Bellaire'); insert into DEPT_LOCATIONS values (5,'Sugarland'); insert into DEPT_LOCATIONS values (5,'Houston'); --works_on 16 delete from WORKS_ON; commit; insert into WORKS_ON values (123456789,1,32.5); insert into WORKS_ON values (123456789,2,7.5); insert into WORKS_ON values (666884444,3,40.0); insert into WORKS_ON values (453453453,1,20.0); insert into WORKS_ON values (453453453,2,20.0); insert into WORKS_ON values (333445555,2,10.0); insert into WORKS_ON values (333445555,3,10.0); insert into WORKS_ON values (333445555,10,10.0); insert into WORKS_ON values (333445555,20,10.0); insert into WORKS_ON values (999887777,30,30.0); insert into WORKS_ON values (999887777,10,10.0); insert into WORKS_ON values (987987987,10,35.0); insert into WORKS_ON values (987987987,30,5.0); insert into WORKS_ON values (987654321,30,20.0); insert into WORKS_ON values (987654321,20,15.0); insert into WORKS_ON values (888665555,20,null); --dependent 7 delete from DEPENDENT; commit; insert into DEPENDENT values (333445555,'Alice','F','05-APR-1986','Daughter'); insert into DEPENDENT values (333445555,'Theodore','M','25-OCT-1983','Son'); insert into DEPENDENT values (333445555,'Joy','F', '03-MAY-1958','Spouse'); insert into DEPENDENT values (987654321,'Abner','M', '28-FEB-1942','Spouse'); insert into DEPENDENT values (123456789,'Michael','M','04-JAN-1988','Son'); insert into DEPENDENT values (123456789,'Alice','F','30-DEC-1988','Daughter'); insert into DEPENDENT values (123456789,'Elizabeth','F', '05-MAY-1967','Spouse'); ----------------------------------------------------------------------------------- set echo on set linesize 120 drop table Employee cascade constraints; commit; create table Employee ( fname varchar2(15), minit varchar2(1), -- can be char lname varchar2(15), ssn number, bdate date, address varchar2(50), sex varchar2(1) CHECK(Sex = 'M' or Sex = 'F'), salary number CHECK(20000 <= salary AND 100000 >= salary), superssn number, dno number DEFAULT 0, constraint EMPPK primary key(ssn), constraint EMPSUPERVRFK foreign key(superssn) references Employee(ssn) ON DELETE SET NULL ); drop table Department cascade constraints; commit; create table Department ( dname varchar2(15),-- NOT NULL, dnumber number, mgrssn number, mgrstartdate date, constraint DEPTPK primary key(dnumber), constraint DEPTMGRFK foreign key(mgrssn) references Employee(ssn) ON DELETE SET NULL ); alter table Employee add constraint EMPDEPTFK foreign key(dno) references Department(dnumber) ON DELETE SET NULL; drop table DEPT_LOCATIONS; create table DEPT_LOCATIONS ( Dnumber number, Dlocation varchar2(15), constraint PK_DnoDloc primary key(Dnumber,Dlocation) ); COMMIT; drop table PROJECT; create table PROJECT ( Pname varchar2(15), Ponumber number primary key, Plocation varchar2 (15), Dnum number, foreign key (Dnum) references Department(dnumber) ); Commit; drop table DEPENDENT; create table DEPENDENT ( Essn number, Dependent_name varchar2(15), Sex Char, Bdate Date, Relationship varchar2(15), foreign key(Essn) references Employee(ssn) -- ON DELETE SET NULL, constraint PK_essn primary key(Essn,Dependent_name) ); COMMIT; drop table WORKS_ON; create table WORKS_ON ( Essn number, Pno number, Hours number, foreign key(Essn) references Employee(ssn)-- ON DELETE SET NULL, foreign key(Pno) references PROJECT(Ponumber) ON DELETE SET NULL, constraint PK_SSN primary key(Essn, Pno) ); commit; ---------------------------------------------------------------- -- keep these two commands at the top of every sql file set echo on set linesize 120 -- test queries, not to be submitted select count(*) from employee; select count(*) as DEPT_COUNT from department; -- comment out the above queries for your homework -- a the first name, last name of employees who work in department 5. select fname, lname from employee where dno = 5; -- b the first name, last name of every employee and name of his/her department select E.fname as FIRST_NAME, E.lname LAST_NAME, D.dname DEPARTMENT_NAME from employee E, department D where E.dno = D.dnumber; --c The first name, last name of employees who works at the 'Research' department select e.fname , e.lname , Dname from employee e inner join department d on e.dno=d.dname where d.name ='Research'; --d. The first name, last name of employee who is the manager of the 'Research' department select e.fname , e.lname , Dname from employee e inner join department d on e.dno=d.dname where d.name ='Research' and e.super_ssn=d.mgr_ssn; --e. The first name, last name of employees who works on the 'Computerization' project. select e.fname,e.lname from employee e inner join department d on e.dno=d.dnumber inner join project p on d.dnumber=p.dnum where p.pname="Computerization";
this happens because you are inserting values to table that depends on other table that is still empty, you should insert on that table first before this one for example, suppose you have employee table, and department table, in which every employee must be assigned to a department, so when you input employee Bob to department IT, it would result in error, since there is no IT yet in department table. so you need to input IT on department table, then you can input Bob to employee table or, you can disable integrity check when importing sql, but this setting is different for each DB engine, so I can't give you an example
Number data type column is not behaving as number
I have a table in oracle which has column recid which is of number Datar type. The table is partition table and it has partition index on it. When I query the partition like select * from table partition (abc) I am able to see value for rec id =50. But when I query select * from table partition(abc) where rec id =50, It doesn’t give any record . If I do type casting as select * from table partition(abc) where cast (recid as number ) =50 I am getting records. Please let me know what might be the issue .? The issue exist only for one partition and rest of the partition working normal.
If it's not behaving as a number, then it's not stored as a number. Run a DESCRIBE (DESC) on your table in either SQL Developer, SQLcl, or SQL*Plus. It will show how the REC_ID column is defined. If it's stored as a VARCHAR2, you wil get an error on your WHERE CLAUSE predicate for REC_ID, if not every REC_ID could be treated as also a number: ORA-01722: invalid number Like so: SQL> DESC employees Name Null? Type EMPLOYEE_ID NOT NULL NUMBER(6) FIRST_NAME VARCHAR2(20) LAST_NAME NOT NULL VARCHAR2(25) EMAIL NOT NULL VARCHAR2(25) PHONE_NUMBER VARCHAR2(20) HIRE_DATE NOT NULL DATE JOB_ID NOT NULL VARCHAR2(10) SALARY NUMBER(8,2) COMMISSION_PCT NUMBER(2,2) MANAGER_ID NUMBER(6) DEPARTMENT_ID NUMBER(4) SQL> SQL> SELECT * FROM employees WHERE first_name = 50; Error starting at line : 4 in command - SELECT * FROM employees WHERE first_name = 50 Error report - ORA-01722: invalid number SQL> select * from emps_copy_num where first_name = 50; EMPLOYEE_ID FIRST_NAME LAST_NAME EMAIL PHONE_NUMBER HIRE_DATE JOB_ID SALARY COMMISSION_PCT MANAGER_ID DEPARTMENT_ID 100 50 King SKING 515.123.4567 17-JUN-87 AD_PRES 24000 90 The first query fails - because not every value in that column can be simplicity cast as a number by the database. The second query works, because I created a copy of the table where all of the first_name strings were values that COULD be cast as a number.
You probably have spaces in there somewhere, eg SQL> create table t ( should_have_been_numeric varchar2(30)); Table created. SQL> SQL> insert into t values ('50 '); 1 row created. SQL> insert into t values (' 50 '); 1 row created. SQL> insert into t values (' 50'); 1 row created. SQL> SQL> select * from t where should_have_been_numeric = '50'; no rows selected SQL> select * from t where cast(should_have_been_numeric as number) = 50; SHOULD_HAVE_BEEN_NUMERIC ------------------------------ 50 50 50 3 rows selected. but as already mentioned, if you are treating strings as numbers, then there is problems ahead in terms of spurious errors, not to mention potential performance issues because the optimizer also doesn't know that these are really numbers.
How to delete the primary key from without using constraint name
CREATE TABLE Persons ( ID int PRIMARY KEY, LastName varchar(255) NOT NULL, FirstName varchar(255), Age int ); How to remove the primary key as there is no constraint defined?
"How to remove PK as there is no constraint defined?" Actually it's every bit as simple as you might hope: SQL> create table t23 (id number primary key); Table created. SQL> select constraint_name, constraint_type 2 from user_constraints 3 where table_name = 'T23' 4 / CONSTRAINT_NAME C ------------------------------ - SYS_C0034419 P SQL> alter table t23 drop primary key; Table altered. SQL> select constraint_name, constraint_type 2 from user_constraints 3 where table_name = 'T23' 4 / no rows selected SQL>
run this to get constraint name : SELECT * FROM user_cons_columns WHERE table_name = Persons; then run ALTER TABLE Persons DROP CONSTRAINT <pk constraint>;
Don't think you can do it in 1 SQL command,without knowing the constraint name, but you can know the constraint name as in this case it would be defined by system. Something which starts with SYS..... Alternatively you can use a PLSQL block to achieve the same. See the example below for your case. CREATE TABLE Persons ( ID int PRIMARY KEY, LastName varchar(255) NOT NULL, FirstName varchar(255), Age int ); Find constraint name select CONSTRAINT_NAME From USER_CONSTRAINTS where table_name='PERSONS' AND CONSTRAINT_TYPE='P'; OUTPUT:= SYS_C0012152 Drop Constraint ALTER TABLE PERSONS DROP CONSTRAINT SYS_C0012152; Note: The constraint name SYS_C0012152 is not enclosed in single quotes. PLSQL Block to do the same declare sql_stmt varchar2(255); cons_name varchar2(30); begin select CONSTRAINT_NAME into cons_name From USER_CONSTRAINTS where table_name='PERSONS' AND CONSTRAINT_TYPE='P'; sql_stmt:=' ALTER TABLE PERSONS DROP CONSTRAINT '||cons_name; dbms_output.put_line(sql_stmt); execute immediate sql_stmt; end;
parent keys not found Oracle 10g
I have two tables : SQL> desc SEGMENT Name Null? Type ----------------------------------------- -------- ---------------------------- INDIP NOT NULL VARCHAR2(11) NOMSEGMENT NOT NULL VARCHAR2(20) ETAGE SQL> desc POSTE Name Null? Type ----------------------------------------- -------- ---------------------------- NPOSTE NOT NULL VARCHAR2(7) NOMPOSTE NOT NULL VARCHAR2(20) INDIP VARCHAR2(11) AD VARCHAR2(3) TYPEPOSTE VARCHAR2(9) NSALLE VARCHAR2(7) I want to add a constraint as the following : ALTER TABLE "POSTE" ADD CONSTRAINT "FK_POSTE_SEGMENT" FOREIGN KEY ("INDIP") REFERENCES "SEGMENT" ("INDIP") ENABLE; But I got this error message : ERROR at line 1: ORA-02298: cannot validate (AIMAD.FK_POSTE_SEGMENT) - parent keys not found How can I solve this
You should check what POSTE table does not contain values in INDIP column what don't exist in INDIP column of SEGMENT table. Like SQL> create table t (x int primary key); SQL> insert into t values(1); SQL> create table t_c (x int); SQL> insert into t_c values(1); SQL> insert into t_c values(2); SQL> commit; SQL> alter table t_c add constraint t_c_x foreign key(x) 2 references t(x); alter table t_c add constraint t_c_x foreign key(x) * ORA-02298: cannot validate (SCOTT.T_C_X) - parent key not found SQL> select * from t_c where not exists (select * 2 from t where t.x = t_c.x); X ----------------------- 2 Also Oracle provides the ability to create constraint in NOVALIDATE status, this prevents Oracle from checking data during contraint creation: SQL> alter table t_c add constraint t_c_x foreign key(x) 2 references t(x) enable novalidate; Table altered. but this can have undesirable side effects because data in both tables are not consistent.
Oracle Forced dropping of Foreign Key during purge on Interval Partitioned Tables
We have several tables which are interval partitioned by day. While working on a purge job to drop a day of partitioning, our DBA has informed us that we will have to drop all foreign keys to any table, before performing the purge. This seems like an unnecessary step, and thus, I am turning to the wisdom of stackoverflow. parentTable childTable ID (PK) ID (PK)(FK) date (PK) date (PK)(FK) otherKey(PK) parentTable childTable ID date ID date otherKey 1 10/23 1 10/23 a 2 10/23 2 10/23 a 3 10/23 3 10/23 a 1 10/24 1 10/24 a 2 10/24 2 10/24 a 2 10/24 b The question is, if we were to drop the 10/23 partition from childTable (first), then parentTable, would we have to drop/disable the Foreign Key constraint before the purge, and create it again afterwards? Is there a data situation where this would have to occur (maybe not as shown in my example above).
Seems that the DBA was right, test case scenario: CREATE TABLE parent_tab ( id NUMBER PRIMARY KEY, start_date DATE ) PARTITION BY RANGE (start_date) INTERVAL(NUMTODSINTERVAL(1, 'DAY')) ( PARTITION pos_data_p2 VALUES LESS THAN (TO_DATE('01-01-2013', 'DD-MM-YYYY')) ); INSERT INTO parent_tab VALUES (1, DATE '2012-01-01'); INSERT INTO parent_tab VALUES (2, DATE '2013-01-02'); INSERT INTO parent_tab VALUES (3, DATE '2013-01-03'); CREATE TABLE child_tab ( start_date DATE, parent_tab_id NUMBER REFERENCES parent_tab(id) ) PARTITION BY RANGE (start_date) INTERVAL(NUMTODSINTERVAL(1, 'DAY')) ( PARTITION pos_data_p2 VALUES LESS THAN (TO_DATE('01-01-2013', 'DD-MM-YYYY')) ); INSERT INTO child_tab VALUES (DATE '2012-01-01', 1); INSERT INTO child_tab VALUES (DATE '2013-01-02', 2); INSERT INTO child_tab VALUES (DATE '2013-01-03', 3); COMMIT; SELECT table_name, partition_name FROM user_tab_partitions WHERE table_name IN ('PARENT_TAB', 'CHILD_TAB'); TABLE_NAME PARTITION_NAME ------------------------------ ------------------------------ CHILD_TAB POS_DATA_P2 CHILD_TAB SYS_P69 CHILD_TAB SYS_P70 PARENT_TAB POS_DATA_P2 PARENT_TAB SYS_P67 PARENT_TAB SYS_P68 ALTER TABLE child_tab DROP PARTITION SYS_P69; > table CHILD_TAB altered. ALTER TABLE parent_tab DROP PARTITION SYS_P67; ALTER TABLE parent_tab DROP PARTITION SYS_P67 Error report: SQL Error: ORA-02266 - "unique/primary keys in table referenced by enabled foreign keys" *Cause: An attempt was made to truncate a table with unique or primary keys referenced by foreign keys enabled in another table. Other operations not allowed are dropping/truncating a partition of a partitioned table or an ALTER TABLE EXCHANGE PARTITION. *Action: Before performing the above operations the table, disable the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command: SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam"; Edit As the author pointed out, disabling the constraint works: SELECT table_name, constraint_name, constraint_type FROM user_constraints WHERE table_name = 'CHILD_TAB'; TABLE_NAME CONSTRAINT_NAME CONSTRAINT_TYPE ------------------------------ ------------------------------ --------------- CHILD_TAB SYS_C0033723 R ALTER TABLE child_tab DISABLE CONSTRAINT SYS_C0033723; ALTER TABLE parent_tab DROP PARTITION SYS_P67; > table PARENT_TAB altered. ALTER TABLE child_tab ENABLE CONSTRAINT SYS_C0033723;
Some day i will learn to manage there my code, So.. CREATE OR REPLACE PROCEDURE manage_constraints (i_status IN varchar2) IS CURSOR ref_cons IS SELECT constraint_name, table_name, status FROM user_constraints WHERE constraint_type in ( 'R') ; -- YOu can disable more constraints type v_status VARCHAR2 (10); v_sql VARCHAR2 (300); BEGIN FOR e_cons IN ref_cons LOOP v_sql := 'ALTER TABLE ' || e_cons.table_name || ' ' || i_status || ' CONSTRAINT ' || e_cons.constraint_name; --DBMS_OUTPUT.put_line (v_sql); EXECUTE IMMEDIATE v_sql; END LOOP; EXCEPTION WHEN OTHERS THEN RAISE; END; --exec manage_constraints('DISABLE'); --exec manage_constraints('ENABLE'); There you can just DISABLE all you constraints and later ENABLE them. select * from user_constraints check constraint types... hope this helps.
Not a direct answer, but it sounds like what you really want here is reference partitioning, which would: cascade partition maintenance operations Allow more simple queries Provide metadata that the two tables' partitions are logically associated Possibly add a small overhead on the inserts into the child tables. http://docs.oracle.com/cd/B28359_01/server.111/b32024/partition.htm#CACIHDII