OCI


41. Below are the security features enabled by default by the Autonomous Database:

  • Transparent Data Encryption, which provides data encryption at rest.
  • SQL Net Encryption, which provides data encryption on transition or on the flight.
  • Automatic Patching, which fixes security vulnerabilities as well along with bug fixes.
42. Below methods can be used to migrate on-premises databases to Autonomous Databases in cloud

  • Data Pump
  • Golden Gate
  • SQL Loader
  • DBMS_CLOUD package
43. Region, Availability domain, Fault Domains in OCI

  • An OCI region is a localized geographic area, and an availability domain is one or more data centers located within a region.
  • Because availability domains do not share infrastructure such as power or cooling, or the internal availability domain network, a failure at one availability domain within a region is unlikely to impact the availability of the others within the same region.
  • fault domain is a grouping of hardware and infrastructure within an availability domain. Each availability domain contains three fault domains. Fault domains provide anti-affinity: they let you distribute your instances so that the instances are not on the same physical hardware within a single availability domain. A hardware failure or Compute hardware maintenance event that affects one fault domain does not affect instances in other fault domains.

44. Below methods can you use to create users and grant roles in Autonomous Database services.

  • SQL/Developer
  • SQLPIus
46. To scale your Autonomous Database, regards to OCPUs and storage:

  • OCPUs and storage can be scaled independently.
  • ADB on Shared Infrastructure does have auto-scaling and this enabled by default when you create a new instance
  • ADB on Dedicated Infrastructure does not have auto-scaling support.
47. Options available to restore an Autonomous Data Warehouse:

  •       Select the backup from which restore needs to be done.
  •       Specify the point in time (timestamp) to restore.






       Reference: https://docs.oracle.com/en/cloud/paas/autonomous-data-warehouse-cloud/user/backkup-recover.html#GUID-78C28C41-AA87-4AD7-BEB6-693235C73F3C

50. Terraform is the open source orchestration tool can be used to provision autonomous database resources in Oracle Cloud Infrastructure.

51. Below are the subset of services offered via OCI-CLI (command line interface) for Autonomous Database (ABD) via calls made to the OCI API's


  • Create, Get, List, Stop, Restore


52. methods can you use to define Machine Learning Users :

  • SQL/Developer
  • Oracle Cloud Infrastructure Console


53. Migrating an on-premise database to Autonomous Database (ADB) for large amounts of data involves multiple steps like creating a credential object, creating (access to) a storage object/location, running datapump export and running a datapump import. Below are the possibilities:


  • SQL Developer can be used to export/move/import of a database to ADB in 1 set of wizard steps.
  • SQL Developer can import files (.dmp and .csv for example) into ADB which are located on Amazon S3 Object storage.
  • SQL Developer can import .csv files into ADB which are located on the system where SQL Developer is running.
  • Datapump can be used to migrate data from cross platform OS environment, means OS can be linux, AIX,windows, does not mater. 
54. Java Database Connectivity (JDBC) thin client version 18.1 onwards  supports the use of HTTP proxy settings that does NOT support TCP to connect to Autonomous Data Warehouse.

55.  On premise pluggable database cannot be migrated to ADB using plug, unplug or clone.

56. Below are the ordered steps when working with Oracle Machine learning
  • Create Oracle Machine Learning User
  • Create projects
  • Create workspaces
  • Create Notebooks
  • Run SQL Scripts

57. Storage can be Scaled independently of the number of CPUs in an Autonomous Database.


59. When connecting Oracle Analytics Cloud to the Autonomous Data Warehouse, CWALLET.SSO file need to be uploaded.

Reference: https://docs.oracle.com/en/cloud/paas/analytics-cloud/acsom/administer-services-analytics-cloud.html#GUID-8DA9679F-47ED-4DCA-9AD6-51012FF79F1C


60.  Predefined Database Service Names for Autonomous Data Warehouse

  • high: The High database service provides the highest level of resources to each SQL statement resulting in the highest performance, but supports the fewest number of concurrent SQL statements. Any SQL statement in this service can use all the CPU and IO resources in your database. The number of concurrent SQL statements that can be run in this service is 3, this number is independent of the number of OCPUs in your database.
  • medium: The Medium database service provides a lower level of resources to each SQL statement potentially resulting a lower level of performance, but supports more concurrent SQL statements. Any SQL statement in this service can use multiple CPU and IO resources in your database. The number of concurrent SQL statements that can be run in this service depends on the number of OCPUs in your database.
  • low: The Low database service provides the least level of resources to each SQL statement, but supports the most number of concurrent SQL statements. Any SQL statement in this service can use a single CPU and multiple IO resources in your database. The number of concurrent SQL statements that can be run in this service can be up to 300 times the number of OCPUs.

Reference: https://docs.oracle.com/en/cloud/paas/autonomous-data-warehouse-cloud/user/connect-predefined.html#GUID-9747539B-FD46-44F1-8FF8-F5AC650F15BE








No comments:

Post a Comment