# Use Oracle as database

**URL:** <https://community.bloomreach.com/t/use-oracle-as-database/1556>\
**Category:** Experience Manager (PaaS/OnPrem)\
**Created:** [November 9, 2019, 7:47am UTC](https://community.bloomreach.com/t/use-oracle-as-database/1556 "2019-11-09T07:47:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mohammad\_1m2](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/mohammad_1m2/32/536_2.png) [@mohammad\_1m2](https://community.bloomreach.com/u/mohammad_1m2)\
**Post date:** [November 9, 2019, 7:47am UTC](https://community.bloomreach.com/t/use-oracle-as-database/1556/1 "2019-11-09T07:47:59Z")

</div>

Hello  
I configure my bloomreach to use oracle as database. I read [Configure Bloomreach Experience Manager for your Database Server](https://documentation.bloomreach.com/library/deployment/configuring/databases.html) and [Configure Bloomreach Experience Manager for Oracle database](https://documentation.bloomreach.com/library/deployment/configuring/configuring-hippo-for-oracle-database.html) and configure the context and repository like examples. The document properly save in oracle tables but the document type save as yaml file in `cms\repository-data\application\src\main\resources\hcm-config\namespaces\cms` directory. How can I tell bloomreach to record all the data and settings in Oracle? If there isn’t any way for this, which data and setting store in file?

---

<div class="post-metadata">

**Author:** ![jasper.floor](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/jasper.floor/32/28_2.png) [@jasper.floor](https://community.bloomreach.com/u/jasper.floor)\
**Post date:** [November 11, 2019, 1:40pm UTC](https://community.bloomreach.com/t/use-oracle-as-database/1556/2 "2019-11-11T13:40:38Z")

</div>

What is happening with the yaml file is autoexport [1]. Autoexport is activated by the cargo profile and should only run on a local deployment. Data still ends up in the database, but it is also exported to your project. This allows developers to make changes they don’t have to manually put back in the project. These changes will become part of the deployment so that they can be migrated to other environments. For content this may or may not be desirable. You can configure paths in autoexport so take a look at that. You can also move data to the development module which shouldn’t be included in build without development data.

[1] [https://documentation.bloomreach.com/library/development/automatic-export-add-on.html](https://documentation.bloomreach.com/library/development/automatic-export-add-on.html)