[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sapdb-general
Subject:    SDBUPD: domain user missing
From:       Gerd_König <koenig () transporeon ! com>
Date:       2004-03-25 10:10:29
Message-ID: 4062B015.2030904 () transporeon ! com
[Download RAW message or body]

Hi,

I want to upgrade from 7.4.03.31 to 7.5.0.5 via SDBUPD.
This step fails with the following error:

========================================
beginning to check sap db instances
resume broken instance check
finding instance type...
finding starting release...
finding migration strategy...
looking for running instances...
checking paramfile modifications...
checking volume access...
looking for domain user...
MaxDB instance "DATABASE" not ready to update
looking for domain user...
user profile container contains:

  dbm

domain user not found in user profile container
unable to load system tables

load system tables and run SDBUPD again
========================================

The command "dbmcli ..... user_getall" shows the same: "dbm"
The 7.4 instance is up and running.

The migration from 7.3 to the currently running 7.4 was done by the steps
mentioned in the "tutorial" migration73_74eng.pdf
except the load_systab call (this was changed to: "load_systab -ud domain")

so, how can I solve this problem, and be successfull in migrating to 
MaxDB ;-) ??


thanks in advance ...GERD...


attached is the log of the SDBUPD-call (why is there an entry with 
profile "LiveCache",
we are using OLTP ?? )

["MaxDBUpdate_install-25.03.2004-10.54.log" (text/plain)]

CALL: SDBUPD -d DBNAME -u dbm,******** -INSTANCE -profile APO LiveCache
STDOUT: 

	MaxDB INSTANCE UPDATE
STDOUT: 	*********************


STDOUT: starting installation Th, Mar 25, 2004 at 10:54:51
STDOUT: operating system: Linux I386 2.4.21 192-smp4G GLIBC 2.3.2
STDOUT: callers working directory: /incoming/maxdb/maxdb-all-linux-32bit-i386-7_5_0_5
STDOUT: installer directory: /incoming/maxdb/maxdb-all-linux-32bit-i386-7_5_0_5
MSG: InstallRegistry: space check ok: 41497252 kb on / (76547348 kb total) available
MSG: install registry successfully locked
MSG: read 15 PACKAGES
MSG: net registry size = 140777 bytes
WRN: InstallRegistry::reserveSpace(): file >= 1024 kb
STDOUT: 

dependencies for package "Base" resolved
package "Base" has no dependencies
dependencies for package "Base" resolved
package "Base" has no dependencies
dependencies for package "Base" resolved
package "Base" has no dependencies
dependencies for package "Base" resolved
package "Base" has no dependencies
dependencies for package "Base" resolved
package "Base" has no dependencies
dependencies for package "Base" resolved
package "Base" has no dependencies
dependencies for package "Base" resolved
package "Base" has no dependencies
dependencies for package "Base" resolved
package "Base" has no dependencies
dependencies for package "Server Utilities" resolved
dependencies for package "Base" resolved
package "Base" has no dependencies
MSG: no installation data to migrate
STDOUT: beginning to check sap db instances
STDOUT: resume broken instance check
x_server is running
got following x_server data:
version = X32/LINUX 7.4.3    Build 031-121-060-910
dbmsrv uses db_online
dbmsrv uses db_admin
STDOUT: finding instance type...
instance type is OLTP
STDOUT: finding starting release...
kernel executable is /opt/sapdb/depend74/pgm/kernel
kernel version by GetBuildString 7.4.3 Build  031-121-060-910
starting release is 7.4.3 Build  031-121-060-910
STDOUT: finding migration strategy...
migration is using compatible log
from 7.4.3 Build  031-121-060-910
to   7.5.00
STDOUT: looking for running instances...
STDOUT: checking paramfile modifications...
check version of paramfile
kernel version   : 7.4.3 Build  031-121-060-910
paramfile is clean
STDOUT: checking volume access...
analyzing volumes by param_getvolsall
rundirectory     = /var/opt/sapdb/indep_data/wrk/DBNAME
mirrored log     = 0
max data volumes = 11
max log volumes  = 2
database process owner is sapdb:sapdb
KNLTRACE 1 knltrace sapdb:sapdb 666 can be accessed as owner sapdb
DATA     1 /opt/sapdb/DBNAME/DISKD0001 sapdb:sapdb 660 can be accessed as owner sapdb
DATA     2 /opt/sapdb/DBNAME/DISKD0002 sapdb:sapdb 660 can be accessed as owner sapdb
DATA     3 /opt/sapdb/DBNAME/DISKD0003 sapdb:sapdb 660 can be accessed as owner sapdb
DATA     4 /opt/sapdb/DBNAME/DISKD0004 sapdb:sapdb 660 can be accessed as owner sapdb
DATA     5 /opt/sapdb/DBNAME/DISKD0005 sapdb:sapdb 660 can be accessed as owner sapdb
DATA     6 /opt/sapdb/DBNAME/DISKD0006 sapdb:sapdb 660 can be accessed as owner sapdb
DATA     7 /opt/sapdb/DBNAME/DISKD0007 sapdb:sapdb 660 can be accessed as owner sapdb
DATA     8 /opt/sapdb/DBNAME/DISKD0008 sapdb:sapdb 660 can be accessed as owner sapdb
LOG      1 /opt/sapdb/DBNAME/DISKL001 sapdb:sapdb 660 can be accessed as owner sapdb
STDOUT: looking for domain user...
user profile container contains:

  dbm

domain user not found in user profile container
unable to load system tables

load system tables and run SDBUPD again

MSG: write 15 packages
MSG: net install registry size = 140777 bytes
MSG: wrote install registry (185876 bytes)
STDERR: MaxDB instance "DBNAME" not ready to update
STDERR: looking for domain user...
user profile container contains:

  dbm

domain user not found in user profile container
unable to load system tables

load system tables and run SDBUPD again


STDERR: MaxDB instance update exited abnormally at Th, Mar 25, 2004 at 10:54:57
MSG: install registry successfully unlocked



-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=sapdb-general@progressive-comp.com

[prev in list] [next in list] [prev in thread] [next in thread]