Re: Datapump question

Hi Ghassan,

I just copied the example from my package on the fly and apparently left lines in it. The example was only intended to explain the problem here. For my customer, I have built a workaround and am satisfied with it first.

However, I will check on occasion if the problem is fixed in 12.2. Which I hope, since I am a huge fan of "dbms_datapump" (and Oracle in general) and have so far only very good experiences with it.

Thanks for your Hint :-)

Am Do., 24. Jan. 2019 um 15:31 Uhr schrieb Ghassan Salem < salem.ghassan_at_gmail.com>:

> Ahmed,
> This should work if you have patch for bug 14202396 (fixed in 12.2, and
> there are backports to older versions).
> And your code does not work as it is: you close a cursor that does not
> exists in the code, and you have to have the function defined in a package,
> not as a standalone one.
>
> rgds
>
> On Thu, Jan 24, 2019 at 10:26 AM Ahmed <gherrami_at_gmail.com> wrote:
>
>> Before I opted for this solution, I made a proof of concept, then the
>> whole thing was implemented and it was revealed during testing that when
>> anonymizing
>> more than ten columns in a table, that does not work at all, and without
>> any reasonable error message. This is from my point of view not fair from
>> Oracle side.
>> Now I have a workaround built in, which cost me two days. But thanks for
>> the hint of Adric.
>>
>> Am Mi., 23. Jan. 2019 um 20:10 Uhr schrieb Mark W. Farnham <mwf_at_rsiz.com
>> >:
>>
>>> cool. Learning something new today. I didn’t even know you could obscure
>>> column content with exp/imp.
>>>
>>>
>>>
>>> *From:* oracle-l-bounce_at_freelists.org [mailto:
>>> oracle-l-bounce_at_freelists.org] *On Behalf Of *Mladen Gogala
>>> *Sent:* Wednesday, January 23, 2019 9:43 AM
>>> *To:* Adric Norris; Ahmed
>>> *Cc:* oracle-l_at_freelists.org
>>> *Subject:* Re: Datapump question
>>>
>>>
>>>
>>> With the advent of cloud and DBaaS, data pump becomes awkward. However,
>>> even Oracle 18c maintains the good, old exp/imp executables which can be
>>> used instead. Ttue, data pump versions are much faster, but there is no
>>> need to copy files locally and there are no limits with the number of
>>> columns.
>>>
>>>
>>>
>>> Mladen Gogala
>>> Database Consultant
>>> Tel: (347) 321-1217
>>>
>>> On 1/22/2019 3:03:23 PM, Adric Norris <landstander668_at_gmail.com> wrote:
>>>
>>> I'm not sure what version you're on, but 11.2.0.4 had a limit of
>>> something like 8-10 columns (going from memory, so the exact number is a
>>> bit fuzzy). We opened a SR for it at the time, and Oracle's response was
>>> that you need to purchase Oracle Data Redaction if the built-in Datapump
>>> limit is insufficient.
>>>
>>>
>>>
>>> On Tue, Jan 22, 2019 at 11:47 AM Ahmed <gherrami_at_gmail.com> wrote:
>>>
>>> I try to export a table using DBMS_DATAPUMP. The table has 20 columns
>>> and I try to anonymise 11 columns using functions from package. Like this
>>> way:
>>>
>>>
>>>
>>> dbms_datapump.data_remap(handle => h1, name => 'COLUMN_FUNCTION',
>>>
>>> table_name => 'TEST_TABLE', column => 'COL1', function =>
>>> 'MYPKG.FU1', schema => USER);
>>>
>>>
>>>
>>> but it seems that work only for 10 columns.
>>>
>>> If I try to anonymize more than 10 columns I get ORA-39001 invalid input
>>> argument at datapump job definition.
>>>
>>>
>>>
>>> Is this a bug or maybe a restriction? Any Idea?
>>>
>>>
>>>
>>> Best Regards
>>>
>>> Ahmed Fikri
>>>
>>> Senior Developer
>>>
>>> Stuttgart, Germany
>>>
>>>
>>>
>>>

--
http://www.freelists.org/webpage/oracle-l