Applying data changes from one database to another I have an application running on Oracle 9i database and I was looking for something more practical to deploy data changes (not schema changes) from the development database to production.
Currently I work as follows: 

Set all the parameters needed on development database (this might take months), the user validates everything and then I have to apply everything again (which might take some more months). I can't just import the development database into production, because all the data from production will be lost.
Is there something that can be done to avoid this "reworking"?

I tried Database Copy and Data Diff tools available on SQL Developer, but didn't work, since it has a lot of problems with dependencies when inserting new data on the tables..

The point is to keep the new/changed data made by the users in production while I work on the development database. Then import what I did without losing what the users did meanwhile.

Thanks in advance.
One way to do this is to ensure that all tables of properties, or metadata, have a date_created and date_last_modified date.  Then you can filter where the date created is in a time period and export the changes as inserts or updates.

What I do is harder. All changes to development properties are saved as a script of inserts/updates and I use a project/bug tracker to keep track of all the collection of changes.  I refresh development weekly so you see right away if you forgot something like a sequence or a grant.  A typical change could involve data inserts, package updates, grants, sequences and triggers so you have to keep it organized.

Edit: Luke asks how do you keep changes as scripts?
I do two things:


all properties and types are added by a package of procedures and functions.  This checks that the input is valid, updates any logging/audit tables and validates the changes against any business logic you may have in the database.  This is a lot of work to set up but allows you to have a consistent practice for adding new metadata.  Each time you use a procedure or function you can save your call as an sql statement.
I use Toad and this has the ability to filter a table for almost any criteria and export the results as Inserts.