---
title: Database Access Manager Configurations
slug: singleconnect-reference-guide-3-1-0/database-access-manager-configurations
description: Learn how to set the 'sql.proxy.bind.port.range' parameter in Single Connect's Database Access Manager to add Oracle devices for new tenants in multitenant environments. This document also explains dynamic data masking and provides a reference to another 
docTags: 
createdAt: 2022-08-02T21:37:19.000Z
---

Single Connect offers a Database Access Manager for multitenant environments. All features of the SQL Proxy are enabled on a multitenant environment, if the user has a license for Data Access Management, along with Multitenancy. Logging, Policy Enforcement, and Masking can be provided.


For a user, device, and policy definition details, please refer to section [](https://app.archbee.com/docs/jsymInd0w_SXayMlKGOmR/5qFd2MJYKbHUD5U7k_n8T)[User/Device/Policy Definition](docId\:GIY4A3O_Acl_brhmGAySs). To add Oracle devices for new tenants, the following parameter should be set from the host admin System Config Manager screen for the port assigning option:

1. Navigate to the** Administration** >** System Config Man**.
2. Set the **sql.proxy.bind.port.range** parameter with the requested port range.

| **Parameter Name**                                          | **Parameter Value**                                                                                                                         |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| **sql.proxy.bind.port.range**                               | Port range (e.g. 6000-7000)                                                                                                                 |
| **sql.proxy.oracle.local.bind.port.tenant\_$tenant\_name$** | Port number for Oracle devices (e.g. 5000). It should be added separately for each newly created tenant, if the Oracle device will be used. |

For dynamic data masking, please refer to section [Dynamic Data Masking](docId\:j6t8XhaumO3cjZG0JrmOI). For further guidance, please refer to the **How to use Data Access Manager in Multitenancy** document.