There is a simple view SCOTT.DEPT_VIEW on the table SCOTT.DEPT.
This insert fails with an error:
SQL> insert into dept_view values('SUPPORT','OXFORD'); insert into dept_view values('SUPPORT','OXFORD')
*
ERROR at line 1:
ORA-01400: cannot insert NULL into ("SCOTT"."DEPT"."DEPTNO")
What might be the problem?
B is incorrect because constraints are enforced on detail tables, not on views. C and D are incorrect because the error message would be different.
What are distinguishing characteristics of a public synonym rather than a private synonym? (Choose two.)
Public synonyms are not schema objects and so can only be addressed directly. They can have the same names as schema objects.
Consider these three statements:
create synonym s1 for employees; create public synonym s1 for departments; select * from s1;
Which of the following statements is correct?
The order of priority is to search the schema namespace before the public namespace, so it will be the private synonym (to EMPLOYEES) that will be found.
A view and a synonym are created as follows:
create view dept_v as select * from dept; create synonym dept_s for dept_v; Subsequently the table DEPT is dropped.
What will happen if you query the synonym DEPT_S ? (Choose the best answer.)
The synonym will be fine, but the view will be invalid. Oracle will attempt to recompile the view, but this will fail.
A sequence is created as follows:
create sequence seq1 maxvalue 50;
If the current value is already 50, when you attempt to select SEQ1.NEXTVAL what will happen?
The default is NOCYCLE, and the sequence cannot advance further.
Currently there are no comments in this discussion, be the first to comment!