Bug 1636177

Summary:	bad parameters on attach or create database CHARACTER SET WIN1250 is not defined
Product:	[Fedora] Fedora EPEL	Reporter:	Pawel Kubiczek <pawel>
Component:	firebird	Assignee:	Philippe Makowski <makowski.fedora>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	emilt, i, makowski.fedora, stefan.michalowski.chum, tuju
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-07-09 15:38:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pawel Kubiczek 2018-10-04 16:11:12 UTC

Description of problem:
After updating Firebird from version firebird-superserver-2.5.7.27050.0-1.el7.x86_64 to firebird-superserver-2.5.8.27089.0-1.el7.x86_64 
application failed to start with error message: "bad parameters on attach or create database CHARACTER SET WIN1250 is not defined". 
I could NOT find any related issue on the google with similar description. After restoring Firebird from backup application works fine. 
But on other CentOS server I do update again and finally found a solution. 
When I take a file /usr/lib64/firebird/intl/fbintl from version 2.5.7 and put it (replaced it) in version 2.5.8 application start working again on 2.5.8. 

alfa /usr/lib64/firebird/intl # ll 
total 2592 
-rwxr-xr-x. 1 root root 884616 Aug 31 12:10 fbintl 
lrwxrwxrwx. 1 root root 25 Sep 25 22:28 fbintl.conf -> /etc/firebird/fbintl.conf 
-rwxr-xr-x. 1 root root 884496 Feb 21 2017 fbintl.ORIG.2.5.7 
-rwxr-xr-x. 1 root root 884616 Aug 31 12:10 fbintl.ORIG.2.5.8 

alfa /usr/lib64/firebird/intl # cp -p fbintl.ORIG.2.5.7 fbintl 
cp: overwrite 'fbintl'? y 

alfa /usr/lib64/firebird/intl # ll 
total 2592 
-rwxr-xr-x. 1 root root 884496 Feb 21 2017 fbintl 
lrwxrwxrwx. 1 root root 25 Sep 25 22:28 fbintl.conf -> /etc/firebird/fbintl.conf 
-rwxr-xr-x. 1 root root 884496 Feb 21 2017 fbintl.ORIG.2.5.7 
-rwxr-xr-x. 1 root root 884616 Aug 31 12:10 fbintl.ORIG.2.5.8 

alfa /usr/lib64/firebird/intl # md5sum fbintl.ORIG.2.5.7 
f2f9004912509b36d58c233b58a08e10 fbintl.ORIG.2.5.7 

alfa /usr/lib64/firebird/intl # md5sum fbintl.ORIG.2.5.8 
02d622f78c978d8cfb069cca1ed540d8 fbintl.ORIG.2.5.8 

alfa /usr/lib64/firebird/intl # systemctl restart firebird-superserver.service 

It looks like missing CHARACTER SET WIN1250 definition in file /usr/lib64/firebird/intl/fbintl on version 2.5.8 from EPEL repository.

Version-Release number of selected component (if applicable):
firebird-2.5.8.27089.0-1.el7.x86_64

How reproducible:
I do it on two systems with the same result

Steps to Reproduce:
1.update firebird to version 2.5.8
2.start application RaksSQL
3.it cound NOT start because of error " bad parameters on attach or create database CHARACTER SET WIN1250 is not defined"

Actual results:
I found workaround, but I am NOT sure that it is safe

Expected results:
No errors when I start application

Additional info:
http://tracker.firebirdsql.org/browse/CORE-5925

Comment 1 Philippe Makowski 2018-10-05 14:33:25 UTC

note that firebird-superclassic don't have this problem.

Comment 2 Pawel Kubiczek 2018-10-08 08:58:35 UTC

Hi,

Are you sure?

File /usr/lib64/firebird/intl/fbintl is part of the rpm package firebird.x86_64 NOT firebird-superserver.x86_64 or firebird-superclassic.x86_64.

alfa ~ # yum list firebird-*
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: ftp.icm.edu.pl
 * elrepo: ftp.icm.edu.pl
 * epel: ftp.icm.edu.pl
 * extras: ftp.icm.edu.pl
 * updates: ftp.man.poznan.pl
Installed Packages
firebird.x86_64                                                                 2.5.8.27089.0-1.el7                                                   @epel
firebird-filesystem.x86_64                                                      2.5.8.27089.0-1.el7                                                   @epel
firebird-libfbclient.x86_64                                                     2.5.8.27089.0-1.el7                                                   @epel
firebird-libfbembed.x86_64                                                      2.5.8.27089.0-1.el7                                                   @epel
firebird-superserver.x86_64                                                     2.5.8.27089.0-1.el7                                                   @epel
Available Packages
firebird-classic.x86_64                                                         2.5.8.27089.0-1.el7                                                   epel
firebird-classic-common.x86_64                                                  2.5.8.27089.0-1.el7                                                   epel
firebird-devel.x86_64                                                           2.5.8.27089.0-1.el7                                                   epel
firebird-doc.x86_64                                                             2.5.8.27089.0-1.el7                                                   epel
firebird-superclassic.x86_64                                                    2.5.8.27089.0-1.el7                                                   epel

alfa ~ # rpm -qil firebird.x86_64 | grep fbintl
/etc/firebird/fbintl.conf
/usr/lib64/firebird/intl/fbintl
/usr/lib64/firebird/intl/fbintl.conf
alfa ~ # rpm -qil firebird-superclassic.x86_64 | grep fbintl
alfa ~ # rpm -qil firebird-superserver.x86_64 | grep fbintl
alfa ~ #

Comment 3 Philippe Makowski 2018-10-08 10:07:38 UTC

(In reply to Pawel Kubiczek from comment #2)
> Are you sure?
> 
yes I am, that's strange, but this is the case.
and if you use fbintl from 2.5.7 package (https://koji.fedoraproject.org/koji/buildinfo?buildID=860631) all is ok too.

We are trying to find why with upstream core-team (Alex).

Comment 4 emilt 2020-01-22 08:14:39 UTC

The issue is still there in the 2.5.9 packages too.

Comment 5 Juha Tuomala 2022-06-19 12:53:07 UTC

Same here, can't get it started. :(

Comment 6 Troy Dawson 2024-07-09 15:38:53 UTC

EPEL 7 entered end-of-life (EOL) status on 2024-06-30.  EPEL 7 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.