From: Andre Reitz [mailto:[EMAIL PROTECTED]]
> Q1: Does it seem to be correct what I am doing? Yes. > Q2: Must OLDINST and NEWINST have the same devspace sizes? No. You will need only enough space for the existing data. Look at the answer of your backup command. There you will see the number of pages saved in the backup. > Q3: DBMGUI shows only the "DBM"-User under > Configuration/Users on NEWINST, but it is possible > to connect the database with the "imported" DBA user. > (on OLDINST DBMGUI shows the Users: "DBM","operator","DBA") > Did I something wrong? This is ok. There are two types of users: "Database users" and "database manager operators". In this step the DBA exists only as database user. The DBM does not show database user (only DBM operators). > Q4: What is the operator user? (I didn't create it) The user "operator" was a implicit created dbm operator with restricted rigths. We have skipped this behavior some time ago because implicit created users are often a security hole because only few people change the initial password of this users. Also we have seen that people which know the operator do not use it. In the current release there should be no user "operator". > Q5: On what does it depend that the User is shown in DBMGUI? > (seems: only systemusers, but what about "operator" and "domain"?) "domain" is a database user and the DBMGui does not show this user. > Q6: Do I have to call: "dbmcli -d NEWINST -u DBM,DBM > load_systab -u DBA,DBA -ud domain" ? > If I do so, then DBMGUI shows the users: "DBM" and "DBA". This step makes the DBA known to the Database Manager and so this user becomes also a dbm operator. > But where is "operator"? Gone. > Q7: What exactly does load_systab? It loads the so called "system tables". This is a script based creation of many views to internal hidden tables. E.g. the TABLES table is "only" a view to such internal table. Without load_systab you can not execute a "select * from tables". In a new database this views do not exist. In a restored database this views exist normally because they are exist in the backup. After a software update you have to call load_systab because the views and/or the internal tables may have changed. Also after a recovery we recommend a load_systab to avoid problems if the backup was from an older release. > Can I call it everytime I want? :) It doesn't matter but there is no need to do this (except the cases above). Bernd -- SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
