As I understand you do not have the same environment for development as on production. You are going to create DAL for derby db and replace it by DAL for oracle before going to live (You will be forced to do so if DAL is not primitive). You trying to mitigate risk of migration by creating test suite over this DAL.
In this case the SUT (system under test) will be DAL + DB. You have to test your DAL interface, not DB directly using DbUnit. Insert rows in DB through yours "store" methods and try to load it using "select" methods. Use fresh fixture for each test - restore empty DB before test run. Only such strategy ensures that your DAL interface will be feasible for both oracle and derby.