Free oracle xml output software for linux

XML::Output is a Perl module for writing simple XML documents.

SYNOPSIS

use XML::Output;

open(FH,>file.xml);
my $xo = new XML::Output({fh => *FH});
$xo->open(tagname, {attrname => attrval});
$xo->pcdata(element content);
$xo->close();
close(FH);

ABSTRACT

XML::Output is a Perl module for writing simple XML documents

XML::Output is a Perl module for writing simple XML document. The following methods are provided.

new
$xo = new XML::Output;
Constructs a new XML::Output object.

open
$xo->open(tagname, {attrname => attrval});
Open an element with specified name (and optional attributes)

close
$xo->close;
Close an element

empty
$xo->empty(tagname, {attrname => attrval});
Insert an empty element with specified name (and optional attributes)

pcdata
$xo->pcdata(element content);
Insert text

comment
$xo->comment(comment text);
Insert a comment

xmlstr
print $xo->xmlstr;
Get a string representation of the constructed document

Oracle::SQL is a Perl extension for building SQL statements.

SYNOPSIS

use Oracle::SQL;
No automatically exported routines. You have to specifically to import the methods into your package.
use Oracle::SQL qw(:sql);
use Oracle::SQL /:sql/;
use Oracle::SQL :sql;

This is a package initializing object for Oracle::SQL::Builder.

GTK Oracle is a GTK+ 2 interface to Oracle that aids in Oracle application development and testing.
Its features include a schema browser, multiple SQL work areas, SQL syntax highlighting, bind variable entry widgets in the command window, and SQL*Plus-style command scripting.
For SQL statement analysis and tuning there is a tree-style SQL statement "explain plan" facility and the ability to load SQL statements from the runtime cursor cache (V$SQL table), Oracle Statspack repository, and the Oracle Automatic Workload Repository in Oracle version 10g. Full statistics are available on loaded statements.
Main features:
- manually running your applications SQL, outside of the application itself
- trying to find out what queries your application is even running
- checking and gathering statistics
- comparing plans
- running statspack to evaluate results
- autotracing
- peeking in AWR
- peeking the shared pool / v$sqlarea / statspack SQL
- identifying high-resource SQL then this might be of some help.
Usage:
- SQL in the text buffer (anything that gets run via the Execute button) is run on its own thread in the background so it will not block the GUI part, and you can cancel it. This execution thread is started when you start up the program, hopefully never exits, and receives commands via a GLib asynchronous queue, so you can safely keep hitting Execute while a command is running, it will just execute them in order.
- If you log in as SYSDBA you will get a combo box just under the main menubar. Changing the value will execute ALTER SESSION SET CURRENT_SCHEMA=somebody; so when you browse it will be as if you were this user. Be aware that any SQL you execute will result in SYS being recorded as the parsing user in the cursor cache, however.
- If you want to access the cursor cache or statspack or AWR you will need to log in with SYSDBA privileges. You might be able to get away with simply having SELECT on SYS.V$SQLAREA and SYS.V$SQLTEXT.
- SYS is excluded from the cursor cache browsing results. Otherwise you end up with a mass of recursive SQL, which you are not going to be able to tune and that is the point here. If youre a masochist and you do want to browse recursives I suppose you can just modify the relevant SQL so that SYS is not exculded and recompile. Have fun.
- AWR features are only available on 10G servers.
- DBMS_OUTPUT works, go to Edit->DBMS OUTPUT Enable

Oracle::CAPI is a Perl XS wrapper extension for the Oracle Collaboration Suite CAPI SDK.

SYNOPSIS

use Oracle::CAPI;
use Text::vCard;

Oracle::CAPI::SetConfigFile($CAPI_INI_FNAME,$CAPI_LOG_FNAME) && die("Cant init/log CAPI");
$capi_session = Oracle::CAPI::CreateSession() || die("Cant create CAPI session");

# Authenticate to OCS
$rv = Oracle::CAPI::ReconnectAuthUser($capi_session,$HOSTNAME,$nodeid,$pass,$uname);

$rv = Oracle::CAPI::FetchContactsFile($capi_session,$VCARD_NAME_TYPE,$VCARD_STARTSWITH_OP,$chr,$filename);
$rv = Oracle::CAPI::CreateContact($capi_session,$vcard);
$rv = Oracle::CAPI::DeleteContact($capi_session,$uid);

$rv = Oracle::CAPI::DestroyPerlSession($capi_session);

A perl XS wrapper to ctapi.h from the Oracle Collaboration Suite CAPI SDK. This was built and tested against OCS version 9.0.4.2 on Linux.

