Debugging PL/SQL Code

Question

I have very interesting situation. I have been assigned to migrate an complete database driven application to Java/Spring and Tomcat Server, now my challenge here is that current application does not have any java, there are only procedures and packages and functions and everything is PLSQL, even front end is in packages, htp.p tag has all HTML front end code.

Other challenging part is that application is legacy application and many developers have worked on it and the last one has just left.

I want to know what approach and guidance you would give to someone who has similar situation as mine and also what are the ways to debug the PLSQL application, would really if you can some useful pointers about debugging PLSQL along with some reference to books or web sites.

Thanks.

anotherdave · Accepted Answer · 2011-03-10 01:02:57Z

2

The best thing to do would be use the database designs (assuming they're OK), and the HTML output of the current version for your view designs, and redo the application in whatever Java framework you're happy with. The PL/SQL version of the application would be a very poor fit if you just tried to re-implement it in Java.

The htp and htf packages are the PL/SQL Web Toolkit. There's pretty much a one-to-one mapping from these procedures to HTML tags so they're very low level and not hard to understand. It's basically the equivalent of servlets for PL/SQL, only less powerful.

Debugging web toolkit code is very awkward because you have to remotely attach to the database session that the Apache modplsql module is using. Oracle's JDeveloper used to support this but current versions don't seem to work properly, at least not with Oracle 11g in my recent attempt. It's a lot easier to use old-fasioned print or logging methods of debugging, for example using LOG4PL/SQL. But really you don't want to get into the code that deeply since you should be throwing all of it away anyway.

answered Mar 10, 2011 at 1:02

anotherdave

711 bronze badge

Sign up to request clarification or add additional context in comments.

2 Comments

Rachel Over a year ago

I did not understood The PL/SQL version of the application would be a very poor fit if you just tried to re-implement it in Java. line, can you elaborate on it.

anotherdave Over a year ago

Unless your legacy application is remarkably advanced it will be mostly procedural code with model, view and controller concepts all mixed up, often in the same procedure. Just directly porting the PL/SQL code to Java will give you an even less maintainable nightmare.

Janek Bogucki · Accepted Answer · 2011-03-09 20:45:14Z

0

Try this tutorial: Developing and Debugging PL/SQL using Oracle SQL Developer (2.1)

answered Mar 9, 2011 at 20:45

Janek Bogucki

5,1533 gold badges32 silver badges41 bronze badges

Collectives™ on Stack Overflow

Debugging PL/SQL Code

2 Answers 2

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related