callproc dbms_metadata.add_file

"Werner Moser" <[email protected]>
Newsgroups gmane.comp.python.db.cx-oracle
Message-ID <trinity-fc957253-3bca-4bb5-9d5b-4f45ce364644-1411586314910@3capp-gmx-bs04>
Hi,

I'm writing a little script which exports some data from my database and I want to use dbms_datapump.

It almost works, I am stuck with the logfile though. To create one, you have to use the function dbms_datapump.add_file:

DBMS_DATAPUMP.ADD_FILE (
handle IN NUMBER,
filename IN VARCHAR2,
directory IN VARCHAR2,
filesize IN VARCHAR2 DEFAULT NULL,
filetype IN NUMBER DEFAULT DBMS_DATAPUMP.KU$_FILE_TYPE_DUMP_FILE),
reusefile IN NUMBER DEFAULT NULL;

when I call it with the first five parameters, I always get an ORA-6502 - for the size of the file (which is not needed for the logfile ...)

cur.callproc('dbms_datapump.add_file',[handle,'test.log','EXP_IMP',102400,'KU$_FILE_TYPE_LOG_FILE'])

cx_Oracle.DatabaseError: ORA-06502: PL/SQL: numeric or value error: character to number conversion error

As far as I have found out only positional parameters can be used, i.e. a dict or key/value is not supported - if it was I could use only the needed parameters here (handle, filename, directory and filetype).

so, how can I get this to work? the parameter filesize is optional but how can I write that?

br,

Werner

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk

_______________________________________________
cx-oracle-users mailing list
cx-oracle-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/cx-oracle-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.