Oracle Docs Fix (#7219)

* Oracle Docs Fix

* doc fixes

catalog-rest-service/src/main/resources/json/schema/entity/services/connections/database/oracleConnection.json

@@ -19,7 +19,7 @@
       "default": "oracle+cx_oracle"
     },
     "OracleDatabaseSchema": {
-      "title": "DatabaseSchema",
+      "title": "Database Schema",
       "properties": {
         "databaseSchema": {
           "title": "DatabaseSchema",
@@ -34,7 +34,7 @@
       "properties": {
         "oracleServiceName": {
           "title": "Oracle Service Name",
-          "description": "Oracle Service Name to be passed. Note: either Database or Oracle service name can be sent, not both.",
+          "description": "The Oracle Service name is the TNS alias that you give when you remotely connect to your database.",
           "type": "string"
         }
       },
@@ -76,10 +76,10 @@
       "description": "Connect with oracle by either passing service name or database schema name.",
       "oneOf": [
         {
-          "$ref": "#/definitions/OracleDatabaseSchema"
+          "$ref": "#/definitions/OracleServiceName"
         },
         {
-          "$ref": "#/definitions/OracleServiceName"
+          "$ref": "#/definitions/OracleDatabaseSchema"
         }
       ]
     },

openmetadata-docs/content/openmetadata/connectors/database/oracle/airflow.md

@@ -140,7 +140,9 @@ workflowConfig:
 - **username**: Specify the User to connect to Oracle. It should have enough privileges to read all the metadata.
 - **password**: Password to connect to Oracle.
 - **hostPort**: Enter the fully qualified hostname and port number for your Oracle deployment in the Host and Port field.
-- **oracleServiceName**: The Oracle Service name is the TNS alias that you give when you remotely connect to your database and this Service name is recorded in tnsnames.
+- **oracleConnectionType** :
+  - **oracleServiceName**: The Oracle Service name is the TNS alias that you give when you remotely connect to your database and this Service name is recorded in tnsnames.
+  - **databaseSchema**: The name of the database schema available in Oracle that you want to connect with.
 - **Connection Options (Optional)**: Enter the details for any additional connection options that can be sent to Oracle during the connection. These details must be added as Key-Value pairs.
 - **Connection Arguments (Optional)**: Enter the details for any additional connection arguments such as security or protocol configs that can be sent to Oracle during the connection. These details must be added as Key-Value pairs.
   - In case you are using Single-Sign-On (SSO) for authentication, add the `authenticator` details in the Connection Arguments as a Key-Value pair as follows: `"authenticator" : "sso_login_url"`

openmetadata-docs/content/openmetadata/connectors/database/oracle/cli.md

@@ -140,7 +140,9 @@ workflowConfig:
 - **username**: Specify the User to connect to Oracle. It should have enough privileges to read all the metadata.
 - **password**: Password to connect to Oracle.
 - **hostPort**: Enter the fully qualified hostname and port number for your Oracle deployment in the Host and Port field.
-- **oracleServiceName**: The Oracle Service name is the TNS alias that you give when you remotely connect to your database and this Service name is recorded in tnsnames.
+- **oracleConnectionType**:
+  - **oracleServiceName**: The Oracle Service name is the TNS alias that you give when you remotely connect to your database and this Service name is recorded in tnsnames.
+  - **databaseSchema**: The name of the database schema available in Oracle that you want to connect with.
 - **Connection Options (Optional)**: Enter the details for any additional connection options that can be sent to Oracle during the connection. These details must be added as Key-Value pairs.
 - **Connection Arguments (Optional)**: Enter the details for any additional connection arguments such as security or protocol configs that can be sent to Oracle during the connection. These details must be added as Key-Value pairs. 
   - In case you are using Single-Sign-On (SSO) for authentication, add the `authenticator` details in the Connection Arguments as a Key-Value pair as follows: `"authenticator" : "sso_login_url"`

openmetadata-docs/content/openmetadata/connectors/database/oracle/index.md

@@ -134,7 +134,9 @@ the changes.
 - **Username**: Specify the User to connect to Oracle. It should have enough privileges to read all the metadata.
 - **Password**: Password to connect to Oracle.
 - **Host and Port**: Enter the fully qualified hostname and port number for your Oracle deployment in the Host and Port field.
-- **Oracle Service Name**: The Oracle Service name is the TNS alias that you give when you remotely connect to your database and this Service name is recorded in tnsnames.
+- **Oracle Connection Type** : Select the Oracle Connection Type. The type can either be `Oracle Service Name` or `Database Schema`
+  - **Oracle Service Name**: The Oracle Service name is the TNS alias that you give when you remotely connect to your database and this Service name is recorded in tnsnames.
+  - **Database Schema**: The name of the database schema available in Oracle that you want to connect with.
 - **Connection Options (Optional)**: Enter the details for any additional connection options that can be sent to Oracle during the connection. These details must be added as Key-Value pairs.
 - **Connection Arguments (Optional)**: Enter the details for any additional connection arguments such as security or protocol configs that can be sent to Oracle during the connection. These details must be added as Key-Value pairs. 
   - In case you are using Single-Sign-On (SSO) for authentication, add the `authenticator` details in the Connection Arguments as a Key-Value pair as follows: `"authenticator" : "sso_login_url"`