How to fix "CHARACTER SET ISO8859_1 is not installed" error while taking backup

[Tommi Prami]

Hello,

Trying to take backup, and log stats with : 

gbak:gbak version WI-V2.5.9.27139 Firebird 2.5
gbak:    Version(s) for database "f:\git\ThFbDbMaintenance\Build\Apps\DEMO_FB4.fdb.tmp"
Firebird/x86/Windows NT (access method), version "WI-V2.5.9.27139 Firebird 2.5"
on disk structure version 11.2
gbak:readied database f:\git\ThFbDbMaintenance\Build\Apps\THDEMO_FB4.fdb.tmp for backup
gbak:creating file f:\git\ThFbDbMaintenance\Build\Apps\THDEMO_FB4.fdb.tmp.fbk
gbak:starting transaction
gbak:database f:\git\ThFbDbMaintenance\Build\Apps\THDEMO_FB4.fdb.tmp has a page size of 16384 bytes.
gbak:writing domains

And suddenly middle of writing data (After writing :

gbak:0 records written
gbak:    writing index PK_VEROTILINPAATOSOTSIKKO
gbak:    writing index UQ_VEROTILINPAATOSOTSIKKO
gbak:    writing index FK_VEROTILINPAATOSOTS_ACDOC1
gbak:    writing index FK_VEROTILINPAATOSOTS_ACDOC2
gbak:    writing index FK_VEROTILINPAATOSOTS_COMPANY
gbak:    writing data for table VEROTILINPAATOSOTSIKKO
gbak: ERROR:CHARACTER SET ISO8859_1 is not installed
gbak: ERROR:gds_$start_request failed
gbak:Exiting before completion due to errors

Never seen something like this, is there way to fix this. I am using variation of the FB2.5 -> FB4 conversion bat posted while back, main difference is that in this case not using stdout->stdin optimization, because that failed even earlier in the process. So there must be something on the server I am running these at, because on local computer it works well. 

So FB2.5.9 and FB4.0.1   embedded  are used 

gbak: ERROR:CHARAC

[Tommi Prami]

Found the possible cause, embedded engines don't have int and other sub folders, have to fix extractors.

I'll try to remember to report the results

[Mark Rotteveel]

On 29-07-2022 08:12, Tommi Prami wrote:
> Found the possible cause, embedded engines don't have int and other sub
> folders, have to fix extractors.
>
> I'll try to remember to report the results

Not having the intl folder and its files is indeed the general cause for
this error.

Mark
--
Mark Rotteveel