You are running a mission-critical database application in Oracle Cloud Infrastructure (OCI). You take regular backups of your DB system to OCI object storage. Recently, you notice a failed database backup status in the console. What step can you take to determine the cause of the backup failure?
Correct Answer: A
Database backups can fail for various reasons. Typically, a backup fails because either the database host cannot access the object store, or there are problems on the host or with the database configuration. First need to determining the Problem In the Console, a failed database backup either displays a status of Failed or hangs in the Backup in Progress or Creating state. If the error message does not contain enough information to point you to a solution, you can use the database CLI and log files to gather more data. Then, refer to the applicable section in this topic for a solution. Database Service Agent Issues Your Oracle Cloud Infrastructure Database makes use of an agent framework to allow you to manage your database through the cloud platform. Occasionally you might need to restart the dcsagent program if it has the status of stop/waiting to resolve a backup failure. Object Store Connectivity Issues Backing up your database to Oracle Cloud Infrastructure Object Storage requires that the host can connect to the applicable Swift endpoint. You can test this connectivity by using a Swift user. Host Issues One or more of the following conditions on the database host can cause backups to fail: - Interactive Commands in the Oracle Profile - The File System Is Full - Incorrect Version of the Oracle Database Cloud Backup Module - Changes to the Site Profile File (glogin.sql) Database Issues An improper database state or configuration can lead to failed backups. - Database Not Running During Backup - Archiving Mode Set to NOARCHIVELOG (When you provision a new database, the archiving mode is set to ARCHIVELOG by default. This is the required archiving mode for backup operations) - Stuck Database Archiver Process and Backup Failures - Temporary Tablespace Errors - RMAN Configuration and Backup Failures - RMAN Retention Policy and Backup Failures - Loss of Objectstore Wallet File and Backup Failures TDE Wallet and Backup Failures - Incorrect TDE Wallet Location Specification - Incorrect State of the TDE Wallet - Incorrect Configuration Related to the TDE Wallet - Missing TDE Wallet File As this is not new provisioned database and already in the ARCHIVELOG , regular backups of DB system to OCI object storage in places, so the best answers are, - Ensure that your database host can connect to the OCI object storage - Restart the database service agent
Question 23
Which two statements are true about Oracle Cloud Infrastructure (OCI) DB Systems Data Guard service?
Correct Answer: A,C
Explanation An Oracle Data Guard implementation requires two DB systems, one containing the primary database and one containing the standby database. When you enable Oracle Data Guard for a virtual machine DB system database, a new DB system with the standby database is created and associated with the primary database. For a bare metal DB system, the DB system with the database that you want to use as the standby must already exist before you enable Oracle Data Guard. Requirement details are as follows: - Both DB systems must be in the same compartment. - The DB systems must be the same shape type (for example, if the shape of the primary database is a virtual machine, then the shape of the standby database can be any other virtual machine shape). - If your primary and standby databases are in different regions, then you must peer the virtual cloud networks (VCNs) for each database. - Configure the security list ingress and egress rules for the subnets of both DB systems in the Oracle Data Guard association to enable TCP traffic to move between the applicable ports. Ensure that the rules you create are stateful (the default).
Question 24
Which two options are true for Autonomous Transaction Processing (ATP) database? (Choose two.)
Correct Answer: B,C
Explanation You can scale up/down your Autonomous Database to scale both in terms of compute and storage only when needed, allows people to pay per use. Oracle allows you to scale compute and storage independently, no need to do it together. these scaling activities fully online (no downtime required) in Details page Autonomous Database click Scale Up/Down. Click on arrow to select a value for CPU Core Count or Storage (TB). Or Select auto scaling to allow the system to automatically use up to three times more CPU and IO resources to meet workload demand, compared to the database operating with auto scaling disabled.
Question 25
You are an administrator with an application running on OCI. The company has a fleet of OCI compute virtual instances behind an OCI Load Balancer. The OCI Load Balancer Backend Set health check API is providing a 'Critical' level warning. You have confirmed that your application is running healthy on the backend servers. What is the possible reason for this 'Critical' warning?
Correct Answer: D
Explanation References: "In this case, your security rules might not include the IP range for the source of the health check requests. You can find the health check source IP on the Details page for each backend server. You can also use the API to find the IP in the sourceIpAddress field of the HealthCheckResult object." https://docs.cloud.oracle.com/iaas/Content/Balance/Tasks/editinghealthcheck.htm#health-status
