Hi and thanks to all who have answered to my questions and big problem
Very appreciated - here is an update:
In the meanwhile, some days ago, i have used "-zapwallettxes" to get rid of the nearly 1 month stucked transaction in my Bitcoin Core wallet. Worked!
Then, right after, i have send them again -
here is the chronological history:
02.12.2017 - I've sent 0,105 BTC - sadly i made a mistake and used one 0 too much so my fee was definetely too small.
(Sidenote: As this transaction is 67000 Bytes(!) big, not like a "regular" transaction of about 250 Bytes, paying a "regular" or even a little bit higher than regular fee - would make this transaction MORE EXPENSIVE THAN THE 0,105 BTC ARE WORTH! ... i just can't pay a fe of 5000$ for a transaction that is only 1500 worth - so this is the main problem i got with this transaction)
28.12.2017 - After my inital transaction wasnt confirmed since learly one month now, i used the trick with "-zapwallettxes" to at least get rid of the transaction in my Bitcoin Core Wallet and got them "free" again in my wallet.dat to send them again.
28.12.2017 - After my 0,105 BTC have been "free" again and available in my wallet, and in the meanhwile another 0,027 BTC arrived in my wallet, i got about 0,132 BTC.
28.12.2017 - To finally get all my mini-transactions "merged" together i have sent all my available 0,132 BTC TO MYSELF (from Bitcoin Core to Bitcoin Core) and payed a fee of 0,0067 BTC for this, which is a lot(!) - about 100$ - but probably still not enough for this 67363 bytes transaction. But again: i cant just pay a "regular" fee like for a regular 250 bytes transaction as this would make the fee thre times bigger than the sent 0,132 BTC !!! Would be sensenless, right?
28.12.2017 - As doing this, the bitcoin core wallet only substracted the fee of 0,0067 BTC from my wallet as it is an "even on delivery". So i had the rest "free" or available in my Bitcoin Core client to send them finally to my prefered destination. So i sent emmediatly the rest of about 0,125 BTC to my prefered destination. THIS transaction (now as it has been "merged") is only 224 bytes big and i payed a fee of exactly 0,0003 BTC which should be very fine i guess.
31.12.2017 - Just today, last day of the year, i have seen that my old inital transaction FINALLY got purged from the mempool and my new two transactions got registered at the mempool - unconfirmed yet. But at leats my old one is gone and my two new ones (with much higher fees) are in the mempool - yeahhh!
So my questions are now:
1. My first new transaction (send to myelf) is the Child and the second one (to my preferred destination) is the Parent, right?
2. If a miner is accepting the parent transaction with the correct and well fee, he has also to accept the child transaction with the monster size (67kb) and the much too low fee? Correct?
3. If yes. Is there a possibility that the miners will decline or ignore the parent transaction because of the "bad" child transaction attached?
Thanks for all your your help and answers and sorry for my bad english, not my native language
Happy new year to all of you!
yamyam