can i get answer for this
which three statements are true about dependent objects
1.invalid objects cannot be described
2.the oracle server automatically records dependencies among objects
3. all schema objects have status that is recorded in the data dictionary
4.you can view whether an object is valid or invalid in the user_objects data dictionay view
Re: can i get answer for this
1.invalid objects cannot be described
3. all schema objects have status that is recorded in the data dictionary
4.you can view whether an object is valid or invalid in the user_objects data dictionay view
these are true.
Re: can i get answer for this
that means oracle server automatically cannot records dependencies among objects.is it so?
Re: can i get answer for this
yeah.. it can not do automatically. we have to create foreign keys to make it record dependencies among objects.( for tables)
Re: can i get answer for this
Re: can i get answer for this
Invalid objects can not be described.
Go and try the query [B]desc object[/B] to any object that is invalid.
It will throws an error like:
SQL> desc TES
ERROR:
ORA-24372: invalid object for describe
Re: can i get answer for this
I think all the four are right and I am 100% sure that options 1 and 4 are correct
Re: can i get answer for this
Hi,
[B]1, 2 & 4 are the right answers.[/B]
[B]1. [/B]Invalid Objects cannot be described, if you try to describe an invalid object using, DESC command, you will get an error, [B]"ORA-24372: invalid object for describe"[/B]
[B]2. [/B]Oracle automatically records dependencies among objects to [B]reduce the complexity of dependency management.[/B]
For example, if you alter a table on which several stored procedures depend, Oracle automatically recompiles the dependent procedures the next time when the procedures are referenced.
[B]4.[/B]You can view whether an object is valid or invalid in the user_objects data dictionay view using the [B]"STATUS" column of USER_OBJECTS view.[/B]
*** Innila ***
Re: can i get answer for this
Innila,
Could you explain why option 3 is not correct?
I am asking this simply because of curiosity...
Re: can i get answer for this
Its having status field for all objects.
3 is right.
but i am wrong telling 2 is false. sorry!:o
Re: can i get answer for this
hi
here the question is about dependent objects
For dependent objects,lets say program unit A (current schema)references Program unit B(remote side located). this means A is dependent on B. so in the current schema both the A and B status will be available?
if so,according to my guess then option 3 must be one of correct answer
if status of B (becoz located remoteside) is not available in current shema then option 1,2,4 will be correct answers
can you clear me this
thanks
gujjar
Re: can i get answer for this
[QUOTE]
Innila,
Could you explain why option 3 is not correct?
I am asking this simply because of curiosity...
[/QUOTE]
Hi,
I am very sure about the dependency management (Option 2) rather than Object status.
Everybody are considering just the status column of user_objects view, but the option (3. all schema objects have status that is recorded in the data dictionar) is not about the "STATUS" column of "USER_OBJECTS" view.
The "STATUS" column of "USER_OBJECTS" consists of only the validity of the object (whether "valid" or "invalid") and [B]does not consists of the cause or the reason why it has become "invalid". [/B]
The invalid status does'nt inform us whether it has been altered or deleted or any other reason.
So i think the actual status is not stored in the data dictionary.
*** Innila ***
Re: can i get answer for this
Hellllllllllll0
again.
If 4 is correct then 3 must be correct and if 3 is correct then which data dictionary?
Bcos USER_OBJECTS is data dictionary maintained by oracle itself always...
so 2 is correct.
As per my friend who think that invalid objects cant describe...
I have doubt..
I did r&d and observe that some views can invalid status still can be described without any error..
If u observe any package body having invalid status can be described because it will describe package specification (he i dont try with different name of package body and pack specification )
but I am sure what I said about view.
Again one additional point is there not "invalid object to desc" always with desc invalid object sometime err msg will "object not exist"