Hello,
are you sure?
As far I can see db_activate will put the database into state "online" and in http://dev.mysql.com/doc/maxdb/en/21/692225b246b24f9202cb4433b5d691/content.htm
there is a warning
"The target instance must not switch to the operational state ONLINE before you import the data backup from the original instance (step 5). If the target instance has already been ONLINE, reinitialize it."
But how can reinitialize a database without "INIT CONFIG"
BTW it is not possible to warm up the database after a restoring.
regards,
Michael
Kittel, Martin wrote:
Hi Michael,
The 'init config' command is not available in 7.5 any more. Adjust your script to use 'db_activate' instead. 'db_activate' will perform both the job of 'init config' as well as of the 'util_activate' command. So you will probably have to remove one of the next lines in your script as well.
See also http://dev.mysql.com/doc/maxdb/en/91/1a74d35cad11d4aa1500a0c9430730/frameset.htm
Best wishes,
Martin. SAP Labs, Berlin
-----Original Message----- From: Michael J�rgens [mailto:[EMAIL PROTECTED] Sent: Dienstag, 12. Oktober 2004 08:21 To: Schmoger, Daniel Cc: [EMAIL PROTECTED] Subject: Re: rpm upgrade Question
Hello,
thanks for your quick reply.
So far so good.
But now we have a problem with our "transport script" which is responsible to transport the database from our production environment to our test environment.
It is nearly the same as described in http://dev.mysql.com/doc/maxdb/en/52/6942db89e5914496483a576b0
b9749/content.htm .
In the step
dbmcli -d TST1 -u dbm,dbm util_execute INIT CONFIG
I get the response:
[exec] --- [exec] > [exec] > [exec] >db_admin [exec] OK
[exec] --- [exec] >util_connect [exec] OK
[exec] --- [exec] >util_execute INIT CONFIG [exec] ERR [exec] -24988,ERR_SQL: sql error [exec] -3008,Invalid keyword or missing delimiter
[exec] ---
My knldiag is:
2004-10-12 08:10:05 31894 11570 startup complete
2004-10-12 08:10:05 31895 11561 COMMUNIC Connecting T52
local 31831
2004-10-12 08:10:05 31903 11561 COMMUNIC Connected T52
local 31831
2004-10-12 08:10:05 31903 11560 COMMUNIC Releasing T52
2004-10-12 08:10:05 31903 12929 TASKING Task T52 started
2004-10-12 08:10:05 31903 11007 COMMUNIC wait for connection T52
2004-10-12 08:10:05 31895 11561 COMMUNIC Connecting T52
local 31831
2004-10-12 08:10:05 31903 11561 COMMUNIC Connected T52
local 31831
2004-10-12 08:10:05 31895 WNG 11835 COMMUNIC UTILITY is
busy state 28 conn 1097561405
2004-10-12 08:10:05 31895 WNG 11832 COMMUNIC rejecting request
2004-10-12 08:10:05 31903 11560 COMMUNIC Releasing T52
2004-10-12 08:10:05 31903 12929 TASKING Task T52 started
2004-10-12 08:10:05 31903 11007 COMMUNIC wait for connection T52
2004-10-12 08:10:08 31895 11561 COMMUNIC Connecting T52
local 31831
2004-10-12 08:10:08 31903 11561 COMMUNIC Connected T52
local 31831
2004-10-12 08:10:08 31903 11560 COMMUNIC Releasing T52 2004-10-12 08:10:08 31903 12929 TASKING Task T52 started 2004-10-12 08:10:08 31903 11007 COMMUNIC wait for connection T52
Any ideas about the failure.
regards,
Michael
Schmoger, Daniel wrote:
Hi Michael, sorry, there is no such way. you can update using the following steps:
1. create a backup of your database.
2. unregister database:
dbmcli -d <db name> -u <dbm user>,<dbm passwd> db_offline
dbmcli -d <db name> -u <dbm user>,<dbm passwd> db_drop
WITHOUTFILES
3. stop communication server:
x_server stop
4. become root user:
su -
5. remove software:
rpm -e `rpm -qa | grep sapdb`
6. remove old software configs:
rm -rf /var/spool/sql
7. install new software:
rpm -Uhv maxdb-*.rpm
8. add your os user to db admin group:
usermod <os user> -G <your group list>,sdba
9. move parameter files and rundirectory:
mv /var/opt/sapdb/indep_data/config/<db name>*
/var/opt/sdb/data/config/
mv /var/opt/sapdb/indep_data/wrk/<db name>
/var/opt/sdb/data/wrk/
chown -R sdb.sdba /var/opt/sdb/data/config/
/var/opt/sdb/data/wrk
10. chown sdb.sdba for all volumes and backups
11. become your os user:
su - <os user>
12. set evironment:
export PATH=/opt/sdb/programs/bin:$PATH
export LD_ASSUME_KERNEL=2.2.20 13. start communication server:
x_server start
14. register your database with new software:
dbmcli -R /opt/sdb/7500 db_create <db name> <dbm
user>,<dbm passwd>
15. change rundir paramater:
dbmcli -d <db name> -u <dbm user>,<dbm passwd>
param_directput RUNDIRECTORY /var/opt/sdb/data/wrk/<db name>
--16. restart database: dbmcli -d <db name> -u <dbm user>,<dbm passwd> db_online 17. load system tables: dbmcli -d <db name> -u <dbm user>,<dbm passwd> load_systab 18. remove old files: rm -rf /var/opt/sapdb /opt/sapdb
HTH, daniel
-----Original Message----- From: Michael J�rgens [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 7. Oktober 2004 08:10 To: [EMAIL PROTECTED] Subject: rpm upgrade Question
Hi,
does anybody know how to upgrade from rpm sapdb-srv74-7.4.3.32 to maxdb-srv75-7.5.0.18 without first erase and then install ?
I�m a little bit afraid to loose some configuration.
regards,
Michael
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
