Unless you have a backup made already, you're in for trouble.

When one drive of a RAID 0 array fails, the entire array is lost.  That's why going forward you should not be building a RAID 0 array -- keep the drives separate.

For the present, you'll need to weigh the value of the lost data against the cost of data recovery.  And even a professional recovery service will struggle recover from a RAID 0 array. If it is possible to recover the data, expect a charge will into the thousands of dollars -- and it may not be possible at all.

why after disconnect and reconnect SSDs problem started? so every time I connect and reconnect SSDs I will have same problem?

It could be a marginal drive that's on its way out.  If your post means you have access to the system at this point, back it up now.  

Then get rid of the RAID 0 array (which does nothing for performance) and set up separate drives, and initiate a backup routine going forward. 

No I don't have access to SSD. it show only 2 SSD is ready for RAID and 1 SSD RAID failed

oh really bad news for me because I lost about 15 Years data :(

One can always learn from mistake.  For periodic routine cleaning, use powerful air duster without touching any of the internal components.  It's also very useful with removal of dust and debris under keyboard.

For system setup, operating system and data do not get performance advantage over a RAIID 0 boot drive.  Since you are at a starting point again, think about your usage needs and make plan to have system storage setup properly.

RAID 0 does not support redundancy, parity, or fault tolerance.  While it's useful to process read/write requests quickly, there is no rebuild option in case of a disk failure.

If data is important, it must be backup externally.  Redundancy in RAID configurations is a good overall protection against single disk failure but is not a substitution for full fledge backup.

With a three disk system, you may consider to build a RAID 5 setup for both redundancy and parity.