Hello Manuel,
please do not use SDBINST 7.3 with --main
SAPDB::Install::Instance::ChVolPerm::main.
you have to use this option with SDBINST 7.6, because there are any
differences in access rights of database files.
you have called SDBINST 7.6 with ".main" instead "-main". thus the
normal installation entry point was started with option "-v", which
means "print version strings".
regards,
Daniel
-----Original Message-----
From: Manuel Reiter [mailto:[EMAIL PROTECTED]
Sent: Montag, 6. Februar 2006 11:46
To: Schmoger, Daniel
Cc: maxdb@lists.mysql.com
Subject: Re: Migration SAPDB 7.3.00.48 to MAXDB 7.6. with in
Place-Migration // 2 problems
Hi, I'm a step further now, but I can not set the data base to admin
state
-bash-3.00# /opt/sapdb/depend/bin/dbmcli -d ZIPDB3C -u USER.PASSWORD
/opt/sapdb/depend/bin/dbmcli on ZIPDB3C>db_offline
OK
/opt/sapdb/depend/bin/dbmcli on ZIPDB3C>db_reg -R /opt/sdb/7600/
OK
/opt/sapdb/depend/bin/dbmcli on ZIPDB3C>exit
-bash-3.00# /opt/sapdb/indep_prog/bin/x_server stop
12721 XSERVER XSERVER stopped
-bash-3.00# /opt/sdb/programs/bin/x_server
12798 NISERVER NI support started.
WNG 12453 NISSLSRV NISSL Init: SSL: Could not locate licence file
12902 XSERVER started, 'X32/LINUX 7.6.00 Build 016-121-109-428'
-bash-3.00# /root/maxdb-all-linux-32bit-i386-7_6_00_16/SDBINST .main
SAPDB::Install::Instance::ChVolPerm::main -v -d ZIPDB3C
PERL MODULE ARCHIVE VERSION: 7.6.00.16 (changelist id: 109428)
SDBRUN VERSION: 7.6.00.16 (changelist id: 109428)
PERL VERSION: 5.8.7
-bash-3.00# /opt/sdb/programs/bin/dbmcli -d ZIPDB3C -u USER.PASSWORD
Error! Connection failed to node (local) for database ZIPDB3C:
ERR_USRFAIL: User authorization failed
Connection with old dbmcli is possible:
/opt/sapdb/depend/bin/dbmcli -d ZIPDB3C -u USER.PASSWORD
/root/sapdb-all-linux-32bit-i386-7_3_0_48/SDBINST -main
SAPDB::Install::Instance::ChVolPerm::main -v -d ZIPDB3C
-bash-3.00# /opt/sapdb/depend/bin/dbmcli -d ZIPDB3C -u USER.PASSWORD
/opt/sapdb/depend/bin/dbmcli on ZIPDB3C>db_admin
ERR
-24994,ERR_RTE: Runtime environment error
1,Check knldiag! Kernel died before reaching ADMIN state (OS error code
11000)
Last part of knldiag seems to be ok:
2006-02-06 04:01:02 4737 52504 SHUTDOWN
2006-02-06 04:01:02 4736 12620 DBSTATE Shutdown normal requested
2006-02-06 04:01:02 4736 12696 DBSTATE Change DbState to
'SHUTDOWN'(24)
2006-02-06 04:01:02 4736 12696 DBSTATE Change DbState to
'COLD'(22)
2006-02-06 04:01:02 4736 11560 COMMUNIC Releasing T5
2006-02-06 04:01:02 4736 11007 COMMUNIC wait for connection T5
2006-02-06 04:01:02 4728 12850 DBSTATE Caught STOP signal
2006-02-06 04:01:02 4728 12696 DBSTATE Change DbState to
'STOP'(27)
2006-02-06 04:01:02 4728 12697 DBSTATE Resuming tracewriter
2006-02-06 04:01:02 4734 12825 TASKING state 27 before shutkill(1)
2006-02-06 04:01:02 4727 12696 DBSTATE Change DbState to
'TRACE_WRITER_WAIT'(27)
2006-02-06 04:01:02 4734 12825 TASKING state 27 before shutkill(1)
2006-02-06 04:01:02 4734 12619 TASKING Releasing tracewriter
2006-02-06 04:01:02 4724 12611 DBSTATE SERVERDB is being stopped
--------------------------------------- current write position
-----------------
+++++++++++++++++++++++++++++++++++++++ Kernel Exit
++++++++++++++++++++++++++++
2006-02-06 04:01:03 4722 12843 DBSTATE Kernel exited normal
2006-02-06 04:01:03 4722 12696 DBSTATE Change DbState to
'KILL_ALL'(27)
2006-02-06 04:01:03 4722 12696 DBSTATE Change DbState to 'OFFLINE
'(27)
--------------------------------------- current write position
-----------------
Connection with DBMGUI is possible:
The database is shown als version 7.6.00.16
But when I view the path for the RUNDIRECTORY it's empty also the path
for DIAG_HISTORY_PATH.
Any ideas are welcome
Schmoger, Daniel schrieb:
Hello Manuel,
you're right. MS mail client has added a newline automatically. :(
But all SDBINST versions >= 7.5 has this option.
"SDBINST -v" shows version strings.
You can use the SDBINST in the 7.6 installation kit for this job too.
Regads,
Daniel
-----Original Message-----
From: Manuel Reiter [mailto:[EMAIL PROTECTED]
Sent: Freitag, 3. Februar 2006 08:25
To: Schmoger, Daniel
Cc: maxdb@lists.mysql.com
Subject: Re: Migration SAPDB 7.3.00.48 to MAXDB 7.6. with in
Place-Migration // 2 problems
Hello Daniel,
if I'm not mistaken than it should be:
/opt/sdb/programs/bin/SDBINST --main
SAPDB::Install::Instance::ChVolPerm::main -v -d <database name>
called from the older version of the database program, because in MAXDB
7.6 these option does not exist.
Manuel
Schmoger, Daniel schrieb:
Hello Manuel,
seems there is a bug in documentation.
A tool chvolperm doesn't exist.
Try this instead:
/opt/sdb/programs/bin/SDBINST --main
SAPDB::Install::Instance::ChVolPerm::main -v -d <database name>
btw: "db_reg -R /opt/sdb/programs" - looks like independent program
path, but you have to use the dependent path.
HTH,
Daniel
-----Original Message-----
From: Manuel Reiter [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 2. Februar 2006 13:10
To: maxdb@lists.mysql.com
Subject: Migration SAPDB 7.3.00.48 to MAXDB 7.6. with in
Place-Migration
// 2 problems
hi I tried it like in the description (both db-versions installed on
Linux 32 bit)
http://dev.mysql.com/doc/maxdb/en/88/c290d224d9e140a9c7048ffff0c233/co
nt
ent.htm
at point 9:
UNIX: Assign the database instance to the new software version.
db_reg -R <dependent_path_new>
in my case: db_reg -R /opt/sdb/programs/
if I try to reconnect to the database after this ( as said in point
11),
the data base cannot be found anymore.
at point 13: Call the "chvolperm" program. This program does not exist
on my server. Does anybody know the packe it should be in ?
regards Manuel Reiter
