Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 468 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
ORDS - backup/restore - refreshes
Hi,
I have an up and running 19.4 ORDS on a Tomcat.
At this moment our developers are creating and testing services.
But now they ask to refresh the data.
Our normal normal procedure is to perform a database cloning with the production database as the source and the DEV database as the target.
But of course, with this procedure will the developers loose all their work.
Is there some kind of ORDS backup/restore procedure? Is it enough to export/import the ORDS_METADATA and the ORDS_PUBLIC_USER? Are there also objects created in the 'service owner' schema?
Thanks for your input!
Steven
Answers
-
What source control system are your devs using?
They should be keeping their restful services there as well.
A SQL script basically...
-
As we are in a POC phase, they use only SQL Developer at the moment.
-
If you are writing code that is important, I would recommend you start versioning it... backing it up at least.
In SQL Developer, right click on your module, you can export it as a SQL script.
I talk about this in detail here
https://www.thatjeffsmith.com/archive/2018/12/how-to-export-your-restful-services/
-
And the extracted DDL in combination with the dump of the ORDS_METADATA is enough to setup it up in a new database?
-
If the ords metadata schema is included in your DB clone, the rest services will already be there
-
What about OAUTH clients, roles, and privileges? I have the same scenario, but it is not enough to export RestServices, we also need to backup our DEV clients id, considering that they are not allowed to switch to production mode, so, they don't exist inside prod db.
When cloning production to Dev, we erase these clients, losing their secrets, ids, and privilege/role mappings.
What do I need to copy, or how could I be sure that I am not going to loose anything?
Thanks!.
-
All of that is in the metadata schema
-
So, should I overwrite the entire ORDS_METADATA scheme? Cause going deeper, I saw internals ID and some cascade constraints, and I am not quite sure about what I am doing.
-
I'd recommend all the code be backed up to SQL scripts that can be re-ran on the cloned environment.
OR
Data Pump ORDS_METADATA in and out as required
