Quantcast

Re: [FB-Tracker] Commented: (CORE-3772) Firebird 2.5 GBak Restore does not create a required USERS table when backing up and restoring a Fb2.0-formatted database.

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [FB-Tracker] Commented: (CORE-3772) Firebird 2.5 GBak Restore does not create a required USERS table when backing up and restoring a Fb2.0-formatted database.

Pvandel@zonnet.nl
Hello Dmitry,

Thanks for your quick response.

However, I think you missed my point; the issue is ***** GBAK ******  (and
not gsec, the latter just reports a missing table USERS).

I still have a question:  How can I appoint co-admins to a specific database
only.

Please read the following text fragment, taken from the description of
Firebird 2.5 QuickStart manual,
topic "Server configuration and management" and sub-topics "Appointing
co-administrators" and "Differences between co-administrators and SYSDBA":

"Please remember:
The RDB$ADMIN role in a database gives the grantee SYSDBA rights in that
database only!

    If it is the security database, the grantee can manage user accounts,
but has no special privileges in other databases.

    If it is a regular database, the grantee can control that database like
he was SYSDBA, but again has no special privileges in other databases, and
has no user administation privileges.
"


As said, earlier, GSEC reports that a USERS table should be defined in a
custom database.
*******************************************************************
***** The issue isn't in GSEC, but the issue is in GBAK! **********
*******************************************************************

Also, to make use of the monitor tables, to see the number of attachments
for example (needed for multi-user usage), one need to log in with the
rdb$admin role. Well, THIS ONLY WORKS WHEN THE USERS TABLE IS IN PLACE! Do
you know another solution?

To me, and to gsec, a table USERS is required.

Please tell me how to appoint co-admins in a custom database that was backed
up and restore with gbak 2.5.1.

Best regards,
Peter  

-----Oorspronkelijk bericht-----
Van: Dmitry Yemanov (JIRA) [mailto:[hidden email]]
Verzonden: vrijdag 24 februari 2012 18:35
Aan: [hidden email]
Onderwerp: [FB-Tracker] Commented: (CORE-3772) Firebird 2.5 GBak Restore
does not create a required USERS table when backing up and restoring a
Fb2.0-formatted database.


    [
http://tracker.firebirdsql.org/browse/CORE-3772?page=com.atlassian.jira.plug
in.system.issuetabpanels:comment-tabpanel&focusedCommentId=24936#action_2493
6 ]

Dmitry Yemanov commented on CORE-3772:
--------------------------------------

USERS is not a system table per se and it's not a part of the Firebird ODS.
It exists in security2.fdb only and GSEC requires it being present there.
But it *should not* exist in any other database. And GSEC *is not* intended
to work with security in user databases.

Thus I see no issue here and IMO this ticket must be rejected.

> Firebird 2.5 GBak Restore does not create a required USERS table when
backing up and restoring a Fb2.0-formatted database.

> ----------------------------------------------------------------------
> ----------------------------------------------------
>
>                 Key: CORE-3772
>                 URL: http://tracker.firebirdsql.org/browse/CORE-3772
>             Project: Firebird Core
>          Issue Type: Bug
>          Components: GBAK
>    Affects Versions: 2.5.1
>         Environment: Firebird 2.5.1 on Windows (7, Vista and XP)
>            Reporter: Peter Vandel
>
> To reproduce:
>   Use Firebird 2.5.1 utility gbak.exe to backup a Firebird database which
has an old 2.0 format.
>   Use Firebird 2.5.1 utility gbak.exe to restore from the backup file made
above.
> The converted database does contain the new (2.1) Monitor tables (like
> MON$ATTACHMENTS, etc.) HOWEVER, the same database does not contain a USERS
(or RDB$USERS) table.
> The USERS table is required by gsec.exe to add co-admins users to a custom
database.
> GSec reports the following if USERS does not exist.
> "gsec -user sysdba -pass <pw> -database <database name/alias>"
> GSEC> disp
> gesec reports the following error: "invalid request BLR at offset 37 table
USERS is not defined".
> A workaround can be to create the table yourself in the database.
> Ok, I hope this isue can be solved soon.
> Thanks in advance,
> Peter Vandel.
> Firebird 2.5 GBak Restore does not create a USERS or RDB$USERS table
> when restoring a 2.0-formatted database

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Firebird-test mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/firebird-test
Loading...