Subject Re: [firebird-support] Falling at second hurdle ...
Author Lester Caine
On 17/01/2019 19:34, Dimitry Sibiryakov sd@...
[firebird-support] wrote:
> 17.01.2019 20:11, Lester Cainelester@... [firebird-support] wrote:
>> So what can I do next to get this to work?
> You can read Release Notes for Firebird 3.0, chapter "Compatibility Issues" including
> "Embedded Connections" and "Initializing Security Database".
> Also reading text of "an add record error" can provide a clue.
> Remember, that in embedded mode password is not checked, but user name is still
> applied, so you must use "-u SYSDBA" when connecting to a database for creating SYSDBA
> user (sounds funny, I know).

Personally I would rather NOT have the Embedded Connection insecurity
but that side of things is working and I have a restored database.

Given the 'Important' notice on the top of the 'Initializing the
Security Database' I skipped to the next section, and the various
changes have been made. And I think are right.

Now I'm being told that perhaps the legacy user has not been set, but
now I can run the scripts on 'Initializing the Security Database'

create user SYSDBA password 'SomethingCryptic';
Statement failed, SQLSTATE = 23000
add record error
-violation of PRIMARY or UNIQUE KEY constraint "INTEG_2" on table
-Problematic key value is ("PLG$USER_NAME" = 'SYSDBA')

WHAT am I not reading here?

Lester Caine - G8HFL
Contact -
L.S.Caine Electronic Services -
EnquirySolve -
Model Engineers Digital Workshop -
Rainbow Digital Media -