quick checkpoints for development mode
i'm a programmer, not a dba. i need a mechanism to quickly make a snapshot of a database (oracle 11g XE) before i run migration. migration changes data, grants, DDL (tables, triggers, lexers, views etc). in case migration fails, i want to quickly revert to the saved state. all this will be done on non-production environment. it's just to speed up the development process
i've heard about full backups, flashbacks, snapshots but i have no idea what's the difference and which one is best for my task
oracle backup snapshot oracle-xe flashback
asked Jun 2 '14 at 23:17
piotrekpiotrek
1041
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
i'm a programmer, not a dba. i need a mechanism to quickly make a snapshot of a database (oracle 11g XE) before i run migration. migration changes data, grants, DDL (tables, triggers, lexers, views etc). in case migration fails, i want to quickly revert to the saved state. all this will be done on non-production environment. it's just to speed up the development process
i've heard about full backups, flashbacks, snapshots but i have no idea what's the difference and which one is best for my task
oracle backup snapshot oracle-xe flashback
asked Jun 2 '14 at 23:17
piotrekpiotrek
1041
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
For development environment, I think that there is no need for heavy guns, so simple export-import could do the trick. Shutdown the database(to have consistent state of data), export user(schema) that you are about to change, do the changes, test applications and if you are not satisfied, drop that user and import exported dmp file.
– mutap
Jun 3 '14 at 23:58
add a comment |
i'm a programmer, not a dba. i need a mechanism to quickly make a snapshot of a database (oracle 11g XE) before i run migration. migration changes data, grants, DDL (tables, triggers, lexers, views etc). in case migration fails, i want to quickly revert to the saved state. all this will be done on non-production environment. it's just to speed up the development process
i've heard about full backups, flashbacks, snapshots but i have no idea what's the difference and which one is best for my task
oracle backup snapshot oracle-xe flashback
asked Jun 2 '14 at 23:17
piotrekpiotrek
1041
i'm a programmer, not a dba. i need a mechanism to quickly make a snapshot of a database (oracle 11g XE) before i run migration. migration changes data, grants, DDL (tables, triggers, lexers, views etc). in case migration fails, i want to quickly revert to the saved state. all this will be done on non-production environment. it's just to speed up the development process
i've heard about full backups, flashbacks, snapshots but i have no idea what's the difference and which one is best for my task
oracle backup snapshot oracle-xe flashback
oracle backup snapshot oracle-xe flashback
asked Jun 2 '14 at 23:17
piotrekpiotrek
1041
asked Jun 2 '14 at 23:17
piotrekpiotrek
1041
asked Jun 2 '14 at 23:17
piotrekpiotrek
1041
asked Jun 2 '14 at 23:17
piotrekpiotrek
1041
asked Jun 2 '14 at 23:17
piotrekpiotrek
1041
1041
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
For development environment, I think that there is no need for heavy guns, so simple export-import could do the trick. Shutdown the database(to have consistent state of data), export user(schema) that you are about to change, do the changes, test applications and if you are not satisfied, drop that user and import exported dmp file.
– mutap
Jun 3 '14 at 23:58
add a comment |
For development environment, I think that there is no need for heavy guns, so simple export-import could do the trick. Shutdown the database(to have consistent state of data), export user(schema) that you are about to change, do the changes, test applications and if you are not satisfied, drop that user and import exported dmp file.
– mutap
Jun 3 '14 at 23:58
For development environment, I think that there is no need for heavy guns, so simple export-import could do the trick. Shutdown the database(to have consistent state of data), export user(schema) that you are about to change, do the changes, test applications and if you are not satisfied, drop that user and import exported dmp file.
– mutap
Jun 3 '14 at 23:58
For development environment, I think that there is no need for heavy guns, so simple export-import could do the trick. Shutdown the database(to have consistent state of data), export user(schema) that you are about to change, do the changes, test applications and if you are not satisfied, drop that user and import exported dmp file.
– mutap
Jun 3 '14 at 23:58
add a comment |
1 Answer
1
active
oldest
votes
The best option would be to use the Flash recovery area option, then set a restore point before you make your change and you can revert to the restore point after you make your change, hence you can rerun the script over and over until you work out the issues. You probably need Enterprise edition to do that, but you can certainly try to make it work. The next best option would be to do an RMAN backup and then run your script and recover the database after the script runs. If it really is a dev system, and if space is tight you might as well turn off archive logging and do a warm backup of the database. hence it is in a consistent state and you don't need to worry about recovering archive logs.
http://docs.oracle.com/cd/E17781_01/server.112/e18804/storage.htm#CIHEHCGI
answered Jun 3 '14 at 16:20
Gandolf989Gandolf989
1,218512
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f66423%2fquick-checkpoints-for-development-mode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The best option would be to use the Flash recovery area option, then set a restore point before you make your change and you can revert to the restore point after you make your change, hence you can rerun the script over and over until you work out the issues. You probably need Enterprise edition to do that, but you can certainly try to make it work. The next best option would be to do an RMAN backup and then run your script and recover the database after the script runs. If it really is a dev system, and if space is tight you might as well turn off archive logging and do a warm backup of the database. hence it is in a consistent state and you don't need to worry about recovering archive logs.
http://docs.oracle.com/cd/E17781_01/server.112/e18804/storage.htm#CIHEHCGI
answered Jun 3 '14 at 16:20
Gandolf989Gandolf989
1,218512
add a comment |
The best option would be to use the Flash recovery area option, then set a restore point before you make your change and you can revert to the restore point after you make your change, hence you can rerun the script over and over until you work out the issues. You probably need Enterprise edition to do that, but you can certainly try to make it work. The next best option would be to do an RMAN backup and then run your script and recover the database after the script runs. If it really is a dev system, and if space is tight you might as well turn off archive logging and do a warm backup of the database. hence it is in a consistent state and you don't need to worry about recovering archive logs.
http://docs.oracle.com/cd/E17781_01/server.112/e18804/storage.htm#CIHEHCGI
answered Jun 3 '14 at 16:20
Gandolf989Gandolf989
1,218512
add a comment |
The best option would be to use the Flash recovery area option, then set a restore point before you make your change and you can revert to the restore point after you make your change, hence you can rerun the script over and over until you work out the issues. You probably need Enterprise edition to do that, but you can certainly try to make it work. The next best option would be to do an RMAN backup and then run your script and recover the database after the script runs. If it really is a dev system, and if space is tight you might as well turn off archive logging and do a warm backup of the database. hence it is in a consistent state and you don't need to worry about recovering archive logs.
http://docs.oracle.com/cd/E17781_01/server.112/e18804/storage.htm#CIHEHCGI
answered Jun 3 '14 at 16:20
Gandolf989Gandolf989
1,218512
The best option would be to use the Flash recovery area option, then set a restore point before you make your change and you can revert to the restore point after you make your change, hence you can rerun the script over and over until you work out the issues. You probably need Enterprise edition to do that, but you can certainly try to make it work. The next best option would be to do an RMAN backup and then run your script and recover the database after the script runs. If it really is a dev system, and if space is tight you might as well turn off archive logging and do a warm backup of the database. hence it is in a consistent state and you don't need to worry about recovering archive logs.
http://docs.oracle.com/cd/E17781_01/server.112/e18804/storage.htm#CIHEHCGI
answered Jun 3 '14 at 16:20
Gandolf989Gandolf989
1,218512
answered Jun 3 '14 at 16:20
Gandolf989Gandolf989
1,218512
answered Jun 3 '14 at 16:20
Gandolf989Gandolf989
1,218512
answered Jun 3 '14 at 16:20
Gandolf989Gandolf989
1,218512
1,218512
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f66423%2fquick-checkpoints-for-development-mode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
For development environment, I think that there is no need for heavy guns, so simple export-import could do the trick. Shutdown the database(to have consistent state of data), export user(schema) that you are about to change, do the changes, test applications and if you are not satisfied, drop that user and import exported dmp file.
– mutap
Jun 3 '14 at 23:58