The Perl side of this is pretty simple

# connect to the database and set date format
# for these reports dates are likey truncated somehome
my $dbh = connectdb();
$dbh->do("alter session set nls_date_format='dd Month yyyy hh24:mi:ss'
+");

# uncomment the following for long running reports
$dbh->do("alter session disable parallel query");
$dbh->do(qq(alter session set "_b_tree_bitmap_plans"=false));
$dbh->do("alter session set db_file_multiblock_read_count=2048");

# compile the SQL
my $sth = $dbh->prepare(SQL);

# run the query
$sth->execute();

# retrieve the names of the columns returned and write header line
my @names = @{$sth->{NAME}};

# create a hash based on the first column
my %data = %{$sth->fetchall_hashref($names[0])};
print Dumper(%data);

[download]

What I'd essentially expect is 2 strings, one the key and the second the XML. I'd then parse the XML to get my columns and fill the data in. The intention is to have this as a simple template so anyone can copy the file, edit the SQL (just changing limits, and data items) and the report would generate what's needed. I already have this for basic list reports.

The issue seems that somewhere in the data line the XML shown as a string in SQLPlus is getting converted somehow.

In reply to Re^2: Parsing Oracle PIVOT XML data by tweetiepooh
in thread Parsing Oracle PIVOT XML data by tweetiepooh

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.