Why does the startup command return the error shown?

You issue commands in SQL*Plus as the Oracle owner, to enable multithreading for your
UNIX-based Oracle 12c database: Exhibit: Why does the startup command return the error
shown?

You issue commands in SQL*Plus as the Oracle owner, to enable multithreading for your
UNIX-based Oracle 12c database: Exhibit: Why does the startup command return the error
shown?

A.
because the threaded architecture requires connecting to the instance via a listener
before issuing a startup command

B.
because the threaded architecture requires restarting the listener before issuing a startup
command

C.
because the threaded architecture requires issuing a new connect / as sysdba from
within sql*pIus before issuing a startup command

D.
because the threaded architecture requires exiting from sql*pIus and reconnecting with
sql*PIus / as sysdba before issuing a startup command

E.
because the threaded architecture requires authentication using a password file before
issuing a startup command



Leave a Reply 5

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


yogui

yogui

A – Before startup first add DEDICATED_THROUGH_BROKER_LISTENER=ON to the listener.ora and reload the listener, than proceed with the restart of the oracle database. Connect as user sys/ and everthing runs fine.
When using THREADED_EXECUTION=TRUE, which enables the multithreaded Oracle model, operating system authentication is not supported. Attemp to connect (CONNECT / AS SYSDBA or CONNECT / ) give ORA-01031 “insufficient privileges” error. The sollution for this is DEDICATED_THROUGH_BROKER_=ON parameter in the listener.ora file. This enables the server to spawn threads when connections to the database are requested through the listener.