Re: Bad parameters on attach or create database - CHARACTER SET ISO8859_1 is not defined Error opening database

327 views
Skip to first unread message
Message has been deleted

Mourad Hedfi

unread,
Dec 28, 2021, 3:46:50 AM12/28/21
to firebird-support
Hello everyone,

I'm returning because I'm really disappointed. I'm blocked with this error and can't deploy my in production.

In fact, I've backuped the database from Windows and restored it on Mac OS Big Sur with gbak with -FIX_FSS_M ISO8859_1 and -FIX_FSS_D  ISO8859_1 flags. On my developpement Mac (Big sur), all works fine and I can access to the database.

But when I deploy the application for tests on 3 Mac OS (Monterry, Big sur), I've always the following error :
####
"Bad parameters on attach or create database - CHARACTER SET ISO8859_1 is not defined Error opening database"
####

I've used the same Firebird package and tried those issues but the problem persists :
  1. backup the database and restore it on test Mac.
  2. using Firebird 3 instead of 2.5.9
  3. use Firebird Classic instead of SS
  4. add intl dylib to the bundle
Please can anyone give me any  help, idea & solution to fix the problem 

Regards

Le jeudi 23 décembre 2021 à 17:19:06 UTC+1, Mourad Hedfi a écrit :
Hello

I've backuped my Firebird 2.5.8 DB on windows using Flamerobin and I've restored it on Firebird 3.0.8 on Mac OS big sur with gback command line.

When I want to connect to the DB from my application I've the following error :
Cannot transliterate character between character sets - Illegal byte sequence Error opening database

I've tried to use -FIX_FSS_M and -FIX_FSS_D options when restoring but the error persists.

Does anyone have encountered this error and can tell me what is wrong ?

Regards
Mourad Hedfi

Dimitry Sibiryakov

unread,
Dec 28, 2021, 5:36:51 AM12/28/21
to firebird...@googlegroups.com
Mourad Hedfi wrote 28.12.2021 9:46:
> But when I deploy the application for tests on 3 Mac OS (Monterry, Big sur),
> I've always the following error :
> ####
> /"Bad parameters on attach or create database - CHARACTER SET ISO8859_1 is not
> defined Error opening database"/
> /####/

This error means that some of these files are missed, cannot be loaded or
corrupted:

intl/intl.dll (libintl.dylib?)
intl/intl.conf
icu*

Use strace (or whatever similar you have in MacOS) to check what file server
is looking for but cannot find.

--
WBR, SD.

Mark Rotteveel

unread,
Dec 30, 2021, 10:15:22 AM12/30/21
to firebird...@googlegroups.com
On 28-12-2021 09:46, Mourad Hedfi wrote:
> In fact, I've backuped the database from Windows and restored it on Mac
> OS Big Sur with gbak with -FIX_FSS_M ISO8859_1 and -FIX_FSS_D ISO8859_1
> flags. On my developpement Mac (Big sur), all works fine and I can
> access to the database.

Why did you use "-FIX_FSS_M ISO8859_1 and -FIX_FSS_D ISO8859_1"? Those
are repair mechanisms that should only be used for repairing certain
issues. Applying them incorrectly can corrupt your database or the data
in it.

Mark
--
Mark Rotteveel

Mourad Hedfi

unread,
Jan 4, 2022, 4:13:30 AM1/4/22
to firebird-support
Thanks Mark for replying.

I've used -FIX_FSS_M / D because my original databse is created on Windows with ISO8859_1 encoding and when I try to restore it on Mac OS I've an error indicating that there're error when writing data. So what I've used those options when restoring and all works fine.

Actually, I've used Firebird Classic Server 2.5.9 for Mac OS and on one Mac it works fine but on the second I've the following error :
####
INET/inet_error: read errno = 54, server address = 127.0.0.1/3050
####

Can anyone tell me how to fix it because I'm using the database locally and I've authorisied firebird service manager.

Regards.

Mark Rotteveel

unread,
Jan 4, 2022, 4:31:22 AM1/4/22
to firebird...@googlegroups.com
On 04-01-2022 10:13, Mourad Hedfi wrote:
> I've used -FIX_FSS_M / D because my original databse is created on
> Windows with ISO8859_1 encoding and when I try to restore it on Mac OS
> I've an error indicating that there're error when writing data. So what
> I've used those options when restoring and all works fine.

Ok, I can't get from your problem description if that was actually
something that those options are intended to fix, but keep in mind that
using those options is a risky thing; always keep a copy of your
original backup/database for safeguarding.

> Actually, I've used Firebird Classic Server 2.5.9 for Mac OS and on one
> Mac it works fine but on the second I've the following error :
> ####
> INET/inet_error: read errno = 54, server address = 127.0.0.1/3050
> ####

On MacOS, socket error 54 is ECONNRESET, or Connection reset by peer
(same as error 10054 on Windows and error 104 on Linux). Which means the
other side of the connection unexpectedly closed the connection. Causes
can range from the client or server crashing, or exiting without cleanly
closing the connection, or abruptly closing the connection without
following the protocol, or things like firewalls interfering with your
network connection.

> Can anyone tell me how to fix it because I'm using the database locally
> and I've authorisied firebird service manager.

Was the issue that you originally asked about fixed? And is this a new
problem? Or is this socket error combined with your original issue?

Mark
--
Mark Rotteveel

Mourad Hedfi

unread,
Jan 4, 2022, 5:10:45 AM1/4/22
to firebird-support
Thanks Mark

I'm getting this error when connecting to database from my application.

Note that I'm using Firebird ClassicServer 2.5.9 et not the SS.

Regards.

Mark Rotteveel

unread,
Jan 4, 2022, 5:24:13 AM1/4/22
to firebird...@googlegroups.com
On 04-01-2022 11:10, Mourad Hedfi wrote:
> Thanks Mark
>
> I'm getting this error when connecting to database from my application.
>
> Note that I'm using Firebird ClassicServer 2.5.9 et not the SS.

Have you checked the firebird.log of the server?

Mark
--
Mark Rotteveel

Mourad Hedfi

unread,
Jan 4, 2022, 5:31:00 AM1/4/22
to firebird-support
Yes, I'm getting this error from the firebird.log.

Regards.

Mark Rotteveel

unread,
Jan 4, 2022, 8:18:59 AM1/4/22
to firebird...@googlegroups.com
On 04-01-2022 11:31, Mourad Hedfi wrote:
> Yes, I'm getting this error from the firebird.log.

There can be more than one firebird.log: one for your server, and one
for your client. If this is the server firebird.log, it might simply be
that the client does not cleanly close the connection.

What error do you get in your client program?

Mark
--
Mark Rotteveel

Mark Rotteveel

unread,
Jan 4, 2022, 8:20:05 AM1/4/22
to firebird...@googlegroups.com
On 04-01-2022 13:58, Mourad Hedfi wrote:
> Where I found the client firebird.log on Mac OS ?

Usually in the same location as the client library loaded by your
application (assuming it's a native application).

Mark
--
Mark Rotteveel
Reply all
Reply to author
Forward
0 new messages