Re: Execute DB2 stored procedue

2023-02-27 Thread Matt Burgess
Stored procedures that take no output parameters and return ResultSets should 
work fine with ExecuteSQL, but for DBs that allow OUT and INOUT parameters, 
those won’t make it into the outgoing FlowFile (in either content or 
attributes).

Regards,
Matt


> On Feb 27, 2023, at 4:19 PM, Dmitry Stepanov  wrote:
> 
> 
> We run our procedure using ExecuteSQL.
> Just make sure to use proper SQL syntax 
> 
>> On February 27, 2023 2:09:19 p.m. Phillip Lord  
>> wrote:
>> 
>> Hello,
>> 
>> Does anyone have any experience executing a DB2 stored procedure?  
>> Potentially using PutSQL? I don't think it can be done using ExecuteSQL, and 
>> I can likely use an executeStreamCommand to accomplish this.  But trying not 
>> to reinvent the wheel if I can just do it using a simple Nifi processor
>> 
>> Thanks
>> Phil
> 
> 


Re: High Cpu Utilisation in Nifi

2023-02-27 Thread Patrick Timmins
Hello Harshit ... I'm assuming "MyssqlTcp" is the name of a process 
group in your NiFi GUI??  If so, can you show a screenshot of the NiFi 
processors that are in that process group so we can see which processor 
or where in the processing things might be hanging up?


Given no other info, the easiest, most likely way for something like 
that to happen in NiFi that I've seen (learned the hard way) is to have 
a mis-configured GetFile processor (eg: have the Keep Source File set to 
true, and have the Polling interval set to 0 sec).


Thanks for any further info you can provide.

Pat


On 2/27/2023 12:44 AM, James Halfpenny wrote:

Hi Harshit,
That does not look typical of NiFi, what it looks like to me is a 
cryptominer. Is this NiFi connected to the Internet without 
authentication or with a weak password? Publicly accessible NiFi 
servers will quickly be exploited to run ExecuteProcess and deploy a 
miner.


The fact that the name doesn’t seem to match anything related to NiFi 
and that the CPU usage is high indicate this may be a malicious 
process. If you kill it there will usually be some sort of persistence 
mechanism that will restart it. If you check and confirm it’s an 
unwanted process I would strongly advise deleting this NiFi instance 
and redeploying.


Kind regards,
Jim


On 27 Feb 2023, at 05:26, harshit.varsh...@iktara.ai wrote:



*From:* harshit.varsh...@iktara.ai [mailto:harshit.varsh...@iktara.ai]
*Sent:* Monday, February 27, 2023 10:53 AM
*To:* 'users@nifi.apache.org'; 'u...@nifi.apache.org'
*Subject:* High Cpu Utilisation in Nifi

Dear Team,

I am currently facing some issues in using Nifi latest Docker image 
as it that is on docker hub using command Docker pull apache/nifi.The 
problem I am facing is After 3 days Nifi starts a process That is 
“MyssqlTcp” that is taking over 500% Cpu utilization when running 
Htop  in server and it is related to nifi how to resolve it any 
suggestions.


Here is the screenshot of the process

Thanks & Regards

Harshit Varshney



Re: Execute DB2 stored procedue

2023-02-27 Thread Dmitry Stepanov

We run our procedure using ExecuteSQL.
Just make sure to use proper SQL syntax

On February 27, 2023 2:09:19 p.m. Phillip Lord  wrote:

Hello,

Does anyone have any experience executing a DB2 stored procedure?  
Potentially using PutSQL? I don't think it can be done using ExecuteSQL, 
and I can likely use an executeStreamCommand to accomplish this.  But 
trying not to reinvent the wheel if I can just do it using a simple Nifi 
processor


Thanks
Phil




Execute DB2 stored procedue

2023-02-27 Thread Phillip Lord
Hello,

Does anyone have any experience executing a DB2 stored procedure?
Potentially using PutSQL? I don't think it can be done using ExecuteSQL,
and I can likely use an executeStreamCommand to accomplish this.  But
trying not to reinvent the wheel if I can just do it using a simple Nifi
processor

Thanks
Phil