What could be the reason for this?

View the Exhibit.

To perform some routine database administration tasks, you execute srvctl status db -d orcl -v to check if all your cluster database instances on the ORCL database are functional before you perform the tasks.

However, the output looks different than it used to be.

What could be the reason for this?

View the Exhibit.

To perform some routine database administration tasks, you execute srvctl status db -d orcl -v to check if all your cluster database instances on the ORCL database are functional before you perform the tasks.

However, the output looks different than it used to be.

What could be the reason for this?

A.
The extra output is generated because you enabled resource debugging within the OCR.

B.
The extra output is generated because you enabled debugging using the -d command-line flag.

C.
The extra output is generated because you requested a verbose output using the -v command-line flag.

D.
The extra output is generated because you set the DEBUG environment variable to TRUE before you executed the SRVCTL command.

E.
The extra output is generated because you enabled tracing for Java-based tools by setting the SRVM_TRACE environment variable to TRUE before you executed the SRVCTL command.



Leave a Reply 0

Your email address will not be published. Required fields are marked *