Category: SQL*Net, Protocol Server

October 18

Driven by a post from Lewis about “OSDM: Rerverse Engineer A Schema“, I dared my luck to play with Oracle SQL Developer Data Modeler (OSDM), trying to see if it understands the XML database realm off doing things. It doesn’t understands it…at least, yet.  I used the early adopter release 1.5.1 (build 518).

I wonder if it is reasonable that I am disappointed; In the long run the “XDB” schema that I used to reverse engineer isn’t relational but (at least) object-relational. Most of the object relational issues, OSDM understands, but not the theory behind XMLType tables. I tried it multiple times, in the end, even the “secondary tables” and “spatial properties” option you can check during the reverse enginering option.

August 29

Undocumented stuff is always very interesting, although there is of course a reason why it is undocumented… Event settings are more or less in this category. They are often used by Oracle Support in their quest to do a good job solving our problems.

Sometimes events disable or enable features. Sometimes they trace internal processes. The later can be very helpful like setting the infamous “10046” event. I noticed some event settings that can be helpful while using XMLDB or the Protocol Server.

Here a small overview of some events that are in the manuals or mentioned during discussions on the OTN XMLDB Forum… Be careful while “playing” with these events. Some are mentioned in the XMLDB Developers Guide and not an big issue, others can cause very strange results or abnormal behavior.

So be advised…

July 8

I noticed that when I wanted to do some tests with the 11g Native Database Web Service (again), NDWS for short, that I had to gather the information from all over the place on my site. Which was not so very handy. So here a short intro how to set it up, configure and deploy it, also based on the OTN XMLDB Forum example from Mark Drake.

Overview

In short you will have to do the following steps:

  1. Install Oracle XMLDB
  2. Enable the Protocol Server for HTTP access
  3. Enable the orawsv entry points in xdbconfig.xml
  4. Create an example to test the NDWS service
  5. Test the NDWS service by calling the WSDL entry point
  6. Troubleshooting

Sounds very complex, doesn’t it? But be assured, it isn’t at all. As pointed out, most of it is described in posts on this site.