Well,

all of these things are not a problem - except for the Oracle database - I suppose that you have an Oracle DataProvider for DNN? Or do you want to have seperate databases (this complicates things a bit..)?

If you do have an Oracle provider for DNN, you can use the new DAL+ help you overcome the Oracle issue.

Other things are just a matter of developing it... (just do it (tm by Nike) )

Well that is one way to go.. and I wouldn't say that there are problems like, more that you cannot use some of the good dnn things (dnn being framework as it is) - example - connection pooling for performance, provider model for abstraction... You can go without all of these things, but they tend to make your life easier sometimes.

That said, I would suggest that you make first an ASP.NET application that does exactly what you need, maybe just instead of many aspx pages, make one page and other things put into user control - and when you are done with that, just convert it to DNN (use appropriate base classes, implement localization, etc...) - it should be easy at that point.

Hope this helps a bit,

Good luck with your module!