In which situation would you use static database registration for a listener?
A.
When multiple databases are to be registered with the listener
B.
When DBAs need to connect remotely to start up the database instance
C.
When users need to connect the database instance using the host naming method
D.
When the database instance that is to be registered with the listener is configured in shared
server mode
Static registration: hardcoding a list of instances in the listener.ora file
Dynamic Registration: During instance startup, available listener will be located and registring
with it.
Listeners listen for incoming request in the database. If we want that the listener listen for our database then we have to register our database service to listener either statically or dynamically. When database instance starts up then PMON process tries to register with the default listener of the server which is listening in the port number 1521. If we want to start our database remotely, we need to have statically registered connect string. Since the database is down which we want to start remotely, it wouldn’t be registered dynamically. Dynamic registration saves lots of effort, whereas static registration takes lots of efforts as things change over time.
Static registration: In newer versions, you can choose to use static registration if:
– Where the listener port than the default port 1521, you do not want the instance is configured to use a non-default port register
– The application requires a static DB register
– In the state of the database is not open, you can connect remotely to a database, and perform operations on the DB