MARC::XML is a subclass of MARC.pm to provide XML support.

SYNOPSIS

use MARC::XML;

#read in some MARC and output some XML
$myobject = MARC::XML->new("marc.mrc","usmarc");
$myobject->output({file=>">marc.xml",format=>"xml"});

#read in some XML and output some MARC
$myobject = MARC::XML->new("marc.xml","xml");
$myobject->output({file=>">marc.mrc","usmarc");

MARC::XML is a subclass of MARC.pm which provides methods for round-trip conversions between MARC and XML. MARC::XML requires that you have the CPAN modules MARC.pm and XML::Parser installed in your Perl library. Version 1.04 of MARC.pm and 2.27 of XML::Parser (or later) are required. As a subclass of MARC.pm a MARC::XML object will by default have the full functionality of a MARC.pm object. See the MARC.pm documentation for details.

The XML file that is read and generated by MARC::XML is not associated with a Document Type Definition (DTD). This means that your files need to be well-formed, but they will not be validated. When performing XML->MARC conversion it is important that the XML file is structured in a particular way. Fortunately, this is the same format that is generated by the MARC->XML conversion, so you should be able to be able to move your data easily between the two formats.

Oracle::Trace is a Perl Module for parsing Oracle Trace files.

SYNOPSIS

use Oracle::Trace;

print Oracle::Trace->new($tracefilename)->parse->test_report;

Currently the parsing and statistics are very rudimentary, and in certain matters may be fundamentally flawed - you have been warned! Expect this to improve as further development takes place.

new

Create a new object for a given Orace Trace file.
my $o_trc = Oracle::Trace->new($tracefile);

init

Initialise the object (check the tracefile).
$o_trc->init.

opentracefile

Perform basic exists/read/etc. checks on given tracefile.
Returns object or undef.
$o_trc = $o_trc->checkfile($tfile);

header

Return the Header object.
my $o_hdr = $o_trc->header;

entries

Return Entry objects which comply with given regex criteria.
my @o_ents = $o_trc->entries(type=>EXEC #d+, key=>dep, value=>0);

oids

Return the unique object ids for the currently known Entryies
my @oids = $o_trc->oids;

footer

Return the Footer object
my $o_ftr = $o_trc->footer;

test_report

Return a simple test_report of the current object.
print $o_trc->test_report(string);

mini_report

Return a simple string of descending order timings for the statements retrieved from the given objects.
my $s_str = $o_trc->mini_report($i_max, @o_objs);

Note that we use microsecond resolution for Oracle 9i and above and centisecond resolution otherwise

PowerDNS Oracle Backend provides a backend which allows PowerDNS to use Oracle as its data store.

PowerDNS Oracle Backend is a backend driver for the PowerDNS nameserver which allows DNS data to be stored in an Oracle database. PowerDNS can load backend modules at runtime. This backend is fully configurable, and SQL statements can be specified in the configuration file.

Persistent::Oracle is a persistent class implemented using an Oracle database.

SYNOPSIS

use Persistent::Oracle;
use English; # import readable variable names like $EVAL_ERROR

eval { ### in case an exception is thrown ###

### allocate a persistent object ###
my $emp = new Persistent::Oracle(dbi:Oracle:ORCL,
scott, tiger, emp);

### define attributes of the object ###
$emp->add_attribute(empno, ID, Number, undef, 4);
$emp->add_attribute(ename, Persistent, VarChar, undef, 10);
$emp->add_attribute(job, Persistent, VarChar, undef, 9);
$emp->add_attribute(mgr, Persistent, Number, undef, 4);
$emp->add_attribute(hiredate, Persistent, DateTime, undef);
$emp->add_attribute(sal, Persistent, Number, undef, 7, 2);
$emp->add_attribute(comm, Persistent, Number, undef, 7, 2);
$emp->add_attribute(deptno, Persistent, Number, undef, 2);

### query the datastore for some objects ###
$emp->restore_where(qq{
sal > 1000 and
job = CLERK and
ename LIKE M%
}, "sal, ename");
while ($emp->restore_next()) {
printf "ename = %s, emp# = %s, sal = %s, hiredate = %sn",
$emp->ename, $emp->empno, $emp->sal, $emp->hiredate;
}
};

if ($EVAL_ERROR) { ### catch those exceptions! ###
print "An error occurred: $EVAL_ERRORn";
}

ABSTRACT

This is a Persistent class that uses an Oracle database table to store and retrieve objects. This class can be instantiated directly or subclassed. The methods described below are unique to this class, and all other methods that are provided by this class are documented in the Persistent documentation. The Persistent documentation has a very thorough introduction to using the Persistent framework of classes.