ADE are correct:
A - TRUE; cash values are lost if instance shuts down
B - FALSE; Transaction can be rolled back if not COMMITed yet, but sequence number was already used and cannot be reused
C - FALSE; user can create sequence and therefore has all privileges to this object, including DROP
D - TRUE; CYCLE parameter can be set and values can be looped
E - TRUE; there is a list of activities that can influence the gaps generation, like failed INSERT or DELETE; COMMIT or INSERT; ROLLBACK etc.
F - FALSE; from ORACLE documentation "Sequence numbers are generated independently of tables, so the same sequence can be used for one or for multiple tables"
The whole idea of SEQUANCE is to provide unique keys so D cannot be correct.
About F - why not?! This is something called in the code. But even as default value, there is no check for unique value accross all tables into the database.
Apparently there are edge cases after using a rollback or incorrect usage of the sequence that can cause this. also the cycle setting will reuse sequence numbers, even though mose sequences are so large you most likely won't run into any problems. but most likely isn't a definitive no. It feel wrong, but if there is even a single edge case that can issue a duplicate, you should answer these questions as it being a possibility.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
yaya32
6 months, 2 weeks agoWingL
1 year agoESZ
1 year, 4 months agoDarnun
1 year, 4 months agoMorticiaAAddams
1 year, 6 months agomavista
1 year, 1 month agoRik92
1 year, 4 months agodexdinh91
1 year, 6 months agoViviana3184
1 year, 7 months agoleongkaon
1 year, 7 months ago