cancel
Showing results for 
Search instead for 
Did you mean: 

update SAP DB version 7.3 to Max DB version 7.5

Former Member
0 Kudos

I need HELP

When I try to update SAP DB version 7.3 to Max DB version 7.5 I have some problem.

I send de log

MaxDB INSTANCE UPDATE

STDOUT: *********************

STDOUT: starting installation Su, Nov 05, 2006 at 22:13:40

STDOUT: operating system: Linux I386 2.4.21 278-smp GLIBC 2.2.5

STDOUT: callers working directory: /

STDOUT: installer directory: /reserve/SAPSOFT/DVD_RDBMS_MAXDB_7.5.00_Build_32/UNIX/LINUX_32

MSG: InstallRegistry: space check ok: 11943600 kb on / (15735176 kb total) available

MSG: install registry successfully locked

MSG: read 10 PACKAGES

MSG: net registry size = 94127 bytes

WRN: InstallRegistry::reserveSpace(): file >= 1024 kb

STDOUT: archive directory: /reserve/SAPSOFT/DVD_RDBMS_MAXDB_7.5.00_Build_32/UNIX/LINUX_32

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 "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: existing instance:

STDOUT: 0: RRP "/sapdb/RRP/db" 7.3.0.46

STDOUT: 1: none

STDOUT: please enter instance id:

STDIN: 0

STDOUT: please enter database manager operators name:

STDIN: control

STDOUT: please enter database manager operators password: STDOUT:

STDIN:

STDOUT: resume broken instance check

x_server is not running

SYS: /sapdb/programs/bin/x_server start: 12798 NISERVER server started.

SYS: /sapdb/programs/bin/x_server start: 12751 XSERVER XSERVER started, 'X32|LINUX 7.3.0 Build 046-000-094-454'

x_server is running

got following x_server data:

version = X32|LINUX 7.3.0 Build 046-000-094-454

dbmsrv uses db_warm

dbmsrv uses db_cold

STDOUT: finding instance type...

instance type is OLTP

STDOUT: finding starting release...

kernel version by 'show version' 7.3.0 Build 046-000-094-454

starting release is 7.3.0 Build 046-000-094-454

STDOUT: finding migration strategy...

migration is using consistent data

from 7.3.0 Build 046-000-094-454

to 7.5.00

STDOUT: looking for running instances...

STDOUT: checking paramfile modifications...

check version of paramfile

kernel version : 7.3.0 Build 046-000-094-454

paramfile is clean

STDOUT: checking volume access...

analyzing volumes by param_directgetall

rundirectory = /sapdb/data/wrk/RRP

logmode = SINGLE

maxsysdev = 1

maxdatadev = 7

maxlogdev = 2

database process owner is sqdrrp:sapsys

KNLTRACE 1 knltrace sqdrrp:sapsys 666 can be accessed as owner sqdrrp

SYS 1 /sapdb/RRP/dbsys/SYS sqdrrp:sapsys 660 can be accessed as owner sqdrrp

DATA 1 /sapdb/RRP/sapdata/DISKD0001 sqdrrp:sapsys 764 can be accessed as owner sqdrrp

DATA 2 /sapdb/RRP/sapdata/DISKD0002 sqdrrp:sapsys 764 can be accessed as owner sqdrrp

DATA 3 /sapdb/RRP/sapdata/DISKD0003 sqdrrp:sapsys 764 can be accessed as owner sqdrrp

DATA 4 /sapdb/RRP/sapdata/DISKD0004 sqdrrp:sapsys 764 can be accessed as owner sqdrrp

DATA 5 /sapdb/RRP/sapdata/DISKD0005 sqdrrp:sapsys 764 can be accessed as owner sqdrrp

DATA 6 /sapdb/RRP/sapdata/DISKD0006 sqdrrp:sapsys 660 can be accessed as owner sqdrrp

LOG 1 /sapdb/RRP/saplog/DISKL001 sqdrrp:sapsys 764 can be accessed as owner sqdrrp

STDOUT: looking for domain user...

user profile container contains:

CONTROL

SUPERDBA

domain

sqdrrp

found domain user in user profile container

STDOUT: checking data consistency for database migration...

looking for backup log position

looking for restart info in cold mode

database state is COLD

restart info by dbm:

First LOG Page => 16811968

Id Restart Record => rpone:RRP_20061012_193259

Id LOG Info => rpone:RRP_20061012_193259

Restartable => 1

Used LOG Page => 17084559

Consistent => 1

current log position 17084559

backup log position 17084559

database was stoped with checkpoint

check ability to recover in backup history

KEY LABEL ACTION LOG FIRSTLOG LASTLOG RC

454E3CF80001 DAT_00482 RESTORE NO 17084173 0

454E38960003 DAT_00485 SAVE WARM NO 17084540 0

no up to date data backup found

MSG: write 10 packages

MSG: net install registry size = 94127 bytes

MSG: wrote install registry (120503 bytes)

STDERR: MaxDB instance "RRP" not ready to update

STDERR: checking data consistency for database migration...

looking for backup log position

looking for restart info in cold mode

database state is COLD

restart info by dbm:

First LOG Page => 16811968

Id Restart Record => rpone:RRP_20061012_193259

Id LOG Info => rpone:RRP_20061012_193259

Restartable => 1

Used LOG Page => 17084559

Consistent => 1

current log position 17084559

backup log position 17084559

database was stoped with checkpoint

check ability to recover in backup history

KEY LABEL ACTION LOG FIRSTLOG LASTLOG RC

454E3CF80001 DAT_00482 RESTORE NO 17084173 0

454E38960003 DAT_00485 SAVE WARM NO 17084540 0

no up to date data backup found

SYS: /sapdb/programs/bin/x_server stop: 12721 XSERVER XSERVER stopped

x_server is not running

STDERR: MaxDB instance update exited abnormally at Su, Nov 05, 2006 at 22:14:56

MSG: install registry successfully unlocked

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

> no up to date data backup found

Hmm. Did you already try to backup your db before the upgrade?

Former Member
0 Kudos

Hi Jochen Diehl

Thank you for your email

I did it. I have a full backup of yesterday

Regards

Jose Brunschwig

former_member229109
Active Contributor
0 Kudos

Hello Jose,

Could you please run the following steps:

Please leave the database instance in the cold mode, take a log backup, then complete data backup, and do the update immediately (without starting the database in between).

Please update with your results after that.

Thank you and best regards, Natalia Khlopina

0 Kudos

Hello,

this worked well for me, thanks Natalia for you help

The error in the upgrade log is a bit misleading, "no up to date data backup found"

Maybe the upgrade tool could give a more precise explanation of the error found

Valerio