Subject | Re: [firebird-support] upgrade to 2.01 loses SYSDBA password |
---|---|
Author | Kyle Green |
Post date | 2007-05-21T08:44:26Z |
Hi Helen,
This upgrade was on a almost clean machine with only one test database on
it which I don't care about. So nothing to lose :)
My problem is the default SYSDBA/masterkey won't work in FB 2.01 to create
a new database.
I just read Adam's message, and I _was_ using Remote Desktop over vpn. I
will try his suggestion. However I have realized that the same script
worked on another machine where I ran it using Remote Desktop (but that
machine was on the local network, no vpn).
Should it make a difference if I am using vpn? I am logged in to the
remote machine as Administrator. Both machines have identical user
accounts (though they may have different rights...)
Still trying,
Thanks,
Kyle
This upgrade was on a almost clean machine with only one test database on
it which I don't care about. So nothing to lose :)
My problem is the default SYSDBA/masterkey won't work in FB 2.01 to create
a new database.
I just read Adam's message, and I _was_ using Remote Desktop over vpn. I
will try his suggestion. However I have realized that the same script
worked on another machine where I ran it using Remote Desktop (but that
machine was on the local network, no vpn).
Should it make a difference if I am using vpn? I am logged in to the
remote machine as Administrator. Both machines have identical user
accounts (though they may have different rights...)
Still trying,
Thanks,
Kyle
----- Original Message -----
Subject: Re: [firebird-support] upgrade to 2.01 loses SYSDBA password
From: "Helen Borrie" <helebor@...>
Date: Sat, May 19, 2007 22:50
At 12:52 PM 20/05/2007, you wrote:
>Hello,
>
>I've upgraded Fb 1.5 to 2.01 on a non-critical Windows 2003 machine that
>had one previous database. (I uninstalled 1.5 first)
>
>I'm trying to run a script file with a simple create database command and
>I get an error.
>
>CREATE DATABASE "d:\db\MyDb.
fdb"
> USER "SYSDBA"
> PASSWORD "masterkey";
>
>Your user name and password are not defined. etc
>
>
>What might have gone wrong, how can I fix?
This is a major upgrade and your old security.fdb won't work.
Meanwhile, your new server is reading security2.fdb, a placeholder
security database, for which the SYSDBA password is
'masterkey'. READ THE RELEASE NOTES !!!
I hope you have retained your existing security.fdb safely somewhere,
as the script needs to operate on it. There is a script that you can
run initially to upgrade your old security.fdb to the new
security2.fdb but you must follow the extremely detailed
instructions: merely renaming it won't work.
./heLen