1Z0-062 · Question #236
Examine the parameter settings in your local ORCL database: Examine the parameter settings for the remote SALES database: As the SYS user, you issue the following command on ORCL: CREATE PUBLIC…
The correct answer is A. The GLOBAL_NAMES initialization parameter should be set to FALSE in the ORCL database. C. Local database users who use this database link should have accounts and the required. To successfully use a public database link named differently from the remote database's global name, the local database's GLOBAL_NAMES parameter must be FALSE, and local users must have accounts and privileges on the remote database.
Question
Examine the parameter settings in your local ORCL database:
Examine the parameter settings for the remote SALES database:
As the SYS user, you issue the following command on ORCL:
CREATE PUBLIC DATABASE LINK sales.us.example.com USING `sales1'; The sales1 tnsnames entry points to the salesdatabase instance. Which two are requirements to ensure that you can successfully connect by using this database link?
Options
- AThe GLOBAL_NAMES initialization parameter should be set to FALSE in the ORCL database.
- BThe SALES1 net service name should beknown to both the local and remote databases.
- CLocal database users who use this database link should have accounts and the required
- DThe REMOTE_OS_AUTHENT initialization parameter should be set to FALSE in the
- EOnly the user creating the database link must have an account and the required privileges in the
How the community answered
(17 responses)- A76% (13)
- B6% (1)
- D6% (1)
- E12% (2)
Why each option
To successfully use a public database link named differently from the remote database's global name, the local database's GLOBAL_NAMES parameter must be FALSE, and local users must have accounts and privileges on the remote database.
If the GLOBAL_NAMES initialization parameter is set to TRUE in the local database, the database link name must match the global name of the remote database. Since the link name sales.us.example.com does not match the global name of the remote database SALES, setting GLOBAL_NAMES to FALSE in ORCL is required to bypass this check.
The SALES1 net service name is only required on the local database (ORCL) to resolve the connection string for the remote database; the remote database itself does not need to know about this local TNS entry.
Any user attempting to use the database link to access objects in the remote database must have a valid account and appropriate privileges (e.g., SELECT, INSERT) on the remote database to perform desired operations.
The REMOTE_OS_AUTHENT parameter relates to operating system authentication for remote connections and is not a general requirement for basic database link functionality, which typically uses database usernames and passwords.
For a PUBLIC database link, any local user who uses the link needs an account and privileges on the remote database to access objects, not just the user who created the link.
Concept tested: Oracle database link configuration
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/managing-database-links.html#GUID-0D120B41-C68C-4C21-93C0-D6B60053C277
Topics
Community Discussion
No community discussion yet for this question.