Typically, the pockets shipped with Bitcoin Core solely retains copies of any transactions that instantly contain the pockets. Once you import a key, your node scans your complete blockchain to see if any transactions concerned that key.
A pruned node has processed the entire blockchain, however solely retains the tail finish of the info. Which means that if you import a personal key in a pruned node, the pruned node doesn’t have the info to examine for related transactions. That is why it’s incompatible with the rescan requirement. To search out the transactions associated to the important thing, you have to to repeat the preliminary synchronization of the blockchain.
As Prayank already acknowledged in his reply, you might use
importprivkey "<key>" "" false
to import one or a number of non-public keys. The “false” within the third argument skips the standard rescan triggered by the import. This could keep away from the error you’re seeing.
After you could have imported all related keys, you restart your node with the -reindex commandline possibility to begin over with the preliminary sync. Your pockets will scan for related transactions throughout the synchronization and rediscover the funds and transaction historical past of the pockets.
In the event you want to keep away from performing one other synchronization along with your node, you might as an alternative import the important thing right into a light-client equivalent to Electrum as prompt by RedGrittyBrick in one other reply.
