Which two predefined service names can you use when connecting to an OCI autonomous data warehouse?

Seleccionar un idiomaInglés (English)

Hi, my name is Angela Wall. Welcome to Oracle University's training on Oracle Autonomous Database, Connect to Autonomous Database. First, let us walk through the predefined database service names. First, there's tpurgent. This is for ATP environments only. It is the highest priority application connection service for time-critical transaction processing operations. This connection service supports manual parallelism. Tp, again, this is for ATP environments only. A typical application connection service for transaction processing operations. This connection service does not run with parallelism. Next, there's high. A high priority application connection service for reporting and batch operations. All operations run in parallel and are subject to queuing. Medium, a typical application connection service for reporting and batch operations. All operations run in parallel and are subject to queuing. Using this service, the degree of parallelism is limited to four. Lastly, there's low. A lowest priority application connection service for reporting or batch processing operations. This connection service does not run with parallelism. The tnsname.ora file provided with the credential zip file contains five database service names. Sessions in these services may get disconnected if they stay idle for more than five minutes, and other user sessions require the resources consumed by the idle session. This allows resources to be freed for other active users in your database. Predefined services minimize application impact. With 16 OCPUs, you would get the following number of concurrent queries before queuing would kick in. Three concurrent queries for high, 20 concurrent queries for medium, 32 concurrent queries for low. Maintenance proactively drain services during maintenance. Tp services have a five-minute drain. Batch has a one-hour drain. Applications connect to a predefined database service to control relative priority, SQL parallelism, max concurrently executing users. For example, most OLTP applications connect to tp service and most batch to a low service. If we look inside the wallet, there are two types of wallets. For autonomous database shared, there's what's called an instance wallet. The instance wallet contains only the credentials and keys for the individual autonomous database being provisioned. The regional wallet on the other hand, contains the credentials and keys for all of the autonomous databases in a specified region. Regional wallets should only be used by database administrators. When you look at entry such as the tnsnames file, you'll see that entries for all the databases that have been provisioned. In the case of the autonomous database dedicated, the wallet file only contains the credentials and keys for a single autonomous database, there is no regional file. You can connect to Oracle Autonomous Databases through SQL*Net, JDBC, or ODBC processes. JDBC thin connections use 12.1 and 12.2 JDBC thin drivers and Java KeyStore, which can be defined in the JKS connection properties. JDBC and ODBC use Oracle Client Interface calls or OCI and tools like SQL*Net and Data Pump use it to communicate with the database. All connections use SSL for encryption. No unsecure connections are allowed to the autonomous database. This is why clients require a security credentials wallet to connect. In the previous slides, we went over the steps for downloading the wallet to use for secure connections. However, in order to execute API keys, you will need to upload the public key. From the console, navigate to identity, select the users panel, and select add public key. There are two connectivity options to establish a connection to the autonomous database. One is through the public Internet directly, and the other is using Oracle's FastConnect service with public peering. The second option provides private connections from on-premise networks. To review the options to establish connectivity to an autonomous database. In this example, a connection is established through the public Internet between a customer's on-premise network and the Oracle Data Center through a public Internet connection using SSL encryption. To access the autonomous database from behind the firewall, the firewall must permit the use of the ports specified in the database connection when connecting to the servers in the connection. The default port number for Autonomous Data Warehouse is 1522. Autonomous database connectivity options using FastConnect with public peering. In this case, to establish connectivity to an autonomous database, a connection is established through the FastConnect with public peering service offered from Oracle Data Centers to a customer's on-premise network using SSL encryption. Autonomous database connectivity options. Oracle Cloud offers the Oracle Cloud Infrastructure Service Gateway Service, which offers private access to Oracle services deployed in the Oracle Services Network. This allows for additional levels of privacy and obfuscation for customers that require complete network isolation and private security. To wrap up, the Oracle Autonomous Database and our connectivity options eliminates the complexity of operating and securing high-performance databases. Thanks so much for watching.